Not sure what happened. I unrooted and tried installing up and it failed. So I wiped everything tried again and it aborted again. So I rooted again while installing all of my apps I noticed that I all of sudden had the Samsung Remote Control options in my security menu and they work.
I have no clue how it happened.
I have the Spring GS3
shaun0207 said:
Not sure what happened. I unrooted and tried installing up and it failed. So I wiped everything tried again and it aborted again. So I rooted again while installing all of my apps I noticed that I all of sudden had the Samsung Remote Control options in my security menu and they work.
I have no clue how it happened.
I have the Spring GS3
Click to expand...
Click to collapse
What does this actually do?
It will let you use Samsung Dive
It's Samsung Dive. Like Seek Droid.
I'd love to know what you did to get it working on sprints phone.. I got the menu to appear via modifying the /system/csc/feature.xml file, but it doesn't actually work for some reason for me.
I'm currently using Blazer 1.6 ROM btw on Sprint's S3. (I last tried with 1.4 version of the ROM, perhaps I should try again )
Related
I just recently rooted my i747 using the No Trip Counter method using ODIN and the stock ROM with root injected into it already. I had a fair amount of stuff frozen with TiBu but nothing on the "unsafe" list. I made sure screen rotation was on, tried to calibrate via the motion settings (little blue dot didn't move at all), even tried battery pulling, reflashing the ROM, wiping the cache, clearing the cache for System UI and Touchwiz. I don't have a custom recovery flashed. I flashed the unrooted stock ROM and called up AT&T. I've got a new device that auto rotate works now but a bit hesitant to re-root. Has anyone heard of this feature being disabled due to something done during/after root? I've Googled my butt off but couldn't find any issues related to rooting.
Note: I got jumped over the weekend and my phone was swiped. It was later returned to an AT&T store but who knows what it went through. That's my guess as far as why it didn't work anymore (probably thrown/dropped/who knows what) but I just wanted to see if there was a possible software issue that I may not have been able to find.
Cheers!
Hey guys. As the title suggests, I can't boot my Note 2 (sgh-i317). It is stuck on the AT&T logo and while it's stuck there it vibrates slightly every 5-6 seconds. I tried changing my screen density to 240 and it worked for a bit but annoed me. then I went to change it back and got this problem. I accidentally set it to 360 I think though, instead of 320. I have wiped the cache. I have wiped the data. I have installed roms countless times already with Odin. I'd imagine my reset counter is at over 10 just from today.
I've been searching on google and these forums for hours and have seen many suggestions, but none of them have worked. The farthest I have gotten was to get the phone to boot, but once I start going through all the setup stuff I begin getting error popups saying that Touchwiz home has stopped responding. As soon as I push OK the error immediately pops up again. I seriously can not do anything with my phone.
Is there any way to get a stock build.prop file somewhere for this phone, and if so, how would I install it if I can't even boot into the device?
Any help would greatly be appreciated. I have no idea where else to turn here. Thanks!
-Mark
Do you have a backup to restore from recovery ??
If not....then power down the device and remove the SD card and place it into a PC card adapter...
Then download or copy over a suitable rom...
Then place the SD into the phone and boot into recovery...
Fully wipe the device and flash the rom of choice...
Reboot....set....profit....g
Edit:
Are you certain that your power button is not stuck ?
If the method I suggested fails... and rebooting occurs with vibration...then your power button is suspect....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Thanks. Well I got it to boot finally, however there's been a couple issues since. It's on 4.1.2 right now...
1. Whenever I try to officially update to 4.3 through the settings, it downloads, then when installing it ALWAYS fails at 25%.
2. This is a big issue. My data connectivity is gone. I have no 4g access period. If I'm not using a wifi network, I can't do anything online, period. I've reflashed numerous times, and can't get it to recognize the network. I can make calls just fine, just no data.
I've tried wiping data and going to factory reset, but this doesn't help in any way whatsoever. I've popped out the battery and sim card and reinserted after a few minutes, still to no avail.
The funny thing also, last night my friend, who has the same phone, updated to 4.3 and got the EXACT issues I've been dealing with. The ONLY thing in common is that we have both rooted our phones in the past. When I first got 4.3 it worked fine. It wasn't until I rooted that these issues began. My friend's phone was not rooted, however it had been in the past. I'm thinking that this 4.3 update has an issue with phones that are rooted or have been at some time. I don't know how it can tell, but that's all I can think of. his phone now is also a doorstop, like mine.
K, fixed data connectivity from another thread here. For some reason, even if I wipe my system, it seems to still keep settings intact. In this case, nothing set in APN. Seems the more I try to fix my phone, the more problems show up.
If you updated to official 4.3...then yes ...a whole new host of problems are yours until the devs figure out the locked bootloader and it's knox flag...
Backups won't restore....and so forth...
Read around ....you'll see...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Wow it has been a long 24 hours. I want to go ahead and appoligize,...I have a really bad memory. Sunday I went from Task650 AOKP (Android 4.3) to Validus 4.1 (Android 4.4.2) . I cleaned everything before flashing and then installed the supersu and gapps as stated in the op. Yesterday I found out I had a wifi problem, not sure if I was able to connect before or not. from this point until I try back to stock i get a popup stating that media has stopped or media storage has stopped and it happens progressively more often as time goes on. I tried dirty flash and it didnt work so i thought i would try a new kernel. I had never tried flashing kernels before but i read up on it and seemed very simple. so I flashed Ktoonsez KT747 kernel, i also flashed EMJB modem to see if there was a difference. afterward when i looked in settings - about phone under kernel version it said (not exactly but best i can remember) 3.4.77-cyanogenmod .... dirty KT747. i couldnt find anything about this but i didnt think this was good. i dont remember if i tried reflashing or doing anything to fix it right then or not. but at some point late yesterday after a reboot my lockscreen was transparent (might have been before), background was black, status bar was gone, when i recieved a call there was no popup it would just ring but i could go in to phone and it said return to current call but i couldnt do anything to answer. I could call backthough. i did still have notification on the lockscreen. xposed fimware was also disabled so i figured that ruled out any issued from it. I was getting aggrivated. i read up a little more. read suggestions to flash back to stock periodically. I figured i should try that. BIG MISTAKE!!! I still dont know why it didnt work but i tried plenty! before flashing the EMJB modem I had DLK3. so i thought that meant i would be ok to return to stock because i never upgraded my bootloader. when i flashed it with odin it went all the way through and restarted the phone but got stuck on samsung logo after at&t splash screen. so i odin flashed cwm booted into recovery and restored a nandroid backup (life saver!!). this worked and i was back on AOKP with DLK3 modem but not satisfied and feeling a little safe to explore knowing that i had a safe return plan unless something went detrimentally wrong. so with my modem saying DLK3 and my rom on 4.3 instead of 4.4 i decided to try back to stock again and use the true stock instead of rooted stock. (WORSE MISTAKE!!) ODIN failed. my heart dropped i was terrified. I decided to download and try KIES but it wouldnt connect to the phone after downloading the firmware. I tried odin flashing root stock again and if finished and stuck on samsung again. so i flashed cwm and sideloaded Validus to get back to 4.4.2. seems to be working good but now to get to the issue. ater i got it back working i got a notification that sdcard was removed unexpectedly. before anyone directs me to one of the hundred threads with this title my issue is with internal storage not the external sd card. i have seached it quite a bit but i cant find anything like my situation. it seems that if i go to /storage/sdcard0 it is empty but i can access it from any of the following locations and its not empty.
/storage/emulated/0
/storage/emulated/legacy
/sdcard
/mnt/sdcard
I do not understand this.
Anyone that has any helpful information thank you in advance.
update : it happened again today. my phone died during the night and when I turned it on just now it popped up the notification SD card removed unexpectedly except it popped up and went away really fast like 10 times. still the only thing missing is storage/sdcard0
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Greetings, I wonder if somebody can solve the following problem. I'm from Venezuela and I bought this model GT-I9192 in December 2013 when the update came out this year it was updated from 4.2.2 (JellyBean) to 4.4.2 (KitKat). I almost never use the camera of this phone and then I noticed that every time I opened the camera app I would get "Warning: Camera Failed". Thinking it was the update I proceeded to install the Cyanogenmod rom 11 for this model, but continued with the same problem. The flash works every time I turn the flashlight application. I took it to a technician telling me that the problem was not hardware but software. This is where my troubles began. I do not remember which firmware was installed. I tried to install several firmwares 4.2.2. but without success all with flashing failures. However, I could install version 4.4.2 of Trinidad and Tobago but with the same camera error. Hopefully someone can help me with this problem. I would like to know exactly what firmware should download to install? Thank you very much.
nelson2006 said:
Greetings, I wonder if somebody can solve the following problem. I'm from Venezuela and I bought this model GT-I9192 in December 2013 when the update came out this year it was updated from 4.2.2 (JellyBean) to 4.4.2 (KitKat). I almost never use the camera of this phone and then I noticed that every time I opened the camera app I would get "Warning: Camera Failed". Thinking it was the update I proceeded to install the Cyanogenmod rom 11 for this model, but continued with the same problem. The flash works every time I turn the flashlight application. I took it to a technician telling me that the problem was not hardware but software. This is where my troubles began. I do not remember which firmware was installed. I tried to install several firmwares 4.2.2. but without success all with flashing failures. However, I could install version 4.4.2 of Trinidad and Tobago but with the same camera error. Hopefully someone can help me with this problem. I would like to know exactly what firmware should download to install? Thank you very much.
Click to expand...
Click to collapse
I registered here just to answer your question.
My Android expertise is very limited but I try to learn from past experience. If I understand correctly, your want:
1. the camera should work.
2. the phone should function properly.
If you do not remember your original firmware, do not worry as it does not matter. Once your upgraded to KK, Knox (google it) kicked in to prevent you from downgrading to JB. That's why all flashing efforts to downgrade failed. So, you can keep your phone with KK if the phone works except camera. In case you want to downgrade to JB, I am sure that able XDA members can help you with that. I am unaware if such methods exist.
Now, to see if the camera works there are several methods. I encountered the same problem with my wives i727 Skyrocket which has JB 4.1.2 installed. One day the camera suddenly failed with the error "Warning: Camera Failed". The flash-light worked flawlessly so I was a bit perplexed. I researched and found several remedies:
1. From application manager, clear cache/data of the camera app and restart phone - Tried this several times, did not work.
2. Perform factory reset- Thought I'd use it as a last resort as the phone had gigs of data in it.
3. Uninstall apps (last installed app uninstalled first and so on) - I uninstalled the last installed app and restarted the phone. Voila! The camera was back. I have no explanations why but it just worked.
Let us know how it goes, good luck!
On the i9195, it is possible and easy to downgrade to JB since there's a 4.2.2 firmware which is similar to the 4.4.2 firmwares, but I don't know about the i9192.
Be careful with this;
If you know what you are doing, get the CWM recovery, format system/data and flash a 4.4.2 firmware again. If that didn't fix it, I suspect that it's a hardware problem and it's having problems with the software, but there should be something wrong with the hardware, for sure.
Good Luck.
snipar said:
I registered here just to answer your question.
My Android expertise is very limited but I try to learn from past experience. If I understand correctly, your want:
1. the camera should work.
2. the phone should function properly.
If you do not remember your original firmware, do not worry as it does not matter. Once your upgraded to KK, Knox (google it) kicked in to prevent you from downgrading to JB. That's why all flashing efforts to downgrade failed. So, you can keep your phone with KK if the phone works except camera. In case you want to downgrade to JB, I am sure that able XDA members can help you with that. I am unaware if such methods exist.
Now, to see if the camera works there are several methods. I encountered the same problem with my wives i727 Skyrocket which has JB 4.1.2 installed. One day the camera suddenly failed with the error "Warning: Camera Failed". The flash-light worked flawlessly so I was a bit perplexed. I researched and found several remedies:
1. From application manager, clear cache/data of the camera app and restart phone - Tried this several times, did not work.
2. Perform factory reset- Thought I'd use it as a last resort as the phone had gigs of data in it.
3. Uninstall apps (last installed app uninstalled first and so on) - I uninstalled the last installed app and restarted the phone. Voila! The camera was back. I have no explanations why but it just worked.
Let us know how it goes, good luck!
Click to expand...
Click to collapse
I haved tried the first two steps and no luck at all. Maybe this weekend I'll try the third one. Thank you for the reply.
snipar said:
I registered here just to answer your question.
My Android expertise is very limited but I try to learn from past experience. If I understand correctly, your want:
1. the camera should work.
2. the phone should function properly.
If you do not remember your original firmware, do not worry as it does not matter. Once your upgraded to KK, Knox (google it) kicked in to prevent you from downgrading to JB. That's why all flashing efforts to downgrade failed. So, you can keep your phone with KK if the phone works except camera. In case you want to downgrade to JB, I am sure that able XDA members can help you with that. I am unaware if such methods exist.
Now, to see if the camera works there are several methods. I encountered the same problem with my wives i727 Skyrocket which has JB 4.1.2 installed. One day the camera suddenly failed with the error "Warning: Camera Failed". The flash-light worked flawlessly so I was a bit perplexed. I researched and found several remedies:
1. From application manager, clear cache/data of the camera app and restart phone - Tried this several times, did not work.
2. Perform factory reset- Thought I'd use it as a last resort as the phone had gigs of data in it.
3. Uninstall apps (last installed app uninstalled first and so on) - I uninstalled the last installed app and restarted the phone. Voila! The camera was back. I have no explanations why but it just worked.
Let us know how it goes, good luck!
Click to expand...
Click to collapse
RoyaLKurTx3 said:
On the i9195, it is possible and easy to downgrade to JB since there's a 4.2.2 firmware which is similar to the 4.4.2 firmwares, but I don't know about the i9192.
Be careful with this;
If you know what you are doing, get the CWM recovery, format system/data and flash a 4.4.2 firmware again. If that didn't fix it, I suspect that it's a hardware problem and it's having problems with the software, but there should be something wrong with the hardware, for sure.
Good Luck.
Click to expand...
Click to collapse
Tried that too and nothing. I also suspect that the problem is a hardware issue. Thank you for the reply.
nelson2006 said:
Tried that too and nothing. I also suspect that the problem is a hardware issue. Thank you for the reply.
Click to expand...
Click to collapse
The problem, in fact is a fault in the hardware problem. If it's still under warranty, request a new phone.
looking for some suggestions as to what I can to to correct these issues. I have a 210R that I screwed up probably flashed something I should not have... to restore I went to sam mobil and downloaded the latest firmware ( T210RUEU0COB1), installed using Oden and restored the Tab. since I have done this (and yes I redownloaded the firmware and reinstalled to make sure it was a good file and installation) the tab now will boot up fine, but will come up with the error messages Process com.androis.systemui has stopped and often com.sec.android.flashbarservice has stopped as well clicking ok will sometimes let me continue, other times will simply reboot. If it lets me continue whatever app I am using will quickly stop as well and the tab reboots. in addition to this the WiFi barely recieves any signal unless I am almost on top of the router. it is currently stock. Any suggestions or help will be greatly appreciated.
Having the same problems minus wifi issues
jdsatyr said:
looking for some suggestions as to what I can to to correct these issues. I have a 210R that I screwed up probably flashed something I should not have... to restore I went to sam mobil and downloaded the latest firmware ( T210RUEU0COB1), installed using Oden and restored the Tab. since I have done this (and yes I redownloaded the firmware and reinstalled to make sure it was a good file and installation) the tab now will boot up fine, but will come up with the error messages Process com.androis.systemui has stopped and often com.sec.android.flashbarservice has stopped as well clicking ok will sometimes let me continue, other times will simply reboot. If it lets me continue whatever app I am using will quickly stop as well and the tab reboots. in addition to this the WiFi barely recieves any signal unless I am almost on top of the router. it is currently stock. Any suggestions or help will be greatly appreciated.
Click to expand...
Click to collapse
Dude my tablet is in the same state I use. The many reboots. All apps/process stopping for no reason. Funny thing is this started happening to me after I received an OTA update for 4.4.2 and flashed it. So basically the official update released by samsung messed up my phone. Somebody please respond with suggestions/solutions.
Sigh.... guess I'll just use it as a paperweight ..