[APP][Beta]Virtual Home Button for Android Wear 2.0 [v3][30/09/18] - LG G Watch

First of all thanks to @ab123321 for porting Android Wear 2.0 to LG Watch G.
Note: I am not responsible for bricked devices, dead SD cards, or any problems that may arise from flashing this ROM.
Virtual Home Button for Android Wear 2.0​
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Description:
Today I have created a system app called Home Button which help us to simulate physical Home Button by tapping a virtual button.So we can use this virtual button to open a wear's default launcher and to complete the wear tutorial (After Reset / Fresh installation.No more paper clips). Also you can use this button on 3rd party app to simulate Home Button if its required.
Features:
Single Press to open android launcher.
Long Press to open Google Assistant.
Auto Start at Boot.
Screen position can be configured .
Transparency can be configured.
Installation:
System Image - App packed inside. This image is created using @ab123321's script. So same as ported rom with App packed inside.
Flash the system image provided below using fastboot.
Code:
fastboot flash system dory.img
Manual installation of APK: (Not necessary if you flashed system image using above method)
1. Create a folder called "HomeButton" under /system/app/
2. Copy the apk into the folder
3. Set permission to 644
4. Restart.
Download:
Version 3:
Note: If you are in version 2 and Google Assistant is working fine for you means you don't need this version. Only updated Google App to 8.20.13.25 and HomeButton to 3.0.0 in this version.
System Image: https://oload.win/f/9D-exXddqkQ/dory_v3.img
APK: https://oload.win/f/SbiakGiQaC8/HomeButton_v3.apk
http://www.mediafire.com/file/unhxocqbt6jbdhs/HomeButton_v3.apk/file
http://www.mediafire.com/file/2ccexhw8jdwr6c5/dory_v3.img/file
Version 2:
System Image: https://oload.win/f/2dvx9cn1Nyc/dory_v2.img
APK: https://oload.win/f/o2x4ZzBoK1Y/HomeButton_v2.apk
Mirrors:
http://www.mediafire.com/file/unhxocqbt6jbdhs/HomeButton_v3.apk/file
http://www.mediafire.com/file/2ccexhw8jdwr6c5/dory_v3.img/file
http://www.mediafire.com/file/35a6775f77d4y27/dory_v2.img
http://www.mediafire.com/file/3r8pz8z9xy2en24/HomeButton_v2.apk
Hash:
dory_v3.img
SHA1: 2FE8B8C23752F990DB1A83122014F92CC15C4E1F
HomeButton_v3.apk
SHA1: 50E3A6DACDD5B0DD7DE18CDE53718E16C5426C60
dory_v2.img
MD5: 84193D0600A5EA1A7C8BE0BE6D31F48C
SHA-1: B69062BF6B21160E42E687F6870DAE8F82F417B8
HomeButton_v2.apk
MD5: 039F379BF5E75000048E77FD5F6CFBB4
SHA-1: 1E6D15271F2551DAFB69E4755945C8C6F038B311

Oh! That's GREAT!

I flashed your system image, and it is working fantastically. Thank you. One word of warning for other users the first boot after flashing took around 10 minutes so don't panic just let it do it's thing.

Has anybody notice if they hold 2 fingers on the screen to turn it off it actualy triggers a command to open the app drawer. Maybe we could expand this built in feature.
---------- Post added at 10:20 PM ---------- Previous post was at 10:11 PM ----------
can anybody help my pc wont pick up my watch in fastboot mode after the wear 2.0 update
---------- Post added at 10:31 PM ---------- Previous post was at 10:20 PM ----------
finally got abd to work and fastboot devices lists my watch now but the home button img will not install it comes up uknown error data transfer failed? please help.

Finally fixed all the errors and it has installed correctly now but the ROM is very unstable, constantly crashing,freezing and jamming up and the button is often non responsive. The other port for this without home button runs flawlessly so maybe collaborate on the project and intergrate each other works into one project.

brostar2017 said:
Finally fixed all the errors and it has installed correctly now but the ROM is very unstable, constantly crashing,freezing and jamming up and the button is often non responsive. The other port for this without home button runs flawlessly so maybe collaborate on the project and intergrate each other works into one project.
Click to expand...
Click to collapse
Are you sure? Anyone else facing this issue?
I'm using this rom from last 7 days. I'm not facing any issue or any lagging.
FYI,I'm using this boot image. https://forum.xda-developers.com/showpost.php?p=73743155&postcount=511

Using the same image and the watch is barely usable with this image across multiple g watches. The other one without but is smooth and instant responds.

Updated.
Changelog:
New system image. (Unpacked @ab123321's latest system image and packed with apk)
Long press to open Google Assistant

brostar2017 said:
Using the same image and the watch is barely usable with this image across multiple g watches. The other one without but is smooth and instant responds.
Click to expand...
Click to collapse
Can you try new system image? Because this image is created by unpacking ab123321's original image and packed with apk.

install manual
How i install manual this program? i guess with minimal adb. i don't want to flash that file on my watch again. can someone do a tutorial? please!

the new system image is amazing, super fast and responsive now and it opens when you push on it and long press now works.

working. tnq

svprm said:
Can you try new system image? Because this image is created by unpacking ab123321's original image and packed with apk.
Click to expand...
Click to collapse
Same problem here. "adb install" yields:
Failed to install ...: Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE: Package couldn't be installed in /data/app/cyb.satheesh.homebutton-1: Package cyb.satheesh.homebutton has no signatures that match those in shared user android.uid.system; ignoring!]
adb push ...\HomeButton_v2.apk /system/app
adb: error: failed to copy '...\HomeButton_v2.apk' to '/system/app/HomeButton_v2.apk': couldn't create file: Read-only file system
(sorry for the newbie questions)

jreschke said:
Same problem here. "adb install" yields:
Failed to install ...: Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE: Package couldn't be installed in /data/app/cyb.satheesh.homebutton-1: Package cyb.satheesh.homebutton has no signatures that match those in shared user android.uid.system; ignoring!]
adb push ...\HomeButton_v2.apk /system/app
adb: error: failed to copy '...\HomeButton_v2.apk' to '/system/app/HomeButton_v2.apk': couldn't create file: Read-only file system
(sorry for the newbie questions)
Click to expand...
Click to collapse
Looks like you don't have permission to install it on /system.So you have to use system.img.

diabolik99 said:
How i install manual this program? i guess with minimal adb. i don't want to flash that file on my watch again. can someone do a tutorial? please!
Click to expand...
Click to collapse
If your watch is rooted and system can be mounted as RW, then you can follow the manual installation. But as of now, our AW 2.0 rom is using Squash filesystem. We can't mount system as RW in squash filesystem. So you have to flash this system.img over AW 2.0 rom to get this work.

svprm said:
If your watch is rooted and system can be mounted as RW, then you can follow the manual installation. But as of now, our AW 2.0 rom is using Squash filesystem. We can't mount system as RW in squash filesystem. So you have to flash this system.img over AW 2.0 rom to get this work.
Click to expand...
Click to collapse
Thanks for the explanation. I now installed just the new system image (without erasing anything), and rebooted (which only took little time). Home button is now there, thanks alot!

Flashed the img and it has been working great for over a week.
I experienced the same bootloop as the original aw 2.0 port, which was solved by following this guide: https://forum.xda-developers.com/g-watch/general/tutorial-avoid-bootloop-porting-wear-2-0-t3656825

So thought I would join in on this seeing as this community is all but dead, I have installed and this is the best thing ever to happen to this device. AW2 runs just fine on this device and adding this home button makes it a lot easier to bring up Google Assistant and the app drawer. This device is still perfect for reading off notifications or getting a quick weather update.
I really hope this community stays alive seeing as Android Oreo will be making its way to AW soon.
Thanks for the virtual home button, it's a must have.

Will the Dev continue to support this watch for wear Oreo?

brostar2017 said:
Will the Dev continue to support this watch for wear Oreo?
Click to expand...
Click to collapse
I don't know if there will be wear based on Oreo.
Hopefully I'm wrong.
The lenok2dory was port of Android Wear 2 for the G watch R, and it isn't getting Oreo.

Related

[WINDOWS]aPkgMan - Easy batch install/uninstall/rename/backup APK packages ^2012/4/16

Just having fun around with Android so I made this little program aPkgMan
Features
Very light-weight (less than 45KB, just extract and run)
Batch install APK packages via ADB (restore data option available)
Batch uninstall APK packages via ADB
Batch backup APK packages via ADB (backup data option available)
Batch renaming APK packages (using file mask)
Check for online version of APK packages
v0.1
http://i.imgur.com/4VEhD.png
v0.2
http://i.imgur.com/vvhk7.png
v0.3
http://i.imgur.com/vkZfM.png
v0.4
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to use?
Download, extract and run
Enable USB debugging mode on your device, connect it to computer via USB cable and select it from the Home tab (Hit Refresh to refresh the connected device list)
You are ready to go
Tip : If the program won't start, open Task Manager and kill the "mshta.exe" process and restart the program
Changelog
2012/04/01 - Initial version
2012/04/02 - v0.2, added batch renaming (support file mask) and backup packages
2012/04/05 - v0.3, added restore package data after installing, added backup data for package; plus code cleaning and commenting and other minor improvements
2012/04/16 - v0.4, added new feature checking for online version of APK packages
aPkgMan is absolute free. Any questions, comments or suggestions are welcome. If you find it useful please click Thanks button below
Good Work
wow, this will be very helpful.
just a question, would this backup app+settings?
thanks!
melander said:
wow, this will be very helpful.
just a question, would this backup app+settings?
thanks!
Click to expand...
Click to collapse
I'm about adding backup/restore feature and a simple file manager too
Thanks man
2012/04/02 - v0.2, added batch renaming (support file mask) and backup packages To restore use the batch install feature
The next things to do are supporting ADB over WiFi and a file manager.
I use "pull" command to backup app data but ADB returns "0 files pulled. 0 files skipped". Can anybody tell me why please?
Hm,i'm havin problem with picking apk path
Sent from my SK17i using xda premium
Black_jackss said:
Hm,i'm havin problem with picking apk path
Sent from my SK17i using xda premium
Click to expand...
Click to collapse
Hi, can you tell me where the problem occurred please? And did the program return any error message?
acb123 said:
Hi, can you tell me where the problem occurred please? And did the program return any error message?
Click to expand...
Click to collapse
It's just i didnt understand how to pick the apk i want to install
Sent from my SK17i using xda premium
New v0.4 as of 2012/04/16, added new feature checking for online version of APK packages Some packages will return "Not Found" since they are no longer on Play Store.
acb123 said:
2012/04/02 - v0.2, added batch renaming (support file mask) and backup packages To restore use the batch install feature
The next things to do are supporting ADB over WiFi and a file manager.
I use "pull" command to backup app data but ADB returns "0 files pulled. 0 files skipped". Can anybody tell me why please?
Click to expand...
Click to collapse
I am having the same issue in an app I am building for the Acer a510.
Or should I say, WAS having.
Bad Code
Code:
adb pull /system/app/ /Backups/system/app
Good Code
Code:
adb pull /system/app/ ./Backups/system/app
The difference for me was the " . " for the destination.
It was creating the files on my root C:\ drive instead of the
intended directory. I pulled the entire contents where I want now.
I am not sure if this will help you at all, but I thought I would share.
***EDIT***
It worked until I got to /data/app
There is where I got the same error.
"0 files pulled. 0 files skipped"
After changing permissions on the folder,
everything pulled.
marlopainter said:
I am having the same issue in an app I am building for the Acer a510.
Or should I say, WAS having.
Bad Code
Code:
adb pull /system/app/ /Backups/system/app
Good Code
Code:
adb pull /system/app/ ./Backups/system/app
The difference for me was the " . " for the destination.
It was creating the files on my root C:\ drive instead of the
intended directory. I pulled the entire contents where I want now.
I am not sure if this will help you at all, but I thought I would share.
***EDIT***
It worked until I got to /data/app
There is where I got the same error.
"0 files pulled. 0 files skipped"
After changing permissions on the folder,
everything pulled.
Click to expand...
Click to collapse
Thank you so much for your sharing On my Sk17i I also changed the folder permission too but still didn't work, but upgrading to custom ROMs makes it work. I will note your solution in the next update of the program so it could help other users
acb123 said:
Thank you so much for your sharing On my Sk17i I also changed the folder permission too but still didn't work, but upgrading to custom ROMs makes it work. I will note your solution in the next update of the program so it could help other users
Click to expand...
Click to collapse
The way I changed permissions was in Root Explorer.
I believe the way I changed them made it 777, not sure.
hi man, thanks for sharing your work!!
it's a really useful program, I just used it to delete a theme apk: I applied the theme (CM 7) and when I reboot my phone had a bootloop!
just a question: why is this software not into the general development section? Here is hard to find it!
anyway, a great alternative for people who don't / are not able to use adb..
see you!
brainvision said:
hi man, thanks for sharing your work!!
it's a really useful program, I just used it to delete a theme apk: I applied the theme (CM 7) and when I reboot my phone had a bootloop!
just a question: why is this software not into the general development section? Here is hard to find it!
anyway, a great alternative for people who don't / are not able to use adb..
see you!
Click to expand...
Click to collapse
It's almost a year and suddenly a new post appeared. Thanks for your interest ! I also hope I could find way to update it in the future.
hi acb123, a really nice little tool you developed!
do you think there would be any way that the uninstall menu does not show every single installed "app", but only the ones that the user installed and can be actually removed?
download link???????
i-HaBiB said:
download link???????
Click to expand...
Click to collapse
Check the attachments in first post

[UPDATE] Remix OS for PC update 3.0.103

In keeping with our weekly update schedule, Remix OS for PC version 3.0.103 update is now available OTA.
Please use the 'System update' app found in your app drawer to initiate the update.
Release notes:
Remix OS for PC version: 3.0.103
Release date: August 9, 2016
Setup wizard now skips Wi-Fi connection step if LAN is connected
File Launcher now aligns icons to grid
GMS can now be activated during the setup wizard
Key-mapping tool now enabled by default
Fixed more Wi-Fi issues
Fixed App drawer crashing when ‘Search’ nets no results
Fixed wallpaper distortion
Important note:
If you have key-mapping tool and/or GMS disabled in version 3.0.102, updating to version 3.0.103 will cause problems if you want to activate these apps in 3.0.103.
If you plan to use these apps, we advise you first activate these apps while still running 3.0.102 before updating to version 3.0.103.
If you have no plans to use either of these apps, you don't need to do anything.
Thanks for the update. Please in next update, fix Video playback issues.
hi , nice job ..
i want to esposing two problems
i have an wacom graphic tablet , everithing work , also push sensitivity of the pen... it work perfectly on classic launchers but on remixos launcher doesnt work double tap and the trag and grab of the icons ... expecially on the app launcher and the file manager
another problem is with the logitech wireless keyboard, the extra key's (volume up and down, music player , mail etc..) doesnt't work ... on the remixos 2.x it work perfectly
thanks for the nice wok
I see it.. but when trying to install:
Start updating..
SRC=/android-2016-08-03
ui_printWaning: No file_contexts
script aborted: system partition has unexspected contents
ui_print system partition has unexspected contents
ui_print
error in data/media/0/autoupdater/otapackage.zip (status 7)
update failed
---
any otherway to update?
-I did noticed the the actual update zip is not called Otapackage.zip
My RemixOS 32bit is installed on sda2/ext4/30gb (using INSTALL=1 with Nvidiacard modeset )
Cheers
Wi-Fi doesn't connect reliable
I am working with version 3.0.103 32bit on a Lenovo T400. Remix OS has been installed on a partition of the hard drive (boot option INSTALL=1). After starting Remix OS in most cases the Wi-Fi is not connected automatically, as long as the "Wi-Fi" pop-up window is not opened yet. After opening the Wi-Fi pop-up window Wi-Fi is connected automatically a few seconds later. So it's not a big problem, just not comfortable.
mitchell4you said:
I see it.. but when trying to install:
Start updating..
SRC=/android-2016-08-03
ui_printWaning: No file_contexts
script aborted: system partition has unexspected contents
ui_print system partition has unexspected contents
ui_print
error in data/media/0/autoupdater/otapackage.zip (status 7)
update failed
---
any otherway to update?
-I did noticed the the actual update zip is not called Otapackage.zip
My RemixOS 32bit is installed on sda2/ext4/30gb (using INSTALL=1 with Nvidiacard modeset )
Cheers
Click to expand...
Click to collapse
Got the same error. Unfortunately torrent from the site is 3.0.103 so can't update the normal way.
mitchell4you said:
I see it.. but when trying to install:
Start updating..
SRC=/android-2016-08-03
ui_printWaning: No file_contexts
script aborted: system partition has unexspected contents
ui_print system partition has unexspected contents
ui_print
error in data/media/0/autoupdater/otapackage.zip (status 7)
update failed
---
any otherway to update?
-I did noticed the the actual update zip is not called Otapackage.zip
My RemixOS 32bit is installed on sda2/ext4/30gb (using INSTALL=1 with Nvidiacard modeset )
Cheers
Click to expand...
Click to collapse
The update of an "INSTALL=1" installation is described here .
In order to perform the update you need to start a Linux operating system using a pendrive (e.g. PartedMagic), in order to rename the basic directory from /android-2016-08-03/ to /android-2016-08-08/ and in order to delete all directories within the basic directory other than /android-08-08/data.
After this step you can perform a normal installation (INSTALL=1), but you must not format your partition sda2 because you want to keep your data.
Ahh... i still cant boot / install on Chuwi Vi10 Pro. I stuck here again:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks the update went flawlessly.
For some reason, I got again the error with the Playstore and the communication problems with the google service. Did I do anything wron, during the install process? I did a clean install and chose to go with the GSM in the wizard.
hundsboog said:
For some reason, I got again the error with the Playstore and the communication problems with the google service. Did I do anything wron, during the install process? I did a clean install and chose to go with the GSM in the wizard.
Click to expand...
Click to collapse
Did you remember immediately to reboot after using the GSM wizard? If you try to use the Playstore without rebooting first then it won't work.
lollyjay said:
Did you remember immediately to reboot after using the GSM wizard? If you try to use the Playstore without rebooting first then it won't work.
Click to expand...
Click to collapse
Yes Sir, I waited till the wizard was done and did a reboot immediately without touching anything.
remixtester said:
The update of an "INSTALL=1" installation is described here .
In order to perform the update you need to start a Linux operating system using a pendrive (e.g. PartedMagic), in order to rename the basic directory from /android-2016-08-03/ to /android-2016-08-08/ and in order to delete all directories within the basic directory other than /android-08-08/data.
After this step you can perform a normal installation (INSTALL=1), but you must not format your partition sda2 because you want to keep your data.
Click to expand...
Click to collapse
Hmm..
Then I'm giving-up.. ( till this gets resolved )
First I installed the 27jul build.. that hat no update... then I installed aug3 build with updater..
An now it seems.. the updater doesnt work...
This downloading the full ISO every week.. is not for me..
i did a ''pm disable com.jide.autoupdate' to stop it nagging
-- Bah.. if you disable the updater.. the taskbar no longer works ( thumz down )
Cheers
Thanks Devs.
Updated without a hitch
Wireless not connecting automatically on boot is fixed on my aspire V5-122p
Standby still broken but I can live with that.
Thanks your work! I try many version after, even 3.0.103 but can't make it work with Clover Bootloader, when add entry Remix OS into Clover boot by path: EFI\Boot\grubx64.efi but nothing happen, just dark screen.
Only with this version i can make it work with Clover boot loader.
Would you fix it, please sir?
NO I upgrade , I have version 3.0.102 I open the app to update and give closes click download and not download anything.
Good
I updated new version remix os is ok ^^ ! No problem, can only hope the next version will support HDMI out TV : Good:
hundsboog said:
Yes Sir, I waited till the wizard was done and did a reboot immediately without touching anything.
Click to expand...
Click to collapse
same here. error to communicating with google server. any advise?
please get touch screen working for surface 3
Game Toolkit is still not showing up for me. I came straight from 3.0.102 even then it didn't show even when enabled.

How to root the Amazon Fire TV 2 box running latest software version 5.2.6.8

I can confirm that this process works on Update v5.2.6.8. Any other version beyond that your mileage may vary. "ADB debugging" and "Apps from Unknown Sources" should be enabled. I would like to thank the following members because without their resources this walkthrough wouldn't have been possible: @diplomatic for the exploit, @el7145 for leaving a cookie crumb trail of clues within his comments in this thread which I had to follow like the yellow brick road in order to repeat his success, @rbox for the custom recovery and pre-rooted image, and @AFTVnews.com because if it hadn't been for your article I probably would've never gotten my AFTV device rooted in time before the 5.2.6.9 OTA update. Oh, I almost forgot... and thanks @Chainfire for SuperSU . And also @teamfresno for the advice.
ACHIEVING TEMPORARY ROOT PERMISSIONS
1. Download and install ADB on your PC.
2. Download "mtk-su_r4.zip" and extract "arm64" folder in ADB install directory (C:\adb).
3. Run command below:
Code:
adb connect 192.168.0.XX
(IP address of your Fire TV device)
4. Transfer mtk-su to your /data/local/tmp folder:
Code:
adb push C:/adb/arm64/mtk-su /data/local/tmp/
5. Open an adb shell:
Code:
adb shell
6. Change to your tmp directory:
Code:
cd /data/local/tmp
7. Add executable permissions to the binary:
Code:
chmod 755 mtk-su
8. Run the exploit:
Code:
./mtk-su
NOTE – The following line should display:
New UID/GID: 0/e
9. Ensure that mtk-su succeeded in setting selinux to permissive by typing the following command:
Code:
getenforce
INSTALLING TWRP & SLOANE
1. Download rbox's TWRP custom recovery and the latest pre-rooted ROM from your PC and copy it to the root of a USB stick [or microSD card].
2. Connect the USB stick [or microSD] to your AFTV2.
3. Change to USB Storage directory:
Code:
cd /storage/usbotg/
NOTE – If recovery is on microSD
Code:
cd /storage/sdcard1
4. Run the zip file. This will automatically run SU:
Code:
sh /storage/usbotg/firetv2_recovery_v7.zip
If recovery is on microSD
Code:
sh /storage/sdcard1/firetv2_recovery_v7.zip
NOTE – It should print out a following lines:
Extracting unzip...
Remounting /system read-write...
Extracting...
Remounting /system read-only...
5. Reboot to Recovery:
Ctrl+C (closes out previously ran script)
Code:
adb reboot recovery
6. Your AFTV2 should reboot to a black screen displaying the Amazon logo, followed by a prompt stating that the device will automatically restart, but if not to unplug then re-plug the power source. It will not automatically restart, but DO NOT unplug the device yet.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7. If you copied the recovery and ROM onto a USB stick then you will need to disconnect it from the AFTV2, and connect a USB hub with at least 2 ports to the AFTV2, and connect both a USB keyboard and the USB stick to the hub at this time. If you copied the recovery and ROM onto a microSD then connect a keyboard to the empty USB port at this time.
8. Now unplug then re-plug the power source and you will be presented with the TWRP splash screen.
9. At the boot menu, press the RIGHT arrow key on the USB keyboard to boot into TWRP recovery.
NOTE – whatever you do DON'T let your AFTV2 idle for too long on the initial recovery boot menu screen or it will time out thus restarting, requiring you to repeat the prior steps.
10. Use the arrow keys to select the "Install" in TWRP.
11. "Select Storage", and choose the location where you stored the pre-rooted ROM.
12. Select "Swipe to Confirm Flash" to start the installation.
13. Select "Reboot System" once the file has finished installing in order to restart the AFTV2.
For those feeling a little adventurous/ambitious then feel free to follow this guide created by @g422 as he discuses where to go from here by delving into other avenues to truly tap into the power of your AFTV2 such as what's "Xposed" and the benefits it offers for rooting your device, and also how to backup your current Fire OS install using TWRP.
Also shouts out to @PhoenixMark who created a guide for Mac users based on my write-up as how to enable root here.
This will work if we have a bricked device stuck on the Amazon logo?
Thanks for this! can't wait till I get home and finish the process with your guide. Other guides had my head spinning. Achieved temp root but no mention of pushing super su.
Oh wow, looks like that exploit spread like wildfire!!
Wonder if anybody will see if this works for the firestickv2 (I don't trust myself to crack the case of mine open lol)
b0ricuaguerrero said:
Thanks for this! can't wait till I get home and finish the process with your guide. Other guides had my head spinning. Achieved temp root but no mention of pushing super su.
Click to expand...
Click to collapse
Worked like a charm on my fire tv 2, but I did notice voice control seems to be broken after achieving permanent root.
Anyone else experienced this????
Thank you for putting this guide together! Also thanks to @rbox for twrp and the rom!Finally got root on my Fire TV 2!
Sent from my SM-G9650 using Tapatalk
worked flawlessly on Amazon fire tv 2, the only thing i would say about the instruction for me was that usbotg was not recognised I only had sdcard0 (int storage) sdcard1 (sd card) apart from that great job thank you
ps there was an update waiting to install from amazon which i blocked, perhaps they are patching already
JUSTINMARMER said:
This will work if we have a bricked device stuck on the Amazon logo?
Click to expand...
Click to collapse
Idk. I think we're pretty much in the same boat now: https://forum.xda-developers.com/showpost.php?p=79063299&postcount=197
Delete... duplicate comment
b0ricuaguerrero said:
Thanks for this! can't wait till I get home and finish the process with your guide. Other guides had my head spinning. Achieved temp root but no mention of pushing super su.
Click to expand...
Click to collapse
Not a problem. Just giving back where I can
b0ricuaguerrero said:
Worked like a charm on my fire tv 2, but I did notice voice control seems to be broken after achieving permanent root.
Anyone else experienced this????
Click to expand...
Click to collapse
I don't use voice activation, voice assistants, etc. as a preference. I'm just paranoid like that
huffmybrd said:
Oh wow, looks like that exploit spread like wildfire!!
Wonder if anybody will see if this works for the firestickv2 (I don't trust myself to crack the case of mine open lol)
Click to expand...
Click to collapse
It's worth looking into. Since I currently own one as well I'll see a/b performing these same instructions and post my findings at some point in time.
salsoul said:
worked flawlessly on Amazon fire tv 2, the only thing i would say about the instruction for me was that usbotg was not recognised I only had sdcard0 (int storage) sdcard1 (sd card) apart from that great job thank you
ps there was an update waiting to install from amazon which i blocked, perhaps they are patching already
Click to expand...
Click to collapse
I tried both ways, with the microSD and USB so I know it works if you followed what was stated in the instructions to the T... I know that when I attempted the USB option the first time, I had forgot to plug the USB stick in which made it show up as USB (0) which is only logical explanation I can think of for what happened to you.
Krog18 said:
Thank you for putting this guide together! Also thanks to @rbox for twrp and the rom!Finally got root on my Fire TV 2!View attachment 4718781
Sent from my SM-G9650 using Tapatalk
Click to expand...
Click to collapse
Not a problem, glad I could help
This is fantastic work!!!
Do you know if root can be 'hidden' to Netflix app won't block it's use?
n8wwd said:
This is fantastic work!!!
Do you know if root can be 'hidden' to Netflix app won't block it's use?
Click to expand...
Click to collapse
Thanks, and unfortunately, no. SuperSU is the component that enables root which can be detected by apps that disengage user functionality when they discover root is enabled. I attempted to install Magisk v18.1 to counteract this side effect, but failed miserably w/ the end result to the point that my AFTV2 does a constant boot loop as recounted here. Magisk would be the only option I'm aware of to make root 'hidden', but it's not worth it at the cost of turning your device into a boot looping paper weight.
True. Nothing like having a 'brick on a rope' so to speak. That's not a 'deal breaker' as I subscribe to IPTV services that out performs it anyway. Do you know if Hulu does the same as Netflix? The missus may take exception if it killed that...
---------- Post added at 12:22 AM ---------- Previous post was at 12:20 AM ----------
I guess the main reason I'd want root access is to take all of the preloaded apps off for room, as well as have the ability to use the external storage within apps.
---------- Post added at 12:48 AM ---------- Previous post was at 12:22 AM ----------
well...I answered my own question..seems Hulu doesn't like it either...*sigh* Time to search for a box that can hide root so my wife won't blow a gasket....
Wait, we can't use Netflix if we are rooted? Yikes.
I've had no trouble with Netflix yet since I rooted this yesterday, but of course ymmv.
Sent from my SM-G9650 using Tapatalk
---------- Post added at 08:36 AM ---------- Previous post was at 07:44 AM ----------
urbanman2004 said:
Thanks, and unfortunately, no. SuperSU is the component that enables root which can be detected by apps that disengage user functionality when they discover root is enabled. I attempted to install Magisk v18.1 to counteract this side effect, but failed miserably w/ the end result to the point that my AFTV2 does a constant boot loop as recounted here. Magisk would be the only option I'm aware of to make root 'hidden', but it's not worth it at the cost of turning your device into a boot looping paper weight.
Click to expand...
Click to collapse
Damn, sorry to hear that. I imagine what happened is the result of magisk patching the kernel on a locked bootloader. I hope you're able to get it fixed. Good luck to you!
Sent from my SM-G9650 using Tapatalk
Krog18 said:
Damn, sorry to hear that. I imagine what happened is the result of magisk patching the kernel on a locked bootloader. I hope you're able to get it fixed. Good luck to you!
Sent from my SM-G9650 using Tapatalk
Click to expand...
Click to collapse
Thanks. You never know, somebody smart enough might actually come up with a tool capable of relieving my device from its eternal boot loop hell

[ROM][F5121][WIP] Ubuntu Touch for Sony Xperia X

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A Mobile Version of the Ubuntu Operating System
Ubuntu Touch is made and maintained by the UBports Community. A group of volunteers and passionate people across the world. With Ubuntu Touch we offer a truly unique mobile experience - an alternative to the current most popular operating systems on the market. We believe that everyone is free to use, study, share and improve all software created by the foundation without restrictions. Whenever possible, everything is distributed under free and open source licenses endorsed by the Free Software Foundation, the Open Source Initiative.
For more information check out the UBports website.
Known issues:
Recording video doesn't work
Changing volume in-call doesn't work
Contribute:
As not everything is working fully yet helping hands are welcome!
Follow the project management issue over at the Halium GitHub page:
https://github.com/Halium/projectmanagement/issues/98
Instructions (tested on Ubuntu 18.04):
First make sure to wipe /system & /data from within TWRP. The partitions must be ext4.
Make sure to upgrade your device to the latest stock Android 8.0 before continuing: https://developer.sony.com/develop/open-devices/get-started/flash-tool/
Download and install the UBports installer: https://github.com/ubports/ubports-installer/releases
OEM unlock your device: https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
Boot your device into fastboot mode by shutting it down and keeping the Volume Up button pressed while plugging in a USB cable between your phone and PC. The LED should be on and blue.
Flash the OEM binaries from: https://developer.sony.com/file/download/software-binaries-for-aosp-nougat-android-7-1-kernel-4-4-loire/ using:
Code:
fastboot flash oem SW_binaries_for_Xperia_AOSP_N_MR1_5.7_r1_v08_loire.img
Run the UBports installer and follow the on-screen instructions
Reserved for future use
wtf bro i never expected to see ubuntu touch on any device again great news and good work! keep it up!
Too bad my device broke......gotta fix fast lol
I've updated download links and the instructions to enable call functionality. Testers welcome!
Ready for tests! Just need to install Ubuntu with current manual
Have I need to flash stock rom with android 7 or just flash binaries on stock android 8?
New tests to be done, we've recently gotten video decoding to work and I enabled basic camera support.
OP has been updated with the link to the newest images.
Feel free to post issues here if you are not feeling well with GitHub.
Regarding stock ROM or not:
Any system image should work, you can even wipe system as it's not used.
As long as the ODM partition is flashed everything should be good.
I'm trying this for the 2nd time and both times I can't get any audio in calls. I ran the commands in the first post. Any tips on what else to try? I'd really like to try this, test some more and help out, but it's the only phone I've got right now.
samijam said:
I'm trying this for the 2nd time and both times I can't get any audio in calls. I ran the commands in the first post. Any tips on what else to try? I'd really like to try this, test some more and help out, but it's the only phone I've got right now.
Click to expand...
Click to collapse
Did you run the commands through ssh or via the Terminal app? Mind doing a "select all" and copy-paste the output to some paste service?
EDIT: Also, did you reboot after issuing the commands?
Thanks for the work on this.
I need a little bit more explanation on how to install this. I gave it a try, but I end up in getting a white boot screen with the sony logo. Installing SailfishOS with the flash.sh script works perfectly.
Questions:
- When do you need to use twrp? When running adb?
- Running the halium install script only works when booted into twrp. Is this correct?
- Do you need to manually boot into fastboot mode (volume up, blue led)?
- The sailfish installation uses oem for android 6, here 7 is used. Can this make the difference?
Thanks for any support.
beidl said:
Did you run the commands through ssh or via the Terminal app? Mind doing a "select all" and copy-paste the output to some paste service?
EDIT: Also, did you reboot after issuing the commands?
Click to expand...
Click to collapse
Sorry for the late reply. I got it to work now. My problem was using an outdated system.img and boot.img. (oops, sorry, my bad!) I had downloaded the newer versions, but had them in the wrong directory. Once I deleted the old and installed the correct versions, I was able to get audio in calls and had the basic camera functionality.
---------- Post added at 16:43 ---------- Previous post was at 16:37 ----------
matiz098 said:
Thanks for the work on this.
I need a little bit more explanation on how to install this. I gave it a try, but I end up in getting a white boot screen with the sony logo. Installing SailfishOS with the flash.sh script works perfectly.
Questions:
- When do you need to use twrp? When running adb?
- Running the halium install script only works when booted into twrp. Is this correct?
- Do you need to manually boot into fastboot mode (volume up, blue led)?
- The sailfish installation uses oem for android 6, here 7 is used. Can this make the difference?
Thanks for any support.
Click to expand...
Click to collapse
boot into fastboot and flash the oem:
fastboot flash oem SW_binaries_for_Xperia_AOSP_N_MR1_5.7_r1_v08_loire.img
then boot into twrp recovery and wipe /system and /data
while in twrp, run the halium-install.sh script (because the computer needs to connect to phone in adb mode, which twrp provides)
following from there, as you see in the first post, you will run "adb reboot bootloader" (but I think I did have to do it manually) which should put you back into fastboot mode where you'll "fastboot flash boot halium-boot.img"
then you should be able to reboot into ubuntu. The first boot takes a little longer.
Are there any screenshots available?
Fajormein said:
Are there any screenshots available?
Click to expand...
Click to collapse
No but you can find some videos on YouTube, just search for "Ubuntu Touch 2019".
The videos might feature different phones but it's the same on the Xperia X.
Is there any way to install it using a windows pc?
Fardin Rehman said:
Is there any way to install it using a windows pc?
Click to expand...
Click to collapse
Not currently.
please make a porting for kugo (x compact) sir
rizky_zulfikar said:
please make a porting for kugo (x compact) sir
Click to expand...
Click to collapse
Someone else is working on that already, but this port is only for the Xperia X (F5121).
In other news:
Installation instructions have been updated, the Xperia X port is now available from the UBports community channel!
Can you make port for XA 2 (H3113)
As I get the question very often: To support the F5122 variant of the Xperia X (or other devices in general) for Ubuntu Touch I need donations to buy the device.
Use the "Donate To Me" button on XDA or head over to https://fredl.me/donate/ for info on how to do so.
In other news: The Xperia X F5121 has gained support for the official UBports installer. You can now flash the device using a fancy GUI.
I hit 2 problems. For some reason neither Emma nor flashtool wants to flash stock rom correctly. Tried to flash ubuntu through stock 8.0 custom rom, phone reboots and black screen. Also there is was an error with something that the file couldn't be sent to the phone
Click to expand...
Click to collapse
Ok, so I did install the stock rom through EMMA fine. I did enable the usb debugging, installed twrp, wiped system & data, made sure they are EXT4. Rebooted to fastboot, installed SW binaries. Opened UBports Installer & proceeded with instructions. I got this error
Code:
Error: systemimage: Error: Error: {"error":{"killed":false,"code":1,"signal":null,"cmd":"C:\\Users\\domin\\AppData\\Local\\Temp\\1Uo4H80AYPnCivmpnC8M9LLWxLb\\resources\\app.asar.unpacked\\platform-tools\\win\\adb -P 5037 shell mount -a"},"stdout":"","stderr":"mount: mounting /dev/block/bootdevice/by-name/userdata on /data failed: Invalid argument"}
Any solutions, did I miss something? I gonna retry without the twrp step, as I am pretty sure the partition format will be EXT4

[Q][ROM][Treble] Treble Zoom

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- = Treble Zoom = -​
This custom ROM based on Havoc-OS 3.5.
Prerequisites - bootloader must be unlocked, clean Stock firmware and TWRP must be installed.
What's done:
- integrated GAPPS (Play Market, Chrome, Google Dialer, Messages, Contacts, etc.), but nothing extra. YouTube has been removed because I use YouTube Vanced);
- installed Nova Launcher (I recommend using it as the main one), RootExplorer, Asus File Manager (for simple tasks), Asus Gallery, AdAway ads blocker, Motor Command Center 2;
- integrated Moto camera from the latest firmware draining. Fully working with the work of all camera modules! In addition the best, in my opinion, for this ROM and our phone Google Camera mod;
- working Adaptive Brightness;
- cleaned up and made the system a little bit easier.
Installation Instruction
1. Download the Project Treble system image archive. Unpack the archive and copy the ROM image to an external SDCard.
2. Copy to external SD Card Magisk Installer https://github.com/topjohnwu/Magisk (latest version for today Magisk v20.4), Disable_Dm-Verity_ForceEncrypt https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 (latest version for today Disable_Dm-Verity_ForceEncrypt_03.04.2020 https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip ) and Permissiver_v4 (see attachments)
3. Reboot in TWRP and go to the "Wipe" tab, "Advanced Wipe" and select Dalvik, System, Data, and then go back two steps back and do a "Swipe Factory reset".
4. Install the Treble Zoom system image. In the "Install" tab in the lower right corner click "Install image" and select ROM Image. A window will open in which you should select partition "System Image" in which the image where to be installed. Swipe for confirm flash.
5. When the installation is complete, go to "Wipe" and perform a "Format Data".
6. Install the Magisk.zip, Disable_Dm-V_ForceEncrypt.zip and Permissiver_v4.zip. Reboot into the system and make the settings, use the Project Treble working system.
The first launch will be a bit long, don't worry and be happy!
Noticed problems on Treble Zoom - Does not pass SafetyNet check (ctsProfile: false; basicIntegrity: true). On Google Play, your device is not certified, but applications are installed and updated. Wired headphones are plugged in. When connected, the Bluetooth headset in the Dialer application works, but when listening to audio, video, YouTube is not.
Fingerprint Unlocking by fingerprint is implemented for scanners on the back of the phone. This problem can be corrected in the following way:
Connect the device to your PC and enter the following commands
Code:
adb shell
su
setprop persist.sys.fp.fod.location.X_Y 450,1760
setprop persist.sys.fp.fod.size.width_height 194,194
reboot
A green circle will appear in the display of your device, which is responsible for your fingerprint.
Niiiiice!!! I will try it ?
It Is Android 10?? You have some screenshot??
Does the fingerprint under the display work with this ROM?
Honzule89 said:
It Is Android 10?? You have some screenshot??
Click to expand...
Click to collapse
Yes, it's Android 10.
No screenshots. It's like Andriod 10.
Honzule89 said:
Does the fingerprint under the display work with this ROM?
Click to expand...
Click to collapse
Unlocking by fingerprint is implemented for scanners on the back of the phone.
Moto Zoom has a fingerprint under the display, which means that this reader will be inoperative and the phone can only be unlocked with a gesture or pin. It is a great pity. I will not install this ROM. But still great work
Honzule89 said:
Moto Zoom has a fingerprint under the display, which means that this reader will be inoperative and the phone can only be unlocked with a gesture or pin. It is a great pity.
Click to expand...
Click to collapse
This is GSI. This is a basic image of the firmware, not for a concrete model. Are you ready to donate for Moto Oe Zoom specific firmware development?
Honzule89 said:
I will not install this ROM.
Click to expand...
Click to collapse
The choice is yours. No one is forcing anyone. It's just that up until now it hasn't been possible to get a working system on Android 10.
After the flashes I get this:
Failed to mount '/system's (Invalid argument)
After I unpack the image zip, I rename to .img, maybe that's why, help me please...
ilia3367 said:
Yes, it's Android 10.
No screenshots. It's like Andriod 10.
Click to expand...
Click to collapse
You're truly incredible, thank-you SOOOOOO much for your work. :laugh:
It's amazing that unofficial development is an entire OS version better than OEM work! :good:
Hi,
nice job....i would donate for development....fix bluetooth?
giar72 said:
....fix bluetooth?
Click to expand...
Click to collapse
I tried to fix it, but I couldn't...
sorry...
Hell yeah, nice work. Probably not going to install it since I rely on Google pay and Bluetooth headphones regularly, but it's nice to finally see some roms for this device.
problem help please
ilia3367 said:
- = Treble Zoom = -​
This custom ROM based on Havoc-OS 3.5.
Prerequisites - bootloader must be unlocked, clean Stock firmware and TWRP must be installed.
What's done:
- integrated GAPPS (Play Market, Chrome, Google Dialer, Messages, Contacts, etc.), but nothing extra. YouTube has been removed because I use YouTube Vanced);
- installed Nova Launcher (I recommend using it as the main one), RootExplorer, Asus File Manager (for simple tasks), Asus Gallery, AdAway ads blocker, Motor Command Center 2;
- integrated Moto camera from the latest firmware draining. Fully working with the work of all camera modules! In addition the best, in my opinion, for this ROM and our phone Google Camera mod;
- working Adaptive Brightness;
- cleaned up and made the system a little bit easier.
Installation Instruction
1. Download the Project Treble system image archive. Unpack the archive and copy the ROM image to an external SDCard.
2. Copy to external SD Card Magisk Installer https://github.com/topjohnwu/Magisk (latest version for today Magisk v20.4), Disable_Dm-Verity_ForceEncrypt https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 (latest version for today Disable_Dm-Verity_ForceEncrypt_03.04.2020 https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip ) and Permissiver_v4 (see attachments)
3. Reboot in TWRP and go to the "Wipe" tab, "Advanced Wipe" and select Dalvik, System, Data, and then go back two steps back and do a "Swipe Factory reset".
4. Install the Treble Zoom system image. In the "Install" tab in the lower right corner click "Install image" and select ROM Image. A window will open in which you should select partition "System Image" in which the image where to be installed. Swipe for confirm flash.
5. When the installation is complete, go to "Wipe" and perform a "Format Data".
6. Install the Magisk.zip, Disable_Dm-V_ForceEncrypt.zip and Permissiver_v4.zip. Reboot into the system and make the settings, use the Project Treble working system.
The first launch will be a bit long, don't worry and be happy!
Noticed problems on Treble Zoom - Does not pass SafetyNet check (ctsProfile: false; basicIntegrity: true). On Google Play, your device is not certified, but applications are installed and updated. Wired headphones are plugged in. When connected, the Bluetooth headset in the Dialer application works, but when listening to audio, video, YouTube is not.
Fingerprint Unlocking by fingerprint is implemented for scanners on the back of the phone. This problem can be corrected in the following way:
Connect the device to your PC and enter the following commands
Code:
adb shell
su
setprop persist.sys.fp.fod.location.X_Y 450,1760
setprop persist.sys.fp.fod.size.width_height 194,194
A green circle will appear in the display of your device, which is responsible for your fingerprint.
Click to expand...
Click to collapse
so i tried to install the rom everything wwent well untill it kept booting to twrp then installed again and now it wont boot at all when plugged in it only lights up the moto sign on the back what can i do?
forgot to mention
death1426 said:
so i tried to install the rom everything wwent well untill it kept booting to twrp then installed again and now it wont boot at all when plugged in it only lights up the moto sign on the back what can i do?
Click to expand...
Click to collapse
i think i accidentally hit boot on slot b on twrp if so how can i fix this if it wont boot into bootloader?
To load into slot A, execute the command:
fastboot --set-active=a
Does it still has the moto shortcuts? Like alsways on display and the flashlight gesture?
There is a 3.8 version in the Havoc-os 3.5 link, can I flash it on One Zoom?...
thirdphotographer said:
There is a 3.8 version in the Havoc-os 3.5 link, can I flash it on One Zoom?...
Click to expand...
Click to collapse
This ROM is not the original GSI Havoc-OS image.

Categories

Resources