Hey guys, im having a weird problem. When ever i flash a touchwiz based rom everything goes fine for sometime and then (maybe after a random reboot) my phone changes its wallpaper to i once applied on cyanogenmod 12.1. And after this happens my wifi stops working, i flashed darklords s6 rom and the aurora v6 note 4 rom it happened on both the roms i even reflashed the roms but i face the same problem. After flashing the roms i restore my apps and system data with titanium backup, is TB causing this problem or is it something else?? Please someone help...
Related
I've been using CM10.1 on this phone pretty much since it's been available and updating nightlies about once a week usually. Typically I use Ktoonsez kernel and also update this regularly. Also I am on the MF1 firmware. So, I'm pretty comfortable with the update process and have done it many times.
The other day I attempted to update to CM10.1 7/8 nightly while also installing a kernel I've never tried before called 'Sultan-kernel-Venturi-r5-USA'. Also completing the update process I rebooted and the phone would not move past the CM loading animation splash screen. After about 10 minutes of this I pulled the battery and rebooted, hoping it was just a hiccup but the same thing happened. After dirty installing various CM10.1 nightly and release versions with various combos of no custom kernel and the KT kernel but nothing would fix the boot issue.
I then attempted to wipe and ended up eventually wiping everything on the phone except the external SD card. Still, I could not get the phone to move past the CM splash screen. I then tried a few other AOSP ROMs with the same issue presenting.
Eventually I installed a TW based ROM and was able to get the phone to boot and and able to at least use my phone now. I've tried a couple time since to do a nandroid backup then try installing CM10.1 again and still nothing changes. I can restore the backup and the TW ROM works fine again.
Any ideas on what could have happened to cause this or anything else I can try to get AOSP ROMs working on my phone again?
I would say Odin back to 4.0.4 stock, do the OTA's, reroot with the one click root in the developer section, and it should work.
Sent from my SCH-I535 using xda app-developers app
I did get this figured out. Somehow my EFS partition was wiped. TW based ROMs would actually boot but displayed a 'Factory Mode' warning on startup. AOSP ROMs would not finish booting at all. After restoring EFS from backup everything started working again.
I dont know if its my phone or what but I haven't had any luck with AOSP ROMS on this phone. It seems like there's always some sort of bug that just kills it. I flashed a CM10.2 rom that felt like speed of lightning but was bugging out. I tried ecilpse and some others but all were to buggy for me. I recently tried to flash liquid cause I wanted to run something else other than touchwiz but it ruined my phone and now I cant flash custom ROMS(i have a help thread up..feel free).. Anyone else having bad luck on these AOSP ROMS
Not what you want to hear, but I'm having no issues with flashing new ROMs. I'm only using LiquidSmooth and waiting/hoping for a 'complete' 4.3 version, but again, no problems with flashing to a new ROM. I have been running LS2.9 (4.2.2) for several weeks and on Sunday flashed up to LS2.10 (4.3) but went back to 2.9 because when I mirror my phone on my AppRadio3, it doesn't auto-rotate my screen to landscape, so I have a portrait orientation of my phone on the radio display, which makes it so small as to be unusable.
I don't recall what method I used to root my phone, but I'm using TWRP 2.6.3 to perform a) a clean wipe every time (Factory Reset + System), then b) install the new ROM, and c) a final reboot back in to recovery and flash the latest gapps image. Does it take a little longer to follow this process? Sure, but it's a reliable process that means I don't have issues afterwards to mess with, so the extra time spent on the front end is worth it to me.
I've had moderate success with the AOSP ROMS. Each one seems to have it's own small bugs, but the AOSP ROMs that I've tried didn't have anything that ruined functionality. Been running Dirty Unicorn ROM for the past couple days and it is really solid. Haven't noticed any issues at all with it yet.
It's got to be your downloads or install process. Do you check MD5? If no then start. Remember just wipe data for each install. Updater-script in ROM zip wipes system for you. Cache resides in data. Do NOT restore system data using TiBu. Other than that I don't know what else to tell ya bud :/
Sent from my SCH-I535 using Tapatalk
Haven;t had any trouble with AOSP flashes, but many of the ROMs or maybe most have some bugs. All the so called AOSP ROMs are built off the same base, CM10. None of them support all the hardware and software features that Tocuhwiz supports. I find the custom TW ROMs far superior in features and as good or better in speed as well.
Make sure you are flashing a compatible Kernel when you switch between CM based ROMs and TW based
I have root my S4 (I9505) and also transformed it to S5 and after a few days the Bluetooth is not turning on (I have stock/official rom).
Any help please?
anorthosis said:
I have root my S4 (I9505) and also transformed it to S5 and after a few days the Bluetooth is not turning on (I have stock/official rom).
Any help please?
Click to expand...
Click to collapse
What specifically installed on the device?
Tamerlan2009 said:
What specifically installed on the device?
Click to expand...
Click to collapse
http://www.androidpit.com/how-to-transform-your-galaxy-s4-into-an-s5
anorthosis said:
http://www.androidpit.com/how-to-transform-your-galaxy-s4-into-an-s5
Click to expand...
Click to collapse
put the default settings
Ok thanks. I will try it.
I'm facing the same problem too... last week only i rooted my phone and installed CWM recovery...then i installed Custom Rom's like Hassan ROM, Omega ROM, Cyanogenmod 11 Rom, Pacman ROM etc etc just to check various Rom's and their features out.....At first i installed only one ROM at a time and den also dual booted two ROM's by romswitcher...While i was checking my phone once i discovered that my phone's Bluetooth is not turning ON...The toggle is only becoming light green and also from the settings its only showing turning Bluetooth On but it's unable to turn bluetooth On.....Now i googled my problem and read across various forums for solution...I tried various things also flashed my firmware to stock samsung but still bluetooth does not turn On...also i flashed with stock samsung firmware of feb and march 2014 and updated my phone over OTA but still the problem persists....i even installed latest perseus kernel while rooted but still could not turn my bluetooth ON.
I would be very grateful if someone can help me solve my problem and help me Switch ON my bluetooth as it is very needed aspect for my daily use.
My Version of S4 is i9500 with android kitkat 4.4.2. Also all my other features are working normally on custom ROM's too.
suhasdutta said:
I'm facing the same problem too... last week only i rooted my phone and installed CWM recovery...then i installed Custom Rom's like Hassan ROM, Omega ROM, Cyanogenmod 11 Rom, Pacman ROM etc etc just to check various Rom's and their features out.....At first i installed only one ROM at a time and den also dual booted two ROM's by romswitcher...While i was checking my phone once i discovered that my phone's Bluetooth is not turning ON...The toggle is only becoming light green and also from the settings its only showing turning Bluetooth On but it's unable to turn bluetooth On.....Now i googled my problem and read across various forums for solution...I tried various things also flashed my firmware to stock samsung but still bluetooth does not turn On...also i flashed with stock samsung firmware of feb and march 2014 and updated my phone over OTA but still the problem persists....i even installed latest perseus kernel while rooted but still could not turn my bluetooth ON.
I would be very grateful if someone can help me solve my problem and help me Switch ON my bluetooth as it is very needed aspect for my daily use.
My Version of S4 is i9500 with android kitkat 4.4.2. Also all my other features are working normally on custom ROM's too.
Click to expand...
Click to collapse
Did you fully cleaned your phone before coming back to stock ?? i had one this problem and all i did was full wiping the phone /Data + /System etc and flashing a stock samsung rom and everything was working well
Rami_Debab said:
Did you fully cleaned your phone before coming back to stock ?? i had one this problem and all i did was full wiping the phone /Data + /System etc and flashing a stock samsung rom and everything was working well
Click to expand...
Click to collapse
yes i did full wiping including cache partition, boot, sysytem, data, sdcard, cache, and dalvik cache also...after that i installed back my stock firmware....the phone came back to original mode with OTA working well and totally unrooted but still bluetooth didn't switched on!
Flash modem
suhasdutta said:
I'm facing the same problem too... last week only i rooted my phone and installed CWM recovery...then i installed Custom Rom's like Hassan ROM, Omega ROM, Cyanogenmod 11 Rom, Pacman ROM etc etc just to check various Rom's and their features out.....At first i installed only one ROM at a time and den also dual booted two ROM's by romswitcher...While i was checking my phone once i discovered that my phone's Bluetooth is not turning ON...The toggle is only becoming light green and also from the settings its only showing turning Bluetooth On but it's unable to turn bluetooth On.....Now i googled my problem and read across various forums for solution...I tried various things also flashed my firmware to stock samsung but still bluetooth does not turn On...also i flashed with stock samsung firmware of feb and march 2014 and updated my phone over OTA but still the problem persists....i even installed latest perseus kernel while rooted but still could not turn my bluetooth ON.
I would be very grateful if someone can help me solve my problem and help me Switch ON my bluetooth as it is very needed aspect for my daily use.
My Version of S4 is i9500 with android kitkat 4.4.2. Also all my other features are working normally on custom ROM's too.
Click to expand...
Click to collapse
If you flash omega ROM and follow instructions correctly you have to flash modem which is not part of the main ROM
Geoxx said:
If you flash omega ROM and follow instructions correctly you have to flash modem which is not part of the main ROM
Click to expand...
Click to collapse
yups have flashed modem too from omega files
suhasdutta said:
yups have flashed modem too from omega files
Click to expand...
Click to collapse
Try The Solution I Gived You In Omega Thread
Let me Know iF iT Works
Sent From My MobiLe Phone
Hello!
I was using the SungSonic ROM for almost a year now and I decided to change it today. So I flashed a CyanogenMod Nightly build for the P3100 This morning.
It booted up fine, and there were no issues in the beginning.
But then it started disconnecting calls randomly. Like, Someone calls, The phone rings for a second and boom! It shows a missed call.
I figured rebooting it would fix it but it made my problem only worse.
It now barely shows any Network service at all. If it is there, only for about 20s before it goes back off.
Is there any way to fix it without flashing another ROM? I like CyanogenMod and plus, its for my mother and I prefer keeping it simple.
Also, keep in mind that my Tab does not get recognised on any PC with any Cable I could find.
So, I am stuck with PhilZ Recovery for the P3100.
If the problem can be fixed via Flashing a new Mode/Baseband then please, give me a .zip for only the modem and not the whole ROM.
Thank You for Reading and I will hope you guys help me out.
Regards,
Shinichi Reshima
Always do a nandroid B/U before you flash so if you run into a problem like this you can go back. CM nightlys are not always stable, and sometimes you can't use them unless you have the base stable version of that ROM already installed. Must try and install the base version of the build, it may fix your problem. I run CM11 by Android Andi with no issues and no nightlys.
Pp.
Okay, so ...
I was using CM11 the last avaliable build and I had no problem with it.
Yesterday I've decided to preview the new ALPHA CM12 so I flashed it and played with it for some time.
Because of bugs I've flashed back CM11 based ROM but this time it was ParanoidAndroid BETA5.
The ROM is perfect but there is no way to start Viber anymore. After installing and opening the app it goes in to crash loop (Unfortunately, Viber has stopped). And that goes all the way until I force close it.
Then I wiped data and cache again and installed CM11. The problem was still there ?! Can't understand the "logic" ?!
Then I was tired and decided to try it with stock rom. Downloaded ODIN and flashed stock. Viber wokred perfectly. Why?
Why I can use it anymore on custom rom?! The problem started when I flashed CM12 and flashed back CM11.
Any help?
I had the same problem on CM11 but only on latest version of viber (5.1)
I downgraded to an earlier version (5.0.2) and everything works fine. I just need to make sure that viber doesn't update on its own
Viber have new update and now no problem with FC.