Hey Guys,
I need to send my phone in to Rogers in Canada since my texts don't work for no reason even though I haven't switched ROMS in a long time so i don't know why it hasnt been working but my question is..other than flashing stock firmware is there anything else I need to do before I send it in? if so, what and how?
Thanks in advance!
Yes. Before unrooting you should clear your binary using the Triangle Away app. Since this seems like a software issue they may check. Also make sure to unroot it and not just flash the stock ROM like any other ROM
Sent from my Samsung Galaxy S4 (SGH-i337) via Tapatalk 4
r8revealed said:
Yes. Before unrooting you should clear your binary using the Triangle Away app. Since this seems like a software issue they may check. Also make sure to unroot it and not just flash the stock ROM like any other ROM
Sent from my Samsung Galaxy S4 (SGH-i337) via Tapatalk 4
Click to expand...
Click to collapse
thanks! hmm now to find out how do to all of the following steps...lol
Well in simpler terms, first download the app triangle away, and clear your binary (I think it works with the S4, check on that again so nothing goes wrong.) Then just backup anything if you need to. Also before unrooting via ODIN, you might want to do a factory reset and all that stuff in your custom recovery prior to your unroot. I think there should be plenty of tutorials on YouTube to help you through this have fun
Sent from my Samsung Galaxy S4 (SGH-i337) via Tapatalk 4
Make a backup of everything with Titanium Backup. I'd also make a nandriod so when they give you your new phone you can go back to where you were easily
Sent from my SAMSUNG-SGH-I337 using xda premium
I used screen mirroring with my Samsung Blu-ray player occasionally, and it stopped working when I upgraded to 4.3. I updated the firmware on the blu-ray and restarted the phone, but the problem persists. The phone will briefly connect (the blu-ray will say "Galaxy S4 connected), but then quickly disconnect. My wife's Note 3 is stock 4.3 and screen mirroring works fine.
I'm still using the MF9 bootloader, but have flashed the MK2 modem and the rooted stock ROM ( http://forum.xda-developers.com/showthread.php?t=2586586 ); I'm also using Wanam Xposed. My searches have led me to believe that screen mirroring won't work without a stock setup. Is that right? I was going to start flashing some other ROMs or some of my earlier Nandroids to see if that fixes the issue, but thought I'd ask about this first before undertaking that project.
Screen mirroring and root are a no go. You will need to return to stock unrooted for it to work. DLNA is the culprit here and disables mirroring while rooted.
cruise350 said:
Screen mirroring and root are a no go. You will need to return to stock unrooted for it to work. DLNA is the culprit here and disables mirroring while rooted.
Click to expand...
Click to collapse
Thanks for the reply. Do you know if this is this new in 4.3? I was running stock rooted 4.2.2 and screen mirroring worked.
nobody291 said:
Thanks for the reply. Do you know if this is this new in 4.3? I was running stock rooted 4.2.2 and screen mirroring worked.
Click to expand...
Click to collapse
You must have been using a custom kernel that allowed you to do it while rooted because it shouldn't have worked on 4.2.2 either if you were rooted. Look into one of the custom kernels in the original development section to see if they support rooted screen mirroring. I know this was the case with the allshare cast dongle thingy. Not sure if it is also the case with a samsung tv or blue ray player.
Sent from my icrap 2 using Tapatalk HD
Im having the same issue with my mirroring
cruise350 said:
You must have been using a custom kernel that allowed you to do it while rooted because it shouldn't have worked on 4.2.2 either if you were rooted. Look into one of the custom kernels in the original development section to see if they support rooted screen mirroring. I know this was the case with the allshare cast dongle thingy. Not sure if it is also the case with a samsung tv or blue ray player.
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
Hey bro im having the same issues let me know if you figure this out, Im kinda new to this rooting stuff
id really appreciate the help.
Thankz
pepe7807684 said:
Hey bro im having the same issues let me know if you figure this out, Im kinda new to this rooting stuff
id really appreciate the help.
Thankz
Click to expand...
Click to collapse
Sadly, no. If you search the entire XDA forum, you'll find some in-depth discussions of the issue related to the Note and other Samsung phones. When I have time, I want to experiment more. I did try one of the modified kernels, but couldn't get wifi to work with it. When I have a full day to mess around, I might try going back to stock, seeing if it works, and going from there. But, everything I've read suggests the cruise350 is right, and rooting breaks screen mirroring. It definitely worked for me just before Christmas when I did a slideshow for some family of recent pix of our kids. I was on stock rooted 4.2.2 at the time. If you're able to revert back to MF9 (the last version of 4.2.2 released for Sprint) modem and ROM, it might be worth trying if you really want screen mirroring to work. But, what I've read tells me that I shouldn't have been able to do it on 4.2.2 either, so you might find that it doesn't work. If I come up with anything interesting with 4.3, I'll post here.
Yea, I I read that it bricks the phone if you try to go back to 4.2.2. I guess well just have to wait for someone to come up with a new 4.3 that fixes this issue. If I find anything ill let you know.
My question has been answered. I was going nuts trying to figure out why it wouldn't work after root
In case anyone missed it, this thread provides a solution to the issue:
http://forum.xda-developers.com/showthread.php?t=2672307
Screen Mirror fixed!!
Thanks to a few guys in the 2014 threads I have finally found a fix for screen mirroring. It is simple and easy to do. simply boot into download mode, hook up to odin and reflash the stock recovery and your done! Using my screen beam pro while posting this right now. If you need the stock recovery it can be found here
B3 for wifi
http://forum.xda-developers.com/showthread.php?p=50492301
It should be Known I've only tested on the p900
Sent from my SM-P900 using XDA Premium HD app
Duly.noted said:
Screen Mirror fixed!!
Thanks to a few guys in the 2014 threads I have finally found a fix for screen mirroring. It is simple and easy to do. simply boot into download mode, hook up to odin and reflash the stock recovery and your done! Using my screen beam pro while posting this right now. If you need the stock recovery it can be found here
B3 for wifi
http://forum.xda-developers.com/showthread.php?p=50492301
It should be Known I've only tested on the p900
Sent from my SM-P900 using XDA Premium HD app
Click to expand...
Click to collapse
Do you know if Screen Mirroring works with WiDi devices? I have a stock, unrooted SM-P900 and have not been able to get it to connect to the WiDi device on my TV.
Originally my S4 worked but now even it will not connect. Since I don't use this very often i am unsure of when it quit. Probably linked to one of the updates.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
REHolt218 said:
Do you know if Screen Mirroring works with WiDi devices? I have a stock, unrooted SM-P900 and have not been able to get it to connect to the WiDi device on my TV.
Originally my S4 worked but now even it will not connect. Since I don't use this very often i am unsure of when it quit. Probably linked to one of the updates.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Unfortunately I do not. I use a Miracast device
Duly.noted said:
Screen Mirror fixed!!
Thanks to a few guys in the 2014 threads I have finally found a fix for screen mirroring. It is simple and easy to do. simply boot into download mode, hook up to odin and reflash the stock recovery and your done! Using my screen beam pro while posting this right now. If you need the stock recovery it can be found here
B3 for wifi
http://forum.xda-developers.com/showthread.php?p=50492301
It should be Known I've only tested on the p900
Sent from my SM-P900 using XDA Premium HD app
Click to expand...
Click to collapse
Nice! Honestly haven't missed this feature much but glad we have fix now!
rkirmeier said:
Nice! Honestly haven't missed this feature much but glad we have fix now!
Click to expand...
Click to collapse
I do a lot of traveling and this is a great solution for watching movies, when it works. My WiDi device is fairly small and connects to the TV with HDMI. Since WiDi is a direct connect between divices and doesn't depend on the local wifi it works much better than Google ChromeCast.
I just wish I could get it to work again with my Samsung devices.
Sent from my SM-P900 using Tapatalk
Duly.noted said:
Screen Mirror fixed!!
Thanks to a few guys in the 2014 threads I have finally found a fix for screen mirroring. It is simple and easy to do. simply boot into download mode, hook up to odin and reflash the stock recovery and your done! Using my screen beam pro while posting this right now. If you need the stock recovery it can be found here
B3 for wifi
http://forum.xda-developers.com/showthread.php?p=50492301
It should be Known I've only tested on the p900
Sent from my SM-P900 using XDA Premium HD app
Click to expand...
Click to collapse
Wow so this is great news. One question is what effect if any will this have with root.
tonyz3 said:
Wow so this is great news. One question is what effect if any will this have with root.
Click to expand...
Click to collapse
root is unaffected. However you cannot have custom recovery
Sent from my SM-P900 using XDA Premium HD app
Duly.noted said:
root is unaffected. However you cannot have custom recovery
Sent from my SM-P900 using XDA Premium HD app
Click to expand...
Click to collapse
Flashed the stock recovery and miracast is working again. So this means we can't load up TWRP?
That is correct. If we can get support for mobile odin then it might be possible to quick swap between the two on the go. As it is I would reccomend making a backup in twrp then reflashing stock recovery. Then if you need to restore just plug up to odin and flash twrp again. They did mention that whatever it was should be fixable to work with twrp. So if they get a fix it should be easy to port over to ours.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Duly.noted said:
Screen Mirror fixed!!
Thanks to a few guys in the 2014 threads I have finally found a fix for screen mirroring. It is simple and easy to do. simply boot into download mode, hook up to odin and reflash the stock recovery and your done! Using my screen beam pro while posting this right now. If you need the stock recovery it can be found here
B3 for wifi
http://forum.xda-developers.com/showthread.php?p=50492301
It should be Known I've only tested on the p900
Sent from my SM-P900 using XDA Premium HD app
Click to expand...
Click to collapse
This is great news. I held off of rooting because I use screen mirroring every week. Now I have some question, what will happen to my installed apps if I root now? Will i have to re install all of my apps?
ceomayl said:
This is great news. I held off of rooting because I use screen mirroring every week. Now I have some question, what will happen to my installed apps if I root now? Will i have to re install all of my apps?
Click to expand...
Click to collapse
Root will not affect anything You already have installed
Sent from my SCH-I605 using XDA Premium 4 mobile app
Thx for the fix post. I am going to do it this weekend when i have sometime encase of an unforeseen issues.... But just so i am clear. I am rooted already and when i flash this will anything be lost-such as settings or any of the Xposed modules etc. If so, any suggestions on a backup method...
We had similiar story on Note 10.1 2012 (N80xx).
No AllShare Cast (old name sammy was using for today's Screen Mirroring...) when custom recovery OR KERNEL (there isn't any yet on NP12s but surely - when it arrives - it will fed up all the users of mirroring... kernel OR mirroring...). Well, getting into technical details, coz I think here we'll hava similiar history:
- tablet - to work with Mirroring - had needed a flash counter reset to zero (using Triangle Away - did u try this one out? I borrowed my dongle to a friend so for a while can't test it...). The reason is that sammy's forced the software to require HDCP to every content possible, even my own screen... - and using HDCP was available only with use of Trusted Zone (mysterious tz.bin partition in sammy's devices...). When flash counter was zero, device had an access to tz and all was working. But...
- standard bootloader was very unkind for modders - if detected custom kernel OR custom recovery, it automatically triggered the counter every boot, so there was no way to effectively reset the counter with custom recovery or kernel. There was some ideas of avoiding this limitation like creating shortcuts to scripts that were flashing kernels and recoveries on the fly, etc, but it still required to reset the counter with Triangle Away (which was and still is performed NOT on-the-fly on the stock kernel, but requires flashing chainfire's custom "kernel + something" and rebooting into the custom boot screen with big danger sign and asterisk etc etc - takes time and sounds dangerous...)
- finally someone found out that flashing the oldest bootloader possible (dunno if it wasn't even a ICS one?) is a brilliant fix for this situation - this bootloader didn't have flash counter auto-trigger mechanism when non-stock recovery or kernel. I use it since today in that device - that is why I do worry flashing last-week kitkat leak, which requires new bootloader... anyway...
- ...Note Pros won't have ICS bootloaders, of course, BUT there was another fix floating around for other devices like s3 and note 2 (never been ported to N80xx, tho..) - a modded libWFD.so library in /system/lib to force turning off HDCP once and for all. It started from Android 4.2+, required disassembling the lib and messing with some assembly code at first (!), however, after difficult beginnings, further mods for different systems and roms were possible more easily, by editing similiar hex patterns in similiar way in the library binary content (and it was not extremely tiring as it required ediiting only three bytes IN TOTAL!).
Hope the last solution will be brought to our devices in the nearest future as it solves the problem in an ultimate way (eh... at least until there comes an update with major changes, causing lib not to work...).
This was a pain, until someone figured out that
esgie said:
We had similiar story on Note 10.1 2012 (N80xx).
No AllShare Cast (old name sammy was using for today's Screen Mirroring...) when custom recovery OR KERNEL (there isn't any yet on NP12s but surely - when it arrives - it will fed up all the users of mirroring... kernel OR mirroring...). Well, getting into technical details, coz I think here we'll hava similiar history:
- tablet - to work with Mirroring - had needed a flash counter reset to zero (using Triangle Away - did u try this one out? I borrowed my dongle to a friend so for a while can't test it...). The reason is that sammy's forced the software to require HDCP to every content possible, even my own screen... - and using HDCP was available only with use of Trusted Zone (mysterious tz.bin partition in sammy's devices...). When flash counter was zero, device had an access to tz and all was working. But...
- standard bootloader was very unkind for modders - if detected custom kernel OR custom recovery, it automatically triggered the counter every boot, so there was no way to effectively reset the counter with custom recovery or kernel. There was some ideas of avoiding this limitation like creating shortcuts to scripts that were flashing kernels and recoveries on the fly, etc, but it still required to reset the counter with Triangle Away (which was and still is performed NOT on-the-fly on the stock kernel, but requires flashing chainfire's custom "kernel + something" and rebooting into the custom boot screen with big danger sign and asterisk etc etc - takes time and sounds dangerous...)
- finally someone found out that flashing the oldest bootloader possible (dunno if it wasn't even a ICS one?) is a brilliant fix for this situation - this bootloader didn't have flash counter auto-trigger mechanism when non-stock recovery or kernel. I use it since today in that device - that is why I do worry flashing last-week kitkat leak, which requires new bootloader... anyway...
- ...Note Pros won't have ICS bootloaders, of course, BUT there was another fix floating around for other devices like s3 and note 2 (never been ported to N80xx, tho..) - a modded libWFD.so library in /system/lib to force turning off HDCP once and for all. It started from Android 4.2+, required disassembling the lib and messing with some assembly code at first (!), however, after difficult beginnings, further mods for different systems and roms were possible more easily, by editing similiar hex patterns in similiar way in the library binary content (and it was not extremely tiring as it required ediiting only three bytes IN TOTAL!).
Hope the last solution will be brought to our devices in the nearest future as it solves the problem in an ultimate way (eh... at least until there comes an update with major changes, causing lib not to work...).
This was a pain, until someone figured out that
Click to expand...
Click to collapse
Sadly our device does not have the wfdengine.lib. None of the kitkat devices appear to. I do know from reading on the 2014 Forum that hdcp was the Culprit. Hopefully work can be done to twrp to allow its use without breaking this feature
Sent from my SCH-I605 using XDA Premium 4 mobile app
Duly.noted said:
Screen Mirror fixed!!
Thanks to a few guys in the 2014 threads I have finally found a fix for screen mirroring. It is simple and easy to do. simply boot into download mode, hook up to odin and reflash the stock recovery and your done! Using my screen beam pro while posting this right now. If you need the stock recovery it can be found here
B3 for wifi
http://forum.xda-developers.com/showthread.php?p=50492301
It should be Known I've only tested on the p900
Sent from my SM-P900 using XDA Premium HD app
Click to expand...
Click to collapse
Please advise, I will have to convert the recovery.img file to a recovery.tar.md5 file in order to flash using odin, correct?
I am about to buy a Miracast receiver (probably a Netgear PTV3000) but both my Note II and Note Pro 12.2 are rooted.
I run stock Touchwiz ROMs with stock recoveries, so will Miracast work?
This thread has confused me a bit because I thought that even though you have root, as long as you are running a stock ROM and the stock recovery you would be able to use Miracast.
BTW I have seen mentioned elsewhere that with Samsung Allshare Cast you ALSO have to have "Flash Binary" at zero (which at the moment I have on the Note II thanks to Triangle Away but I haven't on the Note Pro since AFAIK I can't run Triangle Away on it nor I will be able to use Triangle Away on my Note II once I update it to 4.3 or KitKat) and that's why I am going with the Netgear or with the Asus dongle.
Anybody can shed some (definitive) light on these issues..? TNX
xdapao3 said:
I am about to buy a Miracast receiver (probably a Netgear PTV3000) but both my Note II and Note Pro 12.2 are rooted.
I run stock Touchwiz ROMs with stock recoveries, so will Miracast work?
This thread has confused me a bit because I thought that even though you have root, as long as you are running a stock ROM and the stock recovery you would be able to use Miracast.
BTW I have seen mentioned elsewhere that with Samsung Allshare Cast you ALSO have to have "Flash Binary" at zero (which at the moment I have on the Note II thanks to Triangle Away but I haven't on the Note Pro since AFAIK I can't run Triangle Away on it nor I will be able to use Triangle Away on my Note II once I update it to 4.3 or KitKat) and that's why I am going with the Netgear or with the Asus dongle.
Anybody can shed some (definitive) light on these issues..? TNX
Click to expand...
Click to collapse
I have written it two posts above.
As far as I can see at the moment, TA works fine with Note Pro 12.2 (at least on a Qualcomm one...).
EDIT:
Here's libwfds.so for Note Pro 12.2 LTE P905, modified by me (based on XXUANC3 stock firmware, can't guarantee it will work on any other firmware than this one..), it seems to work with custom recovery (repacked, not-yet-fully-working TWRP).
Just put it in /system/vendor/lib and replace previous one (also, make sure permissions are 644, root:root).
http://www28.zippyshare.com/v/17510448/file.html
IT WILL PROBABLY NOT WORK ON EXYNOS DEVICES (P900 etc).
esgie said:
I have written it two posts above.
As far as I can see at the moment, TA works fine with Note Pro 12.2 (at least on a Qualcomm one...).
EDIT:
Here's libwfds.so for Note Pro 12.2 LTE P905, modified by me (based on XXUANC3 stock firmware, can't guarantee it will work on any other firmware than this one..), it seems to work with custom recovery (repacked, not-yet-fully-working TWRP).
Just put it in /system/vendor/lib and replace previous one (also, make sure permissions are 644, root:root).
http://www28.zippyshare.com/v/17510448/file.html
IT WILL PROBABLY NOT WORK ON EXYNOS DEVICES (P900 etc).
Click to expand...
Click to collapse
:highfive:
I can confirm that this in fact DOES work...not only only that but it SHOULD be good to go for ANY device with a snapdragon 800 running 4.4.2. I'm actually using it on the LTE variant of the tab pro 8.4 and everything is ok...i tested it for a full 2 hours the other night with TWRP installed & didnt have any problems besides an occassional hiccup when trying to connect. For anybody reading this...i'm not sure if the order is important but i replaced the above file BEFORE i flashed the custom recovery although that shouldnt matter. Also...u MAY need to wipe both caches after u install
THEDEVIOUS1 said:
:highfive:
I can confirm that this in fact DOES work...not only only that but it SHOULD be good to go for ANY device with a snapdragon 800 running 4.4.2. I'm actually using it on the LTE variant of the tab pro 8.4 and everything is ok...i tested it for a full 2 hours the other night with TWRP installed & didnt have any problems besides an occassional hiccup when trying to connect. For anybody reading this...i'm not sure if the order is important but i replaced the above file BEFORE i flashed the custom recovery although that shouldnt matter. Also...u MAY need to wipe both caches after u install
Click to expand...
Click to collapse
Nice to know
Btw I replaced it after flashing TWRP, so it should work both ways.
Feel free to post it in the other devices' forums if you find it helpful.
esgie said:
Here's libwfds.so modified by me (based on XXUANC3 stock firmware, can't guarantee it will work on any other firmware than this one..),
Click to expand...
Click to collapse
Really thanks for being so helpful man, but there lies the problem, I can't get a Miracast setup and be at the constant risk that an update breaks it..
Hi, I'm trying to get the native Hotspot working, but there's something weird going on. I'm able to turn it on without getting the sprint message, but my laptop doesn't seem to be able to connect to it. My laptop can see the wifi connection and everything but when trying to connect it just fails.
I flashed the correct odex Nae file. Also I'm on 4.4.2 rooted. Done this many times b4 with prior versions.
I used TWRP to install. I also tried the manual by adding to the framework. I have the menus setting Hotspot.
Any help would be greatly appreciated.
My phone is a Sprint Galaxy S4
Which s4 do you have?
Sent from my SPH-L720T using XDA Free mobile app
SPHL720
Junkyardjames87 said:
Which s4 do you have?
Sent from my SPH-L720T using XDA Free mobile app
Click to expand...
Click to collapse
I have the SPHL720
its on stock NAE and is rooted.
Currently I have TWRP installed and loaded with that.
I have the menu item it turns it on.
Nothing can connect. But I can see it from tablets and PC's
I noticed last night at some point that I lost Wi-Fi functionality on my S4. All other devices on my home network are working without incidence. Any ideas?
Sent from my Samsung Galaxy S4 (SGH-I337) using Tapatalk Pro
I'm having the same problem. My wifi is now working whenever it wants. I didn't have any issues either until yesterday. I was running the GPE 4.4.4 rom by joe-tech and was getting annoyed by the 5.0 update notification. So I got autostarts and disabled the 3 services that check that. After a while, I noticed my wifi stopped working. After countless reboots and hot reboots, the wifi just works sporadically even after re-enabling the 3 services I turned off for the 5.0 update. I wiped cache/dalvik thinking that might fix it too and nope. I wiped the phone completely and installed the latest GoldenEye rom (v48) hoping that would fix it. Nope.
I can be on wireless and it'll just shut off by itself. I'll turn it back on and it turns temperamental.
Please help us
I had this issue too.
randun said:
I noticed last night at some point that I lost Wi-Fi functionality on my S4. All other devices on my home network are working without incidence. Any ideas?
Sent from my Samsung Galaxy S4 (SGH-I337) using Tapatalk Pro
Click to expand...
Click to collapse
I had rooted my fiance's Galaxy S4 and when she wanted it back to unrooted and stock, I put it back. However, it appears that the common recovery that is available online is available with a kernel that is either corrupt, or just plain wrong. Her WiFi would not turn on despite everything. After much searching and attempts at removing the battery, factory restore and whatnot, finally decided to research the flash file itself and sure enough, it would not update past 4.2.2.
The file you will need to reflash via ODIN v1.85 is available here: http://www.androidayos.com/samsung-galaxy-s4-odin-stock-firmware/
Found the proper file (Telus), flashed it and it is now at 4.4.2 and WiFi is working perfect again. Also fast as well. Hope this helps as I know I found it extremely difficult to find answers!
I should have posted by now. My Wi-Fi returned. Weird...
Sent from my Samsung Galaxy S4 (SGH-I337) using Tapatalk Pro