So I am running liberty rom, and every time i boot up my phone rom toolbox force closes, I would love to get the full version if it the x2 was supported, but since I am running liberty rom can I uninstall this app with no ill effects?
You shouldnt use Rom Toolbox with the DX2. Even if it is made to work with Liberty. The reason being is that with our phones, the bootloader is locked. Rom Toolbox allows you to do stuff that our phone doesnt support due to the locked bootloader. Trying to use it for certain stuff can mess up your phone.
---------- Post added at 09:48 AM ---------- Previous post was at 09:44 AM ----------
I think I misunderstood the question. You should be able to remove it. The ROM doesnt depend on it to run. If it is installed as a system app (I dont remember if it is) you might have to take certain steps to remove it.
jsgraphicart said:
You shouldnt use Rom Toolbox with the DX2. Even if it is made to work with Liberty. The reason being is that with our phones, the bootloader is locked. Rom Toolbox allows you to do stuff that our phone doesnt support due to the locked bootloader. Trying to use it for certain stuff can mess up your phone.
---------- Post added at 09:48 AM ---------- Previous post was at 09:44 AM ----------
I think I misunderstood the question. You should be able to remove it. The ROM doesnt depend on it to run. If it is installed as a system app (I dont remember if it is) you might have to take certain steps to remove it.
Click to expand...
Click to collapse
Got it, I was thinking since the rom and toolbox were developed by the same person the ROM actually needed the toolbox to run. I will be un-installing it now. Now that I have finally rooted and flashed a new rom I am starting to see how much of a ***** it is to have a locked bootloader. I will be so glad in 6 months when I can dump this POS!!!! Thankfully Liberty was out for dx2, otherwise I may have already smashed this paperweight.
ziggityz said:
Got it, I was thinking since the rom and toolbox were developed by the same person the ROM actually needed the toolbox to run. I will be un-installing it now. Now that I have finally rooted and flashed a new rom I am starting to see how much of a ***** it is to have a locked bootloader. I will be so glad in 6 months when I can dump this POS!!!! Thankfully Liberty was out for dx2, otherwise I may have already smashed this paperweight.
Click to expand...
Click to collapse
Have you tried the other ROMS available? No offense to the developer but Liberty isnt one of the best ROMS for our phone.
jsgraphicart said:
Have you tried the other ROMS available? No offense to the developer but Liberty isnt one of the best ROMS for our phone.
Click to expand...
Click to collapse
I've tried the cyanogenmod port, just too buggy for me, the sd flip was a major turn off, in order to try eclipse I'd have to sbf, reroot with pete's update to the ota and spend another 2 weeks getting my phone back to where it is now on a new rom. Other than that I have not tried any other x2 roms, I'm running 2.3.4
ziggityz said:
I've tried the cyanogenmod port, just too buggy for me, the sd flip was a major turn off, in order to try eclipse I'd have to sbf, reroot with pete's update to the ota and spend another 2 weeks getting my phone back to where it is now on a new rom. Other than that I have not tried any other x2 roms, I'm running 2.3.4
Click to expand...
Click to collapse
I'm running the latest CM7 ROM and I dont find it buggy. If you think about it, stock 2.3.4 itself is buggy. lol. And if you dont like the flip flop mod, you can always reverse it back. I don't know, to me, CM7 has been the least buggy. And I have never liked that Eclipse was moving onto 2.3.5 either. I tried it and it is nice. I just ended up going back to CM7.
I also found the wifi turned itself off periodically, so i can rename the internal sd back to sdcard and the sd card back to sdcard-ext??
I also had trouble restoring apps via titanium backup, they would say restoring and just hang and hang.
ziggityz said:
I also found the wifi turned itself off periodically, so i can rename the internal sd back to sdcard and the sd card back to sdcard-ext??
I also had trouble restoring apps via titanium backup, they would say restoring and just hang and hang.
Click to expand...
Click to collapse
Did you use the last update to CM7? I think some of that stuff is fixed. But I use llama profiles which allows me to connect to my wifi automatically when I'm in the location. And stay connected until I leave the area. I think this has caused me to not ever have wifi problems. I have had problems with Titanium Backup before. But I think it was when I was playing with the superSU app that came out a while ago. I cant really remember having problems when I flashed the new version of CM7. And with the sd card flip flop, I think you can install CM7 which will have the flip flop mod, then use the file located in this thread here to flip it back:
http://forum.xda-developers.com/showthread.php?t=1229294
jsgraphicart said:
Did you use the last update to CM7? I think some of that stuff is fixed. But I use llama profiles which allows me to connect to my wifi automatically when I'm in the location. And stay connected until I leave the area. I think this has caused me to not ever have wifi problems. I have had problems with Titanium Backup before. But I think it was when I was playing with the superSU app that came out a while ago. I cant really remember having problems when I flashed the new version of CM7. And with the sd card flip flop, I think you can install CM7 which will have the flip flop mod, then use the file located in this thread here to flip it back:
http://forum.xda-developers.com/showthread.php?t=1229294
Click to expand...
Click to collapse
thanks! I think Ill backup and try to flash the updated cm7 and give it a spin!
Related
Although I only had the phone for a day now, I've been reading the forum for a month trying to get the info I needed so that when it arrived, I'd be able to load up froyo, wifi calling and be done quickly. I set it all up and downloaded ryan's OCLF, ran it, rooted, installed the ext files, then the v2 lag fix it said to. Everything was great.
Later I downloaded a few apps and titanium backup, but didn't back up yet. I ran the battery down low. Went into the clockwork app that I downloaded and did a backup restore.
About an hour later the battery finally died. I read that you should turn it on until it won't anymore before finally plugging in to charge and wiping the battery settings. Problem is it wouldn't boot up again. Hung on the Galaxy S screen with the shining S.
I could still reboot into recovery and into download. Was going to ODIN back, but my PC was giving me trouble. I pulled the micro sim and thre the ASOP 2.2 rom on it from another laptop dragged it to card removed and popped it back in. I tried to reboot to recovery which worked, then reinstall, nothing. Tried to get to the SD card, but it doesn't find it.
Finally gave up and went back into recovery and did a factory data wipe reset or whatever it is called. When the phone rebooted it all booted fine, no problems at all however I lost every setting account etc..
So here's where I'm at now, i mounted it as USB and looked at the phone from the PC, in the clockwork folder is my backup I just can't get it to load.
I went back to the market and redownloaded the ryan OCLF and removed the lag, ext and root and I'm back to stock. Phone will turn off and back on.
What now? Where did I go wrong, it doesn't make any sense, I followed every instruction exactly as it was written.
I'm a little concerned to root again, but I want to backup settings, accounts etc.. in case this happens again.
first...welcome to XDA...the baddest forum on the planet...
second....this is the wrong section for this topic....should be in Q & A section...but a Mod will take care of that....
third....read this.....http://forum.xda-developers.com/showthread.php?t=849028
the author worked hard on this to become a sticky so noobs will see it first...if u need more info....there is another sticky in the general section...good luck!!
Thanks, I'll read through it now. I thought I had a good idea to drag the new rom to the sd card and fire it up from there, but it failed. Happy I didn't brick the phone. I saw a lot of posts saying ODIN was the only way back, guess I got lucky with the data wipe.
I've had iphones for 2 years and when this happened it would be a conflict with programs, is there a list like that for android like there was for cydia in the iphone info?
I don't know.... but make sure you read carefully before you flash... in a nutshell the steps for ROM flashing is.
1. Root
2. Download and install ROM Manager from market
3. Flask clockwordmod recovery
4. Nandroid (backup)
5. Backup SD card to pc(just in case)
6. Flash your ROM from clockworkmod recovery.
Sent from my XDA app cuz I'm stalking your mom....
Here's a question I don't think is answered after reading the post. So rooting via OCLF without installing the lag fix v2 is exactly the same as rooting by dragging and dropping.
Rooting in itself can't cause the phone to not reboot, but if you flash incorrectly or apply lag fix and flash over them you could run into trouble. I just can't seem to figure out where the error was. I didn't delete the update zip after rooting, thats the only error I see.
Other issue I noticed is that on mounting to USB after booted I can see the backups, but I can't locate the ROM zip I put on the SD card or the SD card at all.
So let me get this straight... you rooted via OCLF.. but did not apply the lagfix?
Edit: oh I see... u tried to flash a froyo Rom then go back to stock?...
Sent from my XDA app cuz I'm stalking your mom....
No I rooted then applied the lag fix it had available which was version two I believe
Sent from my SGH-T959 using XDA App
Ok... try ODIN back to stock...make sure you have the correct drivers
Sent from my XDA app cuz I'm stalking your mom....
Let me correct what I'm saying, the phone went into the stuck glowing S screen when trying to turn it back on after I ran the battery down to nothing. It wouldn't boot past that point. I tried reinstall, reboot, etc..from the menu in clockwork recov in recov screen as that was all i could get to. When that failed I tried just loading a 2.2 ROM to the sd card direct from my laptop, thought I could just flash from that screen right over everything, didn't work either. Thats when I tried delete all info as a last effort, but then it magically booted back 100% stock, but still rooted. So i reloaded OCLF and unrooted because I don't know what caused the phone to be stuck in the S screen, I didn't flash anything, just did the root and oclf all from ryan's OCLF app
I tried to reroot manual, didn't work, lots of issues, wouldnt root. Went back for OCLF gone. Went for the z4 gone. Found links for both, tried the z4 didnt' work, superuser continiously popping up for permissions, went back removed that and reloaded oclf from web, ran and fixed boot and rerooted, all good. Went back and downloaded and flashed Vibrant AOSP ish JK2 1.1 Official FROYO. Absolutely love it so far. I've been waiting for wifi calling for a long time, it actually works. Problem is I'm not really sure if I rebackup everything now or leave the backups I have from clockwork for stock. I keep reading everything and feel like I'm missing something. I have Vibrant AOSP ish JK2 1.1 Official FROYO saved so I guess if it crashes I just reflash that and don't need a backup, but should titanium backup the whole thing instead now? Sorry if no one replies i get it. Two years of iphone jailbreaking is a waste, nothing like this at all! I will say I never bricked an iphone, feel like i'm gonna brick this thing.
I want to run the OCLF v2, but concerned it's going to cause issues as it's running so smooth right now.
It works fine
Sent from my SGH-T959 using XDA App
version 2 isn't an option, i'm running lag fix one, seems ok I'm having some other issues, but its running
If your still having problems odin back to stock and start over it always safer and will cause less problems
Sent from my SGH-T959 using XDA App
All my issues were because busy box was messed up, all good now
Sent from my SGH-T959 using XDA App
Just to throw it in there... you should always backup your current ROM and all apps using both ROM Manager AND Titanium Backup. It makes it THAT much easier if you do, by chance, have to use ODIN or run a recover, to get your settings, apps, saved data, etc. back without much hassle.
I run a Titanium backup on all of my apps I have loaded (NOT SYSTEM APPS as they are backed up by ROM manager I believe) once a month or so, just to keep fairly recent. It makes it to where, if it does need to be restored, the apps all get re-installed at once including saved data within the app (saved game progress, etc.). This is handy because you don't have to remember what all you had installed and you don't have to go searching through marketplace to get those apps back.
If you are running a custom homescreen (Launcher Pro, etc.), you should also use their backup option to save your homescreen settings.
In short, backup everything you can... it makes 3 hours worth of reloading things condense into a nice little 10-15min "install", "ok" button pressing fiesta!
And, to let you know, I've (as just about 100% of XDA users) flashed, and ODIN'd nearly a thousand times and have yet to brick a phone. These things are crazy indestructible. There's 3 or 4 different ways to get into Download Mode if you get the computer!phone screen... so don't worry about it. The only thing you really lose is time spent getting things back to normal if you screw up. But read up on everything, which it sounds like you already do, before you even attempt anything that could kill the phone. I don't post much on here because just about everything is already answered... you just have to search a little bit.
So it's been a while since I did any rooting/recovery stuff on phones and now that I'm on my 3rd phone but the previous 2 were HTCs which are different from the Optimus V, on virgin mobile.
I did some poking around and looking but haven't found anything, that I know of, that would allow me to do what I VERY MUCH like and prefer to do as opposed to basically starting over on the new phone.
Basically, I'm coming from the HTC HD2 on t mobile with a custom 2.3 rom and have backups of the programs I want to put on the optimus v by using titanium backup, if it makes a difference I also have clockworkmod/TI backup installed on both phones; obviously they wont work on the optimus till its rooted. I know I need to have root ability but don't/won't actually need it permanently b/c other than transferring apps/data over, I want to remove a few of the virgin apps on the phone and be done.
From what I did read, I know I can use SuperOneClick and adb to remove the virgin apps but where does that leave me for the transferring of apps/data?
If you could link files needed along with directions/steps or to a thread that shows how to do this w/ temp root or perm root would be most appreciated.
I need this done asap so i can wipe the hd2 to just a clean android 2.3 and then sell it to a buyer i'm meeting tonight.
Sorry, if this question has been asked but I did look before posting.
Thanks in advance!
See this thread for rooting, & installing custom recovery & custom ROM.
http://forum.xda-developers.com/showthread.php?t=1197991
After everything is done, you should make another Nandroid backup in recovery mode, then could try to restore from your Titanium backup, but it's not recommended for even coming from a different ROM, let alone a different device. If you get weird bugs, then restore to the fresh Nandroid backup & and re-install all apps manually.
Thanks for the reply, i was just looking at your post on rooting/recovery/etc. Ok, guess I will have to do that then since I'm in a rush.
And by manually you mean one by one through adb, correct? If not please enlighten me!
CTR01 said:
Thanks for the reply, i was just looking at your post on rooting/recovery/etc. Ok, guess I will have to do that then since I'm in a rush.
And by manually you mean one by one through adb, correct? If not please enlighten me!
Click to expand...
Click to collapse
manually as in however you installed them originally (either through Android Market or .apk.
ahhh got it lol thanks...well hope that doesnt happen cuz i dont wanna lose my data...thanks again.
And for the record so far the apps are being restored currently and everything seems to be working fine using the BumbleBee rom you linked in your rooting/recovery guide.
CTR01 said:
And for the record so far the apps are being restored currently and everything seems to be working fine using the BumbleBee rom you linked in your rooting/recovery guide.
Click to expand...
Click to collapse
I'm fixin to try a Bumblebee + Blue Sphere combo just for laughs and grins. Will let you know how that works out. Might try the picasticks with it as well.
EDIT: Could not get the bluesphere kernel to play with the Bumblebee ROM. I did get the picasticks kernel to play though. It seemed to smooth it out a little more. I went down to 600MHz where I could see how angry birds played. Stock Bumblebee showed a little lag when game returned to the sling shot. With picasticks kernel it smoothed it out a little better. I liked it. This combo will now be my Froyo ROM in recovery backup(I like to have one Froyo ROM and one Gingerbread ROM in my backups). I'll try it with V6 script on option#2
Just went through the entire 4 hour long process of SBFing to 2.3.3, doing the 2.3.4 OTA, rooting, updating to custom rom, then restoring all my sms/mms etc etc but not system data. I just flipped through the apps and noticed the new icons.
Its smooth as butter except (Edit: It Was... now its laggier then 2.2.2 stock), I just went into About Phone to see If I turned off the upgrader 2.3.4. Their I noticed It said I was still on 2.3.3.
As you can see the kernel is 2.3.4, the build is 2.3.3 and it's telling me to upgrade to 2.3.4. All my system apps says 2.3.4, and I'm on a custom rom (Moto-Ginger-Funk). I doubt I'd be able to install that with no errors if I wasn't. So would just like to ask, what the hell is going on here? I have no problems, a couple force closes after first restore of stuff but a reboot fixed that.
Had to Flash some stuff to the phone and just went into About Phone again and now it says 2.3.4 . Looks like I found another bug, even if it's not that big but it is weird.
It might have just been reading from old data and finally caught up. I am assuming this was after initial startup?
i think you might be using a kernel and system from seperate levels of gingerbread. like one is on 2.3.3 and one form 2.3.4. remember we cant really use a custom rom due to no unlocked bootloader so the rom your using could have system files from both.
AtLemacks said:
It might have just been reading from old data and finally caught up. I am assuming this was after initial startup?
Click to expand...
Click to collapse
No this was after rebooting about 4 times adding stuff into recovery.
^I kinda hope not since everything now says 2.3.4.
You know when I did the sbf it only took 15-20mins and I still had everything that I had when I was on eclipse 0.2.2 except for root. It had all my settings and txt messages. The only thing I had to do was root and *228. I thought sbf was supposed to get rid of everything.
Sent from my DROID X2 using XDA App
(aq) said:
i think you might be using a kernel and system from seperate levels of gingerbread. like one is on 2.3.3 and one form 2.3.4. remember we cant really use a custom rom due to no unlocked bootloader so the rom your using could have system files from both.
Click to expand...
Click to collapse
What? Dude, we have custom roms, just not custom kernels. We have root, we have everything except an unlocked BL. He didn't flash the 2.3.4 rom based on the 2.3.3 kernel, he took the OTA update. You are not very savvy in this are you?
---------- Post added at 06:14 PM ---------- Previous post was at 06:13 PM ----------
densetsu86 said:
You know when I did the sbf it only took 15-20mins and I still had everything that I had when I was on eclipse 0.2.2 except for root. It had all my settings and txt messages. The only thing I had to do was root and *228. I thought sbf was supposed to get rid of everything.
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
You still need to do a full data/system wipe if you plan on going back to complete stock. This is why a lot of people get stuck in boot loops because they don't wipe cache/davlik, or do a full wipe.
I did the sbf a couple of days ago and I had no problems. Hell my phone is running the best it has ever have. I used to hate this phone but after 2.3.4 I love it.
Sent from my DROID X2 using XDA App
Yea re-did it this time SBF not OTA and its running great. Before it was awful.
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!
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: