[ROM][NWD1.171016.002] NegaSt33v Huawei-Rom - Huawei Watch

I decided to update the optimized stock rom that @negamann303 made and some of you are a fan of.
Features:
Based on NWD1.171016.002 - Wear 2.0 - Android 7.1.1
Stock kernel
Optional root/busybox package that will install root and busybox 1.28.1
Same build.prop additions as NegaLite Huawei-Rom NX 2 v 1.2 (including ADB debugging pre-enabled)
Removed Google Fit from /system (download from Play Store if you want it)
Removed the tutorial that appears when you enable wrist gestures (but not the tutorial that happens when you first set up the watch)
Changelog:
v 0.2
Actually installs stock kernel instead of the rooted kernel I accidentally put in v 0.1
v 0.1:
Initial release
Install Instructions:
Factory reset in TWRP (optional, but recommended)
Flash rom
Flash root/busybox package if desired
Note: The first boot takes a looooong time.
Note 2: The SuperSu/Busybox package tells you that it's installing an older version of busybox than what I listed. Don't pay attention to it. If you want to make sure I'm honest just do adb shell, then su, then busybox.
Download v 0.2: https://www.androidfilehost.com/?fid=962187416754467969
Download SuperSu and Busybox package: https://www.androidfilehost.com/?fid=962187416754466211
Download Busybox only package for those who want to use Magisk (personally, I don't see the point of using Magisk on a watch that doesn't need to pass safetynet, but to each their own): https://github.com/yashdsaraf/bb-bot/releases/tag/v1.28.1-YDS-201803061707 (flash the universal zip)
Requests are welcome. Keep in mind that since Android Wear is not fully open source, our power to change it is relatively limited.

TheSt33v said:
I decided to update the optimized stock rom that @negamann303 made and some of you are a fan of. Right now it's a work in progress. I'm pretty sure that everything works, but please test and report back.
Features:
Based on NWD1.171016.002 - Wear 2.0 - Android 7.1.1
Stock kernel
Optional root/busybox package that will install root and busybox 1.28.1
Same build.prop additions as NegaLite Huawei-Rom NX 2 v 1.2 (including ADB debugging pre-enabled)
Removed Google Fit from /system (download from Play Store if you want it)
Removed the tutorial that appears when you enable wrist gestures (but not the tutorial that happens when you first set up the watch)
To do:
Update Gapps
Move more system apps to /data for easy deletion
Include Root Essentials and Advanced Settings (download from Play Store if you want them for now)
Install Instructions:
Factory reset in TWRP (optional, but recommended)
Flash rom
Flash root/busybox package if desired
Note: the first boot takes a looooong time.
Download v 0.1: https://www.androidfilehost.com/?fid=673956719939825513
Download SuperSu and Busybox package: https://www.androidfilehost.com/?fid=962187416754466211
Click to expand...
Click to collapse
Good job! Feel free to pm me if you ever have any questions. I will try my best to answer them
Sent from my SM-G935P using Tapatalk

It's really nice to see the new rom for HW1!
If this rom can have lower brightness for ambient mode, I would love to test the rom!!!

Amazing rom

Thanks for the effort.
I will give it a try when I find some free time.

lentm said:
It's really nice to see the new rom for HW1!
If this rom can have lower brightness for ambient mode, I would love to test the rom!!!
Click to expand...
Click to collapse
According to the quick Google search that I did, it looks like this is controlled by the Android system framework. It's not as easy as changing a build property or telling settings to do something different. So unfortunately it doesn't look like it's something I can change, but if anyone finds any other information on it I'll definitely take a look.

Thanks a lot for continuing his work. Will be testing out on my watch soon.
Sent from my LG-H932 using Tapatalk

Thank you very much for doing this rom, look forward to using my watch again as I haven't used it in months.

It seems this build still installs the "rooted kernel" (that contains SuperSU binaries and configurations), which in turn blocks installation of Magisk (same as the original NX rom), as the two root solutions aren't compatible.
Guess I'll have to work around it using the hard way for now. It's better if the kernel can be made rootless so one can choose to install either SuperSU or Magisk.
EDIT: Got everything working: ROM, Magisk, and Busybox (installed using this one).
EDIT 2: It seems the Daily Tracking is working on this version, as on Explorer watch face the steps and kcals are properly registered just like on Android Wear 1.5.

LSS4181 said:
It seems this build still installs the "rooted kernel" (that contains SuperSU binaries and configurations), which in turn blocks installation of Magisk (same as the original NX rom), as the two root solutions aren't compatible.
Guess I'll have to work around it using the hard way for now. It's better if the kernel can be made rootless so one can choose to install either SuperSU or Magisk.
EDIT: Got everything working: ROM, Magisk, and Busybox (installed using this one).
EDIT 2: It seems the Daily Tracking is working on this version, as on Explorer watch face the steps and kcals are properly registered just like on Android Wear 1.5.
Click to expand...
Click to collapse
Oops. You're right. Sorry about that. I'll fix it this evening.

Source?
Where did you get the source?
i want to start making roms with the AOSP.

Omg. You are the man negast33v. Thanks for keeping this watch alive.

jayjar said:
Where did you get the source?
i want to start making roms with the AOSP.
Click to expand...
Click to collapse
I didn't get the source. In fact I didn't do much at all. I took the stock rom, put negamann's build.prop tweaks in it and put together the optional root package. That's about it, because that's about all that was done to negamann's original rom.

When you say the first boot takes a long time, how long are we talking? I'm testing something with my watch, so I already expect it to fail. I want to know so that I don't wait for hours when it should have been done in 20 minutes, which would mean my test has failed.

TheSt33v said:
I didn't get the source. In fact I didn't do much at all. I took the stock rom, put negamann's build.prop tweaks in it and put together the optional root package. That's about it, because that's about all that was done to negamann's original rom.
Click to expand...
Click to collapse
This is correct! That is why I typically spent more time on the kernel.
Sent from my SM-G935P using Tapatalk

CVertigo1 said:
When you say the first boot takes a long time, how long are we talking? I'm testing something with my watch, so I already expect it to fail. I want to know so that I don't wait for hours when it should have been done in 20 minutes, which would mean my test has failed.
Click to expand...
Click to collapse
Definitely not hours. 5-10 minutes I'd say.

Does someone want to try using the negamann kernel with this rom? It might work. I'm not sure and I don't feel like testing it.

TheSt33v said:
Does someone want to try using the negamann kernel with this rom? It might work. I'm not sure and I don't feel like testing it.
Click to expand...
Click to collapse
Hey,
I tried it, it doesn't work, it just hangs on the Android logo, waited over an hour, rebooted, nothing. Will not boot.
Edit: this is what I tried: negalite_kernel_HW_dffc4c0-2.0.zip - 6/7/2017
Edit 2: Just tried again, this time I cleared cache/dalvik and even so its just been on the Android animation for over an hour, and the watch has become really hot...Going to go back to stock kernal.

RumpSteak01 said:
Hey,
I tried it, it doesn't work, it just hangs on the Android logo, waited over an hour, rebooted, nothing. Will not boot.
Edit: this is what I tried: negalite_kernel_HW_dffc4c0-2.0.zip - 6/7/2017
Edit 2: Just tried again, this time I cleared cache/dalvik and even so its just been on the Android animation for over an hour, and the watch has become really hot...Going to go back to stock kernal.
Click to expand...
Click to collapse
Damn. Thanks for trying.

Thanks for updating this rom. Much appreciated : ).

Related

[ROM][StockWalk T989UVMC6][Debloated tweaked stock] updated 4/28

This is for the Galaxy S2 on T-mobile, for the LG Volt StockWalk go here
What this rom is.[/COLOR]
===========[/SIZE]
This a rebuilt stock deodexed rooted base, with some added csc tweaks and build.prop tweaks.
I have also updated the apps to their latest versions and included a couple extra Google apps (keep, and voice). Also included is
Mi FileExplorer, and Adobe Flash.
But this rom will be kept as the stock Touchwiz feel, I didn't like the way it was debloated by some so I decided to do it myself. And
I like the result.
Some of the features added
=================
Flash Player preinstalled and working - Apk Thread Here Thanks to stempox.
Browser has the user agent set to desktop by default
Browser exit option
Browser Bookmarks are editable
Carrier IQ removed (I consider that a feature lol)
Internet tweaks
4 way reboot - Credit to bryan2894
data/app folder for uninstallation of extra apps
proper root and busybox
Removed Preload Folder
data/app support
HD/off screen playback youtube - credit to theos0o
It does not have (yet)
=============
Unrestricted tethering/data cap (coming to a future build, i wanna take my time with smali editing though... its been a while)
Any kernel changes (never will, you can flash your own[I flash Tiberius])
Volume rocker wake (I hate it)
Flashbar (The amount of info on this is dang near nonexistant, so any help would be appreciated)
Issues
====
Starting with 1.1.1 there will be a tag to the right stating which post the release
started on for easy navigation later for people looking for issues in a particular version
Older
1.0.0
I ran into a no boot issue when wiping cache and dalvik cache, and when trying to flash a kernel, I am working on ripping a new base to attempt to resolve those issues, other than that no issues. The new base will be the next build.
1.0.1
superuser broken see post 13 for fix
1.0.3
left some stuff out by accident, skipping.
1.0.4
if google search is missing just download from play store.
1.1.1 post #36 is the release post
Google now settings don't stick, uninstall googlequicksearchbox.apk from system/app , reboot and install from market.
or just clear the data for google search...
Current
1.2.0 (lite) post #57 is release post
over 30 days of stability!!!!!
1.3.0 Updated version of 1.2.0
post #120 is the release post (if using twrp dont fix root)
Instructions
========
DISCLAIMER: I RUN THIS ON MY OWN PHONE AS MY DAILY DRIVER.
BUT I AM NOT RESPONSIBLE FOR BRICKED DEVICES OR SOMEONES
INABILITY TO READ. I WILL HOWEVER DO MY BEST TO HELP WITH
ANY ISSUES...
TWRP IS RECOMMENDED I AM CURRENTLY USING 2.5
-1. have a nandroid backup in case you have issues
0. use the superwipe scripts to eliminate any issues if you need them.
1. Wipe cache, dalvik cache, factory reset and system.
2. Install rom
2.5. If asked to fix root, don't.
3. Reboot
4. Wait for it to boot and have fun (works best if you
wait a few minutes after it boots for the signal to settle,)
If you use CWM recovery please let me know if it works.
Downloads
=========
Older
1.0.0 - Initial build
1.0.1 - Rebuilt base rom
1.0.3 - Uses chainfire su instead (skipped)
1.0.4 - removed boot sound, fixed flash player preinstallation
1.1.1 - Lots of internal revisions and prep for longterm stability. So far 95% stability, one hiccup. see if you can find anything else.
all old links broken and i have no backups of those
Current
1.2.0 - Lite version, no extra widgets, swype, tmemo or extra live wallpapers. (more system memory, no other apps removed.) over 24 hours of stability!!!!!
1.3.0 - update release for 1.2.0 (if using twrp dont fix root)
Changelog
=======
1.0.0 - Initial Release
1.0.1 - The awesome has begun. Totally re-done from scratch in ubuntu with dsixda's kitchen.
after some thorough testing it shows to be more stable and you can flash compatible kernels and tweaks with no issues, after wiping cache and dalvik cache you may have a slightly longer boot
1.0.4 - Uses Chainfire su v1.25, removed boot sound. fixed preinstallation of flash.
1.0.5 to 1.1.1 - Removed preload folder, updated apps, fixed broken apps, did some tidywork on the app naming for future upgradibility.
1.2.0 - slimmed way down to give 77 mb of space on /system compared to 39mb... removed swype, tmemo, some widgets and wallpapers (check screenshots... what you see is what you get.)
1.3.0 - Same as 1.2.0, Updated superuser and about 5 other apps.
Thanks/Credit
============
Koragg618 - 1.0.0 Base
Google
XDA
bryan2894 - 4 way reboot mod
chainsdd - superuser on versions 1.0.1 and 1.0.2
stempox - Adobe Flash apk
Jamison904 - wipe scripts
Powered by SuperSU - on version 1.0.0 and 1.0.3 and up
theos0o - HD Youtube with off screen playback
If you like this rom and want to use it as a base I'm cool with that. Please give credit to those above when you do.
THREAD RULES
============
i have some ground rules i wanna throw out early on so that everyone knows. I know there are rules and guidelines on xda about searching and whatnot before you post blah blah blah.
screw that... in this thread these are my guidelines (xda is total law over these obviously... what a mod says goes...) i suggest.
1. chit chat is cool as long as it semi-pertains to this rom. I've gotten great ideas and suggestions from chit chat.
2. if a total noob asks a total noob question, don't rip his/her ass for it. answer it or stfu and i will answer it. I don't care if the answer was one page back or in the op... be nice about it.
3. suggestions, feedback, and criticism negative or positive is encouraged. ESPECIALLY NEGATIVE CRITICISM. i'm super serious. the whole point of the rom is to rid all of the crap that annoys you.
4. I will always update the OP (original post, first post) whenever there is an update. and while i am working on the rom i update it super often (every few mins sometimes)..
5. eta requests are allowed.. and ill give one... but know that the e in eta stands for estimated.
Screenshots (1.2.0)
==============
Great
Sent from my SGH-T989 using xda premium
Mine....:thumbup:
Sent from my SGH-T989 using xda premium
New build is up. let me know if you find any issues at all. I cant find any yet.
I liked at but I had no play store. Installed an apk but that didn't work either, would just close immediately. That was the only issue I found.
Sent from my SGH-T989 using xda app-developers app
gariputo said:
I liked at but I had no play store. Installed an apk but that didn't work either, would just close immediately. That was the only issue I found.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
try the new build, its completely rebuilt, but as an fyi on the 1.0.0 version the playstore was working for me and phonesky.apk is in the preload folder and updated, along with gmscore and the others. also if you didnt let it settle for a couple minutes that may have been an issue. just try the 1.0.1 and lemme know. im running it now with no issues.
having trouble with superuser not asking for permissions on apps, any suggestions?
thank you for pointing that out. it may be the version of superuser, im gonna try another one and get another build out tonight.
NerdmastaX said:
thank you for pointing that out. it may be the version of superuser, im gonna try another one and get another build out tonight.
Click to expand...
Click to collapse
cool, i will wait, like you i hate volume rocker wake, at least on this phone...lol
edit: if its not to much to ask or i can do it when downloaded, but i also dont like on, off sound but if you do thats cool i can do it...thanks for the hard work and reply
yeah n/p ill remove the startup sound this go round, im deodexing again with the kitchen but this time im rooting with chainfire instead of chainsdd. manually replacing the superuser.apk and su binary fixes the root issue, i still want to let it finish deodexing the new build for that fresh build taste though. his superuser asks for an update on boot tho in the play store, so im gonna bundle it in so it doesnt ask.
NerdmastaX said:
yeah n/p ill remove the startup sound this go round, im deodexing again with the kitchen but this time im rooting with chainfire instead of chainsdd. manually replacing the superuser.apk and su binary fixes the root issue, i still want to let it finish deodexing the new build for that fresh build taste though. his superuser asks for an update on boot tho in the play store, so im gonna bundle it in so it doesnt ask.
Click to expand...
Click to collapse
sweet, Thank You, i will be waiting then report when all set up so you know whats going on...more info for you the better
this may fix your superuser issues for now while i work on the next build. i wanna do the tethering while i have the rom on the bench again.
NerdmastaX said:
this may fix your superuser issues for now while i work on the next build. i wanna do the tethering while i have the rom on the bench again.
Click to expand...
Click to collapse
if you want i can try that or i can wait no biggie to me, let me know
Hmmm, flashed the latest and still no Play Store. I am also not able to add a Google account. I waited 15 minutes after flashing. I am using Clockwork Recovery. I get stuck on the boot screen us TWRP. I did the appropriate wipes before flashing and cleared caches after.
gariputo said:
Hmmm, flashed the latest and still no Play Store. I am also not able to add a Google account. I waited 15 minutes after flashing. I am using Clockwork Recovery. I get stuck on the boot screen us TWRP. I did the appropriate wipes before flashing and cleared caches after.
Click to expand...
Click to collapse
4.1.2 is havinf trouble when wiping caches afterward, either dont wipe or use the cache wipe file from Jamison904. i dont wipe after flash anymore now...hope this helps
here is the link to it...http://forum.xda-developers.com/showthread.php?t=2235141.
just a helpful pointer if you think it gets stuck after wiping cache on twrp, it stays on the end of that loading bar what seems like forever but eventually does boot, so try giving it a little time, you may be thinking its stuck when its not. shouldnt take longer than 5 mins though.
btw new build is uploading now. root and flashplayer are working.
edit.... please read second post, the wipe scripts should solve our issues.
if i'm on ICS stock rooted, can i flash this in TWR to switch on over to JB?
850Mda said:
if i'm on ICS stock rooted, can i flash this in TWR to switch on over to JB?
Click to expand...
Click to collapse
i would reccomend you flash the newest radio beforehand for no issues (radios can be found here) UVMC6 should be at the top, also be sure to nandroid a backup first.
(note, im not certain if the radio is required, but its the way im using it, perhaps someone can clarify.)
Also... New build up... this should be the one to rule them all, very careful tweaking from here on out. please let me know of any issues you can find, also be mindful of how you wipe due to the symlink partition (read post 2)...
that being said i wiped normally even after flashing a kernel and i am not having any issues other than having to log into my google account again. and thats only when i wipe through twrp. but it does boot regardless if you wait. using the scripts should eliminate that problem though.
reflashed after downloading from my dev host link through the phone and i can flash dalvik cache and cache just fine again through twrp. so this is looking very promising and should turn out to be a stable base.
installed just fine, setup went good has superuser..set up to my liking now, using tiberus kernel with kernel tuner set both cores to max=1836 min=192, smartassv2, scheduler=row, and sd to 4096..only have internal sd so ( dont know if that matters but placebo effect makes me think it does...lol )......no volume rocker wake=awesome...no boot up or shut down sound=awesome.....steup screen to 220 density.....rebooted into TRWP recovery wiped cache/dalvik cache using Twrp advance wipe option installed miui player, s-voice, and transparent accuweather widget...running smooth and fast, wifi calling works...will report back after some more time but for now running great...awesome work, Thank You for the hard work!!!!

[Q] Recent SuperSU Updates - Issues

Figured I would start here in my device thread before trying the SuperSU thread.
Anybody have issues with SuperSU since the last few updates ago?
SuperSU does not even open. Root-dependent apps do not open. Titanium sits there at the initial screen "asking for root rights" until I kill the app. AdAway does not open... just goes right to a black screen until I kill the app. AdAway seems to work though, as my web surfing does not have ads.
I've also tried manually going in and applying the latest update via (philz) recovery.
Would I be safe to roll back to an older version of SuperSU?
Mods... if you're going to gun the thread, please at least point me in the right direction as I did search, but did not find anything related to recent issues on the Note 2 for SuperSU.
TIA for help and suggestions.
Oh yeah its still sitting in the play store. I lost root the last couple updates ago. I had to re flash my rom and start over.
ceabbott2 said:
Oh yeah its still sitting in the play store. I lost root the last couple updates ago. I had to re flash my rom and start over.
Click to expand...
Click to collapse
As part of my search, I did see Chainfire mention in his "fix" thread that some apps like wanam can cause issues. Of course, I have xsposed installed, so that could be the issue.
Do you (or did you) also have xsposed installed as well?
I have tried older versions of SU, uninstalling via philz then redownloading from Play - which now tells me the binaries are out of date and can't be done by SU, and I need to re-root.
Think I might try one of the other SuperUser apps "just to see how it works", or if it does.
lennykravitz2004 said:
As part of my search, I did see Chainfire mention in his "fix" thread that some apps like wanam can cause issues. Of course, I have xsposed installed, so that could be the issue.
Do you (or did you) also have xsposed installed as well?
I have tried older versions of SU, uninstalling via philz then redownloading from Play - which now tells me the binaries are out of date and can't be done by SU, and I need to re-root.
Think I might try one of the other SuperUser apps "just to see how it works", or if it does.
Click to expand...
Click to collapse
For me, I just reflashed the ROM I was running at the time and that resolved it. Of course seeing that the update was " fixed" I attempted it and lost root again. I then did the same as before, wiped and relashed. I didn't do clean installs either time. Just wiped caches and reflashed. That sucks if you have to re-root. I mean, it's easy and all but it shouldn't have to be done.
D
Before attempting any drastic measures (i.e., full wipe and reinstallation of the ROM), try this. This trick usually works for me.
Open your Application Manager, and locate your SuperSU application. Turn it off (i.e., click the "Turn Off" button). It may prompt you that updates are about to be uninstalled; that's ok. Download "BETA-SuperSU-v2.25.zip" and verify the MD5. Reboot into recovery and flash this file. Reboot and re-enable the SuperSU application from the Application Manager (it will be easy to find this time - scroll all the way over to the right, under "Turned Off"). Open SuperSU and it should let you reinstall the binaries.
Recently I've inexplicably lost root a number of times, and the above method has fixed it for me every time.
DJ_Barcode said:
Before attempting any drastic measures (i.e., full wipe and reinstallation of the ROM), try this. This trick usually works for me.
Open your Application Manager, and locate your SuperSU application. Turn it off (i.e., click the "Turn Off" button). It may prompt you that updates are about to be uninstalled; that's ok. Download "BETA-SuperSU-v2.25.zip" and verify the MD5. Reboot into recovery and flash this file. Reboot and re-enable the SuperSU application from the Application Manager (it will be easy to find this time - scroll all the way over to the right, under "Turned Off"). Open SuperSU and it should let you reinstall the binaries.
Recently I've inexplicably lost root a number of times, and the above method has fixed it for me every time.
Click to expand...
Click to collapse
Thanks for the try. Did not work though.
Looks like I just need to re-flash the ROM.
My problem was odd. Before I discovered the aforementioned trick, I'd re-root with Chainfire or Kingo. I'd reboot, and my device would be rooted. But those two methods have an additional payload - they flash the stock recovery. So I'd ODIN the Philz Touch recovery back to the device, reboot, and root would be gone. Never figured out what was going on.
Yup. Issues with new version. Only last 2 or three updates.
They seemed to be perfectly fine with cm12 though.
Sent from my SPH-L900 using XDA Free mobile app
Thanks for all of the input.
After doing a full wipe, and then re-loading Classic Stock 4.4.2, life is good again! Back to running awesome for a few weeks now.
Having said that, I did want to follow-up and ask others what current version of SuperSU you are on. As of right now, I am still on v2.01 (which is what was packaged with the ROM) and have not updated yet. Only other versions of SuperSU I have zips downloaded for are: 2.25 from post above, 2.36, and 2.37.
Any suggestions or confirmations on which newer/more recent versions will not bork my root status? Or which versions to definitely stay away from trying to use?
Thanks, and I appreciate any help and suggestions!
lennykravitz2004 said:
Thanks for all of the input.
After doing a full wipe, and then re-loading Classic Stock 4.4.2, life is good again! Back to running awesome for a few weeks now.
Having said that, I did want to follow-up and ask others what current version of SuperSU you are on. As of right now, I am still on v2.01 (which is what was packaged with the ROM) and have not updated yet. Only other versions of SuperSU I have zips downloaded for are: 2.25 from post above, 2.36, and 2.37.
Any suggestions or confirmations on which newer/more recent versions will not bork my root status? Or which versions to definitely stay away from trying to use?
Thanks, and I appreciate any help and suggestions!
Click to expand...
Click to collapse
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
jlmancuso said:
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
As always, thanks for your response. Your recommendation is what I've been doing, just wanted to follow-up on this and see if there was anything else I needed to consider or change as well.
My main concern was to make sure I was not going to run into any "big" issues (especially security) by staying on current version. Thanks for explaining where the issue really lies on this too. I'm obviously not a dev, however I do want to understand what is exactly going on and responses like yours always provide that type of info. :good: Thank you.
And, FWIW, using "fool proof" to describe a process only makes me more curious (and no, not in that way) about your suggestion. :laugh:
Now I HAVE to find out more about that option... (only after some of the best BBQ in all of the land - Sugarfire BBQ in STL )
jlmancuso said:
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
How do you disable auto update of binary on SuperSU? I keep seeing it in the notification bar, very annoying.

Screen off animation for HTC M9 and xposed installation

After searching high and low, i've finally found the screen off animation i wanted, this particular mod is not mine i'm just providing a find for anyone who is in the same situation.
Thanks to @zst123 for originally posting this
Requirements:
Root access
Custom recovery
Rom running android 5.0XXX
Also note functional on 5.1.XXX ROMs.
*New section for Marshmallow ROMs.
1. Go here and download this http://forum.xda-developers.com/attachment.php?attachmentid=3292041&d=1430517906
or this one if you're on android 5.1 http://forum.xda-developers.com/attachment.php?attachmentid=3313055&d=1431639027
or this one if you're on android 6.0 http://forum.xda-developers.com/attachment.php?attachmentid=3631566&d=1454436795
2. Download the Alpha build xposed framework from here http://forum.xda-developers.com/attachment.php?attachmentid=3200857&d=1425849071
or this one if you're on android 6.0 http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
3. Reboot to recovery and install the .21 or build or the .22 build if you're on 5.1XXX or the v80 sdk23 build if you're on 6.0.XXXX then reboot *NOTE* boot can take some time, 10 minutes at times
4. Once booted, install the alpha build apk downloaded in step 2 using a file manager.
5. Open Xposed and navigate to download, search for screen off animation and download the module.
6. Navigate to modules and enable them, reboot your device.
7. Open the app and choose a screen off animation.
8. Perform a reboot, Done.
FYI, it has been known that xposed can cause bootloops on the M9 so tread carefully and back up prior to installing it.
I can confirm that this and xposed with this installation method works as expected on Leedroid, other ROM's should work but I haven't tested them.
Can also confirm that for the most part, sense 6 toolbox and XUI Mod work too, and again this is not my software.
PS: Just like to add that the screen off Vertu animation is my personal favourite, it's a classy finish to a phone that deserves it.
------------------THEMING------------------
@ineedone This is his theme.
You need to flash the theme after xposed, clearing cache and dalvic after the initial installation of Chameleon. If you don't then you can (not always) end up in a boot loop, if you didn't wipe the caches then power down and boot back to recovery.
The initial boot after wiping the caches can take a long time, 10 minutes + is not uncommon.
This can also be assumed for any other mods which affect a lot of the ROMs system files.
Confirmed with Newest Leedroid and chameleon.
http://forum.xda-developers.com/showthread.php?t=3082322
@dladz
The third link has a extra http// in it.
Here's the right one
http://forum.xda-developers.com/showthread.php?t=3034811
aooga said:
@dladz
The third link has a extra http// in it.
Here's the right one
http://forum.xda-developers.com/showthread.php?t=3034811
Click to expand...
Click to collapse
All sorted, thanks mate, oversight on my part.
Posted in error
Xposed and xuimod work on 5.1 too. Sense 6 toolbox let's you change number of app drawer icons but won't let you in the app itself. Gonna test gravity box now.
Tested , it loads and stuff but none of the features really work.
tango280581 said:
Xposed and xuimod work on 5.1 too. Sense 6 toolbox let's you change number of app drawer icons but won't let you in the app itself. Gonna test gravity box now.
Tested , it loads and stuff but none of the features really work.
Click to expand...
Click to collapse
Aye I've used gravity before but have avoided it as I get everything I need from xui and screen off animation. I don't even use sense toolbox no more. I've read that Xposed works with 5.1 and there is a framework for it but as I haven't tested it on a HTC device I've not added it to the OP that its fully functional.
Gravity needs a big update, there have been quite a few broken bits for a while, also found gravity was always very heavy on the system too, might have just been me.
tango280581 said:
Xposed and xuimod work on 5.1 too. Sense 6 toolbox let's you change number of app drawer icons but won't let you in the app itself. Gonna test gravity box now.
Tested , it loads and stuff but none of the features really work.
Click to expand...
Click to collapse
Does that include stock 5.1?
Sent from my HTC One M9 using Tapatalk
neverborn said:
Does that include stock 5.1?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Stock as in not rooted or stock as in rooted on a stock rom, if it's the latter then it should work. That's probably the best way to use these mods. Unfortunately screen off animation as far as I know does not function as of yet. I'm away for a week now, but will be doing some testing of all the mods on my return.
Stock, rooted. Ive never had this much trouble just to get xposed.
Basically i:
1. Unlocked bl
2. Twrp
3. Backup of system image
4. Root
5. Xposed zip for arm64
6. Installed xposed apk
7. When trying to launch amplify it says xposed isn't running, even if xposed says it's active
Sent from my HTC One M9 using Tapatalk
That is literally what you are meant to do, some modules are functional, some aren't. For me the screen off animation didn't work and so strange as it might sound, I would miss it and as such I have retained 5.0.2, I really do not see any difference between the two, all modules work, nothing appears broken to me and the battery life is as good as I need it to be. To answer your question in short I get the same message with screen off animation, as if it's not installed. It's because it's not been updated. Either wait for it to be updated or downgrade like me
Updated op. Screen off animation working properly on 5.1, been using it for a while now.
neverborn said:
Stock, rooted. Ive never had this much trouble just to get xposed.
Basically i:
1. Unlocked bl
2. Twrp
3. Backup of system image
4. Root
5. Xposed zip for arm64
6. Installed xposed apk
7. When trying to launch amplify it says xposed isn't running, even if xposed says it's active
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Usually says that when either xposed isn't installed properly or the module hasn't been updated and you'll have to wait.
Follow the tutorial to install xposed, you can't miss.
dladz said:
Usually says that when either xposed isn't installed properly or the module hasn't been updated and you'll have to wait.
Follow the tutorial to install xposed, you can't miss.
Click to expand...
Click to collapse
And replace soft reboot with a regular reboot. Also had some bad experiences with particular modules. After a regular reboot they all worked fine
oemfoefoee said:
And replace soft reboot with a regular reboot. Also had some bad experiences with particular modules. After a regular reboot they all worked fine
Click to expand...
Click to collapse
Actually in that part of the tutorial, you only need a soft reboot. Regular if you need it but not necessary.
help!
Is the S-off bootloop bug fixed? M9+/S-off/5.0.1 I really want to install Xposed. Please help! :crying:
Vinncent said:
Is the S-off bootloop bug fixed? M9+/S-off/5.0.1 I really want to install Xposed. Please help! :crying:
Click to expand...
Click to collapse
Boot loops are a risk I've written how I was able to get xposed without boot loops but I've also warned that it can happen. If you follow my instructions you stand a food good chance
working great on the latest ViperOne rom... thanks man...
dladz said:
Boot loops are a risk Ive written how I was able to get xposed without boot loops but Ive also warned that it can happen. If you follow my instructions you stand a food chance
Click to expand...
Click to collapse
Food chances are the best!
Works on my m9:highfive:
Krsmqn said:
Food chances are the best!
Works on my m9:highfive:
Click to expand...
Click to collapse
Haha Bloody Auto correct.. Guess my phone is telling me to be a fatty ..
apaquette420 said:
working great on the latest ViperOne rom... thanks man...
Click to expand...
Click to collapse
No worries

[ROM] Marshmallow for Nexus 10

Get it while it's hot. All works. AOSP rom
Also included: directions how to build one of your own, TWRP images to flash right now, and a description of a VERY VERY cool hack i undertook to make GPS work
http://dmitry.gr/index.php?r=06. Thoughts&proj=03. Android M on Nexus10
My nexus 4 and nexus 10 are happy today thanks to you.
dmitrygr said:
Get it while it's hot. All works. AOSP rom
Also included: directions how to build one of your own, TWRP images to flash right now, and a description of a VERY VERY cool hack i undertook to make GPS work
http://dmitry.gr/index.php?r=06. Thoughts&proj=03. Android M on Nexus10
Click to expand...
Click to collapse
Had soft reboots when using browser. Wiped, re-flashed and same issue.
What gapps package did you use? I made a quick one with play services and gmail.
jase33 said:
Had soft reboots when using browser. Wiped, re-flashed and same issue.
What gapps package did you use? I made a quick one with play services and gmail.
Click to expand...
Click to collapse
Go into permissions and issue all permissions to the browser, or just install chrome - it supports 6.0 better
I am not going to talk about GApps, sorry
Try the marshmallow for nexus 4 thread - people there might have answers.
dmitrygr said:
Go into permissions and issue all permissions to the browser, or just install chrome - it supports 6.0 better
I am not going to talk about GApps, sorry
Try the marshmallow for nexus 4 thread - people there might have answers.
Click to expand...
Click to collapse
thanks
For gapps i used this package https://www.androidfilehost.com/?fid=24052804347833783 its pretty basic but gets you what you need, make sure to do a factory reset after flashing it otherwise the setup wizard will fc.
Now all we need is root
Used these gapps, follow the instructions though, use "touch 'filename' " in TWRP terminal for the file creation. Gapps on 6.0 is struggling right now, but these instructions worked for me.
EDIT: Forgot the link. http://forum.xda-developers.com/and...le-apps-minimal-edition-t2943330/post63226314
Same problem with soft reboots. Often just after starting Android before or after login. Even if I don't install gapps.
billyx1 said:
Same problem with soft reboots. Often just after starting Android before or after login. Even if I don't install gapps.
Click to expand...
Click to collapse
did you erase all data and cache when flashing?
if no, nothing i can do - i do not support that
if yes send me logcat
peachpuff said:
For gapps i used this package https://www.androidfilehost.com/?fid=24052804347833783 its pretty basic but gets you what you need, make sure to do a factory reset after flashing it otherwise the setup wizard will fc.
Now all we need is root
Click to expand...
Click to collapse
Thanks, that worked for me.
Also tried flashing supersu 2.52 beta from twrp but that seems to make it stick at the android loading screen so I guess there's no root at the moment.
it is a userdebug image, so at least in adb you have root
Amazing piece of work. Gonna try it as soon as a reliable gapps package is out!
dmitrygr said:
Get it while it's hot. All works. AOSP rom
Also included: directions how to build one of your own, TWRP images to flash right now, and a description of a VERY VERY cool hack i undertook to make GPS work
http://dmitry.gr/index.php?r=06. Thoughts&proj=03. Android M on Nexus10
Click to expand...
Click to collapse
Woot nice!
Could you share your device tree ?
edit thx for sharing :
I was having the bootloop at google logo and couldn't figure out what to do.
great job on the rom, no idea why people are having issues, i found the gapps package in the nexus 4 forum....no bootloops here, everything seems to work......I was able to enable google now on tap however i do not know how to use it, instructions say to hold down the home button to launch, however we do not have a home button, any ideas?
phonetec said:
great job on the rom, no idea why people are having issues, i found the gapps package in the nexus 4 forum....no bootloops here, everything seems to work......I was able to enable google now on tap however i do not know how to use it, instructions say to hold down the home button to launch, however we do not have a home button, any ideas?
Click to expand...
Click to collapse
home softbutton in systemui (the middle one)
dmitrygr said:
home softbutton in systemui (the middle one)
Click to expand...
Click to collapse
Ok I tried that and nothing happened, maybe I was using it wrong, I'll try again later when I get home
Sent from my SM-G925P using Tapatalk
I think I might cry. Flashing now.
---------- Post added at 11:12 AM ---------- Previous post was at 10:42 AM ----------
corumuk said:
Thanks, that worked for me.
Also tried flashing supersu 2.52 beta from twrp but that seems to make it stick at the android loading screen so I guess there's no root at the moment.
Click to expand...
Click to collapse
Maybe we need a kernel that supports root. That's how it is on the Nexus 5 anyway. I don't know if any of the lollipop kernels would work on this. Maybe I'll try that sometime soon.
Just an FYI.....
Updating Google Play Services (required for YouTube) sends it into a FC loop.
Hey guys, Have you noticed any kind of performance improvement after installing marshmallow ?
fifthelement said:
Hey guys, Have you noticed any kind of performance improvement after installing marshmallow ?
Click to expand...
Click to collapse
I've noticed it has been pretty quick. Did a full wipe and used the system.img from his website. Used these gapps. https://github.com/XorgMC/gapps-mm/releases/download/v1-mini/gapps-mm-mini.zip
Also, if you use those gapps it will say it failed if you try to restore your apps. Hit skip and it will say restoring. It will take a long time to install the apps. If you lock the screen and then unlock it swiping from the side to open the google app you can use the device while it restores your apps.
I havent had any issues related to the rom, just the gapps. Google app fails when i try to search something.

Questions about running stock rooted ROM / XPosed (Gravity Box) / Substratum

Hi guys,
After months of hesitation, I finally ordered a Pixel 2 XL. Now after a few years of running custom ROMs, I'm thinking of running the stock Google ROM with tweaks. But I haven't done that in a while so I have some questions, after rooting and installing TWRP:
- is it safe to install the latest Xposed framework beta? (bootloop/crashes)
- does Gravity Box work fine (no crash/bootloop)?
- can I apply Substratum themes on rooted stock?
- which kernel would you choose between Flash and ElementalX? I've been using the latter for a long time but curious about Flash.
- how do you handle monthly OTAs? Can they be installed running all of the above?
Thank you! :good:
Ghisy said:
Hi guys,
After months of hesitation, I finally ordered a Pixel 2 XL. Now after a few years of running custom ROMs, I'm thinking of running the stock Google ROM with tweaks. But I haven't done that in a while so I have some questions, after rooting and installing TWRP:
- is it safe to install the latest Xposed framework beta? (bootloop/crashes)
- does Gravity Box work fine (no crash/bootloop)?
- can I apply Substratum themes on rooted stock?
- which kernel would you choose between Flash and ElementalX? I've been using the latter for a long time but curious about Flash.
- how do you handle monthly OTAs? Can they be installed running all of the above?
Thank you! :good:
Click to expand...
Click to collapse
Like you, I have always run custom ROMs and this is my first time running stock with tweaks like you mentioned.
1- yes, as far as Xposed goes for me and my device, I've had 0 issues. If there is any lag, just choose the "optimize apps now" option in the Xposed installer.
2 - gravity box works flawlessly for me and gives so many features. I had to support the dev and bought the unlocker!
3 - you can use substratum, but since the March update, you have to reboot after building overlays to see them in the overlay manager.
4 - I've tried almost all kernels available for our device, and I don't know why, maybe it's a placebo, maybe not, but Flash has been the best for me. Virtually no slowdowns in terms of performance, and solid battery life as well.
5 - most people flash the factory images, editing the flash-all file, removing the "-w" to prevent data from being wiped. Me on the other hand, I do the most overkill option which is fastbooting the factory images to both slots, leaving the "-w" intact, and basically starting fresh every month it ends up being a few hour process but I don't mind because I have a bit of OCD and like having a clean slate to start from when new updates release.
Hope this helps!
rickysidhu_ said:
5 - most people flash the factory images, editing the flash-all file, removing the "-w" to prevent data from being wiped. Me on the other hand, I do the most overkill option which is fastbooting the factory images to both slots, leaving the "-w" intact, and basically starting fresh every month it ends up being a few hour process but I don't mind because I have a bit of OCD and like having a clean slate to start from when new updates release.
Click to expand...
Click to collapse
Hi,
Thanks for the comprehensive reply, it's appreciated and it does help!
I'm not sure about your last answer about OTAs though. So we have to flash the whole factory image every month? Isn't it possible to sideload the OTA? And what about Magisk and Xposed, do they have to be flashed again every time? I guess Substratum themes have to be compiled again as well? I guess I've been so used to custom ROM and dirty flashing that I got somewhat lazy
Does the unlocker for Gravity Box add more options? Or is it just a way to donate money to the dev?
Thanks again.
Ghisy said:
Hi,
Thanks for the comprehensive reply, it's appreciated and it does help!
I'm not sure about your last answer about OTAs though. So we have to flash the whole factory image every month? Isn't it possible to sideload the OTA? And what about Magisk and Xposed, do they have to be flashed again every time? I guess Substratum themes have to be compiled again as well? I guess I've been so used to custom ROM and dirty flashing that I got somewhat lazy
Does the unlocker for Gravity Box add more options? Or is it just a way to donate money to the dev?
Thanks again.
Click to expand...
Click to collapse
Unlocker is to support dev as well as it unlocks the ultimate notification controls which has a trial period
Ota are fine but we all prefer to flash the whole image because it is recommended and hardly comes up with errors
If you install magisk module for xposed then you would only need to re install magisk zip and your previous modules would be still installed
For substratum you need to disable overlays before updating and just re enable them after updating to latest update
Cheers ?
Sent from my Google Pixel 2 XL using XDA Labs
rickysidhu_ said:
Like you, I have always run custom ROMs and this is my first time running stock with tweaks like you mentioned.
1- yes, as far as Xposed goes for me and my device, I've had 0 issues. If there is any lag, just choose the "optimize apps now" option in the Xposed installer.
Click to expand...
Click to collapse
Hey,
I can't seem to be able to boot after flashing the xposed zip. My device shows a corrupted system error and boots back to the bootloader.
Is there anything I'm missing here?
Thanks!
Ghisy said:
Hey,
I can't seem to be able to boot after flashing the xposed zip. My device shows a corrupted system error and boots back to the bootloader.
Is there anything I'm missing here?
Thanks!
Click to expand...
Click to collapse
Which version of Xposed did you flash? And which version of the Xposed installer did you install?
rickysidhu_ said:
Like you, I have always run custom ROMs and this is my first time running stock with tweaks like you mentioned.
1- yes, as far as Xposed goes for me and my device, I've had 0 issues. If there is any lag, just choose the "optimize apps now" option in the Xposed installer.
2 - gravity box works flawlessly for me and gives so many features. I had to support the dev and bought the unlocker!
3 - you can use substratum, but since the March update, you have to reboot after building overlays to see them in the overlay manager.
4 - I've tried almost all kernels available for our device, and I don't know why, maybe it's a placebo, maybe not, but Flash has been the best for me. Virtually no slowdowns in terms of performance, and solid battery life as well.
5 - most people flash the factory images, editing the flash-all file, removing the "-w" to prevent data from being wiped. Me on the other hand, I do the most overkill option which is fastbooting the factory images to both slots, leaving the "-w" intact, and basically starting fresh every month it ends up being a few hour process but I don't mind because I have a bit of OCD and like having a clean slate to start from when new updates release.
Hope this helps!
Click to expand...
Click to collapse
Ditto.
rickysidhu_ said:
Which version of Xposed did you flash? And which version of the Xposed installer did you install?
Click to expand...
Click to collapse
I flashed xposed-v90-sdk27-arm64-beta3.zip. But I ended up installing XPosed through Magisk and it actuallly worked.
Are we not supposed to flash the .zip? It's what broke everything. I managed to flash the factory image and got my phone back to normal.
Ghisy said:
I flashed xposed-v90-sdk27-arm64-beta3.zip. But I ended up installing XPosed through Magisk and it actuallly worked.
Are we not supposed to flash the .zip? It's what broke everything. I managed to flash the factory image and got my phone back to normal.
Click to expand...
Click to collapse
Glad you got it working.
I downloaded the Xposed APK in the Magisk thread and installed Xposed within the app; after reboot everything seems to work normally for me.
The way you did it is also fine though:good:

Categories

Resources