Related
Quick question. Can I do a nandroid restore after wiping data, cache and dalvik?
If you chose to put it in your external SD card when you made it, yes. wiping the big 3 doesn't wipe the SD card
Sent from my MB870 using XDA App
IDMA.DROID.X2 said:
If you chose to put it in your external SD card when you made it, yes. wiping the big 3 doesn't wipe the SD card
Sent from my MB870 using XDA App
Click to expand...
Click to collapse
So i will be able to go back to my original ROM just as I left it even after wiping the big 3?
Yup! I've got a back ulbof every ROM except MIUI, haven't flashed it yet! Haha
Sent from my MB870 using XDA App
EDIT: Make sure its on the external SD card though. Not sure weather it will be there on the SD card if you put it there then wiped the big 3
IDMA.DROID.X2 said:
Yup! I've got a back ulbof every ROM except MIUI, haven't flashed it yet! Haha
Sent from my MB870 using XDA App
EDIT: Make sure its on the external SD card though. Not sure weather it will be there on the SD card if you put it there then wiped the big 3
Click to expand...
Click to collapse
I have a nandroid on my internal that has endured several data wipes and sbf's. It is a backup of my stock phone before flashing anything. I backed it up in both places just in case.
Sent from my cm7dx2 using XDA App
litetaker said:
So i will be able to go back to my original ROM just as I left it even after wiping the big 3?
Click to expand...
Click to collapse
Well, that depends. If you upgraded to say, Android 2.3.5, then you have a different kernel and the kernel is NOT backed up via Nandroid. So unless you are still on the same android version, then you should SBF back to the base OS version you were on. This was tested extensively about a month or so back and it was determined that a nandroid restore doesn't restore the kernel.
Otherwise, nandroiding back should get you where you were before.
iBolski said:
Well, that depends. If you upgraded to say, Android 2.3.5, then you have a different kernel and the kernel is NOT backed up via Nandroid. So unless you are still on the same android version, then you should SBF back to the base OS version you were on. This was tested extensively about a month or so back and it was determined that a nandroid restore doesn't restore the kernel.
Otherwise, nandroiding back should get you where you were before.
Click to expand...
Click to collapse
Good to know! I missed the tests done, I thought it backed up everything.
Sent from my MB870 using XDA App
iBolski said:
Well, that depends. If you upgraded to say, Android 2.3.5, then you have a different kernel and the kernel is NOT backed up via Nandroid. So unless you are still on the same android version, then you should SBF back to the base OS version you were on. This was tested extensively about a month or so back and it was determined that a nandroid restore doesn't restore the kernel.
Otherwise, nandroiding back should get you where you were before.
Click to expand...
Click to collapse
So if MIUI is saying that it is running Android 4.0.3, and CM7 is Android 2.3.7, then is it not ok to nandroid back to CM7 from MIUI?
jsgraphicart said:
So if MIUI is saying that it is running Android 4.0.3, and CM7 is Android 2.3.7, then is it not ok to nandroid back to CM7 from MIUI?
Click to expand...
Click to collapse
No, it should be fine. 4.0.3 is STILL using the same kernel. 4.0.3 is the OS version, not necessarily the kernel version.
Since the bootloader is still locked, flashing the DX2 MIUI still keeps the 2.3.4 kernel. All that gets replaced are the system files. So, nandroiding back to CM7 (which is what I did) is fine because you are still running the same kernel.
At least, that's how I read it when I researched a little on this and with some other people posting their explanations as well.
The reason you shouldn't flash 2.3.4-based ROMs over 2.3.5 is because the kernel version was changed. Remember, the kernel can ONLY be updated via a Verizon-approved OTA. The 2.3.5 update is not an official release, but it DID come from Motorola servers, so it has the signature in it that the X2 is looking for when the kernel is attempted to be upgraded. Hence, that is why flashing a 2.3.4-based ROM over a 2.3.5 image is not a good thing. Same goes with flashing a 2.3.5 ROM over a 2.3.4 image. It's just not a good idea and could pose problems down the road.
iBolski said:
No, it should be fine. 4.0.3 is STILL using the same kernel. 4.0.3 is the OS version, not necessarily the kernel version.
Since the bootloader is still locked, flashing the DX2 MIUI still keeps the 2.3.4 kernel. All that gets replaced are the system files. So, nandroiding back to CM7 (which is what I did) is fine because you are still running the same kernel.
At least, that's how I read it when I researched a little on this and with some other people posting their explanations as well.
The reason you shouldn't flash 2.3.4-based ROMs over 2.3.5 is because the kernel version was changed. Remember, the kernel can ONLY be updated via a Verizon-approved OTA. The 2.3.5 update is not an official release, but it DID come from Motorola servers, so it has the signature in it that the X2 is looking for when the kernel is attempted to be upgraded. Hence, that is why flashing a 2.3.4-based ROM over a 2.3.5 image is not a good thing. Same goes with flashing a 2.3.5 ROM over a 2.3.4 image. It's just not a good idea and could pose problems down the road.
Click to expand...
Click to collapse
Ok, that makes sense. I figured it would be fine but didnt know the technical details.
I've flashed my 2.3.4 backups over 2.3.5 quite a bit since my cheesecake backup is 2.3.5 and I've never had any issues. Do we really know if the kernel changed? I never really looked at the kernel version on 2.3.5.
Sent from my MB870 using XDA App
T3HBR1AN said:
I've flashed my 2.3.4 backups over 2.3.5 quite a bit since my cheesecake backup is 2.3.5 and I've never had any issues. Do we really know if the kernel changed? I never really looked at the kernel version on 2.3.5.
Sent from my MB870 using XDA App
Click to expand...
Click to collapse
Back in December, I asked the question about nandroiding and if it replaced the kernel. Motcher (and ashclepdia) helped out with this one. Motcher SBF'd to 2.3.4 and then nandroided back to Eclipse 2.0.3 (which is 2.3.5) based and the kernel version came up as 00005 which is the 2.3.4 kernel. So, Nandroiding does NOT replace the kernel.
Here's the posted that he posted about this:
http://forum.xda-developers.com/showpost.php?p=20808392&postcount=20
It may be that the differences are minor enough that it won't cause issues, but if the official 2.3.5 ever comes out, it might be best to always SBF back to 2.3.4 if you have to just to be on the safe side. I guess the moral of the story is, do this at your own risk.
Ok I tried to nandroid back to cm7 from Miui and I got a md5-sum mismatch message, and I wasn't able to go back. Do I need to wiped the big 3 every time I nandroid ?
Sent from my DROID X2 using XDA App
bandit1224 said:
Ok I tried to nandroid back to cm7 from Miui and I got a md5-sum mismatch message, and I wasn't able to go back. Do I need to wiped the big 3 every time I nandroid ?
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
No. That means the md5-sum hash key that was generated after the backup was created isn't matching with your nandroid backup. It means possibly your backup is corrupted.
Wiping the big three has nothing to do with nandroiding.
Uninstall bsr -either cm7 or orig. Then reinstall cm7 bsr. It worked for me On cm7. BTW Be sure not to use any spaces when renaming.
failed restore
So im trying to reload my backup from my sd card. I have made 2 thus far and neither work.
I am on the Rogers network on a i747 with the dlk4 baseband. CWM, rooted, stock rom. When i try to restore it loads a few things (ie. system), and starts loading the DATA portion. Which at this point i get an error message. I reboot it, and my phone gets hung up at the samsung loading screen.
I have tried wiping the big 3 and also under mount and unmount i formated system before restoring as well with no success.
Could it be that my version of CWM is 5.5.0.4.. And, from my understanding I dont think it would be the cause, but maybe because i made the backup after being rooted and flashing cwm
Sykotyk said:
So im trying to reload my backup from my sd card. I have made 2 thus far and neither work.
I am on the Rogers network on a i747 with the dlk4 baseband. CWM, rooted, stock rom. When i try to restore it loads a few things (ie. system), and starts loading the DATA portion. Which at this point i get an error message. I reboot it, and my phone gets hung up at the samsung loading screen.
I have tried wiping the big 3 and also under mount and unmount i formated system before restoring as well with no success.
Could it be that my version of CWM is 5.5.0.4.. And, from my understanding I dont think it would be the cause, but maybe because i made the backup after being rooted and flashing cwm
Click to expand...
Click to collapse
this is a thread for the motorola droid x2.
oops
Lorenzo VonMatterhorn said:
this is a thread for the motorola droid x2.
Click to expand...
Click to collapse
i've been searching threads with search tool....guess i wasn't paying attention.
Cheers
Hey Guys, Well big Hello and just wanted to say that usually every question ive had for my phone that I typed into google sent me here so i joined: I just got the dx2 as a replacement for my dx. so first thing i did was root it . now it is running 2.2.2 froyo i rooted with ginger break. I know that their is the latest update out and I froze the updater because it kept prompting me to update. so my question is can i one click root the latest update, or can i use OTA rootkeeper. YES i have done the reading in the posts but didnt get the clear cut answer i wanted so simply is rootkeeper the easyiest way to keep root or should i just ota update then root.
thanks guys
Broadley1 said:
Hey Guys, Well big Hello and just wanted to say that usually every question ive had for my phone that I typed into google sent me here so i joined: I just got the dx2 as a replacement for my dx. so first thing i did was root it . now it is running 2.2.2 froyo i rooted with ginger break. I know that their is the latest update out and I froze the updater because it kept prompting me to update. so my question is can i one click root the latest update, or can i use OTA rootkeeper. YES i have done the reading in the posts but didnt get the clear cut answer i wanted so simply is rootkeeper the easyiest way to keep root or should i just ota update then root.
thanks guys
Click to expand...
Click to collapse
Rootkeeper works just fine. Only thing to watch out for is you can not install eclipse 2.+ with rootkeeper installed. You have to erase your back up. But it will get you to 2.3.4 no problem
Just from what I read in these forums, root keeper works, but people do have problems with it in some circumstances. I dont read about people having problems with the other two one click root methods. I've always used the one click methods and never used root keeper so Im just basing it off of what I read. But in your circumstance, either way will probably be fine. But like what was already said, you might have to use the one click methods if you are updating to certain things.
Broadley1 said:
Hey Guys, Well big Hello and just wanted to say that usually every question ive had for my phone that I typed into google sent me here so i joined: I just got the dx2 as a replacement for my dx. so first thing i did was root it . now it is running 2.2.2 froyo i rooted with ginger break. I know that their is the latest update out and I froze the updater because it kept prompting me to update. so my question is can i one click root the latest update, or can i use OTA rootkeeper. YES i have done the reading in the posts but didnt get the clear cut answer i wanted so simply is rootkeeper the easyiest way to keep root or should i just ota update then root.
thanks guys
Click to expand...
Click to collapse
I would recommend following my SBF tutorial and SBF to 2.3.4 (Gingerbread), then follow my rooting tutorial for the DX2, then follow my nandroid backup tutorial. Once you have those, take a look at CM7DX2 for a nice ROM for the DX2 (the original post (OP) has detailed installation instructions that I wrote), or Nitro's Eclipse ROM.
All links to my tutorials are in my signatue. Look up the CM7DX2 and Eclipse ROMs in the development section for the Droid X2.
Ciao!
Moon Shadow - NM said:
I would recommend following my SBF tutorial and SBF to 2.3.4 (Gingerbread), then follow my rooting tutorial for the DX2, then follow my nandroid backup tutorial. Once you have those, take a look at CM7DX2 for a nice ROM for the DX2 (the original post (OP) has detailed installation instructions that I wrote), or Nitro's Eclipse ROM.
All links to my tutorials are in my signatue. Look up the CM7DX2 and Eclipse ROMs in the development section for the Droid X2.
Ciao!
Click to expand...
Click to collapse
Thanks moon shadow what your saying makes sense. I am just leary about the whole flash, sbf method. i have had bad luck with rsd in the past. I am really not a big rommer i tried liberty before and it repeatedly soft bricked my phone. I used rsd to run the gb leak for my original dx and found it very unstable. I just really wanted the update but also keep my root goodies.
Travisdroidx2 said:
Rootkeeper works just fine. Only thing to watch out for is you can not install eclipse 2.+ with rootkeeper installed. You have to erase your back up. But it will get you to 2.3.4 no problem
Click to expand...
Click to collapse
Im not a big rommer just really want the latest ota but also keep my root goodies. Can you explain a basic breakdown on what i have to do before i take the OTA and after.
Backup ur app with rom tool box pro, or titanium backup. Accept the ota and use zergrush to root all u do is plug it into ur comp press enter and boom rooted. I recommend gb2.3.3 stock. So far it has been the best stock rom. Way better than 2.3.4. But that is my opinion. Remember anything u do is at ur own risk. Enjoy
Sent from my DROID X2 using XDA
droid2 rc said:
Backup ur app with rom tool box pro, or titanium backup. Accept the ota and use zergrush to root all u do is plug it into ur comp press enter and boom rooted. I recommend gb2.3.3 stock. So far it has been the best stock rom. Way better than 2.3.4. But that is my opinion. Remember anything u do is at ur own risk. Enjoy
Sent from my DROID X2 using XDA
Click to expand...
Click to collapse
Thanx bud well the update it sends me is for 1.3.232 now what is that is that for 2.3.4 or later?
that's 2.3.3
you could try DX2 ezSBF
just don't update to 1.3.418
unless you want to risk not having root
edit: 1.3.232 is just 2.3.3
I have a list of updates, in my collection of links
Sent from my DROID X2 using xda premium
Moon Shadow - NM said:
I would recommend following my SBF tutorial and SBF to 2.3.4 (Gingerbread), then follow my rooting tutorial for the DX2, then follow my nandroid backup tutorial. Once you have those, take a look at CM7DX2 for a nice ROM for the DX2 (the original post (OP) has detailed installation instructions that I wrote), or Nitro's Eclipse ROM.
All links to my tutorials are in my signatue. Look up the CM7DX2 and Eclipse ROMs in the development section for the Droid X2.
Ciao!
Click to expand...
Click to collapse
Hey moon shadow, I tried the OTA update and it seems to fail i unfroze and unrooted but still no luck? I think that i might have made a mistake because I erased the stupid bloat games that came with it ( golf 2, nfs) is this my problem?
Broadley1 said:
Hey moon shadow, I tried the OTA update and it seems to fail i unfroze and unrooted but still no luck? I think that i might have made a mistake because I erased the stupid bloat games that came with it ( golf 2, nfs) is this my problem?
Click to expand...
Click to collapse
Yes it all has to be there including those games
Sent from my DROID X2 using xda premium
you can not remove stock app, if you want to update
you will have to SBF
HowTo: Perform a SBF ("factory restore") of your Motorola Droid X2
next time use titanium backup to freeze unwanted apps, so you just unfreeze when you want to update
sd_shadow said:
that's 2.3.3
you could try DX2 ezSBF
just don't update to 1.3.418
unless you want to risk not having root
edit: 1.3.232 is just 2.3.3
I have a list of updates, in my collection of links
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Got a question about using zip. when I unzip where do i extract to? and do i just move the sbf or drivers too?
sd_shadow said:
you can not remove stock app, if you want to update
you will have to SBF
HowTo: Perform a SBF ("factory restore") of your Motorola Droid X2
next time use titanium backup to freeze unwanted apps, so you just unfreeze when you want to update
Click to expand...
Click to collapse
Yea i did do a backup it restored the games but still wont OTA. I am usually pretty careful cant believe i was that stupid to erase those apps i do usually freeze with tb but when i restored and tried the ota it still failed oh well sbf it is
Broadley1 said:
Got a question about using zip. when I unzip where do i extract to? and do i just move the sbf or drivers too?
Click to expand...
Click to collapse
what zip are you using?, moto drivers need to be installed on pc, move SBF to any where on computer that you can find again
---------- Post added at 11:42 AM ---------- Previous post was at 11:39 AM ----------
Broadley1 said:
Yea i did do a backup it restored the games but still wont OTA. I am usually pretty careful cant believe i was that stupid to erase those apps i do usually freeze with tb but when i restored and tried the ota it still failed oh well sbf it is
Click to expand...
Click to collapse
if you restored apps, you could try fixing permissions, in ClockworkMod recovery,
I don't use stock, so when update comes out have to SBF, anyways
sd_shadow said:
what zip are you using?, moto drivers need to be installed on pc, move SBF to any where on computer that you can find again
---------- Post added at 11:42 AM ---------- Previous post was at 11:39 AM ----------
if you restored apps, you could try fixing permissions, in ClockworkMod recovery,
I don't use stock, so when update comes out have to SBF, anyways
Click to expand...
Click to collapse
yea sorry i was wondering about the drivers im not familiar with unzipping them and where to put them when i do i put the sfb in a temp file for rsd but didnt know where to put the drivers?
I just wanted to say thanks again shadow your a huge help for a noob
if drivers are in zip, unzip anywhere
then run them, by double clicking
Shadow im having an issue flashing it wont pull the right information for my phone it just says s flash and n/a for everything else shoud i be in mass storage or charge only?
to flash SBF, you need to be in bootloader mode
RSD Flash Support
turn off, hold volume up, reboot
all it will say is "starting RSD support"
then your ready
yea i got that far but in your tutorial it says that i should see the infor on my phone in slot 1 but all it says is s flash, and all the info on the phone is N/A? is this alright?
edit: sorry it was the link that you sent me it said i should see my phone info
edit: duh im a dumbass sorry for you having to put up with me shadow i answered my own question i just had to read a little closer
thanks again ill keep you posted
I'm happy with my current setup on Eclipse, but of course I'm curious about CM7 and CM9. I was wondering, would it be possible to:
-nandroid backup my current eclipse setup
-follow install instructions for CM7/9 or even getting back to stock rooted or any other ROM.
Then, if I choose I prefer Eclipse over CM7/9 whatever, just simply restore my nandroid backup of Eclipse to get back to my current setup? or would I have to go through all the procedures again?
I guess my question boils down to: Does the nandroid backup backup everything as is? Or can I restore between different nandroids on different ROMs without worry?
flanker1743 said:
I'm happy with my current setup on Eclipse, but of course I'm curious about CM7 and CM9. I was wondering, would it be possible to:
-nandroid backup my current eclipse setup
-follow install instructions for CM7/9 or even getting back to stock rooted or any other ROM.
Then, if I choose I prefer Eclipse over CM7/9 whatever, just simply restore my nandroid backup of Eclipse to get back to my current setup? or would I have to go through all the procedures again?
I guess my question boils down to: Does the nandroid backup backup everything as is? Or can I restore between different nandroids on different ROMs without worry?
Click to expand...
Click to collapse
It will not back up your kernel therefore, make your nandroid. SBF back then root install Cm9. If you want to go back you will have to use ota root keeper take the ota then restore your nandroid to be back on eclipse
Sent from my MB870 using xda premium
flanker1743 said:
I'm happy with my current setup on Eclipse, but of course I'm curious about CM7 and CM9. I was wondering, would it be possible to:
-nandroid backup my current eclipse setup
-follow install instructions for CM7/9 or even getting back to stock rooted or any other ROM.
Then, if I choose I prefer Eclipse over CM7/9 whatever, just simply restore my nandroid backup of Eclipse to get back to my current setup? or would I have to go through all the procedures again?
I guess my question boils down to: Does the nandroid backup backup everything as is? Or can I restore between different nandroids on different ROMs without worry?
Click to expand...
Click to collapse
trafalger888 said:
It will not back up your kernel therefore, make your nandroid. SBF back then root install Cm9. If you want to go back you will have to use ota root keeper take the ota then restore your nandroid to be back on eclipse
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
if you have any trouble following the instructions given here, let us know.
Ah. Because CM7 and 9 are based on 2.3.4, whereas Eclipse is 2.3.5 based, correct?
flanker1743 said:
Ah. Because CM7 and 9 are based on 2.3.4, whereas Eclipse is 2.3.5 based, correct?
Click to expand...
Click to collapse
Correct
Sent from my MB870 using xda premium
I try and keep two NANDroid by...
One is stock untouched 2.3.4
The other is stock untouched 2.3.5...
Flashing is quick and easy, so all I have to do is wipe and install...
DROID DOES, Apple did...like I forgot when
Pixelation said:
I try and keep two NANDroid by...
One is stock untouched 2.3.4
The other is stock untouched 2.3.5...
Flashing is quick and easy, so all I have to do is wipe and install...
DROID DOES, Apple did...like I forgot when
Click to expand...
Click to collapse
Here, Here!
Hi everyone,
I've been having some serious issues and I am stumped on what to do so I'm turning to you smart guys here at XDA...
I'm using a Droid X2 flashed to Cricket, running CM7.2. I read through the CM10 Jelly Bean thread and really wanted to give it a try because of all the neat features it has in it. I did a Nandroid backup, installed the zip and gapps, wiped data/cache and booted into CM10. Everything went good, got CM10 configured, but had a non-relevant issue with CM10 and figured it was probably just a bad install. I tried to restore my Nandroid and it froze up halfway through and sat at "Restoring .android_secure" for OVER an hour. So I made the dumb mistake of pulling the battery which resulted in a bootlooping soft-brick. I then did an SBF back to 2.3.5 which naturally wiped my flash to Cricket. So I rooted and re-flashed to get my network working again which went perfectly fine. Then I restored my Nandroid and went back to CM7.2....and now my Wi-FI says "Error" and will not even attempt to connect. I figured the Nandroid probably got botched so I restored it again and had the same issue. I tried to reflash CM7.2 and also tried to reflash CM10 and get the "assert failed: run_program (tmp/kernel_check) ==0 (status 7)" error on both. I have tried repeatedly redownloading both zip files and attempted reflash with the same error. Obviously rebooting the phone and trying Wi-Fi fixer do absolutely nothing. I would either like to stay on CM7.2 OR give CM10 another try but cannot flash either zip with the CM7 patched BSR. If I can have the Wi-Fi fixed on CM7.2 then great, if I can be on CM10 with working Wi-Fi even better, but I would like to be able to get this fixed WITHOUT having to do another SBF...flashing it to Cricket is a PITA and I can only do the flash on 2.3.5 since that is the only version that gives the "PC Mode" option for USB connection. Factory Reset is not an issue with me, I just want things working properly. Any and all help is as usual GREATLY appreciated. Thanks in advance.
Err, you couldn't have been on 2.3.5 and CM7 before. That and CM10 are 2.3.4 ROMs. If you sbf'd to 2.3.5 then your only options are stock ROM or eclipse 2.3
Sounds like you need to sbf back to 2.3.4
Sent from my DROID X2 using xda app-developers app
three west said:
Err, you couldn't have been on 2.3.5 and CM7 before. That and CM10 are 2.3.4 ROMs. If you sbf'd to 2.3.5 then your only options are stock ROM or eclipse 2.3
Sounds like you need to sbf back to 2.3.4
Sent from my DROID X2 using xda app-developers app
Click to expand...
Click to collapse
You are correct, they are ROMS that need to be flashed from 2.3.4, but I didn't flash, I restored a Nandroid backup. I started on 2.3.4, flashed CM7, used that for a while, then flashed CM10 over CM7, then did SBF to 2.3.5 and then restored a Nandroid back to my CM7. As I stated above, I can only get my phone onto Cricket from 2.3.5 as that is the only version of android that has the "PC Mode" option when connecting to computer with USB, that is the ONLY connection mode that can be used to network flashing. If I SBF back to 2.3.4 I might be able to flash a new ROM but then I won't be able to do the network flash myself, I will have to take it to cricket which I would prefer not to have to do.
d34thbl00m said:
You are correct, they are ROMS that need to be flashed from 2.3.4, but I didn't flash, I restored a Nandroid backup. I started on 2.3.4, flashed CM7, used that for a while, then flashed CM10 over CM7, then did SBF to 2.3.5 and then restored a Nandroid back to my CM7. As I stated above, I can only get my phone onto Cricket from 2.3.5 as that is the only version of android that has the "PC Mode" option when connecting to computer with USB, that is the ONLY connection mode that can be used to network flashing. If I SBF back to 2.3.4 I might be able to flash a new ROM but then I won't be able to do the network flash myself, I will have to take it to cricket which I would prefer not to have to do.
Click to expand...
Click to collapse
You can not restore a nandroid from one kernel to another without having problems even with wiping. You can try to flash the Mx2 versions they don't ask for the kernel check but you might still have problems on 2.3.5.
appl3mac said:
You can not restore a nandroid from one kernel to another without having problems even with wiping. You can try to flash the Mx2 versions they don't ask for the kernel check but you might still have problems on 2.3.5.
Click to expand...
Click to collapse
Yeah I started to think that that could have been the issue, that it was still running the 2.3.5 kernel. Well I saw no other option so I decided to SBF back to 2.3.4, and it somehow now has the PC Mode option, so I can do the Cricket flash on that now. Weird that it didnt have that option the last time I did the SBF. Guess it should work now, will post a final update once I get the Cricket flash and CM10 reflashed.
Stick with 2.3.4 for Cm7, definitely if that is what your Nandroid is from. 2.3.5 is so limited as to what is developed for it.
tallyforeman said:
Stick with 2.3.4 for Cm7, definitely if that is what your Nandroid is from. 2.3.5 is so limited as to what is developed for it.
Click to expand...
Click to collapse
Yeah I got it all figured out, gonna run CM9. I've reflashed to Cricket so many times by now I can do it in 5 minutes or less lol. Thanks for the input guys.
CM9 is full of bugs.... you sure?
Sent from my DROID RAZR HD using Xparent Cyan Tapatalk 2
GoClifGo05 said:
CM9 is full of bugs.... you sure?
Sent from my DROID RAZR HD using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
Yeah, I've been using it for 2 solid days now and other than a little battery drain and the very occasional random reboot I would say it's running really good. I'm just sick of Gingerbread and after trying CM10 I decided I won't be going that route until a couple more alphas are released.
I have been using Eclipse 2.3 for sometime now and I have occasionally booted into recovery and backed up everything. Having come from the OG Droid, I am used to Nandriod and know how to restore from a Nandroid backup but the DX2 under eclipse is confusing me.
If I flashed a different ROM and then decided to go back to my Eclipse setup How would I go about restoring the Eclipse backup I made?
Len
Eclipse runs on gb 2.3.5. Cm7, 9, 10, AOKP, and pretty much every other rom runs on gb 2.3.4. You would need to make sure you are running 2.3.5 before you restore your nandroid backup.
So, for example, if you're running Cm7 and you want to go back and restore your Eclipse backup. You would need to SBF back to 2.3.5, root, install cwm recovery and restore the backup in the custom recovery.
Sent from my DROID X2 using Tapatalk 2
Juice3250 said:
Eclipse runs on gb 2.3.5. Cm7, 9, 10, AOKP, and pretty much every other rom runs on gb 2.3.4. You would need to make sure you are running 2.3.5 before you restore your nandroid backup.
So, for example, if you're running Cm7 and you want to go back and restore your Eclipse backup. You would need to SBF back to 2.3.5, root, install cwm recovery and restore the backup in the custom recovery.
Sent from my DROID X2 using Tapatalk 2
Click to expand...
Click to collapse
Thanks
You're welcome. Hope that helps.
Sent from my DROID X2 using Tapatalk 2