Related
Link: http://forum.xda-developers.com/showpost.php?p=9172522&postcount=2058
Many thanks to supagforce, for this find!!
I personally tested this on TnT Lite 1.02, with no issues in the default browser (other than high memory use, but I guess that's to be expected).
11/29/10 EDIT: Newer Flash version out, GLES optimized. See this post for details: http://forum.xda-developers.com/showpost.php?p=9476506&postcount=26
Doesn't work on cm6
akodoreign said:
Doesn't work on cm6
Click to expand...
Click to collapse
Good point. For cm6.1 beta2, just alter the build.prop as follows:
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
and reboot.
This was not my fix, and I take no credit for it - it was in the big thread. I believe that the forthcoming beta 3 is going to have this change built-in.
roebeet said:
Good point. For cm6.1 beta2, just alter the build.prop as follows:
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
and reboot.
This was not my fix, and I take no credit for it - it was in the big thread. I believe that the forthcoming beta 3 is going to have this change built-in.
Click to expand...
Click to collapse
yup that was it. TY !
I can confirm it works on CM6 with the above added to the build.prop. I've done it myself.
Wants to join the party
I have been trying to days now to get this one last piece working. I have copied the flash apk to everywhere I can think of but still can't get it to install. I have tried using ADB (INSTALL_FAILED_INVALID_APK), Droid Explorer (crashes while trying to install), made sure SYSTEM was R/W, and still I am stumped.
Any ideas what else I can try? I am running CM v6.1b2.
Gbmedusa said:
I have been trying to days now to get this one last piece working. I have copied the flash apk to everywhere I can think of but still can't get it to install. I have tried using ADB (INSTALL_FAILED_INVALID_APK), Droid Explorer (crashes while trying to install), made sure SYSTEM was R/W, and still I am stumped.
Any ideas what else I can try? I am running CM v6.1b2.
Click to expand...
Click to collapse
look at the post above about the build.prop change. Btw, there's a beta3 now that does not have this issue, tmk.
Hulu
Can this be hacked to include the mod in the hulu enabled flash apk? Can they be diffed?
http://forum.xda-developers.com/showthread.php?t=688054
Thanks for all your hard work roe...
The Dude
It worked for me in stock system
roebeet
Please thank supag for me. I am not a programmer, I purchased this item so I could show my patients video and anatomy intructional pics. There is no way I would have been able to use it with out the combined team effort from all you folks.
P.S. The only change I made to the system was loading Launcher Pro.
Thanks again
Wyngnut
Gbmedusa said:
I have been trying to days now to get this one last piece working. I have copied the flash apk to everywhere I can think of but still can't get it to install. I have tried using ADB (INSTALL_FAILED_INVALID_APK), Droid Explorer (crashes while trying to install), made sure SYSTEM was R/W, and still I am stumped.
Any ideas what else I can try? I am running CM v6.1b2.
Click to expand...
Click to collapse
I am having the same problem trying to install on full vanilla. In fact, my device will not even download the rar...it fails. I had to copy it from another device....so dumb question, i assume i just need to rename the file to apk, not unrar it?
Flash 10.1 fix
I used a RAR extractor on my windows machine then side loaded the APK into SD on system. I then used ES file explorer to find the file On the internal SD and when I opened it it gave me the option to install. Install went off without a hitch.
I have stock system with no ROM changes and I loaded launcher pro which I use instead onf TapNTap. I have now viewed many Utube video's as well as movie trailers with no problems.
Hope that helps
Wyngnut
roebeet said:
look at the post above about the build.prop change. Btw, there's a beta3 now that does not have this issue, tmk.
Click to expand...
Click to collapse
My apologies for not explaining more fully. I actually have the build.prop edit in place. I tried copying the flash apk to /system as well as /system/app. My problem is that I can't get it to install. Either I get an error, the program attempting the install crashes, or nothing happens.
By the way, you mention a beta 3 of CM. Any idea where I can find it? I did a quick 'net search but came up with nothing specific for the gtablet. Guess I need to plow through the megathread again.
Any help would be greatly appreciated.
Edit: Could it be I need to fix flash prior to installing CM? I had to do that with the wifi hack before it would work. Guess I need to get another backup going just in case.
Edit (again): Never mind about Beta 3. I see in the megathread that it is in the works.
For the APK error, not sure about vanilla (never tried it). TnT Lite is 90% vanilla so I figured it should work on full stock.
I usually install with "adb install", which is how I tested it. I assumed a sideload would also work. I haven't put it in /system yet although I probably will do that when I build out TnT Lite 2.00 - that's coming next week btw, as soon as VS sends out their new firmware update and I can get my hands on it.
roebeet said:
For the APK error, not sure about vanilla (never tried it). TnT Lite is 90% vanilla so I figured it should work on full stock.
I usually install with "adb install", which is how I tested it. I assumed a sideload would also work. I haven't put it in /system yet although I probably will do that when I build out TnT Lite 2.00 - that's coming next week btw, as soon as VS sends out their new firmware update and I can get my hands on it.
Click to expand...
Click to collapse
Yeah, the ADB install just gave me an invalid APK error so I gave up there.
I may try flashing back to stock(ish) and installing from there.
Wyngnut said:
I used a RAR extractor on my windows machine then side loaded the APK into SD on system. I then used ES file explorer to find the file On the internal SD and when I opened it it gave me the option to install. Install went off without a hitch.
I have stock system with no ROM changes and I loaded launcher pro which I use instead onf TapNTap. I have now viewed many Utube video's as well as movie trailers with no problems.
Hope that helps
Wyngnut
Click to expand...
Click to collapse
+1 on that. Same setup and very easy fix. Thanks for this!
still no luck..
roebeet said:
Good point. For cm6.1 beta2, just alter the build.prop as follows:
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
and reboot.
This was not my fix, and I take no credit for it - it was in the big thread. I believe that the forthcoming beta 3 is going to have this change built-in.
Click to expand...
Click to collapse
this doesn't work for me.. in fact i opened the build.prop file and the properties were already set to the same values.. i'm running tnt lite 2.0. any suggestions?
i'm willing to even use CM if it'll mean running flash player, but so far this rom has been the most stable.
Works on the stock "out of the box" G Tablet!!
S_C_B said:
Works on the stock "out of the box" G Tablet!!
Click to expand...
Click to collapse
I am having the same problem as iksnae. I changed the Rom to TNT Lite 2.0.2 prior to loading the 10.1 Flash Player. I get Youtube videos and even Angry Birds but I can't get flash video from CNN or Hulu? Should I flash back to stock and then add flash. If so can someone point me to that thread? Every other hack has worked perfectly.
cbrownesq said:
I am having the same problem as iksnae. I changed the Rom to TNT Lite 2.0.2 prior to loading the 10.1 Flash Player. I get Youtube videos and even Angry Birds but I can't get flash video from CNN or Hulu? Should I flash back to stock and then add flash. If so can someone point me to that thread? Every other hack has worked perfectly.
Click to expand...
Click to collapse
My GTab was configured like yours. I unintalled Flash 10.1 and loaded the vanilla "out-of-the-box" Rom version. This version also had the clockwork menu so when you Flash don't panic if you see this pop up, just follow the instructions for loading the update.zip file from the /sdcard (I think it was option 2). I then side loaded Flash 10.1.apk from the PC to /sdcard and using ES File Explorer to access /sdcard, I doubled clicked on the Flash 10.1.abk to install.
Then I reinstalled TnT_Lite 2.0, flashed and then TnT_Lite 2.02 & Flashed this update.
ESPN3 works great. Also get Flash_TV from the Android Market and you now have IPTV. I am anxious to get the docking module so I can stream HDMI 1080P to my 46" LCD. No more cable, no more monthly cable bills (I do get internet 28MB/sec service).
Still looking for an optimized Nvidia Tegra 2 video media player that will take advantage of the processors embedded video encoder functions. I expect this will play HDMI 1080P movies quite nicely. Rock Player is rumored to be working on a dual core Cortex 9 version. Right now it plays using the software control option and is slow and clunky.
I believe that Flash 10.1 is optimized for the Nvidia Tegra 2 processor and it is quite nice. The streaming videos play smoothly. Not sure how they will play in HD when using the docking module and the HGMI connection to the large screen.
Best of luck. It's easy once you figured out how to do the original Flash load(s).
EKS
roebeet said:
Link: http://forum.xda-developers.com/showpost.php?p=9172522&postcount=2058
Many thanks to supagforce, for this find!!
I personally tested this on TnT Lite 1.02, with no issues in the default browser (other than high memory use, but I guess that's to be expected).
11/29/10 EDIT: Newer Flash version out, GLES optimized. See this post for details: http://forum.xda-developers.com/showpost.php?p=9476506&postcount=26
Click to expand...
Click to collapse
Thank you for this 11/29 edit pointer to the flash apk file (rename txt to API), all I have done is rooted thus far with z4root, stock TnT, and now YouTube videos work!
I take no credit for this amazing equalizer. All credits go to @zhuhang and the people from his thread for the convolvers.
If you don't know what V4A is check here for more details.
But basically it's an audiophiles dream that can cause serious hearing loss and such audio enjoyment at the same time!
The Zip has all the files included to enable "neon" support for convolvers, which are also included.
The feedback I've received so far is 100% success.
INSTRUCTIONS:
1) DOWNLOAD THE ZIP
2) FLASH IN RECOVERY (no need to uninstall if you already have viper installed)
3) open the app and you will be prompted to install the drivers. (I always choose the top one, although it does consume more batter, we'll worth it)
The EQ can be either super simple with just the basic adjustments or can get really technical in "expert" mode.
To activate the convolvers hit the 3 dots in the top right and click click the "ui settings" and change it to expert
Current version Download and discussion starts here
UPDATE VERSION 2.4.0.1 Neon Enabled + Convolvers
If using my previous zip version a simple flash of the new zip will update your V4A.
If you are running any version other than the one in my previous zip you will need to follow the steps below to ensure a smooth update to 2.4.0.1.
1) uninstall current driver from Viper by selecting the option is the app or use file manager and delete "libv4a_fx_ics.so" from system/lib/soundfx.
2) wipe data app with application manager or TiBackup
3) uninstall your current V4A
4) Flash to new zip
5) boot up and enjoy
6) hit the thanks button.
old version
Viper4Android neon enabled including convolvers
Enjoy!
I am on AT&T Galaxy S6 so I cannot have a custom recovery. Can you flash the neon zip using Flashfire? It should work, correct?
Sent from my SAMSUNG-SM-G920A using XDA Free mobile app
It did not work. I ended up having to uninstall the drivers then reinstalling them. So any other way to get NEON working?
Sent from my SAMSUNG-SM-G920A using XDA Free mobile app
Bobthahog said:
It did not work. I ended up having to uninstall the drivers then reinstalling them. So any other way to get NEON working?
Sent from my SAMSUNG-SM-G920A using XDA Free mobile app
Click to expand...
Click to collapse
You flashed using flashfire? You could push the files from the Zip with a file explorer with root access and set permissions to the folders (rwxr-xr-x, 755) and files (rw-r--r--, 644).
You should have it like this
system/priv-app/ViPER4Android_FX_A4.x/lib/arm/libV4AJniUtils.so
system/priv-app/ViPER4Android_FX_A4.x/VIPER4Android_FX_A4.x.apk
system/etc/audio_effects.conf (rw-r--r--, 644)
Also if you a folder located in the system/priv-app/SoundAlive_30, delete or freeze it
I posted this same Zip in my rom thread and have confirmation from AT&T edge and S6 users.
I am having a strange issue on my G920F,
I had a previous version of Viper4Android installed which reported the driver status as normal, I then deleted that version completely because it was installed in the wrong priv-app folder.
I then installed this version via recovery and when I installed the driver it reports the drivers status as abnormal and doesn't even report the sampling rate (reports it as 0), even when installed manually.
stangdriver44 said:
You flashed using flashfire? You could push the files from the Zip with a file explorer with root access and set permissions to the folders (rwxr-xr-x, 755) and files (rw-r--r--, 644).
You should have it like this
system/priv-app/ViPER4Android_FX_A4.x/lib/arm/libV4AJniUtils.so
system/priv-app/ViPER4Android_FX_A4.x/VIPER4Android_FX_A4.x.apk
system/etc/audio_effects.conf (rw-r--r--, 644)
Also if you a folder located in the system/priv-app/SoundAlive_30, delete or freeze it
I posted this same Zip in my rom thread and have confirmation from AT&T edge and S6 users.
Click to expand...
Click to collapse
So, two things -
1) This zip contains a BUNCH of needless folders for what looks like other programs. while they are empty as far as i can tell, they make everything more cluttered (doubly so since they get copied over the the phone...).
2) If you stick with just the 3 files you list there, V4A works but still without NEON support. There is a fourth file however, that one brought over, is the culprit for breaking V4A; under /system/lib/ there is the libV4A_FX_ICS.so. If i replace this file with the one included in your ZIP, then sure enough, like the other powers, V4A goes into abnormal state and is broken until the old file is returned. I suspect you are missing something (or this file is wrong), given the hapazard nature of the entire zip itself....
I love you
For anyone else I had to flash this with flashfire.
If i used twrp I'd get the starting apps splash on loop.
Everything is running great here @stangdriver44!!!! Neon is working and status is normal and my ear drums are now blown out lol. Thanks for everything stang!!!
SwornXIII said:
For anyone else I had to flash this with flashfire.
If i used twrp I'd get the starting apps splash on loop.
Click to expand...
Click to collapse
Hummm, it flashed fine for me with twrp. But thanks a lot for confirming it will flash with flash fire though.
I have tried this option and various other options mentioned in other threads and getting no where. The most I can get with installing the app as userapp is drivers working without Neon and Convuler. I have no luck with this option and always get unsupported. Tried installing via flashfire, twrp and also manually copying files without luck. Also frozen sound_alive and Adapt sound.
Can anyone think of any other issues that I may have overlooked.
SwornXIII said:
For anyone else I had to flash this with flashfire.
If i used twrp I'd get the starting apps splash on loop.
Click to expand...
Click to collapse
Did you already have V4A installed or fresh install?
Sent from my SM-G920V using Tapatalk
I had V4A installed previously. I have tried installing this over existing V4A. Also tried uninstallin/deleting all files and then clean installing this. No luck.
Also, I am on stock kernel rooted with pingpong. I think SElinux is enforcing. I tried the SELinux changer but not sure if that works on samsung phones with knox.
Divine_Madcat said:
So, two things -
1) This zip contains a BUNCH of needless folders for what looks like other programs. while they are empty as far as i can tell, they make everything more cluttered (doubly so since they get copied over the the phone...).
2) If you stick with just the 3 files you list there, V4A works but still without NEON support. There is a fourth file however, that one brought over, is the culprit for breaking V4A; under /system/lib/ there is the libV4A_FX_ICS.so. If i replace this file with the one included in your ZIP, then sure enough, like the other powers, V4A goes into abnormal state and is broken until the old file is returned. I suspect you are missing something (or this file is wrong), given the hapazard nature of the entire zip itself....
Click to expand...
Click to collapse
Did some more reading - the secret sauce for people is needing to run this script:
http://forum.xda-developers.com/showpost.php?p=61242973&postcount=18854
Once done, the .so file i thought was bad works just fine....
Can confirm that above script is what was needed to get everything working fine. Now Neon enabled . Thanks all.
What is ""neon support for convolvers" ?! Thanks!
Schweet! Thanks for this @stangdriver44
this worked like a charm, I had a previous version that neon wasn't enabled on, I flashed this on top and lost Viper4A from my app drawer. I had to go in and delete the old version completely, then fight my way through fc's to reboot at which point I was good to then flash this version, happy to say neon is enabled! thanks for this
sent from my S6 using tapatalk
I flashed this zip and worked right out of the box. Thank you for finally enabling us to use the convolver
---------- Post added at 03:16 AM ---------- Previous post was at 03:14 AM ----------
There is one slight problem but I'm not sure if it's just me. I have a wide range of irs and when I select knew it works but when I select another it sounds exactly the same as the first knew and when I select another random irs it works. Anyone else have this issue
rshift said:
Did you already have V4A installed or fresh install?
Sent from my SM-G920V using Tapatalk
Click to expand...
Click to collapse
Fresh
I fresh installed as well did exactly like it said with the 50viper.sh script and it works perfect. I love using the TRacks Wide.irs
Sent from my SM-G920V using Tapatalk
Im running truepure Rom. Would love to have android pay working, but just cant get it going. Assuming will have to live without for a while...
I have it installed on the stock rooted MM (soak test) and my card is loaded. I have not had a chance to actually use it yet. There aren't many retailers that accept it yet. If I get a chance to use it I'll report back.
rsmiff said:
I have it installed on the stock rooted MM (soak test) and my card is loaded. I have not had a chance to actually use it yet. There aren't many retailers that accept it yet. If I get a chance to use it I'll report back.
Click to expand...
Click to collapse
As I understand, Android pay pretty much only works works with stock ROM due to system system Partition Modifications made on custom Rom's. I understand some devices have had limited luck with Custom Roms but for the most part, Stock only. All that said, I just upgraded to MM 6.0 on Friday and then Rooted using the Beta System less Root method from the forum and Android Pay works like a charm, added cards no problem and works perfect at the retailers that accept it. Most recently, RiteAid in my area. This root is not a full root as I understand but the apps I use get permissions without an issue , Quick Boot is my must have and it works just fine. (Did notice ES File Explorer wont' allow full access to my device but Root Browser did. Adding XPOSED would still disable Android Pay since it modifies the partititons , I really wish that was not the case but I really love Android pay so for now, I might just have to do without it. I am sure you saw the Root Method but just in case, the link is below. Follow the instructions carefully and don't forgot to hit the Do Not Install button in TWRP (Your device does not appear to be rooted) every time you reboot from there . You'll know what I am talking about as soon as you get to that point.
Anyway, good luck!
Mike
http://forum.xda-developers.com/moto-x-style/development/wip-systemless-root-t3263405
EDIT: And I broke pay somehow... So I guess this is not a great guide...
I am having Android pay working on a slightly modded stock rooted MM.
- I did the OTA process (back to stock and side loaded the OTA)
- Installed and setup Android Pay (including cards)
- Installed TWRP 2.8.7.1 in fastboot (link)
- Rooted with Chainfire's systemless autopatcher (link)
- Renamed system\recovery-from-boot.p to .bak in TWRP
- Installed No increased ringtone in TWRP (link)
- Installed and setup AdAway
- Android Pay is still working, I tested it at the vending machine at work.
I have not tried to add the new Google dialer (link), someone in the thread say it doesn't break Android pay.
timeToy said:
I am having Android pay working on a slightly modded stock rooted MM.
- I did the OTA process (back to stock and side loaded the OTA)
- Installed and setup Android Pay (including cards)
- Installed TWRP 2.8.7.1 in fastboot (link)
- Rooted with Chainfire's systemless autopatcher (link)
- Renamed system\recovery-from-boot.p to .bak in TWRP
- Installed No increased ringtone in TWRP (link)
- Installed and setup AdAway
- Android Pay is still working, I tested it at the vending machine at work.
I have not tried to add the new Google dialer (link), someone in the thread say it doesn't break Android pay.
Click to expand...
Click to collapse
I have Android pay working here. stock MM and systemless root. I did try flashing the dialer zip and it did break Android pay. However I moved the required files into place using root explorer and set the correct permissions, and Android pay works no problem.
So it seems that flashing zips that modify the system partition in any way will break Android pay, but not if you modify it while in the OS itself. I've been using the cigital safteynet playground app to check each time I make a modification. Definitely make a backup of /system so you can always restore Android pay functionality if a mod breaks it.
Also using Xposed WILL break Android pay. I try not to miss it much, but honestly I've got my MXPE pretty much perfect for me, and what apps I use that require root are all working well with systemless root.
Sent from my XT1575 using Tapatalk
timeToy said:
- Renamed system\recovery-from-boot.p to .bak in TWRP
Click to expand...
Click to collapse
What does this do?
EVR_PR said:
What does this do?
Click to expand...
Click to collapse
This prevent the stock recovery from overwriting TWRP
I actually have TWRP in read only mode, which allows stock to overwrite it, and the file ends in .p.
Will changing it to .bak allow me to remove the read-only status?
bb12489 said:
However I moved the required files into place using root explorer and set the correct permissions, and Android pay works no problem.
Click to expand...
Click to collapse
Any chance you'd be willing to elaborate on this a little? (i.e. which files, where and the correct permissions)
Thanks!
innoman said:
Any chance you'd be willing to elaborate on this a little? (i.e. which files, where and the correct permissions)
Thanks!
Click to expand...
Click to collapse
Well the flashable zip as the folder structure laid out inside it, so just use that to know where to move the files. Usually the permissions are rw-r-r in most folders, but just check other files in the directories to make sure what permissions to set. That's all I've done to get the dialer working at least. I imagine it works for other things as well.
bb12489 said:
I have Android pay working here. stock MM and systemless root. I did try flashing the dialer zip and it did break Android pay. However I moved the required files into place using root explorer and set the correct permissions, and Android pay works no problem.
Click to expand...
Click to collapse
That didn't work for me, I was able to install the 3.2 dialer just fine using root explorer, but it break Android Pay (Fail Cigital Safteynet Playground)
I try step by step install, testing with Cigital after every step, it fail when I copy the Google Dialer folder to pri-app. How did you do?
timeToy said:
That didn't work for me, I was able to install the 3.2 dialer just fine using root explorer, but it break Android Pay (Fail Cigital Safteynet Playground)
I try step by step install, testing with Cigital after every step, it fail when I copy the Google Dialer folder to pri-app. How did you do?
Click to expand...
Click to collapse
I followed the same steps that bb did and am getting the same results you are. Android Pay was working just fine with systemless root and Adaway, but so far, DPI changes and the Google Dialer have both broken Android Pay for me.
I lost it manually installing the new emoji font pack and google keyboard. I manually copied the files over and fixed the permissions.
I'm stock UK, but I keep getting a popup saying Android Pay isn't available in the UK
Jay794 said:
I'm stock UK, but I keep getting a popup saying Android Pay isn't available in the UK
Click to expand...
Click to collapse
That's because it isn't but it should be coming to the UK in the next few weeks according to rumours.
Sent from my LG-D855 using Tapatalk
CF-Auto-Root's installing SuperSU are available for the Moto Z2 from https://desktop.firmware.mobi/
Search for nash in the search bar!
Thanks to @ac1dx for testing.
Chainfire said:
CF-Auto-Root's installing SuperSU are available for the Moto Z2 from https://desktop.firmware.mobi/
Search for nash in the search bar!
Thanks to @ac1dx for testing.
Click to expand...
Click to collapse
Root is there. Just as buggy as Magisk with this dual partition phone. Can't remove system apps with Titanium Backup. Can't set some things as r/w with root browser. Besides flashing the boot.img, is there anything else that needs to be done as some parts of system are r/o still or do we need twrp for full system access with this device?
Edit: as explained later in thread, this isn't an issue with CFAR, it's an issue with apps not working correctly with our boot partitions and directories.
Uzephi said:
Root is there. Just as buggy as Magisk with this dual partition phone. Can't remove system apps with Titanium Backup. Can't set some things as r/w with root browser. Besides flashing the boot.img, is there anything else that needs to be done as some parts of system are r/o still or do we need twrp for full system access with this device?
Click to expand...
Click to collapse
I have full system access. I have deleted both bootanimation zips to get the stock Android boot animation going. I have deleted some of the T-Mobile bloat. This was done with root explorer. All rooted apps work as they did with any other phone. I even flashed BusyBox with flashfire. But I think BusyBox is a little buggy on here. Not 100% sure lol.
Sent from my Moto Z (2) using Tapatalk
ac1dx said:
I have full system access. I have deleted both bootanimation zips to get the stock Android boot animation going. I have deleted some of the T-Mobile bloat. This was done with root explorer. All rooted apps work as they did with any other phone. I even flashed BusyBox with flashfire. But I think BusyBox is a little buggy on here. Not 100% sure lol.
Click to expand...
Click to collapse
I wish mine was that easy. You use Sprint model?. Below are attached images. Flashed stock removed Magisk then flashed CF.
One is TB showing root access. One is the error can't find APK. Then SU screen shot showing root. And the last one is the error when trying to move (not copy, but cut/paste) a system app to SD.
Edit: Chainfire, it seems the method for T-mob either isn't working the same for sprint or with dual boot.imgs there is some odd issue after updating. If you need logs, let me know how to help
Deleted.
Please see below.
ac1dx said:
I tried for the heck of it and it worked.
Oh, your on Sprint. No I'm on Tmobile. Wonder if it's boot image specifically to gsm and cdma.
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
I would think Chainfire did the same edits to T-Mob img as Sprint. (using their corresponding boot images) did yours flash boot_a or Boot_b? Mine flashed Boot_b
Edit:
C:\Users\Uzephi\Downloads>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_b' (20457 KB)...
OKAY [ 0.506s]
writing 'boot_b'...
OKAY [ 0.408s]
finished. total time: 0.918s
C:\Users\Uzephi\Downloads>fastboot reboot
rebooting...
finished. total time: 0.003s
C:\Users\Uzephi\Downloads>
Uzephi said:
I wish mine was that easy. You use Sprint model?. Below are attached images. Flashed stock removed Magisk then flashed CF.
One is TB showing root access. One is the error can't find APK. Then SU screen shot showing root. And the last one is the error when trying to move (not copy, but cut/paste) a system app to SD.
Edit: Chainfire, it seems the method for T-mob either isn't working the same for sprint or with dual boot.imgs there is some odd issue after updating. If you need logs, let me know how to help
Click to expand...
Click to collapse
It is different. Judging by the Magisk thread, you guys have a boot image for Sprint and one for TMobile.
Sent from my Moto Z (2) using Tapatalk
---------- Post added at 12:57 AM ---------- Previous post was at 12:54 AM ----------
Uzephi said:
I would think Chainfire did the same edits to T-Mob img as Sprint. (using their corresponding boot images) did yours flash boot_a or Boot_b? Mine flashed Boot_b
Edit:
C:\Users\Uzephi\Downloads>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_b' (20457 KB)...
OKAY [ 0.506s]
writing 'boot_b'...
OKAY [ 0.408s]
finished. total time: 0.918s
C:\Users\Uzephi\Downloads>fastboot reboot
rebooting...
finished. total time: 0.003s
C:\Users\Uzephi\Downloads>
Click to expand...
Click to collapse
Yes. It is boot_b. I know it's weird and we are all gonna have to get used to it lol. Hopefully roms are easy.
Sent from my Moto Z (2) using Tapatalk
ac1dx said:
It is different. Judging by the Magisk thread, you guys have a boot image for Sprint and one for TMobile.
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
Yes, We have different boot images and I downloaded the one specifically made for sprint by Chainfire per the linked website.
Uzephi said:
Yes, We have different boot images and I downloaded the one specifically made for sprint by Chainfire per the linked website.
Click to expand...
Click to collapse
I'm stumped then.
Sent from my Moto Z (2) using Tapatalk
ac1dx said:
I'm stumped then.
Click to expand...
Click to collapse
I found it out. Titanium Backup cannot find app due to it being in oem and not /sys. Removed Chrome and it worked and is a system app. All apps in system/app can be removed besides the one app I tried:Translate. Bug on my phone? Maybe... Attached images of the issue. One showing oem/app being Amazon, audible, etc. Second showing only translate not having correct perms in root browser. Odd.....
Uzephi said:
I found it out. Titanium Backup cannot find app due to it being in oem and not /sys. Removed Chrome and it worked and is a system app. All apps in system/app can be removed besides the one app I tried:Translate. Bug on my phone? Maybe... Attached images of the issue. One showing oem/app being Amazon, audible, etc. Second showing only translate not having correct perms in root browser. Odd.....
Click to expand...
Click to collapse
I have the same issue.
Sent from my Moto Z (2) using Tapatalk
filthyfnj24 said:
I have the same issue.
Click to expand...
Click to collapse
When all else fails, use lucky patcher. Just be sure the stock image will flash for you. It won't back up apps, but it removed all my bloat I wanted to remove...
Edit: tried removing Translate. The one System/app that has wrong permissions. Lucky Patcher was about to remove it, hard reboot and it's still there with the wrong permissions. I guess translate is a must on stock?
Uzephi said:
When all else fails, use lucky patcher. Just be sure the stock image will flash for you. It won't back up apps, but it removed all my bloat I wanted to remove...
Edit: tried removing Translate. The one System/app that has wrong permissions. Lucky Patcher was about to remove it, hard reboot and it's still there with the wrong permissions. I guess translate is a must on stock?
Click to expand...
Click to collapse
hey for all those that have root i use a program called root uninstaller pro..i do not have any of the permissions issues that you guys have with titanium backup i was able to very easily completely de bloat the phone..
Uzephi said:
Root is there. Just as buggy as Magisk with this dual partition phone. Can't remove system apps with Titanium Backup. Can't set some things as r/w with root browser. Besides flashing the boot.img, is there anything else that needs to be done as some parts of system are r/o still or do we need twrp for full system access with this device?
Click to expand...
Click to collapse
This is not an issue with SuperSU (or Magisk). This is an issue with Titanium Backup (and many other tools) not being fully able to cope with the partition setup on newer devices yet.
Uzephi said:
Edit: Chainfire, it seems the method for T-mob either isn't working the same for sprint or with dual boot.imgs there is some odd issue after updating. If you need logs, let me know how to help
Click to expand...
Click to collapse
I don't understand what you mean, please elaborate.
The T-Mobile and Sprint images do the same thing. CFAR/SuperSU uses a different method than Magisk. The Magisk images are pre-rooted, while the CFAR images patch the boot image present on your device when you boot it. In other words, if both the T-Mobile and Sprint root images are able to boot on your device, what they do is identical, and you'd end up with an identical root.
In case of any issues, try 'fastboot flash'ing back the stock boot image, before 'fastboot boot'ing the CFAR.
Chainfire said:
This is not an issue with SuperSU (or Magisk). This is an issue with Titanium Backup (and many other tools) not being fully able to cope with the partition setup on newer devices yet.
I don't understand what you mean, please elaborate.
The T-Mobile and Sprint images do the same thing. CFAR/SuperSU uses a different method than Magisk. The Magisk images are pre-rooted, while the CFAR images patch the boot image present on your device when you boot it. In other words, if both the T-Mobile and Sprint root images are able to boot on your device, what they do is identical, and you'd end up with an identical root.
In case of any issues, try 'fastboot flash'ing back the stock boot image, before 'fastboot boot'ing the CFAR.
Click to expand...
Click to collapse
I figured it out. The apps I was testing root with were exactly what you describe. TB and an odd permission error with translate. Root works. My later posts go into detail. It's just the oddities with possibly two boot partitions or just an idiosyncrasy on our phone why translate has different permissions than all other files.
Thanks for getting CFAR working on our phone.
raver445 said:
hey for all those that have root i use a program called root uninstaller pro..i do not have any of the permissions issues that you guys have with titanium backup i was able to very easily completely de bloat the phone..
Click to expand...
Click to collapse
Can you remove Translate? for some reason on my Sprint model it doesn't have correct permissions to remove it on any root app.
Uzephi said:
Can you remove Translate? for some reason on my Sprint model it doesn't have correct permissions to remove it on any root app.
Click to expand...
Click to collapse
I have the T-Mobile variant but but I do remember being able to remove all bloatware applications except for one of the Google applications and it wasn't translate that wasn't able to be removed it was Google Sheets. But yes translate should be able to be removed
Sent from my LGLS992 using Tapatalk
raver445 said:
I have the T-Mobile variant but are you talking about Google Translate?
Sent from my LGLS992 using Tapatalk
Click to expand...
Click to collapse
Yes. If you see my last post on page 1 you will see translate has different permissions than other system/ apps causing it to not be removed by any root app on my Sprint model. I wonder if it's sprint only, Z2 Force only or something just with my phone with the dual boot partition causing oddities.
I'm figuring it's probably just Sprint Sprint version causing the problems can you send me some screenshots please
Sent from my LGLS992 using Tapatalk
raver445 said:
I'm figuring it's probably just Sprint Sprint version causing the problems can you send me some screenshots please
Sent from my LGLS992 using Tapatalk
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=73858447&postcount=10 Post 10 has the screenshot of what the issue is. Check rw permissions in root browser. All system/app folders have drwxr-xr-x while only the translate folder has drw-------- meaning there is something causing translate to not be able to be written over/deleted. I tried with console commands and root browser to modify permissions of the file but access denied error. When I tried to remove with another app, Lucky Patcher, it was about to remove then the phone rebooted and the system/app was still there.
Exist an easy way to export magisk module list? Export and import?
Clarifications needed... Which list are you talking about? The entire Magisk repo or just the ones you've installed (I'm gonna guess the latter)? And for what purpose?
Didgeridoohan said:
Clarifications needed... Which list are you talking about? The entire Magisk repo or just the ones you've installed (I'm gonna guess the latter)? And for what purpose?
Click to expand...
Click to collapse
only the one i have installed. full list for backup / reinstall purpose. installed and not active. xposed ha a function to export /import list. I like it.
If you just need a backup, make a backup of the Magisk image (/data/adb/magisk.img). That's where all modules are kept (for now, this might change in a future version of Magisk).
Didgeridoohan said:
If you just need a backup, make a backup of the Magisk image (/data/adb/magisk.img). That's where all modules are kept (for now, this might change in a future version of Magisk).
Click to expand...
Click to collapse
oh. perfect. no problem. can i restore? like in a rom change to a new rom? what is status for enabled disabled module?
simona70 said:
oh. perfect. no problem. can i restore? like in a rom change to a new rom? what is status for enabled disabled module?
Click to expand...
Click to collapse
I do this all the time.. back the files in location mentioned above to ext sdcard...wipe device for a clean flash (all except ext sdcard/EFS obviously)...flash new ROM, then flash gapps, then flash magisk, then still in TWRP, I copy the files back to correct location and reboot
73sydney said:
I do this all the time.. back the files in location mentioned above to ext sdcard...wipe device for a clean flash (all except ext sdcard/EFS obviously)...flash new ROM, then flash gapps, then flash magisk, then still in TWRP, I copy the files back to correct location and reboot
Click to expand...
Click to collapse
Thanks. Providential.
73sydney said:
I do this all the time.. back the files in location mentioned above to ext sdcard...wipe device for a clean flash (all except ext sdcard/EFS obviously)...flash new ROM, then flash gapps, then flash magisk, then still in TWRP, I copy the files back to correct location and reboot
Click to expand...
Click to collapse
Where are the ZIP files located, in case I just want to backup those rather than the img?
oroboros74 said:
Where are the ZIP files located, in case I just want to backup those rather than the img?
Click to expand...
Click to collapse
Zip files are not saved. It gets extracted in to the location as mentioned in this thread. But each time you flash a module the zip file is downloaded in to Download folder of your internal storage. Save it for future use.
Now /data/adb/magisk.img is no more used... What folder must I backup?
Didgeridoohan said:
If you just need a backup, make a backup of the Magisk image (/data/adb/magisk.img). That's where all modules are kept (for now, this might change in a future version of Magisk).
Click to expand...
Click to collapse
Hi how can i find data/adb/magisk/img
Sk7007 said:
Hi how can i find data/adb/magisk/img
Click to expand...
Click to collapse
That's an old post you're quoting, and the last part of it has come true...
All modules are currently stored in /data/adb/modules.
Didgeridoohan said:
That's an old post you're quoting, and the last part of it has come true...
All modules are currently stored in /data/adb/modules.
Click to expand...
Click to collapse
How to backup now then?
Sent from my motorola one power using Tapatalk
Always wondered the same..
73sydney said:
I do this all the time.. back the files in location mentioned above to ext sdcard...wipe device for a clean flash (all except ext sdcard/EFS obviously)...flash new ROM, then flash gapps, then flash magisk, then still in TWRP, I copy the files back to correct location and reboot
Click to expand...
Click to collapse
All modules are currently stored in /data/adb/modules. Would the concept of copying the files back to the correct location still work after a reboot?
rodken said:
All modules are currently stored in /data/adb/modules. Would the concept of copying the files back to the correct location still work after a reboot?
Click to expand...
Click to collapse
I actually havent tried it since the change from the img method
I can tell you i do backup and restore the magisk.db file....i have a Galaxy Active2 Watch, and if it even sniffs root i have to reset the watch and start over to get Samsung Pay working. So i flash the ROM/GApps, then Magisk, reboot and setup the ROM and Magisk, set my Android ID back to the previous one (to avoid having to reset the Watch, and have it connectable in Gear app) then copy the magisk.db to /data/adb, then reboot. Then enable MagiskHide, and hide Magisk Manager. When i restore my apps the Samsung ones are already in the MagiskHide list and Samsung Pay works as before, once i reconnect the watch.
Next time i flash ill try copying back the /data/adb/modules and let you know
rodken
Just a quick update
I was about to flash a new ROM for testing, and thought about doing the test...copy the modules folder from /data/adb, and restore on new ROM and then realised that not all modules im using are going to like that, as some set symbolic links during install and some now use filesystem overlays as well (thinking busybox and Vanced Youtube)
Ive just decided rather than copying im going to stick with what works 100%, and install them by hand one by one
73sydney said:
rodken
Just a quick update
I was about to flash a new ROM for testing, and thought about doing the test...copy the modules folder from /data/adb, and restore on new ROM and then realised that not all modules im using are going to like that, as some set symbolic links during install and some now use filesystem overlays as well (thinking busybox and Vanced Youtube)
Ive just decided rather than copying im going to stick with what works 100%, and install them by hand one by one
Click to expand...
Click to collapse
Thanks for the update.