Related
My goal for this thread is to gather as much info for the BLU Life One X 2016.
Specs
Screen: 5.2", 1080 x 1920 pixels, ~424 ppi, Gorilla Glass 3
Memory: 2 GB RAM, 16 GB storage, microSD slot (up to 64GB)
Camera: 13 MP rear, 5 MP front, LED flash front & rear, [email protected] video
Battery: Li-Ion 2900 mAh
Chipset: Mediatek MT6753
CPU: Octa-core 1.3 GHz Cortex-A53
GPU: Mali-T720
Model: L0070UU
Links & Other General Resources
BLU Products
Amazon: Black - White
GSMArena
BLU Products Development Team (Google+)
L0070UU User Manual
ClanGSM claim to have firmware files for our phone but it would cost $$$ to download: / mnt / data / ftp / Flashes / BLU / Life One X / L0070UU /
Similar Phones
Wiko Fever (GSMArena)
Micromax Canvas 5 (GSMArena)
XOLO Black 1X (GSMArena)
Elephone P8000 (CM12.1) and P6000 Pro
Quantum Go 4G (PhoneMore)
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Note: While I use a variety of operating systems on a regular basis everything here will be Windows 10 focused.
ADB & Fastboot
Before doing most things mentioned below you will need "adb" and "fastboot" installed. Two of your options are to install the Android SDK Tools or the Minimal ADB and Fastboot tool. If you are somewhat new to this I highly recommend the second one. Go here, download the latest version (1.3.1 as of this writing), and install it. When setup is complete you should have an icon for the Minimal ADB and Fastboot tool.
Note: I highly recommend you add "C:\Program Files (x86)\Minimal ADB and Fastboot" to your PATH variable in Windows. This way you can open a Command Prompt anywhere and use adb or fastboot.
Drivers
I recently setup a 5th gen Kindle Fire 7" tablet on my Windows 10 desktop. Because the BLU Life One X 2016 and the Kindle Fire are similar enough it just worked. To use the Amazon drivers you can find them on this page: https://developer.amazon.com/public...etting-up-your-kindle-fire-tablet-for-testing. The direct link is https://s3.amazonaws.com/android-sdk-manager/redist/kindle_fire_usb_driver.zip. Extract the zip file and then run KindleDrivers.exe.
Unlock Bootloader, Install Custom Recovery, and Install Root
Note #1: All credit for this guide goes to manos78's post for rooting the Wiko Fever!!! You can check it out here.
Note #2: I use Windows 10 on every PC I own. I assume Windows 7 and 8 should work just fine but cannot test that.
Note #3: The following assumes you have setup ADB and the proper drivers before beginning. I will try to detail that at a future time.
Note #4: Your phone will be completely erased. If there is anything you want to save do so beforehand.
1) Unlock Bootloader
Power on the phone and skip through all of the setup options
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly
Type fastboot oem unlock
Press Volume Up to say Yes and wait for this to finish
Type fastboot getvar all and look for (bootloader) unlocked: yes
Type fastboot reboot
You should see your phone reboot a couple times as it erases the phone
2) Install Custom Recovery
Note #1: We will flash a version of CWM or TWRP that was built for a Wiko Fever as they appear to be fully compatible with the BLU Life One X 2016. Go to this thread and download the latest CWM (http://www.sendspace.com/file/4g87bj) or TWRP (http://www.sendspace.com/file/y4jel8). Extract the img file. Again, many thanks to manos78 for CWM and hanuma for TWRP!!!
Power on the phone
You can configure your phone now or just skip through all of the setup options and do that later
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt to wherever you extracted the .img file
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly
For CWM type fastboot flash recovery recovery-custom-wiko-fever.img or for TWRP type fastboot flash recovery TWRP_WikoFever_2.8.7.0.img
Type fastboot reboot
Note: If your phone does not reboot then just hold the power button until it turns off. Hold the power button again until it turns back on.
3) Install Root
Note: While there are newer beta versions of the SuperSU app I am not sure if they will work properly on our stock rom. You can test one of those out and report back but I would recommend you do a full backup beforehand.
Download BETA-SuperSU-v2.52.zip and save it to the phone's internal memory or an inserted microSD card
Plug the phone in to your PC
Open a Command Prompt
Type adb reboot recovery
You should now be in CWM. Go to Install zip, find BETA-SuperSU-v2.52.zip, and install it
When it finishes go to Go Back -> Reboot Phone -> No
Once the phone boots up launch SuperSU and configure it as you like
Xposed
Download the latest version of Xposed for sdk22 and arm64 from here. As of this writing it is xposed-v79-sdk22-arm64.zip. Also download XposedInstaller_3.0_alpha4.apk and xposed-uninstaller-20150831-arm64.zip (just in case).
Reboot into CWM or TWRP and do a full backup
Install xposed-v79-sdk22-arm64.zip and then reboot
Cross your fingers and hopefully your phone will start properly. Mine rebooted like five times during the "Android is starting" step but finally finished.
Once your phone boots up install XposedInstaller_3.0_alpha4.apk
ViPER4Android
ViPER4Android adds audio effects to your Android device and is beloved by many. First we will install SELinuxModeChanger and then ViPER4Android. Special thanks to Tha Watcher for his original write-up here.
1) SELinuxModeChanger
Go to the SELinuxModeChanger page on F-Droid, download the latest version (3.2 as of this writing) or use this direct link, and save it to your Desktop
Launch Minimal ADB and Fastboot and type adb install %USERPROFILE%\Desktop\com.mrbimc.selinux_42.apk
On the phone you may see a prompt saying Installation Blocked. If so, click the little triangle and tap Install anyway (unsafe). If you see a failure just do it again and it should work.
Launch the SELinuxModeChanger app on your phone, grant it root permissions, and click Permissive
Note: If you have any issues with SELinuxModeChanger then head over to the XDA thread.
2) ViPER4Android
Download the latest version in zip format from here and extract ViPER4Android_FX_A4.x.apk to your Desktop
Launch Minimal ADB and Fastboot and type adb install %USERPROFILE%\Desktop\ViPER4Android_FX_A4.x.apk
Launch the ViPER4Android app on your phone, click Yes when prompted, click Super Audio Quality, and then click OK
Grant root access when prompted
Click OK
Reboot your phone
Note: Once your phone reboots you can start configuring ViPER4Android. I cannot really help much with that but feel free to look over the official XDA thread or their Settings Explained page on the official website.
Engineering Mode
Note: If I were you I would not change anything unless you absolutely know what you are doing!
I cannot seem to get the phone codes to work. You can install the MTK Engineering Mode app from the Google Play Store.
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Frequently Asked Questions
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
MTK Droid Tool
MTK SP Flash Tool
Latest Version: 5.1548.00.000
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Q: How can I tell if my model is the BLU Life One X 2016?
A: Go here and see if it is the same model.
Q: When I try to use adb root I get the following error: adbd cannot run as root in production builds
A: You can purchase and install [root] adbd Insecure by Chainfire. Once installed, launch the app, grant it root access, and then check Enable insecure adbd and Enable at boot
Q: How do I (re)mount /system as read-write?
A: Install [root] adbd Insecure as mentioned above, open a Command Prompt, type adb root, and then adb remount rw
Q: How can I disable the audio that plays when starting up or shutting down my phone?
A: Using a file explorer with root access, or an adb shell, delete or rename (with .bak at the end) /system/media/bootaudio.mp3 and /system/media/shutaudio.mp3 and then reboot your phone.
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Reserved #4
Have you tried porting the Elephone rom for the Blu? They both have a MT6753, so from what I understand from reading on XDA it might work. You might need to make changes suggested at http://forum.xda-developers.com/showthread.php?t=2701283.
Has anyone been brave enough to try this yet?
---------- Post added at 02:16 AM ---------- Previous post was at 02:12 AM ----------
I'm receiving my phone tomorrow so i might be the guinea pig...lol
Did this last night on my phone. Most difficult part for myself was finding the correct drivers as this is my first mediatek device. Ended up being my fifth attempt that had the correct set.
After I had the drivers it was extremely similar to a nexus process.
Do you have a link to the drivers
Sent from my 6045X using Tapatalk
I must inform you that I am still running good ol' Windows 7 so there's that.
All credit on my end comes from [Tutorial] Flash/Root/update elephone P8000 by vetkak and the first step with the link. Its not a real link, but a copy and past of the mega.co link had the proper drivers.
If you're on Windows 10 there is a separate thread out there somewhere with instructions for that.
OK thanks
Sent from my 6045X using Tapatalk
I feel like it needs mention that after flashing the recovery (I used the TWRP flavor) that after the fastboot command you need to immediately power off the phone, instead of rebooting, then do the volume up + power button press to get to the custom recovery.
SCrid2000 said:
Have you tried porting the Elephone rom for the Blu? They both have a MT6753, so from what I understand from reading on XDA it might work. You might need to make changes suggested at http://forum.xda-developers.com/showthread.php?t=2701283.
Click to expand...
Click to collapse
Unfortunately the guy that was bringing up the elephone p8000 has sold it and subsequently not be supporting it any longer. I'm happy enough there is custom recovery options and root. An AOSP ROM would be nice, but naturally the custom gestures would be lost.
jmcneil919 said:
Has anyone been brave enough to try this yet?
Click to expand...
Click to collapse
I did but from the original Wiko Fever thread instructions. I did this a couple of weeks before he actually posted this thread and I made my own instructions that I think are clearer and more concise than the Wiko thread; however, rogersa2k's guide is pretty thorough and easy to understand besides the following correction....
The fastboot reboot after flashing the custom recovery doesn't yield the same results, because when I did that it did NOT work! I corrected it by help from a comment by member yrude (and as hottcakes mentions above) and made my own instructions with the addition of adding the installation for Viper4Android. But I hesitate to post it on XDA as I don't want to step on any toes. However, I did post it on Google+, Amazon and GSMarena. If people want this alternate guide and notify me to post it, then I will. Otherwise, I'll keep it off XDA.
hottcakes said:
I must inform you that I am still running good ol' Windows 7 so there's that.
All credit on my end comes from [Tutorial] Flash/Root/update elephone P8000 by vetkak and the first step with the link. Its not a real link, but a copy and past of the mega.co link had the proper drivers.
If you're on Windows 10 there is a separate thread out there somewhere with instructions for that.
Click to expand...
Click to collapse
I was trying to using the link to download the driver, but the mega site asked for "decryption key" before I can download. Is there a key available to share? Thanks,
Tha Watcher said:
I did but from the original Wiko Fever thread instructions. I did this a couple of weeks before he actually posted this thread and I made my own instructions that I think are clearer and more concise than the Wiko thread; however, rogersa2k's guide is pretty thorough and easy to understand besides the following correction....
The fastboot reboot after flashing the custom recovery doesn't yield the same results, because when I did that it did NOT work! I corrected it by help from a comment by member yrude (and as hottcakes mentions above) and made my own instructions with the addition of adding the installation for Viper4Android. But I hesitate to post it on XDA as I don't want to step on any toes. However, I did post it on Google+, Amazon and GSMarena. If people want this alternate guide and notify me to post it, then I will. Otherwise, I'll keep it off XDA.
Click to expand...
Click to collapse
Pls post yours here. I saw your Amazon comment and tried to follow it. Everything seemed to work till I run "fastboot oem unlock" then the PC just displays "Waiting for device response...." and my BLOX never showed any response on screen. I suspected that I did not have the driver for this particular type cellphone device. Thanks,
clu1688 said:
Pls post yours here. I saw your Amazon comment and tried to follow it. Everything seemed to work till I run "fastboot oem unlock" then the PC just displays "Waiting for device response...." and my BLOX never showed any response on screen. I suspected that I did not have the driver for this particular type cellphone device. Thanks,
Click to expand...
Click to collapse
I appreciate that but the only way I'd post it in this thread is if the OP says it's fine. I do not like hijacking or taking over other people's threads.
It sounds like ADB is actually not loaded or working on your computer or otherwise you wouldn't get that message. I could be wrong, though. To test to see if it is indeed working and drivers are properly loaded, what does it respond when you type: adb devices
SCrid2000 said:
Have you tried porting the Elephone rom for the Blu?...
Click to expand...
Click to collapse
Not yet, but I do plan to try to start with that. It's nice that Elephone released the source code for the P8000 so that could help as well. If I ever get to this I will need lots of help.
jmcneil919 said:
Has anyone been brave enough to try this yet?
Click to expand...
Click to collapse
Everything that *I* post in the OP will be something that I tested on my own device first unless I specifically mention otherwise.
hottcakes said:
I feel like it needs mention that after flashing the recovery (I used the TWRP flavor) that after the fastboot command you need to immediately power off the phone, instead of rebooting, then do the volume up + power button press to get to the custom recovery.
Click to expand...
Click to collapse
I will add a note about that but some of us had issues so I chose the alternate method that has worked for me the first time every time.
Hello all XDA Developers and site visitors,
I recently picked up a Junsun A931 Rear View Mirror on AliExpress and didn't see any forums on it. So, I decided to write my own about how I managed to gain root and install Magisk. Links to all the files will be included.
This works for Junsun's A930/A931 with Android 5.1. The process will probably work for other Rear view Mirrors with MTK chips, you will need to have access to the boot.img and scatter file for your device.
**Disclaimer: Proceed at your own risk! Although this worked for me without issues, there is always a chance of bricking your devices/making your device unusable. I am not responsible for your device(s).
Instructions:
1. Install MTK Drivers provided.
**I only have the ones for Windows. Mac/Linux, I couldn't find any MTK drivers for you.
**If you have trouble installing drivers, try turning off "signed drivers" in Windows Recovery.
2. Attach device to computer via USB cable.
3. If computer doesn't recognize device when it's fully booted:
-Go to "Set Up"
-Slide over to "Other" tab
-Scroll down to "Version"
-Click on "Version" until it brings up a menu (Same principle as Developer Mode, except it pop's up a menu)
-Click on "USB Host"
-Select "USB Device" (the one that has "adb" in the description)
**If this doesn't work, then try switching USB ports on your computer. It only ever works on my USB 3.0 ports.
4. Install Kingoroot on PC.
5. Launch Kingoroot and let it recognize your device, then click "Root."
** This is only a temporary root. It will reset every time you shutdown/restart. If that's what you want, stop here. Otherwise, continue on.
PERMANENT ROOT:
6. Open your choice of ADB on your PC. (I used Minimal ADB and Fastboot)
-Type "adb devices" to see if your devices is recognized and listed.
-Type "adb install [location of magisk.apk on computer]"
**replace "[location of magisk.apk on computer]" with location of magisk.apk (provided in RootPack.zip). This can be done by just dragging the file into adb or you can type the address from Windows Explorer.
-Type "adb push [location of boot.img for device] /sdcard/download"
**replace "[location of boot.img for device]" with location of boot.img for YOUR DEVICE. USING A BOOT.IMG FOR A DIFFERENT DEVICE WILL MOST LIKELY RESULT IN YOUR DEVICE BEING BRICKED!!! That being said, I have provided the software for Junsun A930/A931 for Android 5.1. If you have a different device, you will need the boot.img for it.
-Type "adb install [location of file explorer apk]" or install an file explorer from the Playstore, etc.
**replace "[location of file explorer apk]" with file explorer of your choice. I used ES Explorer.
7. Now open Magisk on the Rear View Mirror. (Make sure you're either connected to WiFi or Data)
**Be sure to grant it SuperUser Permission from Kingo SuperUser.
- Click "Install" next to "Magisk is not installed"
- Click "Install" on propt that pops up
- Choose "Select and patch a file" option.
- Scroll down and click on Es Explorer (or the file explorer you chose)
- Now go into the "download" folder and click the "boot.img"
- Click the option "File way"
**The "Normal Android Way" option kept failing for me.
- Let this complete.
8. Go back into ADB on the PC
- Type 'adb pull "sdcard/download/magisk_patched.img" C:/Downloads'
**You can replace "C:/Downloads" with whatever location you want to pull the file to on your computer.
9. Launch SP Flash Tool on your PC (provided in RootPack.zip)
-Load Scatter File by clicking the "Scatter-loading" button next to "Scatter-loading File" in the "Download" tab.
**This can be found in the firmware that I've provided, IF you have the Junsun A930/A931. If you have a different device, load the scatter file for it, instead.
-Now unclick all the boxes.
-Now click the box for "location" on the "boot" aisle.
-Select the "magisk_patched.img" that we just made from C:/Downloads or wherever you saved yours. Click "Open."
-It should have now have put the location of your "magisk_patched.img" file in the "location" box and the box next to the "boot" aisle should now be selected again (If not, make sure it is. Also, that it is the only one selected)
-Now click on the "Download" button (with the Green Arrow) at the top.
-Hold the home button the Rear View Mirror and click "Restart" (be sure to keep the mirror connect to the computer via USB)
-Now let the bar at the bottom finish.
-When it's done, there will be a pop-up that says "Download OK"
-Your device will restart
10. In your Mirror, launch Magisk Manager.
-Congratulations! The Magisk Installed option should now be green and you should have permaroot! Enjoy!
**You can now uninstall Kingo SuperUser.
Links:
Root Pack: https://drive.google.com/open?id=11poc-Pr30J_aPmhVJktuqZx1H9fkX371
Firmware: https://drive.google.com/open?id=19zUz_piQ6aiO_uGCQTmKpC9ErAR5-4xZ
A BIG THANK YOU TO THE DEVELOPERS AT MAGISK, KINGOROOT, MINIMAL ADB AND FASTBOOT, MTK DRIVERS, SP FLASH TOOL, XDA, AND EVERYONE ElSE WHO ATTRIBUTED TO THIS THROUGH DEVELOPMENT OF PROGRAMS USED! IF THIS WAS HELPFUL, BE SURE TO THANK ALL OF THEM!
great tutorial, really appreciate it
locale?
Thanks
seeing the A930P mt6735 root here, reboot after root language becomes us and timezone becomes China
I think I'm back to the default, but if you change the language, time zone to Japan and then restart it, it will go back to the default again
Do you need to change settings with build props etc?
otan032 said:
Thanks
seeing the A930P mt6735 root here, reboot after root language becomes us and timezone becomes China
I think I'm back to the default, but if you change the language, time zone to Japan and then restart it, it will go back to the default again
Do you need to change settings with build props etc?
Click to expand...
Click to collapse
Hmm.. could you give me some more information? Did you install Magisk or just use the temporary root with KingoRoot?
You could probably edit the build.prop to get the correct results by changing the "en" to "jp" for Japanese (or the whatever region). However, I'm not sure why yours is resetting to default after reboot? Mine always retains the settings after restarting. So if you could give me a little more information, I'll see if I can figure out what's the problem.
Great write up! Thank you.
I ended up picking a diff model Junsun /w 2gb RAM and am having issues with the USB port:
aliexpress : /item/32844242296.html
It won't recognize any USB devices, so assuming the drivers are missing or it's disabled permanently somehow. This unit is not powered thru USB port, there are separate 12v +/- to hardwire in. I've tried multiple USB cables as well.
I tried USB sticks for storage, but my actual intent is to hook up a USB DAB+ antenna like I'm using on another vehicle's Android
HeadUnit:
aliexpress: item/33003465623.html?spm=a2g0s.9042311.0.0.5ad74c4dUcy6j9
I just need basic USB drivers and 5V output on the USB port, any ideas on how to get this working or add drivers onto the existing ROM etc.?
Thanks!
iamrance.asa said:
Hello all XDA Developers and site visitors,
I recently picked up a Junsun A931 Rear View Mirror on AliExpress and didn't see any forums on it. So, I decided to write my own about how I managed to gain root and install Magisk. Links to all the files will be included.
This works for Junsun's A930/A931 with Android 5.1. The process will probably work for other Rear view Mirrors with MTK chips, you will need to have access to the boot.img and scatter file for your device.
**Disclaimer: Proceed at your own risk! Although this worked for me without issues, there is always a chance of bricking your devices/making your device unusable. I am not responsible for your device(s).
Instructions:
1. Install MTK Drivers provided.
**I only have the ones for Windows. Mac/Linux, I couldn't find any MTK drivers for you.
**If you have trouble installing drivers, try turning off "signed drivers" in Windows Recovery.
2. Attach device to computer via USB cable.
3. If computer doesn't recognize device when it's fully booted:
-Go to "Set Up"
-Slide over to "Other" tab
-Scroll down to "Version"
-Click on "Version" until it brings up a menu (Same principle as Developer Mode, except it pop's up a menu)
-Click on "USB Host"
-Select "USB Device" (the one that has "adb" in the description)
**If this doesn't work, then try switching USB ports on your computer. It only ever works on my USB 3.0 ports.
4. Install Kingoroot on PC.
5. Launch Kingoroot and let it recognize your device, then click "Root."
** This is only a temporary root. It will reset every time you shutdown/restart. If that's what you want, stop here. Otherwise, continue on.
PERMANENT ROOT:
6. Open your choice of ADB on your PC. (I used Minimal ADB and Fastboot)
-Type "adb devices" to see if your devices is recognized and listed.
-Type "adb install [location of magisk.apk on computer]"
**replace "[location of magisk.apk on computer]" with location of magisk.apk (provided in RootPack.zip). This can be done by just dragging the file into adb or you can type the address from Windows Explorer.
-Type "adb push [location of boot.img for device] /sdcard/download"
**replace "[location of boot.img for device]" with location of boot.img for YOUR DEVICE. USING A BOOT.IMG FOR A DIFFERENT DEVICE WILL MOST LIKELY RESULT IN YOUR DEVICE BEING BRICKED!!! That being said, I have provided the software for Junsun A930/A931 for Android 5.1. If you have a different device, you will need the boot.img for it.
-Type "adb install [location of file explorer apk]" or install an file explorer from the Playstore, etc.
**replace "[location of file explorer apk]" with file explorer of your choice. I used ES Explorer.
7. Now open Magisk on the Rear View Mirror. (Make sure you're either connected to WiFi or Data)
**Be sure to grant it SuperUser Permission from Kingo SuperUser.
- Click "Install" next to "Magisk is not installed"
- Click "Install" on propt that pops up
- Choose "Select and patch a file" option.
- Scroll down and click on Es Explorer (or the file explorer you chose)
- Now go into the "download" folder and click the "boot.img"
- Click the option "File way"
**The "Normal Android Way" option kept failing for me.
- Let this complete.
8. Go back into ADB on the PC
- Type 'adb pull "sdcard/download/magisk_patched.img" C:/Downloads'
**You can replace "C:/Downloads" with whatever location you want to pull the file to on your computer.
9. Launch SP Flash Tool on your PC (provided in RootPack.zip)
-Load Scatter File by clicking the "Scatter-loading" button next to "Scatter-loading File" in the "Download" tab.
**This can be found in the firmware that I've provided, IF you have the Junsun A930/A931. If you have a different device, load the scatter file for it, instead.
-Now unclick all the boxes.
-Now click the box for "location" on the "boot" aisle.
-Select the "magisk_patched.img" that we just made from C:/Downloads or wherever you saved yours. Click "Open."
-It should have now have put the location of your "magisk_patched.img" file in the "location" box and the box next to the "boot" aisle should now be selected again (If not, make sure it is. Also, that it is the only one selected)
-Now click on the "Download" button (with the Green Arrow) at the top.
-Hold the home button the Rear View Mirror and click "Restart" (be sure to keep the mirror connect to the computer via USB)
-Now let the bar at the bottom finish.
-When it's done, there will be a pop-up that says "Download OK"
-Your device will restart
10. In your Mirror, launch Magisk Manager.
-Congratulations! The Magisk Installed option should now be green and you should have permaroot! Enjoy!
**You can now uninstall Kingo SuperUser.
Links:
**I am unable to add links due to how new my account is. For the files as of now, search "[Root] Junsun Android 5.1 Rear View Mirror A930/A931 " on YouTube and all the links are in the description. I will update here as soon as time allows.
A BIG THANK YOU TO THE DEVELOPERS AT MAGISK, KINGOROOT, MINIMAL ADB AND FASTBOOT, MTK DRIVERS, SP FLASH TOOL, XDA, AND EVERYONE ElSE WHO ATTRIBUTED TO THIS THROUGH DEVELOPMENT OF PROGRAMS USED! IF THIS WAS HELPFUL, BE SURE TO THANK ALL OF THEM!
Click to expand...
Click to collapse
Also, just adding more info to my post above.
I've tried contacting Junsun directly and thru AliExpress, they weren't helpful and just advised this feature isn't supported.
Apparently the USB port can be used for flashing firmware, but no other information.
rochbaz said:
Great write up! Thank you.
I ended up picking a diff model Junsun /w 2gb RAM and am having issues with the USB port:
aliexpress : /item/32844242296.html
It won't recognize any USB devices, so assuming the drivers are missing or it's disabled permanently somehow. This unit is not powered thru USB port, there are separate 12v +/- to hardwire in. I've tried multiple USB cables as well.
I tried USB sticks for storage, but my actual intent is to hook up a USB DAB+ antenna like I'm using on another vehicle's Android
HeadUnit:
aliexpress: item/33003465623.html?spm=a2g0s.9042311.0.0.5ad74c4dUcy6j9
I just need basic USB drivers and 5V output on the USB port, any ideas on how to get this working or add drivers onto the existing ROM etc.?
Thanks!
Click to expand...
Click to collapse
So MTK usually doesn't recognize in Windows the traditional way. You'll need a MTK program or the ADB/Fastboot. Since I don't have this model, I have no way to test it but I would look around the settings to see if there are some extra settings menus like developer mode. In the A930, they have extra menu by clicking the "version" and tapping it multiple times (not Android's but Junsun's custom one).
The driver's that I provide here: https://drive.google.com/file/d/11poc-Pr30J_aPmhVJktuqZx1H9fkX371/view?usp=drivesdk
Should work for your model since it uses the same processor. It should be able to recognize it on start but if it doesn't recognize it when it boots up then there's probably something in settings that will enable it to. It will probably be hidden since it's most likely only for developers who were working on the rom.
Hello I've just rooted my junsun A930 alps-1.6.91 with Dr. Fone root, it showed device as ASUS A10 but rooted no problem and so far seems permanent..
Monkandi said:
Hello I've just rooted my junsun A930 alps-1.6.91 with Dr. Fone root, it showed device as ASUS A10 but rooted no problem and so far seems permanent..
Click to expand...
Click to collapse
Thanks ! It works! I try many times with Kingoroot, but allways fail. My mirror is recognized as MediaTek FX. It is android 5 . Is there any options to upgrade it to newest Android version?
Hello I'm looking for upgrade or custom rom myself, if I find anything I will let you know, but we're already in the best place XDA for it to happen... Good luck
I ask on Junsun Official Store and their answer: "Our equipment cannot upgrade the system. The system is fixed in the device..." So , no solution from official.
Monkandi said:
Hello I'm looking for upgrade or custom rom myself, if I find anything I will let you know, but we're already in the best place XDA for it to happen... Good luck
Click to expand...
Click to collapse
It depends on if anyone will spend the time to build an update rom or port for that device. If you send your device info, someone might end up working on it for you
nejcov said:
I ask on Junsun Official Store and their answer: "Our equipment cannot upgrade the system. The system is fixed in the device..." So , no solution from official.
Click to expand...
Click to collapse
I doubt it will ever have the support for the most current Android version. Most devices like this don't receive updates from official channels and the product isn't popular enough for most developers to have it.
updating fail due to power failed
I am using 4G Junsun A930 model DVR (1GB RAM) I have lost my framework "alps.l1.mp3.v2.95_t98_v2.1.10" I try to flash "full_E08_KM_4G_9.35_WJ_EN_1.6.91" but failed. any possibility to flash my dvr or get "alps.l1.mp3.v2.95_t98_v2.1.10" framework
ajish110 said:
I am using 4G Junsun A930 model DVR (1GB RAM) I have lost my framework "alps.l1.mp3.v2.95_t98_v2.1.10" I try to flash "full_E08_KM_4G_9.35_WJ_EN_1.6.91" but failed. any possibility to flash my dvr or get "alps.l1.mp3.v2.95_t98_v2.1.10" framework
Click to expand...
Click to collapse
Contact them and ask for the firmware for your device. They will most likely send you it. Flash it instead.
Then follow the steps I outlined but using the firmware they sent you instead. That is if you want root.
I requested but they are not respond
---------- Post added at 10:22 AM ---------- Previous post was at 10:10 AM ----------
Orginal firmware ony we can flash in mtk mt6753 chipset? No other solution? I try miracle tool it shows mt 6753 then try to read boot8 after tool auto shutdown
Do you have a picture of the back of your device?
I don't know of any other tools/methods. There's some other programs for MTK development but they won't be much help in this case. You'll need to get the stock firmware back before anything. There's no programs to find suitable software nor is there a cross-reference. There is also no custom roms for these devices. Thus, why root and Magisk integration is such a positive.
drive.google.com/file/d/1Q9v9S_F3OXGp5h-ekh_yAdtJAk246ukY/view?usp=drivesdk
---------- Post added at 11:34 AM ---------- Previous post was at 11:33 AM ----------
drive.google.com/file/d/1Q0Jsw5QbNm2NRsE9vPAr1nXd8_7s_dja/view?usp=drivesdk
There was no access so I requested it
Ok now added
!!WARNING!!
1st
You cant boot the 2019 Pro with a magisk patched boot.img. If you try to run the install script with a patched image it will brick the device!!!
The script re-locks the bootloader so if you want to try using any modified .img files you need to flash them individually or modify the script.
2nd
After you unlock the BL AI upscaling is disabled. Even after the BL is re-locked. Flashing back to the normal firmware should fix this but I am not sure of that.
3rd
After flashing the "developer" firmware the fact is it is no different than the standard firmware right now.. If Nvidia provides a rooted image in the future plz pm me and I will update this post.. I am leaving this post up for anybody who like myself is looking for shield pro 2019 info and was wondering if it could be rooted taking steps similar to the 2017 here
So with that said..
I just switched from a firestick 4k as my streaming device of choice to a shield pro 2019. I tried the cheaper $160 version first but when I looked at the specs and tried to do anything to it the lack of usb ports and 8gb storage made upgrading to the $200 pro a no-brainer.
So far I have gotten a few nice tweaks installed and Ill go into that in another post.
Things you'll need
A windows or linux PC with adb-fastboot binaries SDK Platform Tools
A male to male usb cable (my laptop has a usb-c input but It wouldn't work to connect to the shield)
NVIDIA SHIELD ANDROID TV 2019 Pro Developer Only OS Image HERE
SHIELD Family Windows USB Driver HERE
USB keyboard (or shield game controller possibly?)
First thing I did was enable USB debugging. Its the same process as other android devices. Device Preferences> About > then tap build info 10x. Then Device Preferences> Developer Options> enable usb debugging.
Now I made my own male to male usb cable by just splicing two old cables together matching the colors to each other. No special wiring is needed.
I used windows but it's easier to use linux if you can since windows required me installing a driver for fastboot to work.
To put the Shield into fastboot mode. Attach the usb cable to the usb port furthest from the hdmi port. And attach a usb keyboard to the usb next to the HDMI-out. Also keep the device connected to an HDMI display during the process. If you are using a pc that shares a screen with the shield tv then I suggest using chrome remote desktop to run the commands on the pc while the shield is using the display.
Windows 10: hold shift and right click in the platform tools folder
select open powershell here
type .\adb devices
type .\adb reboot bootloader
Linux you can just open a terminal and as long as adb is installed type adb devices then adb reboot bootloader
When it reboots there is an option to unlock the bootloader. You just select that and let it reboot again. You'll know it is unlocked because when it boots up with an unlocked bootloader a warning telling you the firmware cant be verified comes up for about 10 seconds.
To flash the firmware you need to get back into fastboot. Either go through the setup again quickly to enable usb debugging once more or there's another way to enter fastboot using a key combination (A+B on the shield controller, I don't know the combination on a keyboard).
Once its in fastboot again if you are using linux
unzip nv-recovery-image-shield-atv-2019-pro-8.2.0-dev_rooted.zip and cd into the directory containing the flash-all.sh script
and run it.
In windows 10 I needed to install the nvidia fastboot drivers before fastboot would detect it.
In device manager action> scan for hardware changes there should be a device with Fastboot in the name
You need to choose the option to update driver then select "have disk" and select the android_winusb.inf file and the device type should be Android Bootloader Interface.
Once fastboot drivers are installed open the file manager to the folder containing the flash-all.bat file, hold select and right click to open powershell in this location and type .\flash-all.bat
After the script runs the device will flash the dev firmware and lock the bootloader again.
I patched the boot.img with magisk but it wouldn't boot with it. I may try again tonight with different settings to get magisk to work.
EDIT: edited post to remove quote per op request lol. apparently after they posted the dev os firmware and i reported it to nvidia they never fixed it.. the dev os firmware on nvidia site for nstv pro 2019 model is exactly same as stock lolol
last i dled the dev os firmware it wasnt actually dev os firmware and was regular firmware.. once bl is relocked also u cant root it since it will no longer allow custom firmware..
this instruction us flawed to say the least
Thank you for start trying run magisk :good:
I didn't test patched boot-image, but when you can't boot, it maybe related to "vbmeta"
It seen nvidia don't like to provide root access to customers! because it remove vbmeta_skip.img from official 8.2.0-dev_rooted.zip package.
So may be you should try flash vbmeta_skip.img to achieve successful boot.
I attached vbmeta_skip.img from 8.1.0-dev_rooted.zip for you.
HTML:
fastboot flash vbmeta vbmeta_skip.img
I suggest keep testing on @Steel01 LOS releases. If we achieve an stable custom rom open-source, it's much much better than vendor release! I prefer freedom vs AI-Upscaling.
LOS releases: https://forum.xda-developers.com/showpost.php?p=83587703&postcount=458
mrhamed said:
Thank you for start trying run magisk :good:
I didn't test patched boot-image, but when you can't boot, it maybe related to "vbmeta"
It seen nvidia don't like to provide root access to customers! because it remove vbmeta_skip.img from official 8.2.0-dev_rooted.zip package.
So may be you should try flash vbmeta_skip.img to achieve successful boot.
I attached vbmeta_skip.img from 8.1.0-dev_rooted.zip for you.
fastboot flash vbmeta vbmeta_skip.img
I suggest keep testing on @Steel01 LOS releases. If we achieve an stable custom rom open-source, it's much much better than vendor release! I prefer freedom vs AI-Upscaling.
LOS releases: https://forum.xda-developers.com/showpost.php?p=83587703&postcount=458
Click to expand...
Click to collapse
yes, disabing vbmeta should be a given lol.. theres already root and steps have been discussed spread out in various threads already.. its just not a simple "flash this and youre rooted" so ppl keep asking about it lol
First You Need an unlocked bootloader there are many guides to unlock the bootloader on Samsung devices I recommend this one Unlock Guide
Once you have an unlocked bootloader we can proceed
1: Flash Twrp if you don't have it already: Snapdragon Twrp Or Exynos Twrp Download The Twrp For your device Model And Also Download Vbmeta Disabled, Reboot Into Download Mode By Pressing Volume Up And Volume Down When Booting The device
Download Odin and Samsung Drivers On your Computer Odin And Samsung Drivers
After You have Odin And Samsung Drivers, Open Odin and On the AP Section Select The Twrp You downloaded And On the Userdata Section Select The Vbmeta Disabled You Downloaded , GO TO OPTIONS AND DISABLE AUTO REBOOT!!!, Press The Start Button and once it Finishes, You Should Press The Power Button And Volume Down And When It Starts To Reboot Press The Volume UP And Power Button If you Did it right you Should Boot Into Twrp
2:
On Twrp Go to Wipe > Format Data > Type Yes (This will WIPE ALL DATA ON THE DEVICE!!!)
Then Go to Reboot > Recovery
After It reboots Go to Reboot > Fastboot
Download Adb On your Computer Adb Download And extract it into a folder, Then Press Shift On your Keyboard And Right Click At the same time Select The "Open Command Prompt Here" Option, You should see A command Prompt
Now You need To Download The Gsi You want to flash, (You can Find Many Gsi In the s20 fe Gsi's Group Here) Or you can Also Check Treble Gsi's Group
(Roms Based on Older PHH Patches than v303 Will not work)
Once You have the Gsi you want to flash Copy it into the adb folder And Also RENAME THE FILE to sys.img
Now On the Command Prompt You can Run > fastboot flash system sys.img
(If You Cant Get Your Drivers Working i recommend Trying ubuntu Because it has Drivers Pre Installed)
If you Dont get any errors then you are Good Reboot your device and you should see the gsi is installed
Fixing Rounded Corners:
Reboot Into Twrp And Open Adb On your computer
Download The Overlay and place it in the adb folder
Run ( adb shell mount /dev/block/dm-1 /vendor )
Then Run ( adb shell rm /vendor/overlay/framework-res__auto_generated_rro_vendor.apk )
Then ( adb push treble-overlay-samsung-rq8.apk /vendor/overlay )
Bootloop Problems:
You may have a bootloop If you are using A newer Vendor
This Was Tested On the one Ui 3.0 Vendor I Recommend Downgrading to 3.0 Vendor If you can
!!! I am not sure if its working on one UI 3.1 Vendor !!!
(Vendor is the one UI version you have)
Magisk:
To flash magisk you need some special Instructions, !!!Without them flashing magisk will result in a bootloop!!!
They are a bit complicated and you can find them Here (I don't recommend Using Magisk With Gsi's)
Issues?
Current issues are: 60fps Video Recording, Fingerprint Sensor And MTP
Fingerprint Might be fixed On android 12!!!
IF YOU ENCOUNTER PROBLEMS JOIN THE S20 FE HELP GROUP Here
(THIS WAS ALL TESTED ON SNAPDRAGON I AM NOT SURE IF IT WORKS ON EXYNOS)
I haven't clicked to look but is the magisk for GSIs that thing where you have to reboot from recovery to activate root ?
I suppose if it is the phone still wouldn't pass SafetyNet would it ?
3mel said:
I haven't clicked to look but is the magisk for GSIs that thing where you have to reboot from recovery to activate root ?
I suppose if it is the phone still wouldn't pass SafetyNet would it ?
Click to expand...
Click to collapse
no, you can fix magisk but its a bit hard, And yes you can pass safetynet with magisk, Some roms like pe+ Can pass safetynet without it tho
If only the fingerprint sensor worked on GSI ROMS. I would have definitely went for it.
S20 FE 5G rooted on android 11 (one ui 3.0)
Kolyei said:
If only the fingerprint sensor worked on GSI ROMS. I would have definitely went for it.
S20 FE 5G rooted on android 11 (one ui 3.0)
Click to expand...
Click to collapse
that's down to Samsung doing the bare minimum to qualify for treble compatibility, same as the vendor layers of most OEMs. only Sony went the extra mile to actually make sure their hardware would work apparently.
3mel said:
that's down to Samsung doing the bare minimum to qualify for treble compatibility, same as the vendor layers of most OEMs. only Sony went the extra mile to actually make sure their hardware would work apparently.
Click to expand...
Click to collapse
Not really, it has been confirmed that android 12 will add official support for underscreen scanners, so GSI devs aren't wasting any time on fixing FOD.
Doomer231 said:
Not really, it has been confirmed that android 12 will add official support for underscreen scanners, so GSI devs aren't wasting any time on fixing FOD.
Click to expand...
Click to collapse
any hardware OEMs add has supposed to have been functional for the last 3 years. they control their vendor layers which should work seamlessly with the OS layer. I'm paraphrasing the xda page that introduces treble and Phhuson.
OEMs have little interest in making treble work as it does nothing for them (they think). if google support was the reason 60fps would work for video recording but it doesn't.
Doomer231 said:
Not really, it has been confirmed that android 12 will add official support for underscreen scanners, so GSI devs aren't wasting any time on fixing FOD.
Click to expand...
Click to collapse
it was android 11 that broke it lol, on a10 it was fine
QUESTION for the GSI users out there...
do you have any of the screen juddering while trying to scroll or touch screen dead spots that occasionally happen ? any ghost touch issues, I suppose with the caveat of if you had them before ?
3mel said:
QUESTION for the GSI users out there...
do you have any of the screen juddering while trying to scroll or touch screen dead spots that occasionally happen ? any ghost touch issues, I suppose with the caveat of if you had them before ?
Click to expand...
Click to collapse
i never had any issues in one ui and i also dont on gsi
Does doing this guide trip Knox on the phone?
pOLLYpOCKET said:
Does doing this guide trip Knox on the phone?
Click to expand...
Click to collapse
yes, if you unlock your bootloader it trips knox
how can i found vbmate file for fold 2 ?
rowihel2012 said:
how can i found vbmate file for fold 2 ?
Click to expand...
Click to collapse
Do not install a gsi on the fold, it will be horrible as stock android has bad support for folding devices
overlay commands not functional (gives file not found error framework-res__auto_generated_rro_vendor.apk)
luisf0202 said:
overlay commands not functional (gives file not found error framework-res__auto_generated_rro_vendor.apk)
Click to expand...
Click to collapse
sounds like a question for the mighty phhuson and friends
luisf0202 said:
overlay commands not functional (gives file not found error framework-res__auto_generated_rro_vendor.apk)
Click to expand...
Click to collapse
try this instead adb shell rm /vendor/overlay/framework-res__auto_generated_rro_vendor.apk
For me fixing round corners disabled nav buttons and when choosing gestures as nav keys only swipe up for home gesture works back button is broken
are you using a 3rd party launcher ? navigation gestures are or were supposedly broken on 3rd party launchers regardless of which rom you're running.
no, im using quick step. But even with gestures disabled i dont have any buttons
View attachment 5376913
What is it? What is Ubuntu Touch?
Ubuntu Touch, as comes from naming, is Ubuntu managed to run on phone.
Well, Canonical abandoned it, so community organization, UBports, now develops, maintains, and ports UT to new devices.
And this is what the thread is about. The amount of devices able to run UT was 63(as written on website at the time of writing this post). But now it is 64 devices.
The 64th port to Xiaomi Mi 8.So, lets talk now what works, and what is not(you will also be able to see that on website, as soon as merge request will be accepted).
What works:
Actors
Manual brightness(auto seems not supported by UT, idk)
Notification LED
Vibration
Torchlight
Camera
Flashlight
Photo
Video
Switch between front and rear cameras
Cellular
Carrier info
Calls
SMS
Audio routings (switching between main speaker, and phone speakers)
Volume control
Misc
Battery percentage
Online charging(while phone is on, or in sleep/standby state)
UBports recovery
Network
WiFi(2.4GHz, 5GHz)
Bluetooth
Hotspot(partially, seems that 5G is not supported)
Flight Mode
Sensors
Fingerpring
GPS
Rotation
Touchscreen(ofc, otherwise I would write this post)
Sound
Microphone
Earphones
Loudspeaker
Volume Control
USB
ADB
MTP
Several things, are not tested, such as Wireless Display, NFC, SIM PIN Unlock, MMS, Dual SIM.
Non working features are Offline Charging, Auto-brightness, Proximity Sensor(you need to click the Power Button, that won't stop the call).
Big thanks to TheKit who helped me with the port.
TheKit's Gitlab and UBports forum profile.
Right now, config for UBports Installer is waiting approval of pull request, and merge request for devices.ubuntu-touch.io is still not approved, you will have to do everything manually. UBports Installer config PR finally merged, but only Global versions are supported, since firmware files that are flashed by Installer are for Global. If you do install, be sure to flash vendor and firmware packages for your variant after.
WARNING! YOU MUST HAVE UNLOCKED BOOTLOADER! EVERY THING YOU DO, YOU DO ON YOUR RISK, IF YOU BRICKED DEVICE, THATS YOUR FAULT, NOT MY! I DO NOT TAKE ANY RESPONSIBILITY FOR YOUR BRICKED DEVICE!
Preparations before installation.
Flash TWRP recovery
You need to download and flash stock firmware and vendor from Android 9, MIUI V11.0.6.0.PEAMIXM(be aware that this Vendor+Fw is for Global, if your Device is Chinese or Russian variant, or any other, flash vendor package according your phone variant). It is compressed into ZIP file, so you will have to flash it though TWRP. Do not use adb sideload, push file to any directory you want, and install it from phone.
Download boot.img, system.img, recovery.img from here.
In TWRP go to "Wipe" ==> "Format Data" ==> Type "yes" ==> Enter. Then go to Reboot ==> Recovery. After restarted. Again go to Wipe ==> Advanced Wipe, and select all partition except USB-OTG
Now we have two ways of installation, from TWRP, and from Fastboot.
TWRP
On PC:
Code:
$ adb push system.img /tmp
$ adb push boot.img /tmp/
Now go to "Install"
Get to /tmp/ directory
"Install Image"
Flash boot.img to Boot partition, system.img to System.
Then reboot to system.
If system works, reboot to TWRP again and push recovery.img to /tmp/, then flash it to Recovery partition.
Fastboot method:
Code:
#Simple as that
$ fastboot flash boot boot.img
$ fastboot flash system system.img
$ fastboot flash recovery recovery.img
#Flash recovery only after you are sure system works.
Or you can just install a installable zip archive I've recently made. All my builds will be hosted on GitHub Releases on my repo. New builds will come by every new official OTA release. UBports recovery is not included, installation goes proceeds from TWRP, install just as simple as custom ROM installation. Btw, do you want me to add notch patches to system image, so it doesn't look awkward?
Note: this zip is not signed, so disable signature verification before installing, or installation will fail.
Optionally you can adjust your panel so it doesn't look weird. Rn idk how to move panel below the notch(display cutout, I hate Apple for that). It moves buttons in Panel below, and adjusts height of the panel. This repo will do everything for you. Just download it to device. And run apply-notch-hax.sh. It will automatically find device name, apply patches, and restart Unity.
Note: run the script as standard user, not root.
Note2: if you get bootloop, wipe system, format data, restart bootloader, flash everything again, but before rebooting to system try flashing SELinux permissiver. And don't flash Magisk, it's useless, and may destroy your system.
Device source: Gitlab
Kernel source: Gitlab
Gitlab CI build artifacts: Gitlab
Join Telegram support group if you need any help.
See all supported devices at official website.
P.S. Since you have to use fastboot, and UBports Installer uses fastboot, there may be some difficulties for Ryzen CPU users. I attached zip file with executable (.bat file). It will allow you use fastboot with USB 3.x + Ryzen. Unpack it. And run .bat file as admin. Reboot. Voila, fastboot works as should.
Linux users should either use another laptop with Intel CPU, or flash from Windows, or use USB 2.0 hub.
P.S.S. Ok, I managed to get GitHub CI to work, so now if any of you want to test fixes and new features, head to this GitHub repo, and download artifacts from "Make OTA images"(in Actions tab), and flash them using fastboot.
Amazing work! I've always wanted to port UBTouch to Mi 8 but I couldn't get WiFi and mobile data to work on my attempts. As my primary phone, I needed it to be online as much as possible. Really happy to be able to use it on our devices
I've noticed an issue (I haven't managed to recreate this however):
- The OS can't switch between audio outputs, for example I need to restart my phone to hear sounds from loudspeaker after making a phone call. Please let me know if there's a workaround for this issue.
I'll be looking out for more issues to report. Once again, thanks for this port it's amazing
someone plz port Ubuntu to poco f1 too
gamerlucky said:
someone plz port Ubuntu to poco f1 too
Click to expand...
Click to collapse
It is already ported, a long before Mi 8
@itagizade have you tried waydroid on this?
nSKN3i said:
@itagizade have you tried waydroid on this?
Click to expand...
Click to collapse
No still not.
this amazing work. i have ran some x11 app on my phone,jt works. now i can say hava a pc in my pocket . one problem i found is system partion size too small (only 3g), this not enough if i want install more linux package lije chrome firefox
I updated download link, so if you have already flashed everything, I suggest you to flash a new recovery, as previous one, identified device as Mi MIX 3.
it is still complex for my level of knowledge to install this rom on my Mi 8 and it is with great joy that we have a port like this from Ubuntu Touch and that in the future it will be easier to install and maybe other ports as well as SailfishOS in the menu. Mi 8 great job Dev.
itagizade said:
It is already ported, a long before Mi 8
Click to expand...
Click to collapse
link please
gamerlucky said:
link please
Click to expand...
Click to collapse
See on devices.ubuntu-touch.io.
tried it out and worked great, glad to see something different, keep up the excellent work bro!
hey i was wondering about file system can we use f2fs ?
I tried installing apk files but getting error
Also notch fix gives me this error in terminal
EDIT: nevermind the apk i forgot to run anbox-tool install
EDIT2: nevermind notch fix i just pushed the file to downloads and run sh command
Amazing work! It is the fastest rom I have ever installed! The SIM PIN unlock works well and the offline charging partially (approximately, five minutes after connecting the charger). I hope NFC works, too. In the future, it would be nice if apply-notch-hax.sh was fixed (error, line 57). Anyway, thank you for porting and providing this rom!
For Waydroid support, there are some instructions here. To start the container service, use the following command:
Code:
sudo waydroid container start
Advanced Gears said:
Amazing work! It is the fastest rom I have ever installed! The SIM PIN unlock works well and the offline charging partially (approximately, five minutes after connecting the charger). I hope NFC works, too. In the future, it would be nice if apply-notch-hax.sh was fixed (error, line 57). Anyway, thank you for porting and providing this rom!
For Waydroid support, there are some instructions here. To start the container service, use the following command:
Code:
sudo waydroid container start
Click to expand...
Click to collapse
Glad you enjoy it. Right now I'm a little busy, but asap I will continue the work on this. Gotta make it daily-driver ready.
About error with `apply-notch-hax.sh`, other people have successfully used that script. Could you please specify the error?
The touch has been dead since I flash This rom
MilkywayOpenSource said:
The touch has been dead since I flash This rom
Click to expand...
Click to collapse
You mean Touchscreen is not working? Did you change you stock panel?
No,
MilkywayOpenSource said:
No,
Click to expand...
Click to collapse
Is your device Chinese version, or any other that Global?
It is global and after I install Ubuntu touch the screen never response to touch even in twrp