Related
Hello,
I just tried to install Remix OS 2.0.205 64-bit UEFI boot on my brand new Samsung Galaxy Tab Pro S. The procedure went well and I could boot ok. Unfortunately the touch screen and the wireless are both not working. Rest seems to be ok, but without wireless, there is not much I can do...
Hello....we're you ever able to get this running on your tabpro s? I'm contemplating buying a tabpro.
Sent from my SM-P905V using XDA-Developers mobile app
I just bought this tablet and I would like to know too. I feel like remix on this would be amazing...
Hey, I've confirmed that Remix OS 3.0 does boot on my Galaxy Tab Pro S and the touch screen does work along with the keyboard! Wi-Fi, screen brightness control, and the touchpad is not working though.
mrDmola said:
Hey, I've confirmed that Remix OS 3.0 does boot on my Galaxy Tab Pro S and the touch screen does work along with the keyboard! Wi-Fi, screen brightness control, and the touchpad is not working though.
Click to expand...
Click to collapse
How can this be sorted out as I would love to have this on my Tabpro S!
mrDmola said:
Hey, I've confirmed that Remix OS 3.0 does boot on my Galaxy Tab Pro S and the touch screen does work along with the keyboard! Wi-Fi, screen brightness control, and the touchpad is not working though.
Click to expand...
Click to collapse
Hi I too have a tabpro s, and want to install remix os or stock android. My question is have you install on a partition? or usb stick? if on a partition does it automatically give you an option to boot into windows/ remix? or is there a separate method.
Speaking of brightness is there an option to set the brightness before booting? some laptops had this feature.
last question is installing remix the same as installing a stock marshmallow rom?
nielo360 said:
Hi I too have a tabpro s, and want to install remix os or stock android. My question is have you install on a partition? or usb stick? if on a partition does it automatically give you an option to boot into windows/ remix? or is there a separate method.
Speaking of brightness is there an option to set the brightness before booting? some laptops had this feature.
last question is installing remix the same as installing a stock marshmallow rom?
Click to expand...
Click to collapse
I'm going to install it on my Tabpro S tonight and will report back.
Biggenz said:
I'm going to install it on my Tabpro S tonight and will report back.
Click to expand...
Click to collapse
EDIT2: or these methods also from the xda remix 3.0 threads
In /system/build.prop change ro.remixos.box=true to false (should give brithness icon on the bottom)
or
Use Fn+left or right key combination
or
Edit: try this https://play.google.com/store/apps/details?id=com.curvefish.widgets.brightnesslevelGreat!
it was mentioned on another xda remix 3.0 thread.
looking forward to it Im waiting for my usb adapter but might consider the partition method if brightness can be lowerd via a work around to save battery or fixed.
I installed it last night and can confirm what mrDmola said. Everything works fine apart from wifi and screen brightness. For me the keyboard and track pad DID work. Such a shame as it's a brilliant OS.
Are there any developers who can sort this out for some beer money?
I'd donate if someone was willing to fix WiFi and brightness as its an excellent device for dual booting. Currently I use splashtop windows store version to stream ami duo os android from my desktop. It works flawlessly lag free with most games and touch screen works well with splashtop. I'd prefer remix however as a native os.
nielo360 said:
I'd donate if someone was willing to fix WiFi and brightness as its an excellent device for dual booting. Currently I use splashtop windows store version to stream ami duo os android from my desktop. It works flawlessly lag free with most games and touch screen works well with splashtop. I'd prefer remix however as a native os.
Click to expand...
Click to collapse
I tried installing Android-x86 but that doesn't even boot. I just get a black screen and my Tabpro S becomes unresponsive. I couldn't switch it back on and nearly got worried. A soft reset sorted it out.
Then I also tried Phoenix OS which works fine on my PC, but same again on the Tabpro, it won't boot. Just goes black screen and then nothing.
Nielo have you tried Phoenix OS by any chance? If not could you try to install it and let me know your findings please?
Biggenz said:
I tried installing Android-x86 but that doesn't even boot. I just get a black screen and my Tabpro S becomes unresponsive. I couldn't switch it back on and nearly got worried. A soft reset sorted it out.
Then I also tried Phoenix OS which works fine on my PC, but same again on the Tabpro, it won't boot. Just goes black screen and then nothing.
Nielo have you tried Phoenix OS by any chance? If not could you try to install it and let me know your findings please?
Click to expand...
Click to collapse
I haven't tried that OS, I will try remix os if I can find a wifi fix. I'm still waiting for my Samsung usb adapter to boot via usb
nielo360 said:
I haven't tried that OS, I will try remix os if I can find a wifi fix. I'm still waiting for my Samsung usb adapter to boot via usb
Click to expand...
Click to collapse
Phoenix OS is very similar but I prefer Remix OS.
Why is it so hard for someone to tell us how to fix this problem?
nielo360 said:
Hi I too have a tabpro s, and want to install remix os or stock android. My question is have you install on a partition? or usb stick? if on a partition does it automatically give you an option to boot into windows/ remix? or is there a separate method.
Speaking of brightness is there an option to set the brightness before booting? some laptops had this feature.
last question is installing remix the same as installing a stock marshmallow rom?
Click to expand...
Click to collapse
I installed on a partition It automatically gave me the option to boot into windows or remix OS. I had to change the boot settings in my bios first before I was able to do any of this though
Without wifi most games wont work so trying it would not be useful, but its good to see the touchscreen working. 2.0 had issues with touchscreens
WiFi drivers needed
Hey, I just installed the latest version of 3.0 as of 12th october 2016
Touch screen WORKS! (Unlike Surface Pro 4)
Touch pad now works
Keyboard works
*But the deal breaker remains Wifi*
Tab Pro S uses a Qualcomm wifi chip and obviously there are no drivers for it installed in the build of Android x86 that Remix OS are using.
Can't we just add these ourselves? Or do the drivers simply not exist for Android on x86?
Other quibbles but not as problematic...
No bluetooth
No screen brightness control
No battery info or charge levels
All again just driver issues.
It really would be wonderful to get this working as there are no other premium Android tablets on the market with a faster chipset than an iPad Pro and an AMOLED screen for 750 euros
Hey guys I have been making some progress with a rooted custom build of Remix OS.
The WiFi adapter chipset in the Tab Pro S is the Qualcomm QCA6174. The Linux drivers which come packaged with the Remix OS kernel as it stands do not work.
There are the same QCA6174 issues with Linux based OS - https://bbs.archlinux.org/viewtopic.php?id=204871
Following from that research I downloaded a few different versions of the QCA6174 driver from Github and it appears the filenames need to be a certain way for it to be picked up by Remix OS / Android x86 (see guide below).
The result is I can now get the WiFi hardware to be detected OK by Remix OS and it switches on, starts searching for access points... However we are not quite there yet. It does not actually detect any SSIDs or connect to the internet. So I need to figure out from the error logs why that is.
Bluetooth seems to now work as well - was able to show a list of discoverable devices and pair with my phone, but not pick up a LTE personal hotspot for the internet.
Seems something basic to do with TCP/IP or Ethernet connectivity is broken?
By the way all this needs root access to Remix OS. I used this guide to root - http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
Also I had to install a custom version of Remix OS with the bloatware removed and a more powerful File Manager along with Super User app pre-installed. I used this version based on Jide's v3.0.202 -
http://forum.xda-developers.com/remix/remix-os/remix-os-pc-hacked-edition-ota-v2-0-201-t3345968
You also need to edit a file on the EFI partition in Windows before rebooting to get proper root access. To add the REMOUNT_RW=1 flag to the kernel you are going to be editing the grub.cfg file in the /BOOT directory of your EFI partition and this won't be mounted in Explorer. To mount this using the guide I linked to above in Windows 10 it is important to run the command prompt as an administrator (right click, run as...) even if you are logged in as admin. By default it will run in user mode and you won't get permission to access the EFI partition at all.
So in summary -
1. In Windows install the custom version of Remix OS from here:
2. You do NOT need to install it on a separate partition, put it on C:/ drive
3. Do not reboot Windows after the installer finishes, instead run the Command Prompt (right click, run as admin)
4. Type command and enter - taskkill /im explorer.exe /f
5. Type command and enter - mountvol X: /s
6. Type command and enter - explorer.exe
7: Type command and enter X: and then cd to directory boot/grub
8: Edit the grub.cfg file in X:/boot/grub (command prompt - notepad grub.cfg) - please note DOS edit command removed from Windows 10 so it will open in Notepad
9. Add the line REMOUNT_RW=1 in the kernel commands, the line should look like this -
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1
10. Reboot
11. At dual boot option screen select Remix OS and it will finalise installation, before booting to Remix OS desktop
12. Run Super User app, ignore message about it needing to search for an update
13. At the desktop run cyanogenmod File Manager (not the Mac OS style Remix OS one as it has no root access) and go to the root /system folder, grant full read/write privileges in Super User app when prompted
14. You will need to copy the QCA6174 driver files from a USB drive. These files you should download from here on a machine with internet access:
https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0
In Remix OS these belong in the following folder:
/system/lib/firmware/ath10k/QCA6174/hw3.0/
In the driver package downloaded from github the file "firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1" needs to be renamed firmware-4.bin
Make sure files are named as follows:
firmware-4.bin
board-2.bin
board.bin
15. Reboot and the WiFi hardware will now switch on in Remix OS and begin searching for access points, bluetooth should detect nearby devices.
Other stuff which I found currently works:
Touchscreen (it does not on Surface Pro 4 so big reason to use Tab Pro S!!)
Trackpad
Keyboard
Audio, with reservations (system sounds audible like tapping in calculator app, but MP3 media audio didn't work in bundled player)
To do:
Final fixes to WiFi
Screen brightness control
Battery charge level and standby (it can only tell if connected to A/C, no battery polling levels detected)
Further check audio and app compatibility once WiFi is working
Great job thanks for your work on the issues looking forward to working wifi!
Is Remix OS better in terms of battery life?
My ProS doesnt last long with screen switched off, unless I shutdown windows.
commanderspike said:
Hey guys I have been making some progress with a rooted custom build of Remix OS.
The WiFi adapter chipset in the Tab Pro S is the Qualcomm QCA6174. The Linux drivers which come packaged with the Remix OS kernel as it stands do not work.
There are the same QCA6174 issues with Linux based OS - https://bbs.archlinux.org/viewtopic.php?id=204871
Following from that research I downloaded a few different versions of the QCA6174 driver from Github and it appears the filenames need to be a certain way for it to be picked up by Remix OS / Android x86 (see guide below).
The result is I can now get the WiFi hardware to be detected OK by Remix OS and it switches on, starts searching for access points... However we are not quite there yet. It does not actually detect any SSIDs or connect to the internet. So I need to figure out from the error logs why that is.
Bluetooth seems to now work as well - was able to show a list of discoverable devices and pair with my phone, but not pick up a LTE personal hotspot for the internet.
Seems something basic to do with TCP/IP or Ethernet connectivity is broken?
By the way all this needs root access to Remix OS. I used this guide to root - http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
Also I had to install a custom version of Remix OS with the bloatware removed and a more powerful File Manager along with Super User app pre-installed. I used this version based on Jide's v3.0.202 -
http://forum.xda-developers.com/remix/remix-os/remix-os-pc-hacked-edition-ota-v2-0-201-t3345968
You also need to edit a file on the EFI partition in Windows before rebooting to get proper root access. To add the REMOUNT_RW=1 flag to the kernel you are going to be editing the grub.cfg file in the /BOOT directory of your EFI partition and this won't be mounted in Explorer. To mount this using the guide I linked to above in Windows 10 it is important to run the command prompt as an administrator (right click, run as...) even if you are logged in as admin. By default it will run in user mode and you won't get permission to access the EFI partition at all.
So in summary -
1. In Windows install the custom version of Remix OS from here:
2. You do NOT need to install it on a separate partition, put it on C:/ drive
3. Do not reboot Windows after the installer finishes, instead run the Command Prompt (right click, run as admin)
4. Type command and enter - taskkill /im explorer.exe /f
5. Type command and enter - mountvol X: /s
6. Type command and enter - explorer.exe
7: Type command and enter X: and then cd to directory boot/grub
8: Edit the grub.cfg file in X:/boot/grub (command prompt - notepad grub.cfg) - please note DOS edit command removed from Windows 10 so it will open in Notepad
9. Add the line REMOUNT_RW=1 in the kernel commands, the line should look like this -
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1
10. Reboot
11. At dual boot option screen select Remix OS and it will finalise installation, before booting to Remix OS desktop
12. Run Super User app, ignore message about it needing to search for an update
13. At the desktop run cyanogenmod File Manager (not the Mac OS style Remix OS one as it has no root access) and go to the root /system folder, grant full read/write privileges in Super User app when prompted
14. You will need to copy the QCA6174 driver files from a USB drive. These files you should download from here on a machine with internet access:
https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0
In Remix OS these belong in the following folder:
/system/lib/firmware/ath10k/QCA6174/hw3.0/
In the driver package downloaded from github the file "firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1" needs to be renamed firmware-4.bin
Make sure files are named as follows:
firmware-4.bin
board-2.bin
board.bin
15. Reboot and the WiFi hardware will now switch on in Remix OS and begin searching for access points, bluetooth should detect nearby devices.
Other stuff which I found currently works:
Touchscreen (it does not on Surface Pro 4 so big reason to use Tab Pro S!!)
Trackpad
Keyboard
Audio, with reservations (system sounds audible like tapping in calculator app, but MP3 media audio didn't work in bundled player)
To do:
Final fixes to WiFi
Screen brightness control
Battery charge level and standby (it can only tell if connected to A/C, no battery polling levels detected)
Further check audio and app compatibility once WiFi is working
Click to expand...
Click to collapse
Great work! Hope we will see the wifi working soon. I bought the tab pro s to replace my ipad pro, now it basically sit in dust, was thinking about selling it until I see this post.
For me and some users, while typing, or even scrolling up and down, time to time we see black virtual cursor for 0.5 sec
It's show ups for me about 10-100 times a day, very annoing!
I have seen this bug on every custom roms like RR 5.8.2, lineage os 14.1, Purenexus, etc, installed by TWRP 3.1.0-1 by nijel8/3.1.0.0 official one by strix
Changing different firmwares 7.2.9-7.3.16 - not helped.
Did a clean install throuth Mi flash tool - not helped.
Any ideas, how to fix this bastard?
Could it be recovery or even hardware problem?
If it were indeed a hardware issue, wouldn't we be seeing it on stock miui as well?
I suppose we need a common denominator - something that the custom roms have, but miui doesn't.
1) could it be related to root permissions? Has it been seen on both rooted and non-rooted devices?
2) Does it depend on how the ROM is flashed?
3) Has it been seen on other xiaomi phones? I assume both hydrogen and helium are impacted
just thinking out loud, what if we disable HID client drivers or the entire mouse support in kernel?
lukacsp said:
just thinking out loud, what if we disable HID client drivers or the entire mouse support in kernel?
Click to expand...
Click to collapse
Already tried and not helping.
Let start by taking some setup info and logs, guys. Make sure you have ran phone for a while and have seen cursor appearing at least few times. Run these commands on PC with phone USB connected:
Code:
adb shell dumpsys > c:\dumpsys.txt
Code:
adb shell dmesg > c:\dmesg.txt
Code:
adb shell logcat -d > c:\logcat.txt
or run their respective equivalents on phone terminal emulator...
Zip those files and post them here.
Haha I just saw the black mouse cursor pop up for a split second on my Helium running Pure Nexus. It's really not a big deal though. I'm sure it will eventually be fixed. It only pops up for like one tenth of a second. I'ts not even annoying but kind of funny.
Never seen it on my helium , on any Rom but then again i don't really stare at the screen looking for a cursor haha
Sent from my Mi Max using Tapatalk
Happening on Hydrogen RR5.8.2 - been happening on a few builds every now & again; annoying but not a deal breaker.
never seen on NitogenOS, but I saw it last day when I was trying nijie8's lineage, scroll up/down on the settings' About phone when back from about lineage.
Helium 3G/64G.
nijel8 said:
Already tried and not helping.
Let start by taking some setup info and logs, guys. Make sure you have ran phone for a while and have seen cursor appearing at least few times. Run these commands on PC with phone USB connected:
or run their respective equivalents on phone terminal emulator...
Zip those files and post them here.
Click to expand...
Click to collapse
I decided to clean flash your latest lineage 14.1 rom build 27.03.17 via your latest twrp 3.1.0-1, with latest firmware 23.03.17, and latest pico gapps 01.04.17
magic is happen, idk how, but for 3-4 days, I didn't see this mouse cursor bug at all... only one app that I didn't install is Google app for Google now (don't think that is a reason). BTW mb last kernel setup with hot plugging small cores give us instability and bugs ?
Will check for a while and get feedback if something changes.
It's a bug reported on Lineage's Jira. Here it is https://jira.lineageos.org/plugins/servlet/mobile#issue/REGRESSION-214
nijel8 said:
Already tried and not helping.
Let start by taking some setup info and logs, guys. Make sure you have ran phone for a while and have seen cursor appearing at least few times. Run these commands on PC with phone USB connected:
or run their respective equivalents on phone terminal emulator...
Zip those files and post them here.
Click to expand...
Click to collapse
After a free week of mouse cursor bag, I decided to reboot device..
After rebooting this bug coming back in 2-3 minute... WTF )
It happens to me on Pure Nexus which leads me to believe it's not a Lineage bug.
ajsmsg78 said:
It happens to me on Pure Nexus which leads me to believe it's not a Lineage bug.
Click to expand...
Click to collapse
We should to get some logs to nigel to fix this bastard
Get notice it on NitrogenOS v20170330...
Who used Android 7.1.2, bug still there ?) For a while, im coming back to MIUI Android 7, coz of this annoying bug
Resurrection Remix 7.1.2 Helium. BLACK VIRTUAL CURSOR CONFIRMED
Lineage OS 7.1.1-7.1.2 Helium. BLACK VIRTUAL CURSOR CONFIRMED
i noticed a battery drain since i first noticed the black cursor problem.
i started to think it is a stuck background process that kills battery. ( am i being so psychopath ? )
No cursor here. RR 5.8.3 on Helium. 7.4.13 firmware.
I have not seen the cursor in the last 11 days after enabling Settings -> Accessibility -> Large mouse pointer.
No i m not infected on any rom
I also occasionally see it. I am on stable MiUi 10 stock rom, but rooted with twrp & magisk
Yes you heard it right!
It's finally done!
Its a custom ROM for the WIKO RAINBOW JAM!
The porting community for this phone is so small that the phone isn't even listed at this site. (Thanks XDA)
!Sorry that I posted that thread at the Wiko Rainbow Forum!
I don't know if this works on the 8gb version of the phone, which means only the 16gb variant is supported now.
____________________________________________________________________________________________________________
UPDATE !
Android MM (6.0) has some really annoying porting bugs(especially camera) which cause bootloops for example and I would even say, that porting Nougat to this phone is a LOT easier than fixing these bug(which doesnt mean, I'm not going to fix them)
Even newer update:
I tried like 2 months getting the camera to work and NONE of my builds worked out.
I think I have to accept, that the camera drivers are just stuck on Android 5.1 or even just the original Stockrom.
So now there is a VERY experimental build of the Ressurection Rom for the Wiko Rainbow Jam.
(Bluetooth, Camera, and a lot of Apps like CM-Audio dont work correctly
+ phone sometimes randomly reboots)
Yeah , this build can be installed exactly the same like the other one (exept the MM-Gapps)
v.01 = "https://mega.nz/#!E51imQgZ!FfoRt1kltg7_qkXSa2lAQTlK8Q2m1Mg6zs4E9WnQb54" (This has a bootloop!)
v.02 = https://mega.nz/#!gp1ATSCA!dJcc6YvSp-9ZFkv1sfETZpU_623mj9SrvvGiq6Y18ks (Known bugs mentioned earlier)
DONT FORGET TO WIPE DALVIK AND REFORMAT THE DATA PARTITION!
___________________________________________________________________________________________________________________
This is for the 3G version ONLY!
This rom is nearly completly untested and bugs shouldn't be a rarity.
PRE-REQUIREMENTS:
-A working WIKO RAINBOW JAM
-A Internet Connection
-Enough time to read my Instructions
-A USB-OTG Cable + USB MOUSE !IMPORTANT!
-Windows PC (Windows 7 or above)
-At least 80% Battery
What works?
WIFI / BT
Dual-Sim detection
SMS/MMS
Vibration
All of the buttons
Every app i tested till now...
Calling someone
Screen (Brightness / Pixel / Touchscreen ...)
Voice recording
720p YouTube playback ( The phone has a 50 hz display which means 60fps videos are experimental!)
Regular internet browsing via Chrome
+ The new Lineage OS 13 Features
Doesn't work
Camera ... fix will come soon!
Wrong Internal Storage detection ( only shows 1.45 gb in total)
UPDATE : to fix this problem you have to boot into recovery mode > wipe > Advanced wipe > check data > confirm
+ go to advanced wipe again > FS options > Repair FS > THEN RESIZE the partition
The Rom has still the build.prop from the phone I took the PortRom from ( INFINIX X510)
Feel free to post Feedback !
Modifications to the rom are welcome!
I WILL TAKE NO WARRANTY IF YOU BRICK YOUR PHONE . ALWAYS MAKE A BACKUP
HOW TO INSTALL.
1. : Download the zip file I uploaded : "https://mega.nz/#!dh9S2K4D!WsZlBayDdI-kIAj0bgJp5f9xUEtQWZU63WDGKcnM_rY"
2. : Extract everything and open the SmartPhoneFlashTool (SPFT) . Now search for the flashtool.exe ( YES this guide is for Windows)
3. Go to the Download tab and select the Android scatter file from the "Files for flashing" folder.
4. You should see that all of the fill the boxes up automaticaly.
5. Say goodbye to your old Lollipop rom and to your internal storage. Then shut the phone down!
6. Click the "Download" button first! and then connect your phone via USB to your computer.
7. If your drivers are setup correctly the bar below should start blinking and the phone is about to be flashed (DON'T UNPLUG THE PHONE NOW)
8. If the green "check" shows up you can safely disconnect your phone from the PC
YOU NEED A USB-OTG Cable now because the TWRP recovery has a broken touchscreen support
9. Boot into Recovery Mode via pressing "POWER BUTTON" + "VOL-UP". (Thanks to the creator of the Recovery!)
10. Use the USB Mouse to wipe the Dalvik Cache ( Wipe/Advanced Wipe/"now check only Dalvik Cache" ) and confirm you action
11. Reboot and optionally install GAPPS ( ARM Marshmellow Android 6.0) and root via SuperSU if you want
Proceed with the phone setup and you are ready to go...
I added all my source as a .txt file to the downloadable zip I mentioned earlier.
_______________________________________________
Is it hard to instal im a boob with phones and computer s :silly:
I would recommend a bit of knowledge on the whole flashing thematic. Just following the the instructions should be fine.
Just be sure that you have enough time to download the file properly and have at least 20 min of your time for the flashing process.
Camera fix
great rom, thanks. for when camera bug fix?
I dont know when this feature will work again. I tried so many bugfixing tutorials that i don't know where to start. It will probably be fixed in a few weeks, but from know on i need to wait until summer vacation because of school . That means that the project isn't dead yet
Dunno if someone is still interested in this device, anyway here's an interesting directory for those who are able to port ROMs:
https://androidfilehost.com/?a=show&w=files&flid=247444
...hope that inspires !
Hello,
Mega is asking for a key ??
Friendly,
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Known issues:
You tell me
Instructions :
1. Boot into twrp
2. Advanced -> ADB Sideload -> Swipe
3. adb sideload copy-partitions.zip
4. Go back into sideload mode
5. adb sideload lineage.zip
6. Wipe Data
7. Reboot to bootloader
8. fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Downloads :
https://build.lolinet.com/file/lineage/ginna/
Source Code: https://github.com/motoe7
ROM OS Version: LineageOS 17.1
ROM Kernel: Linux 4.9
Version Information
Status: Stable
Credits:
Electimon - The entire device bringup
Rohan Hasabe - TWRP bringup, helped with device bringup
betaxab - Gave devices, helped with TWRP and device bringup
2/6/2021:
Fixed random crashes - https://build.lolinet.com/file/lineage/ginna/lineage-17.1-20210206-UNOFFICIAL-ginna.zip
Thanks to everyone who contributed to these bits, I'm hopeful that by the end of the year I will be using my new moto-e-2020 as my main phone to replace my aging moto-g-2015. I've got a couple first bugs/issues/showstoppers to report, but first I think it's important to note-
Finally I'm able to go to walmart (in the usa) and buy a sub $100 ($70) 'roid (boostmobile) phone (meeting some other criteria as well) which I can immediately install a (mostly?/sdks/tools) non-google-built os on. I erred a bit by doing lots of research (to avoid paying more for a moto g7) and forgetting that the moto-e-2020 is *not* at the moment on motorola's list of models their registered (free) dev program will give bootloader unlock codes for. However after thinking I was going to have to return the phone, I parsed the verbiage on their page and decided to just try 'fastboot oem get_unlock_data'. Then tried going through motorola's unlock code process. To my pleasant surprise, they did give me an unlock code. My next hiccup happened when I was disappointed to discover the 'allow oem unlucking' option was greyed out. I netsearched and found a similar samsung issue that was resolved on phones that hadn't been updated/activated by setting their date back a week. That didn't work here, but what did work was giving my new phone access to wifi and letting it start an update. After a few minutes, while it was still updating, the 'allow oem unlocking' was no longer greyed out, and the rest of the install was straightforward enough (getting used to a and b slots for recovery).
Anyway, as for the first glaring issues-
1) random reboots, seemed at first yesterday it would average less than 10 minutes of uptime and rarely an hour. Seems a bit better right now, I'm seeing if I can get some adb logcat output of interest. Let me know if there are other tests/logs I should do. I haven't yet tried the modded lineageos18. The image I used was lineage-17.1-20210119-UNOFFICIAL-ginna.zip.
2) mobile data won't work. I note that I first activated after installing this rom. I wonder if it would have helped to activate with stock android like I probably did long ago with my moto-g-2015. Note that it shows up as 't-mobile', however given my moto-g with boost showed up as 'sprint' and boost using sprint infra which merged with t-mobile recently...? My aboutphone:simstatus shows 'network:t-mobile', 'mobile network state:disconnected' (but mobile data enabled). If I uncheck automatic network selection, I can click on 'boost' by name on a list (that doesn't include t-mobile) and it will say 'connected' right away, but with no change I see otherwise. There was a weird thing with activation as an additional line, boost first charged me $20, then later charged me $30. And the confirmation sms for the activation happened hours later, but mobile data still isn't working.
3) I'd like to know if twrp is really necessary. I noticed a recovery.img in the download directory, guessing that might be the lineageos17.1 version I was happy to see available for my moto-g-2015. I'm guessing I could try it myself, but I would like to avoid brick-risky things.
4) I wonder if the 'your phone has an unlocked bootloader / can't be trusted' post unlock splash screen can be changed (with the same?) images that are available for the moto-g-2015 (that I read can be used on some other models as well). At least with the moto-e-2020 the splash has a black background.
Feel free to let me know if there are tests I can do or logs I can provide to help. Looks very promising, but not quite usable for me so far.
hi yes please do
adb logcat > logcat.txt
and send me the logcat.txt after around 10 seconds of it running
i've fixed the random crashes.
2/6/2021:
Fixed random crashes - https://build.lolinet.com/file/lineage/ginna/lineage-17.1-20210206-UNOFFICIAL-ginna.zip
Electimon said:
2/6/2021:
Fixed random crashes - https://build.lolinet.com/file/lineage/ginna/lineage-17.1-20210206-UNOFFICIAL-ginna.zip
Click to expand...
Click to collapse
Confirmed (so far, but I'm optimistic). Also I'm quite happy to report that mobile data is now working for me as well (maybe just a reinstall would have fixed?).
The most glaring (new?, not sure) issue/bug now is that speaker output doesn't seem to work except during calls. If I plug in headphones I do get output. Jacksensing failure could be an explanation?
Then after that, I'm getting the sense that the microphone level/gain is not good. Testing by leaving a vmail on my moto-g-2015 the level of the audio on the message seems too low. That is seperate from the longstanding issue I have had with the moto-g-2015/lineage output level. Long ago there was a known issue with a mixer_paths.xml workaround, though I've just lived with seeming lower, but barely tolerable, level since then. I've always planned on going full aosp rebuild with removing whatever softvol max limits are in place whereever. But the mote-e-2020 definitely doesn't have that problem (side by side comparison of same vmailbox checking). But it does seem with this rom the mote-e-2020 has too low mic/gain level. Seems like there could be a standardized testrig used for lineageos qa that could report expected decibel levels/metric on the devices wiki so people know what to expect.
In any event this update will definitely let me get to more serious testing.
Also worth noting, I did the upgrade by repeating the install steps. I noticed that on the copy partitions sideload it ends with an error after doing a lot of partitions fine, then ending with vendor(_b) "dd /dev/block/dm-2: write error: no space left on device". I think that may have happened on my initial install and I just ignored it, and it doesn't seem to matter (yet, afaict).
Ok, can you post a logcat while trying to play audio? Thanks
also, perhaps canceling what I said about in-call output levels, I discovered I'm only getting audio during calls with headphones(jack or usb) or when speakerphone is on. I.e. what I was interpreting as good in-call audio output level in non-speakerphone mode seems to really be a not very loud speakerphone mode output. And interesting to note that the default(?remembered?) setting after installing the rom is speakerphone-on. And to what I mentioned about the mic level, I tried a set of bluetooth earbuds with mic and left equivalent voicemails, and it was clear the bluetooth mic was at standard level, while the phone mic was quite low. That led me to want to try the same test with the default soundrecorder app, but curiously it seems unable to record from (this) bluetooth mic, getting input from the phone mic even when earbuds are connected. I noted the bt/dev settings have on/off for 'phone calls' and 'media audio'. Maybe it's just not supported by these earbuds/headset. I'll check 18.1 when I go back next. Though the mic level on the recorded audio there sounded acceptable compared to the low in-call voicemail test.
Also, is there any difference and a way to install the lineage-17.1-20210207-0753-ginna-25.zip. I'm testing with 0206-UNNOFFICIAL.
Not gonna lie, super excited about this! I never thought that this device would gain traction on XDA due to it being a very low budget device but boy am I glad it's getting some love.
I'm having some trouble here. I can flash Lineage no problem in TWRP the phone just won't boot. So then I try to follow the instructions exactly and get this...
So my moto e booted into Lineage unexpected (I didn't think it would). Nevertheless I'm going to share the command lines I followed since some suggest they failed and I find that strange since Lineage is thus far working.
V:\Everything Android\platform-tools>fastboot devices
ZY227J63CQ fastboot
V:\Everything Android\platform-tools>fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.016s]
Finished. Total time: 0.049s
V:\Everything Android\platform-tools>fastboot devices
ZY227J63CQ fastboot
V:\Everything Android\platform-tools>adb sideload copy-partitions.zip
serving: 'copy-partitions.zip' (~47%) adb: failed to read command: No error
V:\Everything Android\platform-tools>adb sideload lineage-17.1-20210206-UNOFFICIAL-ginna.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
V:\Everything Android\platform-tools>adb sideload lineage-17.1-20210206-UNOFFICIAL-ginna.zip
Total xfer: 1.00x
V:\Everything Android\platform-tools>fastboot devices
ZY227J63CQ fastboot
V:\Everything Android\platform-tools>fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.015s]
Finished. Total time: 0.023s
V:\Everything Android\platform-tools>
Also, about half the internal storage is apparently taken, I must've done something wrong in the flashing process?
Cyb3rSl4v3 said:
also, perhaps canceling what I said about in-call output levels, I discovered I'm only getting audio during calls with headphones(jack or usb) or when speakerphone is on. I.e. what I was interpreting as good in-call audio output level in non-speakerphone mode seems to really be a not very loud speakerphone mode output. And interesting to note that the default(?remembered?) setting after installing the rom is speakerphone-on. And to what I mentioned about the mic level, I tried a set of bluetooth earbuds with mic and left equivalent voicemails, and it was clear the bluetooth mic was at standard level, while the phone mic was quite low. That led me to want to try the same test with the default soundrecorder app, but curiously it seems unable to record from (this) bluetooth mic, getting input from the phone mic even when earbuds are connected. I noted the bt/dev settings have on/off for 'phone calls' and 'media audio'. Maybe it's just not supported by these earbuds/headset. I'll check 18.1 when I go back next. Though the mic level on the recorded audio there sounded acceptable compared to the low in-call voicemail test.
Also, is there any difference and a way to install the lineage-17.1-20210207-0753-ginna-25.zip. I'm testing with 0206-UNNOFFICIAL.
Click to expand...
Click to collapse
Also not getting audio from speakerphone, just headphones. I cannot comment on calls as I'm not using the device as a phone.
Lahpyrcopa said:
Also not getting audio from speakerphone, just headphones. I cannot comment on calls as I'm not using the device as a phone.
Click to expand...
Click to collapse
This morning my first recompile from source finally finished (took a solid couple days and an impressive swap storm on an 8G system (and cough 18G of swap used that I saw. perhaps mka -j 2 will help (default -j left 4 massive java processes running, metalava something or other)). I'll post more as I progress. I had to comment most of device/motorola/ginna/libshims/Android.mk to get it to compile. I was guess/expecting wifi tethering not to work, it seems to say no sim / phone service, though I had let my plan lapse.
But the cool thing is that I do now get speaker out. Another issue is that the recovery.img doesn't want to flash (preboot verification failed, I'll see if I can still reflash twrp next). And now that I've verified I can can compile moto-e-2020/17.1 (after having gotten moto-g-2015/17.1, with CPU_SSE42=false and JAVA_TOOL_OPTIONS=-Xmx6g, kept for e-2020), I'll go try 18.1 again to see if I can get it built without gapps (though I did recently renotice a /d/gapps app on f-droid). I had an issue with libllvm_android/LegalizeIntegerTypes there on my last attempt, but perhaps a fresh start (and reposync) will help me there as it did on 17.1 (which I'm quite optomistic I'll be happy enough with if need be soon enough).
also, I discovered that MotoBootLogoMaker from another xda thread does work (on linux/debian/mono to boot), and while I haven't tried replacing the untrusted/orange unlocked bootloader warning yet, I was able to extract that image with the tool, so I'm hopeful it can be replaced (perhaps excepting the small 'N/A' rendered font text which could perhaps be obscured by some whiter pixels in a custom logo/splash/background, or maybe the font/color is tweakable with that tool too).
Damn, it must take a very beefy machine to operate on android to take days to compile the system.
Well like I said before I only really need the headphone jack working for audio and that creepy message that Moto gives about having an unlocked phone that can't be trusted is absolutely hilarious . Look, I get it Motorola if you read this, you don't want to be liable for jack all nor do any of these even bigger empires. Just tone the scare tactics down a smidge so I can breathe!
To the developer, thanks for your effort. I thought that given the price of the device no one would bother with it.
clarifying a few points above-
- i had forgotten the twrp install step of via .zip (including magiskboot and ramdisk-recovery.cpio stuffs). I.e. I was just able to use the lineage171 recovery to install its build, but just not to install itself as twrp can (perhaps an a/b magisk thing, not sure maybe I saw that was a known thing until lineage adds that functionality? Perhaps I could reuse the twrp zip, or presumably better start building twrp from github now that I'm past the point of having a building lineage tree to use for that purpose)
- indeed MLBM can replace the orange bootloader unlocked splash/logo (which unlike moto-g-2015, is shown after a few milliseconds of the normal seperate logo image). But it doesn't look like there is a way (yet?) with MLBM to effect the 'N/A' text/font/color which remains (again, presumably obscurable if you put an area of white pixels over it on your custom replacement)
- my specific 17.1(and 18.1) build issue with device/motorola/ginna/libshims/Android.mk not-so-much-of-a-workaround-because-simdetection/calling-no-longer-works was a result of this-
"
FAILED: finishing build rules ...
Error: makefile error
Output:
ESC[1mdevice/motorola/ginna/libshims/Android.mk: ESC[31merror:ESC[0mESC[1m "libqsap_shim (SHARED_LIBRARIES android-arm64) missing libqsap_sdk (SHARED_LIBRARIES android-arm64)" ESC[0m
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
ESC[1mdevice/motorola/ginna/libshims/Android.mk: ESC[31merror:ESC[0mESC[1m "libqsap_shim (SHARED_LIBRARIES android-arm) missing libqsap_sdk (SHARED_LIBRARIES android-arm)" ESC[0m
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
ESC[1mbuild/make/core/main.mk:972: ESC[31merror: ESC[0mESC[1mexiting from previous errors.ESC[0m
"
At one point, still even earlier in noob mode, I guessed and tried treating (iirc) /vendor/{lib,lib64}/libqsap_sdk.so as perhaps missing device blobz, and/or went with ALLOW_MISSING_DEPENDENCIES=true. Maybe I'll try again now that I've otherwise got a successful build. I'm doing all this just using the 3 android_ repos from github.com/motoe7. Let me know if I should be using any of the other repos.
Cyb3rSl4v3 said:
I'm doing all this just using the 3 android_ repos from github.com/motoe7. Let me know if I should be using any of the other repos.
Click to expand...
Click to collapse
github.com/LineageOS/android_system_qcom seems to be the answer to my libshims/libqsap_sdk.so issue. I now have a build that at first glance at least is a good reproduction with the addition that speaker out now works for me. Still no in-call volume control. Though as I typed that I see that I seem to be getting crashes similar to what I first reported here but were fixed with the update build. I'll skim my logs a bit...
and seeing the recent git commits and motog7/17.1/nightlies thread (and my log) it seems I can live without MotoActions for the timebeing. I may try toggling some of the recentish audiofx things at some point to see if that gets the in-call volume control working. Also, /d/gapps seems to not apply without root, but I'll try building 18.1 again.
Is this ROM mostly functional? RE: Voice, data, sms? Is it Gapps free?
Just got this phone yesterday & want to start w/ an aged, working build before experimenting further. Open to other suggestions, just want to be free of Goog apps & framework...
Thanks to all who have taken the time to make this affordable phone tweekable.
googleverifysux said:
Is this ROM mostly functional? RE: Voice, data, sms? Is it Gapps free?
Just got this phone yesterday & want to start w/ an aged, working build before experimenting further. Open to other suggestions, just want to be free of Goog apps & framework...
Thanks to all who have taken the time to make this affordable phone tweekable.
Click to expand...
Click to collapse
From my experience it is 80% stable with certain glitches that occur.
I've tried flashing multiple different build of this ROM, and everything is working great, except when I try to flash GAPPS (anything besides pico) and I get an error about having no space on my /system partition.
When flashing PICO gapps, the installation finishes, but the OS fails to boot afterwards.
Any ideas? I've tried Lineage 17 and 18 now and can't get either to work.
googleverifysux said:
Is this ROM mostly functional? RE: Voice, data, sms? Is it Gapps free?
Just got this phone yesterday & want to start w/ an aged, working build before experimenting further. Open to other suggestions, just want to be free of Goog apps & framework...
Thanks to all who have taken the time to make this affordable phone tweekable.
Click to expand...
Click to collapse
It is gapps free, and everything is working on my Moto E. Can't get GAPPS to flash for the life of me though.
I recently bought Asus Zenfone, because here in Ukraine is war, so I want small device with Windows (electricity often is off here because rockets fall on our electrric infrastructure etc).
So I've bought Asus Zenfone 2 used (it costed 16,25$). It came without accumulator, and 1/3 screen working. So I went to radio-market to buy new battery, it costed + ~10.25$ + 2,5$ to install battery. Then I've bought new touchscreen for it for ~22,5$, plus payed ~6,25$ to install it. Then around 7,5$ to restore battery connectors (on device and accumulator). So finally it worked, and wanted to see how to install Windows on Zenfone. Sure, if I had possibility to buy anywhere Zenfone better, new, not used, - I'ld do it, but it is not that easily available, just like any other Intel smartphone.
So, I started reading - how to make my device rooted. I don't understand how to get root. I found on wikipedia, that rooting is different from unlocking bootloader, and realized - yes. I need to unlock bootloader, and to boot from external flash-disk and install windows, or at least - new kernel with KVM support. I used pn my Android (non intel) Limbo x86 emulator, it can run some old windows 98 etc, maybe even xp, never win 2000, and if it runs win-7 or win-8 - it is so terribly slow. So I decided to buy Asus Zenfone. As in KVM mode I can send commands to CPU directly, and hope this Windows works much faster than in emulator. I hope just at least to run Windows XP on it, I need to code some C# code, so that Andorid phone is not only for mp3-playing, internet on the go and make calls, but to learn, study and to work. I don't know why Microsot, Intel and other companies don't like Intel CPUs in mobiles. They could do it if they wanted. I like WIndows because most programs are for Windows. And I want desktop x86 windows also on every mobile, intead of all Androids.
Anyway, What I tried to with my Zenfone. I found one amazing experience - that our hero and inspirer (ley God blesses him, maybe he will work in Intel/AMD/Asus/Microsoft etc to make more newer KVM kernels for future x86 phones with windows) - so Ycavan made KVM for Asus Zenfone 2. Great, I've read his thread - https://forum.xda-developers.com/t/...0-with-kvm-bridge-compiled-need-help.3145055/ - completely, with pen and paper writing down important information, downloaded all the files, and decided to start flashing.
I copied them to root of my Zenfone, unpacked tars and converted them into ZIPs. I also unpacked .img files to root of phone (I mean its folder which is visible if I connect it thorught USB, I know it is not "/" root of file system of Andoird, but anyway it is visible even inside CWM... sorry, was visible)...
So, I made some mistakes. I downloaded the kernel, tried to flash it using commands like :
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150710.img
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150714.img
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150717.img
fastboot flash boot boot_fhd_2.20_kvm_bridge_20150820.img
fastboot flash boot boot_2.19_kvm_bridge.img
fastboot flash boot boot_fhd_2.20_kvm_bridge_20150820.img
but non of them produced bootable Zenfone. So I had to revert to previous bootloader using the CWM tool.
In fact I liked this CWM most. I found this thread - https://forum.xda-developers.com/t/...root-ze500-ze550-ze551-temporary-cwm.3114063/
or similar here on forum, and it worked amazingly. I attached Zen-phone to USB, turned it off, then on while pressing, keeping pressed volume-up key, and after Asus logo appeared and some "zzz" vibration, again it blinked and I saw bootloader with Android robot, and possibility to scroll through menu using volume up-down, to choose normal boot, or reboot/power off, or to run restore etc.
For some reason, Restore there not worked. So anyway, I understood that I can use tool like ADB (Android debug bridge) and fastboot to copy new firmwares/kernels/bootloaders etc to it, so I guessed I can do it myself, and was ready for risks... And this what bad can happen - it happened.
So, I runned in CWM - file cai_dat_CWM.bat - which asked to type ACCEPT and then T4, and phone started to go into amazing mode, some "clouds" started appearing on phone, and it loaded into special secret menu, from which I could select what to do next. To me it looked like default boot manager which I wanted to see like in Dos/Windows machines - so I can choose to run into safe mode windows, or set some settings before booting, or even use "reanimator dvd" etc to load Windows and other tools to do partitioning, passwrods recovery etc. So it looked like on desktops, and very nice. I went inside the menu, and found good option to make backup. I did it all. Then in same CWM tool (I think it is called SuperSU for Android), I finally choose to restore bootloader/kernel/boot (custom recovery), and this saved my from bricking the first time after I followed the manual from Ycavan. Well, I know I can read a lot more threads how to do this and that, but there is always risk that something wrong can happen. So I tried to read as much as I could, and follow manuals as precisely as I could understand. But my phone is kind of "bricked".
Now it shows some scfreen like TV which can't catch any tv program. So it is some random colors - see attached picture. It is good that it shows at least this. But in worse situation - it doesn't show anything. So let me tell how I achieved this, and if you can tell me how to avoid this mistake and to recover it. I hope to get help from anyone here who installed KVM kernel(s) and acheieved running Windows on their zenfone 2 (or maybe anyone who has XPerience with other x86 phones may help, or if it is general issue how to unbrick - then also non x86 users please help).
So, CWM made backup, I became more non-scared to make more experiments with firmware. But main problem is that I don't know which firmware to use. I ideally suggested that when I change kernel to KVM-supported from Ycavan - that it will work with my Andorid 5.0 (it was installed when I bought it). So, but unfortunately, after installing any of KVM kernels of Ycavan - I was unable to understand which OS to install, which version. So even I tried to try to flash whole 1GB+ image (I have downloaded UL-Z00A-WW-2.20.40.59-user.zip from official asus.com - https://www.asus.com/ua-ua/supportonly/asus zenfone 2 (ze551ml)/helpdesk_bios/ - but. I was unable to upload it to zenfone (flash it), as it said it is older than installed version.
Anyway, now it doesn't matter as I cannot run into ANdroid at all. Worse - I cannot even get Bootloader working in Android, as I see after turning phone on - only "white screen" with non-working TV-like image (see attached picture of my Zenfone 2).
So, to make this happen, I did this: I found some information about TWRP. I tried to install as recovery tool. Even though it was flashed into mobile, and I installed it from apk from Google-Play, still, I was unable to run it... So then I found even cooler tool - which was too risky to install. I was good, but Andorid stopped running at all.
This tool is called - preroot601. I runned in it preroot.bat, and then it did something similar to CWM, but several times it restartd the phone _ i have added screenshots of how it looked like on PC / Windows. So after several restarts, it did a lot of changes - Android didn't start after it. Phone always was able to start into recovery mode - into TWRP (I downloaded its .img and flased it as recovery for phone). But in TWRP I think I did something wrong. I made backup of all files (syste,, bootloader, everything). I saw it is cool - to see there terminal, ability so set attributes for files, mount partitions ... even USB -hey, can I run from flash-disk? or from external DVD/Bluray which I have in this mode? I have USB-hub, and can connect to it keyboard, mouse, flash-usb, ssd/hdd - all through Microusb-usb adapter and to usb-hub. So what I wanted to do is to try to see flash-disk, mount it on my android zenfone. And then after restart - I had black screen or this 'non-working analog-TV screen when no program/channel/wave is caught for signal"...
So, I don't even understand what I did, and why this all happened, and why I have to do to restore bootloader at least.
My aim is to have KVM enabled in the kernel. I don't mind if it is old Windows like XP working on this Zenfone, but I like windows to be my main OS on every phone which I may use in future (and hope they all be x86-64 and not ARM). So as I don't have Steamdect now (it has also AMD x86 CPU, like Zenfone), I want to do this, achieve it - having Windows on mobile - Zenfone.
I can carry it in pocket everywhere, so why not people like having desktop Windows x86-64 in each and every mobile? Even Lenovo are collaborating with IBM - then why not make also IBM-Mobile / IBM-smartphone, which will also be as good as PC - to unassemble it, change any part like on desktop, why not do it? I think everyone will enjoy it, and it will boost everything to better hights, levels.
So, please. If anyone here has similar experience of going to same screen like I have (see screenshot), or like that - black screen - indeed my device also may not even show any thing - even no ASUS logo, no bootloader (even if I press Volume-UP after powering and after flash it usually showed bootloader with robot - no... not now)...
So I don't see anything on screen of Android Zenfone now. no text, no bootloader, no recovery even - no TWRP menu. I think I am ready to format whole zenfone, and install there maybe some partition manager (like you know there is Partition magic on PCs, when I can split HDD/SSD nto two parts, one for Windows, and say other for Unix - Ubuntu or Android x 86 - all on same physical drive)... So I want some re-partitioning for intern SD memory, and be able to install there some ISOs, say with DOS, Win3.11, win 95, 98, 2000, xp, 7, 8,1 and maybe even 10. But guess last will be slow. I think Windows XP would be ideal OS for my Zenfone, if it can run fast. Win 7/8 maybe will be slow. But for some sceintific aims - like I just write some algorythm in Visual studio, and can do it even in WinXP, so why don't do it on my Zenfone? I don't like many Andorids, as they are not for work much - they are used by many people to play games, watch videos on phones, surf social networks, but not for real work. Real work is usually on WIndows, and no laptop can replace "Windows x86 in pocket" (on mobile). And I wonder why Microsoft develops "Windows for ARM" instead of investing millions into efforts like which Ycavan did - to make Windows run in KVM mode fast on x86 smartphones.
Ok, So, any ideas? What should I do now? I need some special tool to fix my phone first. Fix its loader. I think I need to bypass fastboot.exe restriction, which shows "waiting for device". Command in cmd like this: ADB.exe devices -L --- shows device from time to time - it shows:
c:\adb>adb devices -l
List of devices attached
0123456789ABCDEF device
c:\adb>fastboot flash boot boot_2.19_kvm_bridge.img
< waiting for device >
So, I cannot even flash some recovery device in this way. In devices manager I see "ADB interface" in "USB devices" category in devices treeview. And sometimes Moorefield appears, but with exclaimation mark - I have no idea how to make it disappear. I found here some info that I can install tool - xFSTK_Downloader_v1.7.0.zip - I downloaded it, installe,d but it doesn't run (I have win10 x64bit). hm... And driver required - iSOC_USB_Driver_Setup_v1.2.0.zip - I installed - but nothing.
So, what to do? How to make bootloader appear again? And how to write there prob=per bootloader with KVM kernel, and which firmware to flash so I can use KVM fast there with fast Windows...? Is it possible at all to make it run WIndows natively on Zenfone? or it will always be only in virtual machine inside some ArchLinux or in Limbo x86 on Android?
I read that Ycavan used this ArchLinux, but I don't understand why. Is he installing it over Android? Then also which version he uses? I need to know each and every version whcih he uses to make everything works. I 'ld require all the firmwares which he uses to make it work also - to make some Windows iso run on my Zenfone 2.
Did anyone achieved this successfully, except for Ycavan - to run Windows on Zenfone? Or except for him noone was able to install KVM kernel, and it was similar to mine situation? And maybe this is the reason why manufacturers of phons don't like x86 phones? I don't know. Any ideas?
See screenshots. What to do in this state?
IF anyone can please upload to somewhere whole pack of files ("WIndows on Zenfone starter kit") to make anyone able to just follow instaructions which will work in all cases to install WIndows there like Ycavan has - it would be great. There is lack of more detailed information - which .img files, .zips, firmwares etc, which OSes are supported by Ycavan's KVM kernels?
I have no idea. if anyone passed this path, and achieved Windows on Zenfone, please share your experiences, Ireally need it. Here in Ukraine when electricity disappears almost daily, we need devices like x86 phones almost for everyone. And mo matter if Windows is a bit old. KVM mode I guess must be much faster, almost native speed, so (like on tablet PCs), so please help...
Thank you all in advance, whoever will answer me.
indubhushan said:
c:\adb>adb devices -l
List of devices attached
0123456789ABCDEF device
c:\adb>fastboot flash boot boot_2.19_kvm_bridge.img
< waiting for device >
Click to expand...
Click to collapse
wrong mode. adb is only working in
- normal/boot mode
- recovery mode
fastboot is only working in
- bootloader mode
- fastboot mode
You can see 0123456789ABCDEF device in adb devices, therefore you are either in TWRP or in Android (Win?)
type adb shell and check the prompt is either $ (shell) or # (root shell)
in root shell you can flash partitions from cmd line. you can also reboot into bootloader/fastboot mode from cmd line.
Code:
adb reboot bootloader
I had success in restoring my bootloader (logo with android robot) - I intalled xFSTK, so somehow I had success to make it run, and I added threee files (1, 2, and 4th) and tried to flash it. Phone was visible as Moorefield. Then I tried to use Asus flash tool to flash big RAW image, but for some reason I don't know why - I had even whole day left it to flash, it didn't do the task - Android stopped booting - no logo showing at all - have to use xFSTK to recover. Maybe I use wrong RAW image (from official site it is .zip, so have no idea where to get those raw files).
When try to flash using flashboot - I get error: - flash cmd error.
As for devices list. My device rarely appear there. It may appear for some seconds, and then xfstk can have success to flash it, and maybe even make it runnable into Android robot scren (bootloader).
I am thinking that I need to install maybe ArchLinux, which Ycavan is using, but have no idea where to get RAW file for it, and how to flash it. Maybe some problem with my USB port on old laptop, or maybe even with USB cable (though have few good almost new cables, even new 4Amperes one). So maybe even problem in port of Zenfone itself (to change it). No idea. Because even when I tried to flash it (that huge 1GB file), phone disconnected, or showed "ready for commands", instead of showing process of ownloading RAW image/Android into phone's memory.
Flashboot/adb almost unusable. Well, I'll try, maybe it'll work.
My hope is try to go into CWM, run from it into "secret menu" on phone, and from it - to access internal memory of phone, and restore phone from backup. But when I tried to load into it once - it hanged on "clouds". I don't know...
And I don't think I'm ready now to format internal memory of phone or to repartition. At least I don't have backup on some external card (sd-card) etc.
as for adb. maybe it can't see my device, even if it is "recovery mode" (when see in devices manager in Windows - Moorefield). Now I'm stuck on xFSTK and can't go anywhere further like adding TWRP into phone, or foing into backup/restore menu on phone, and of course there is no Android. Even when I see Android robot (boot menu) - I feel happy, that at least phone shows anything, so at least bootloader workds. Maybe difference is in drivers - when I have Moorefield driver, then maybe it contradicts with Zenfone driver, and I have to reinstall them? Or use other OS? I have dual-boot (two Windowses on my laptop), so maybe I need to use one Windows - to work with Moorefield (xfstk) - when phone is in "worst" situation when no logo shows / no bootloader. And the other Windows I have to run on laptop - with Zenfone driver installed (I think it shows something like Asus device in device manager). But they seem to use contradicting drivers, I am not sure. And maybe it's some problem with my usb ports, but hope no. They seem to be ok... Maybe I'll have to go some day to give phone for diagnostics to repairing center again ;-(