Related
Only fresh flashed bootloader locked XT1058 AT&T - ROM LPAS23.12-21.7-1, and XT1060 VZW - ROM LPAS23.12-39.7-1 are supported!
See archive content for instructions. Time to install ~20 min. If you experience problems after Android boot, like not working buttons or quick settings, wipe cache + data partitions. Don't update SuperSU (disable auto updates), it won't work. Later I'll post complete debloated ROMs with fresh SuperSU version, and simplify instructions. Be informed also, that this method doesn't give you read-write rights like unlocked bootloader. You may read and write having root-rights, but only till a restart or shutdown occurs, and every change will be undo by the Qualcomm protection (like HTC' s=on).
At the moment patch includes:
SuperSU 2.65 Free
Xposed Framework v86 (installer, modules)
Busybox 1.25.0.YDS, path /system/xbin/busybox
Download
P.S. Install only on indicated above ROM versions, and it's obvious that you must have enough theory knowledge and practical experience to make use of 9008 patch, so I'm not responsible for any consequences, etc. Greets go to: CrashXXL (method inventor), Sabissimo (our former OP), and serg_gangubas (ROM guru).
==============================================================================================
31.07.2017 - Full ROM Patch for Bootloader Locked Moto X ATT/VZW/etc
Based on the same principle, and not depend on system partition content, so it suits any bootloader locked Moto X Gen1 ATT/VZW (possibly any model, besides 1049 RepW / 1055 US Cell), but takes about 4 hours to be done - prepare for that, 100% battery level only!
This full ROM patch includes:
SuperSU 2.82 Free
Xposed Framework v87 (installer, modules)
Busybox 1.26.2, path /system/xbin/busybox
ViperFX 2.5.0.5 - sorry needs polishing, removed now (
Gallery and Camera not depend on Moto services
Gboard instead AOSP Keyboard. If it eats too much RAM, see Simple Keyboard
GAPPSes updated. Use command like adb shell pm uninstall --user 0 com.blahblah.blah to block any unwanted app or service
ES File Explorer Free Edition (a clone, you can disable and install yours )
"Jedy" gesture
AdBlock support (effect lasts till the 1st reboot yet, I'll think about make it constant). Please, choose /data/hosts instead of /system/etc/hosts
ROM debloated, but not deodexed.
Download
Instruction
Be careful, phone will be WIPED then flashed in 9008 "brick" mode (CrashXXL idea). Before you start install Moto drivers, latest RSD Lite, and fully charge the battery.
1) Download and unpack zip on С: (or any), open Python27, launch RUN_path.bat (needs to be launched only single time), install driver QHSUSB_driver.exe, and launch file _Moto.X.BootLocked.*.exe (where * - is desired ROM).
2) Go into fastboot mode, execute RUN_blbroke.bat. Screen gets black, Device Manager in Windows finds "QHSUSB_DLOAD", and installs it as "Qualcomm HS-USB QDLoader 9008 (COM*)". If it doesn't install, google for Windows driver digital signature disable.
3) Now launch RUN_root.bat, and see that patching process took start.
4) A small patch *SPEAKERS.BOOST.exe (if exists) boosts both speakers' volume.
P.S. Please, don't flash anything extra into the phone. In case of trouble, all you need is inside this folder. Just make it work.
To make "Battery OK" in fastboot use fastboot_cyclecharge.bat
Completely drained out battery causing "USB input device" needs disassembly of the phone to charge externally.
In case Titanium Backup shows error "Batch backup interrupted: insufficient free storage space", delete default backup folder, and make a new:
Titanium Backup > Menu > Preferences > Backup folder location > Storage Provider > DocumentProvider storage > Show Internal Storage > Internal Storage > Select Internal Storage > Create the folder > Use the current folder. Done!
Notes for myself: Viper, force wipe, readme.txt, volume patch, Adblock, advanced debloat
Debloated, rooted, lightweight ROM - soon! )
PUBLISHED. Sorry, took long time.
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
DownTheCross said:
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
Click to expand...
Click to collapse
This method is working on locked BL.
DownTheCross said:
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
Click to expand...
Click to collapse
Wait wait... If you can have now possibility to unlock bootloader - go for it immediately! You will have normal FULL root-rights (SuperSU 2.49). Don't install 5.1, if you plan to unlock, because Sunshine app (25$) works only on 4.4.2 Android.
This topic is to help those AT&T users that are boot locked forever (who missed out possibility to unlock on 4.4.2 by proceed to 5.1) to give them READ-ONLY root. Yes, it's limited, but anything at least.
s5610 said:
If you can have now possibility to unlock bootloader...
Click to expand...
Click to collapse
I guess anyone on 4.4.4 today. There is no possibility to use Sunshine anymore.
Anyway spasibo za method
Ahh, if I don't have to be BL unlocked that's great lol.
I haven't read too much into the 5.1 updates or sunshine for that matter.
I've been on krypton 1.4.1 since it was released, and I haven't been able to successfully upgrade to any 5.1 roms yet.
Works great!
Works great for me on Windows 10 RTM 64-bit! Thanks a ton, I was waiting for a post like this.
I only had 3 minor hiccups:
1. RSD Lite gave me an error about "getvar", so I had to go into flashfile.xml in the ROM zip and remove the line that said getvar
2. I had to reboot to disable driver signature enforcement twice for some reason because Windows Update
3. The run-root.bat got stuck on "Executing..." because I installed the wrong driver (the correct file is qcusb.inf when installed from device manager -> browse my computer for driver software -> let me pick from a list -> all devices -> have disk)
Otherwise, everything runs just as well as KitKat, including Xposed.
Hehe got to love step 9
System Write
How can we help in getting the system write to zero using the same method,because I have xt1058 model bootloader unlocked and I provide any file needed to disable the pesky system write...
How can we help in getting the system write to zero using the same method,because I have xt1058 model bootloader unlocked and I provide any file needed to disable the pesky system write...
Click to expand...
Click to collapse
First, never quote op. It takes way to much space and is redundant.
Second, to get write off we would need to some how either start a custom kernel some magical way or disable it via a kernel mod like htc guys did. Another way, which was done before was to burn the efuse but kernel has been patched since then.
Need some help, I did all steps until step 9. I installed the QHSUSB_DLOAD driver manually, and I can see 'Qualcomm HS-USB QDLoader 9008 (COM4)' showed in my Device Manager, but when I run 'RUN_Root.bat', I got this
c:\Python27>python qdloadRoot.py MPRG8960.bin -ptf root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com4
Sending MAGIC ...
QCOM fast download protocol targ:
Version: 7
Compatible version 2
Maximum block size 1024 (0x00000400)
Base address of Flash 0x00000000
Flash: eMMC
Window size: 30
Number of sectors: 128
First sector size: 2097152 (0x00200000)
Feature bits: 09
Sending SBL Reset...
Done
c:\Python27>pause
Press any key to continue . . .
Then I tried to run 'RUN_Root.bat' again, then I got
c:\Python27>python qdloadRoot.py MPRG8960.bin -ptf root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com4
Requesting Params...
Params:
Version: 8
Min version: 1
Max write size: 1536 (0x00000600)
Model: 144
Device size: Invalid or unrecognized Flash device, or Flash device progr
amming not supported by this implementation
Device type: Intel 28F400BX-TL or Intel 28F400BV-TL
Requesting SoftwareVersion...
Version: PBL_DloadVER2.0
Requesting SerialNumber...
Serial number: 00,00,48,03
Requesting HW Id...
HW Id: 00,00,48,03,e1,10,7e,00
Requesting PublicKey...
PublicKey: 39,c4,ee,3e,b5,be,eb,87,8e,2f,e3,b8,53,4d,14,6f,91,ca,fd,bb,94,2a,0d
,aa,d0,1e,b0,87,62,d4,b9,b8
Uploading file 'MPRG8960.bin' to addr 0x2a000000...
Executing...
Could not find Qualcomm device in Emergency download mode
Done, with errors!!!
c:\Python27>pause
Press any key to continue . . .
any suggestions? Thanks
jahrule said:
First, never quote op. It takes way to much space and is redundant.
Second, to get write off we would need to some how either start a custom kernel some magical way or disable it via a kernel mod like htc guys did. Another way, which was done before was to burn the efuse but kernel has been patched since then.
Click to expand...
Click to collapse
Ill put the files here
Fantastic!!! I was looking this. All the last week I was sleeping about 3 hours per day trying to root my phone.
----
I scream "Victory" before the process finish.
Damn! My phone reboot and stay in the android doll fallen screen.
DejanPet said:
Ill put the files here
Click to expand...
Click to collapse
What to do with these files?
Those files are needed by Jahrule
Sabissimo
Hello.
I did everything as instructed, but eventually got the screen "no command".
The only thing I did not flash rom - a month ago updated by an OTA to 5.1, thought it was not necessary.
Factory reset does not help.
Advise something.
In the end, everything worked, thank you))
It works
It works great! Thank you very much! ATT xt1058.
eze_cba17 said:
Damn! My phone reboot and stay in the android doll fallen screen.
Click to expand...
Click to collapse
Follow the OP instruction EXACTLY, no exceptions!
If you got your current 5.1 through AT&T OTA, it's not enough for root patching procedure. A full RSD 5.1 official SBF flash over is required.
Could someone please do a video on this. I'm having a little trouble.
ONEPLUS 3 - SUPPORTS ALL VERSIONS UP TO THE LATEST OXYGEN OS BUILD.
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
The Unified Android Toolkit brings together all the Google, Nexus, OnePlus and Samsung Toolkits and supports many devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT
* Install correct adb/fastboot drivers automatically
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your /data/media (virtual SD Card) to your PC for a Full Safe backup of data
* Root any public build automatically
* SkipRoot boot image to AutoRoot (selected builds)
* Sideload root/unroot files via Custom Recovery
* ALLINONE to Unlock, Flash Recovery, Root, Rename the restore file + install Busybox (G,N,O)
* ALLINONE to Flash Recovery, Root, Rename the recovery restore files + install Busybox (Samsung)
* Unlock/Re-Lock your Bootloader (G,N,O)
* Download Google Stock Image files directly to the ToolKit (G,N,O)
* Check md5 of google stock image before flashing
* Flash Google Stock Image (G,N,O)
* Flash any part of a stock firmware image to device [boot, system, recovery, etc.] (G,N,O)
* Download/sideload stock OTA image (G,N,O)
* Install BusyBox binarys on device
* Rename the Recovery Restore File present on Stock Roms (if stock recovery is being restored after flashing custom recovery image)
* Flash Stock Recovery, CWM touch, Philz_touch or TWRP Touch Recovery
* Pull /data and /system folders, compress to a .tar file and save to your PC
* Auto Update Toolkit at startup (PRO ONLY)
* Auto Update superuser file and custom recovery images to latest versions (PRO ONLY)
* Disable forced encryption on Nexus5X,6,6P and 9
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps
* Install EFS/Partition Backup/Restore app by Wanam
* Create tar with 1-Click for flashing via Odin
* Fix extSdCard write permissions in Android 4.4+
* Perform a FULL NANDROID Backup of your system via adb and save in Custom Recovery format on your PC (selected builds)
* Useful Mods, Fixes and Tools Section
* Extras, Tips and Tricks section (includes guides)
* Backup/Restore your /efs partition (gsm only)
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC ( on builds with insecure image available)
* Mods section to automatically perform certain tasks on your device
* Boot to any recovery without Flashing it (G,N,O)
* Boot or Flash .img Files directly from your PC
* Quick Picks Professional Feature (10 slots)
* Install a single apk or multiple apk's to your device
* Push Files from your PC to your phone
* Pull Files from your phone to your PC
* Set Files Permissions on your device
* Pull and Trim your Radio Image (gsm models only) to your PC
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Rip cache.img to zip file in CWM format
* Reboot device to Fastboot Mode or Android in fastboot mode (G,N,O)
* Reboot device to Fastboot Mode, Recovery, Android or Download Mode in adb mode
* Turn Initial Start Screen On/Off for next use
* Sideload any zip file via Custom Recovery
* Basic Toolkit for use with ANY Android device
Key: G-Google N-Nexus O-OnePlus S-Samsung
--------------------------------------------------------------
{
"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"
}
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: Grarak or TWRP custom recovery on OnePlus 3, ChainsDD for Superuser, Chainfire for SuperSU and kernel patches, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to get into your FastBoot Mode
1. Turn your phone off
2. Unplug your usb cable if you have one plugged in
3. Keep holding the 'Volume Up' and 'Power' buttons to boot the phone into FastBoot Mode
How to get into Recovery
1. First boot into FastBoot Mode as described above
2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by using the Unified Android Toolkit. No warranties of any kind are given.
**FAQ**
**VIDEOS**
I have finished all the work on the OnePlus modules for the 1, 2 and 3 devices and it is ready for testing.
You can download and test the Toolkit from the link in post#1. Please remember that this IS a test version at the moment as I do not own any OnePlus devices but I have checked all the code thoroughly and don't see any problems. I am especially pleased with the unlock/lock routines and will probably implement the code for the Nexus modules if it works well.
Everything can be checked (and please do) except downloading a stock build directly from the Toolkit as I am waiting to hear back from AndroidFileHost to see if I can get direct links to use in the Toolkit. The fastboot flash routines are working though and the Toolkit will detect the storage of the device (16GB or 64GB) and flash the relevant userdata image so you do not have to do that manually anymore.
I have used the Universal USB driver pack from CWM so if anyone has not installed OnePlus drivers yet PLEASE test if this works. I did originally include the official drivers from OnePlus but they close the Toolkit when the drivers installation starts and thats not great.
The ALLINONE routine should work fine and I have sent out some pro codes to testers to check it all works.
All builds are covered and the correct version of TWRP will be downloaded depending on the build selected. Please check everything and let me know of any bugs or textual errors (as I used a lot of the Nexus code) so I can release it publicly as soon as possible.
Thanks, Mark.
Great job, thanks a lot!!!
Dude, did a scan of your file and found this: Result: Detected: Trojan-Ransom.Win32.Cryrar.gib care to explain?
Trojan?
I hope not - seems legit.
I have 2 problems:
1)
It never asks me to authenticate the PC on the phone after installing drivers - tried both driver versions.
But the Phone serial shows up in the menu, the driver test is fine and I can backup .apks.
2)
I can not flash the OTA
Is it because it is a full stock image instead of an OTA?
gruntyoldbag said:
Trojan?
I hope not - seems legit.
I have 2 problems:
1)
It never asks me to authenticate the PC on the phone after installing drivers - tried both driver versions.
But the Phone serial shows up in the menu, the driver test is fine and I can backup .apks.
2)
I can not flash the OTA
Is it because it is a full stock image instead of an OTA?
Click to expand...
Click to collapse
Just saying, got that hit when I scanned the installer file. Might be wrong but I will not run it until dev explain why
TheErk said:
Dude, did a scan of your file and found this: Result: Detected: Trojan-Ransom.Win32.Cryrar.gib care to explain?
Click to expand...
Click to collapse
Did you read the first post of the thread?
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Click to expand...
Click to collapse
The Toolkit has been running over 4 years and there have never been any viruses in it.
Mark.
I ran this on my Nexus days, the guy is well known around, you can go with this.
Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
gruntyoldbag said:
Trojan?
I hope not - seems legit.
I have 2 problems:
1)
It never asks me to authenticate the PC on the phone after installing drivers - tried both driver versions.
But the Phone serial shows up in the menu, the driver test is fine and I can backup .apks.
2)
I can not flash the OTA
Is it because it is a full stock image instead of an OTA?
Click to expand...
Click to collapse
I found the problem right away, just deleted 1 word by accident when I was renaming things.
I have made new device modules and uploaded them. Delete the ConfigOnePlus3.exe file from the Tools folder (or run ToolkitClean and select the OnePlusThree), then rerun the Toolkit and select your device to download new modules. Should work then.
Mark.
mskip said:
Did you read the first post of the thread?
The Toolkit has been running over 4 years and there have never been any viruses in it.
Mark.
Click to expand...
Click to collapse
Thought I did! Thanks for the fast reply!
---------- Post added at 11:23 AM ---------- Previous post was at 11:11 AM ----------
Impressive tool you got here! Thanks!
mskip said:
Delete the ConfigOnePlus3.exe file from the Tools folder (or run ToolkitClean and select the OnePlusThree), then rerun the Toolkit and select your device to download new modules. Should work then.
Click to expand...
Click to collapse
I cleaned the toolkit and
**************
Also I had to restart the toolkit (my own error - I didnt use the toolkit to restart, but restarted manually) and I got:
************
Tried again and Windows installed more device drivers when accepting sideload from ADB.
Didnt work the 2nd time either.
**********
BTW: drivers are installed correctly
******
Btw: I really love your tool - nice, clean, fast and a lot of HELP in the menus
gruntyoldbag said:
I cleaned the toolkit and
**************
Also I had to restart the toolkit (my own error - I didnt use the toolkit to restart, but restarted manually) and I got:
************
Tried again and Windows installed more device drivers when accepting sideload from ADB.
Didnt work the 2nd time either.
**********
BTW: drivers are installed correctly
******
Btw: I really love your tool - nice, clean, fast and a lot of HELP in the menus
Click to expand...
Click to collapse
Thanks and thank you for staying with me, I have had to change some of the procedures for the OnePlus.
Should be all fixed now. One of the procedures I had to skip set the filename for the OTA image. Have added it back in.
Clean the module files, download the new ones and retest. Hopefully it should go through.
Mark.
It is sideloading now
Reboot was successful - thx
Btw: If you want the help text to be 100% correct:
When you reboot you have to chose ENGLISH (or you can chose chinese or madarin?)
And it is called 'Install from ADB' not from USB.
Then click OK to 'Do you want to update' (not 100% sure about this text - can not remember now.
************
Just tried option 11 from the main menu:
****
Booting to stock recovery gives me the same error.
gruntyoldbag said:
It is sideloading now
Reboot was successful - thx
Btw: If you want the help text to be 100% correct:
When you reboot you have to chose ENGLISH (or chinese or whatever)
And it is called 'Install from ADB' not from USB.
Then click OK to 'Do you want to update' (not 100% sure about this text - can not remember now.
Click to expand...
Click to collapse
Thank you. I have uploaded the fixes to all the OnePlus device modules so that part at least should work for them all now.
Does the language selection come up as soon as the device boots to recovery?
I put Install from USB as thats what it said in the flashing tutorial on oneplus.net I will change it to Install from ADB/USB just to be safe for all devices.
Thanks again for the feedback. If you want to test any of the pro functions (ALLINONE) then let me know and I will send an activation code to your inbox.
Mark.
gruntyoldbag said:
It is sideloading now
Just tried option 11 from the main menu:
****
Booting to stock recovery gives me the same error.
Click to expand...
Click to collapse
Have you unlocked your bootloader? This is required before flashing/bootings images to your device.
I can capture the error when trying to boot/flash with a locked bootloader to provide more help for the user.
Mark.
The language selection come up as soon as the device boots to recovery - yes.
No I didn't unlock the bootloader - I didn't think it was necessary - help text said something about unlocking - but not that it was required.
I just wanted to backup the device - not flash anything.
Yes let me try (ALLINONE) - send me a PM thx.
gruntyoldbag said:
The language selection come up as soon as the device boots to recovery - yes.
No I didn't unlock the bootloader - I didn't think it was necessary - help text said something about unlocking - but not that it was required.
I just wanted to backup the device - not flash anything.
Yes let me try (ALLINONE) - send me a PM thx.
Click to expand...
Click to collapse
I have changed the text when booting to recovery and added extra error control when flashing or booting an image without the bootloader unlocked. New device modules uploaded.
Now sending a pm to you with a code.
Mark.
PM received - PM sent
New text and error control seems to work :good:
I spent weeks trying to find a way to install a Linux distribution alongside my Android devices, or replace Android with one entirely. While researching the possibility, I was really disappointed to learn installing a distribution alongside Android was already a 'fad' which had already come and pretty much gone. A lot of the methods that worked in 2012 and 2013, no longer work on current Android devices, or at least very few of them. However I don't go down without a fight. Please note, I did NOT create any of this software nor did I develop it. I just put it all back together, in a working order. Though it's pretty much impossible to brick your device using this guide, I still feel obligated to say: I am not responsible for any damage this guide may cause to your device, yourself, or the jealous friends you'll have after installation is completed xD
In order to install a Linux distribution, your Android device MUST be rooted. Unfortunately there is no way around that. After more than 2 weeks of research, reading and testing, I have managed to get three different distributions working across four devices, with plans to test it on at least one more device:
- Amazon Kindle HD 8.9 (Rooted with TWRP custom recovery and a custom CyanogenMod [CM] Marshmallow 6.0 ROM).
- Samsung Galaxy J1 (Rooted. Android Lollipop 5.1.1).
- Samsung Galaxy S3 (Rooted with TWRP custom recovery and a custom SlimRom Marshmallow 6.0 ROM).
- Samsung Galaxy S7 (Rooted, US Variant, Android Nougat 7.0).
- (Plan to test) Amazon Fire 7 (Rooted. Custom Lollipop 5.1.1 ROM).
The following guides will allow you to install any Linux distribution you desire (provided it's available). You can install the distributions as a .img on your internal storage/sdcard or partition part (or use all) of an removable sdcard (external storage). It is recommended you have at least 4GB of free storage space. If you want to try another distribution, it's just a case of deleting a few files or folders to uninstall them. Or you can partition another part of your sdcard (external storage). Please note you will not be able to repartition any internal storage.
These guides will be long. It will seem harder than it is. I really think this is one of the coolest things for Android I've stumbled upon. I haven't even begun to scrape the surface of what this allows you to do. Be patient and have fun
Part One: Installing a Linux distribution on internal storage
To get started, you need to do and have installed the following things:
- Make sure you have root.
- Make sure you have BusyBox installed and working.
- Terminal Emulator for Android, Termux and it's API or an SSH client.
- VNC Viewer for Android or your preferred VNC viewer.
- Linux Deploy
- AParted ( Sd card Partition )
1. Go to Sourceforge and download your preferred Linux .img. Those .img files are courtesy of a once awesome organization called 'LinuxOnAndroid'. Simply click on one of the nine distributions and download whichever one and size you prefer.
2. Extract the .zip in a folder on your PC. Name the folder the name of the distribution (i.e. Kali, Debian etc). **NOTE: You MUST download and extract all distributions on your desktop PC. These .zip files will not decompile and extract properly on your Android and the .img files will not boot.**
3. On your Android, using a root explorer, create a folder with the distribution's name in /sdcard or /storage/emulated/0. On your PC, in your extracted Linux distribution folder, copy and paste the .img file into the folder you created in one of those two storage directories.
4. If you haven't already, download and install Linux Deploy from Google Play.
5. It's now time to configure your distribution. Tap the three lines at the bottom right corner. You will then get a screen with a list of configurations. For the purpose of this guide, I have selected the Debian distribution. The first set of configurations should be as follows (See image below the list):
- Containerization method: chroot
- Distribution: Debian
- Architecture: armhf (This allows the Linux OS to be compatible with armv7)
- Source Path: (This will be an automatically selected URL and will vary from distribution to distribution. You should never have to change this configuration)
{
"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"
}
6. Now we configure the type of installation we will be doing. For this particular guide, we are installing the distribution on internal storage. Please configure your settings as listed (See image below the list):
- Installation Type: File
- Installation Path: /sdcard/Debian or /storage/emulated/0/Debian
- Image size: 6000 (The lowest recommended allocation is 4000MB [4GB])
- File System: ext4 (Not all devices support ext4. Some only support ext2 or ext3. If ext4 doesn't work, try one of the other two. You will also have to select the proper .img format from LinuxOnAndroid i.e. ext4, ext3, ext2).
- User Name: android (You can choose any name you like. This will be used to connect to the OS via a VNC viewer later on).
- User Password: ******* (Although the password is automatically generated, you can make this any password you want. This will be used to connect to the OS via a VNC viewer later on).
7. Set the configurations below See images below the lists):
- Privileged Users: root (This will be the name given to you when entering a root shell via the sudo command. You can change this to your liking)
- DNS: Automatic Detection
- Localization: en_US.UTF-8 (Language and region selection. If you're not sure of this setting, use Google to determine your local i.e. en = English, US = United States)
- INIT: Make sure box is checked to enable
- Init System: run-parts
- Mounts: Make sure box is checked to enable
- SSH: Make sure box is checked to enable (This allows you to set up an SSH client to connect to the Linux OS as opposed to using a VNC viewer)
- GUI: Make sure box is checked to enable (This tells the Linux OS to create a graphical interface so you're able to use a VNC viewer)
- Graphics Subsystem: VNC
8. Now you can configure GUI settings. This creates graphics of high or low quality. You are able to customize these settings to your liking and they will vary from device to device based on screen sizes and resolutions. In this case, I have the distribution loaded on my Galaxy J1 so these settings are set to my taste based on that device (See image below the list):
- Display: 0
- Depth (bits): 24 (The higher the number, the better the graphics)
- DPI: 100 (Dots per inch)
- Width: 800
- Height: 480
9. Tap the back button once. From the main screen swipe right or tap the three lines in the upper left corner and tap the settings option. Here you can configure the application settings for Linux Deploy. A lot of these options are already selected and some don't require any changes. Please set the settings according to the list below (See image below the list):
- Lock Screen: Make sure the box is checked
- Lock WiFi: Make sure box is checked (Some devices will turn off WiFi when you aren't using Android for a period of time. Some carriers and manufacturers do not give you the option to 'keep WiFi on' when the device is 'asleep.' Checking this box will allow the application to attempt to keep WiFi on)
- Wake Lock: Make sure box is checked. (This option can be set to your taste. However, to avoid problems with Linux Deploy and a VNC viewer in case you don't shut down your Linux environment or Linux Deploy, keep this box checked)
- Language: English (Obviously this option would change depending on your preferred language)
- Font Size: 10 = default (This changes the size of the text in Linux Deploy application only)
- Scroll Size: 100 (This tells Linux Deploy how many lines of text you're able to scroll back and look at in the application)
- Theme: Dark or Light (Take your pick)
- Timestamp: Shows the timestamp next to the lines of test in the application. Totally up to you)
- Show Icon: Make sure box is checked (Some devices will attempt to shut down Linux Deploy, even with root. Displaying the icon in the status bar allows a constant notification to be present, which generally stops the system from shutting down the app)
- Stealth Mode: Hides the application icon within your launcher
- Autostart: Check the box if you want Linux Deploy to open and start the Linux OS each time you reboot. This is not recommended especially for lower end/older devices
- Autostart Delay: Tells Linux Deploy how long after the system boots, to open and activate the container (Linux OS)
- Network Trigger: Check this box if you plan on leaving your distribution running while traveling with your device.
- Terminal Command: telnet 127.0.0.1 5023 (This allows you to open a terminal in your distribution that connects to the device. This is just a standard terminal so you don't have to open a terminal emulator in Android. In order to use this you'll need to install the telnet package once your distribution is operational)
- ENV Directory: Auto selected. No need to change (Not sure what exactly this does)
- Path Variable: Blank. (Also not sure of this setting so I didn't change it)
- Enable CLI: Make sure this box is checked (Allows the application to use a command line within, I believe, both the application and the distribution)
- Update ENV: Update the operating environment (This updates the operating environment setup of Linux Deploy. (Please see the next step on how this function works)
- Remove ENV: Removes/deletes the operating environment (This removes/deletes the operating environment. Anytime you change the settings in this settings menu, you MUST tap Remove ENV and tap yes. Then tap Update ENV and yes to update the settings you just changed. Only do these last two
steps when completely done changing settings)
- Telnet: Enable telnetd daemon (Make sure box is checked. You need this option if you choose to install and use the telnet application on your Linux distribution)
- Port: 5023 (Preconfigured. The port that telnet uses to connect to your device inside the Linux OS via terminal)
- Localhost: Make sure this box is checked. This is a security feature which allows only the localhost (that's you inside the Linux OS) to be allowed to connect to the distribution. Leaving the box blank can potentially set yourself up to be hacked, in a bad way. Leave it blank at your own risk and is you know what you're doing)
- Enable Httpd daemon: I am not sure what this does. The box is preconfigured as blank, so I left it as such
- Debug mode: Enable debugging information if you wish
- Trace mode: Enable if you wish.
- Logging: Enable if you wish. The setting below it tells Linux Deploy what type of file to save logs as
10. Now once all those settings are configured, scroll up and tap on Remove ENV and yes when it asks. Then tap on Update ENV and yes when it asks. You have not configured Linux Deploy. Tap the arrow (back) at the top left of the screen.
11. Tap the three dots at the top right of the screen. Tap 'Install'. If everything has been properly configured, and you placed your .img of your distribution in the correct place, Linux Deploy should begin to install your chosen distribution.
If installation doesn't work or fails to install for whatever reason, don't worry; it will NOT brick you're device. It is impossible. You CAN however, corrupt your sdcard, which usually just means you have to reformat it completely and repartition it (but that is a discussion for my next thread). The installation process requires a constant connection to WiFi until it completes. The time the installation takes depends on several variables i.e. your chosen img size and distribution, how good your WiFi connection is and so on. Based on my experience, installation took anywhere from 10 minutes to as long as 40 minutes. If for whatever reason it doesn't complete installation, it will list errors. Be sure to get a screen shot of those errors. I've never had Linux Deploy freeze during installation. You may see the same line of text for a few minutes, especially during the first few minutes of installation.
12. Installation will be complete when you see <<deploy appear as the last line of text. Tap stop at the bottom of the screen. When the process completes (usually a few seconds), tap the three dots at the top right again. Tap configure. This will assure your Distribution is configured to the proper settings that we set up earlier. It will also install any needed updates. This process could take anywhere from 30 seconds to a minute or two (usually). When completed tap stop.
13. You should be ready to launch the distribution. Tap start at the bottom of the screen. If absolutely no errors are given, this should boot up your distribution. If you see the word 'skip,' this is ok and is NOT an error.
14. Now here's the fun part. It's time to configure a VNC viewer. For the purpose of this guide, and one of two VNC viewers I use, we will be setting up VNC Viewer for Android. It will start in landscape mode, but you can rotate once the viewer connects to the distribution. Remember the settings you configured in Linux Deploy? Your distribution will be your chosen height and width once it loads.
15. You will need to set up VNC Viewer for Android as follows:
- Nickname: android (Or the name you chose in Linux Deploy as the 'username')
- Password: The password you set up in Linux Deploy
- Address: 127.0.0.1 (This should be universal for all devices and is what the Linux Deploy application uses to connect)
- Port: 5900 (Also preconfigured in Linux Deploy and it's the port it uses to connect)
- Username: You can leave this blank. I usually do
- Color Format: 24-bit color (4 bpp) (This allows for the best quality graphics possible. And honestly, the graphics are pretty great)
- Local Mouse Pointer: Check the box for a track-pad type mouse (I think? Should enable the mouse to act like a track pad on a laptop. Leave unchecked to use the mouse as pointer tapping?)
- Force Full Screen Bitmap: Make sure box is checked (Could be preference, but I've always had the box checked)
- Use Immersive mode (Devices running KitKat 4.4 and above ONLY)
- Use Wake Lock: Check the box if you desire
- Repeater: No repeater (Not a clue what this does)
That's it. You should be configured. Scroll to the top of the screen in the VNC viewer and make sure the box is checked where it says 'keep' to save the settings when you restart the application.
Now the moment of truth. Can I have a drum roll please? tap, tap, ap, tap, tap.....tap on connect.....iy might take a second or two for your distribution's wallpaper to appear. You may get an error box that pops up just before it fully boots. Just tap on ok or use the 'mouse pointer' to tap it. Sometimes the distribution boots a tad slower than the virtual connection through the viewer.
That's it! You have successfuly installed a Linux OS alongside your Android device. You can interact with your device in a terminal and view files and folders on your distribution, that exist on your device. Perhaps the coolest part of all, you now have access to hundreds, if not thousands of applets in the terminal. Tap on the far bottom left corner icon that will bring up your menu. Tap on system tools and tap on the terminal. Now you can use Linux terminal like it was a full, operating system...because it is You also get a root shell. In terminal type:
Code:
sudo -i
If you want to install an application, for example git (github for Linux. You have access to just about every repository on github now) you need to have a root shell first. Type in the terminal:
Code:
sudo -i
apt-get install git
Debian on my Samsung Galaxy J1, Lollipop 5.1.1
Type in the letter Y if propted. To get a list of all available applications you can install with that command (this is a very, very long list), type in the terminal:
Code:
apt list
To exit the VNC connection ONLY, simply tap your recent apps button and swipe it away. To stop the Linux distribution, in Linux deploy, tap the stop button at the bottom of the screen. Then tap the three bars at the top left and tap exit. This should be done EVERY time you want to end your session in Linux Deploy. Do NOT exit or stop Linux Deploy via the recent apps button.
Please stay tuned for the next post below this one titled: 'Part Two: Partitioning external storage (removable sdcard) and installing a Linux Distribution onto it'
I want to thank everyone who followed this guide. Please give me a thanks by tapping the thumb at the bottom of this post or consider a small donation I really think this is awesome and I haven't begun to scratch the surface. I've been too excited getting this to work on so many devices! Please post your results and problems. I very much look forward to your replies!
Reserved for part two guide
Reserved for part three guide
Reserved for my comment
Awesome guide though, will follow when I can download everything
The repeater in above mentioned is for setting up remote access and viewing. And httpd.conf:
---------- Post added at 09:21 AM ---------- Previous post was at 09:18 AM ----------
jeremyandroid said:
The repeater in above mentioned is for setting up remote access and viewing. And httpd.conf: is historically named after httpd daemon for Apache2 set up
Click to expand...
Click to collapse
jeremyandroid said:
The repeater in above mentioned is for setting up remote access and viewing. And httpd.conf:
---------- Post added at 09:21 AM ---------- Previous post was at 09:18 AM ----------
jeremyandroid said:
The repeater in above mentioned is for setting up remote access and viewing. And httpd.conf: is historically named after httpd daemon for Apache2 set up
Click to expand...
Click to collapse
Like your avatar. Speaking of Kali, I installed that one first. Love it. But I get a 404 when trying to upgrade most of the add on 'security' tools. Is there any way I can get those to work or an I out of luck?
Click to expand...
Click to collapse
DragonFire1024 said:
jeremyandroid said:
The repeater in above mentioned is for setting up remote access and viewing. And httpd.conf:
---------- Post added at 09:21 AM ---------- Previous post was at 09:18 AM ----------
Like your avatar. Speaking of Kali, I installed that one first. Love it. But I get a 404 when trying to upgrade most of the add on 'security' tools. Is there any way I can get those to work or an I out of luck?
Click to expand...
Click to collapse
404 error is .sources list problem usually providing you allocated enough space for Kali. May have to either use original ones or replace with rolling ones.
Click to expand...
Click to collapse
jeremyandroid said:
DragonFire1024 said:
404 error is .sources list problem usually providing you allocated enough space for Kali. May have to either use original ones or replace with rolling ones.
Click to expand...
Click to collapse
10000 should be enough? I will have to try it again and see what happens.
Click to expand...
Click to collapse
DragonFire1024 said:
jeremyandroid said:
10000 should be enough? I will have to try it again and see what happens.
Click to expand...
Click to collapse
Yes should be plenty Kali comes with like several hundred tools so I'm pretty sure it's over 4gig so that will be fine
---------- Post added at 10:02 PM ---------- Previous post was at 09:47 PM ----------
Also not trying to sound like I know everything because I don't! I just love to learn and love Linux and Android. Im just now back on here I authored roms for the Note 2 years ago so it's been a long time lol. However I have used Linux for years and made custom distributions and kernels. Android has changed so much I'm catching up lol
Click to expand...
Click to collapse
So I had 3/4 of the second Guide written when the house lost heat. It got so cold my fans on my PC were starting to run too slowly, so it shut down as a precaution. I lost the work I had done on the second guide. So until I get heat back at home, I can't write the second guide. Apologies for the delay.
Latest Ubuntu running like a champ Thanks man!
Though any idea on how to make the screen bigger (without zooming in)?
Craz Basics said:
Latest Ubuntu running like a champ Thanks man!
Though any idea on how to make the screen bigger (without zooming in)?
Click to expand...
Click to collapse
You have to mess around with the VNC settings in Linux Deploy. Might take a few times to tweak to your liking.
DragonFire1024 said:
I spent weeks trying to find a way to install a Linux distribution alongside my Android devices, or replace Android with one entirely. While researching the possibility, I was really disappointed to learn installing a distribution alongside Android was already a 'fad' which had already come and pretty much gone. A lot of the methods that worked in 2012 and 2013, no longer work on current Android devices, or at least very few of them. However I don't go down without a fight. Please note, I did NOT create any of this software nor did I develop it. I just put it all back together, in a working order. Though it's pretty much impossible to brick your device using this guide, I still feel obligated to say: I am not responsible for any damage this guide may cause to your device, yourself, or the jealous friends you'll have after installation is completed xD!
Click to expand...
Click to collapse
Quick question for anyone who might know...
I'm running Debian on my Xperia Xc, and I'm interested in copying files back and forth from Linux to Android. I was able to figure out how to mount the loop device, and get access to it in terminal, but files don't show up in file manager, even though I go to the same directory I can see them in terminal.
How can I get the device to show up in the file manager?
Thanks
Edit - I was able to get it working in reverse, (show my Android file system on Linux), by using custom mount point option in LD, so I guess that works... Would still be interested to know if there's a way to do it the other way...
Question, Does installing a Linux Distro in this fashion allow one to pair and access simple B/T serial devices other than a B/T mouse our keyboard? I installed GNU Root Debian Jessie and got is working with LXDE but
none of my tracking apps that have to use a USB or B/T connection to an outboard receiver are accessible. Don't have access to /dev so I could change permissions on the ports the GNU Root Debian. Wireless or USB peripherals
are useless. I want to specifically run Xastir with outboard datastreams. Piece 'o cake with a laptop but no dice with GRB. Kurt KC9LDH
Any idea how to get it to work with magisk? I think it's due to busybox not working but when set to chroot, nothing happens when trying to start or install.
Humpie said:
Any idea how to get it to work with magisk? I think it's due to busybox not working but when set to chroot, nothing happens when trying to start or install.
Click to expand...
Click to collapse
I have no idea actually. I only have two devices with unlocked bootloaders and niether of them have magisk. Sorry I'm not more familiar with it.
DragonFire1024 said:
I have no idea actually. I only have two devices with unlocked bootloaders and niether of them have magisk. Sorry I'm not more familiar with it.
Click to expand...
Click to collapse
Ahhw that's a shame. It really is the cleanest way to root since apps like Netflix will still be available in the play store and Google pay etc will still work.
But I have a module which should have put busybox in /system/xbin (and it works in termux, I can type "chroot")
Edit: I'm a bit further, I set PATH to /system/bin/sh and chroot now at least runs, but it won't mount the img, let's download that again..
Edit2: mounting container gives me a fail... Any idea?
Okay I've got debian working by installing it into a folder instead of an IMG file. For some reason the img didn't work (might be android 8.1 or magisk related). I also didn't have to download an img from sourceforge as the app can download the files itself.
Humpie said:
Okay I've got debian working by installing it into a folder instead of an IMG file. For some reason the img didn't work (might be android 8.1 or magisk related). I also didn't have to download an img from sourceforge as the app can download the files itself.
Click to expand...
Click to collapse
An .img works best if you use external sdcard. You can partition it or use the whole thing.
DragonFire1024 said:
An .img works best if you use external sdcard. You can partition it or use the whole thing.
Click to expand...
Click to collapse
Yes, however my pixel 2xl doesn't have an sdcard slot .
Projectivy Launcher (formerly ProjecTivy Tools) now has its own dedicated thread located here.
Intro
There's so much information here that a new user could probably feel lost without the courage to read everything. So let's keep things simple : as the thread's title says, the primary aimed devices are projectors produced by Xiaomi related brands (xiaomi/fengmi/wemax), though it could probably be useful to other Android Tv models and other brands, so you might want to keep reading until the end of the introduction.
What you can find here :
Full tutorial to Googlize your chinese device with my custom made Google Apps package dedicated to Android Tv 6 (only tested on MiUi Tv, root required)
General FAQ related to these devices [post #2]
Information on how to root xiaomi/wemax/fengmi/vava projectors (and custom made TWRP for many chinese models) [post #2]
Full firmware and OTA for many models [post #2]
Google Apps / Services instructions
Here's a full tutorial to root and install Google services on your Android 6 MiUi device (ie: chinese xiaomi/fengmi/wemax).
This has been tested successfully on all devices where a custom TWRP is available below. If anything goes wrong for you, try to factory reset / clean flash
Except for "AndroidMediaShell" (Google Cast server), most (all?) features are working fine including :
Tv settings
Google Play (to let it install/update apps, please enable the Accessibility Service)
ATV remote service : if you install Google ATV remote on your smartphone, everything (including speech recognition) will work
Google Assistant : with the Accessibility Service enabled, a short press on the mic button on your stock remote control will launch Google Assistant. Then, when it's listening, press and hold the mic button while speaking and release it when done. According you've used More Locale to change to your mother tongue, this will even work in your language.
Installation steps:
root your device (see post #2) (you don't need to flash any firmware)
if not already done, install the latest version of ProjecTivy Launcher and launch it
execute Applications / install 3rd party apps, then install :
Aptoide Tv Store
ATV launcher [optional] (alternative launcher)
Youtube [optional]
MoreLocale [optional] (in case your mother tongue is not english, it will let you choose more than what's listed in Android settings)
Google Apps/services (don't forget it )
execute Applications / Freeze Stock launcher (to disable your stock home screen)
execute Applications / Freeze Stock apps (to disable most Xiaomi apps and services)
execute System / Custom Props override (to pass safetynet checks, enable more stock behavior and fix black screen with non-stock launcher)
execute System / Accessibility Service, enable the service in accessibility settings (to fix "Google Play" ability to install/update apps and to link the stock remote control "Voice recognition" button to Google Assistant as well as many other features)
[Optional] Install magisk module "Nexus Media" to change the stock bootanimation (go to Shortcuts / Magisk Manager to execute it, and then in the left menu, "Downloads" section, just install "Nexus Media")
Reboot and complete the Welcome app to setup your Google account (first and second boot will be longer than usual)
Note that an Android accessibility setting might get enabled after the first reboot when Google Apps have been installed. It'll cause green borders around buttons. Just go to settings / accessibility and disable "talkback".
Launch Google Play to update Google apps and let the update finish before exiting Google Play (if the app's accessibility service is running as it should, it will display a message when launching/exiting Google Play)
[Optional] start MoreLocale to change your language
Disable the "smart update" in the projector settings so that it doesn't try to download and install OTAs (which would just display an "error" message after each boot, when it fails to install it)
Enjoy your Google Tv device !
Important :
Once installed, don't change the device resolution in the Android Tv settings. This is not supported by the video drivers that will then only display a checkerboard. The only known solution as of now is to factory reset and start again.
Engineering Menu App Translation
Here you'll find information about xiaomi's engineering menu app.
After a bit of google translate and reverse engineering, here's a translation of the different menus, along with my own values (1st one is for "rainman", second one for "batman")
Projector information
- Brightness [1541][1610]
- DLP vendor name [APPO][APPO]
- Production Week [1812][1921]
- Contrast ratio [3828][3370]
- Brightness Uniformity [940][856]
- Serial Number
- Color coordinates [r:860 g:860 b:860 x:283 y:302][r:860 g:860 b:860 x:2720 y:2790]
Solid color (android) -> displays a solid color (using android system)
Solid color (projector) -> displays a solid color (native)
Other image test (android) -> displays a gradient (using android system)
Other image test (projector) -> displays a gradient (native)
Color wheel delay -> when incorrectly set, this can lead to posterization issues (gradients become unnatural and tend to display large uniform areas) [490][420]
Save color wheel delay to Android
Image mode: change the screen light intensity
- Standard
- Highlight
- Energy saving
Temperature monitoring
- ambient temperature [31][43]
- color wheel [52][63]
- Laser temperature channel 1 [60][74]
- Laser temperature channel 2 [61][74]
- DMD temperature [-][0]
Model name [MiProjA1][MiProjLAS2]
Human body induction -> enables/disables IR sensor that disable image when coming close to the laser
Save information to projector
DLP version [major:1, minor:2, patch:5][major:7, minor:3, patch:7]
3D (when modified, need to restart to take effect) -> enable/disable 3d support
Devices list
For reference, here's a list of devices where ProjecTivy (and several of its special features) has been tested working fine.
Only models using Android 6 can be rooted yet.
1080p Laser Projectors:
Xiaomi Mi Laser UST Projector 150" (chinese) / MiProjA1 / model: MJJGYY01FM / codename: rainman
Wemax One 7000 / MiProjA1 / model: FMWS01C / codename: rainman (thanks rockpaperscissors)
Wemax One Pro / MiProjA1 / model: FMWS02C / codename: rainman
Xiaomi Mi laser UST Projector 150" (international) / MiProjA1 / model: MJJGYY02FM / codename: anglee (thanks Nathan0121) (no root supported yet)
Xiaomi Mijia ALPD 3.0 (rear throw laser) / model: L185JCN / codename: franky (no feedback concerning twrp yet, try rainman and report if it works)
4k Laser Projectors:
Xiaomi Mi Laser UST Projector 150" 4k (chinese) / MiProjLas2 / model: MJJGTYDS01FM / codename: batman
Xiaomi Mijia 1S 4k (chinese) / MiProjLas2 / model: MJJGTYDS04FM/ codename: batman
Wemax A300 / MiProjLas2 / model: L1668FCF / codename: batman
Fengmi 4K cinema laser / MiProjLas2 / model: L176FCN / codename: batman
probably not released yet / MiProjLas2 / model: L246 / codename: batman
Fengmi 4K cinema pro laser / FMProjA2 / model: L176FCNPro / codename: jerry (no root supported yet)
Fengmi 4K C2 (cinema 2) / ? / model: L166FCN / codename: jerry (no root supported yet)
Fengmi 4k Max / model: L406FCN / codename: jerry (no root supported yet)
Xiaomi Mi 4K laser UST Projector 150" (international) / model: XMJGTYDS01FM / codename: angleeUHD (no root supported yet)
Led projectors:
Xiaomi Mi Home Projector Lite / Mijia DLP Projector Youth edition / MiProjLED1 / model: MJJGTYDS02FM / codename: conan (root using rainman twrp below)
Mi Smart Compact Projector (international) / Mijia DLP Projector Youth Global edition / model: M055MGN / MiProjM05 / SJL4014GL / codename: ?
Fengmi M055FCN / model: M055FCN / MiProjLED1 / codename: doraemon (root using rainman twrp below)
Xiaomi Mijia Mi / ZMiProj / model: TYY01ZM / codename: zodiac
Tvs:
Xiaomi Mi TV 3s / codename: mission impossible
Xiaomi Mi TV 4 / codename: pulpfiction
Xiaomi Mi TV 4a/4c/4s/4x / codename: matrix/xmen
to be completed
More in post #2 below
FAQ and more resources related to these devices
Differences between projector devices
Wemax One / Chinese Xiaomi Mi Laser:
They are (almost ?) the same.
Software-wise :
They are exactly the same (exaclty same codename, firmware, etc...)
Hardware-wise :
Wemax is black, Xiaomi Mi is white
Wemax is described to be 7000 lumens (1688 ansi lumens), Xiaomi mi 5000 lumens (1600 ansi lumens) (not sure if hardware is different or it's only a software parameter that changes its laser power)
Chinese Xiaomi Mi Laser/ International Xiaomi Mi Laser:
Software-wise :
Chinese one comes with android 6.0.1 and MiUI Tv (a Xiaomi UI dedicated to chinese users), International one comes with android 8.1 (more details below)
Hardware-wise :
Chinese one is equipped with DDR3 ram, International version DDR4
Chinese one has Amlogic T968 with onboard Mali T830 gpu, International one has Amlogic T962 with onboard Mali 450 gpu (somewhat less powerful, not sure it has any real world impact)
Also note than more often than not, International version will probably come with a warranty. It might be important, as few people complaining about dead white pixels seem to have a hard time getting their chinese projector repaired.
Pros/Cons of 8.1 international device / firmware (as of 10/10/2018)
This might help people choose between 02 international version and 01/wemax devices. Most of the information below come from this test. This is however subject to change as I believe Xiaomi will probably enhance their drivers in the coming monthes.
Pros
Complete software translations (no more chinese ressources)
Better user interface
Google Play Store availability
Better support of media apps that hardly work on 6.01 (Netflix, Prime Video...)
Better default colorimetry (but less configurable)
Less input lag (75,6 ms vs 126,6 ms) fixed on 1218+ firmwares
Cons
No 3d support
Less options related to display settings (missing RGB levels)
Worse image quality as noise reduction and sharpness seem to be less effective than on the 01 version
Judder and image tearing during media playback
Can devices international firmware be flashed on chinese models
No :
- devices hardware is not exactly the same
- partition layout is different (android 8.x requires a vendor partition)
- we don't have access to any international firmware
Supported video modes
EDID data here for "rainman" (1080p version) : View attachment edid-rainman-report.txt
EDID data here for "batman" (2160p version) : View attachment edid-batman-report.txt
EDID data here for "jerry" (2160p version) : View attachment edid-jerry-report.txt
EDID data extracted with HDMI 2.0 enabled from /sys/devices/hdmirx.28/hdmirx/hdmirx0/edid and analyzed with Advantiv EDID Editor 1.01.0268
Is my 4K device really displaying in 2160p ? Why does YouTube refuse to stream 4k ?
- Yes.
- Blame it on Google. Or AmLogic.
More details here.
Note : more recent devices such as Fengmi Cinema 4k pro (codename Jerry) based on Amlogic T972 soc don't have this limitation (they support VP9 hardware accelerated decoding)(but seem to lack 3D support)
ALR Screens
Interesting post from @servo386 regarding Ambient Light Rejection screens dedicated to UST devices.
Rainbow effect
I see many questions regarding rainbow effect (due to the DLP technology used). What I can say is that I never saw anybody complaining about it on the Mi laser projectors. A previous projector I owned (an Optoma) was also using DLP technology and I could see this rainbow effect from time to time. In the case of rainman/batman, I've never been able to see it.
Input lag
The Mi laser projectors have relatively high input lag (150/175 ms). Firmware updates sometimes help. As of september 2019, the lowest input lag can be obtained on "Monitor" or "Game" mode (approximately 100ms on batman, 75ms on rainman). If your device is rooted and you're using the ProjecTivy Tools, you can also use the "User" mode, and long press the "back" button to get down to the same input lag as "Monitor" mode, with the benefits of keeping your calibration settings.
Dead/black/white pixels
One owner of the chinese version here (french) who had a dead pixel managed to fix it by increasing RGB custom settings above 1500 for some time (don't know how long). When reverting to previous values, the white pixel had disappeared. Didn't work out for another user, but it might be worth a try.
This might change in the future (in this case, please keep me informed), but trying to manually repair by changing the chip is a dead end. It's not the usual Texas Instrument DLP4710FQL, but the DLP4711FQL (source), which is not compatible(source) and can't be bought online.
Display issues with MJJGTYDS01FM (Xiaomi branded 4k model)
Many display issues can affect this device : taking time (minutes) to start displaying something, displaying only half image or white lines/bands... Most issues appear when the device is cold and get fixed when it has heat up.
Seems like a hardware design issue that can be fixed by removing a few screws. More information here. After this, like your projector, you won't be screwed anymore
More details can be found here as well.
HDMI input ports don't work anymore in International devices after upgrade
Install the tools, launch engineering menu and select "HDCP key reset" (thanks @xthing)
Cross platform Remote Control
I also developped a simple web based remote control for MiUI TV (Xiaomi with chinese interface) based android devices (such as projectors, boxes, TVs).
No need to install anything special on your controlled device, this website/webapp communicates with the MiUI TV internal web server to send events to your device.
It should be compatible with anything running a web browser (provided it's quite up to date): Android, iPhone/iPad, PC/Mac computers...
Just head to http://mireco.hopto.org, configure your device local IP address and you're good to go.
More details on GitHub.
Other Tools
MiiInfo from 4PDA user Loly, shows various details concerning your projector.
Firmware updates after rooting and/or installing Google Apps
Firmware updates won't install if files on your system or kernel partition are modified. Using the ProjecTivy Tools and installing the Google apps won't modify existing system files, but rooting with magisk will modify the kernel. So before any update, you have to restore your kernel (aka "boot") partition using TWRP, and then reapply Magisk once update is done.
Google Apps Issues / not yet working
Amazon Prime video : it's been reported that Amazon purposefully blocks the app on projectors. The app loads, but refuses to stream videos. Some previous versions (requiring mouse for some features) work fine though. You can install the most recent compatible one using the ProjecTivy Tools.
Netflix : No recent Tv version seems to work. Some previous versions (requiring mouse for some features) work fine though. You can install the most recent compatible one using the ProjecTivy Tools. Anyway, due to missing full widevine support, full hd / 4k will probably never work.
Chromecast framework (Google Cast Server, aka AndroidMediaShell) isn't supported (devices need to be approved by Google to be supported)
Recovery
To go into recovery, turn off your projector, unplug it, hold down OK and BACK buttons simultaneously (OK and HOME for anglee) on your remote and plug back your projector while still holding them down.
Warning : don't "hot-unplug" it, turn it off before, or it won't work.
If you're looking for TWRP, have a look a few points below
Unroot
Start the Magisk Manager app and select uninstall
OR
Boot Twrp and reflash the Boot (kernel) backup you made just before installing Magisk
Factory Reset
Reflash the full stock firmware available below in this post. This doesn't require any intervention on your part so it should work even if you can't see the display
OR
Boot the stock recovery and select the "reset device" (not sure of the exact terms) option
Root
Note : both methods below work for rainman as well as batman (4k) devices.
Easy Method:
This method doesn't require any special hardware, only the TWRP I made (3.2.2.0, based on stock recovery files), along with another config file.
Thanks to @cr4zyw3ld3r who made a video tutorial based on the following instructions.
For french people, here you can find a tutorial made by Pierre. Thanks to him.
Extract this file View attachment batman_twrp_3.2.2.0b.zip (for "batman" 4k), this file View attachment zodiac_twrp_3.2.2.0.zip (for "zodiac"), or this file View attachment rainman_twrp_3.2.2.0.zip (for "rainman" 1080p and most other devices such as conan) at the root of your (FAT32 formatted) USB drive, where you also place the latest magisk version (magisk 20+ version support has been added on tools v3.5+), and plug it into your projector (I used the right USB port)
I also built (but not tested) a twrp for Vava projectors here : View attachment vava_twrp_3.2.2.0b.zip (please report if it works).
Download ADB for your computer (check here)
Start command line (terminal)
Enable USB debugging in Android settings / developer options (you can access them from the projectivy tools)
Type "adb connect IP_OF_YOUR_DEVICE:5555" to connect through the network
Type "adb reboot update" (This will restart your device and make it boot the TWRP on the USB drive.)
Once in TWRP a mouse will be required. Make backups if you wish (at least "boot" partition that you'll need to restore before applying any OTA update), and then mount SYSTEM, and install magisk in order to root the device (it will be in "/udisk" and will be called Magisk-......zip)
Note : to thank the donors, I also developed an application that installs on your Android smartphone, which automates steps 1 to 6. There is no need for computer or custom command lines in this case. Once the app is connected to your projector, you're only one button click away from TWRP.
Note : if it still boots to stock recovery and not twrp, make sure you extracted the zip and not only copied it to your usb drive. If it's extracted correctly but still doesn't work, try another usb drive, a few people reported that this fixed their issue (some users had to try 3 or 4 usb devices before finding one the works).
Old Method:
With the correct hardware, you can root your device, following this tutorial from @servo386
To simplifiy the rooting process described in the link above :
Extract this file View attachment twrp-files.zip at the root of your USB drive, where you also place the latest magisk version (as of now 19.3), and plug it into your projector
Follow the steps described in the tutorial, up to the point where you have a root console access in recovery
Then, according you've plugged your USB drive before starting your device, just type ". /udisk/twrp.sh" in the root console. This will copy the necessary files and automatically run twrp, reducing the number of steps (and potential mistakes) to root your device.
Once in TWRP, make backups if you wish, and then mount SYSTEM, and install magisk in order to root the device (it will be in "/udisk" and will be called Magisk-.....zip)
Roms / Dumps
Due to issues on the new XDA 2021 website (preventing edition of long posts containing many links), full firmwares and OTA have been (temporarily ?) moved to post #4.
You'll have to scroll down by yourself, I can't even add a link to it
Spocky great work this looks fantastic,
you highlighted that you're not yet rooted and I've tried a few things so far that haven't worked however a few days ago one of the guys on the XDA forums has managed to access command line probably using the jtag points on the board. It's quite likely but this is a good way to get a ADB and then root access, and therefore if uses nandroid type tools he should be able to complete a full dump of the ROM.
I have a Chinese projector with same firmware as your own, but I'm hoping we can load the Android TV launcher interface as in the international version.
Let me know if you need anything specific tested.
Roms / Dumps
Warning: Full roms below can help you recover your device if you're stuck with a non functional projector. However, if your device shipped with a more recent firmware than the one you're trying to flash and has a more recent hardware revision, you might have display issues. So before flashing a full firmware, please try to boot to recovery and use the "wipe all data" option. On MiTv devices, this will basically do the same thing (this will automatically flash the device with the stock shipped firmware, which is present on the /backup partition).
MJJGYY01FM / FMWS01C / FMWS02C (Chinese Xiaomi Mi Projector / Wemax One) [rainman]
Full rom 1.3.63 (6.0.1.935) (thanks to @servo386 and rockpaperscissors)
OTA [user] from 6.0.1.935 to 6.0.1.1074 (1.3.63 to 1.3.74)
OTA [user] from 6.0.1.935 to 6.0.1.1218 (1.3.63 to 1.3.97)
OTA [user] from 6.0.1.935 to 6.0.1.1289 (1.3.63 to 1.3.105)
OTA [user] from 6.0.1.1074 to 6.0.1.1218 (1.3.74 to 1.3.97)
OTA [user] from 6.0.1.1218 to 6.0.1.1289 (1.3.97 to 1.3.105)
OTA [user] from 6.0.1.1289 to 6.0.1.1425 (1.3.105 to 1.3.105)
OTA [user] from 6.0.1.1289 to 6.0.1.1453 (1.3.105 to 1.3.105) (Latest Stable)
MJJGTYDS01FM / L1668FCF / L176FCN / L246 (4k Chinese Xiaomi/Mijia Mi Projector / Wemax A300 / Fengmi Cinema 4k) [batman]
Full rom 1.3.97 (6.0.1.312) ONLY FOR MIJIA
Full rom 1.3.105 (6.0.1.494) Owners of recent fengmi devices, use the rom below
Full rom 1.3.105 (6.0.1.669) Should be working on most recent Fengmi Cinema 4k, with hardware version l176_1. If yours is fm_10, it probably won't work (I still need a /dev/block/backup image of fm_10 hardware version)
Full rom 1.3.105 (6.0.1.724) Extracted from a recent Mijia 1S. Should probably work on most batman devices (people with fengmi 4k fm_10 stuck on a black screen, give it a try)
OTA [user] from 6.0.1.312 to 6.0.1.494 (1.3.97 to 1.3.105)
OTA [user] from 6.0.1.494 to 6.0.1.624 (1.3.105 to 1.3.105) (ONLY FOR MIJIA)
OTA [user] from 6.0.1.494 to 6.0.1.793 (1.3.105 to 1.3.105) (Latest Stable)
MJJGYY02FM (International Xiaomi Mi Projector) [anglee]
Full rom 8.1.0.1317 (OPM8.190205.001.1317)
Full rom 9.0.0.1911 (PQ3B.190705.003.1911)
L176FCNPro / L166FCN / L406FCN (Fengmi 4K cinema pro, 4k Max, C2) [jerry]
Full rom 1.2.1.1689 (only for Cinema Pro, more recent device should use the next one)
Full rom 1.4.6.2378 (use this one for Fengmi C2 and Max 4k. Cinema Pro should work fine too)
MJJGTYDS02FM (Mijia Projector Youth edition) [conan]
Full rom 1.3.97 (6.0.1.304)
Full rom 1.3.123 (6.0.1.519) (Prefer this version as it's probably compatible with most recent devices too)
TYY01ZM (Xiaomi Mijia Mi) [zodiac]
Full rom 1.3.67 (6.0.1.391)
M055FCN (Fengmi M055FCN) [doraemon]
Full rom 1.3.123 (6.0.1.309)
L206FCN-X2 (Fengmi Formovie T1) [nemo]
OTA [user] from 2.0.0.2289 to 3.0.0.3049 (Not final, but stable)
How to flash :
[OTA only] be sure your current firmware version is the same as the "from" version specified above.
Download and extract the zip file to the root of a USB thumb device and follow the procedure to boot into recovery mode. The full firmware or OTA update will be automatically installed (approximately 5 minutes will be necessary). You shouldn't lose any data (well, unless there's a power cut during the update process ). Even after flashing the full firmware, I still had my apps installed. I suppose you need to factory reset if you want a clean install.
Those willing to reinstall from scratch will need to use the "wipe all data" from the recovery menu. If you can't acces it somehow, you can try flashing a full rom (935 for rainman, 312 for batman *mijia* or 494 for batman *fengmi/wemax*), and then flash to the latest available OTA (you might need to chain flash if no direct OTA is available from you stock full rom to the rom you're targeting).
Please note that for a few users, the OTA won't install (it will stop during the update process with a chinese message). It's due to the fact that during installation, a check on the system files and kernel is made and at least one could not pass. This will be the case if you have rooted your device (only kernel is modified then). In that case, if you want to apply the update, you'll need to revert to an unmodified kernel/system. If you didn't modify system partition, restoring kernel partition (boot.img) should be enough (or uninstall Magisk from magisk manager app). If not, try restoring system.img also. If nothing works, reinstall from scratch (see just above)
wemax 7000
Great job !
I will try it tomorrow on my wemax 7000.
Let me know how I can help.
Should I also make a dump of my Chinese rom ?
How did you dump yours ?
I also badly hope to get the android tv rom working with the play store.
Thanks a lot !
Getting a wemax dump would be great indeed !
I did it with adb, connected wirelessly to my computer.
To do the same :
- download adb for your system
- connect wirelessly by using "adb connect IP.OF.YOUR.WEMAX"
- create a folder for the dump on your computer : "mkdir dump"
- go in it : "cd dump"
- pull system files : "adb pull /system"
Then every file that doesn't require root access will be downloaded to your computer. Just make a zip of it and upload it somewhere.
If it feels too complex for you, wait for a few days, I'll probably upload a tool to make an archive and automatically upload it somewhere. I just need to fix a few things before.
Hello, I'm the one who got root via the HDMI->UART diagnostic bridge. All credit goes to @loly though on 4PDA, who is the person who actually figured out this process on his Xiaomi Mi TV 4A, which has a similar chip to this projector so I took a guess that it would work too.
The posts I made on AVSforum are pretty long and lots of pictures and formatting so for now im just gonna link it but hopefully I can easily copy over the posts and make them here too.
https://www.avforums.com/threads/xi...aser-projector.2142037/page-101#post-26580089
Hi,
I installed the app and got a Chinese popup telling me that what I was doing was forbidden to users.
The menu is in Chinese too and I tried translating it with google translate but It's very tedious and I'm not very confident going through the menus.
Thanks a lot for the procedure for the backup.
I will cleanup all the installed apps and maybe reset it completely so that i can share the backup online.
If you're going to prepare a tool to do so, I will wait so I can test it as well.
Let me know if I can help you by sending you more infos.
Cheers
Jerome
Xiaomi Mi Laser Root Procedure
This is a long one. Also it was originally written for an audience who may have not been as familiar with Android/Linux commands so it has lots of explanation that might feel out of place on XDA.
So first and foremost ALL CREDIT BELONGS TO @loly ON THE 4PDA.RU FORUM WHO ACTUALLY DISCOVERED THIS PROCESS
https://4pda.ru/forum/index.php?showtopic=810785&st=3260#entry75802829
I definitely am just a copy cat who guessed that his process would also work on this device since their both Xiaomi TV devices with Amlogic T96* boards.
So if you read his post (which you definitely should in addition to this post in order to get the full picture of how this is done), you'll see that this is quite complicated and a kind of high level hack. I hope I'll be able to explain it enough and walk through it enough for it be fairly accessible for less technically inclined people who want to root their Xiaomi projectors.
What is required:
1. HDMI cable you can chop up or an HDMI breakout cable like this one: https://www.amazon.com/Adapter-signals-Terminal-Breakout-Connector/dp/B01CU9SHOO/
2. UART to USB adapter cable/board like this one: https://www.amazon.com/Adapter-Serial-Converter-Development-Projects/dp/B075N82CDL though there are cheaper options available
3. Cables/wires to connect both things. The USB UART package above comes with some, though you'll have to strip the ends to screw them into the terminals of the HDMI breakout board.
4. A spare USB drive
5. A computer to use the USB to UART adapter and a terminal program, i am using Putty.
So the basic idea behind this is that one of the HDMI ports (HDMI 1 in this case, the one closest to the edge) also serves as a diagnostic/UART port via 3 of the 19 pins of the HDMI. When this HDMI port is properly wired to the UART adapter, and you have a terminal open observing said port, upon boot the machine reads out all its startup stuff and when booting into recovery, gives you a completely liberated UNIX terminal that accepts input from the UART terminal, with full root privileges and busybox! As @loly says in his post, here we thank the people at Xiaomi for not bothering to secure this section and giving us full diagnostic root access with busybox. This is almost surely the way the developers of this machine would interact with this machine and developed for it. So let me try to explain how this works and how we get to TWRP and root.
Steps:
1. We need to properly connect the correct pins on the HDMI cable to the correct pins on the UART.
Here I am going to re-post some of @loly's images from the original thread, so all credit goes to him.
Here we see the pins we need. Pin 14 is our VCC, which in this 5v (the UART adapter im using has a switch for 3.3v or 5v, this switch needs to be set to 5v!) Pin 15 is the receive pin and Pin 16 is the transmit pin
The fourth lead we need is the GND (ground), which in the case of an HDMI cable is usually an un-shielded wire that connects to the the case of the connector itself.
I'm going to stop here for a sec and say this is why it's alot easier to use the HDMI breakout board over trying strip an HDMI cable and finding which wire corresponds to which pin (you need a multi-meter to do that)
its a small investment but it makes everything ALOT easier. On the HDMI breakout board, the ground terminal is pin 20.
the corresponding pins on the UART are pretty straightforward. VCC goes to VCC on the UART, pretty straightforward, on the other hand the RX pin of the HDMI (pin 15) goes on the TX OF THE UART makes sense right? the receiever of the HDMI should be listening to the transmitter of the UART and vice versa, so the TX pin of the HDMI goes on the RX pin of the UART. The GND pin (pin 20 on breakout board) goes to the GND on the UART.
Here's my setup. Sorry for the not very great picture. The terminal blocks on the HDMI breakout board work basically like you were connecting speakers to an amp, you unscrew the terminal till you see a little metal hole and you stick the stripped tip of the cable into the hole and screw the terminal back up till its snuggly holding onto the cable. You can use a multi-meter if you have one to make sure the wire is making contact with the terminal and even test the exact pin with the cable to make sure the connection goes all the way. If you're cable is making contact with the metal of the terminal, it is almost certainly correctly making contact with the actual HDMI pin, barring maybe a badly manufactured breakout board. I used spare MALE end pin connector cables to strip the ends and stick in the terminals, and connected them to the FEMALE connectors that came with the UART adapter. You don't necessarily have to do it this way, you can directly strip one of the female ends of the cable and connect the other female end to the pins on the UART, but you'll have a pretty short cable from HDMI to USB and you'll probably need a USB extension to comfortably use it with a computer.
So now you have you're HDMI diagnostic cable!
2. Setup your computer for UART and Putty.
Connect your UART to USB adapter to your computer. In Windows 10, it should automatically install drivers, but if it doesn't, your device should come with a link or something to download the drivers. I'm not going to get into the specific of how to install drivers on Windows computers but needless to say, you need to get the computer to recognize the device and properly utilize it via the drivers. Once you have it properly installed on the machine, it should show up in your device manager under Ports (COM & LPT) or something similar.
this is important because we need to 1. determine what COM port you're device is on and 2. change the baud setting.
So in the photo you see that it tells you what COM port is, which we need for later.
Now you need to go into the settings of the device and go into Port Settings tab
WE NEED TO SET THE BITS PER SECOND TO 115200!
Very important!
Setting up putty:
Basically open up putty and put the button on Serial, set the speed to 115200 and in the SERIAL LINE put the correct COM port number (COM1, COM2, COM3, ect)
Pressing enter on this should open a big blank black terminal with no activity. Thats good because its working. If it wasn't, you'd get an error about not reaching COM port or something.
3. Testing out our diagnostic cable with UART and Putty
Unplug your projector. Plug your HDMI into HDMI port 1 and connect your USB to computer. Open up a Putty terminal session as outlined above. If you get a big black screen with no errors upon launching the terminal, youre in a good spot.
Plug in the Projector. If you've done everything right you should get a big long readout of text scrolling by as it boots. If you get this, congratulations, you've accessed the diagnostic correctly!
The final step for actually accessing the usable terminal is doing the same but while booting into recovery.
4. Booting into recovery
Turn off your projector. Unplug it. Take your remote and hold down THE OK BUTTON and the BACK BUTTON at the same time. While still holding this, plug in the projector. It should start booting up. You're terminal Putty should be going crazy with text readout like last time. After a few seconds, let go of the buttons. Your projector should eventually end up on the Recovery menu, which is just some big buttons in english and chinese with a black background.
image courtesy of jaberwocky on AVS
After the readout in the terminal has stopped, press enter. It should skip to a new line with
Code:
~#
Tada, root! You're officially in a fully privileged root terminal in the underlying unix system of the projector.
This is the hard part of all this. If you've successfully reached this part, you've won the battle. Everything from here on out is just a couple of commands and some files being downloaded and transferred.
Launching TWRP, making a Nand dump, flashing Magisk, getting Root
So if you indeed have reached the point where, from recovery, you can enter commands into the terminal session, now the question what to with it. The answer is basically anything you want, but let's launch TWRP and go from there.
So here is where you need to download this zip file, also courtesy of @loly from the original russian thread. He went to the trouble of (I'm assuming) compiling his own TWRP for Xiaomi Mi TV 4A which, which as I've mentioned before it's chip (Amlogic T962) is the in the same family as the chip in our projector (Amlogic T968) so it works. That said I would say right now this is not a full TWRP specially made for our projectors, so we aren't going to flash it. We are going to launch it from the terminal (as per @loly's instructions) and use it, but not flash it to our recovery partition. This is for the best right now because a. it's not for our device and b. stock recovery allows us to install OTA updates if they come in the future
View attachment TWRP.zip
my attached version has only the twrp folders, no recovery image, no magisk included.
https://yadi.sk/d/uTUrwdAl3ZyUcN <---- original zip
Download that zip file and unzip its contents right into your USB drive, so that the folder `twrp` (lowercase) is in the root of your drive . This will make it easier to type the commands exactly as they appear later. Ignore the recovery.img, we're not flashing this onto this device.
The magisk included in the TWRP.zip is old by this point. I flashed Magisk 17.1 flashable zip, the latest stable as of this writing. Get it here https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip and put it on the flash drive.
A quick primer, this terminal instance has Busybox installed. Busybox is a "swiss army knife" of unix command like binaries because it packages all the standard linux commands into one single binary, so instead of calling
Code:
ls
to see the contents of the directory you instead would type
Code:
busybox ls
and it would work.
One last thing before I continue: while doing terminal stuff, I quickly learned that occasionally the terminal would throw up all kinds of gibberish which, as far as I can tell, had no rhyme or reason to it and more important had no discernible effect on what i was doing. Its a weird bug that maybe only ill experience because of my setup, I don't know. It would take two forms, one where it would throw up a bunch of lines of technical sounding text which included references to errors and such, but would ever actually affect anything. the other is when it would randomly spit out something like "hotplug_9" and again, id just press enter to get to the new line and nothing would have been affected. Don't be alarmed.
1. Insert USB drive into projector
Take your USB and plug it in. On your terminal, you should a small flurry of activity and references to a new device located at
Code:
/dev/block/sda1
or
Code:
/dev/block/sda2
take note of this, because this is the physical address of your USB drive thats going to have to be mounted. sda1 is the typical one, in my experience.
2. Mount USB and copy over files
This is just a series of commands, type them in precisely as I have them here, assuming you've maintained the same file structure on your USB stick as I did, unzipped the TWRP.zip straight onto the root of the USB.
Code:
busybox mount /dev/block/sda1 /sdcard
This mounts your USB device to the folder `/sdcard' if you're usb is at a different device location, change it appropriately.
Code:
busybox ls /sdcard
Just do a quick readout of the contents of `/sdcard` to make sure it properly mounted. you should see the contents of your USB drive listed here
Code:
busybox cp -r /sdcard/twrp/twres /
Copy the folder `twres` from the USB to the root of your projector
Code:
busybox cp -r /sdcard/twrp/license /
Copy the folder `license` to the root of your projector
Code:
busybox cp -rf /sdcard/twrp/etc/* /etc
Copy the contents of the folder `etc` to the etc directory on your projector
Code:
busybox cp -rf /sdcard/twrp/sbin/* /sbin
Copy the contents of the folder `sbin` to the sbin directory on your projector
Code:
busybox chmod -R 0750 /sbin
Change the permissions of the sbin folder to its all executable
So thats all the copying, now the moment of truth
3. Launch TWRP
YOU NEED A MOUSE PLUGGED INTO THE PROJECTOR TO NAVIGATE TWRP!
Code:
/sbin/run.sh
after hitting enter on this command, TWRP should boot up on your screen (and a bit of readout in your terminal
IF TWRP DOESN'T LAUNCH, YOU'VE DONE SOMETHING WRONG. GO BACK AND CHECK EVERYTHING.
I hope if you're doing this you're somewhat familiar with TWRP, but I will try to walk through the 2 most important things to do
4. Rom backup
One of the big buttons is BACKUP, go there and you'll see a series of check boxes for each of your partitions (boot, bootloader, recovery, system, ect). Select the ones you want (I selected all but I know for a fact this is unnecessary but I did't want to overlook anything and I didn't want to guess which I could ignore). It should ask you where to save the backup, select either the USB drive or internal memory and pick a folder. Slide over the thing to begin backup. It'll take a bit but eventually it should finish. Tada, you have a backup of your entire device.
5. Flash Magisk (ie get root)
This is the big kahuna, the one that unlocks everything OS-wide. Before trying to flash Magisk, we need to mount the system partition. This was big headache for me cause I didn't know why all the commands in the install scripts for failing and it was because /system/bin contains all the commands/binaries that Magisk installer script uses to do its stuff, so thats why we need to mount it first before trying anything. Go to the big MOUNT button and you should see checks next to USB and INTERNAL MEMORY or something to that effect, i can't remember off the top of my head. Almost certainly SYSTEM does not have a check next to it, meaning its not mounted. Click the check mark next to SYSTEM and that should be it, it is now mounted.
There is a quick way to check this, which is to go to ADVANCED>TERMINAL and in the terminal type
Code:
mount
if you get any sort of read out of device partitions, you're good, that means the mount command is working meaning the /system/bin is being made available to TWRP to execute commands.
With that done, go over to the INSTALL button on the home screen and navigate over to your USB stick and find the Magisk 17.1.zip. Select it. Check the check mark to reboot after install. Slide over the slider to begin the install. Moment of truth, you'll likely get to errors in big red text something like MOUNT -O BIND /SDCARD FAILED or something, thats fine, ignore it. It should go onto to say
Code:
|----Magisk Installer Script 17.1----|
or something like that, that means its doing its thing. Everything should go well and it should ask to reboot.
6. Verify root
Once you boot into the Xiaomi home screen after flashing Magisk, you should get some kind of thing asking to confirm that you want to install the application. That application is the Magisk Manager, which means you did it, Magisk installed successfully!
Go ahead and install some app that you know asks for superuser and it should prompt you for superuser access, grant it. You did it, you're root!
View attachment 4617430
jhordies said:
Hi,
I installed the app and got a Chinese popup telling me that what I was doing was forbidden to users.
The menu is in Chinese too and I tried translating it with google translate but It's very tedious and I'm not very confident going through the menus.
Thanks a lot for the procedure for the backup.
I will cleanup all the installed apps and maybe reset it completely so that i can share the backup online.
If you're going to prepare a tool to do so, I will wait so I can test it as well.
Let me know if I can help you by sending you more infos.
Cheers
Jerome
Click to expand...
Click to collapse
There's really not much this app can break (and not much to change neither). Most interesting thing would be the information page, along with the temperature page.
Concerning the dump, no need to cleanup anything as user data is stored :
- in /sdcard (internal memory) mount
- in app folder which can't be accessed without root
Dumping /system won't access any of them, this will basically only copy files that where part of the last firmware installed on your device.
As for my app, not sure I'll have time to finish it before next week.
servo386 said:
This is a long one. Also it was originally written for an audience who may have not been as familiar with Android/Linux commands so it has lots of explanation that might feel out of place on XDA.
So first and foremost ALL CREDIT BELONGS TO @loly ON THE 4PDA.RU FORUM WHO ACTUALLY DISCOVERED THIS PROCESS
https://4pda.ru/forum/index.php?showtopic=810785&st=3260#entry75802829
I definitely am just a copy cat who guessed that his process would also work on this device since their both Xiaomi TV devices with Amlogic T96* boards.
So if you read his post (which you definitely should in addition to this post in order to get the full picture of how this is done), you'll see that this is quite complicated and a kind of high level hack. I hope I'll be able to explain it enough and walk through it enough for it be fairly accessible for less technically inclined people who want to root their Xiaomi projectors.
What is required:
1. HDMI cable you can chop up or an HDMI breakout cable like this one: https://www.amazon.com/Adapter-signals-Terminal-Breakout-Connector/dp/B01CU9SHOO/
2. UART to USB adapter cable/board like this one: https://www.amazon.com/Adapter-Serial-Converter-Development-Projects/dp/B075N82CDL though there are cheaper options available
3. Cables/wires to connect both things. The USB UART package above comes with some, though you'll have to strip the ends to screw them into the terminals of the HDMI breakout board.
4. A spare USB drive
5. A computer to use the USB to UART adapter and a terminal program, i am using Putty.
So the basic idea behind this is that one of the HDMI ports (HDMI 1 in this case, the one closest to the edge) also serves as a diagnostic/UART port via 3 of the 19 pins of the HDMI. When this HDMI port is properly wired to the UART adapter, and you have a terminal open observing said port, upon boot the machine reads out all its startup stuff and when booting into recovery, gives you a completely liberated UNIX terminal that accepts input from the UART terminal, with full root privileges and busybox! As @loly says in his post, here we thank the people at Xiaomi for not bothering to secure this section and giving us full diagnostic root access with busybox. This is almost surely the way the developers of this machine would interact with this machine and developed for it. So let me try to explain how this works and how we get to TWRP and root.
Steps:
1. We need to properly connect the correct pins on the HDMI cable to the correct pins on the UART.
Here I am going to re-post some of @loly's images from the original thread, so all credit goes to him.
View attachment 4617376
Here we see the pins we need. Pin 14 is our VCC, which in this 5v (the UART adapter im using has a switch for 3.3v or 5v, this switch needs to be set to 5v!) Pin 15 is the receive pin and Pin 16 is the transmit pin
The fourth lead we need is the GND (ground), which in the case of an HDMI cable is usually an un-shielded wire that connects to the the case of the connector itself.
I'm going to stop here for a sec and say this is why it's alot easier to use the HDMI breakout board over trying strip an HDMI cable and finding which wire corresponds to which pin (you need a multi-meter to do that)
its a small investment but it makes everything ALOT easier. On the HDMI breakout board, the ground terminal is pin 20.
the corresponding pins on the UART are pretty straightforward. VCC goes to VCC on the UART, pretty straightforward, on the other hand the RX pin of the HDMI (pin 15) goes on the TX OF THE UART makes sense right? the receiever of the HDMI should be listening to the transmitter of the UART and vice versa, so the TX pin of the HDMI goes on the RX pin of the UART. The GND pin (pin 20 on breakout board) goes to the GND on the UART.
View attachment 4617377
Here's my setup. Sorry for the not very great picture. The terminal blocks on the HDMI breakout board work basically like you were connecting speakers to an amp, you unscrew the terminal till you see a little metal hole and you stick the stripped tip of the cable into the hole and screw the terminal back up till its snuggly holding onto the cable. You can use a multi-meter if you have one to make sure the wire is making contact with the terminal and even test the exact pin with the cable to make sure the connection goes all the way. If you're cable is making contact with the metal of the terminal, it is almost certainly correctly making contact with the actual HDMI pin, barring maybe a badly manufactured breakout board. I used spare MALE end pin connector cables to strip the ends and stick in the terminals, and connected them to the FEMALE connectors that came with the UART adapter. You don't necessarily have to do it this way, you can directly strip one of the female ends of the cable and connect the other female end to the pins on the UART, but you'll have a pretty short cable from HDMI to USB and you'll probably need a USB extension to comfortably use it with a computer.
So now you have you're HDMI diagnostic cable!
2. Setup your computer for UART and Putty.
Connect your UART to USB adapter to your computer. In Windows 10, it should automatically install drivers, but if it doesn't, your device should come with a link or something to download the drivers. I'm not going to get into the specific of how to install drivers on Windows computers but needless to say, you need to get the computer to recognize the device and properly utilize it via the drivers. Once you have it properly installed on the machine, it should show up in your device manager under Ports (COM & LPT) or something similar.
View attachment 4617379
this is important because we need to 1. determine what COM port you're device is on and 2. change the baud setting.
So in the photo you see that it tells you what COM port is, which we need for later.
Now you need to go into the settings of the device and go into Port Settings tab
View attachment 4617381
WE NEED TO SET THE BITS PER SECOND TO 115200!
Very important!
Setting up putty:
View attachment 4617383
Basically open up putty and put the button on Serial, set the speed to 115200 and in the SERIAL LINE put the correct COM port number (COM1, COM2, COM3, ect)
Pressing enter on this should open a big blank black terminal with no activity. Thats good because its working. If it wasn't, you'd get an error about not reaching COM port or something.
3. Testing out our diagnostic cable with UART and Putty
Unplug your projector. Plug your HDMI into HDMI port 1 and connect your USB to computer. Open up a Putty terminal session as outlined above. If you get a big black screen with no errors upon launching the terminal, youre in a good spot.
Plug in the Projector. If you've done everything right you should get a big long readout of text scrolling by as it boots. If you get this, congratulations, you've accessed the diagnostic correctly!
View attachment 4617385
The final step for actually accessing the usable terminal is doing the same but while booting into recovery.
4. Booting into recovery
Turn off your projector. Unplug it. Take your remote and hold down THE OK BUTTON and the BACK BUTTON at the same time. While still holding this, plug in the projector. It should start booting up. You're terminal Putty should be going crazy with text readout like last time. After a few seconds, let go of the buttons. Your projector should eventually end up on the Recovery menu, which is just some big buttons in english and chinese with a black background.
View attachment 4617401
image courtesy of jaberwocky on AVS
After the readout in the terminal has stopped, press enter. It should skip to a new line with
Code:
~#
Tada, root! You're officially in a fully privileged root terminal in the underlying unix system of the projector.
This is the hard part of all this. If you've successfully reached this part, you've won the battle. Everything from here on out is just a couple of commands and some files being downloaded and transferred.
Launching TWRP, making a Nand dump, flashing Magisk, getting Root
So if you indeed have reached the point where, from recovery, you can enter commands into the terminal session, now the question what to with it. The answer is basically anything you want, but let's launch TWRP and go from there.
So here is where you need to download this zip file, also courtesy of @loly from the original russian thread. He went to the trouble of (I'm assuming) compiling his own TWRP for Xiaomi Mi TV 4A which, which as I've mentioned before it's chip (Amlogic T962) is the in the same family as the chip in our projector (Amlogic T968) so it works. That said I would say right now this is not a full TWRP specially made for our projectors, so we aren't going to flash it. We are going to launch it from the terminal (as per @loly's instructions) and use it, but not flash it to our recovery partition. This is for the best right now because a. it's not for our device and b. stock recovery allows us to install OTA updates if they come in the future
View attachment 4617409
my attached version has only the twrp folders, no recovery image, no magisk included.
https://yadi.sk/d/uTUrwdAl3ZyUcN TERMINAL and in the terminal type
Code:
mount
if you get any sort of read out of device partitions, you're good, that means the mount command is working meaning the /system/bin is being made available to TWRP to execute commands.
With that done, go over to the INSTALL button on the home screen and navigate over to your USB stick and find the Magisk 17.1.zip. Select it. Check the check mark to reboot after install. Slide over the slider to begin the install. Moment of truth, you'll likely get to errors in big red text something like MOUNT -O BIND /SDCARD FAILED or something, thats fine, ignore it. It should go onto to say
Code:
|----Magisk Installer Script 17.1----|
or something like that, that means its doing its thing. Everything should go well and it should ask to reboot.
6. Verify root
Once you boot into the Xiaomi home screen after flashing Magisk, you should get some kind of thing asking to confirm that you want to install the application. That application is the Magisk Manager, which means you did it, Magisk installed successfully!
Go ahead and install some app that you know asks for superuser and it should prompt you for superuser access, grant it. You did it, you're root!
View attachment 4617430
Click to expand...
Click to collapse
Thank you for your time adding this post here and for the tests you've made to root this device. That's really cool !
If you have time, don't hesitate to post a full dump of your rom, we might learn a bit more than with mine.
Also I have not read your post from my computer so it might just be a bug, but Tapatalk reports your twrp.zip file as being 5 bytes only.
Edit: nevermind, your twrp is fine
I've ripped the "backup" archive that is a flashable update image of the stock image, used by the machine when you do "system restore" in recovery.
Basically here is the stock rom for the model 01 "rainmain" at last.
https://mega.nz/#!jY40SCQR!2gPjpPxzoDg3c1--pxGBR7qfKHxSyzWqU3eZGUz7kb0
#1 and #2 posts edited, adding many details, roms links...
Hi,
Thanks again guys for the effort you put on this.
I bought the hdmi breakout and a usb ttl and followed the instructions (very clear, thanks again for this) and backed up everything as you did but didn't root the device yet.
Are my .win backup files usefull to anyone (Wemax 7000) or do you need me to root the device to make the dump as spocky12 suggested?
I don't know how interesting my Chinese rom would be to others though...
Anyway it's good to know that we could flash the device with the android 8.1 rom when it will be available.
If you know anyone having the english rom, I would be willing to send him my cable to make a backup of his.
Cheers
jhordies said:
Hi,
Thanks again guys for the effort you put on this.
I bought the hdmi breakout and a usb ttl and followed the instructions (very clear, thanks again for this) and backed up everything as you did but didn't root the device yet.
Are my .win backup files usefull to anyone (Wemax 7000) or do you need me to root the device to make the dump as spocky12 suggested?
I don't know how interesting my Chinese rom would be to others though...
Anyway it's good to know that we could flash the device with the android 8.1 rom when it will be available.
If you know anyone having the english rom, I would be willing to send him my cable to make a backup of his.
Cheers
Click to expand...
Click to collapse
Thank you for your message. Glad you managed to follow @servo386's intructions. If you don't mind, I'd be interested in your .win files, to validate a few assumptions I have.
Concerning the international model, unfortunately, as of now, no owner seems to be willing to take the plunge. Hopefully it'll change soon enough.
For hackers out there, I found a tool that might prove helpful to build customs roms or repack roms using international model paritions (once somebody will dump it).
It's AMLogic Tools 5.5.0 that can be found here. I haven't had time to read the full thread yet. There might be valuable information there.
You can use it with the stock rom (935) from @servo386 that I specifically extracted and repacked with latest (1074) recovery (stock "backup" rom does not ship with recovery, which is needed by AmLogic Tools).
You can use the "customization tool" to easily extract/repack a rom that can be flashed in recovery or with special Amlogic USB flash tool.
There is also a tool that can "convert" a classic recovery to TWRP recovery (but supposedly only works with S905/S912. Might be interesting to check what is needed to make it work on our chip)
Unfortunately, I'm not an expert at building custom roms in Android (the latest custom rom I built was for Windows Mobile 6.1) (Great. I'm feeling old now ). I'm not quite sure what is allowed to be flashed with our bootloader. I haven't tried to flash anything yet, as if I brick the projector, my wife will probably kill me . But I suppose that if the custom built firmware doesn't embed bootloader/recovery, most errors will be recoverable by flashing the stock rom again.
If you want to test, don't forget to call the built rom "update-rainman.zip" and to put it in the root folder of an USB device along with this file.
Hey, it's me again
Some of you might be interested in an update to a more recent (but beta) version for wemax/chinese Mi projector.
I added a link to OTA from 1074 (1.3.74, built on May 4th) to 1189 (1.3.95d, built on Oct 12th) in the second post (yes, it's still Android 6.0.1)
To install it, just extract the zip file to the root of a USB thumb device and follow the procedure to boot into recovery mode. The update will be automatically installed (approximately 5 minutes will be necessary). You won't lose any data (well, unless there's a power cut during the update process ).
I haven't tested much, but here are the changes I've seen :
- most menus (settings) are in english now
- new settings options (the only one still in chinese) : automatic power off after 10 minutes of inactivity (doesn't seem to work, though)
- new volume UI
- Karaoke app added
- new animations during recovery installation
- wmv3 video format support added
As a side note, I've found a reference to an upcoming Xiaomi Laser projector in code, that wasn't there before : MiProjLAS2, codename batman.
spocky12 said:
...
I added a link to OTA from 1074 (1.3.74, built on May 4th) to 1189 (1.3.95d, built on Oct 12th) in the second post (yes, it's still Android 6.0.1)
...
Click to expand...
Click to collapse
Thank you so much for your work.
The file to update to the current beta is only 55Byte in size. Nothing happens when plugging in the USB stick.
===============================
I had two xiaomi laser projectors so far.
Projector 1 had dead pixels after 3 weeks of use. Here are the key figures from the engineering menu.
Here projector number 331 from 2018 calendar week 3:
It had a great contrast: 5382:1
The one complained to gearbest and got an exchange(Projector 2).
Here projector number 1196 from 2018 calendar week 13:
Contrast: 2441:1
Projector 2 unfortunately has too little contrast and is very blurred at the edges. Currently exchange projector 3 is on its way.
.bismarck
Thanks for your message. Comparing data from different projectors is really interesting.
Concerning the link, my bad, I've updated it to the right file, you can download it again if you wish.
Thanks spocky12, just loading the beta
When Projektor3 has arrived, I put the values from the menu here.
Edit: I copied the unzipped archive into the root of the USB stick. But nothing happens when inserting the stick.
.bismarck
You have to follow the procedure to boot into recovery. Either use :
- "ADB reboot recovery" if you have ADB
or
- unplug your projector, keep your remote "ok" and "back" pressed and plug your projector back in. It will boot into recovery and automatically start the update process.
(Your usb thumb drive should be formatted in fat32 and both files placed in its root folder).
Initial post for Sailfish Os for the Samsung Galaxy S2 (i9100) device.
Code:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! W A R N I N G !!
!! !!
!!(Although I am using this on my backup phone)!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! Everything you do, !!
!! you do at your own peril and risk. !!
!! !!
!! I do not bear any responsibility !!
!! for your faulty devices. !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! !!
!! ROM IS NOT SUITABLE FOR DAILY DRIVE !!
!! ONLY FOR EXPERIMENTAL PURPOSES !!
!! !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Making this port was challenging because Sailfish OS, from version 3, doesn't support kernel version 3.0 which is apparently the kernel on the S2.
Fortunately, the SailfishOS-porter guys do very seriously know their business and they are extremely helpful.
From here I would like to emphasize my gratitude towards them for helping me in this project! Thank you!
Requirements:
Before you start to download anything, please read it carefully.
The first requirement is your device must be rooted and you should be able to install a custom recovery (preferably TWRP) onto it.
For this ROM you can either use the stock partitions or you can re-partition to give more space to /system and /data. It doesn't matter which one you chose, I tried and both worked well.
Or if you scroll down to the New partition layout, you can use a completely unique partition layout which gives the most of the internal storage to Sailfish OS. (I currently use my device with this setup.)
Installation instructions:
1. Download all files, CM12.1 zip, Sailfish OS zip, twrp2.8.7.img and kernel*.img to the external SD card on the phone
2. Reboot into TWRP (hold buttons: Power on + Home + Volume up)
3. Do a factory reset
At this point if you want you can repartition the S2 internal storage. (Later you can put the stock layout back if you want to go back to Android.)
The steps for repartitioning are:
Download the 'Repartition: System=1GB, Data=14GB, eMMC=8MB, /preload=7MB' or the 'Repartition: System=1GB, Data=4GB, eMMC=7GB, /preload=0.5GB' .zip file and put into the external SD card. (The difference between these two is explained down at the New partition layout section
Then boot into TWRP and flash the zip as any other zip file. The script first will warn you that it cannot do the partitioning with mounted partitions and it also copies the script itself into /tmp. You just simply need to flash the copied version from /tmp and that will do the trick. The script will format the new partitions accordingly, so once it is completed you can go ahead with the next step.
4. Still in recovery, flash the CM12.1 image
5. Still in recovery, flash Sailfish Os image
6. Still in recovery, flash twrp2.8.7.img to recovery partition
7. Still in recovery, flash kernel*.img to boot partition (this step is not required since sfos 4.4, kernel is installed by flashing the zip file)
8. Reboot
9. Enjoy the latest (4.4.0.68) Sailfish OS on your i9100.
You will need patience as the first boot will take for a while. Then you can go through the initial Sailfish OS set up.
This Sailfish OS Android HAL based on CM 12.1.
Downloads:
kernel12_mtp.img for Sailfish OS 3.2.1.20
kernel33016.img for Sailfish OS 3.3.0.16
kernel34024.img for Sailfish OS 3.4.0.24
kernel41024.img for Sailfish OS 4.1.0.24
kernel43015.img for Sailfish OS 4.3.0.15
twrp2.8.7.img for i9100
CM 12.1 for i9100
Sailfish OS 3.2.1.20 for i9100
Sailfish OS 3.3.0.16 for i9100
Sailfish OS 3.4.0.24 for i9100
Sailfish OS 4.1.0.24 for i9100
Sailfish OS 4.3.0.15 for i9100
Sailfish OS 4.4.0.64 for i9100
Sailfish OS 4.4.0.68 for i9100
Sailfish OS 4.4.0.72 for i9100
Odin v1.83
AOSP-LP-Kernel+_25-08-2015_TWRP-2.8.7.0.tar
Repartition: System=1GB, Data=14GB, eMMC=8MB, /preload=7MB
Repartition: System=1GB, Data=4GB, eMMC=7GB, /preload=0.5GB
Stock partition pit file
kernel07_flatpak (kernel with Flatpak support. Flatpak install/usage instructions.)
Some useful tips:
Low power mode aka ambient mode (in Fingerterm):
Code:
mcetool --set-low-power-mode=enabled
Disable lock screen animation (in Fingerterm):
Code:
mcetool --set-lockscreen-animation=disabled
Some useful patches:
Patchmanager 3.0
More folder icons
Operator name at bottom (Stopped working on 3.3.0.16)
Silica mail (transparent background) - Well documented here
Apps from Openrepos
Apart from the Jolla store there are plenty of other, community-made apps in Openrepos. There is a user-friendly app to install/remove apps from this source called Storeman. It can be downloaded and install from this location: Storeman
Debug/login/troubleshooting:
In Ubuntu, connect USB cable. telnet 192.168.2.15 2323 or SSH [email protected].
Notes:
On Sailfish OS, as it is a Linux system, you cannot install/run any android apps.
How to make a backup/restore with TWRP:
Now the old clunky method is no longer needed. Once you flashed the twrp2.8.7.img to the recovery partition you can boot into TWRP with the usual button combination (Hold buttons: Power on + Home + Volume up) and can make backup/restore.
Instructions for Bluetooth (On Sfos 4.3, BT works normally, don't need this magic)
BT works however turning it on/off is not as user friendly as I hoped. Here is a little instruction/troubleshooting.
Turn BT on (It only works from Settings/Bluetooth!!!!! DON'T try from TOP MENU!!):
If BT hasn't turned on since last boot:
go to Settings/Bluetooth
tap on the dot next to the Bluetooth option
If BT has turned on at least once since last boot:
go to Settings/Bluetooth and tap on the dot next to the Bluetooth option
go back to Settings
go to into Settings/Bluetooth again
tap on the dot next to the Bluetooth option (if it is not turned on repeat from Step 2! Eventually, BT should turn on.)
Turning BT off: Go to Settings/Bluetooth and tap on the white dot next to the Bluetooth option.
Notice: Never try to tap on the white dot twice without going back to the main menu of Settings.
Never try to turn BT on from Top Menu.
However, if you accidentally did any of these BT cannot be turned on again unless you:
reboot the device (this is the easiest) or
in a command line as root issue the following command 'systemctl restart bluetooth-rfkill-event.service' (this will restart the bluetooth-rfkill-event service)
I am not sure how pairing works with different devices.
New partition layout
I mentioned that I tried this Sailfish OS installation with the stock partitions and with another what created for Android 7.1.2. With the stock partitions however was a bit more sluggish than the other one. No wonder as in the stock partitions the /system has only 0.5GB and the /data has only 2GB storage and the rest 12GB is the separate internal storage (eMMC). In Sailfish the entire os (rootfs) including all directories (like /home) live on the /data partition so the 2GB was a bit tight. (The OS itself consumes about 1GB so not much left for apps and other stuff.)
With the other partition layout, the picture was a bit better as the /system had 1GB, the /data got 4GB and the rest 9GB remained for the internal storage. But the partition where the OS lives was separated from the 9GB partition. When I installed a few apps and copied some big files into the /home, I felt the limitation very soon.
Although this layout was sufficient for android but not good enough for Sailfish.
Therefore I have created my own partition table where I restructured the sizes accordingly to my need. (The lanchon repit zip file is available in the download section.)
In this new layout I gave 1GB for the /system (the prior 0.5GB was also fine as the CM12.1 base consumed only 400MB which let a 100MB free space, but I thought that might be not enough in the future so I have chosen 1GB here), I gave only 8MB for the internal storage (eMMC which is mounted into /android directory in this rom), and this made me possible to gave all the rest 14GB to the /data partition. So basically the Sailfish apps and /home can utilize the entire internal storage.
As an extra, on the S2 there is a 0.5GB /preload partition which is hidden and unused by default. In my partition setup I set 7MB to this and the rest almost 0.5GB is also added to the /data.
Go back to stock partitions
In case you would like to do this, you can download the stock partition pit file from the download section.
For this use Odin v1.83 which is also in the download section.
The steps are:
Boot the device into download mode and connect to the PC.
Open Odin v1.83 and tick the 'Re-partition' checkbox at the Option.
Then click on the PIT button and select the downloaded stock pit file.
Then click on the PDA button and select the downloaded TWRP (AOSP kernel) file.
Then click on start.
Done. You need to boot into TWRP and wipe all partitions (system, data, emmc) then you can install the stock rom back. (or if you select the stock rom at PDA instead of the AOSP kernel, it will do the repartition and install the stock rom as well. In this case, you don't need to wipe anything and the device will reboot into the stock Android at the end.)
Changelog:
15.02.2022
=========
General advice:
Patience! All (except camera) apps do start and work but they do need time. This is true for websites. When you clicked on something, wait patiently, eventually, it will start/load.
Work:
Same as previously
Improvement: Stock browser stable and works!
Do not work:
The camera app crashes the device into reboot.
03.09.2021
=========
Work:
Same as previously
Bluetooth does work, but once it is off, needs to be toggled a few times in Settings to make it turn on again.
14.06.2020
=========
Work:
Same as previously + Mobile data is fixed! (To make it work: change Protocol to IP in Settings/Mobile network/Data access point.)
Bluetooth doesn't work, it is still WIP
Do not work:
Same as previously
06.05.2020
=========
The latest version of Sailfish OS 3.3.0.16 is available to download. This requires a different kernel. Both of these can be found in the download section.
Note: With the new version the patch that displays the provider logo at the bottom on the lock screen stopped working. This issue is not related to the OS. The owner of the app should fix it.
Update: In openrepos Kodi is fixed for SFOS 3.3.0.16!
29.04.2020
=========
Work:
Screen
Touch
IMEI number is detected
Sensors (GPS, Rotation, Acceleration, Gyroscope, Magnetometer, Light & Proximity)
Wifi
MTP
Bluetooth (instruction is above)
Calls incoming/outgoing
Messages incoming/outgoing
External SD card detected and mounted to /run/media/nemo/_sdcard_name_ (where _sdcard_name_ is name of the sd card when it was formatted like 7C97-785B)
Internal SD card is mounted to /android
Pixel ratio and icons set to 1.00 (Can be changed to 0.82 which is more appropriate for the device's screen. to do this as root run the 'kimmoli-diyicons.sh 0.82' command. It will fail to install imagemagick but will set the ratio to 0.82 and as we have all icons in place it will work.)
Audio is routed to headphone if that presents
Camera front/rear (only for taking pictures)
Jolla store
findutils is installed by default (updatedb and locate commands work out of the box)
Torch
the charging icon does work properly, however, there is a little delay
can boot into TWRP recovery with the usual button combination (hold buttons: Power on + Home + Volume up)
kernel and recovery .img can be flashed from TWRP (no need for PC to flash Sailfish OS, kernel and recovery)
Low Power Mode (AKA "sneak peek" or "ambient display") works (install instruction is in this post)
The softkeys (each side of the home button) work as notification leds
Do not work:
Mobile data (WIP)
Video recording (It doesn't really work in other 3.x versions either. See my test results here.)
There is an extra little issue that is a delay in screen refresh which is related to how vsync is handled in v10 backend in qt5-qpa-hwcomposer-plugin. I managed to improve this but there is a little delay still. Probably this is the reason why we need to jump back to Settings every time before trying to turn BT on, but I am not sure.
04.04.2020
=========
Work:
Same as previously + Softkeys are used as notification leds
Bluetooth doesn't work, it is still WIP
Do not work:
Same as previously
23.03.2020
=========
Work:
Same as previously + with 'kernel12_mtp' the MTP works!
Bluetooth partially works (to switch on BT requires a reboot or issue a command manually, it is still WIP)
Do not work:
Same as previously
25.02.2020
=========
Work:
Same as previously + with 'kernel07_flatpak' the Low Power Mode (AKA "sneak peek" or "ambient display") works! (install instruction is in this post)
Do not work:
Same as previously
23.02.2020
=========
Work:
Same as previously + but from now on you don't need PC and heimdall to flash kernel and twrp
Do not work:
Same as previously
19.02.2020
=========
Work:
The same as listed earlier + with the new kernel (kernel06) I attached you can boot into TWRP with the usual button combination (hold buttons: Power on + Home + Volume up)
Do not work:
Same as previously except the TWRP/Sailfish OS boot which has fixed.
08.02.2020
=========
Work:
Screen
Touch
IMEI number is detected
Sensors (GPS, Rotation, Acceleration, Gyroscope, Magnetometer, Light & Proximity)
Wifi
Calls incoming/outgoing
Messages incoming/outgoing
External SD card detected and mounted to /run/media/nemo/_sdcard_name_
(where _sdcard_name_ is the name of the sd card when it was formatted like 7C97-785B)
Internal SD card is mounted to /android
Pixel ratio and icons set to 1.00 (can be changed, I set 0.82 which is more appropriate for the device's screen resolution see the download section)
Audio is routed to headphone if that presents
Camera front/rear (only for taking pictures)
Jolla store
findutils is installed by default (updatedb and locate commands work out of the box)
Torch
Do not work:
Mobile data
Bluetooth (the bt driver is in the kernel, so in theory, with some config file changes on the device it can work)
MTP
Video recording (It doesn't really work in other devices with CM12.1 base.)
Screen delay in refresh (related to how vsync is handled in v10 backend in qt5-qpa-hwcomposer-plugin)
the charging icon doesn't work properly: when the device is not on charger still shows it's charging (when I unplug the cable the message appears: "Charging..."
cannot boot into TWRP recovery (See Notes above)
Battery life:
In my experience the battery life is good. On standby, it can survive 10 days. (Almost 11.) I have checked once or twice daily during this period.
{
"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"
}
Pictures:
App drawer
Top menu
Settings
About product
In case somebody missed these I would like to highlight some improvements since day 1:
Now both the kernel and twrp can be flashed as an .img from twrp (no need for PC and heimdall anymore)
Plus I uploaded a kernel with Flatpak support
With kernel07_flatpak, I have installed Flatpak and Angelfish but got an error when started Angelfish.
It looks like this is a limitation of the old kernel, but there might be a workaround.
I'll keep you posted.
With kernel12_mtp, MTP works. (and bluetooth partially)
The soft keys each side of the home button are used as notification leds. As this device doesn't have leds, the softkeys can be re-used as "leds". They do blink if the device is fully charged or there is an unread incoming text message. When the device is on charger they are on, otherwise both of them are off.
Can you post your sources? I'm interested in getting an I9100 as my new phone, and was considering a port and I'm happy to see you've already done all the leg work and then some!
Also about the kernel on this phone, I've been trying to port to a tablet with weird kernel images, can you run "file (path to android base kernel image)" - if it says ForPro FPT or similar I will be very very interested in how you got this phone to boot into rootfs. Very interested in the progress you've made though :3 Thanks for the awesome rom!
Galaxyninja66 said:
Can you post your sources? I'm interested in getting an I9100 as my new phone, and was considering a port and I'm happy to see you've already done all the leg work and then some!
Also about the kernel on this phone, I've been trying to port to a tablet with weird kernel images, can you run "file (path to android base kernel image)" - if it says ForPro FPT or similar I will be very very interested in how you got this phone to boot into rootfs. Very interested in the progress you've made though :3 Thanks for the awesome rom!
Click to expand...
Click to collapse
Sorry for delay in my reply.
The necessary repos in github are:
local manifest
dhd (in here the dhd submodule has to be refreshed from mer-hybris repo upgrade-3.2.1 branch)
droid-hal-i9100
droid-hal-version-i9100
android_device
kernel
The file (path to android base kernel image) command gives me: "Linux kernel ARM boot executable zImage (little-endian)"
A new image has been generated and can be downloaded. This one includes the patch of reusing the two softkeys (each side of the home button) and they do work as a notification leds!
Currently I am working on the mobile data and bluetooth (this latter partially works but is not reliable yet).
You're a g! I just bought an i9100M (different radio ).
I do recall ofono being unfriendly towards older RIL versions, galaxy nexus afaik is unfixable in 2.0+. However, if you have any service that is exciting! I can't wait to setup my environment and play around with this! If i9100M has a different partition layout/mount points (you know how samsung is) I will blow my brains out. How is camera working? Does this image include gstreamer/droidmedia?
You've probably got this sorted way better than I could hope to sort it! I'm shocked this doesn't have more replies.
EDIT: I noticed you have a complex patch for the pixel ratio. Have you tried just setting it in your patterns?
Galaxyninja66 said:
You're a g! I just bought an i9100M (different radio ).
I do recall ofono being unfriendly towards older RIL versions, galaxy nexus afaik is unfixable in 2.0+. However, if you have any service that is exciting! I can't wait to setup my environment and play around with this! If i9100M has a different partition layout/mount points (you know how samsung is) I will blow my brains out. How is camera working? Does this image include gstreamer/droidmedia?
You've probably got this sorted way better than I could hope to sort it! I'm shocked this doesn't have more replies.
EDIT: I noticed you have a complex patch for the pixel ratio. Have you tried just setting it in your patterns?
Click to expand...
Click to collapse
I am not sure what you d understand under 'any service' but except the mobile data, everything else works fine (calls in/out, texts in/out).
I don't know the difference between the i9100 and i9100m but on the internet you probably can find something about it.
One suggestion, before you start porting, install an android onto and boot into that and note the mounting points. This can save a little time when you need to set the fixup_mountpoints in hybris-boot.
The camera works but only for pictures. The video recording doesn't work. I think this is down to the cm12.1 base what I used for my port. I think gstreamer/droidmedia are there but am not sure.
I think the reason why this doesn't get more hype because this is a very old device and except some old fashioned folks like us, not many are using anymore. I don't mind it because this is my hobby. I am going through a to-do list until all I wanted works.
Currently, as the new version 3.3.0.14 is out) I am working on to update my port to 3.3.0.14. Unfortunately currently there is no OTA but hope eventually it will be sorted.
Changing the pixel ratio is not essential as the default 1.0 is ok-ish. I have found the 0.82 better so I included the icons into my image. As the script (kimmoli-diyicons.sh) is also included, we just need to run one command as root. I may try to set the 0.82 out of the box but currently it is not my to priority. As I will need to re-build everything for 3.3.0.14, I will try to set 0.82 in the pattern file.
Please keep me posted with your progress.
edp17 said:
The camera works but only for pictures. The video recording doesn't work. I think this is down to the cm12.1 base what I used for my port. I think gstreamer/droidmedia are there but am not sure.
Click to expand...
Click to collapse
You'd 100% know if you built gstreamer, it's specified in the middleware section iirc and you have to uncomment it from your patterns. I hope it's easier to build nowadays. Also I noticed your port wasn't on the mer-wiki, if I remember my login is it okay if I add it :3 ?
EDIT: https://wiki.merproject.org/wiki/Adaptations/libhybris#Samsung - I added it to the bottom. creditted you in the edit note. you can create an account on the mer bug wiki and use it to edit the tables. I'll also be closely following this and editting it to match your progress. Tell me if you'd like any values changed!
Galaxyninja66 said:
You'd 100% know if you built gstreamer, it's specified in the middleware section iirc and you have to uncomment it from your patterns. I hope it's easier to build nowadays. Also I noticed your port wasn't on the mer-wiki, if I remember my login is it okay if I add it :3 ?
EDIT: https://wiki.merproject.org/wiki/Adaptations/libhybris#Samsung - I added it to the bottom. creditted you in the edit note. you can create an account on the mer bug wiki and use it to edit the tables. I'll also be closely following this and editting it to match your progress. Tell me if you'd like any values changed!
Click to expand...
Click to collapse
I remember that I built gstreamer and un-commented the related stuff in the pattern file. I don't know whether easier to build now because I don't know how difficult it was before. I only can compare this project against my hammerhead one a few months earlier. For the hammerhead I needed to build the image with MIC, now the rpm/dhd/helpers/build_packages.sh command does everything for you. (For this you need to export the RELEASE, EXTRA_NAME values in your .hadk.env)
Unfortunately I still don't have OBS account so I couldn't add this device into the wiki. Thank you for doing that! Unfortunately new account creation on the mer bug wiki is restricted at the moment.
I have checked the wiki you have added and if you don't mind I would like you to amend a few things:
LED works (the two softkeys have repurposed as notification leds)
GPS works
Sensors Gyro and Magnetometer both work
(I need to double check the RTC alarm and USB net.)
I updated the page. I was going to set up my build env but seeing your row in the adaptations page made me realise you're so far along, and there isn't anything I could really do to push things forward by much. Once you get data and camera working this is pretty much one of 2 daily driver stable samsung sfos ports. Congrats :3 !
Galaxyninja66 said:
I updated the page. I was going to set up my build env but seeing your row in the adaptations page made me realise you're so far along, and there isn't anything I could really do to push things forward by much. Once you get data and camera working this is pretty much one of 2 daily driver stable samsung sfos ports. Congrats :3 !
Click to expand...
Click to collapse
Thank you for the update and for the congrats but I think it is only partially my merits. I probably couldn't done this without the help of sailfishos-porter guys.
As I mentioned in the main comment, I am using my S2 with this image on it as a secondary phone already. Mobile data is not crucial as my main phone can be a hotspot and with my S2 I can connect to it via wifi. Of course this doesn't stop me trying to make that work. (The BT was almost done but I then broke something.)
The camera is a different story. Afaik the video recording generally is broken in the CM12.1 base that I chosen for this device. (That doesn't work on my hammerhead which is also using CM12.1 base.) So I think that will remain outstanding unless I try to port with a different android base.
I think will stop with this for while because the new version (3.3) is out soon and would like to upgrade to it first, then continue working on the missing bits.
Video recording works in the latest scm12.1 snapshot (YOG7D). I wish they hadn't tanked the old etherpad faq, I swear I saw something about hybris 12.1 specific video recording stuff.
If I can find another sub 20 USD i9100 I am definitely working on this, but since my i9100m is my daily driver and dualbooting isn't as easy as with other devices (espescially since YOG7D doesn't have isorec committed ). Thanks for getting so much done though, You have no idea how much it means to me that Sailfish OS is available for our device, and so stable too! :laugh:
Galaxyninja66 said:
Video recording works in the latest scm12.1 snapshot (YOG7D). I wish they hadn't tanked the old etherpad faq, I swear I saw something about hybris 12.1 specific video recording stuff.
If I can find another sub 20 USD i9100 I am definitely working on this, but since my i9100m is my daily driver and dualbooting isn't as easy as with other devices (espescially since YOG7D doesn't have isorec committed ). Thanks for getting so much done though, You have no idea how much it means to me that Sailfish OS is available for our device, and so stable too! :laugh:
Click to expand...
Click to collapse
I think the video recording also works in cm12.1 on the android side, but the problem is a, between the android and Sailfish or b, on the Sailfish side. I am not sure but when I tried to fix it on the hammerhead (same cm12.1 base) I was told the recording was broken in general with cm12.1 base. I'll see how it works (what I can do about it) after Sailfish 3.3 is out.
Have you thought about to purchase a cheap android phone to use as daily driver and using the i9100m for your Sailfish project? (You probably can get a decent second hand android phone for sub 20 maybe with better spec than the i900.)
Thanks again for the kind words. This phone (the S2) is my favorite old friend. It is indestructible . I have soft bricked so many times and managed to install many other OS but as couldn't find Sailfish OS, so I though worth a try to port. And with support of the Sailfishos-porters guys, my dream became real :good: .
Sailfish
Wow, great. I installed and the system works! Bluetooth does not work after installing the packages, but bluetooth-rfkill-event- * are not installed (error). There are few programs in the system, however. Especially browsers, the standard one hangs up (maybe there is a third-party?). Slightly slows down, but bearable.
By the way, are you not working with @linusdan? It also seems to be working on the port github com /sailfish-i9100 (link)
Sorry no link rights.
P/s By the way, I saw on the postmarket wiki site for i9100 about working kernels for our device. Available: kernel version 4.2 or mainline kernel
S2UserRU said:
Wow, great. I installed and the system works! Bluetooth does not work after installing the packages, but bluetooth-rfkill-event- * are not installed (error). There are few programs in the system, however. Especially browsers, the standard one hangs up (maybe there is a third-party?). Slightly slows down, but bearable.
By the way, are you not working with @linusdan? It also seems to be working on the port github com /sailfish-i9100 (link)
Sorry no link rights.
P/s By the way, I saw on the postmarket wiki site for i9100 about working kernels for our device. Available: kernel version 4.2 or mainline kernel
Click to expand...
Click to collapse
I am glad you managed to install it. Have you tried to re-partition the internal memory as I advised?
Yeah, the bt and mobile data is still WIP status. Hopefully will have some time to complete them soon.
For the browser, the native one doesn't hang for me. You can try to look for and install one from the openrepos. (I suggest to install the Storeman as you will find more useful apps for Sailfish OS.)
I don't know linusdan but have seen he has checked this post already. Hope he also found it useful.
I am aware of the postmarketos for the S2 and tested it on my S2. At that time (about a year ago) there was no mainline linux kernel option for the S2. Unfortunately the mainline kernel doesn't help with Sailfish because the Samsung proprietary blobs are missing from there. This means Sailfish wouldn't work. It needs the drivers from the Android layer.
S2UserRU said:
Wow, great. I installed and the system works! Bluetooth does not work after installing the packages, but bluetooth-rfkill-event- * are not installed (error). There are few programs in the system, however. Especially browsers, the standard one hangs up (maybe there is a third-party?). Slightly slows down, but bearable.
By the way, are you not working with @linusdan? It also seems to be working on the port github com /sailfish-i9100 (link)
Sorry no link rights.
P/s By the way, I saw on the postmarket wiki site for i9100 about working kernels for our device. Available: kernel version 4.2 or mainline kernel
Click to expand...
Click to collapse
I forgot to mention that there should be a folder '/edp17packages/bluetooth' where you can find the missing packages for the bt. Once you installed it, probably only need to tweak some config files and need to create some scripts. I currently started working on it.