Develop Bugs

[Q] Installing Hulu in other ROMs

I'm trying to nail down the exact procedure for installing Hulu into Roms other than SkyRaider. Specifically I am currently using HeyItsLouFroyo which after trying all the ROMs I could find worked the best.
So far I have downloaded the Hulupack.zip from the OP of this thread http://forum.xda-developers.com/showthread.php?t=764787&highlight=hulu
and the Hulu.apk.zip file from an update to the same thread http://forum.xda-developers.com/showthread.php?p=7903587&highlight=hulu#post7903587
I tried installing the "install_huluflash_player.apk" but it gave me an error during the install something to the effect of "Application was not installed". From there I installed the "Hulu.apk" which installed successfully. Next I tried "flash_fixed_final.apk" which gave me the same error as the original flash install. Just for grins I launched the Hulu app and to my surprise it seemed to be working until I got a message that said "Unfortunately Hulu is not supported on your platform" I have not installed the updated hulu.apk that I found later in the thread yet. I wanted to first start a thread and see if you guys can save me some time and frustration by telling me what the proper process is for getting this working.
Any help is appreciated. Thanks.

It looks like I may have posted this in the wrong spot. Can someone please move this to the correct spot or tell me how I can move it and where to?

Bump bump
Sent from my ADR6300 using Tapatalk

subscribed, i've actually been trying to figure this one one since 9am tried everything found in every 2.2 thread

Did you uninstall old files first?

daftlush said:
Did you uninstall old files first?
Click to expand...
Click to collapse
I did not. I just removed the flash app via Titanium and tried to install the flash_fixed_final.apk but received the same error as before.
Now I have no flash at all and still can't install flash. HMMM, now what?

Wait, alright I rebooted and after the reboot I was able to install the new version of flash. I opened hulu and it seems to be working now except it has this issue where the voices are super slow. I remember reading something about this in another forum but I think it was fixed by an update to the ROM. Anyone know how to fix the demon voices?

I have a 100% working Hulu now.
The fix for the demon audio was found in another forum. Here is what I did.
1. Opened Rom Manager
2. Selected "Download ROM"
3. Selected "Ihtfp69"
4. Selected "Goodies for 2.2+"
5. Clicked on the "Download" button
6. Checked the checkbox next to "Revert Audio Fix" and clicked OK.

So now the new Busy Box update is borked??? WiFi don't work!!!

WTF...First there were a million updates to Super User till the dev broke that about a month ago.
Now I update Busy Box in the market today and my WiFi connection won't work properly...Not having any idea that it could even be Busy Box's fault I started doing a serch and others are having the same problem after the new Busy Box update.
And I just installed the newest ota update so I don't have an old nandroid to restore to.
The WiFi will work sometimes but slow and not seem to respond at all other times...weird.

Can you uninstall updates through Settings > Applications?
Edit: Actually, is busybox even necessary anymore? I just realized I'm on McD's ICS ROM and I don't seem to have busybox installed. I've restored all of my apps through Titanium and it never prompted me to install.
Sent from my ADR6300 using XDA App

Now I am having problems with TB, don't know if its busy box related. Just tried to integrate maps and now it is gone from my phone.

I updated earlier and have had no issues. I dont see how it would mess anything up as it was just an update to the app (which is basicly just an updater) not the busybox binary which is what actually performs all the actions.

cmlusco said:
I updated earlier and have had no issues. I dont see how it would mess anything up as it was just an update to the app (which is basicly just an updater) not the busybox binary which is what actually performs all the actions.
Click to expand...
Click to collapse
Thats what I was thinking. But all of a sudden have just started having some weird issues. Maybe a coincidence.
And now had my first problem with TB integrating an app, but I think TB uses another version of Busy Box so I dunno.

Hand76 said:
Thats what I was thinking. But all of a sudden have just started having some weird issues. Maybe a coincidence.
And now had my first problem with TB integrating an app, but I think TB uses another version of Busy Box so I dunno.
Click to expand...
Click to collapse
I believe your right, TB has busybox built into it.

I'm also expieriencing broken WiFi after updating busybox last night. Now running 1.19.3 - woke up today and my phone was super hot (110 F), battery was at 80% when I unplugged it and WiFi is stuck on 'obtaining IP address'
I'm unable to get wifi to work on my home wireless where I have WPA secuirty setup, or on my work's wireless where I have no security.
I've been trying various suggestions posted in other threads and on other forums but nothing has resolved the issue. I'll keep at it when I have free time today and update this thread if I have any success..
EDIT: not sure if it's worth mentioning or not, but Root File explorer seems to be broken as well, opening up to a blank screen that just says 'Root Explorer' on top. Have to hit the home key to exit the program.
______________
Should mention, phone is an AT&T Samsung Galaxy S2 runningSerendipity 8.2 ROM w/ Entropy's kernel

cmlusco said:
I believe your right, TB has busybox built into it.
Click to expand...
Click to collapse
This is correct, it has it built into the app.

I got it working by setting a static IP. Hardly a fix, but wifi is working now.
I have no idea what the root cause of this is.. or if it's even related to busybox.
Apologies if I've hijacked the thread (having completely different hardware and all) but I believe we share the same issue. I'm planning on flashing to a new ROM soon if I can't get DHCP working again.
EDIT: Root Explorer still not working though, & eventually force closes if not exited with home button.

If you believe the new busybox is the problem just open it up and install the previous version.

RamAir02 said:
Can you uninstall updates through Settings > Applications?
Edit: Actually, is busybox even necessary anymore? I just realized I'm on McD's ICS ROM and I don't seem to have busybox installed. I've restored all of my apps through Titanium and it never prompted me to install.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
busybox is baked into most roms now.

cmlusco said:
If you believe the new busybox is the problem just open it up and install the previous version.
Click to expand...
Click to collapse
I tried that and it didn't resolve the issue. I'm unable to remove it because I don't have the full version..
--Update (day after). Flashed to cm7 last night and everything's good now. I don't have the patience to troubleshoot lately.

Need help getting Viper/ARISE working on stock, rooted setup

I've spent way too long trying to get this working without any success.
If I flash a custom ROM (ie. Pure Nexus), I can flash the ARISE zip (ARISE+Deuteronomy+2.94+Modular+AROMA+Installer.zip) and it works perfectly. No driver issues, or anything.
When running stock, rooted, after flashing the above zip file, it appears to flash successfully, but when I open the app after rebooting, it always says that the drivers are missing and offers to install them. If I choose the option to install the drivers, it always fails.
I learned that if you're on stock, you have to flash a custom kernel before it'll actually flash (and auto install the apk), so I tried with franco and elemental kernels.
Does anyone know the steps I'm missing? I'm wondering if maybe it's because I need busybox, but I'm not sure where to install busybox (or the best method).
I know there has to be a way to get this working. I'm sure I'm missing something simple.
Thanks in advance!

eleazar123 said:
I've spent way too long trying to get this working without any success.
If I flash a custom ROM (ie. Pure Nexus), I can flash the ARISE zip (ARISE+Deuteronomy+2.94+Modular+AROMA+Installer.zip) and it works perfectly. No driver issues, or anything.
When running stock, rooted, after flashing the above zip file, it appears to flash successfully, but when I open the app after rebooting, it always says that the drivers are missing and offers to install them. If I choose the option to install the drivers, it always fails.
I learned that if you're on stock, you have to flash a custom kernel before it'll actually flash (and auto install the apk), so I tried with franco and elemental kernels.
Does anyone know the steps I'm missing? I'm wondering if maybe it's because I need busybox, but I'm not sure where to install busybox (or the best method).
I know there has to be a way to get this working. I'm sure I'm missing something simple.
Thanks in advance!
Click to expand...
Click to collapse
I think not only do you need Busybox (you should just be able to download this from the play store now you're rooted) you will also need a way of setting SELinux to permissive. Try The SELinux toggler.

rename/remove /vendor/etc/audio_effects.conf

grifforama said:
I think not only do you need Busybox (you should just be able to download this from the play store now you're rooted) you will also need a way of setting SELinux to permissive. Try The SELinux toggler.
Click to expand...
Click to collapse
Shawn haz root said:
rename/remove /vendor/etc/audio_effects.conf
Click to expand...
Click to collapse
Thank you both! I will try all of those solutions right now.
When I tried to install busybox via the play store installer to /system/xbin/, it says "It looks like the installation of BusyBox was not successful. Try installing to a different location, that may resolve the issue".
My understanding is that I need to put it in /system/xbin. Do you guys have any ideas? The busybox installer was granted root when I first opened it, so I know it has root access. :\

eleazar123 said:
Thank you both! I will try all of those solutions right now.
When I tried to install busybox via the play store installer to /system/xbin/, it says "It looks like the installation of BusyBox was not successful. Try installing to a different location, that may resolve the issue".
My understanding is that I need to put it in /system/xbin. Do you guys have any ideas? The busybox installer was granted root when I first opened it, so I know it has root access. :\
Click to expand...
Click to collapse
I'd be interested to hear how you get on.
I have Viper4Arise installed, Busybox installed, and it appears to be working (sometimes it just doesn't) but when it does, I don't hear any difference when I apply my convolver irs .

grifforama said:
I'd be interested to hear how you get on.
I have Viper4Arise installed, Busybox installed, and it appears to be working (sometimes it just doesn't) but when it does, I don't hear any difference when I apply my convolver irs .
Click to expand...
Click to collapse
When I was running custom roms, it worked perfectly and I could tell a major difference in the music.
How did you get busybox installed? I can't figure out why the play store installer is failing. It's also failing for my friend on his Pixel XL (also rooted)

eleazar123 said:
When I was running custom roms, it worked perfectly and I could tell a major difference in the music.
How did you get busybox installed? I can't figure out why the play store installer is failing. It's also failing for my friend on his Pixel XL (also rooted)
Click to expand...
Click to collapse
If you install an app called "root browser classic", the second you open it, it requests to install an add on which is busy box. Then close and open it again and it asks to update which takes you to the Google play store then installed the busy box app. Not exactly a conventional way but I just tried and it installed. Not sure if that will help you or not.
Root browser
https://play.google.com/store/apps/details?id=com.jrummyapps.rootbrowser.classic
Busy box
https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer
I also installed this with no issues
https://play.google.com/store/apps/details?id=stericson.busybox

Shawn haz root said:
If you install an app called "root browser classic", the second you open it, it requests to install an add on which is busy box. Then close and open it again and it asks to update which takes you to the Google play store then installed the busy box app. Not exactly a conventional way but I just tried and it installed. Not sure if that will help you or not.
Root browser
https://play.google.com/store/apps/details?id=com.jrummyapps.rootbrowser.classic
Busy box
https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer
I also installed this with no issues
https://play.google.com/store/apps/details?id=stericson.busybox
Click to expand...
Click to collapse
Thank you! That jrummy busy box installer worked perfectly the first time. I confirmed in the stericson version that busy box is really installed.
I went ahead and flashed the arise zip file, and it has an option to set SELinux to permissive. Unfortunately upon reboot, it was the same drivers not installed error
I'm now thinking my issue might be the audio_effect.conf file. I've tried Solid Explorer (my go to file explorer) and Root Browser that you linked above. Both explorers have been granted root, but neither can actually rename the file (or delete it). Jrummy's app just says operation denied, while solid explorer shows the file gone, but if you refresh, it's right back where it was. I'm struggling to find a way to mount system r/w in either app. Do you have any ideas? :\
I tried to find a tool to set SELinux to permissive and i found lots of kernel tuning apps, but none that actually allowed setting permissive. Even Franco's own app for his kernel doesn't have that option (he said it's something about trying to keep it more secure). Hopefully the arise zip is really setting it properly, it's just the audio_effects issue causing my problem.
Thanks again for your help, guys!

SafteyNet Compatibility Test fails but all apps work.

Fairly new to rooting and stuff so ignore the "noobness" of my words. So i recently rooted my OnePlus 5T using Magisk v16. Everything was and is working smoothly all the apps work even google pay. But today i tried checking the saftey net status using magisk and i get an error saying "response is invalid" i am not sure what that means. I used a root checker app to check the saftey net compatibility status and it says Failed. I am not sure if it's failing how are all of the apps from google play work fine? What is wrong.
Again i am fairly new to the lingo so please if someone can explain what exactly saftey net test is and how can i fix this issue so that it passes. Any help is appreciated.

We can't fix it buddy :silly:
https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post77329420

So basically everything is fine? No need to worry? Cause everything works okay for me

haroonqamar said:
So basically everything is fine? No need to worry? Cause everything works okay for me
Click to expand...
Click to collapse
Something is definitely down.
Currently everyone just fails safetynet worldwide.
They get the invalid response error.
It should be fine and you should be able to use all your apps.
What i did notice that cause of this i cant see some apps in the play store so you have to use apkmirror to get them.

cikeZ00 said:
The something is definitely down.
Currently everyone just fails safetynet worldwide.
They get the invalid response error.
It should be fine and you should be able to use all your apps.
What i did notice that cause of this i cant see some apps in the play store so you have to use apkmirror to get them.
Click to expand...
Click to collapse
You can check the safetynet status with root checker!
https://play.google.com/store/apps/details?id=org.freeandroidtools.root_checker

Magisk No root prompts

^title, I haven't done anything new and all of the sudden today my magisksu will not prompt when apps request root with the log only saying superuser denied. I googled it and found posts dating back to 2017 about issues with this (which seems to happen 100% of the time when I have issues). I've done the fixes people said worked for them (turning off adaptive battery, repackaging magisk manager, rolling back to older magisk, taking magisk manager off the optimizing battery list, installing some adb fastboot ndk module thing, reinstalling magisk, full uninstall and reinstall, reflashing /boot /system and /vendor back to factory image stock.) and no luck. Has anyone else fixed this without a factory reset/reflash? Also at the same time this issue popped up I'm also having a really annoying time getting apps to install from the play store, it'll download say for instance 2.50 MB/2.50 MB 100% and just sit there for literally minutes before the app randomly says it's installed after the screen blacks out.
Oh also I'm getting no errors at all in the magisk log even entry is an informative.
Update: I was able to get solidexplorer to request root successfully but it literally too 3 minutes of waiting for the prompt to appear. I'm also getting errors in the log "write failed with 32: broken pipe" which I also saw in that forum post from 2017.

StykerB said:
^title, I haven't done anything new and all of the sudden today my magisksu will not prompt when apps request root with the log only saying superuser denied. I googled it and found posts dating back to 2017 about issues with this (which seems to happen 100% of the time when I have issues). I've done the fixes people said worked for them (turning off adaptive battery, repackaging magisk manager, rolling back to older magisk, taking magisk manager off the optimizing battery list, installing some adb fastboot ndk module thing, reinstalling magisk, full uninstall and reinstall, reflashing /boot /system and /vendor back to factory image stock.) and no luck. Has anyone else fixed this without a factory reset/reflash? Also at the same time this issue popped up I'm also having a really annoying time getting apps to install from the play store, it'll download say for instance 2.50 MB/2.50 MB 100% and just sit there for literally minutes before the app randomly says it's installed after the screen blacks out.
Oh also I'm getting no errors at all in the magisk log even entry is an informative.
Update: I was able to get solidexplorer to request root successfully but it literally too 3 minutes of waiting for the prompt to appear. I'm also getting errors in the log "write failed with 32: broken pipe" which I also saw in that forum post from 2017.
Click to expand...
Click to collapse
Are you using Adware?
Edit: @StykerB My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'

Homeboy76 said:
Are you using Adware?
Click to expand...
Click to collapse
Can you be specific?
-----
I don't have "adwares" but I have the same issue too. Surprisingly it persists when I reverted to last known good version. Which makes everything strange.
I could not afford a clean format at the moment. But until I have the time to do it (and hopefully it goes away), any suggestions to solve this would be extremely appreciated.
I am not using Pixel 3, but I use Nokia 6. Someone told me that it's a common Nokia issue, but being brought here at a very different device forum kind of prove a point that this is a bug that has to do with Magisk, and not Nokia-specific (or device-specific as for this case (maybe)) issue.

TechnoSparks said:
Can you be specific?
-----
I don't have "adwares" but I have the same issue too. Surprisingly it persists when I reverted to last known good version. Which makes everything strange.
I could not afford a clean format at the moment. But until I have the time to do it (and hopefully it goes away), any suggestions to solve this would be extremely appreciated.
I am not using Pixel 3, but I use Nokia 6. Someone told me that it's a common Nokia issue, but being brought here at a very different device forum kind of prove a point that this is a bug that has to do with Magisk, and not Nokia-specific (or device-specific as for this case (maybe)) issue.
Click to expand...
Click to collapse
My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'

Homeboy76 said:
My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Click to expand...
Click to collapse
The page didnt help with my issue unfortunately
-------------------------------
I managed to solve my issue by actually formatting everything (including data). Painful 2 hrs for me lel. Now on 6.1 Manager and 7.3 Magisk and everything works as it should.
Since I formatted data, the issue may have something to do with magisk's leftover files.
Still, the problem with 18.x and 7.0 manager will always happen if i update. Fun fact: if you play around the root settings in Magisk Mgr, you may have a luck and the root prompt will appear. Unfortunately, the root prompt will only appear for the current boot. If you reboot, the problem is there again. Use this window of freedom to grant root to your apps.

TechnoSparks said:
The page didnt help with my issue unfortunately
-------------------------------
I managed to solve my issue by actually formatting everything (including data). Painful 2 hrs for me lel. Now on 6.1 Manager and 7.3 Magisk and everything works as it should.
Since I formatted data, the issue may have something to do with magisk's leftover files.
Still, the problem with 18.x and 7.0 manager will always happen if i update. Fun fact: if you play around the root settings in Magisk Mgr, you may have a luck and the root prompt will appear. Unfortunately, the root prompt will only appear for the current boot. If you reboot, the problem is there again. Use this window of freedom to grant root to your apps.
Click to expand...
Click to collapse
Just a thought and maybe you do it but after each update instead of just directly rerooting, run the magisk uninstaller first.
Flash update
Reboot
Boot back to bootloader
Install TWRP, your phones method
Flash Magisk uninstaller.zip
Flash custom kernel if applicable
Flash magisk.zip
Reboot

Tulsadiver said:
Just a thought and maybe you do it but after each update instead of just directly rerooting, run the magisk uninstaller first.
Flash update
Reboot
Boot back to bootloader
Install TWRP, your phones method
Flash Magisk uninstaller.zip
Flash custom kernel if applicable
Flash magisk.zip
Reboot
Click to expand...
Click to collapse
Already did that too my friend. But never mind. I am done for