Im currently on the original leaked USCC Froyo rom and am have alot of issue. I was wonders...
a. should I reinstall this rom to fix issues
b. will I need to revert back to stock, root, install clock work then upgrade?
c. Is there alot of people having issue with the froyo build?
issues im experiencing are lag, freezing, issue where standby button randomly takes screen shots, and a few other random issues
what should I do?
First thing I would is redownload the rom and reflash it. That is usually the easiest fix. Are you still having problems? Will try to help you where I can!
K ill redownload it and reinstall it and see if it helps
Reinstalled leaked froyo plus I installed the red CMW and voodoo.
Havent played around to much but I have noticed it runs alittle faster but thats prolly because the lagfix. still having some freezing though
What exactly is freezing? Certain apps or when you try to do certain things?
its freezes in both some times it freezes when im trying to play music sometime it freezes when im texting sometimes it right when the phone boots. it seems completely random and never had any of these errors on enclair with CMW and voodoo.
You may want to try a reset on it next. Make sure you back up everything with titanium first tho. Factory reset option in recovery. You may have to do this after a reflash tho. You may also need to wipe the dalvik cache before a new flash too. Those are the things I would try if you are still having issues.
Also be careful which things you back up with titaniun, I've read restoring certain data onto a new rom can cause issues like that
Sent from my SCH-I500
thanks for the replies I just went ahead and installed the newwer E16 rom which is running much better
Related
I am having a problem with switching ROMs on my sensation which just started a few days ago. I am currently running ARHD 3.1.1 and it is very stable and I have had no problems whatsoever, but like many here, I like trying out different and new ROMs. Anyways, I did a backup and installed ARHD 3.6.2, and it was forcing close on several apps, and kept getting soft reboots, so I tried RCMix's, and it would load and automatically install some apps and settings that I had on my previous ROM, and it was working fine, but then I started getting soft reboots when I would open any app, so I tried about 2 other ROMs (S3n5eay/Pyramid3D) and same thing, so being fed up I restored my backup and then I began to have superuser problems, so I unistalled updates, cleared data, and still was unable to gain root access. I kept clearing data, installed superuser 2.3.6 then 3.02 and finally got root again, but everytime I reboot I lose root. I then again tried different ROMs, and same thing is happening. I have used superwipe script, ARHD's wipe script, P3D wipe script, formated from CWM, and no matter what, I am still unable to keep a new ROM and keep losing root with my backup. I'm sorry for a long post, but can anyone please help me figure this out. I have upgraded ROMs many a times in the past on this phone and others, and have never experienced these problems, so can someone please help me.
I kinda had the same problem with you, with that being root was the problem. But the ROM's are pre-rooted so that shouldn't be a problem. Try to flash the root file again, until it is succesfull flashed.
Thanks. I'll go ahead and try that.
Sent from Sensational toy running ARHD 3.1.1
Geez, that sounds horrible, man. It never ceases to surprise me how different every one of these seemingly identical devices are.
West0000 said:
Geez, that sounds horrible, man. It never ceases to surprise me how different every one of these seemingly identical devices are.
Click to expand...
Click to collapse
Well for the most part everyone downloads different software. For that just one of the factors that make us all somewhat "different" this is why everyone has some sort of problems here and there.
Most times a fix can be a reboot or reinstall of the app. Even clearing of caches helps because of data conflicts on the phone. Especially when someone like me that flashes different ROMS, that's why nandroids and backups are key so that if you fudge up your phone, you can always revert back to your nandroid.
And for all the people who are trying to revert back to their nandroid after flashing a different rom, you need to use the wipe data scripts in ARHD or Coredroid to reformat the ext4 before reverting your nandroid. Just a FYI.
All I know is that wiping everything before flashing a new ROM does not guarantee that you won't get FCs and soft reboots.
For example, I did a factory reset, wiped cache, wiped dalvik, and then did superwipe (yes I know redundant), and then flashed a ROM and I thought nothing could go wrong. Then while setting up I went ahead and setup my google account during the setup process, and once I was finished I began restoring my apps+data from Titanium Backup. While that was happening Market started auto-reinstalling my apps, and this instantly conflicted with the fact that I was doing the same thing from TB. It caused a few of my apps to FC all the time. So make sure you skip adding your google account during setup.
You can also get stuff to go haywire if you restore system data from TB. Doing so will conflict with the ROM and cause FCs and reboots. For example, I didn't know how to easily back up texts and contacts for a while, and I would go in to TB and restore everything that said something like mms, messages, texts, messages widget, etc. and doing so actually caused my messages to go haywire. Same thing with contacts. The only things you should be restoring from TB are your user apps+data. As already noted, you should also superwipe before restoring a nandroid because it is exactly like flashing a new ROM. If you're on a ROM you just flashed that has 1 version of superuser, and then you go straight into recovery and restore a nandroid without wiping everything first (and has a different version of superuser), you're going to get issues with superuser.
The rule of thumb when it comes to avoiding FCs and reboots is to avoid letting data conflict. Don't mix ROM data, don't mix app data, don't restore system settings from your old ROM on your new one, etc.
Believe me, I have attempted everything without any success. I guess I'm going to stay on my current ROM until I get the time to deal with all of this, and hoping that for whatever reason I don't have to reboot my phone, or that it randomly reboots in order not to deal with the problems. I have always wiped going/coming from different ROMs, but have never experienced this before, and it is very frustrating especially when I like to try different developers mods. I'll keep attempting to try to figure this out, and if I find a solution, I will update.
cbrvnm said:
Believe me, I have attempted everything without any success. I guess I'm going to stay on my current ROM until I get the time to deal with all of this, and hoping that for whatever reason I don't have to reboot my phone, or that it randomly reboots in order not to deal with the problems. I have always wiped going/coming from different ROMs, but have never experienced this before, and it is very frustrating especially when I like to try different developers mods. I'll keep attempting to try to figure this out, and if I find a solution, I will update.
Click to expand...
Click to collapse
Keep trying different ROMs and different strategies of when you wipe/restore stuff. It's quite interesting that theoretically identical phones can have different responses to the exact same actions. 2 people can install a ROM in the exact same way and for 1 it will work, the other it won't. You just gotta work it out until you figure out how to manage your particular issues.
Yeah, I hear you. It's just very frustrating when in the past I have switched ROMs on all the phones that I have ever owned without any problems until now. But I'll try different methods and see what happens. I appreciate everyones input. Thanks. Oh, and if anybody has any other suggestions, please, share.
Ok, I was able to get Pyramid3D v0.8.0 working so far. I flashed with superwipe about 3 times then installed the ROM. I did not sign into my account, and installed my apps from titanium first, and then signed in. I got several reboots with setcpu so I unistalled it. I also get a few market fcs. Now the problem that I have is that I installed the 4EXT recovery and my phone is unable to play my music files through any of the music players. I am able to open them with astro, but not music player. But I guess I'll try to figure this one out now. Thanks for the advice.
The Janitor Mop said:
All I know is that wiping everything before flashing a new ROM does not guarantee that you won't get FCs and soft reboots.
For example, I did a factory reset, wiped cache, wiped dalvik, and then did superwipe (yes I know redundant), and then flashed a ROM and I thought nothing could go wrong. Then while setting up I went ahead and setup my google account during the setup process, and once I was finished I began restoring my apps+data from Titanium Backup. While that was happening Market started auto-reinstalling my apps, and this instantly conflicted with the fact that I was doing the same thing from TB. It caused a few of my apps to FC all the time. So make sure you skip adding your google account during setup.
You can also get stuff to go haywire if you restore system data from TB. Doing so will conflict with the ROM and cause FCs and reboots. For example, I didn't know how to easily back up texts and contacts for a while, and I would go in to TB and restore everything that said something like mms, messages, texts, messages widget, etc. and doing so actually caused my messages to go haywire. Same thing with contacts. The only things you should be restoring from TB are your user apps+data. As already noted, you should also superwipe before restoring a nandroid because it is exactly like flashing a new ROM. If you're on a ROM you just flashed that has 1 version of superuser, and then you go straight into recovery and restore a nandroid without wiping everything first (and has a different version of superuser), you're going to get issues with superuser.
The rule of thumb when it comes to avoiding FCs and reboots is to avoid letting data conflict. Don't mix ROM data, don't mix app data, don't restore system settings from your old ROM on your new one, etc.
Click to expand...
Click to collapse
Good post. I didn't realize I should be doing so much wiping even before restoring a backup.
Incidentally, I'm kicking myself now, but in the excitement of flashing my first custom ROM, I forgot to backup my original system. Doh. It's the only time I haven't backed up before changing ROMs, but that's arguably the most important backup to make.
Hi Everyone,
So recently YouTube updated to version 2.4.4, and apparently, videos launch with considerable lag that locks up the device. I've tried every rom with every kernel and they all behave the same. Maybe Titanium Backup? But it worked before...
1. Anybody else getting this?
2. Any solutions?
Wait I just installed RolleTube (version 2.1.6) and it still lags. Now I'm seriously wondering what's wrong.
something is wrong on a system level. try a fix permissions in cwm
icenight89 said:
something is wrong on a system level. try a fix permissions in cwm
Click to expand...
Click to collapse
Well, the even weirder thing is that when I just install a ROM, TiBu, and run youtube, there's no lags. Then when I reboot (because of battery or something), the lag reappears. Fix Permissions seems to be locking up in the middle of the process, and I have to hard shutoff to get the device back working. Funny thing is that youtube worked fine like a month ago...
eliwu26 said:
Well, the even weirder thing is that when I just install a ROM, TiBu, and run youtube, there's no lags. Then when I reboot (because of battery or something), the lag reappears. Fix Permissions seems to be locking up in the middle of the process, and I have to hard shutoff to get the device back working. Funny thing is that youtube worked fine like a month ago...
Click to expand...
Click to collapse
I would wipe everything and start fresh
Sent from SKYROCKET
NexusMod 4.0
Romracer 0.3
xcrazydx said:
I would wipe everything and start fresh
Sent from SKYROCKET
NexusMod 4.0
Romracer 0.3
Click to expand...
Click to collapse
Did that already... Even wiped my internal 16gb. Darkside wipe, fix permission, etc. etc. didn't work - still there.
Also: it seems Go Launcher also has some problems with YouTube's lag... the widget on Go Launcher lags to launch the video on the widget, while twlauncher doesn't have that (as much). Still has crazy device-locking lags though.
EDIT: Oh wow... it seems when I connect my phone to my PC it shows up as a corrupted disk... Windows is asking me if I want to fix the disk. Would that be the problem? And if it is, can I let Windows fix the disk?
I don't think I would let windows do that. It says corrupted or needs formatted?
Sent from SKYROCKET
NexusMod 4.0
Romracer 0.3
Ok. Boot into odin and reflash cwm 5.0.2.6. Boot into cwm and format system, then data, the cache and dalvik cache. Repeat 3x. Flash stock through odin. Reboot, twice. Now reflash cwm and then flaah a rom and configure. I don't care what your problem is, that method is a guarantee fix lol
icenight89 said:
Ok. Boot into odin and reflash cwm 5.0.2.6. Boot into cwm and format system, then data, the cache and dalvik cache. Repeat 3x. Flash stock through odin. Reboot, twice. Now reflash cwm and then flaah a rom and configure. I don't care what your problem is, that method is a guarantee fix lol
Click to expand...
Click to collapse
I did this, and I still had lag after restoring TiBu. Lol the look on my face when it happened
But turns out, the TiBu backup of Go Launcher was actually screwing many apps up (including YouTube)... dunno if it was a system issue, but it was the problem. Transitioned to ADW after a full wipe again (without ever launching go launcher) and all was good. Thanks guys.
eliwu26 said:
I did this, and I still had lag after restoring TiBu. Lol the look on my face when it happened
But turns out, the TiBu backup of Go Launcher was actually screwing many apps up (including YouTube)... dunno if it was a system issue, but it was the problem. Transitioned to ADW after a full wipe again (without ever launching go launcher) and all was good. Thanks guys.
Click to expand...
Click to collapse
Don't restore stuff across roms with TiBu. I only use it as a reference of the apps I had. So I always have a clean slate
xcrazydx said:
Don't restore stuff across roms with TiBu. I only use it as a reference of the apps I had. So I always have a clean slate
Click to expand...
Click to collapse
glad u got it sorted. And while I agree with xcrazydx thay starting clean is best, I have too many apps and not enough time, so thag metgod is impractical. I've never had this ssort of problem though to be honest
My girlfriend's Skyrocket starting tonight has been freezing while the screen is locked. It won't wake by pressing the button immediately, but opens briefly after maybe 30 seconds. I pull the battery and restart and it worked fine for about two hours and did it again.
Any ideas? I have her fix permissions but it keeps coming back.
I feel bad because she was fine with stock but I convinced her to let me root it!
Unlocked, rooted, stock rom.
wipe cache and dalvik cache? Any new apps or changes that have been done recently?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
this happens to mine maybe once every two weeks, so it is so few and far between that i dont mind. using nexusmod gb.
whenever it freezes, i hold down the home button to see which apps are running and attempt to close them, but it takes too long and i just yank the battery. the only common app that is always running during every freeze is 'phone'.
jphilippon said:
My girlfriend's Skyrocket starting tonight has been freezing while the screen is locked. It won't wake by pressing the button immediately, but opens briefly after maybe 30 seconds. I pull the battery and restart and it worked fine for about two hours and did it again.
Any ideas? I have her fix permissions but it keeps coming back.
I feel bad because she was fine with stock but I convinced her to let me root it!
Unlocked, rooted, stock rom.
Click to expand...
Click to collapse
Rooting wont freeze your phone, that's something to do with the ROM. Did you make a CMW backup before rooting? If yes, then you can boot into recovery, perform a factory reset 3 times, then wipe cache 3 times, then wipe davlik cache 3 times, then restore from the backup, reboot back to recovery and flash the radio (the ICS radio's ) work with GB so you can chose one from them.
If you haven't made a backup, you can download the stock 2.3.5 rom from sammobile, install it, and then do the update to 2.3.6.
Also dont restore apps, using Titanium backup, it causes issues. You can use superbackup to restore, call logs, sms and contacts, that's what I use.
If you would like to try a ICS rom, you can install Sky ICS 4.2E, there is an update 4.2F but it kept crashing so I am on 4.2E runs butter smooth as the stock GB.
All custom ROMS you can find in the Android Development Section
Unless she is going to run themes on AOSP, she probably won't get much other benefit from root. Sounds like she just wants stable, stock. I learned that lesson the hard way with my wife...every time she ran into a glitch! Otherwise, SkyICS is going to be your best bet for the least problems. My wife has been using it with no complaints... yet.
Sent from my SGH-I727 using xda app-developers app
aviseqdas said:
Rooting wont freeze your phone, that's something to do with the ROM. Did you make a CMW backup before rooting? If yes, then you can boot into recovery, perform a factory reset 3 times, then wipe cache 3 times, then wipe davlik cache 3 times, then restore from the backup, reboot back to recovery and flash the radio (the ICS radio's ) work with GB so you can chose one from them.
If you haven't made a backup, you can download the stock 2.3.5 rom from sammobile, install it, and then do the update to 2.3.6.
Also dont restore apps, using Titanium backup, it causes issues. You can use superbackup to restore, call logs, sms and contacts, that's what I use.
If you would like to try a ICS rom, you can install Sky ICS 4.2E, there is an update 4.2F but it kept crashing so I am on 4.2E runs butter smooth as the stock GB.
All custom ROMS you can find in the Android Development Section
Click to expand...
Click to collapse
SkyICS 4.2F is running far more flawlessly than all other sky roms. The vast majority of users have no issues. It's based on an official release, not a leaked release. Those users with issues are normally at fault, not the rom; and these issues are usually easily fixed.
Don't be afraid of 4.2F.
Using SeanZ's SkyICS 4.2F r2 v6B ROM / XDA Premium
I followed the instructions exactly on this page: http://forum.xda-developers.com/showthread.php?t=1663169
CM9 seemed to work fine for a while. I installed Titanium Backup and brought back my apps and just a bit of system data (contacts, voicemail, texts, etc). After I had restored those things, it said it suggested a reboot. I did that, but now it just reboots over and over. I can't get in to the OS for more than a few seconds before it reboots again. Help please!
As that thread specifies, I have a MX2 from CSpire. For now I don't care so much about getting CM9 working as just getting my phone back to a working state. I have both a nandroid and titanium backup on the sd card. I just need very specific instructions on how to get back to the way it was (2.3.6) given that I can't get in to the OS.
Edit: Pulling the battery doesn't resolve anything
Does it let you stay in long enough to remove the app/settings you restored? Are you able to get into recovery mode at all?
If you can get into recovery you might first want to try Fix Permissions and see how that works. If this does not solve it then consider doing a factory wipe and start restoring your apps/settings again one by one and rebooting in between until you get to the particular one that started your reboot problem.
What ROM were you on prior to CM9? Although they should be largely universal sometimes there are some slight changes in custom ROMs that might work well in many other ROMs but not in a select few. Other times it is an app that is not compatible.
The post below might be of some help since your phone seems to have a different method of getting into recovery than what I have dealt with so far.
http://forum.xda-developers.com/member.php?u=4395758
Factory Restore DX2
This might help. It's a factory restore, like you just bought it. http://forum.xda-developers.com/showthread.php?t=1317707
After much sweat, tears, and button pressing, I have gotten it back to stock CM9 and it seems to be behaving as expected. I am going to install apps one by one and reboot between every install. Hopefully I'll find the culprit soon enough.
Hi,
I recently have flashed some new roms on my phone. So heres what happened... I had been using MIUI for months now for my NxS4g but the MIUI rom was just getting too laggy for me for daily use. So then I flashed Factory Rom. Worked good for a while then it started this rebooting randomly.. I Did Full Wipe, Format etc before flashing.. It seems fine while using it but once I turn the screen off and let it sit it just starts to randomly reboot. So I thought oh well its just the rom. Then I went back to MIUI and flashed the new Miui 2.10.26.2 which is a great running rom and I thought it fixed my problem because I spent an hour or 2 installing fresh new apps from the market, didnt restore anything or flash a custom kernel everything was stock and all fresh new apps. So I went to bed woke up at 6am like usual and noticed my phone had stopped responding... had to take the battery out and boot it up.. sometimes it does that and i have to pull the battery and sometimes it fully reboots. So now I am stumped ive tried everything i know. full format/wipes, fixing permissions, wiping dalvik and cache, and still not working! I hope my phone isnt dying or something. It was working fine. Please if anyone has a fix or knows what to do please help me! The only thing I haven't done is formatted my SD card which is what im about to try.
Thanks in Advance!
Adam
Hi,
What factory ROM?
Every ns4g responds to different kernels differently...maybe the newest version of that ROM u installed had a different kernel that sometimes causes many random reboots... so check that plz.
But u say udid a factory reset and stuff... did u wipe Dalvik and cache? Cuz that is important.
Good luck
Vs Nexus S4G using tapatalk2