Related
Okay, so I see there are many people that have the same questions I had yesterday trying to apply this update with a custom ROM already on my phone. Here is what you'll need and how to get your phone updated. This isn't the only way to do it, but it's what I did and it was pretty easy. It was harder finding out how to do all of this, and in what order than actually doing the process.
It will take a little while to do this, roughly 30-45 minutes.
Here are the steps I had to use being on 1.5.7 with GingerBlur:
Here is what you'll need after backing up your apps/files to the SD Card, in this order:
Download RSD Lite 5.0
Download 1.8.3 sbf
Gingerbreak
GladEnable
Tenwar's System Recovery
GreyBlur 2.X (Or insert custom ROM here)
1: Flash the 1.8.3 update on to your phone using RSD Lite, this will reset your phone completely to stock.
2: Run GingerBreak to root the device.
3: At this point I was unable to install Tenwar's, so I used GladEnable to sideload it.
4: Installed Tenwar's and loaded up my custom ROM.
5: Restore your backup.
This should get you all updated and with your custom ROM installed.
Awesome! Thanks man
quick question: how do we make a backup (Ti Backup?) on our current setups? And will restoring the backup we make bring back all apps and settings and everything?
Thanks a lot for this....
spitefulcheerio said:
Awesome! Thanks man
quick question: how do we make a backup (Ti Backup?) on our current setups? And will restoring the backup we make bring back all apps and settings and everything?
Click to expand...
Click to collapse
Yes, use Titanium Backup to backup your User Apps and Data, not the system apps or data. And make sure to backup to your SD Card as the flash with wipe your internal memory and your backup will be lost. I had that issue and had to reinstall all of my apps. It's minor, but still a pain in the ass.
Flashing 1.83 should not wipe anything; as far as apps or info. goes. Some people have had a problem with gingerbreak wiping some things though. I flashed 1.83 and ran ginerbreak with no problems, except for having the bloatware re-installed and loosing my root, but that's to be expected.
Swiftks said:
Flashing 1.83 should not wipe anything; as far as apps or info. goes. Some people have had a problem with gingerbreak wiping some things though. I flashed 1.83 and ran ginerbreak with no problems, except for having the bloatware re-installed and loosing my root, but that's to be expected.
Click to expand...
Click to collapse
When I flashed 1.8.3 through RSD Lite, it completely put everything back to bone stock. It wiped the entire internal memory. So I'm not sure if it should or shouldn't, but it did. I know it wasn't GingerBreak because you flash the update before installing GB.
IrateCustomer said:
When I flashed 1.8.3 through RSD Lite, it completely put everything back to bone stock. It wiped the entire internal memory. So I'm not sure if it should or shouldn't, but it did. I know it wasn't GingerBreak because you flash the update before installing GB.
Click to expand...
Click to collapse
that's weird, b/c when I flashed it, it didn't wipe anything just added the bloat ware back and changed the radio, etc. still had homescreen the same with all my apps, etc.... oh well
Swiftks said:
that's weird, b/c when I flashed it, it didn't wipe anything just added the bloat ware back and changed the radio, etc. still had homescreen the same with all my apps, etc.... oh well
Click to expand...
Click to collapse
Maybe because I was on 1.5.7, and flashed 1.8.3 instead of going back and OTAing the phone. That would make sense because the OTA process probably does a backup/restore during the process. As mentioned in the OP, it's only one way to do it, but there are other options.
the sbf download is sending me to Motorola site,, dont I need the sbf not the exe??
Datblkbro said:
the sbf download is sending me to Motorola site,, dont I need the sbf not the exe??
Click to expand...
Click to collapse
I've updated the link in the OP so you can download the correct file. My apologies.
Regarding 1.8.3 sbf, which of the sfb files from the link you provided is it? They vary in size. Thanks.
You want the one with the most hits and the ridiculously long filename.
It actually has 1.8.3 buried in the name of the file. It's a few from the top.
THANK YOU this has been a big question mark for me ever since 1.83 came out. Fantastic guide.
Swiftks said:
Flashing 1.83 should not wipe anything; as far as apps or info. goes. Some people have had a problem with gingerbreak wiping some things though. I flashed 1.83 and ran ginerbreak with no problems, except for having the bloatware re-installed and loosing my root, but that's to be expected.
Click to expand...
Click to collapse
Did the GingerBlur 3.1 get fixed when it comes to the Webtop mod? Cuz I read something about it having a problem with actually working on this Rom? Maybe that was on the 3.0, so I figure 3.1 fixed it?
PLease just a simple "yes it works" or "No, it doesn't" will suffice
Thanks
Just wanted to post my initial experience with using RSDlite to update afterting and gingerblurring it.
I followed your how to as much as I could (You should provide a link to RSDlite instructions, I had to search for it because I didn't know how to do it exactly... not a big deal but it would make it easier/idiot proof)
When I first updated via RSDlite, something must hve went wrong. At first, A triangle and lil android was haunting me on my screen... so I went to reboot.. **** [I thought I bricked it]... Then I restarted it again... DOUBLE ****... Couldn't load into recovery... I restarted a third time and it loaded up(**** YES). But for some odd reason, it said I still had to update (even though it said the firmware was @ 1.8.3.)
Everything seemed to work fine, and was able too root and ginger blur it. About a few hours later, wifi seemed wonky (kept randomly disconnecting and the update dialog came up every 15 minutes).
I ended up reflashing to 1.2.8 and OTA's all the way up to 1.8.3 and then re-rooted and blurred it. No problems since the full refresh
Hopefully everybody elses experience goes better than mine!
Also, Random question. How do you remove Tenwars System Recovery app after using it to load up a rom?
winky! said:
Also, Random question. How do you remove Tenwars System Recovery app after using it to load up a rom?
Click to expand...
Click to collapse
You can use Uninstaller for Root (I found it on the Market), and you can uninstall from there if you wish. Personally I see no real reason to remove it, but you can if you need to with the above referenced Uninstaller. There are a few others that can do it, but UfR is free, which is clearly a win.
564mb for the sfb??? Thats freaking huge
GreyBlur on 1.8.3
After following the steps I still show
"System Version 4.1.57MB860.ATT.us"
rooted and sideloading enabled by gladroot then flashed greyblur 2.1....little help for the n00b?
My wife has a stock unrooted Vibrant running 2.1, and recently she's started having speed issues and the Youtube app has stopped working, so she's asked me to fix it. I was thinking I'd just root and flash her phone with a 2.2 ROM so she could get some tweaks, rather than just update to stock 2.2. I just had a few questions on the flashing process.
1) When I flash a ROM, do I have to go into CWM and wipe data, cache, and Dalvik, or can I just flash over a stock 2.1 install?
2) Whenever I want to flash a new ROM, do I have to return to stock 2.1, and then re-root?
3) Does returning to stock 2.1 delete the phone's user data?
4) Does flashing a new ROM delete user data?
5) Would updating to stock unrooted 2.2 using the Samsung tool delete the user data?
Also, does anyone have any suggestions on a ROM to flash? I'd probably go to a 2.2 ROM, and I was looking at Trigger 3.2, but I'm open to suggestions.
1) Always do all 3 + fix permissions total of 4 options in CmRecovery
2) Flashing FROYO ROMs is easy and can be done with out the need to ODIN. Its just when flashing 2.3 GB ROMs initially that will require ODIN.
3) Wiping of SD cards is known to have different results, for different users, in different situations, at different times, during different moon phases. LOL. jkjk, but to be honest ALWAYS make a backup! Move the backup from the phone to ur PC or else.
4) Same answer as 3
5) Not sure
6) Its gawd awful hott here!!!
7) Good luck!
Thanks for the quick reply
Also, I agree with 6). I burned myself getting into my car yesterday. Stupid Texas weather....
The AC went out at my werk yesterday, ugh. Back up now but still sittin at 79* even tho I got the thermostat down to 65*
*Tip*
My sisters Vibrant started to crap out last week and I almost shot myself trying to find a ROM with her that she'd like. Eventually I gave up and we went with @Whitehawkx stock 2.2. BOOM! EPIC win/win
It looks like Bionix has a 2.2 ROM that removes the Touchwiz Launcher. My wife currently uses ADW anyways, so that might help speed up her phone a bit and free up some memory for her apps.
I'm thinking about SBFing my rooted x2 back to 2.3.3 from 2.3.4 because of the terrible battery indicator, and was just wondering if I would be able to update straight to 2.3.5 (or possibly ICS) when the update comes. I don't know why this wouldn't be possible, but I just wanted to make sure before I actually SBFed the phone.
I also was wondering if my phone would still be rooted after the SBF because of the maintain-root-through-any-update mod. Any thoughts?
On a different note, if I had the x2 bootstrap, the maintain-root-through-any-update mod, and MyBackup Root, could I just backup all my apps and the system (using MyBackup Root and the bootstrap, respectively), SBF, then restore the phone by downloading the bootstrap and MyBackup Root and restoring my apps/system? Would this get my back to where I was before, or would I have to manually download each one of my apps and lose all previous data that I had on them? I'm just wondering what's the easiest way to restore my phone back to the layout that I had before I SBFed.
Thanks for your answers to any of these 3 questions!!! I definitely appreciate it.
germmeetsworld said:
I'm thinking about SBFing my rooted x2 back to 2.3.3 from 2.3.4 because of the terrible battery indicator, and was just wondering if I would be able to update straight to 2.3.5 (or possibly ICS) when the update comes. I don't know why this wouldn't be possible, but I just wanted to make sure before I actually SBFed the phone.
Click to expand...
Click to collapse
Perhaps someone elses experience proves different however, I kept 2.2.2 on my DX2 for quite some time because of similar reasons. When I decided to take the plunge from 2.2.2 and upgraded to 2.3.4 OTA, my phone needed to first upgrade to 2.3.3 before it would upgrade to 2.3.4. Thus, I had to perform two separate OTA updates.
If you're going to SBF you can SBF directly from your current version to the desired version.
germmeetsworld said:
I also was wondering if my phone would still be rooted after the SBF because of the maintain-root-through-any-update mod. Any thoughts?
Click to expand...
Click to collapse
To be honest, I'm not sure. I personally prefer to SBF to a clean DX2, wiping all settings and cache. To me I treat it like formatting my computer with a clean install of it's OS.
Perhaps someone else will have more insight with the maintain root through updates mod.
germmeetsworld said:
On a different note, if I had the x2 bootstrap, the maintain-root-through-any-update mod, and MyBackup Root, could I just backup all my apps and the system (using MyBackup Root and the bootstrap, respectively), SBF, then restore the phone by downloading the bootstrap and MyBackup Root and restoring my apps/system? Would this get my back to where I was before, or would I have to manually download each one of my apps and lose all previous data that I had on them? I'm just wondering what's the easiest way to restore my phone back to the layout that I had before I SBFed.
Thanks for your answers to any of these 3 questions!!! I definitely appreciate it.
Click to expand...
Click to collapse
What I typically do is using the X2 Bootstrap, I make a Nandroid backup and restore directly from that. Performing an SBF is only going to be necessary if the backup was on a different kernel, otherwise if you may run into boot looping.
What exactly happened and what are you trying to do? Are you trying to restore your phone to an earlier point via SBF? As in you enjoyed the phone on 2.3.3, made a backup and now you're unhappy on 2.3.4 and wish to go back?
It sounds like if you were to SBF back to your desired version (the version you made the backups on) you would then be able to apply your backups and should be back to your desired phone state.
I'm slightly confused to the details due to the way it's worded. I know it's somewhat difficult to describe but that's the basic idea I'm getting. Please feel free to correct me if I'm wrong or fill in the blanks.
Is 2.3.5 much better?
Sent from my DROID X2 using XDA App
Okay so what I did was SBF back to 2.3.3 (I did this two nights ago) and before I did that, I:
1. Renamed the bloatware back to .apk (I had the suffix's ".bak" as an alternate "freezing" method).
2. Used MyBackup Root to make a backup of all my apps+their data.
3. Made a backup of the phone using the bootstrap.
4. SBFed
5. Rooted
6. Downloaded MyBackup Root
7. Restored all my apps and data and it worked!!!
8. Celebrated! I had no faith in it working but all my apps are back! I was so impressed, I was expecting to have to redo all my games and everything. MyBackup Root is such a sweet app, or I'm just a loser.
I hoped this helped other people, I had no idea what was gonna happen, no one's ever told me how to specifically get my phone back to the layout that I wanted.
and related to reaktor's post, what I was doing was SBFing back to my desired state of 2.3.3, just because I hate the battery glitch on 2.3.4. It had nothing to do with any apps I had, sorry for the confusion.
Your last reply was a little off but that was my fault, I'm sorry for my wording haha. I just have never known how to NOT have to redownload all my apps and start over on my games' data once I restore/SBF a phone. Now I know.
BTW my phone didn't maintain its root, just for reference for others. I had to reroot.
Well... You might want to do that again. There's now a battery fix for 2.3.4 and 2.3.5 in the dev forum.
Pepperm1nt's battery fix thread @ http://forum.xda-developers.com/showthread.php?t=1350336
It works great
Greatttttt haha all that fer nuthin. I may update again, or I just might wait til I get bored with the phone again to install this. Thanks a bunch for the link though!
Sent from my DROID X2 using XDA Premium App
The battery fix works great. Just flash it over stock or any custom rom. It works perfect!
I have my phone rooted and BSR/busybox/superuser installed. How do I flash it and actually put the rom on the phone?
(P.S. Its eclipse 2.1)
Well you have a lot of reading to do but let me give you a few important tips:
1) Before doing anything else make sure to go into your BSR and make a nano back up of your stock system. If you do not know how to do nano back ups then read up on that. You will be doing that for different roms. http://forum.xda-developers.com/showthread.php?t=1318083
2) Make sureyour kernal matches the version of the rom. For example you want to flash eclipse 2.0+ this is made for 2.3.5 update. If you are stock you are probably 2.3.4 Some have flashed eclipse 2.0+ and had no issues but it is not recommended.http://forum.xda-developers.com/showthread.php?t=1313103
this thread should help you out a lot also.
3) Once you get your stock Rom backed download the rom of your choice onto your sd card. Go back into BSR and first wipe data factory reset, wipe partion cache, go into advance and wipe Dalvik cache. Once you wiped the big 3 go to install from sd. Locate the rom using your volume buttons and power button to select. Sit back and let the rom run. Once it is done you can reboot now or flash one more safety step. It is the rerecovery zip. This actually allows you to restore your phone easy in the case of something bad happens. If you boot loop or something goes wrong then you just pull your battery and give it about 30 seconds. Put the battery back in and leave the phone off and just plug it into the wall charger. This will bring you straight to BSR. Here is that link http://forum.xda-developers.com/showthread.php?t=1426062
Also remember as long as you can get into BSR you can restore your nano backup of choice. Good luck and have fun. If you run into trouble we can help you out. The phone is pretty easy to fix.
I have made my recovery but was told it is ok to install Eclipse 2.1 on 2.3.4. I have the file downloaded but am I going to have to reprogram my phone for service?
If I'm not mistaken, flashing eclipse 2.1 on Android 2.3.4 can cause some Wi-Fi and data problems, so I highly recommend sbf-ing android 2.3.5 before flashing eclipse. Ill link a comprehensive sbf guide at the end of this post. To answer your question, though, you shouldn't have to activate your phone again if you havent sbf-ed or updated android. If you do decide to use 2.3.5, you will have to activate your phone again, though it only takes about 30 seconds in my area (could take more or less time depending on your signal strength).
http://forum.xda-developers.com/showthread.php?t=1317707
Hope I could be of assistance. If you need help, feel free to ask. I have no life so ill be here all day.
theredvendetta said:
If I'm not mistaken, flashing eclipse 2.1 on Android 2.3.4 can cause some Wi-Fi and data problems, so I highly recommend sbf-ing android 2.3.5 before flashing eclipse. Ill link a comprehensive sbf guide at the end of this post. To answer your question, though, you shouldn't have to activate your phone again if you havent sbf-ed or updated android. If you do decide to use 2.3.5, you will have to activate your phone again, though it only takes about 30 seconds in my area (could take more or less time depending on your signal strength).
http://forum.xda-developers.com/showthread.php?t=1317707
Hope I could be of assistance. If you need help, feel free to ask. I have no life so ill be here all day.
Click to expand...
Click to collapse
I have managed to softbrick my phone. No it is stuck on the "dual core technology" screen and I can't do anything
Spanks906 said:
I have managed to softbrick my phone. No it is stuck on the "dual core technology" screen and I can't do anything
Click to expand...
Click to collapse
Have you pulled you battery and tried it again? If you have I'd sbf back to 2.3.4 and then update to 2.3.5 then root it, and then install BSR and go into recovery and like said above, wipe the "big 3," install the ROM and then reboot and see if that helps.
Spanks906 said:
I have managed to softbrick my phone. No it is stuck on the "dual core technology" screen and I can't do anything
Click to expand...
Click to collapse
I tried installing it just now... It gets past the dual core but sticks on the ECLIPSE loading screen... wtf? any idea how to load the original os?
GaryMcDroid said:
I tried installing it just now... It gets past the dual core but sticks on the ECLIPSE loading screen... wtf? any idea how to load the original os?
Click to expand...
Click to collapse
Sbf back to 2.3.4....its not too hard. Search for it.
Sent from my MB870 using xda premium
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: