Related
So like many of you who were running the awesome LPV build for the past few months and just recently tried updating to official Lollipop (LRX21O) have likely run into issues on first boot (black screen with only a back button). In this state/issue the phone will respond to "OK Google" but nothing else. The pulldown shade will also be present but show nothing. The issue appears to be related to the lock screen. The following is how I fixed my issue, and I will be looking at this thread to try and update the OP as we pin down the EXACT issue, but I believe I have a fix:
NOTE: If you've already updated and are AT the black screen, I hope you have a backup to restore as you'll need to revert to change some settings. If not, you may find flashing the system.img or zip of your old build (LPV) allows you access to your phone again to access these settings.
1. Restore backup or revert if necessary so you can access settings BEFORE flashing LRX21O.
2. Settings-Security-Screen Lock Make sure you have one set other than swipe so you can perform the next step (we will change this back later)
3. Go to "Trust Agents" on the same screen (Security) and turn OFF SmartLock
4. Go back to screen lock, now select SWIPE (or none if present, but I don't believe it's an option on most)
5. (Optional) I chose to both enable USB debugging as well as going into SuperSU (if present) and setting it to grant all requests. I did not need this, however if you're having issues it may help your troubleshooting to have root adb access.
6. With your lock screen set to swipe and smart lock off, now try flashing LRX21O, followed by a custom kernel (or boot.img if you have it) and/or root in that order if you'd like.
7. Upon boot, it SHOULD have resolved the black-screen issue. I did still have the "non-working home button" issue that was quickly resolved by running the setup wizard again with the following command via adb:
adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity
When it asks about restoring backups or setting up as a new device, choose set up as new device. The "Restore" would simply re-download and restore apps that are already installed. "Set up as new device" simply tells setup to do nothing, which is fine, because all your data is already there
8. SDcard Fix (root required): If you have issues seeing SD card content, use these ADB commands below (credit to rootSU here
su
restorecon -FR /data/media/0
That's IT! You should be set. I love dirty flashing (I know everyone hates it because yes, it does cause a lot more chatter in the forums, but that's half the fun ) and problem solving. Everytime I see someone claiming they fixed a problem by factory resetting I'm thinking "...that's like saying you fixed your car by buying a new car". I hope I this makes other's lives a little easier
biktor_gj said:
Hello everyone!
Android Wear for Gear 2 / Gear 2 Neo
This thread is about development of Android Wear for Gear 2 & Gear 2 Neo
IF YOU HAVE A QUESTION, ASK IT HERE: http://forum.xda-developers.com/gear-2/help/qa-porting-android-to-gear-2-t3018159
View attachment 3279773 View attachment 3279774 View attachment 3279775View attachment 3299034View attachment 3299035View attachment 3312899View attachment 3312900
DISCLAIMER
Code:
Your warranty is now void. Not only void,
it's not comming back. The moment you
flash anything on this thread you can say
goodbye to it. I almost hard bricked my
watch once. It can happen to you too.
I do my best to post things that aren't
dangerous for the device, but anything
as simple as a 9 instead of a 4 in the GPU
driver might make it overheat and kill it.
Everything here is at your own risk.
You have been warned.
Current development stage
Kernel:: Still work in progress. Most functions are working correctly. Expect some bugs.
GITHUB REPO: Github Android B2 Repository
Recovery:: Minimal image. Not actively worked on, but enough to wipe and access ADB: MediaFire
Android: Most of it is working, and for me at least, IS usable. Some things are still missing and will need to be worked out though.
Working:
Boot
USB: ADB, MTP [july 19th]
Display: Software rendering, OpenGL and mixed compositions
Screen dimming
Screen always on
Battery reporting and charging
Oportunistic Sleep (kernel)
Bluetooth: basic functionality (working for notifications, music control etc), Tethered internet access (still some bugs to work out though)
Vibration
Heart Rate Monitor
Accelerometer sensor
Step counter
Gyroscope (this includes tilt to wake)
Power management: CPU Hotplugging, frequency scaling, Amoled LPM, runtime suspend and opportunistic sleep.
Depending on use, can give from 12 to 48 hours of battery life. Normal use gives me about 18-20 hours with screen always on
Audio: Input and Output
Infrared
Basic TWRP recovery functions
Not working:
Camera
There's no way of playing music to the speaker directly from the watch
There's no gallery app
Palm-on-screen to suspend
Anything that's not specifically put as "working"
Latest development image:
August 13th, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J)** Bugfix release,
Full flash Package:
Mediafire: http://www.mediafire.com/download/ar8ir73m32yx05n/Wear_511__08_13_2015.tar
Includes: Kernel Settings application:
* Control vibration intensity
* Control brightness in ambient mode
* Enable / Disable Partial Redraws (enable for best battery life)
* Enable / Disable Idle Mode (reduces color depth in ambient mode to enhance battery life)
If you want root, Install the root package from TWRP after installing the Odin Package: (recommend to ADB sideload it)
http://www.mediafire.com/download/9ppo5zd6f9y41yl/Wear-SuperSU-v2.40(1).zip
Previous builds:
July 22nd, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J)** Bugfix release
Full flash Package:
Mediafire: http://www.mediafire.com/download/pr3vljpdecep0dd/wear_511__07_22_2015.tar
md5: def249f18214c7ca00a5bc65391d0c0f wear_511__07_22_2015.tar
After flashing the big file, flash one of these, depending on what you need:
ADB only boot image: http://www.mediafire.com/download/cuo5fa95d5tgmv5/bootimage_ADB_ONLY.tar
ADB+MTP boot image: http://www.mediafire.com/download/bs6rwapqcc35sc6/bootimage_MTP_AND_ADB.tar
July 17th, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J)** Screen always on in Low Power Mode, MTP Support, @bitstra IR App Updated
Full flash Package:
Mega: https://mega.co.nz/#!0ZxgQYZA!7m986voG9NLYUUx7Nxzx8EiYbdgXxwFi56otuxQFZbM
Mediafire: http://www.mediafire.com/download/k71o1m16g32x65y/Wear__5_1_1__07_19_2015.zip
MD5: deffb5160968d81a4e560416315791eb Wear__5_1_1__07_19_2015.zip
July 13th, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J)** Infrared support (thanks @bitstra for your IR app!)
Full flash Package:http://www.mediafire.com/download/6mmb33lftfrr8w8/Wear_511__07_13_2015_Try2.zip
July 12th, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J) ** Screen always on + Audio IN/OUT modifications
Full flash Package: http://www.mediafire.com/download/myzqnv4bkwa55b3/Wear_5_1_1_07_12_2015.zip
July 5th, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J) ** Audio support!
Full flash Package: http://www.mediafire.com/download/eths38jax91sgnd/Wear_511_07_05_2015.zip
July 1st, 2015: Android Wear Lolipop - 5.1.1 (buildLDZ22J)
Full Flash Package: http://www.mediafire.com/download/6rzpfswta2s8fg3/Wear_511_07_01_2015.zip
June 27th, 2015: Android Wear Lolipop - 5.1.1 (build LDZ22J)
Full Flash Package: http://www.mediafire.com/download/bmcjbaikve5sob2/Gear2_Wear_Lolipop_5.1.1_06292015.tar.zip
June 27th, 2015: Android Wear Kitkat - 4.4.2W (build KNX01Q)
Full Flash Package: http://www.mediafire.com/download/2ar5ye1vla8g8gf/full_06_27_2015.zip
Everything I have/done with the Gear 2 is available on this folder: https://www.mediafire.com/folder/092gaz7gudh0f/Gear2, in case you want to dig a bit deeper
Installing
Odin: http://www.mediafire.com/download/v67itqpjitxxogi/Odin3_v3.09(1).zip
User @alvaromartinezb has made a really good video explaining what you have to do, check it out! https://www.youtube.com/watch?v=bBqg72z8LOk&feature=youtu.be
@alvaromartinezb Walkthrough video on audio: https://www.youtube.com/watch?v=klYqseFd90g
KNOWN ISSUES
USB doesn't work! --> Check if you're running latest build, check your drivers. Windows 7 may have some issues with MTP
ADB doesn't work! --> You might need to manually install the driver on the device manager in Windows (you can use Google SDK's bundled driver)
Battery doesn't last! --> Be careful with battery hog watchfaces, some will prevent the watch from entering suspend, or keep the heart rate sensor active at all times.
I can't play music from the watch to the speaker --> I haven't found an app that works. We're the only people with a speaker on an Android Wear device, and there aren't many 3rd party apps for that. Driver level is OK
I can't take photos! --> Work in progress, everything takes time, and my watch doesn't even have a camera!
Calls don't get routed through the watch and without it I will die! --> Then go back to Tizen. That functionality doesn't exist in Android Wear, and hundreds of hours of work for a function that probably wouldn't end up working anyway. And I hated it when I had it on Tizen, it only gave my phone issues when connecting to my car's bluetooth handsfree, and forcing me to choose back my phone on each and every call. I'm not developing that. If you want to try to code it yourself and you succeed, I can link to your work if you want, but I'm not wasting my time on that.
Going back to Tizen
BE ADVISED: GOING BACK TO TIZEN MIGHT PROVE DIFFICULT TO ANYBODY WITHOUT KNOWLEDGE OF THE WATCH, SDB, ADB, AND ANYONE WHO DOESN'T USE ODIN. DON'T PM ME FOR IT. IT'S WRITTEN BELOW. ASK IN THE Q&A SECTION PLEASE. THIS IS A DEVELOPMENT THREAD, AND THESE IMAGES ARE FOR DEVELOPMENT ONLY.
BE ADVISED (again): There's no PIT file for this watch. If your favourite flashing app for samsung phones requests one, use Odin. I know, I don't like it either. But we live in a world full of virtual machines with the ability to share USB ports. Now it's your chance to use them if you don't feel like installing Windows in your machine.
*. Walkthrough video by @alvaromartinezb : https://www.youtube.com/watch?v=LhzIqFopQNY&feature=youtu.be
1. Flash this file: http://www.mediafire.com/download/3cg2eazoouur0bs/Tizenmod-Full-Restore.tar
2. When it fails to boot and the screen goes blank, reboot to the bootloader menu and select recovery.
Extreme Recovery mode - Only use if above method doesn't work
YOU NEED TO KNOW HOW TO USE ADB/SDB FOR THIS.
It may happen that you try to recover your watch but for whatever reason it still enters a bootloop when attempting to boot Tizen. This might happen if you played with partitions, if some permissions were set where they shouldn't be, etc. If you enter recovery mode in Tizen and you don't see a confirmation that the watch is being restored to default, you can try this:
*NOTE* This is highly destructive. You do this wrong, your watch might not boot again. I'm not responsible for whatever damage you do to your watch.
First of all download everything from this folder:
https://www.mediafire.com/folder/a1tcatuw1a8t3/Full_Restore
And then follow these steps:
Code:
1. Flash TizenModFull
It will start rebooting itself
2. Flash recovery_fota_cache
3. Enter recovery, and run the following commands through ADB:
adb shell ->
umount /data
mount /dev/block/mmcblk0p15 /system
mount /dev/block/mmcblk0p13 /system/opt
mount /dev/block/mmcblk0p14 /system/opt/usr
rm -rf /system/opt
cp /system/usr/system/RestoreDir/opt.zip /system
cd /system
unzip opt.zip
sync
cd /
umount /system/opt/usr
umount /system/opt
umount /system
Exit the shell and select "Reboot -> PowerOff" from TWRP
4. Now press and hold the power button until "Rebooting..." appears, then enter Download mode
5. Flash kernel_tizen.tar
6. Reboot again to download mode
7. Flash tizenmod2.tar
Some info about the device
Gear 2 specifications
Samsung Exynos 3250, dual core up to 1GHz
512 Mb of RAM
4 Gb of flash, divided in 15 partitions (see below)
Mali 400 GPU, using Exynos DRM driver
YMU381 audio, supported by ALSA
BCM4334W Bluetooth/WLAN controller, already supported by Android in a bunch of phones
Samsung SensorHub (STM32) controlling Gyro/accelerometer and HRM. Supported in the kernel and seen in Android HAL.
Partition layout
bota0 -> ../../mmcblk0p1
bota1 -> ../../mmcblk0p2
csa -> ../../mmcblk0p3 --> ext4 -> /csa
boot -> ../../mmcblk0p5 --> Main Kernel
csc -> ../../mmcblk0p12 --> ext4 -> /system/csc
fota -> ../../mmcblk0p10 --> seems empty
ramdisk-recovery -> mmcblk0p8 -> ext4 -> Unused in tizen --> USED AS BOOT PARTITION IN ANDROID
module -> ../../mmcblk0p9 --> ext4 -> /lib/modules --> USED FOR TWRP IN ANDROID
rootfs -> ../../mmcblk0p15 ext4 "/" --> Root file system, recovery works from here too. If you break it it will only boot to download mode. --> USED AS SYSTEM PARTITION IN ANDROID
system -> ../../mmcblk0p11 EMPTY --> Did samsung start with Android on this thing then changed their minds?
system-data -> ../../mmcblk0p13 --> ext4, /opt --> If you erase this partition, your watch won't boot back into Tizen. Do not touch it unless you have a backup and know your way into restoring it.
user -> ../../mmcblk0p14 EXT4, /opt/usr --> all user data, including the MTP available part (/opt/usr/media) --> USED AS DATA & SDCARD IN ANDROID
Click to expand...
Click to collapse
Original thread -----
http://forum.xda-developers.com/gear-2/development/please-help-kernel-compiling-android-t2992953
Straightforward install. OP you da MVP!
Sent from my iPad using Tapatalk
Keep working on it man! Fantastic work!
Link to the original thread is wrong...
Sent from my SM-N910C using Tapatalk
Any updates?
Sent from my Nexus 6P using Tapatalk
I love you.
I take à neo for xmas.
It never appear on my z2.
I flash with Android wear today immediatly work.
Ty ty ty à lot
1.3 ROM update
Excellent!!!
But remember to flash with 1.3 ROM. It fixed OK Google and Always On issues.
Search youtube for "Android Wear for Gear 2 1.3 Update!"
any new updates for Geo s2 neo and android wear ?
Thanks,
Mike
Yes, i like a port of aw to the gear 2 (the only thing i would buy a 2, have a Gear 1 with Tizen and am missing features from my LG G).
And i appreciate the work.
But i am not so sure about some things mentioned here:
Using the speaker to play music on watch and phoning with it: Since there are some devices with speakers (Zenwatch 2, Huawei watch and others (more expensive ones)) and i read that android wear 6 will be out only for such devices... There should bei possibilities to use the speaker "full" - except it is a problem of missing drivers because the port comes from a device that lacks of speaker?
I am pretty sure that i had seen apps for that, but hadnt tested because my G has no speaker.
Is there any newer/more information?
Edit:
Its german, but f.e. it is mentioned there that with aw 1.4 came support to phone via watch and to watch videos with sound:
http://www.cnet.de/88165305/asus-br...e-fuer-zenwatch-2-und-neue-smartwatch-modelle
SirTurbo said:
Yes, i like a port of aw to the gear 2 (the only thing i would buy a 2, have a Gear 1 with Tizen and am missing features from my LG G).
And i appreciate the work.
But i am not so sure about some things mentioned here:
Using the speaker to play music on watch and phoning with it: Since there are some devices with speakers (Zenwatch 2, Huawei watch and others (more expensive ones)) and i read that android wear 6 will be out only for such devices... There should bei possibilities to use the speaker "full" - except it is a problem of missing drivers because the port comes from a device that lacks of speaker?
I am pretty sure that i had seen apps for that, but hadnt tested because my G has no speaker.
Is there any newer/more information?
Edit:
Its german, but f.e. it is mentioned there that with aw 1.4 came support to phone via watch and to watch videos with sound:
http://www.cnet.de/88165305/asus-br...e-fuer-zenwatch-2-und-neue-smartwatch-modelle
Click to expand...
Click to collapse
Biktor, the developer who made the AW port for the Gear 2 (Neo), has indeed ported most of the AW 1.4 functionality.
The speaker is working (the watch rings when a call comes in), but he didn't succeeded in actually taking the call on the watch.
So you will still need to take the calls on the phone itself.
There is a program called "Wear Notifications" which allows to read out loud the notifications on the watch
(really cool feature), but also that developer has stopped developing. The latest version has problems reading out loud the notifications.
When you flash the AW port on the Gear 2 (Neo), be aware that other features also don't work...like camera, BT calling on watch.
And the battery life on AW is worse than on Tizen.
I know this is probably a pipe-dream but, I would be so happy if we see an android wear 2.0 port once it drops this month. Or ever for that matter. *crosses fingers*
SumTuusDeus said:
I know this is probably a pipe-dream but, I would be so happy if we see an android wear 2.0 port once it drops this month. Or ever for that matter. *crosses fingers*
Click to expand...
Click to collapse
Yes!!! Me too
I guess that something has updated but suddenly, when I was in the pub last night, the watch face had changed - digital clock at the top and a background that changes with the time of day and weather (pictorially) - never seen it before - it seems to be called Incrememt according to the Android Wear app - I don't remember downloading it - If I try and change the watch face back I get the message 'Unfortunately Zenwatch manager has stopped'.
Anyone else had this / know anything?
***FIXED*** by reflashing watch
I flashed this the other day and can't get my mic to work. Is there a work around for it or did I miss something?
I would suggest reflashing. Because, my mic works.
How about notification sounds. Mine doesn't seem to have those either.
That works for me too.
Are you using the newest build in the OP?
Yup
Maybe I have an app or permission causing my mic and notification sound to break. New to android wear device
Updated version of this ROM: [ROM][TMOBILE][S7_SM-G930T][Oreo 8.0 Rooted][WifiCalling]G930TUVU4CRI2
ROM last updated: 10/30/2018
Introduction:
HUGE thanks to the guys that got this going like root & figuring out hybrid stocks! This ROM is a complete rewrite of my ROM [ROM][TMOBILE][S7_SM-G930T][Oreo Rooted] That ROM doesnt have WifiCalling & I couldn't get it to work for the life of me, so I rewrote it. I started with stock, and slowly stepped back making changes, reinstalling each time, confirming it still worked. About 200 installs later & 1000s of changes, this is the result. Yes, it took a LONG time. Hope you enjoy it! Don't forget to say Thanks so I know it is actually helpful to others, and continue doing this!
Description:
Stock Tmobile Oreo 8.0 modified (G930TUVU4CRF1)
EXTREMELY debloated! Nearly bare minimum, while still retaining hardware functionality. Eg, Samsung Gallery & Camera exist so we get 4k recording, and there aren't errors when we pull up the Gallery to edit, etc. Yes, this means NO Samsung or Android Pay. There could be more apps to debloat but Im out of time for now! (Please provide suggestions if interested)
Everything possible I replace Samsung with Google
Solid ROM. It was actually kind of slow for me, but I'm curious how this works for others.
Xposed is part of the guide, which will give you infinite customization & tweak-ability
If you hate Samsung SW and just want a solid working ROM with very few install options to get you up and running this is for you.
This will delete all of your data on the phone! (Not external SD card) This is the only way so don't ask. Backup your data!
Features:
Tmobile Wifi Calling works, along with Visual Voicemail & Mobile Hotspot
Many Aroma Installer app options
(Optional) KevinsFavorites option in Aroma. I'm not sure I'd recommend it due to my tastes. If you're looking for some good common apps tho, it includes: Amazon, AmazonMusic, AquaMail, Gmail, GoogleDrive, GoogleKeep, GooglePhoto, Hangouts, IFTTT, Pandora, RootBrowserClassic, TitaniumBackup, Uber, & Wink (If you install these and want to remove them later, use TitaniumBackup (or similiar) to uninstall
Root Features: See Downloads->Recommended Root Zip & say Thanks!
Debloated
De-Knoxed
Decrypted /data/ partition
OTAs disabled
Speed & Build Prop Tweaks
Dual speaker
Ruthless Launcher
Apps
AdAway
AOD Clock Face Themes
CPUSpy
DisableService
Kernel Adiutor
Samsung Video Editor and Trimmer
Xposed
Many more...
Download Links:
Base.7z & Oreo_Kevin71246Modded_v3.#.#.zip
Installation:
This will delete all of your data! If you continue, you acknowledge that the Author is NOT responsible for anything that happens to your phone!
Summary (for Pros)
Flash Oreo stock
Root
Flashfire
Oreo_Kevin71246Modded_v3.1.##, Auto-mount, Mount /system read/write Option
Go through Aroma setup. When finished, it should boot to Recovery (if not do this). Do a "Wipe data/factory reset"->Reboot
Detailed Steps
Install Stock Oreo:
Download mode & Setup
Make sure you have latest device drivers setup on your PC
Enable USB Debugging on phone in Developer Settings
Boot phone into Download Mode:
Turn off your device
Press and hold Volume Down + Home + Power button
When you see the warning screen, release buttons & press Vol UP. Phone should say "Downloading..."
Download and unzip Base.7z to PC (This contains stock Oreo, ODIN, & root)
ODIN
Open ODIN on PC (\Base\Odin_313.exe)
Connect USB from PC to phone. ID:COM in Odin should turn Blue with a COM port
Select AP, BL, CP and CSC files from the \Oreo_Stock\Base\ folder for corresponding files
Select HERO2QLTE_USA_VZW.pit
Select Start
Finished: Phone will reboot & show Carrier screen for 3-5mins. Wait until Setup screen & go through quickly (bare minimum) since you'll wipe it again. Once in Android, go to Settings->Display->Screen resolution->WQHD->Apply
Root Instructions: (+Flashfire, SuperSU)
Reboot phone into Download mode
Odin
AP: Select \Base\Root\AP_SM_G930_OREO_ENG_BOOT.tar
Start-> Wait for phone to boot to Android OS
Root
Double-click \Base\Root\cmd-here.exe & Type: root.bat [enter]
Option: 1 (Install Root No tweaks) (Or pick whatever you want)
*Note: With this system root, do not update su binary. Disable notifications for SuperSU app. Don't flash any superuser zips in recovery that are not made by jrkruse
Install Custom Hybrid ROM & Xposed
Download & copy Oreo_Kevin71246Modded_v##.zip to phone
Flashfire
Open Flashfire on phone
Red + symbol->Flash Zip or OTA->Oreo_Kevin71246Modded_v#, Auto-mount, Mount /system read/write Option->Check mark
Click Lighting bolt at bottom-> OK
Phone will reboot to Aroma. Go through setup. (See above for what's in KevinsFavorites)
When finished, allow Aroma to exit.
It should reboot into Recovery (If not, do this: immediately hold Vol-Up btn+Home btn until you see recovery on screen. If you missed it, try again: hold Vol-Down+Pwr btn ~10sec until phone restarts & immediately hold Vol-Up btn+Home btn until you see recovery on screen.)
In recovery: Factory Reset->Yes->Restart phone
*Wait 5-10min on loading screens
Go thru Android setup. Ignore "Xposed Installer has stopped" error
Followup-Steps:
Set Dialer: Phone Settings->Apps->Menu->Default Apps->Calling App->Select Phone
Recommendations:
Xposed
Setup Xposed: Xposed Installer app:Install framework option & restart phone
Xposed Installer app: Settings button (3 lines)->Download->Search "GravityBox [O]"->Click it->Versions tab->Download->Install->Back arrow (upper left)->Settings->Modules->Check box next to GravityBox [O]->Restart phone
GravityBox [O] Tweaks: (Open GravityBox app)
Battery indicator: Statusbar tweaks->Battery settings->Turn on Master switch->Battery indicatory style: None->Battery percent text...->Back
Clock: Statusbar tweaks->Clock settings->Turn on Master switch->Center clock...
Firefds Kit [O] Tweaks: (Install same way as Gravity box)
This is a supplement to Gravitybox. Things of note: Advanced power menu, call recording, & disable bluetooth toggle popup, etc
Known Issues:
Visual Voicemail may fail to register, but restart phone and give it a few hours. It works eventually.
RCS (Rich Communication Services/AdvancedMessages/Chat) texts don't show up in Android Messages & Textra, etc apps (This is an issue on stock as well!!)
Fix: (Use Samsung Messages)
How to Install Samsung Messages via ADB (Easiest way though is just reinstall!):
Download Messaging_SEP81.zip, unzip, & manually copy apk to phone via usb/Windows My Computer
adb shell (Get into shell to run beow commands)
su (Run as root)
mount -o rw,remount /system (Mount system read/write since default it read-only)
chmod 755 /system/priv-app/Messaging_SEP81 (Set permissions on folder)
chmod -R 644 /system/priv-app/Messaging_SEP81 (Set permissions on apk file)
ls -l /system/priv-app/Messaging_SEP81 (Check permissions - Should be: -rw-r--r-- 1 root root - not sure what 1 & 2 is)
ls -l /system/priv-app | grep "Messaging" (Check permissions - Should be: drwxr-xr-x 2 root root)
reboot (Reboot device)
Changelog:
Version 3.1.32: First stable build
Ver 3.1.36:
-Disabled encryption on /data/ partition to resolve "Bluetooth paired devices deleted after reboot" issue & so mods play nicer with ROM
-Fixed "Device not supported" error on Google Phone app
Ver 3.1.37:
-Added most of the apps I replaced or added as options in Aroma Installer now
Credits:
- @jrkruse & @klabit87 for Root
- @partcyborg for helping jrkruse
- @jrkruse for his similar ROMs as guides & help
- @Lanc-City for assistance in ROM modding
- @gustco for eng boot.img
- @Raymonf for modified odin
- @amarullz for Aroma Installer
- @Chainfire for FlashFire & SuperSU
- @rovo89 for Xposed
- @JaeKar99 for the cool & colorful boot animation
- @mrRobinson for AdAway ADAway.org
- Brandon Valosek for CPUSpy
- WangQi for DisableService
- Willi Ye for Kernel Adiutor
- @shubby for Ruthless Launcher
- @Craz Basics for Dual Speaker Mod
...
- Please PM me if you were forgotten!
Some screenies:
Saved2
Saved3
Well nice job!
jrkruse said:
Well nice job!
Click to expand...
Click to collapse
...but your'e the best! (You & I both know I couldnt have done it without all your other work!)
Once I FINALLY got WifiCalling to work, I thought... Imagine ALL the S7 XDA members out there with crappy Tmobile signal across Rural America that could TOTALLY use Wifi Calling!!! Haha, but seriously!! & that thought was the birth of this thread
kevin71246 said:
...but your'e the best! (You & I both know I couldnt have done it without all your other work!)
Once I FINALLY got WifiCalling to work, I thought... Imagine ALL the S7 XDA members out there with crappy Tmobile signal across Rural America that could TOTALLY use Wifi Calling!!! Haha, but seriously!! & that thought was the birth of this thread
Click to expand...
Click to collapse
Is this Ufirm firmware?
jrkruse said:
Is this Ufirm firmware?
Click to expand...
Click to collapse
I have so many FW packages on my PC at this point, from so many places that I used while trying to get this to work, but I think it might be a package from one of your threads(?) Since I'm not exactly sure what you're asking regarding "Ufirm FW", I'll elaborate hoping that answers your question. (Tho I'm thinking you mean the U variation/unlocked. So based on these stock files below I guess the answer is no.) If you're question is really, "is it possible to get tmobile wifi calling to work on a U model #", then I'd have to really think about that. But at this point I don't have an answer. I can tell you a million dependencies about it tho! (I seriously have hundreds of revisions I made while testing, & notes. The symbolic & meta links in Aroma initially broke it, as I found out after a week or so of testing - wish I knew a bit more about them, and why they're all there, then I'd know what was wrong about them...)
High-level process:
1)Flash Base/Stock/Oreo Rom:
- AP_G930TUVU4CRF1.tar
- BL_G930TUVU4CRF1.tar
- CP_G930TUVU4CRF1.tar
- CSC_TMB_G930TTMB4CRF1.tar
- HEROQLTE_USA_VZW.pit
2)Root with your method
3)Flash Xposed framework & my ROM (it's a "start with stock then remove what we don't want" type of Aroma/Edify script)
jrkruse said:
Is this Ufirm firmware?
Click to expand...
Click to collapse
BTW, any idea how to prevent the "verification failed" error I mention in the OP steps, after flashing Xposed framework? I tried flashing dm-noverity but no luck. At least my guide covers it at this point tho... Thanks again
kevin71246 said:
BTW, any idea how to prevent the "verification failed" error I mention in the OP steps, after flashing Xposed framework? I tried flashing dm-noverity but no luck. At least my guide covers it at this point tho... Thanks again
Click to expand...
Click to collapse
If you choose the keep safestrap option during root the it will flash the system/vendor/etc/ fstab.qcom that totally removes data encryption but when that fstab.qcom is flashed it also requires a data wipe for phone to boot then when you install xposed you won’t see that error but either way you end up wiping data so your choice
Sent using some kind of device I modified
It works perfectly!!
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
First, I want to thank you so much kevin71246. I tried your previous version as I was sick and tired of how sluggish my phone felt after the last two T-Mobile OTA updates. So far the experience on the phone has been great but I wanted to post about an issue I had with that version to see if anyone else has come across it or can figure out what is going on. The reason I am making this a reply in this thread instead of your other is because I will be flashing this update shortly but I want to get the ball rolling on the issue first.
I went through the whole process, installing the minimum with Google Apps, though I did restore everything previously installed once I log in with my Goggle Account. I am unsure if this contributed to the problem but I will not be restoring apps on the next try. It seems no matter what process I attempt to connect my Ticwatch E to my S7 the Wear OS app will not recognize it which causes the watch to get stuck in the setup phase, making it useless. This was after multiple and different connection attempts, resets, reboots and factory (watch only) restores. The watch will show up under bluetooth and create the initial connection but it will not stay connected. Anyone have any idea? Is this ROM missing something?
Edit: Mid way through the install, I wanted to note that I checked for the issue after doing the "Install Stock Oreo" but before Root and everything worked as it should. Wear OS sees the watch instantly and Bluetooth connects fine.
Edit: So I am a day into using the ROM and I am still having issues. While it will connect and work perfectly fine now, when ever I do a reboot of the phone the watch no longer connects. I will just get constant Bluetooth Connection Requests, every single time the watch tries to get data, and it never actually connects. To fix this I need to do a complete reset of the watch and do the whole setup process again. As you can imagine this is no good, expecting to wipe my watch every time my phone reboots makes it still almost useless.
charredchar said:
First, I want to thank you so much kevin71246. I tried your previous version as I was sick and tired of how sluggish my phone felt after the last two T-Mobile OTA updates. So far the experience on the phone has been great but I wanted to post about an issue I had with that version to see if anyone else has come across it or can figure out what is going on. The reason I am making this a reply in this thread instead of your other is because I will be flashing this update shortly but I want to get the ball rolling on the issue first.
I went through the whole process, installing the minimum with Google Apps, though I did restore everything previously installed once I log in with my Goggle Account. I am unsure if this contributed to the problem but I will not be restoring apps on the next try. It seems no matter what process I attempt to connect my Ticwatch E to my S7 the Wear OS app will not recognize it which causes the watch to get stuck in the setup phase, making it useless. This was after multiple and different connection attempts, resets, reboots and factory (watch only) restores. The watch will show up under bluetooth and create the initial connection but it will not stay connected. Anyone have any idea? Is this ROM missing something?
Edit: Mid way through the install, I wanted to note that I checked for the issue after doing the "Install Stock Oreo" but before Root and everything worked as it should. Wear OS sees the watch instantly and Bluetooth connects fine.
Edit: So I am a day into using the ROM and I am still having issues. While it will connect and work perfectly fine now, when ever I do a reboot of the phone the watch no longer connects. I will just get constant Bluetooth Connection Requests, every single time the watch tries to get data, and it never actually connects. To fix this I need to do a complete reset of the watch and do the whole setup process again. As you can imagine this is no good, expecting to wipe my watch every time my phone reboots makes it still almost useless.
Click to expand...
Click to collapse
I believe I know what the issue is, I'm testing a fix (for THIS ROM) as we speak. Stay tuned. Maybe tomorrow if I have time and it works I'll update the OP. BTW, this ROM and my other ROM are TOTALLY different. Thanks for the feedback!
FranMLG said:
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
Click to expand...
Click to collapse
What do you mean by this? "but if you do not pull them, let me know"
And tell me more about Viper4Android, and if it works solid for you on this ROM...then I'll consider adding it. Thanks!
New version, see change log in OP for details.
Yeah i.a give this a shot in a little. Do I need to root phone or can I just flash through Odin. Sorry not used to this locked bootloader crap..... s8crj1 are the last 6 digits of the software I'm on. I did receive the latest update will this effect me installing this. Sorry as I said not used to this locked bootloader crap.
jrkruse said:
If you choose the keep safestrap option during root the it will flash the system/vendor/etc/ fstab.qcom that totally removes data encryption but when that fstab.qcom is flashed it also requires a data wipe for phone to boot then when you install xposed you won’t see that error but either way you end up wiping data so your choice
Sent using some kind of device I modified
Click to expand...
Click to collapse
Hi, why you have to flash this - HEROQLTE_USA_VZW.pit on 930t, is it ROM specified? if I do and don't then what are pro and cons?
---------- Post added at 01:36 PM ---------- Previous post was at 01:26 PM ----------
josh2020glacier said:
Yeah i.a give this a shot in a little. Do I need to root phone or can I just flash through Odin. Sorry not used to this locked bootloader crap..... s8crj1 are the last 6 digits of the software I'm on. I did receive the latest update will this effect me installing this. Sorry as I said not used to this locked bootloader crap.
Click to expand...
Click to collapse
since bootloader is locked you can't use TWRP so you have to use Flashfire to install this ROM, as you know flashfire required root so you have to setup the base per OP and then root the base then install the ROM and then root it again, read the first page I don't think you will get a instructions more detailed then his
Okay so I just realised I was posting comments on the old thread, my bad. Coming back to the question, can the boot animation be changed? I've messed with the qmg files in an attempt to replace the weird, nauseating rainbow animation but even after overwriting the latter, it persists. Looking forward to a reply kek
Alkan3 said:
Okay so I just realised I was posting comments on the old thread, my bad. Coming back to the question, can the boot animation be changed? I've messed with the qmg files in an attempt to replace the weird, nauseating rainbow animation but even after overwriting the latter, it persists. Looking forward to a reply kek
Click to expand...
Click to collapse
Nauseating rainbow? LOL. Sorry. This is much more of a general question though, that wouldn't exactly pertain to this ROM specifically. And given I don't have an answer, I'd try searching BootAnimation How-Tos to get this customized. The ONLY thing I did regarding this was replaced the existing files with the rainbow ones. That's it. Apologies in advance.
Just discovered an issue: RCS (Rich Communication Services / Chat) texts don't show up in Android Messages app. See "Known Issues" in OP for a solution. BTW I posted a new ROM version a few days back that allows many choices in Aroma Installer. Make sure to pick Samsung Messages (instead of Google), so you get RCS chat text messages!
So I just recently came across this watch and have been fiddling with it. I managed to twrp it, unpack the 5.1.1 boot img other day and patch it with magisk and flashed it successfully. There was a little error in magisk manager you could slide by when you first opened it but it showed installed could grant superuser permissions.
The newest updates (6.0.1) and above I guess are using this squashfs scheme for system so it's not mountable. I noticed on the lg watch there was a squashfs doryimg, does anyone have squashfs sprat compatible twrp already anywhere, or can create one quicker than me? Or lead me in the right direction to compile it myself? An update installed on me unrooted me and failed to install, ideas on easiest way to freeze them prefferably adb shell pm uninstall -0 type command? Managed to also magisk patch 6.0.1boot img and flash it successfully get superuser permissions but its not proper doesnt have system permission to change anything much because of squashfs.
Tried DPI Changer is nice. Google Keyboard is good but wish it had an enter button so I can fiully type in jackpal terminal spaces that require an enter key. Will maybe try hackers keyboard(tried swype, gboard, minuum on 5.1.1 no dice). Google Analog draw keyboard zip kind of nice but annoying to type with. Es File Explorer pro size render disallowed looking at others app menu beside users. Es File Explorer worked to uninstall on 6.0.1 but not 5.1.1 had to go to go to data/ app to uninstall on 5.1.1. Could not install apk from device. Have been having to use adb install and push commands to get most files on the watch. Chrome apk latest works. I'd like to stay at 5.1.1 to maintain proper magisk/ twrp solely because of lack of squashfs support. Anyway to update google play service (1.1 to android 1.3 or 1.5) without updating version or install real playstore? Tried remote desktop/ gmail but only thing stopping me was I am unable to login to a google account on device because there is no account section in settings. Tried several app versions, shortcuts, workarounds no luck but lmk if you were able to.
Used rootjunky restore tool v2 to restore stock 4.4 it works well. V3 wouldn't recognize my almost bricked device but V2 would. OTA back from 4.4 is super annoying tho adb doesnt work says unauthorized until 5.1.1 doesnt give key doesnt pop up. Adb sideload is friend. There is not another boot img until 6.0.1 so had to apply patch updates then unpack/ repack. Had issues with backups not restoring root somehow. https://forum.xda-developers.com/wiki/Samsung_Gear_Live couldnt find anything newer besides one reddit post. first 6.0.1 update is twrp flashable.
well thats about all for now when I reupgrade I'll try and upload 5.1.1 magisk root if nothing changes. Thank you kindly Feel free to chime in if you still have this device, what worked for you., any tips, :good:
Still looking??
Sorry, I can't help you....... The gear live support just keeps getting less..... Well, it IS five years old after all...
Anyhow, I still have mine an love it. I read you were able to get TWRP on it successfully.
I can flash TWRP to the Gear Live just fine, but as soon as I reboot normally, the stock software replaces TWRP with the original recovery.
Supposedly, TWRP has a patching feature built in, but I've not been able to make it work.
SO....... Do you have any ideas why mine would not be working??
Thanks
Boowho??
Has anyone managed to update or replace the system Webview? I am trying to use the home assistant Wallpanel app and it works fine except custom cards fail to function, all the info I've found so far lead me to believe it's to do with the webview, maybe because it's V74 and I need a newer one, I've not managed to download one that will install, the latest one fails to install, and I've tried installing an older one (89.0.4389.86) which said it installed but checking in dev options it's still showing V74.
Anyone have any ideas?
The easiest way would be to root your device and use a Magisk Module like the Webview Manager I have attached here.
The other method is to try to change/update your framework.apk but that's really hard to do (especially with the newer android versions) without causing a bootloop.
I've been looking but not found a way to root the device yet, might just work around the limitations of the webview issue