Database Develop

Xposed for RK3288 Devices

Hi, im new here and this is my first post, so i appreciate all the help and feedback you can give me.
im interested in using xposed in android TV Box's and Dongles, i've been reading and learning all about it for more than a month now. i've got it to work on most TV Box's and dongles that i have "RK based devices with android V 4.4 or less",but i still have a problem with one device which is an RK3288 based with android 5.1 that is already rooted.
i used twrp to flash xposed-v86-sdk22-arm.zip which was successful, than i wiped Dalvik/cache and rebooted, but the boot stuck on bootanimation, i disabled xposed by installing the uninstaller.zip and everything went back to normal. i tried it many times but with no use. i noticed that twrp doesnt mount internal SD, i installed an older version of bootloader which gave me the ability to mount the internal Sdcard, and i tried to install xposed again and this time it pass the animation and goes to a black screen where i can use the mouse but nothing else. with some research i found that UT3+ is based on firefly board and their original ROM is available for download and it has the same bootloader version that came installed with the device, after flashing the new ROM i was able to mount the internal Sdcard and i tried to install xposed again, and this time it gives me optimizing apps but after it finish the device reboot and get stuck again on bootanimation.
my question is, if there is a log for errors to know why the system/boot get stuck , where can i find them??
and if there is no logs how can i monitor the booting process to find the info i need??
also i know or read what bootloader is but i dont understand how it is effecting xposed installation.
Sorry for the long post, and thank you for your help in advanced
EDIT: i finally got adb connection with the device and used logcat to get the logs, but im not sure how to attach the files. if anyone can help i will gladly send the logs. thanks

Update 1
i was looking at the logs "didnt know what to search for im not a developer" and i noticed that everything is crashing and "Not granting permission" ,"Unknown permission " are everywhere .
sample of logs:
Code:
"com.google.android.partnersetup.permission.WRITE_APP_PROVIDER in
package com.android.vendingW/PackageManager( 4712): Not granting
permission android.permission.BIND_WALLPAPER to package
com.android.camera2 (protectionLevel=18
flags=0x58bc45)W/PackageManager( 4712): Not granting permission
android.permission.BIND_APPWIDGET to package com.android.launcher3
(protectionLevel=18 flags=0x583e45)W/PackageManager( 4712): Unknown
permission android.permission.READ_SETTINGS in package
com.android.launcher3W/PackageManager( 4712): Unknown permission
com.android.launcher.permission.READ_SETTINGS in package
com.android.launcher3W/PackageManager( 4712): Unknown permission "
so i decided to root again with KingRoot, and i tried installing xposed again, and it kinda worked. the system boot and the launcher opens but crashing messages keeps showing "Stresstest for 5.0 has stopped running" , "The process com.android.phone has stopped running", and others.
now im not sure about what im doing but i'll test two methods:
1- i will unpake ROM.img put xposed in the root and update the updater script to install xposed when i flash the ROM.
2- the device can run Linux version from SD card so i might run it and manually install xposed files.
if anyone have any tips or info please let me know. thanks

SOLUTION
For those who are having problems with their RK based android TV Box with android 5.1, if you get stuck on Boot animation or the system boots with black screen and you can use your mouse only, or if you getting errors when you boot the main problem would be your firmware is modified and up to Xposed V.86 is not supported because of the error "No implementation found for void dalvik.system.VMRuntime.clam" you can read more about it in this post https://github.com/rovo89/Xposed/issues/167.
and luckily dsa8310 made a modefied version of xposed, i tested it and it works you can find the download link here http://forum.xda-developers.com/showpost.php?p=67787484&postcount=325

viVaPale said:
luckily dsa8310 made a modefied version of xposed, i tested it and it works you can find the download link here http://forum.xda-developers.com/showpost.php?p=67787484&postcount=325
Click to expand...
Click to collapse
I can't get to the page with the link. (I get a noob alert) We want to try this xposed on a ugoos ut3s (android 5.1 with a rk3288)
Would someone please be so kind to post it here or tell me where I can download it.

Anyone that can compile Xposed v87 to fix this problem for RK3288 Lollipop devices?
https://github.com/rovo89/Xposed/issues/167
https://android.googlesource.com/platform/art/+/379d09fe3c3feb7c2a2fb5a3623689b5ace7e79b
Are there instructions somewhere so we can compile it ourselves?
The code above looks like it needs to be applied to Android source code, what must be changed in Xposed Github code to fix it and compile our own new Xposed only for our devices?
Thanks

humptydumpty said:
I can't get to the page with the link. (I get a noob alert) We want to try this xposed on a ugoos ut3s (android 5.1 with a rk3288)
Would someone please be so kind to post it here or tell me where I can download it.
Click to expand...
Click to collapse
Please try this link https://mega.nz/#!300ggYoJ!1vdLP0OyU2D1ky6pWv-Y3VJFH5paHSAqV3Y8A64bvkk
i recommend you download the xposed uninstaller in case something wrong happend

viVaPale said:
Please try this link https://mega.nz/#!300ggYoJ!1vdLP0OyU2D1ky6pWv-Y3VJFH5paHSAqV3Y8A64bvkk
i recommend you download the xposed uninstaller in case something wrong happend
Click to expand...
Click to collapse
Wow ! Work nice on my haier pad971 (ifive air clone) rk3288 5.1.1 !!
Thanks so much

does anyone know if there's an RK3288 enabled xposed v89 built to avoid the issues described by viVaPale? Tried the one from 3.1.5 installer, but after boot it doesn't load the launcher, only mouse can be moved around like viVaPale describes.

CrDrooid Android 7.1 test

https://yadi.sk/d/aDqvPskH3EaeFX
Based on the 3.10 kernel... (for the first revision, Android 5.1) Beta-try, chase, complain, correct.))
The same Resurrection Remix with the system settings
Features and changes:
Very fast firmware in the likeness of Resurrection Remix
The latest source code for AOSP/LOS
Combines various features from LOS, RR, Paranoid Android, SlimRoms, OmniRom, etc.
Support Substratum Theme Engine
There is a good feature called LTE. It disables only voice calls and WIFI works.Not to be confused with airplane mode
Fixed Offline charging
Root is built-in is enabled in developer options
Gapps sewn.

So this is android 5.1 or 7.1 ? I'm willing to try it on my elephone M2.

NLSteve said:
So this is android 5.1 or 7.1 ? I'm willing to try it on my elephone M2.
Click to expand...
Click to collapse
7.1.1.

I have a problem installing this.
Update: I think the problem is I encrypted phone before installing this using 9x9 grid. I will decrypt phone and try again.
I used TWRP 2.8.7.3 (megthebest) -> install crDroidAndroid-7.1.1-20170223.zip
FAILED
Updating partition details...
...done
" E:Resource (image)-(background) failed to load "
E:Error executing updater binary in zip '/external_sd/crDroidAndroid-7.1.1-20170223.zip
Click to expand...
Click to collapse
Error flashing zip '/external_sd/crDroidAndroid-7.1.1-20170223.zip'
Updating partition details...
...done

NLSteve said:
I have a problem installing this.
Update: I think the problem is I encrypted phone before installing this using 9x9 grid. I will decrypt phone and try again.
I used TWRP 2.8.7.3 (megthebest) -> install crDroidAndroid-7.1.1-20170223.zip
FAILED
Error flashing zip '/external_sd/crDroidAndroid-7.1.1-20170223.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
TWRP 3.0 It is necessary to use

update:
Listed: 02/25/2016 11:30 pm
ROM Version: TWRP M2 3.0.0
http://www.needrom.com/wp-content/uploads/2016/02/TWRP-3.0.0-Elephone-M2-megthebest.rar

NLSteve said:
update:
Listed: 02/25/2016 11:30 pm
ROM Version: TWRP M2 3.0.0
http://www.needrom.com/wp-content/uploads/2016/02/TWRP-3.0.0-Elephone-M2-megthebest.rar
Click to expand...
Click to collapse
What is it?

NLSteve said:
update:
Listed: 02/25/2016 11:30 pm
ROM Version: TWRP M2 3.0.0
http://www.needrom.com/wp-content/uploads/2016/02/TWRP-3.0.0-Elephone-M2-megthebest.rar
Click to expand...
Click to collapse
You tried to link to

duffi200000 said:
You tried to link to
Click to expand...
Click to collapse
yes. This is working download link for TWRP 3.0
---------- Post added at 01:53 PM ---------- Previous post was at 01:14 PM ----------
To get working Wi-Fi set country Wi-Fi region code to Europe or Germany that did the trick.
So far so good. Nice OS you have here. All good still runnning.
I'm noticing this OS is faster compared to cyanogen
Android 7.1.1 has issues with:
- Gboard keyboard disappearing when typing.
Solution: Install keyboard app like swiftkey.
- File transfers USB: files to Windows or Mac (MTP) does not work.
Solution: use transfer photo (PTP) and copy files to DCIM folder, later move files with an explorer app on the phone.
- No support for Xposed framework as of yet. Read latest post by Rovo89

NLSteve said:
yes. This is working download link for TWRP 3.0
---------- Post added at 01:53 PM ---------- Previous post was at 01:14 PM ----------
To get working Wi-Fi set country Wi-Fi region code to Europe or Germany that did the trick.
So far so good. Nice OS you have here. All good still runnning.
I'm noticing this OS is faster compared to cyanogen
Android 7.1.1 has issues with:56
- Gboard keyboard disappearing when typing.
Solution: Install keyboard app like swiftkey.
- File transfers USB: files to Windows or Mac (MTP) does not work.
Solution: use transfer photo (PTP) and copy files to DCIM folder, later move files with an explorer app on the phone.
- No support for Xposed framework as of yet. Read latest post by Rovo89
Click to expand...
Click to collapse
http://4pda.ru/forum/index.php?showtopic=678045&st=5240#entry52552870
Try that, that's what I was able to set the phone to the computer, everything works fine. And Yes the firmware is still a test, but she's really smart, the problem with the camera can't decide

Thank you, I will try that for usb connection to computer.
This is a nice rom overall. @duffi : Did you find 56 issues? i see you added this to my text "Android 7.1.1 has issues with:56 "
If anyone needs advice or a step-by-step guide to install on elephone M2, feel free to ask!

Hi NLSteve,
can I get a step by step guide for install 7.1.1 on M2? I use 5.1 latest rom and I have root on the prhone.

How To Install CrDrooid Android 7.1 on Elephone M2
Make sure you save your contacts and essential info to SD card or computer.
If for any reason your phone is encrypted, change the unlock code to pin 4 numbers! if you use pattern larger than 3x3 or more complex pin you're screwed XD
For this guide, you will need:
Sp-flash-tool-v5-1648 (latest version)
TWRP M2 3.0 (megthebest)
CrDrooid Android 7.1
SR3-SuperSU-v2.79-SR3 (latest version)
Copy the ROM and supersu to External SD Card.
TWRP flashing with SP Flash Tool
1. Shut down your phone and Disconnect usb cable from pc.
3. Run SP Flash Tool and navigate to 3rd tab Download, load download agent MTK_AllInOne_DA.bin and load MT6753_Android_scatter-TWRP3.txt for your phone.
4. Only have recovery checked and keep the option Download Only.
5. Click Download button and connect your phone (which is off) with PC via USB cable. Process should start. After process (60 seconds or more) is finished you will see green circle on screen again. Unplug USB from phone.
6. Turn on by pressing Power and Volume +, hold for 10-20 seconds until boot into TWRP recovery mode.
Installing ROM
1. Go to Wipe. Go to Advanced Wipe. From here, tick the boxes next to Dalvik Cache, System, Data and Cache, then swipe the slider at the bottom to perform a full wipe.
2. Go back to Install and browse to the location where you saved the file and select the crDroidAndroid-7.1.1-20170223.zip file
3. When done tap Reboot to boot into Android.
4. After system done, shut down to recovery and install supersu.zip by browsing to the location of Supersu.zip and choose install.
This is it for now. Good luck!

Hi NLSteve, it works, Antutu 39965 Points. But camera is not working, Fingerprint is not working and Bluetooth is also not working, its flaky. Phone M2 works faster then stock ROM 5.1. What I do missing is the function for updates next time. Great work. Hall Sensor is also not working. Thx.

Hi @volobobo, sorry to hear to hear you miss many functions. For me the camera and bluetooth is working though. :S
Hall effect sensor is used to detect flip covers? I just use close proximity sensor on camera to turn off screen.

@NLSteve
NLSteve said:
Hi @volobobo, sorry to hear to hear you miss many functions. For me the camera and bluetooth is working though. :S
Hall effect sensor is used to detect flip covers? I just use close proximity sensor on camera to turn off screen.
Click to expand...
Click to collapse
Hi NLSteve, camera is really working? Bluetooth is also really working? I have paired with my bluetooth headphones. If so I will keep it a new try. Hall sensor was a misstake on M2, we have one proximity sensor.

Is SIM card working? My ports for other Phone works except sim card recognition.. Bad thing.. therefore I ask.. good to read that you make roms for the M2, which is not a current phone.
Gesendet von meinem SM-G900F mit Tapatalk

Ehy what about making an updated version?

What suprise - M2 isnt dead
Hi all,
since eragon give up because his broken phone, nothing is going forward with our M2,
always stuck on the old Android 5.
Now, we could make a jump to 7.1.
Only a test version by now, but nice to see, there are more options with this hardware.
Unfortunally, my camera changed from an resolution from 13 MP to 5,3 MP. The focus doesnt function (sharpness) in short distance under 50 centimeter.
I tried several camera apps in the last view days. But no one solved that problem.
I looked in the build.prop, but have really no idea, what i can do do rechange to 13 MP.
So, the camera is like dead, i cant get any acceptable pictures by now. :crying:
Have anybody an solution for this problem?
Thanks to all, spending so much time and energy, to keep this phone alive. :good:

Please anyone re-upload link.

EFIDroid for the Samsung Galaxy Note 4/Note Edge (Snapdragon Variants)

I have ported EFIDroid (developed by @m11kkaa) to the Snapdragon variants of the Samsung Galaxy Note 4/Note Edge.
@m11kkaa's original EFIDroid thread here: https://forum.xda-developers.com/android/software-hacking/efidroid-t3447466.
This is an unofficial port of beta software. I am not responsible for anything that may happen to your device. Use at your own risk.
Note: This has been tested with Samsung stock ROM, EmotionOS 7.1.1, and TWRP 3.0.2-0 on an SM-N910V/trltevzw. All other configurations are untested by me, but should work.
Confirmed working on:
- SM-N910V (trltevzw) (my device)
- SM-N910T (trltetmo) (thanks @viewsfromthepi)
- SM-N910G (trltedt) (thanks @Preet Juneja)
- SM-N910P (trltespr) (thanks @carlosggb)
- SM-N910W8 (trltecan) (thanks @d3multimedia)
- SM-N910F (trltexx) (thanks @cod_r) (possibly some issues with multiboot)
- SM-N915FY (tbltebtu) (thanks @jpearn)
- SM-N915F (tbltexx) (thanks @Juank2007)
I believe this works on all Snapdragon variants. If you're willing to test a variant not listed above, follow the instructions below, and post below if you had success, or if you encountered any issues.
Warning: There have been reports of the app failing to backup the boot/recovery partitions on other devices, leaving the device unable to boot to the OS and/or recovery. I have no way of testing whether this happens on the Note 4, so be ready with a working recovery/boot img on your computer...
I believe this issue does not affect the Note 4, as there have been successful installs with the app. However, I am leaving the related info on how to recover below, just in case this happens to one of you.
Installation
Install the attached EFIDroid Manager apk. Since this is an unofficial port, the EFIDroid Manager app from the Play Store won't work.
Open the EFIDroid Manager app, open the menu (at the top left), and click "Install/Update".
Click the big orange Install button.
And voila, you're done in 3 easy steps! Reboot to see your new 2nd-stage bootloader!
Post below with your variant/installed ROM if you have success.
To update EFIDroid, just repeat step 2, and the click the big orange Update button.
The app won't automatically check for updates, so I'll post an announcement on this thread whenever an important update is available.
Multibooting
You can use EFIDroid as a multiboot manager. To add a multiboot ROM, do the following:
Open the EFIDroid Manager app. Press the plus button at the bottom right side of the screen to start adding a multiboot slot.
Under "Location", there should be a couple paths. Select the one containing "/data/media/0" if you want the new slot to reside on the internal SD card (recommended for speed). Select the one containing "/mnt/media_rw/" if you want the new slot to reside on the external SD card.
You can give the slot a name/description by using the appropriate fields.
Press the checkmark at the top right side of the screen to create the multiboot slot.
Reboot. When EFIDroid comes up, select TWRP, then select the newly created slot.
Go to the "Wipe > Advanced Wipe" menu. Select "System", then swipe to wipe.
Install all the zips you want on that slot.
Reboot, and when EFIDroid comes up, your new slot should automatically be selected. Press the power button to boot, and enjoy!
Migrating from Dual Boot Patcher
Coming soon!
Troubleshooting
If you are unable to boot the OS/recovery from EFIDroid, do the following (you do have a working boot.img and recovery.img, right?)
This assumes you have fastboot properly setup.
In EFIDroid, use the volume keys to navigate to "Fastboot", the press the power key to select it.
There should only be one entry in the Fastboot menu. Press the power key to select it.
Connect your phone to your computer with a USB cable. Run the following (on the computer), one line at a time:
Code:
fastboot flash boot <path/to/boot.img>
fastboot flash recovery <path/to/recovery.img>
fastboot oem exit
In EFIDroid, use the volume keys to navigate to the back button at the top of the screen. Press the power key to select.
Use the volume keys to navigate to "Reboot", then press the power key to select.
If Maintenance Mode comes up, press the home button to reboot.
You should be able to boot the installed OS/recovery now. If this doesn't work, you can always Odin a TWRP tar, and then flash your original boot.img from inside TWRP, to get back up and running again.
Known Bugs
Aroma installers in TWRP may flicker, rendering them unusable.
Again, all credit goes to @m11kkaa for doing all the hard work in developing EFIDroid.
XDA:DevDB Information
EFIDroid, Kernel for the Verizon Samsung Galaxy Note 4
Contributors
abraha2d, m11kkaa
Source Code: https://github.com/efidroid
Kernel Special Features: UEFI, MultiBoot
Version Information
Status: Beta
Current Beta Version: 0.1
Beta Release Date: 2017-03-18
Created 2017-03-19
Last Updated 2017-07-03

I have the Sprint model. Is it safe to try?
Anyone try this yet.?

aaron74 said:
I have the Sprint model. Is it safe to try?
Anyone try this yet.?
Click to expand...
Click to collapse
I believe the Sprint variant is similar enough hardware-wise to the Verizon variant.
As with everything, make sure you backup, and store the backup somewhere other than your phone.
That being said, I believe there are no risks, other than possibly an hour or so of downtime (if something goes wrong with the installation). Since EFIDroid only modifies the boot and recovery partitions, if something goes wrong, you can always flash TWRP via Odin, and then in TWRP flash the boot.img from whichever ROM you're currently running to get back up and running.
If you're willing to wait, I have a friend who has volunteered to test this out on his Sprint variant in a week or two (when he gets his daily driver back).

There is my error now ... what boot and recovery img are you talking about??

Neuken69 said:
There is my error now ... what boot and recovery img are you talking about??
Click to expand...
Click to collapse
Trying clearing the data of the EFIDroid Manager app.

abraha2d said:
Trying clearing the data of the EFIDroid Manager app.
Click to expand...
Click to collapse
Same error
---------- Post added at 10:54 PM ---------- Previous post was at 10:16 PM ----------
im runnng aurora ROM now and i swap between that and Noble ROM not sure if that plays into the error
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
im runnng aurora ROM now and i swap between that and Noble ROM not sure if that plays into the error
---------- Post added at 11:14 PM ---------- Previous post was at 10:55 PM ----------
If you have devices.json in that folder and your running a n910v ... can you share that file?

Neuken69 said:
Same error
---------- Post added at 10:54 PM ---------- Previous post was at 10:16 PM ----------
im runnng aurora ROM now and i swap between that and Noble ROM not sure if that plays into the error
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
im runnng aurora ROM now and i swap between that and Noble ROM not sure if that plays into the error
---------- Post added at 11:14 PM ---------- Previous post was at 10:55 PM ----------
If you have devices.json in that folder and your running a n910v ... can you share that file?
Click to expand...
Click to collapse
Is Noble ROM or Aurora ROM a Note 5/7 port? Because that may be the issue. The app might be getting confused.
I have another user who's having the same issue, with a Note 7 port ROM... I'll have to debug on my end, and see what the problem is... The app is supposed to be downloading that file from the OTA server...

abraha2d said:
Is Noble ROM or Aurora ROM a Note 5/7 port? Because that may be the issue. The app might be getting confused.
I have another user who's having the same issue, with a Note 7 port ROM... I'll have to debug on my end, and see what the problem is... The app is supposed to be downloading that file from the OTA server...
Click to expand...
Click to collapse
Being on Note 7 port, as you said I've changed product code.
I'm really sorry that I can't test right now by flashing stock firmware but I promise I'll do it sooner.
If anybody else is on stock, please report!

Im downloading paulpizz stock rom ... will be testing within 45 min

Neuken69 said:
Same error
---------- Post added at 10:54 PM ---------- Previous post was at 10:16 PM ----------
im runnng aurora ROM now and i swap between that and Noble ROM not sure if that plays into the error
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
im runnng aurora ROM now and i swap between that and Noble ROM not sure if that plays into the error
---------- Post added at 11:14 PM ---------- Previous post was at 10:55 PM ----------
If you have devices.json in that folder and your running a n910v ... can you share that file?
Click to expand...
Click to collapse
Preet Juneja said:
Being on Note 7 port, as you said I've changed product code.
I'm really sorry that I can't test right now by flashing stock firmware but I promise I'll do it sooner.
If anybody else is on stock, please report!
Click to expand...
Click to collapse
Guys, can you install the attached debug apk, clear data, grant storage permission, and then try again? If it still errors, can you send me a logcat?
@Preet Juneja There's a way to get logcat without a computer, using the Matlog app from the Play Store. See this for details:
https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/
You don't need to do the adb part if you're rooted...

abraha2d said:
Guys, can you install the attached debug apk, clear data, grant storage permission, and then try again? If it still errors, can you send me a logcat?
@Preet Juneja There's a way to get logcat without a computer, using the Matlog app from the Play Store. See this for details:
https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/
You don't need to do the adb part if you're rooted...
Click to expand...
Click to collapse
All logs related to EFIDroid attached:

Preet Juneja said:
All logs related to EFIDroid attached:
Click to expand...
Click to collapse
Did you just search for all lines containing EFIDroid, or did you actually filter by app? Because these logs seem incomplete...
Sent from my Samsung Galaxy Note 4 using XDA Labs

abraha2d said:
Did you just search for all lines containing EFIDroid, or did you actually filter by app? Because these logs seem incomplete...
Click to expand...
Click to collapse
Logs: (From launching EFIDroid app to pausing logs on Matlog app)

Preet Juneja said:
Logs: (From launching efidroid app to pausing logs on matlog app)
Click to expand...
Click to collapse
Did you put anything into the "Override OTA Server" dialog? From the logs, either there's something wrong with the app, or you put "samsung/trltevzw" into the dialog...

abraha2d said:
Did you put anything into the "Override OTA Server" dialog? From the logs, either there's something wrong with the app, or you put "samsung/trltevzw" into the dialog...
Click to expand...
Click to collapse
Oh. I put it when I didn't edit build.prop (when it was Noblelte). I already tried clearing data due to which it should've removed. Well if it didn't, how can I remove it?
I'm sure it's problem from my side and not yours... it's all because I'm using custom ROM.
UPDATE:
YES IT OPENED!
I emptied that override OTA server and the app finally asked for Root access!
Thank you so much, I'll sooner report what will be the next.

Preet Juneja said:
Oh. I put it when I didn't edit build.prop (when it was Noblelte). I already tried clearing data due to which it should've removed. Well if it didn't, how can I remove it?
I'm sure it's problem from my side and not yours... it's all because I'm using custom ROM.
Click to expand...
Click to collapse
No problem, it should probably be clearer. That dialog is for entering a different URL for the OTA server, not a different device codename. Just remove what's in there, and press Ok. That will clear it. :good:
EDIT: Just saw your edit. Nice to hear it's working.

abraha2d said:
No problem, it should probably be clearer. That dialog is for entering a different URL for the OTA server, not a different device codename. Just remove what's in there, and press Ok. That will clear it. :good:
Click to expand...
Click to collapse
Thank you so much.
Will update you soon.

Ok now what???

Neuken69 said:
Ok now what???
Click to expand...
Click to collapse
Just reboot your device to see changes!
Perfectly working, please add N910G support as 'confirmed' in 1st post.
Also, you can add instructions for custom ROM user to edit build.prop as required.
I was able to boot into TWRP and ROM without use of fastboot.

abraha2d said:
I believe the Sprint variant is similar enough hardware-wise to the Verizon variant.
As with everything, make sure you backup, and store the backup somewhere other than your phone.
That being said, I believe there are no risks, other than possibly an hour or so of downtime (if something goes wrong with the installation). Since EFIDroid only modifies the boot and recovery partitions, if something goes wrong, you can always flash TWRP via Odin, and then in TWRP flash the boot.img from whichever ROM you're currently running to get back up and running.
If you're willing to wait, I have a friend who has volunteered to test this out on his Sprint variant in a week or two (when he gets his daily driver back).
Click to expand...
Click to collapse
Thanks! So this allows you to dual boot 2 different roms?
One is primary installed as normal, i take. Now the second one, how is it installed? How is it saved?
Thank you. I'm just curious. This sounds convenient to have your daily driver as primary, and be able to test other roms without constantly backing up and restoring. Am i correct in thinking this way?

[TOOL][ROM] UpdateEngine UI -- Flash Android O beta without wiping data

I highly recommend @JamFlux's work instead. Currently, this has got way more complicated than it should be (in the past 24 hours, only 40% users have managed to accurately follow the procedure, and even less for the latest beta). However, I will continue working on this project in order to make it compatible across more devices. The app is now open-source and you can visit the GitHub repo here. Thanks for using UpdateEngine Interface and I hope to see you folks again soon.
I've created the UpdateEngine Interface, a tool to install OTAs that haven't been assigned to your device. It talks to Android's update_engine binary to flash the block-based updates just the way the original updater does, ensuring that your data is preserved and your system partition's signature doesn't change.
TLDR: It allows you to install Oreo without using someone else's TWRP backup or losing data.
Now has the latest build (20th December)
Installation:
Install Magisk
Install the attached Magisk module (named UpdateEngine_1.2.zip) and reboot
Open the newly installed UpdateEngine app and press start
Wait for the installation to complete and restart your device to boot into Android O
If you wish to update to the latest beta, use Magisk to install UpdateEngine_1.3.zip afterwards
Note: If you're a FlashFire user, please uninstall it and reboot before continuing.
Note #2: You must install Oreo via v1.2 before installing the latest beta (via v1.3).
XDA:DevDB Information
UpdateEngine User Interface, Device Specific App for the Xiaomi Mi A1
Contributors
ur0
Version Information
Status: Stable
Current Stable Version: 1.1
Created 2017-12-19
Last Updated 2017-12-19

Does it need a virgin /system?

I love you! thats what we need.

konradit said:
Does it need a virgin /system?
Click to expand...
Click to collapse
Yeah. It requires that the system hasn't been modified since the December OTA (just like the original updater) since the updates are applied block-by-block.

Which beta does it have currently? THE first one or newer?

jazzthe#1 said:
Which beta does it have currently? THE first one or newer?
Click to expand...
Click to collapse
I only have the first build, since that's the only one that people captured (I'm not in the beta, so I can't get the newer ones myself).

Okay

@ur0 wow, thats awesome, thank you bro)

This looks interesting, although I'm waiting for Xposed Oreo. A question though, I've heard the leaked Oreo build is rooted, does this method install untouched boot.img?

@Filip013 yes, this installs the untouched boot.img.
@rostifaner and @TerQQ, You're welcome!

so this tool can install android O ota beta without twrp ? and without losing data ? and how to install this tool ? sorry for many question .

is possible to add feature "choose ota file from device" or something similar ?

TerQQ said:
is possible to add feature "choose ota file from device" or something similar ?
Click to expand...
Click to collapse
I'm looking into adding this -- the only problem is that it also requires a bit of metadata (which is inconvenient to type manually). I'll look into defining a format which the app can read directly.

It doesn't seem to be working for me. When I press Start, it opens FlashFire app & nothing happens. Even if I come back to this app, there will two buttons Pause & Stop, but nothing will be happening. Also can you please make it open source?

ghpranav said:
It doesn't seem to be working for me. When I press Start, it opens FlashFire app & nothing happens. Even if I come back to this app, there will two buttons Pause & Stop, but nothing will be happening. Also can you please make it open source?
Click to expand...
Click to collapse
That's weird -- can you please post the logcat outputs after this happens (maybe after restarting and trying again)?
I'm sure that it's something with flashfire since the app doesn't use it or depend on it.
I'm definitely going to open-source this after I fix a few hacks I made to get the initial version working.

Any chance of posting your work to github? would be interesting to see the source if possible

How to install?
How to install magisk and update engine. Will we have to root and flash these file from TWRP? Please give the tutorial in detail.

for me its working great.

I don't understand what purpose this tool serves. You're saying that using this we can install the oreo update without someone's twrp bakup?

I keep getting a crash when i press start, then the app won't open again until I reboot and even then no download... am i missing something?
I have magisk 15.6 and i disabled all my other modules just in case...
EDIT:
12-19 11:32:16.564 3121-3267/? E/DatabaseUtils: Writing exception to parcel
java.lang.SecurityException: Permission Denial: reading com.android.providers.media.MediaProvider uri content://media/external/fs_id from pid=9022, uid=10111 requires android.permission.READ_EXTERNAL_STORAGE, or grantUriPermission()
at android.content.ContentProvider.enforceReadPermissionInner(ContentProvider.java:608)
at android.content.ContentProvider$Transport.enforceReadPermission(ContentProvider.java:483)
at android.content.ContentProvider$Transport.query(ContentProvider.java:212)
at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:112)
at android.os.Binder.execTransact(Binder.java:565)
I think you need to add the read/write premission to your app. not sure how its working for others
EDIT 2: Selinux is denying your app.. had to use a selinux disabler app to get it not to crash... might want to look into that..
EDIT 3: Not working... Nothing happens when i click start...

[Rom] Ubuntu touch [halium 9] with waydroid [11] support

This is an update to the Ubuntu Touch build that I shared a while back.which was based on halium 7. Now we are moving to halium 9. Even with quite a few unsolved issues ,these builds are marginal improvement over the previous ones.
This port had been no means easy, in reality, the initial builds was even more buggy compared to previous gen ,but most of them were much easier to fix, as I got lots of help from the porting community.I was able to get it to a booting state in about 3 months time as compared to more than a year with halium 7 , to be fair the delay was also due to the fact that I was not exactly an android developer or a developer for that matter, and had to read a lot at first .
anyways I share it here as I have reached a point where further bug fixing is beyond my capability . or in other words, Googling error codes and testing all possible methods /solutions don't seem to yield any meaningful full result, I do really wish someone better than me would look into it and make it even better ;- )
In the meantime let me add more Verbose ;-P
What is ubuntu touch
ubuntu touch is different from other oses as it is fork of Linux as compared to all our favorite mobile oses being forks of android. in other words, it is a fully functional Linux os optimized to run on arm64 device in a touch environment.The original idea was conceived by canonical and later they stoped their work and open-sourced the project and transferred the assets to the ubports community, the community is actively improving it, and trying to bring it to feature parity with Android .
whats working on this port
calls,data ,wifi
sound, vibration
auto rotation
auto, manual brightness
Offline charging
GPS
and other misc things
whats partially working
camera (preview and take video works clicking picture not working)
fingerprint (fingerprint wakes the device but cant enroll fingerprints)
Bluetooth (everything works except file transfer)
what does not work
adb,mtp
one of the feature improvements amongst other things is the support for waydroid
Waydroid
waydroid is a containerised approach to get an android environment running in a Linux system with the added advantage of full hardware access.so we can android apps and games natively. more details can be found here. to install way droid open terminal and paste the following
sudo -s
mount -o rw,remount / && apt update && apt install waydroid && waydroid init
It also need a fix as waydroid is intended for treble devices which can be found in this post. Thank you @erfanoabdi for enabling support for non treble devices.
Installation
- flash the halium-boot and the following zip file
- clean flash recommended
- reboot after the initial setup is done
Halium-boot .img
ubuntu_touch_installer_Kenzo_halium9_v7.zip
Please Donate
Every rupee ,euro ,doller counts. It would feel wounderful to be gifted something no matter how small.
If you like to do more, please consider buying me a coffee or may be even another Kenzo.
if you are in India please use this upi id -- > [email protected]
else do pm me.
default user password is " a "
For the History book
ubuntu_touch_installer_Kenzo_halium9_v6.zip
ubuntu_touch_installer_Kenzo_halium9_v5.zip
ubuntu_touch_installer_Kenzo_halium9_v4.zip
ubuntu_touch_installer_Kenzo_halium9_v2.zip
The sources
[https://github.com/mathew-dennis
[https://github.com/LineageOS
[https://github.com/Halium
[https://github.com/ubports
Thankyou
ubports community --> TheKit ,FlowHack, kn8rider divin, ari and everyone else
Redmi note 3 community --> thanks to all Dev's for keeping the device alive for the community .
This port would have never reached anywhere without their efforts..
And the truth is my efforts are very little as compared theirs...thank you ...
changelog
"Why not make something new from old code!" (Also because my pc can't handle A10+ builds)
v7
- updated to latest rootfs (ota-24)
V6
- updated to latest rootfs (ota-22)
- rebuild android image
- auto-brightness
V5. 1 (this is a patch for v5)
- bluetooth (everything else except file transfer )
- offline charging
- gps ( for real this time ) ( as ut dont have A-GPS support 1st fix might take 5+ min ,then it should work as normal)
v5
- gps is working now ( it's broken again)
-changed audio hal to a late start service
-enabled wireless display option (should work on miracast devices ) (not tested )
-fixes from ubports --> magnetometer and notification led is working and other fixes from ota 18 to ota 20
v4
- fixed issue with initial setup --thankyou Kn8Ryder
-audio should come up more often during boot than before
Telegram
If you are interested in bug fixing and contributing to this project , report a bug , click here to reach Telegram group

#Screenshots

what is default user password...

KrutosVIP said:
what is default user password...
Click to expand...
Click to collapse
"123" if u flashed old rom first, else "a"

mathew..denniss said:
"123" if u flashed old rom first, else "a"
Click to expand...
Click to collapse
ok, will try

Touch not working! after initial setup

mathew..denniss said:
"123" if u flashed old rom first, else "a"
Click to expand...
Click to collapse
Working for me, thanks for porting this amazing system.

BraveAmbush said:
Touch not working! after initial setup
Click to expand...
Click to collapse
For me the fix was to firstly install old ubuntu touch, load it and configure. After that,flash bootimage of new Ubuntu Touch with Halium9, then flash .zip with new Ubuntu Touch. It will give error, it is normal - go to /data/ and delete dir "ubports", then try again.
After that - just reboot, system will start with configured profile "Ubuntu"
The password is just "a"

Also, for me sound not working.

KrutosVIP said:
For me the fix was to firstly install old ubuntu touch, load it and configure. After that,flash bootimage of new Ubuntu Touch with Halium9, then flash .zip with new Ubuntu Touch. It will give error, it is normal - go to /data/ and delete dir "ubports", then try again.
After that - just reboot, system will start with configured profile "Ubuntu"
The password is just "a"
Click to expand...
Click to collapse
both flash may end with flash error that not a problem its a busybox compatibility thing.(not relevant )

KrutosVIP said:
Also, for me sound not working.
Click to expand...
Click to collapse
try a hard reboot(long press power button) .it should work afterwards

BraveAmbush said:
Touch not working! after initial setup
Click to expand...
Click to collapse

mathew..denniss said:
both flash may end with flash error that not a problem its a busybox compatibility thing.(not relevant )
Click to expand...
Click to collapse
For me deleting ubports helps to end without error-
When i don`t delete and get error, the system just don`t want to boot.
No animation, just black screen and when reboot

um that for me sound dont work too..
if not delete ubports in recovery and install, it 'll show a short black screen with a small mouse and reboot.
Also there are strange permission issues in the system dirty flashed from halium 7

Can I ask for some clarification? I managed to install the alpha version from your previous post, but how do you flash these update zips? I tried flashing them via TWRP on the device but I keep getting "recovery busybox setup failed" error.

jeangjenq said:
Can I ask for some clarification? I managed to install the alpha version from your previous post, but how do you flash these update zips? I tried flashing them via TWRP on the device but I keep getting "recovery busybox setup failed" error.
Click to expand...
Click to collapse
An update on this, after two more tries of reinstalling old ubuntu touch > flashing halium-boot through fastboot > Flashing zip through TWRP. It flash without issue and booted. Initially the sound isn't working, but after several weird restarts (select poweroff but it restarted, select poweroff but it froze on boot logo, etc etc), sound is working. This is a fun project

updated the flashable zip .. thankyou for the fix @Kn8Ryder

t
jeangjenq said:
Can I ask for some clarification? I managed to install the alpha version from your previous post, but how do you flash these update zips? I tried flashing them via TWRP on the device but I keep getting "recovery busybox setup failed" errotry v4
Click to expand...
Click to collapse
jeangjenq said:
Can I ask for some clarification? I managed to install the alpha version from your previous post, but how do you flash these update zips? I tried flashing them via TWRP on the device but I keep getting "recovery busybox setup failed" error.
Click to expand...
Click to collapse
try v4 ,it has some more fixess.busybox things are gone now

how many minutes does waydroid open to you ?

I did clean install
boot halium + v4 update
then install waydroid thru terminal
loading screen boot logo waydroid? is this alright?
im waiting to it