Ok, I flashed something that wasn't for my sgs2 skyrocket and when I did it nothing happened, then when I rebooted it it seemed ok untill it kept freezing, no sound even on full val. I cant call because I cant here the other person and that it freezes on every app I open it takes like 2mins to open or a force close comes up. Well I have flashed back to stock using odin but still the same problem. I dont know what to do? Any thoughts about fixing this?
Sent from my samsung galaxy s2 skyrocket i727.
If you have flashed back to stock, and are still having the same issues it sounds like there may be a hardware problem. Did you do a full clean flash back to stock? (system wipe, clear the dalvik)
Sent from my SAMSUNG-SGH-I727 using xda premium
Why would you flash something not for the Skyrocket?
Wipe the phone completely, as in all data, the system, caches, and repeat that wipe three times in recovery, then power down. Go into download mode and restore to GB stock (yes, all the way back), then use Kies to do the ICS update and stay stock for a few days to make sure everything works after that.
If it's still not working after that, your hardware is jacked. Restore the thing back to GB, pull the cord out during the ICS update on Kies and finish the job. Hope you're still in warranty; if not, I hear you can get a used Captivate for $60 or so while you learn not to flash stuff for the wrong phone.
in stock recovery wipe caches and do a reset, if still a no go, install cwm, wipe caches and reset x3, reflash stock firmware with odin again, perform a reset, if still a no go then hw malfunction
Well someone's lazy...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
No I just flashed it back. But ima try that right now. Hope it this will work.
CaLLm3LAzY- said:
No I just flashed it back. But ima try that right now. Hope it this will work.
Click to expand...
Click to collapse
You just flashed it back? You're not making any sense. Post a link to the ROM you flashed or we can't help you.
I flashed the stock rom.
Hello there !
I can't toggle on Bluetooth in my GT-P3110 recently.. I'm not on airplane mode.. but WiFi works though...
I even flashed a CM ROM(10.1.3 right now) to see if it works.(may be an silly deed.. I'm just new to these android things)
I have uploaded two videos which shows what really happens when trying to turn on bluetooth...
When I was using the stock rom
After flashing CM
I think that I'm having some hardware failure (i.e. dropping the unit - I never dropped myself.. idk if it happened actually as I share this tablet with my family )
I want to know whether this can be repaired ?.
Is there a seperate accessory inside for Bluetooth which can be replaced ?
Thanks in advance !
Were you on stock firmware when you noticed your bluetooth is not turning on? Was it from the start of your new tablet? Take a look at this thread, someone has the same problem with you and solved it but his problem was caused of inproper flashing http://forum.xda-developers.com/showthread.php?t=2447156
You could also try to reinstall using wipe data/factory reset, wipe cache, wipe dalvik cache from clockwork mod and reinstalling cyanogen again to see if that fixes it.
As your last resort you could flash your tab back to stock recovery and fw (and use TriangleAway to reset your flash counter) and send it to Samsung for repair, especially if it still has warranty.
some other threads with your problem: http://forums.androidcentral.com/go...s/225585-4-2-upgrade-cant-turn-bluetooth.html
katsika said:
Were you on stock firmware when you noticed your bluetooth is not turning on? Was it from the start of your new tablet? Take a look at this thread, someone has the same problem with you and solved it but his problem was caused of inproper flashing http://forum.xda-developers.com/showthread.php?t=2447156
You could also try to reinstall using wipe data/factory reset, wipe cache, wipe dalvik cache from clockwork mod and reinstalling cyanogen again to see if that fixes it.
As your last resort you could flash your tab back to stock recovery and fw (and use TriangleAway to reset your flash counter) and send it to Samsung for repair, especially if it still has warranty.
some other threads with your problem: http://forums.androidcentral.com/go...s/225585-4-2-upgrade-cant-turn-bluetooth.html
Click to expand...
Click to collapse
Thanks for the reply... I noticed the issue when I was on stock stock ROM. I may have to send it to Samsung.
Thanks for the support :highfive:
Is it possible you have another kernel other than stock?
Sent from my XT907 using xda app-developers app
Guys, I'm running Purity room with Franco kernel and PA GAPPS. I've had this problem recently, where my room is running perfectly. But when ever I do a factory reset through CWM 6.0.4.5 and reboot, the error "phone had stopped" pops up and all I can do is long press the power button to reboot into recovery and restore a backup.
Any ideas guys?
Sent from my Nexus 5 using XDA Premium 4 mobile app
I would suggest redownloading purity and Gapps and franco kernel (You just never know). Flash them individually and boot into the phone and see which one is causing you problems; after a factory reset with wiping cache/ dalvik. If this does not work try a different ROM (I always keep a stock rooted/deodexed on my phone), if it still persist I would do a full wipe start over from scratch.
mistahseller said:
I would suggest redownloading purity and Gapps and franco kernel (You just never know). Flash them individually and boot into the phone and see which one is causing you problems; after a factory reset with wiping cache/ dalvik. If this does not work try a different ROM (I always keep a stock rooted/deodexed on my phone), if it still persist I would do a full wipe start over from scratch.
Click to expand...
Click to collapse
Thanks for the reply, however, Ive already done the following:
1- Wipe Data/Factory reset > Reboot: "Phone has stopped" Error
2- Wipe Data/Factory reset > Install Purity (with/without GAPPS) > Reboot: "Phone has stopped" Error
3- Wipe Data/Factory reset > Install Puroty (with/without Franco kernel) > Reboot: "Phone has stopped" Error
4- Wipe Data/Factory reset > Installed other ROM> Reboot: "Phone has stopped" Error
5- Wipe Dialler/SIM toolkit > Wipe Data/Factory reset > Reboot: "Phone has stopped" Error
Cache/Dalvik Cache cleared every time.
The old backup still works, I even dirty flashed the new Purity version over it and works ok. The problem only arises after Wipe Data/Factory Reset.
Couldn't find any other solutions, any other suggestions?
Well I would say that if it works after your backup and then dirtyflashing a newer version of purity then leave it go, this is probably not the best option but if it works.... My other option in my previous post was to completely wipe the phone and start over as in back to stock and start over.
Something could've corrupted, who knows, maybe something went wrong with your installation of a bootloader. You said you are running CWM 6.x.x.x, try flashing the stock bootloader and then reflashing a different bootloader I suggest TWRP but there are other options. I used CWM on my nexus and it did it's purpose but when I flashed TWRP onto my nexus 5 it was just more clean and it had touch, go figure.
I'd try using Titanum Backup and clearing the data of the phone, dialer storage, etc after the reset. Had a similar situation the other day that doing that resolved. Hope that helps. Problems like this can be annoying.
Just thought of this: Could be your recovery. Might not be wiping things correctly. If what I suggested doesn't help, then try TWRP. I've found very few things that TWRP is not better at vs CWM (on officially supported phones).
OK try to install cyanogen mode and let me know what happened
Sent from my Opal 800 using xda app-developers app
mistahseller said:
Well I would say that if it works after your backup and then dirtyflashing a newer version of purity then leave it go, this is probably not the best option but if it works.... My other option in my previous post was to completely wipe the phone and start over as in back to stock and start over.
Something could've corrupted, who knows, maybe something went wrong with your installation of a bootloader. You said you are running CWM 6.x.x.x, try flashing the stock bootloader and then reflashing a different bootloader I suggest TWRP but there are other options. I used CWM on my nexus and it did it's purpose but when I flashed TWRP onto my nexus 5 it was just more clean and it had touch, go figure.
Click to expand...
Click to collapse
Will try resetting and well then install twrp ... let's see. Can't let it be coz I need to be able to test other roms and stuff.
Sent from my Nexus 5 using XDA Premium 4 mobile app
es0tericcha0s said:
I'd try using Titanum Backup and clearing the data of the phone, dialer storage, etc after the reset. Had a similar situation the other day that doing that resolved. Hope that helps. Problems like this can be annoying.
Just thought of this: Could be your recovery. Might not be wiping things correctly. If what I suggested doesn't help, then try TWRP. I've found very few things that TWRP is not better at vs CWM (on officially supported phones).
Click to expand...
Click to collapse
Yeah that would be an easier option to try before resetting... Will try twrp as well.
Sent from my Nexus 5 using XDA Premium 4 mobile app
You can install any ROM it does not have to be cyanogen mod.
why is that the goto for everyone?.....
---------- Post added at 12:18 PM ---------- Previous post was at 12:18 PM ----------
es0tericcha0s said:
I'd try using Titanum Backup and clearing the data of the phone, dialer storage, etc after the reset. Had a similar situation the other day that doing that resolved. Hope that helps. Problems like this can be annoying.
Just thought of this: Could be your recovery. Might not be wiping things correctly. If what I suggested doesn't help, then try TWRP. I've found very few things that TWRP is not better at vs CWM (on officially supported phones).
Click to expand...
Click to collapse
What does TWRP not do that CWM does?
mistahseller said:
You can install any ROM it does not have to be cyanogen mod.
why is that the goto for everyone?.....
---------- Post added at 12:18 PM ---------- Previous post was at 12:18 PM ----------
What does TWRP not do that CWM does?
Click to expand...
Click to collapse
CM is usually the go to to try something else because A) It's usually the most stable of aftermarket Roms due to the larger community and user support B) been around the longest / out for the most phones so is more well known C) it's different than AOSP so if you have issues with AOSP AND CM then you know something is really going on. That being said, CM is boring and plain to me. I appreciate that they are a good base to work off of but just by itself - yawn.
There have been a time or 2 that something would not flash through TWRP or CWM is recommended by the dev, though this is few and far between on this phone. I mod phones all the time (have done over 100 different ones) and sometimes things just work better on one than the other for various reasons.
es0tericcha0s said:
CM is usually the go to to try something else because A) It's usually the most stable of aftermarket Roms due to the larger community and user support B) been around the longest / out for the most phones so is more well known C) it's different than AOSP so if you have issues with AOSP AND CM then you know something is really going on. That being said, CM is boring and plain to me. I appreciate that they are a good base to work off of but just by itself - yawn.
There have been a time or 2 that something would not flash through TWRP or CWM is recommended by the dev, though this is few and far between on this phone. I mod phones all the time (have done over 100 different ones) and sometimes things just work better on one than the other for various reasons.
Click to expand...
Click to collapse
The problem im facing doesnt seem to be related to stability .... can try twrp though to make sure there isnt a problem with flashing or resetting through CWM.... Should I directly install TWRP over CWM or should I first reset my phone with stock and then root again before installing TWRP?
Ad.Shk2 said:
The problem im facing doesnt seem to be related to stability .... can try twrp though to make sure there isnt a problem with flashing or resetting through CWM.... Should I directly install TWRP over CWM or should I first reset my phone with stock and then root again before installing TWRP?
Click to expand...
Click to collapse
The stability idea was referring to the other poster's confusion over why someone suggested trying CM in the first place.
You can install TWRP over CWM with no issues. I typically just fastboot the recovery image, though if you aren't comfortable with that, then install the app GooManager and installing the OpenRecovery script in there will do the trick for you. No reason to go all the way back to stock at all for that. If I had a $1 for every time I had issues because of some file / recovery /formatting incompatibility, then I'd probably be able to take my wife out to a fancy dinner. Heh (I work on a lot of phones, it's my job. ) If you need help with either method, feel free to hit me up on Hangouts or make sure to post quote me because otherwise I'll forget to check back on the thread. Good luck.
es0tericcha0s said:
The stability idea was referring to the other poster's confusion over why someone suggested trying CM in the first place.
You can install TWRP over CWM with no issues. I typically just fastboot the recovery image, though if you aren't comfortable with that, then install the app GooManager and installing the OpenRecovery script in there will do the trick for you. No reason to go all the way back to stock at all for that. If I had a $1 for every time I had issues because of some file / recovery /formatting incompatibility, then I'd probably be able to take my wife out to a fancy dinner. Heh (I work on a lot of phones, it's my job. ) If you need help with either method, feel free to hit me up on Hangouts or make sure to post quote me because otherwise I'll forget to check back on the thread. Good luck.
Click to expand...
Click to collapse
Thanks a lot for the help bro. I just flashed TWRP (fastboot method) and wiped my phone, the problem "unfortunately, phone has stopped" persists..... Any ideas?
Ad.Shk2 said:
Thanks a lot for the help bro. I just flashed TWRP (fastboot method) and wiped my phone, the problem "unfortunately, phone has stopped" persists..... Any ideas?
Click to expand...
Click to collapse
Ah, that sucks man. Ok, well, next things to try include:
Wipe cache + dalvik
Go to Advanced / Fix Permissions
Reboot
Do you have a PIN on your SIM card? I was reading through the Purity thread and some were saying they had your problem and disabling that resolved.
es0tericcha0s said:
Ah, that sucks man. Ok, well, next things to try include:
Wipe cache + dalvik
Go to Advanced / Fix Permissions
Reboot
Do you have a PIN on your SIM card? I was reading through the Purity thread and some were saying they had your problem and disabling that resolved.
Click to expand...
Click to collapse
Nope no pin.... Will try the permissions thing and shall let you know.
Sent from my Nexus 5 using XDA Premium 4 mobile app
es0tericcha0s said:
Ah, that sucks man. Ok, well, next things to try include:
Wipe cache + dalvik
Go to Advanced / Fix Permissions
Reboot
Do you have a PIN on your SIM card? I was reading through the Purity thread and some were saying they had your problem and disabling that resolved.
Click to expand...
Click to collapse
No luck my friend, I'm back on cwm... antyother ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Ad.Shk2 said:
No luck my friend, I'm back on cwm... antyother ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It looks like at this point, it's time to try another rom or update the Purity one. That, or maybe try this: http://forum.xda-developers.com/showthread.php?t=2526844
Dw about it. Fixed it. Apparently there was a problem with the com.android.phone/telephony. UnInstalled them, and then factory reset my phone. Then installed the Rom again. All well thanks for you help bro.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Ad.Shk2 said:
Dw about it. Fixed it. Apparently there was a problem with the com.android.phone/telephony. UnInstalled them, and then factory reset my phone. Then installed the Rom again. All well thanks for you help bro.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You're welcome. Glad all is well again.
I had the same problem. But i did not make a backup..
How can I unninstall phone apk from recovery?
I flashed Moar a couple months ago. Also added custom recovery. Just yesterday the infamous "warning camera failed" came on. I want to take my phone to sprint so I need to flash it back to stock. Please help!
Google search. Problem solved.
Sent from my SM-G900P using xda premium
Glitterloveglamour said:
I flashed Moar a couple months ago. Also added custom recovery. Just yesterday the infamous "warning camera failed" came on. I want to take my phone to sprint so I need to flash it back to stock. Please help!
Click to expand...
Click to collapse
Before you unroot, and take your device back to Sprint. Have you tried booting into Recovery, and clearing caches ? Did you do a clean install of MOAR ?
Also, just an FYI. Your post should've been made in Q/A [emoji6].
prboy1969 said:
Before you unroot, and take your device back to Sprint. Have you tried booting into Recovery, and clearing caches ? Did you do a clean install of MOAR ?
Also, just an FYI. Your post should've been made in Q/A [emoji6].
Click to expand...
Click to collapse
Yes I did clear cache, I was just a bit confused since I installed philz recovery I don't know if I need to uninstall that's or just unroot?
Yes I did a clean install MoAr was working fine up until a couple days ago when my camera stopped working
Had you installed any other tweaks, mods, or Xposed Modules prior to the issue ? Using Philz Recovery should have nothing to do with the camera issue. I would suggest force stopping the camera, and clear data in Applications manager. Then immediately boot into recovery , clear caches, and reboot. After the device fully boots, check to see if the camera is working correctly. My next step after that would be a fresh install ( Full wipe ) . Then let it settle in for a few hours without installing any apps. Check the camera to see if it's operating correctly. If it is install your apps one at a time checking the camera afterward to make sure that nothing interferes with the operation of the camera.
The last resort if the issue just does not get resolved would be to ODIN back to Stock. If the issue persists, then take the device in for service.
Moved to Q&A.
prboy1969 said:
Had you installed any other tweaks, mods, or Xposed Modules prior to the issue ? Using Philz Recovery should have nothing to do with the camera issue. I would suggest force stopping the camera, and clear data in Applications manager. Then immediately boot into recovery , clear caches, and reboot. After the device fully boots, check to see if the camera is working correctly. My next step after that would be a fresh install ( Full wipe ) . Then let it settle in for a few hours without installing any apps. Check the camera to see if it's operating correctly. If it is install your apps one at a time checking the camera afterward to make sure that nothing interferes with the operation of the camera.
The last resort if the issue just does not get resolved would be to ODIN back to Stock. If the issue persists, then take the device in for service.
Click to expand...
Click to collapse
Idid a full wipe....then did a full wipe and installed the new version of MOAR and I am still having the same problem *sigh*
how would I go back to stock do I need to upload a different recovery, the changes I've made are philz and Moar, or do I just simply unroot and put stock firmware?
I decided to reflash to stock from the Renovate Note 7 ROM I was running. Everything went smoothly in odin and the phone rebooted, but it booted to the same wallpaper, same apps, but now force closing because apps from the Note 7 are on the older firmware. Does anyone know how to fix this? I just wanna go back to stock, fully wiped. If anyone can help as soon as possible that would be awesome. It is not such a grave problem because I can access download mode. Thanks!
NizzleFish98 said:
I decided to reflash to stock from the Renovate Note 7 ROM I was running. Everything went smoothly in odin and the phone rebooted, but it booted to the same wallpaper, same apps, but now force closing because apps from the Note 7 are on the older firmware. Does anyone know how to fix this? I just wanna go back to stock, fully wiped. If anyone can help as soon as possible that would be awesome. It is not such a grave problem because I can access download mode. Thanks!
Click to expand...
Click to collapse
ODIN doesn't wipe anything, maybe enter recovery mode and factory reset?
Sent from my Smartfren Andromax AD9A1H using XDA Free mobile app