Phone reboots-runtime reboot or soft reboot? - Nexus S Q&A, Help & Troubleshooting

Hi all,
When I am browsing market then decide to press the back or home button. Sometimes my phone will reboot for no reason, this happens maybe 3/5 times when I'm browsing market. I'm running the bionix rom with 1.3ghz Trinity kernel. This happened while I was running bionic with 1.2 ghz Trinity kernel.
Thanks!
Sent from my Nexus S using XDA App

Ssunyoto said:
Hi all,
When I am browsing market then decide to press the back or home button. Sometimes my phone will reboot for no reason, this happens maybe 3/5 times when I'm browsing market. I'm running the bionix rom with 1.3ghz Trinity kernel. This happened while I was running bionic with 1.2 ghz Trinity kernel.
Thanks!
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Does it happen specifically with the market? Or does it also happen with other apps too? Also, are there any other common factors among your random reboots (the colloquial term for what you are referring to)? My best advice would be to wipe your dalvik cache, cache, and data and then reflash the rom and kernel. Restore your apps the long way and see if that solves your problem.
(the reason I'd recommend this is that it sounds like there is an issue with your flash and a clean flash might clear that up)

Hey thanks for the fast reply, I actually went to clockwork and wipes every single option avaible except dalvick. Also it only seems to happen while closing or switching from market. I have not experienced the reboot during calls issue like other users. So if I do wipe Dalvick cache, does it uulnable root? Sorry, my first android phone here.
Sent from my Nexus S using XDA App

Ssunyoto said:
Hey thanks for the fast reply, I actually went to clockwork and wipes every single option avaible except dalvick. Also it only seems to happen while closing or switching from market. I have not experienced the reboot during calls issue like other users. So if I do wipe Dalvick cache, does it uulnable root? Sorry, my first android phone here.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Its no problem man, everyone has "silly" questions when they start. =)
Basically, the Dalvik cache (found in advanced in Clockwork Recovery mod, aka CWM) is a list of things to boot. It speeds up the booting process but it also can cause issues during boot if there are conflicts between an old rom and a new one so wiping this is always good.
When you flash a new rom, you don't need to wipe everything, just wipe the Dalvik Cache (again found in the advanced section of CWM), Cache (found in mounts and storage and the actual action you'll be selecting will be "format cache"), and Data (found in mounts and storage and the actual action you'll be selecting will be "format data"). Once you do this flash your rom. Now if you're going to flash a kernel that you have never used before, I generally suggest allowing the phone to boot to make sure everything is fine, get myself all setup, to do a NANDroid backup before adding the kernel. That is my preference and is by no means necessary. Once you flash the kernel you can reboot and re-add your apps.
Now, I mentioned Titanium Backup and I'm still not sure you 100% know what that is so let me explain (as it is a very useful tool). It is a program that backs up your applications all with their data (IE preferences and the like). It does a great job (with the one exception that due to the way Android is built it cannot restore widgets) but it does require some work so it gets tedious when you have to use it a lot. I generally only use it the first time I'm flashing a new ROM. If you want to have a variety of roms you can easily access and switch between here is something I posted in another thread that can make it very, very easy to do:
kenvan19 said:
For reference to the OP, this is what I do. When I see a new rom I want to try I do a backup through Rom manager (it allows you to name Backups rather than just have a date/timestamp). Then I do a titanium back up of all my apps. Next I flash the rom and/or kernel I want to try and then do a titanium restore of my apps, get everything set up how I like it and then immediately do another NANDroid backup through Rom manager.
Right now I have these backups on my phone:
StockWapps (Stock rom, stock kernel, rooted, with apps set up)
CM7apps (CM7 rom, standard CM7 kernel, rooted, with apps set up)
CM714apps (CM7 rom, trinity 1.4GHz OC kernel, rooted, with apps set up)
Bionixapps (Bionix rom, standard bionix kernel, rooted, with apps set up)
Bionix13apps (Bionix rom, trinity 1.3GHz OC kernel, rooted, with apps set up)
Bionix14apps (Bionix rom, trinity 1.4GHz OC kernel, rooted, with apps set up)
On my wife's:
StockWapps (Stock rom, stock kernel, rooted, with apps set up)
CM7apps (CM7 rom, standard CM7 kernel, rooted, with apps set up)
BionixZuneApps (Bionix rom, standard bionix kernel, ZuneEvo theme, rooted, with apps set up)
If you see the pattern its basically ROMThemeKernelApps for easy reference when restoring. Its so simple that I told my wife this morning to put her phone back to stock and she was able to figure it out with only minimal help getting to the right screen (she is a complete techNOTphile)
Also, I have a backup on my computer of all of the backups. Unlike Simms, I only do backups when I make significant changes to apps, themes etc (by significant I include changing a shortcut on my launcherpro dock lol).
Click to expand...
Click to collapse
I apologize for the huge wall of text but I hope it helps! Always remember that we're here to help you (as long as you search before you post a question, not applicable to this but it makes everyone's lives easier hehe)

Woah thanks. I really don't mind not backing up haha. So I did what you said and wiped cache/data and dalvik but this time I used stock kernel with bionix. The problem I have now is that the rom manager bundled with bionix says I don't have clockwork installed and when I try to install from there, it just hangs and I have to force close, not a big deal but I can't even backup I guess.
Sent from my Nexus S using XDA App

Ssunyoto said:
Woah thanks. I really don't mind not backing up haha. So I did what you said and wiped cache/data and dalvik but this time I used stock kernel with bionix. The problem I have now is that the rom manager bundled with bionix says I don't have clockwork installed and when I try to install from there, it just hangs and I have to force close, not a big deal but I can't even backup I guess.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Hmm. Try this: turn off your phone and then once its off hold the volume up button and then press the power. This should boot you into the bootloader. Now using the volume rocker to scroll and the power button to select, select recovery. Let it boot into that then tell me what color the text is in recovery.
Sent from my Nexus S

Fixed
Hey Kenvan,
Thanks for the help, I decided to revert back in to stock Android with no root and I have stopped having problems with anything! I also do not experience the rebooting during calls bug.
Thanks!

Related

[Q]Reflashing s7 from cm7 and app install problems

So I flashed the unofficial cm7 build from the dev forum meaning I now have blue Cwm instead of red that I used with s7. What steps are required to reflash s7? Do ihave to use sgs kernel app to reflash kernel then flash s7?
Also I'm having issues restoring apps with titanium. The "stock" app installation screen doesn't allow me to choose install, only cancel. Does this issue stem from not having done a factory data wipe? The thread I read only mentioned to format the system disk but I don't think it was written from the perspective of having come from s7.
Mad props for any help
Sent from my SGH-I997 using XDA App
Yes you will eventually have to use SGS to flash a kernel. Maybe this is the long way around but when I flashed back from cm7 yesterday I used sgs kernel flasher and followed the instructions for infused gb. When I flashed the kernel it got stuck converting partitions to ext4 (probably because they were already in ext4). But I did a battery pull in the middle and was back in red cwm. After that I flashed infused again without hassle with infusion core b. That being said, as long as you have red cwm, you should theoretically be able to flash whatever rom you want.
So in short : just follow the FULL instructions to flash infused v2. Then flash s7. Hope this helps
Sent from my SGH-I997 using XDA App
Thaanks! Will try this if my reflash of cm7 doesn't fix issues....do you think my app install problems are stemming from a previous install?
Sent from my SGH-I997 using XDA App
Hmmm...well out of habit I always personally makes sure I format everything, wipe the dalvik cache, fix permissions and wipe the cache partition as well. A lot of the devs stress that this is necessary so I wouldn't doubt that your app install problems are from a previous install. Something tells me, and someone please correct me if I'm wrong, that when you are going from a voodoo enabled ROM like infused or s7 to a ROM like cm7 that doesn't use voodoo lagfix, you will have issues with trying to get your apps back because they were using a different (but still similar since they are both EXT4) file system. This is just my guess. If anyone could elaborate more on this please do.
I would highly suggest flashing back to stock if you still experience issues or even ultimate unbrick so that way you can get a clean slate. Maybe try using apps2sd. I own it and can verify that it works well. Many others have also praised it. Good luck!
stratatak7 said:
Hmmm...well out of habit I always personally makes sure I format everything, wipe the dalvik cache, fix permissions and wipe the cache partition as well. A lot of the devs stress that this is necessary so I wouldn't doubt that your app install problems are from a previous install. Something tells me, and someone please correct me if I'm wrong, that when you are going from a voodoo enabled ROM like infused or s7 to a ROM like cm7 that doesn't use voodoo lagfix, you will have issues with trying to get your apps back because they were using a different (but still similar since they are both EXT4) file system. This is just my guess. If anyone could elaborate more on this please do.
I would highly suggest flashing back to stock if you still experience issues or even ultimate unbrick so that way you can get a clean slate. Maybe try using apps2sd. I own it and can verify that it works well. Many others have also praised it. Good luck!
Click to expand...
Click to collapse
i went and did another install of cm7 before i ultimate unbrick back to stock. i figure out the app install problem; unknown sources wasn't checked...very noob. but the promt at the beginning of titanium caught me off guard and i cancelled before i could read it.
i, too, noticed that my app icons were intact on my desktop after the s7 to cm7 flash but most (if not all) those that did not require root would force close upon opening. reinstalling the app worked, but i had to get them from the market at the time as my unknown sources box was unchecked. also, i've noticed that widgets do not reload after reboot.
one more thing, after the second flash of cm7, i noticed that flashing gapps only provided me with the market. others such as email and talk were available for dl thru the market but weren't loaded from the gapps flash. i tried multiple times to no avail.
i'm about to ultimate unbrick and reflash cm7 from stock. one more last thing, i'm fairly comfortable with red cwm but have only encountered blue with cm7...how do i wipe the dalvik cache?
thanks for the help!
albee320 said:
i'm about to ultimate unbrick and reflash cm7 from stock. one more last thing, i'm fairly comfortable with red cwm but have only encountered blue with cm7...how do i wipe the dalvik cache?
thanks for the help!
Click to expand...
Click to collapse
When using TiBu, make sure and restore apps using the "restore all apps with data" option, just did it coming from S7 to MIUI and worked fine.
As far as Gapps go, I downloaded them from the Cm7 wiki and installed them manually from blue CWM just to make sure everything was added and it worked for me.
Dalvik is in advanced just like red CWM, just a different color.
xIC-MACIx said:
When using TiBu, make sure and restore apps using the "restore all apps with data" option, just did it coming from S7 to MIUI and worked fine.
As far as Gapps go, I downloaded them from the Cm7 wiki and installed them manually from blue CWM just to make sure everything was added and it worked for me.
Dalvik is in advanced just like red CWM, just a different color.
Click to expand...
Click to collapse
I've always heard it is a huge no-no to restore all apps with data.
EricNagel said:
I've always heard it is a huge no-no to restore all apps with data.
Click to expand...
Click to collapse
restoringing all USER apps with data is okay but dont include SYSTEM apps with data
EricNagel said:
I've always heard it is a huge no-no to restore all apps with data.
Click to expand...
Click to collapse
the "system data" is the no no, and "restore missing apps" is the preferred option, but I've always avoided system data and have been fine everytime I restore.

[Q] Xoom reboots when screen timeouts

Hello All,
I'm having an issue w/ my Xoom rebooting when the screen times out.
I did some searching and made sure my wifi disconnect was set to never.
Still the same thing.
I flashed the Moray Rom last night w/ no issues. (im on 3.2.1)
It ran find all day.
Today I flashed the Kernel to Tiamat Xoom 2.2.0 "Odachi" stock gpu version.
Im not sure if that is what is causing the issue or not. I also tried the OC gpu version w/ the same results.
Any ideas??
Are you overclocking? You may have the clockspeed set too high.
No OC at all - just the strait ROM and Kernal.
Ended up just restoring everything back using the nandroid backup I did.
Anycase - Ill try it again tomorrow.
Actually - can I ask you a quick question about "procedure" before flashing a new rom.
I have CWM 3.2.0.0 - and I did a nadroid backup to my sdcard.
I also have titantium backup and backed up all my apps.
I have my xoom set up exactly how I like it (The layout is what Im talking about - widgets where I want them, etc...).
To flash to the new Moray rom It says I have to wipe to factory before doing so.
So If I do that - then flash - how can I restore things so the layout is what it was before? Do I have to restore each thing individually using Titanium? If I restore using CWM it restores everything, including the kernal (Found this out already!)
Any suggestions would be great!
Thanks
Ok - Its defiantly an issue w/ this rom and my xoom.
I go back to stock and everything is fine. Screen times out - I hit the powerbutton to wake it up - good to go.
I flashed Team Tiamat Xoom Rom 2.2.2 - Moray
(d/l from this thread: http://forum.xda-developers.com/showthread.php?t=1254933 )
I set the screen timeout to 2 mins - wait - then goes to sleep after 2 mins - and reboots.
Any ideas would be causing this.
I dont have enough posts to post on the ROM thread or I would move this there.
Just for the hell of it - I restored to the nandroid backup (stock 3.2.1 w/ root) then flashed the Xoom Zone 2.2.2 ROM. Same thing.
Timeout = reboot.
rob_v said:
Just for the hell of it - I restored to the nandroid backup (stock 3.2.1 w/ root) then flashed the Xoom Zone 2.2.2 ROM. Same thing.
Timeout = reboot.
Click to expand...
Click to collapse
Well, the XoomZone rom is based on Moray, so if it is the Moray rom that's causing the reboot issue, then XoomZone wouldn't fix it. What about just the Odachi kernel with the stock rom? It might be worth a try?
What I do to minimize my setup troubles after a wipe is #1 make sure that I have a very up-to-date Titanium Backup, and #2 since I use ADW Launcher EX, I go into ADW settings and backup there.
Then after I wipe/flash the new rom, I download TB, then choose (under settings/batch) "restore missing apps and data" and that takes a while. Then I open ADW launcher EX and make it My default, then go into ADW settings and click on Restore. This should restore your desktop/pages/setup with the exception of widgets, which you will probably have to manually setup again. The trick is to be prepared and do a fresh TB backup and backup your desktop just before the wipe/install. Also, a fresh nandroid is always advisable, just in case.
Thanks for advise on the restore - exactly what I was looking for. I use ADW as well - never realized there was a backup option there
Ill do a restore of my last nandroid backup then try just the kernal and see what happens.
What allows the OC - is that part of the kernal or the Rom? Or can you OC just by having root and running something like setCpu?
The kernel is what allows overclocking.
Ok - so I ended up flashing the Odachi kernal (Tiamat-Kernel-Xoom-2.2.0-stockGPU) with the stock rom, same thing.
One other thing I noticed is that it will also reboot if I hit the power button in the back to put it to sleep mode. I hit the power - the screen turns off - then in a minute - it reboots.
Doing some more investigation - the reboot only happens when Im NOT connected via USB. If I have the USB connected - it will go into sleep mode - but will NOT reboot.
Any other suggestions? Should I move this to the Tiamat Rom thread?
I am also having this issue! Does anyone have a solution?
I put in an sd card, and now no reboots. Weird...
rmkilc said:
I put in an sd card, and now no reboots. Weird...
Click to expand...
Click to collapse
Eh - that does seem strange. I was gonna see if you guys had tried raising minimum
clock up to 200 or 400mhz....? It just might work, and if so just shows your system may be over sensitive to certain tweaks in the kernel. worth a shot
nadiros said:
Eh - that does seem strange. I was gonna see if you guys had tried raising minimum
clock up to 200 or 400mhz....? It just might work, and if so just shows your system may be over sensitive to certain tweaks in the kernel. worth a shot
Click to expand...
Click to collapse
I did try that. Didn't help. It would reboot whenever the screen was off. I put my SD card back in, and its as stable as ever!
Sent from my Motorola Atrix using Tapatalk

[Q] cyanogenmod7

First post! Hopefully it's in the correct place!
Anyways,
I have rooted my phone using the ACE Hack Kit. Once that was completed I wanted to use the cyanogen ROM(recommend from a friend). I fully wiped from phone and then ran the cyanogen zip. Everything is fine until I use my phone for an extended period of time(for instance when I'm trying to set up my phone). For some odd reason my phone will freeze and I will be forced to take my battery out. From what I've read/understand I have done everything properly. Is there anything that I possibly missed or have not done that will cause these random freezes?
Thank you,
-ant_wailes
ant_wailes said:
First post! Hopefully it's in the correct place!
Anyways,
I have rooted my phone using the ACE Hack Kit. Once that was completed I wanted to use the cyanogen ROM(recommend from a friend). I fully wiped from phone and then ran the cyanogen zip. Everything is fine until I use my phone for an extended period of time(for instance when I'm trying to set up my phone). For some odd reason my phone will freeze and I will be forced to take my battery out. From what I've read/understand I have done everything properly. Is there anything that I possibly missed or have not done that will cause these random freezes?
Thank you,
-ant_wailes
Click to expand...
Click to collapse
You or anyone wouldn't happen to know off hand if the kernel is UVed or OCed? This sounds like a UV or OC problem. Its an easy thing to fix if it is and I find that's is always best to rule out the easy stuff first! Some phones don't like to be UVed or OCed at all and freezes like this sometimes are caused by exactly that, UV or OC.
edit: and oh yeah, WELCOME! If you really like CM ROMs, give absolution a try (at the very least, if you or someone doesn't know if the kernel is UVed or OCed, you're be using a ROM I'm familiar with and if the problem persists on this ROM, diagnosing the a UV or OC problem should be fairly simple and I'll know how to get that fixed quickly for you since I haven't used the straight CM ROM in quite some time!) Actually come to think of it, did you check the md5 number? you could have downloaded a bad link causing a bad flash. It's rare most of the time but I have seen it happen..
If you havent downloaded any apps and dont mind reflashing the ROM just down load the full wipe place in ROOT (No Folder) of SD Card go into recovery.
Full Wipe (DO NOT RENAME AFTER DOWNLOAD)
http://www.megaupload.com/?d=CJPE5CB7
1. Choose zip from SD Card (Full Wipe 1.5) and Install
2. Choose zip from SD Card (Cyanogen ROM) and install
3. Reboot system and enjoy.
I dont like to do the wipe cache, wipe dalvik whatever method, the zip 1.5 does a full wipe all on its own. Its an EXT4 Wipe so I use it for all EXT4 ROMS that I like to try out.
!!!WARNING: When you flash the full wipe do not exit recovery without installing your ROM. So make sure that when you enter into recovery thru Rom Manager to reflash make sure that you have both (Full Wipe Zip) and (Your ROM Zip) on your SD Card before installing.
I tried cyanogen and completed hated it. Absolution is the Bomb!!! But to each their own flavor.
ENJOY
@reponse
First off, thank you for the responses!
@MMM-BACONSTRIPS
I do not know if the rom is OCed or UVed(had to look up those). Here's the link to the page where I downloaded it from. Also, I did not check the md5 numbers.
http://forum.xda-developers.com/showthread.php?t=965342
So far today it hasn't froze on me. However, if it does it again I'll def look at some different roms (absolution & puregandroid)
@Reinaldo33897
I did full wipe(I don't remember if the version was 1.5) before I installed the rom. If anything. I'll try absolution and puregandroid.
Once again, thank you!
-ant_wailes
ant_wailes said:
First off, thank you for the responses!
@MMM-BACONSTRIPS
I do not know if the rom is OCed or UVed(had to look up those). Here's the link to the page where I downloaded it from. Also, I did not check the md5 numbers.
http://forum.xda-developers.com/showthread.php?t=965342
So far today it hasn't froze on me. However, if it does it again I'll def look at some different roms (absolution & puregandroid)
@Reinaldo33897
I did full wipe(I don't remember if the version was 1.5) before I installed the rom. If anything. I'll try absolution and puregandroid.
Once again, thank you!
-ant_wailes
Click to expand...
Click to collapse
Not a problem man! Be aware though with the 1.5 wipe that it DOES format your system and data to EXT4, and if I'm not mistaken if you make a back-up on EXT 4 and then format back to EXT 3, it will not work and the same applies for vice versa. If you do end up trying Absolution just drop on by the Q & A if the freezing problem persists, I or one of the devs will try to give you hand the best we can..feel free to PM if you go with Absolution
So does the 1.5 wipe SDCard also? will EXT4 end up being a problem? Also, will do! I really appreciate the help!
I'll def give absolution a shot!
ant_wailes said:
So does the 1.5 wipe SDCard also? will EXT4 end up being a problem? Also, will do! I really appreciate the help!
I'll def give absolution a shot!
Click to expand...
Click to collapse
No, if you use the full wipe it pretty much just does the wipe data, wipe cache and wipe dalvik cache in one flashable zip. I typically use the 1.5 then wipe data, cache and dalvik cache. It is completely overkill and really not necessary but I do it just the same. No, EXT4 should no cause a problem. I'm pretty sure that almost all the ROMs are now EXT4 supported. I believe it would say it if it wasn't at this point. I know the major ROMS (ARHD, CD, Bindroid, MIUI) are all compatible with EXT4. The only issues you will find with EXT4 is the issue I mentioned in my first post and if you want to use gene's tool to unroot.
Welcome to xda and yes I had the same problem I was setting up setcpu and I sneezed and I accidentally pushed it all the way over to 1.9 and my phone didn't like it it just froze...I was worried :/ so I turned my phone back on and went into setting and forced setcpu to close (mind you it took a few restarts lol) but yes I had let it reset itself and now it's working again I just need to remind myself to do a nandroid once a day xD hehe
Sent from my Inspire 4G using xda premium
No problem we are here to help each other. Usually if I want to get back to EXT3 I just flash the rooted ATT gingerbread ROM (PD98 zip) in hboot.
Sent from my Inspire 4G using xda premium
Reinaldo33897 said:
No problem we are here to help each other. Usually if I want to get back to EXT3 I just flash the rooted ATT gingerbread ROM (PD98 zip) in hboot.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
I believe there is a 1.3 wipe that formats to ext 3 again, just in case the OP wanted to format to ext3 before flashing a new ROM as opposed to flashing a new rom and then having to wipe and then flash again.
Cool Thx I'll do s search for the 1.3. It be good to have.
Sent from my Inspire 4G using xda premium

Phone freezing and unresponsive

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

Rooted, Backed-Up, Flashed to Synergy...First timer...How to load backups now?

So I left Apple, came to Android, rooted my VZW GS3. First time I've ever done anything like this, so I'm new to it. I backed up EVERYTHING using TiBu, did the IMEI backup, Full system/image backup using CWM, unlocked bootloader, etc. Then I flashed to Synergy r46 (august 20th - yesterday's release).
Now I'm at work and my back-up pulled my contacts via Verizon's server, but how do I get back EVERYTHING else? SMS/MMS logs, call logs, apps, app data, etc? Do I need to download TiBu again (fresh from google market) and then load my backups off my Ext-SD card, or what? I guess I'm a bit confused as to where my TiBu items were even stored/saved...I assume it was the ExtSD card, otherwise I would have lost them all upon flashing to Synergy, correct?
Any help to get all my apps and data back on my newly Synergized phone would be awesome!!!! Thanks in advance!!!
Yes download titanium and then point it to the directory you had your back ups saved to (its sd card by default, and which is your phone storage btw) then tab to backup/restore click the check, then once your app data populates, and select run next to restore apps and data.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 02:56 PM ---------- Previous post was at 02:55 PM ----------
And no flashing roms will not wipe all your user data unless you do a complete wipe.
Sent from my SCH-I535 using Tapatalk 2
I used titanuium backup pro to back up all my Apps and system data. And when I flash a new rom I just redownload titanium pro and it automatically restores all my Apps and system data. It is the easiest app I have used. So to answer ur question.....back up ur apps with titanium then after flashing a new rom go and redownload titanium and restore your system data and apps or just apps alone if that's what u prefer? Does that answer ur question or would u like more detailed instructions?
Sent from my SCH-I535 using xda app-developers app
Welcome to android!
Sent from my SCH-I535 using Tapatalk 2
Another very nice feature of Titanium Backup is its ability to pull data from CWM nandroids. There have been a few times where I was quick to flash a new rom without doing a backup of my apps. This has saved me much time from having to re-flash the nandroid backup, backup via TB, then re-flash to the new rom.
voodoomanx said:
And no flashing roms will not wipe all your user data unless you do a complete wipe.
Click to expand...
Click to collapse
This is one thing that scares me...I don't quite understand what's being wiped or how to perform a full wipe. I hope I don't do this on accident on day...When I flashed the ROM, I basically booted into CWM recovery and installed from there....I was unable to install by opening the ROMs ZIP file via ROM Manager. When I tried to install this way, it failed.
Can somebody confirm if I flashed correctly, just to put my worries to rest? Here's how I did it...
I backed everything up, unlocked bootloader, and tried to install Synergy r46 via ROM manager, but I had problem. I had the ZIP for the ROM downloaded to my Ext-SD card, like the installation instructions say. I then opened ROM Manager and went to "install ROM from SD card." The phone rebooted and opened in CWM to install...But kept having problems finding some "path" or something.
So I decide to wing it and rebooted into CWM. I cleared davik cache(sp?), then user data, then navigated to my Ext-SD and selected the ROM ZIP to install. Now, everything seems fine and it says it installed successfully, but I still think I installed in a way that wasn't described.
Is this a legit install and is this how most people flash ROMs, from booting directly into CWM, or should ROM manager have worked for me via "install ROM from SD card???" If so, why didn't ROM Manager work for me?
Rather urgent question: When I restore my items, do I want to click "RESTORE MISSING APPS + ALL SYSTEM DATA?" ill this restore the bloatware that was on my phone prior to flashing????? If so, is there any way around it
Thanks a bunch! Just waiting on an answer to the later questions before I restore.
Weioo said:
This is one thing that scares me...I don't quite understand what's being wiped or how to perform a full wipe. I hope I don't do this on accident on day...When I flashed the ROM, I basically booted into CWM recovery and installed from there....I was unable to install by opening the ROMs ZIP file via ROM Manager. When I tried to install this way, it failed.
Can somebody confirm if I flashed correctly, just to put my worries to rest? Here's how I did it...
I backed everything up, unlocked bootloader, and tried to install Synergy r46 via ROM manager, but I had problem. I had the ZIP for the ROM downloaded to my Ext-SD card, like the installation instructions say. I then opened ROM Manager and went to "install ROM from SD card." The phone rebooted and opened in CWM to install...But kept having problems finding some "path" or something.
So I decide to wing it and rebooted into CWM. I cleared davik cache(sp?), then user data, then navigated to my Ext-SD and selected the ROM ZIP to install. Now, everything seems fine and it says it installed successfully, but I still think I installed in a way that wasn't described.
Is this a legit install and is this how most people flash ROMs, from booting directly into CWM, or should ROM manager have worked for me via "install ROM from SD card???" If so, why didn't ROM Manager work for me?
Rather urgent question: When I restore my items, do I want to click "RESTORE MISSING APPS + ALL SYSTEM DATA?" ill this restore the bloatware that was on my phone prior to flashing????? If so, is there any way around it
Thanks a bunch! Just waiting on an answer to the later questions before I restore.
Click to expand...
Click to collapse
I am wondering if you didn't do the full wipe. If you are using CWM v6.0.1.0 then there is no option labeled "user data" it is "wipe data/factory reset" which is the full wipe like I mentioned.
As far as doing it correctly, as you may have already noticed there is more than one way to do about anything. Personally, I still use CWM v6.0.1.0 and flash the zips there.
P.S. I see you are enjoying your freedom of losing your apples!
Also, tell me how your r46 is working ... I have held off at r23 while they are playing around with kernels and ramdisk tweaks for awhile.
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
dan_joegibbsfan said:
I am wondering if you didn't do the full wipe. If you are using CWM v6.0.1.0 then there is no option labeled "user data" it is "wipe data/factory reset" which is the full wipe like I mentioned.
As far as doing it correctly, as you may have already noticed there is more than one way to do about anything. Personally, I still use CWM v6.0.1.0 and flash the zips there.
P.S. I see you are enjoying your freedom of losing your apples!
Also, tell me how your r46 is working ... I have held off at r23 while they are playing around with kernels and ramdisk tweaks for awhile.
Click to expand...
Click to collapse
I'm fairly certain I did "wipe data/factory reset," I just wasn't sure how it was labeled when I typed that out, but that's really ringing a bell. I think I may have gotten the errors before (using ROM Manager) because I hadn't factory reset? Seems to me I'm good to go! However, my question regarding TiBu still remains.
Edit: In regards to informing you about r46, I'm not sure what to report as I've never used a previous Synergy and have no idea how to compare, other than to the rooted stock ROM. I have heard reports of battery life being worse than the stock ROM, and I can confirm this. I've barely used the phone since I flashed to Synergy and it's dropped 15% battery life in ~3 hours. Seems faster than before but I'm unsure.
nguyenvn said:
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
Click to expand...
Click to collapse
I started getting that sort of behavior so I just restored back to my stock rooted backup and reflashed Synergy 1.7 r23 and then reflashed the theme I'm using. I thought my issues came from other modifications I had tried so I will try to remember to report back to this post tomorrow and tell you if I'm still having those similar issues or if I'm stable again.
dan_joegibbsfan said:
I started getting that sort of behavior so I just restored back to my stock rooted backup and reflashed Synergy 1.7 r23 and then reflashed the theme I'm using. I thought my issues came from other modifications I had tried so I will try to remember to report back to this post tomorrow and tell you if I'm still having those similar issues or if I'm stable again.
Click to expand...
Click to collapse
Was 1.7 r23 supposed to be a really stable release? I read through some of the Synergy thread and didn't see anyone having the issues I had. I felt like I was doing something wrong.
nguyenvn said:
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
Click to expand...
Click to collapse
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
voodoomanx said:
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I used the EZ-unlock app in the play store. I did see that a custom kernel was loaded however when i flashed back to my nandroid (stock rooted) I am back on the orignal kernel. Would the way I rooted have an effect on the reboots? I used the non flash method by Noxious Ninja.
voodoomanx said:
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I agree I have yet to have Synergy boot loop although I'm still on 1.7. I would try to wipe cache and dalvik cache and see if that helps or you could be over clocking to high.
Sent from my Transformer TF101 using xda premium
nguyenvn said:
Was 1.7 r23 supposed to be a really stable release? I read through some of the Synergy thread and didn't see anyone having the issues I had. I felt like I was doing something wrong.
Click to expand...
Click to collapse
I don't know the answer to that specifically. All I know was that I was stable before another modification I made (that said it wouldn't work but I tried it anyway). Since restoring from backup and reloading Synergy and theme I have not seen any weird rebooting anymore.
nguyenvn said:
Would the way I rooted have an effect on the reboots? I used the non flash method by Noxious Ninja.
Click to expand...
Click to collapse
I'm not familiar with that method. I've only used Odin, even when I did have to redo everything I used Odin to stock de-bloated rooted .md5 then CWM'd from there.
So I'm giving it another shot on r50. I made sure to clear dalvik, cache and data. After flashing It gave me the reboot problems again. I installed system tuner to change the cpu back to 1.5. Maybe it's from the overclock but we'll see how it goes. Is everyone leaving it overclocked on 1.9 not having issues?
nguyenvn said:
So I'm giving it another shot on r50. I made sure to clear dalvik, cache and data. After flashing It gave me the reboot problems again. I installed system tuner to change the cpu back to 1.5. Maybe it's from the overclock but we'll see how it goes. Is everyone leaving it overclocked on 1.9 not having issues?
Click to expand...
Click to collapse
That may very well be the issue. 1.9ghz is a very aggressive overclock, and i wouldn't be surprised if was unstable on a good number of phones. Synergy's supposed to boot at 1.5ghz max by default - I don't know whether that was successfully implemented. I personally think it's silly to OC such a capable phone, anyway. Back in the days of the Droid 1, an overclock from the stock 550mhz to 800mhz-900mhz was an enormous improvement. Today, the only thing OCing the S3 gets you is a <10% improvement in Quadrant, more heat, possible instability, and no perceptible difference outside of those silly synthetic benchmarks.
Anyway, in this thread, there seems to be a fair bit of confusion as far as what's what in the android partitions. I'll give you a short rundown.
"aboot" is what's referred to here as the bootloader. It checks to see whether the next partition in the boot sequence, "boot", is authorized. When you unlocked your bootloader, you overwrote aboot with a version that does not perform that check.
"boot" contains your kernel. If your ROM has a custom kernel, it contains a boot.img to overwrite boot.
"system" is the meat of the OS. This is primarily what ROMs flash.
"data" contains all of your apps and settings. When you perform a factory reset, you're reformatting data. If you're flashing a ROM that is significantly different from what you're on now, some of those old settings and data can cause errors, force closes, random reboots, and boot loops. When in doubt, wipe data before flashing a new ROM. When going from one version of a ROM to a newer, very similar version of the same ROM (nightly to nightly), you probably don't need to wipe data, but make a backup just in case. dalvik-cache is also in data; if you wipe data, you've automatically wiped the dalvik cache. It's redundant to wipe data and then wipe dalvik cache.
"cache" is just that, the cache partition. Clearing it won't make you loose anything, at least not anything Android won't silently replace.
So far it seems to be pretty stable on r50. I installed system tuner and brought it down to 1.5 Ghz. I'm not sure why 1.9 is set to default. Doesn't seem like a good idea to me. Thanks all for the help/advice.

Categories

Resources