Related
This is my second time trying to restore a backup using clockwork and it just hangs on the vibrant screen. The first time I forgot to disable voodoo so that was the problem then, but this time I was on obsidian froyo rom and had issues where I was not able to get any data reception (3g/edge) so I figured to try and got back to stock to see if that solved the issue but no I'm stuck on vibrant screen. It went through the process of restoring then rebooting but it got suck. I am very frustrated because I can't never get it to work so what is the point of backing up stuff. I will be using odin again to restore and not use backups anymore. Just wanted to vent as I am very frustrated about this. If there is some out there that could shed some light as to why I keep getting stuck on the vibrant screen I would appreciate it.
Will be getting a replacement phone from my date issue, and yes my voice still works just not data part.
Sent from my T-Mobile G1 using XDA App
Froyo has a differnt kernel than eclair. You were trying to restore an eclair build, but you did not flash the stock eclair kernel first.
s15274n said:
Froyo has a differnt kernel than eclair. You were trying to restore an eclair build, but you did not flash the stock eclair kernel first.
Click to expand...
Click to collapse
what eclair kernel can i use for the future???
i odin back to JFD and my 3g/edge is working again i wonder why i lost it?
Probably the easiest thing to do would have been to flash a new custom rom with the kernel included, like Fusion/Bionix.
You could have flashed the stock kernel and then restored a JI6 nandroid too though I imagine. I've not tried yet. The stock kernel can be found in my signature or in the development section. I have a copy on my internal memory just in case.
So i'm pretty noob with all this stuff but i finally decided to try flashing my phone and, in the end, ended up with a "bricked" (or the extent a vibrant can be bricked) phone. Thanks in advance for the advice.
what i did
I followed the flashing guide in the sticky post "** GUIDE - TIPS - TRICKS ** Last Update 12/03/10 ** READ BEFORE ASKING" and everything worked great. I downloaded Rom manager, made a nandroid backup of my stock rom, flashed it with bionix fusion and everything worked great. I didn't do the titanium backup and there was an app that i needed to use the next day so on the way to work, i decided to restore back to the stock thinking that i could go back for the day, use the apps that i needed and when i got home got home, back up my apps with titanium back up and restore again back to the bionix fusion. So i did that. I went to rom manager and I first backed up my bionix fusion rom and then tried to recover my stock rom. When the phone restarted, it didn't go past the vibrant/samsung screen.
The question...
what went wrong? based on some reading i think it has something to do with the kernel but i'm not really sure.
but the real question is, how do i avoid from this happening again? did i do the recovery wrong? what's the best way to unbrick my phone back to stock without losing any data on the phone. is it possible????
at this point, i can go into download mode. what should be my next move?
Thank you again if you can provide any insight.
*edit*
So looking at some posts, I looks like I need to flash the stock kernel. can anyone tell me how to flash just the kernel using odin? I've never used it and I can't seem to find anything on flashing just the kernel. Thank you.
Problem SOLVED!
ok. not completely solved T_T.
What i've done.
I've flashed back to stock vibrant firmware and that works fine. When i try to restore my nandroid backup, and it reboots, I get stuck back to the same place i was. I made two nandroid backups and tried them both but neither of them work. am i doing it wrong? I have even re-rooted my vibrant and downloaded rom manager again and tried it through there and still get the problem. have tried it about 4 times now with no luck.
Again, any help is appreciated.
Nandroid doesnt replace the kernal
Sent from my SGH-T959 using XDA App
Exactly, nandroid doesn't replace the kernel. If you want to run a nandroid restore, you have to either flash the rom the nandroid was created on, then restore (safest imho), or flash a compatible kernel for the rom from which your nandroid was created, then run your nandroid restore.
Sent from my Vibrant running Macnut R13 w/JK6 Modem and Black Froyo
Pretty sure this was in the sticky too
I had zero problems when rooting and flashing my G1, but now with my Vibrant I am not sure what I did.
A few excellent stickies at the top but I seem to not be making any progress.
Here are the steps I took.
I had a stock Vibrant running 2.1
I downloaded ROM Manager, installed clockwork mod.
Did a backup of my current system ( was I supposed to do a clockwork AND nandroid?)
Downloaded and successfully installed a ROM called Blackhole 1.0
it runs ok but didn't give me the option to switch from 3G to EDGE data, and then I couldn't get internet access at all so i decided to restore my original stock vibrant system.
So I rebooted into recovery, selected restore (my phone won't go into recovery anymore for some reason) and waited, it took a while, then I rebooted (forgot to wipe), but it just got stuck on the Vibrant screen. So I booted into recovery mode again and wiped just user data not cache and rebooted, same thing stuck at Vibrant.
Now i keep hearing about something called ODIN, what I can tell it is some kind of flasher program for ROMS, nobody seems to give any kind of link or anything, is it greymarket or something?
So where am I now? I think the excellent noob guide needs to be updated a bit more.
My phone can get into download mode (whatever it is for i don't know) but it won't get into recovery mode anymore.
Everything you need is here: http://forum.xda-developers.com/showthread.php?t=771111
i think what happened to you is you flashed a 2.2 ROM then tried to revert back to 2.1 without doing the proper downgrading steps i.e. you did not flash a 2.1 kernel first.
but since you can get to download mode.. just flash stock JFD or JI6 through ODIN and you should be good.
good luck
Once you get back to stock don't give up on the 2.2 toms. Try axura or nero. They might have a few minor bugs but its way better then stock 2.1.
Powered by Axura with a dash of Voodoo
I have done the samething as you, coming from a nexus one it seemed easier to flash roms without worrying about downgrading kernels or what not. Recently I was on Nero froyo and flashed to a different rom, and tried to revert back but ended up stuck at the vibrant screen. Think it has something to do with voodoo lag.
Anyways I had to use Odin with the no brick froyo off ebproductions. Ran that and uploaded clockwork, reinstalled voodoo lag fix and was able to nandroid back to my Nero set up. Somewhat of a pain but once you've done it, no need to worry about bricking
xtone said:
Everything you need is here: http://forum.xda-developers.com/showthread.php?t=771111
i think what happened to you is you flashed a 2.2 ROM then tried to revert back to 2.1 without doing the proper downgrading steps i.e. you did not flash a 2.1 kernel first.
but since you can get to download mode.. just flash stock JFD or JI6 through ODIN and you should be good.
good luck
Click to expand...
Click to collapse
So the steps that are in this page?
http://forum.xda-developers.com/showthread.php?t=734475
GreggoryD502 said:
Once you get back to stock don't give up on the 2.2 toms. Try axura or nero. They might have a few minor bugs but its way better then stock 2.1.
Powered by Axura with a dash of Voodoo
Click to expand...
Click to collapse
Well as long as I can use Odin if I f-up royally like above then I might give it a shot.
Need to read about downgrading kernals or whatever. Might just wait for Cyanogen 6.1
Just so you know, the backup utility in Rom Manager (clockwork) is really just shortcut to a nandroid backup.
The way I have things set up for backups, and this is just for my personal convenience, is as follows...
I have a stock JFD ODIN rom to flash in case anything goes wrong. (A lot of people here will tell you to flash this whenever flashing a new rom. It is safer, and cleaner to do it this way, but not absolutely necessary)
I make a nandroid of my last stable rom (I only keep one at a time cause the files are huge) and keep a backup of that on my PC.
I backup all my apps and a few other things (call logs, bookmarks, sms) through Titanium backup. If you get the pro version, you can load it up after flashing a new rom and have it automatically restore all your apps in one click (system settings can be dangerous to restore when going from rom to rom, so be careful with those.) I also keep a backup of this on my PC.
I will also occasionally backup both of the sd cards to the PC.
Maybe overkill, but you probably wont ever lose anything forever.
thegreatcity said:
Just so you know, the backup utility in Rom Manager (clockwork) is really just shortcut to a nandroid backup.
The way I have things set up for backups, and this is just for my personal convenience, is as follows...
I have a stock JFD ODIN rom to flash in case anything goes wrong. (A lot of people here will tell you to flash this whenever flashing a new rom. It is safer, and cleaner to do it this way, but not absolutely necessary)
I make a nandroid of my last stable rom (I only keep one at a time cause the files are huge) and keep a backup of that on my PC.
I backup all my apps and a few other things (call logs, bookmarks, sms) through Titanium backup. If you get the pro version, you can load it up after flashing a new rom and have it automatically restore all your apps in one click (system settings can be dangerous to restore when going from rom to rom, so be careful with those.) I also keep a backup of this on my PC.
I will also occasionally backup both of the sd cards to the PC.
Maybe overkill, but you probably wont ever lose anything forever.
Click to expand...
Click to collapse
OK I will just do the long way from now on. I use this phone on AT&T, I was worried that I flushed $500 down the toilet but ever since i modded my first phone way back in the day i've been addicted.
Running Odin and my phone is in download mode, about to flash this b**ch.
wish me luck.
I flashed Odin on my phone to revert to stock. Re-Rooted it but now I can't flash Clockworkmod. Please help D:
use the update.zip posted here. You want B.
Hi, all. Relative noob here. Fascinate, Stock ED04 OTA, Rooted, modified stock kernel to "stick" CWM, Bloat frozen using TB.
I want to take the next step of flashing a ROM, and am doing (I feel) due dilligence by reading everything possible in this forum. However, I think I'm starting to suffer from information overload, and confusion has set in.
I used Odin to flash CWM 3.0.2.8x.ti. Immediately after selecting backup and restore/backup, I get "Error while backing up boot image". I see a few posts with the same statement, but no resolution. Flashed back to CWM 2.5; and backup appears to complete successfully. However, the date of the backup is 2000-01-01; and this is consistent on repeated attempts. The time and date on my phone (when booted) is correct.
Am I missing something? Any help would be greatly appreciated.
dhartman977 said:
Hi, all. Relative noob here. Fascinate, Stock ED04 OTA, Rooted, modified stock kernel to "stick" CWM, Bloat frozen using TB.
I want to take the next step of flashing a ROM, and am doing (I feel) due dilligence by reading everything possible in this forum. However, I think I'm starting to suffer from information overload, and confusion has set in.
I used Odin to flash CWM 3.0.2.8x.ti. Immediately after selecting backup and restore/backup, I get "Error while backing up boot image". I see a few posts with the same statement, but no resolution. Flashed back to CWM 2.5; and backup appears to complete successfully. However, the date of the backup is 2000-01-01; and this is consistent on repeated attempts. The time and date on my phone (when booted) is correct.
Am I missing something? Any help would be greatly appreciated.
Click to expand...
Click to collapse
i have had the same thing happen every time i try and backup. I'm wondering if it has anything to do with the newer recovery b.c when i had 2.5 i had no issues with it. Anybody have an answer for this?
I was in the same boat as you: rooted and bloat frozen via TB since the first week, and just added the modified kernel with CWM 3 earlier this past week. Haven't had any problems with it. I used Heimdall to flash CWM and the kernel. Now I'm running Evil Fascination with the LG Alternate Launcher. Tried ComRom but didn't care for it, though the default wallpaper was very pretty.
Back to the point, after I flashed the kernel and CWM I restarted the phone, let it boot, then rebooted into recovery to backup, instead of unplugging it and immediately booting Recovery.
Honestly, you've made it this far, you want to get a new ROM, I say download one and follow the directions (read them three times top-to-bottom) before flashing, and you should be good.
Yeah - I think Evil is where I want to end up until CM7 is fully functional (just spent all morning reading the CM7 waiting room thread).
Unfortunately, I'm apprehensive about flashing a new ROM until I can get a good backup image. I'm not sure why I'm getting the erroneous date on the backups. I could certainly be doing something wrong; just not sure what (if anything).
Maybe I need to use a different CWM? 2.5.1 and 3.0.2.8. don't seem to have worked for me. Also, If I understand what eulipion2 said, I have already fully booted, then powered down and rebooted into CWM to do a backup. 3.0.2.8 fails and 2.5.1 gives be incorrect dates.
Going to do a few hours of reading on CWM, I guess!
I'm using the first kernel listed in this thread from times_infinity. I initially flashed ComRom, didn't like it, kept this recovery, and flashed EF. Works great so far.
Give the Nandroid a go with this Recovery and see if it works for you.
hey i figured out how to get the back up to work. you have to enable voodoo and then it will work
Hey guys. Thanks for the suggestions. Tried the CWM 3 link from above, still no dice. I suspect I may need to have a voodoo kernel installed to actually enable the voodoo and try the backup again. Makes sense I guess.
Getting frustrated.
Success! Flashed a voodoo kernel, and was able to get (what appears to be) a successful nandroid backup with 3.0.2.8 (red). Never did get 2.5.1 (yellow) working. Strange, but irrelevant. CM7 build 7 is looking like it's ready for a test drive.
Hello everyone. I'm a noob.
I have a Droid X2 and Verizon service. It was running Gingerbread 2.3.5 and version 1.3.418, and up until yesterday I hadn't even rooted it. I followed these instructions for CM10 carefully but apparently made a slight mistake.
I made sure to root properly: Superuser worked perfectly, I had Busybox, NANDroid, and Bootstrap Recovery all working, and the phone worked just like before.
In the tutorial I linked to above, I think I know where I went wrong. I downloaded GAPPS 4.2.2 (funky wording since he said 'latest' and then '4.1.x' , so not the latest) and then CM10 A3. I then went into BSR and installed from the external SD card. GAPPS succeeded, but CM10 did not (Status 7, some kernel disapproval or something). When I booted the phone after that, MultiTouch keyboard couldn't start and so I just froze it with Titanium Backup and used Swype because it was annoying. The next thing I tried came from another xda thread (that I seem to have misplaced) saying that removing the top 2 lines of META-INF/com/google/android/updater-script would make it work. I'm pretty sure this failed similarly to before. I then tried wiping all data (since I had backed it up 3 different ways) and installing CM10. It still didn't work, and when I booted I got to my current state of purgatory.
Now when I boot, it tries to run the initial setup but that crashes (and multitouch keyboard crashes too). I've probably lost root access and currently don't have Titanium Backup or any other method to restore from backup since the programs were wiped. I've been trying to do an SBK factory reset using RSD Lite, but the phone won't go into RSD mode.
At this point I just want a working phone again and I'm not sure what to do.
TL;DR: Used the wrong GAPPS version when installing CM10 A3, decided to wipe all my data and try the install, now I'm stuck in neutral.
I guess the internet lied and gave me the wrong SBK the first time. Setup did work, and it wasn't RSD like I had thought.
I still would like to know what went wrong the first time through, and why it seemed like I wasn't able to overwrite the incorrect GAPPS version I had first installed. Once I saw my mistake I did use the correct version and nothing changed.
Dasoccerguy said:
I guess the internet lied and gave me the wrong SBK the first time. Setup did work, and it wasn't RSD like I had thought.
I still would like to know what went wrong the first time through, and why it seemed like I wasn't able to overwrite the incorrect GAPPS version I had first installed. Once I saw my mistake I did use the correct version and nothing changed.
Click to expand...
Click to collapse
Did you get it working then? Were you running A2 before hand?
Dasoccerguy said:
Hello everyone. I'm a noob.
I have a Droid X2 and Verizon service. It was running Gingerbread 2.3.5 and version 1.3.418, and up until yesterday I hadn't even rooted it. I followed these instructions for CM10 carefully but apparently made a slight mistake.
I made sure to root properly: Superuser worked perfectly, I had Busybox, NANDroid, and Bootstrap Recovery all working, and the phone worked just like before.
In the tutorial I linked to above, I think I know where I went wrong. I downloaded GAPPS 4.2.2 (funky wording since he said 'latest' and then '4.1.x' , so not the latest) and then CM10 A3. I then went into BSR and installed from the external SD card. GAPPS succeeded, but CM10 did not (Status 7, some kernel disapproval or something). When I booted the phone after that, MultiTouch keyboard couldn't start and so I just froze it with Titanium Backup and used Swype because it was annoying. The next thing I tried came from another xda thread (that I seem to have misplaced) saying that removing the top 2 lines of META-INF/com/google/android/updater-script would make it work. I'm pretty sure this failed similarly to before. I then tried wiping all data (since I had backed it up 3 different ways) and installing CM10. It still didn't work, and when I booted I got to my current state of purgatory.
Now when I boot, it tries to run the initial setup but that crashes (and multitouch keyboard crashes too). I've probably lost root access and currently don't have Titanium Backup or any other method to restore from backup since the programs were wiped. I've been trying to do an SBK factory reset using RSD Lite, but the phone won't go into RSD mode.
At this point I just want a working phone again and I'm not sure what to do.
TL;DR: Used the wrong GAPPS version when installing CM10 A3, decided to wipe all my data and try the install, now I'm stuck in neutral.
Click to expand...
Click to collapse
you state in the beginning that you are on 2.3.5. it is crazy that you were even able to flash cm10. it is made for 2.3.4 . and DZKs OP on cm10 is a bit sketchy in the wording and severly outdated.
there are a few things you need to do in order to get BSR working inside of A3 , as well as needing the GAPPS for 4.1.X and not 4.2.2 this is only cm10 , not 10.1 .
you need to SBF back to 2.3.4 (google EZsbf for droid x2) it is way easier than trying to use rsdlite for a "noob" , and then root. then follow the steps you completed to get where you are now, except use the right gapps.
THEN: (this is not in the OP for cm10 ) , perform THIS : http://forum.xda-developers.com/showpost.php?p=37698274&postcount=1573 in order to get the patched cm7 bootstrap working. DO NOT try to use the regular BSR .
i can try to help as i get back to my computer here and there, but hopefully others pitch in , as i dont have that much time. hope this helped.
Simpsons11 said:
Did you get it working then? Were you running A2 before hand?
Click to expand...
Click to collapse
I got back to 2.3.5 and restored all my apps and data, so I called it a night. Well... the sun had come up, but same idea. Like I said, up until yesterday I had yet to even root the phone, so I was just running the stock version of Android given to me by Verizon.
Lorenzo VonMatterhorn said:
you state in the beginning that you are on 2.3.5. it is crazy that you were even able to flash cm10. it is made for 2.3.4 . and DZKs OP on cm10 is a bit sketchy in the wording and severly outdated.
there are a few things you need to do in order to get BSR working inside of A3 , as well as needing the GAPPS for 4.1.X and not 4.2.2 this is only cm10 , not 10.1 .
you need to SBF back to 2.3.4 (google EZsbf for droid x2) it is way easier than trying to use rsdlite for a "noob" , and then root. then follow the steps you completed to get where you are now, except use the right gapps.
THEN: (this is not in the OP for cm10 ) , perform THIS : http://forum.xda-developers.com/showpost.php?p=37698274&postcount=1573 in order to get the patched cm7 bootstrap working. DO NOT try to use the regular BSR .
i can try to help as i get back to my computer here and there, but hopefully others pitch in , as i dont have that much time. hope this helped.
Click to expand...
Click to collapse
I wasn't able to flash CM10. I was able to flash GAPPS 4.2.2, but then unable to flash GAPPS 4.1.x over that installation.
And is it really that outdated and sketchy? The version of CM10 I was trying to flash was made on January 11, 2013. Correct me if I'm wrong, but Gingerbread 2.3.5 is almost 2 years old now, right? It's surprising that I'd have to go back to the previous version.
I may try out your suggestions later, but 8 hours of fiddling with my phone yesterday wore me out a little (a lot). Thanks!
Dasoccerguy said:
I got back to 2.3.5 and restored all my apps and data, so I called it a night. Well... the sun had come up, but same idea. Like I said, up until yesterday I had yet to even root the phone, so I was just running the stock version of Android given to me by Verizon.
I wasn't able to flash CM10. I was able to flash GAPPS 4.2.2, but then unable to flash GAPPS 4.1.x over that installation.
And is it really that outdated and sketchy? The version of CM10 I was trying to flash was made on January 11, 2013. Correct me if I'm wrong, but Gingerbread 2.3.5 is almost 2 years old now, right? It's surprising that I'd have to go back to the previous version.
I may try out your suggestions later, but 8 hours of fiddling with my phone yesterday wore me out a little (a lot). Thanks!
Click to expand...
Click to collapse
the OP for cm10 hasnt really been updated since alpha 1 . so yeah it is outdated. alpha 2 had a non working wifi module that was never even mentioned in the OP and had to be figured out by the droid x2 community. alpha 3 had the working wifi back in, but did not have the proper Hijack.zip in place in the system files, whereas the old versions did. this was also never mentioned in the OP.
watch this video. it may help.
http://www.youtube.com/watch?v=HJdvyufvYp0
the dude who made this video also has DOZENS of how-to videos for the droid x2 on his channel. just search for it on youtube. (ex: how to sbf droid x2)
sbfing your phone to 2.3.4 , using EZSBF , shouldnt take more than 15 minutes.
2.3.5 re-introduced a lot of issues that we had with 2.3.4, so most devs base their roms around 2.3.4. in fact, there are really only two roms for 2.3.5 worth trying out, Eclipse, and gingerbread phone , 7 and they are both gingerbread. :crying:
if you read up on what needs to be done, the whole process of SBF, ROOT, and flash cm10 THEN gapps, should all take less than an hour, even for someone who is fairly inexperienced.
i wasnt trying to dog DZK's post for cm10. i was only stating that if you follow HIS instructions, it is confusing as hell.
Lorenzo VonMatterhorn said:
the OP for cm10 hasnt really been updated since alpha 1 . so yeah it is outdated. alpha 2 had a non working wifi module that was never even mentioned in the OP and had to be figured out by the droid x2 community. alpha 3 had the working wifi back in, but did not have the proper Hijack.zip in place in the system files, whereas the old versions did. this was also never mentioned in the OP.
watch this video. it may help.
youtubelink
the dude who made this video also has DOZENS of how-to videos for the droid x2 on his channel. just search for it on youtube. (ex: how to sbf droid x2)
sbfing your phone to 2.3.4 , using EZSBF , shouldnt take more than 15 minutes.
2.3.5 re-introduced a lot of issues that we had with 2.3.4, so most devs base their roms around 2.3.4. in fact, there are really only two roms for 2.3.5 worth trying out, Eclipse, and gingerbread phone , 7 and they are both gingerbread. :crying:
if you read up on what needs to be done, the whole process of SBF, ROOT, and flash cm10 THEN gapps, should all take less than an hour, even for someone who is fairly inexperienced.
i wasnt trying to dog DZK's post for cm10. i was only stating that if you follow HIS instructions, it is confusing as hell.
Click to expand...
Click to collapse
Thanks for the link. I remember watching one of his videos yesterday for something, but apparently this was the one I needed! He does have another video on how to SBF back to 2.3.4, so I think I will just go for it right now.
Also yesterday it only took so long because I had to figure out what mess I had gotten myself into before I could figure out how to figure out what to do. This definitely looks like it shouldn't take more than an hour. :good:
I do have one quick question about backups. NANDroid is a full system backup, including the OS, right? And Titanium Backup is for apps and data? Therefore I should be able to restore all of my apps and data into Android 4.2.1 with Titanium, right? I at least know how to get back to 2.3.5 and restore my data if I can't restore it in 4.2.1, but I'd rather not have to go through this process again if I find out that Titanium can't restore everything.
(haha... I couldn't quote you because of the outside link and my 'xda noob' status )
Dasoccerguy said:
Thanks for the link. I remember watching one of his videos yesterday for something, but apparently this was the one I needed! He does have another video on how to SBF back to 2.3.4, so I think I will just go for it right now.
Also yesterday it only took so long because I had to figure out what mess I had gotten myself into before I could figure out how to figure out what to do. This definitely looks like it shouldn't take more than an hour. :good:
I do have one quick question about backups. NANDroid is a full system backup, including the OS, right? And Titanium Backup is for apps and data? Therefore I should be able to restore all of my apps and data into Android 4.2.1 with Titanium, right? I at least know how to get back to 2.3.5 and restore my data if I can't restore it in 4.2.1, but I'd rather not have to go through this process again if I find out that Titanium can't restore everything.
(haha... I couldn't quote you because of the outside link and my 'xda noob' status )
Click to expand...
Click to collapse
a nandroid backs up the OS as well as all apps and data, but that only helps you if you are modding/messing with that specific rom. so yes, TB is the way to go for restoring apps across roms. glad to point you in the right direction! report back once youve made the jump. :fingers-crossed:
Success!
I used Tomsgt123's tutorials and they were fantastic. First I had to install the 2.3.4 SBK and then CM10 and Gapps. I'm currently running Titanium Backup and it's working flawlessly.
I did have one hiccup earlier though. I noticed that my contacts weren't backed up, and apparently I had disabled the online contact backup also. I was hoping that I could do a NANDroid restore, backup my contacts, and then go through with the CyanogenMod installation. But, the restore kept hanging and refused to finish. I tried 3 or 4 times, and on the last try I restored by section and it was the data section that caused the hang.
So, I'll have to rebuild my contacts list a little bit, but since SMS was backed up I'll at least get the people I care about . Cyanogen is pretty sleek and so far it's been noticeably faster than Gingerbread. I was constantly getting a low framerate just navigating my mainscreen before, and that's one of the reasons I was inspired to try out Jellybean or just anything newer. I can't make any claims about battery life yet since I haven't unplugged it, but other reviews said the battery can last more than twice as long which is fantastic.
I can't thank you enough, Lorenzo, for pointing me in the right direction. :highfive:
Dasoccerguy said:
Success!
I used Tomsgt123's tutorials and they were fantastic. First I had to install the 2.3.4 SBK and then CM10 and Gapps. I'm currently running Titanium Backup and it's working flawlessly.
I did have one hiccup earlier though. I noticed that my contacts weren't backed up, and apparently I had disabled the online contact backup also. I was hoping that I could do a NANDroid restore, backup my contacts, and then go through with the CyanogenMod installation. But, the restore kept hanging and refused to finish. I tried 3 or 4 times, and on the last try I restored by section and it was the data section that caused the hang.
So, I'll have to rebuild my contacts list a little bit, but since SMS was backed up I'll at least get the people I care about . Cyanogen is pretty sleek and so far it's been noticeably faster than Gingerbread. I was constantly getting a low framerate just navigating my mainscreen before, and that's one of the reasons I was inspired to try out Jellybean or just anything newer. I can't make any claims about battery life yet since I haven't unplugged it, but other reviews said the battery can last more than twice as long which is fantastic.
I can't thank you enough, Lorenzo, for pointing me in the right direction. :highfive:
Click to expand...
Click to collapse
thats awesome. i loved the feeling when i first flashed a new rom on this phone. glad you got it figured out. make sure to thank Tomsgt for his videos as well . hes a cool dude and put a lot of time into it.
as for battery life, its kinda a bit rough on cm10. i wouldnt say twice as good. that would be too good to be true...lol . but if you limit your apps, it shouldnt be that much worse.
one thing, to improve performance, under settings, go to developer options, and near the bottom there is background processes. its set at standard limit by default. change it to three at most. this will make a noticeable improvement in performance, but will also need to be re-set at 3 at most if you ever reboot/power off.
glad i could help! :highfive: