Hey guys. I recently purchased a Gear VR for my S6 which is running a stock version of 6.0.1 but its not running any setup services when plugged into the headset. It doesn't seem to recognize it since I had the charger plugged into the headset and the phone connected to the headset but didn't charge. Any ideas on what the problem might be? I tried searching online for the apks and installing them manually but cant seem to find all of them either and the ones that I did didn't do much.
Thanks
Try flashing a PG1 TAR file using Odin. Get it from my thread here: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
It is the latest update available. Test your Gear before rooting or installing TWRP.
Related
After browsing the internet all day yesterday I never did see an actual fix for this issue for this specific model. I did see a lot of random ones for different carriers which would probably work. But not for Sprint specifically.
Problem? My Sprint Galaxy Tab 3 7" failed at 27% whenever I attempted to update it.
Issue: The Tab was Rooted by my brother - who then Un-Rooted and returned it back to Factory before giving it to me. Then failed to mention he had rooted the thing to begin with.
Fix: Re-Flash using Odin and stock 4.2 image.
So I tried getting Kies installed and working. Tab would NEVER connect no matter what I did. I tried installing the USB drivers again (though the computer recognized the damn thing), reinstalling Kies, trying to put Kies into Compatibility mode (since I'm on Windows 8.1)
After ALL that I finally called my brother who gave it to me as a gift. Found out the thing may or may not have been Rooted. But he thought he had reverted it back to stock and un-rooted it.
So back to searching on the internet. Finally found this article: http://theunlockr.com/2014/03/21/unroot-samsung-galaxy-tab-3-7-0-sprint/ which suggested I try re-flashing using Odin to get rid of Root on the device.
I followed the steps in the article (Tip: Do a search on Google for the correct image zip for your model tablet and download it from androidhostfiles) Example for my specific model T217SVPUANB8: http://www.androidfilehost.com/?fid=23329332407579787
Was able to restore it back to "true stock" and was able to update to KitKat. Kies started working finally. And all was well with the world again.
Oh, and I uninstalled Kies immediately after I was done with that POS software. :silly:
Hopefully this will help the I dunno the two other people that still have one of these that they received for free from Sprint.
A little while ago, I rooted my S4 Mini and installed Android 5 custom firmware. However, my online banking app didn't like root, so I reverted back to standard firmware and removed the root. The phone works fine.
However, when running the OTA update, the phone tells me it cannot update due to root, and I should try using Kies.
I've installed Kies on my PC; plugging the phone in Kies tells me there is an update. It appears to download the required file but the phone does not update. I have tried with SmartSwitch also, but the same happens.
Can anyone please advise me on the following:
What is the latest official update for the S4 Mini; is it Android 5?
How can I update the phone? I thought flashing with Odin, but googling for various permutations of 'S4 Mini Official ROM, S4 Mini Android 5' etc. tends to yield results for the S4 and not the Mini...
Any help here would be great!
There is no official Android 5 lollipop for our S4 Mini. Best place to look is http://www.sammobile.com/firmwares/ should have all available firmwares for your model of S4 Mini. Flash the corresponding model of your S4 Mini and country code to your device and do this a couple of times over to fully restore your stock OS. I find without using an xposed module like rootcloak which doesn't always work that's stock is usually the only option to run apps that don't like root. I have the same issue with an app called channel 4 on demand which will only run on stock OS.
Hiii guys. I just got a samsung a7 2017 with updated 7.0 version and as I'm a guy who wants to get into the field of android development I rooted my device and right after that my camera stopped working and when I connect my device to my pc, my device is not shown in my pc. So I searched a lot about that and found that it might also happen because of errors in framework. So was rooting my device a problem. If not please suggest a way to get my device work normal again.
Everytime i reboot s4 all bluetooth devices unpair... any suggestions?
Same issue Here
it was working fine before I rooted it. Problems only occurred after a flashback to stock rom obtained from Sammobile.com
I just posted this in another thread. This is a known issue once rooted, however easily fixed. There is a module that you need to load via Magisk. Search for: "libsecure_storage companion for rooted Samsung devices". Load that up and you'll be good to go.
I have an old Samsung Galaxy Pro 8.4 Tablet (the model is SM-T320 and called mondrianwifi) that I'm trying to breath life into. I rooted it with ODIN + CF AutoRoot and then installed TWRP. I was able to successfully install Lineage OS several times, but I never got the sound to work.
First I tried Lineage 17.0-20191204-UNOFFICIAL-mondrianwifi (Android 11) with the corresponding GAPPS for Android. I had no sound in the Samsung media player, when playing VLC, etc.
So I wiped it clean and tried Lineage lineage-13.0-20180121-nightly-mondrianwifi (Android 6) with the corresponding "gapps-arm-6.0-pico-20220215" ... I booted it up and all programs seem to run fine...except it also doesn't play any sound.
Both versions are supposed to be supported and compatible according to forums at xda-developers.com and the website I got it off of.
I then tried ColtOS v6.5Euphoria-mondrianwifi-20201109-Official - and that also installs with programs running but the speaker sound doesn't exist.
The only way to get sound is to plug a headphone into the 3.5mm jack or use a bluetooth speaker.
Googling lineageosroms.com shows the Galaxy Tab Pro 8.4 (SM-T320) is called Mondrianwifi, so the Roms I downloaded that have Mondrianwifi in their names should be correct. https://lineageosroms.com/mondrianwifi/#start-the-build
Any help would be appreciated.
@Intranetusa
The chosen ROMs are correct for your device.
To exclude the possibilty of a hardware problem I think it might be helpful to return to stock via Odin, test speakers and start all over again.
Btw. CF-Autoroot is afaik only necessary if you want a rooted stock ROM.
When planning to flash a custom ROM anyway there's no need for that.