Moon Shadow's Droid X2 Tutorials - HowTo: Perform a bootstrap (or nandroid) backup and recovery of your Motorola Droid X2
Please note that some people call this a clockworkmod (CWM) backup or a nandroid backup. The backup procedure was adapted from the original CWM nandroid backup code, so technically that is a correct statement. I just wanted to point that out for clarification.
Please keep in mind that this tutorial is specifically for the Motorola Droid X2 running Gingerbread 2.3.3 or 2.3.4. These procedures MIGHT work for other phones, however, I would not recommend taking the risk of bricking, or even soft bricking, your phone.
Standard disclaimer: I, nor XDA Forums, are responsible for what you do to your phone. Just because these tutorials work for me, does not mean that they will work for you.
I make no claims to be the original owner of this process. I am just consolidating the process into an easy to follow (hopefully) guide that will help everyone from noobs to experienced users.
This tutorial has been adapted from the post: Droid X2 Boostrap APK (here now!) by c21johnson who combined what he found into this thread. The original bootstrap method came from koush.
This method uses no computer! That’s right! This is done all on your phone… Well, except to transfer the apk to your phone, unless you are viewing this on your phone’s browser, or the XDA app.
I am making some assumptions in this tutorial:
1. You must be rooted before installing the bootstrap recovery for the Motorola Droid X2. Follow this procedure: Moon Shadow's Droid X2 Tutorials - How To Root Your Motorola Droid X2.
2. You understand and are comfortable with installing software on your Droid X2 phone.
3. You understand and are comfortable with downloading programs, or transferring programs, to your Droid X2.
4. You understand and are comfortable with extracting compressed files (*.zip, *.rar *.7z, etc.) (I recommend 7zip to extract all compress files.)
5. You are willing to read this entire tutorial and ask questions if something is unclear to you, BEFORE you start this process. (Better to be safe than sorry.)
Now, on to the good stuff…
Hints:
Text in green are applications to launch or buttons to push within an application.
Text in red are warnings.
Orange is reserved for text that must be typed or copied. – Specific commands are also listed in code boxes.
This process will HIJACK the power off charge screen (who wants to see the battery do the wave on the charge screen anyway?). This process is REVERSABLE as well!
I have performed this method of backing up my phone a couple of dozen times. I have also used it to restore my phone a couple of times.
Initial steps to get the backup on your Droid X2:
1. You must be rooted before installing the bootstrap recovery for the Motorola Droid X2. Follow this procedure: Moon Shadow's Droid X2 Tutorials - How To Root Your Motorola Droid X2.
2. Make sure you are rooted and have the latest versions of Superuser and Busybox installed from the market.
3. Again, please make sure you are rooted!
4. Now, download the Droid X2 Recovery APK.
5. Using 7zip, extract the apk file from the archive. (Hint: it’s the only file in the archive!)
6. Copy the file to your phone. I use DropBox. It’s free to store up to 2GB, and the app is also free, plus it just works. Plus, if you click on the linked DropBox from here, signup, and install it, we will both receive an extra 250MB of space.) Okay, enough with the gratuitous advertising…
7. Once you have the app on your Droid X2, launch it. It is also called “System Recovery” so if you don’t launch it immediately, you can find it in the app drawer.
8. Once System Recovery has been launched, tap “Install Recovery”.
9. Tap “Allow” when Superuser asks for permission.
10. Wait about 5 seconds to ensure the Recovery Install has completed successfully.
11. Make sure your phone is not plugged into the USB port of your computer or a USB hub. It must be plugged into the wall charger!
12. Now tap “Recovery Mode”. In 3-5 seconds the Droid X2 will APPEAR to reboot. What it is actually doing is performing the hijack of the Power Off Charge Mode of the Droid X2. The Droid X2 actually powers off, but because the BSR hijacks the Charge Animation screen (the battery with the fuel level showing the amount of charge), it will look like it is booting up. In a sense, it is, but it will boot into the Bootstrap Recovery. The battery will continue to charge as well.
Backup procedure (If you have followed the steps above, you can jump directly to step #10, but I recommend you read the entire process):
1. Pay very close attention here… This is what bit me in the arse and led me to ask a stupid question…
2. Take the Motorola factory USB cable and unplug it from everything… The computer, the wall charging block, the phone… Everything!
3. Plug the micro USB end into the phone.
4. Plug the male USB-A end into the wall charging block.
5. Plug the wall charging block into the wall.
6. DOUBLE CHECK THE FOLLOWING!
7. Make sure the phone is plugged into the wall charger and plugged into the wall… NOT a USB hub, not a USB port on a computer, Not anything but the wall charger, and the wall charger is plugged into the wall…
8. Okay, enough…
9. Now, power off the phone and don’t touch anything. The phone will power down, then power back up and boot into the Droid X2 Recovery GFAN.COM screen. The menu choices are GREEN! (Damn! That’s not an application or a button to push… Oh well…)
10. Once in the recovery menu, press the VOLUME DOWN BUTTON 6 times. This should highlight the option to Backup & restore.
11. Tap the power button. This selects the Backup & restore option.
12. Use the VOLUME UP or VOLUME DOWN buttons to select the memory location you would like to store the backup on. If you have not enabled the SD Card flip, or you don’t know what the SD Card flip is, store the backup on the External SD Card. If you have, then the choice is up to you. (I will be releasing a tutorial on how to implement my favorite mods. When I do, I will link to it here.)
a. Internal SD Card = the 8GB internal, non-removable memory. (The Internal SD Card has a little over 6.4GB of usable storage space.)
b. External SD Card = your removable MicroSD card.
13. Once you have highlighted your selection, tap the power button.
14. On the next screen, tap the power button again, since the Backup option is already selected.
15. Now, wait, the backup takes about 10 minutes to complete. Once it is complete, you should be back at the Droid X2 Recovery GFAN.COM screen.
16. Now press the power key since the menu selection is already on Reboot system now.
17. You have successfully made a bootstrap recovery backup of your Droid X2.
Note: The bootstrap recovery backup does not erase old backups. You must do that yourself from within your favorite file explorer. The backups are located in /mnt/sdcard/clockworkmod/backup/YYYY-MM-DD.HH.mm.ss.
YYYY = the 4 digit year. 2011 for example.
MM = the 2 digit month. Such as 10 for October.
DD = the 2 digit day. Such as 24 for the 24th day of October.
HH = the hour in 24 hour time. Such as 14 for 2PM.
mm = the 2 digit minute of the hour. Such as 34 for 34 minutes after 2PM, or 2:34PM.
ss = the 2 digit seconds the backup was created. Such as 17 seconds, or 2:34:17PM
Note: DO NOT add SPACES to any of the folder or backup names as this will BREAK your recovery! You can add additional information to them, just don't add any spaces. I did confirm this and it did work for me. (Now I know which ROM is which backup! Cool!)
Now you are wondering, what happens if I totally hose my Droid X2? It’s in a boot loop that a battery pull then factory wipe has not fixed! (Or some other dreadful, stomach sinking feeling of, “Oh CRAP! I just bricked my $500.00 phone!) How do I restore my backup? Not to worry, IF you did a backup BEFORE you did whatever it is you did to your Droid X2 to boot loop it or what have you. Just follow the Restore procedure below! If not, you will have to use the SBF procedure that I have outlined in Moon Shadow's Droid X2 Tutorials - How to perform an SBF of your Motorola Droid X2 to flash your phone back to factory, then do all the custom things you have done to it again.
Restore Procedure:
1. Make sure the phone is plugged into the wall charger and plugged into the wall… NOT a USB hub, not a USB port on a computer, Not anything but the wall charger, and the wall charger is plugged into the wall… (I won’t go through all that again…)
2. Now, power off the phone. The phone will power down, then power back up and boot into the Droid X2 Recovery GFAN.COM screen.
3. Once in the recovery menu, press the VOLUME DOWN BUTTON 6 times. This should highlight the option to Backup & restore.
4. Tap the power button. This choses the Backup & restore option.
5. Use the VOLUME UP or VOLUME DOWN buttons to select the memory location you have your backup stored on.
6. Once you have highlighted your selection, tap the power button.
7. On the next screen, press the VOLUME DOWN BUTTON once to highlight the Restore option.
8. Now, tap the power button. This selects the Restore option.
9. Use the VOLUME UP or VOLUME DOWN buttons to select the folder that contains the backup you would like to restore. For example, I selected 2011-10-24.12.35.09/. Your folder will have a different name! Please keep this in mind.
10. Tap the power button. This choses the folder you have selected and offers a new menu.
11. Using the VOLUME UP or VOLUME DOWN buttons, select – Yes – Restore.
12. Again, tap the power button.
13. Now, wait, the restore takes about 10 minutes to complete. Once it is complete, you should be back at the Droid X2 Recovery GFAN.COM screen.
14. Now press the power key since the menu selection is already on Reboot system now.
15. You have successfully restored a bootstrap recovery backup from your Droid X2.
Again, if you have any questions, or comments, either post them here, or PM me! Thanks all!
Ciao!
Thanks for all the tutorials. Hopefully this keeps the noob post to a minimum.
booked said:
Thanks for all the tutorials. Hopefully this keeps the noob post to a minimum.
Click to expand...
Click to collapse
Hey, anything I can do to help. I also work a helpdesk, in addition to being a sysadmin, so, I know how important good tutorials are. Thanks for the kudos!
U need to add a step tho
After pressing install recovery make sure phone is plugged into an outlet via wall charger
That is the one step most missed and should be in capital letters
I know its in the portions below but the initial recovery install and entering steps don't have it lol
And even tho u say read all some won't lol
GREAT JOB!!! I am LOVING THESE!! THEY ARE PERFECT AND EXACTLY WHAT IS NEEDED. These NEED TO BE STICKIED BY TOMORROW AS they are the easiest to read and follow and are exactly the type of write up that should be easily found at all times.
ashclepdia said:
U need to add a step tho
After pressing install recovery make sure phone is plugged into an outlet via wall charger
That is the one step most missed and should be in capital letters
I know its in the portions below but the initial recovery install and entering steps don't have it lol
And even tho u say read all some won't lol
GREAT JOB!!! I am LOVING THESE!! THEY ARE PERFECT AND EXACTLY WHAT IS NEEDED. These NEED TO BE STICKIED BY TOMORROW AS they are the easiest to read and follow and are exactly the type of write up that should be easily found at all times.
Click to expand...
Click to collapse
You are correct, I just tried it and when you tap the recovery mode button, without being plugged into power, it turns the phone off. Thanks! I've updated the OP.
The thing is the last step in the section says tap recovery mode. If u do that and and u aren't plugged in it will just reboot the phone which may confuse someone as to why it didn't go to recovery mode.
Just trying to eliminate any confusion as these should be stickied and everything else about them won't cause any confusion of done right except for that step.
CONGRATULATIONS MOON SHADOW on your sticky status
This is. Going to be a good day for the x2 I can feel it
Thank you MS.. great work.
Could please add: only "adding spaces" will break md5 sum check. Use / continue the dot format and rename is fine.
Also in the clockworkmod folder create and empty file named : ".hidenandroidprogress" and progress "files being copied" will be suppressed speeding up the action.
I have changed the name of my backups before by adding a description word at the end like .eclipse and never had a problem with restoration.
Edit::this is just a confirmation to above post
One heck of a tut to say: go into recovery, click Backup and Restore, Backup, External..Click restore to ... restore.
Sent from my DROID X2 using xda premium
X0dus said:
One heck of a tut to say: go into recovery, click Backup and Restore, Backup, External..Click restore to ... restore.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Dude, you have seen many of the posts noobs make... Heck, *I* posted one like that! They (okay, read *we*) can have the directions right in front of them and still want a baby step by baby step procedure. I've written WAY to many Standard Operating Procedures, so something like this is really simple for me to cook up. Anyhow, you are correct... I typed a whole bunch just to say that...
skwoodwiva said:
Thank you MS.. great work.
Could please add: only "adding spaces" will break md5 sum check. Use / continue the dot format and rename is fine.
Also in the clockworkmod folder create and empty file named : ".hidenandroidprogress" and progress "files being copied" will be suppressed speeding up the action.
Click to expand...
Click to collapse
I only put information in the tutorial that I personally have done or verified. I have verified that renaming the folder and/or file won't break the restore. I have not verified the speed up. Plus, I think most noobs want to see something happening. Or, at least, I do... For now...
ashclepdia said:
CONGRATULATIONS MOON SHADOW on your sticky status
This is. Going to be a good day for the x2 I can feel it
Click to expand...
Click to collapse
Thanks dude! I really appreciate the kudos! This is my contribution to the DX2 community. Right now there are a couple of devs working on good things, so instead of poking around the OS and breaking something, I'll leave it up to them... Unless it is something that I think I just have to have, then I'll start mucking around in my system, and break something... When I had the Samsung Continuum, we had one dev that was willing to work with us, so I did quite a bit of poking and prodding, and breaking.
Well done sir. Since I got moved to the DX2 by a insurance replacement I have been slightly discouraged with the info I find on it. Posts like this, while some people scoff at the simplicity, are extremely needed.
Now that we have Liberty here now, along with some cool Atrix ports, Eclipse and so on I think the DX2 scene is getting a little prettier. I will be sharing out your fine tuts.
Thank you for this as well. I have these bookmarked!
Updates, Lost Info & ZIPS
The bootstrap works great. I did notice after recovery all my personal little preferences, even ringtone was lost. All other rooted customizations were in tact.
A couple questions:
Are there automatic updates?
Do I launch the "Update.zip's"?
Install zip from SDCARD?
Thank you for such a wonderful product and safeguard for all our hard work.
Mark~
inchga said:
The bootstrap works great. I did notice after recovery all my personal little preferences, even ringtone was lost. All other rooted customizations were in tact.
A couple questions:
Are there automatic updates?
Do I launch the "Update.zip's"?
Install zip from SDCARD?
Thank you for such a wonderful product and safeguard for all our hard work.
Mark~
Click to expand...
Click to collapse
Not quite sure why things were "lost". A nandroid backup backs up your system and restores it to the exact same state, or at least, that has been my experience with it.
Not sure what you mean by "automatic updates". If you are asking whether or not the nandroid backup automatically updates itself? The answer is no. This is a 100% manual process for our phone... For now, at least until we get a full custom recovery for it.
There is no need to launch an update.zip, unless you have a zip file that you want to flash to your phone. Usually, we use the install other zip files option for that... But, that's another topic. I've been considering doing a tutorial on flashing .zip files...
See the above paragraph for the install ZIP from SDCard. Same thing. Installing a zip file is essentially flashing a portion of your phone.
http://forum.xda-developers.com/showthread.php?p=19095250#post19095250
Speedup
skwoodwiva said:
http://forum.xda-developers.com/showthread.php?p=19095250#post19095250
Speedup
Click to expand...
Click to collapse
I don't think that app will work with the DX2 as we do not have "real" CWM recovery. We have a hijacked charge mode recovery. Anyone with a DX2 try this yet?
No it is not any version otherthan the features of all cwm recoverys, ours included. This is the speedup I mentioned previously. This evidence of .hidenandroidprogress working. Once booted all cwr are the same.
skwoodwiva said:
No it is not any version otherthan the features of all cwm recoverys, ours included. This is the speedup I mentioned previously. This evidence of .hidenandroidprogress working. Once booted all cwr are the same.
Click to expand...
Click to collapse
Ahhh, got it. I think the advanced users will do just fine without the progress bars, but for a noob, they usually want to see something happening. Thanks for the info!
Ciao!
Related
i currently have the TNT 4.4.0 ROM installed but I was looking to switch to the Vegan Ginger ROM and also to install pershoots kernel. are they compatible? how would i go about this without bricking the device? theres a lot of stuff here about firmware versions and incompatbilities and bricking and stuff and im not really sure about the process.
thanks in advance for your help?
Here is a detail step by step instruction on how to root, install a rom, etc.
http://forum.xda-developers.com/showthread.php?t=865245
I highly recommend Calkulin+Clemsyn combo rom. It's super fast, stable, and is based on the TnT stock rom. Very easy to use for newbies.
PS - with the rom I linked to, market fix and flash have already been applied. All you need to do is flash root and the Calkulin+Clemsyn combo rom and you're set.
what about all of that wiping and stuff. i have to do that also, correct? can any step of this completely brick the device?
thanks again!
None of the steps will brick your device however i would recommend an iPad
joshtb86 said:
what about all of that wiping and stuff. i have to do that also, correct? can any step of this completely brick the device?
thanks again!
Click to expand...
Click to collapse
Ok, here are the instructions, since I feel particularly good today on my day off.
(1) Follow the instruction on that other link for installing ClockworkMod.
(2) Create a folder in your sdcard name "rom" or "ROM" or "hoogabooga" or whatever name you want. Just make sure you remember the folder.
(3) Download the file I have included in this post (down below) called Calkulin's_FORMAT_ALL.zip.
(4) Download your choice of rom. There are now half a dozen to choose from. Calkulin+Clemsyn combo is the fastest and most stable according to my experience.
(5) Put those roms into that "hoogabooga" folder you created in your sdcard. Turn off your gtab.
(6) Startup into clockworkmod by pressing the power button and the volume + button and keep pressing the volume + button until you see something appearing on the upper left hand side of the screen during the birds.
(7) Scroll up and down using the volume control. Go down to where it says "install zip from sdcard" and press the house button.
(8) Choose zip from card.
(9) Go to your hoogabooga folder and choose Calkulin's_FORMAT_ALL.zip.
(10) Press the back button and go to advance.
(11) Choose the 2nd choice where it says wipe dalvik cache.
(12) Go back and pick install zip from sdcard again. This time, choose the rom that you chose.
(13) After it finishes "installing", reboot. Note that the first time the device boots into a new rom it will be very slow. Just let it sit there and do its thing. If you try anything at this point, you will screw up your machine. So, just let the darn thing boot up, please. We got enough users coming in here complaining about why their machine is screwed up because they did something while it's booting up. Good god...
Please be aware that I wrote the instructions thinking you have common sense. In other words, use common sense. Where it says "running" or "installing" or whatever then you're suppose to wait. Don't just follow the instructions blindly.
Invest some time in setting up nvflash. It's much less stressful with a safety net.
http://forum.xda-developers.com/showthread.php?t=861950
Don't even think about an iPad.
My problem with nvflash is that it's newbie unfriendly. I was a newbie not too long ago and I can tell you nvflash looked like a nightmare.
Unless the user does something stupid like interrupting a startup process, the gtab is fairly hard to brick.
And as always, I highly recommend getting rid of the gtab and buy an ipad. Less whiners for us to take care of. Let apple take care of them. Apple already got an army of whiners. I say we let them have a few more.
goodintentions said:
And as always, I highly recommend getting rid of the gtab and buy an ipad. Less whiners for us to take care of. Let apple take care of them. Apple already got an army of whiners. I say we let them have a few more.
Click to expand...
Click to collapse
I know this is sarcasm, crossed with a political statement, spliced with some frustration with newbies. But for me it comes off as a dig at the OP.
The nvflash discussion has been had elsewhere, however as an android modding newbie, following Roebeet's NV flash tutorial (due to his constant encouraging) has made mucking around with my Gtab 10x more enjoyable, knowing that I have a way to easily start from scratch. And it's near impossible to set up nvflash in a hurry after you have soft bricked.
Josh, the tutorial above is excellent, and it will certainly get you to where you want to go. But if you hit one of the gtab landmines (trying out 1.1 to 1.2 for example) nvflash will be your best friend.
brettdwagner said:
I know this is sarcasm, crossed with a political statement, spliced with some frustration with newbies. But for me it comes off as a dig at the OP.
Click to expand...
Click to collapse
On the contrary, I stand behind 100% what I said. Like I said before, I fix computers as a side job to bring in an extra dollar or two to go out and party... I mean to pay my bills. Most people, when it comes to computers and gadgets, like to whine more than they like to enjoy their machines. I'm sure apple's got a whole division specializing in dealing with whiners since they already got an army of whiners.
Whiners have nothing to do with being a newbie or not. It's got to do with the spoon-feed-me attitude. Over the months, I have seen complaints about the gtab by dedicated whiners. Everything from "it's .3 lb heavier than the ipad which makes it too heavy!" to "why you no give me honey!" Frankly, neither VS nor this community is properly equipped to deal with whiners. Why not send them to apple and let it be apple's problem?
I'd like to think I'm a resourceful person. When I see a problem, instead of complaining I try to find a solution. I see the gtab as an investment. So, instead of just watching videos on it I have incorporated it into my daily work. I crinch in pain every time I see people whine before they even tried to find a solution. So, why not send them to apple?
I don't mind it for the true whiners, but since you post this everywhere it looks like your trying to fend off any and all new users who have questions. The subtext of "get an iPad" is 'you can't handle this and we don't really want you here.'
That said, your post above went above and beyond to help out the OP. Your a mystery to me goodintentions
brettdwagner said:
I don't mind it for the true whiners, but since you post this everywhere it looks like your trying to fend off any and all new users who have questions. The subtext of "get an iPad" is 'you can't handle this and we don't really want you here.'
That said, your post above went above and beyond to help out the OP. Your a mystery to me goodintentions
Click to expand...
Click to collapse
It's my day off.
goodintentions said:
Ok, here are the instructions, since I feel particularly good today on my day off.
(1) Follow the instruction on that other link for installing ClockworkMod.
(2) Create a folder in your sdcard name "rom" or "ROM" or "hoogabooga" or whatever name you want. Just make sure you remember the folder.
(3) Download the file I have included in this post (down below) called Calkulin's_FORMAT_ALL.zip.
(4) Download your choice of rom. There are now half a dozen to choose from. Calkulin+Clemsyn combo is the fastest and most stable according to my experience.
(5) Put those roms into that "hoogabooga" folder you created in your sdcard. Turn off your gtab.
(6) Startup into clockworkmod by pressing the power button and the volume + button and keep pressing the volume + button until you see something appearing on the upper left hand side of the screen during the birds.
(7) Scroll up and down using the volume control. Go down to where it says "install zip from sdcard" and press the house button.
(8) Choose zip from card.
(9) Go to your hoogabooga folder and choose Calkulin's_FORMAT_ALL.zip.
(10) Press the back button and go to advance.
(11) Choose the 2nd choice where it says wipe dalvik cache.
(12) Go back and pick install zip from sdcard again. This time, choose the rom that you chose.
(13) After it finishes "installing", reboot. Note that the first time the device boots into a new rom it will be very slow. Just let it sit there and do its thing. If you try anything at this point, you will screw up your machine. So, just let the darn thing boot up, please. We got enough users coming in here complaining about why their machine is screwed up because they did something while it's booting up. Good god...
Please be aware that I wrote the instructions thinking you have common sense. In other words, use common sense. Where it says "running" or "installing" or whatever then you're suppose to wait. Don't just follow the instructions blindly.
Click to expand...
Click to collapse
okay thanks a lot. i read in the clem+calk ROM thread that some people used CWM, the most recent version, not the .8 version which i have been using. is that correct? or should i use the .8 version?
so all the steps say to download this stuff to your sd card, but i cant actually access my microsd card from CWM. i can only access the folder called SDCARD which is actually my internal memory. should i still download it there? is there another way to access my microSD from CWM? is it okay to leave it on the sdcard folder which is my internal drive?
thanks again!
Your sdcard is your internal space. The microsdcard is called sdcard 2. Cwm only access your sdcard which is your internal.
I am now making post that there really shouldn't be any need for, because all that's in here is already covered elsewhere. 100% Apparently not easy enough to find for newcomers, so I'm making an attempt to help info collection.
NOTHING here is my work! All I’ve done is trying to make easy to follow instructions to other people’s hard work. Those people deserve your thanks, not me!
I’m a newbie myself and that’s why I can say that this really is very easy! If I can do it without problems, so can you! I try not to chat away too much in the instructions. Make regular searches, here or Google for more info. I found it, so surely you can too! Any questions? Well, being a noob myself I probably can't answer. Google is a very good friend of mine though...
Please do not ask questions through pm. It's better if people that know more than I do get a chance to answer them in the thread instead!
You need to know how to burn an sd image. Separate instructions to that after the other instructions if you don’t.
Step 1: Establish what it is you want to do! Choose A, B or C
A: You do not want to touch the internals of your NT but want to try CM10 anyway
B: You want to stay in the BN environment but would like to be able to install apps from elsewhere (for example Google Play Store)
C: You want to get rid of BN and install CM10 instead.
A: Run CM10 from sd card – no root required
This should work on 8GB Tablet as well as 16GB
When you boot into the card you’re running Android ICS. Remove the card and you’ll boot to internal BN operating system. (Or keep the card in, boot to Cyanoboot Menu and choose “internal boot”)
Ready-made card image download links to be found here: http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
It’s a large download (around 500 MB), but it is a ready-made sd card image. As it says in the instructions there, you’ll more than likely want to expand the user partition to take full advantage of the card, but that’s covered in his instructions.
There are other, more manual ways to make these cards as well. Also covered both in that blog and here at XDA! Go search!
B: Root the Tablet
This works on both 8GB and 16 GB Tablet.
“Rooting” is like unlocking your device, giving you access and control over it. You’re still running BN operating system though. Several excellent root guides here on XDA.
For example: http://forum.xda-developers.com/showthread.php?t=1488035
Or http://forum.xda-developers.com/showthread.php?p=21275927#post21275927
The first one (Brian’s) require a 2 GB card the other one (Albert’s) just needs a very small card. (I think 128 MB would do, but I don’t have any that small to try)
Both give good instructions in their topics.
Both install gApps.
If you want to block OTA updates from BN, go to Play Store and find NT Hidden Settings. Even if it got installed with the root it’s probably not latest version and doesn’t have the Block OTA function.
C: Installing CM10 internally
***8GB owners must make sure to use ROM that works with their device!***
Since I’m a noob I look for easy way, and this is very easy and needs very little know-how!
***Warning! CWM is a very powerful tool. Do not "wander around" and "experiment" with stuff without doing proper research! Seriously! DON'T!***
1. You need a bootable CWM card. Instead of making my own I use Albert's root image from B (above) because this image includes CWM 5.x.x. I use this to flash a higher version CWM internally. I erase the zip files from the card to make room for a flashable CWM 6.x.x
2. Find a flashable CWM 6.x.x I found mine through http://forum.xda-developers.com/showthread.php?t=1640958
I use the one named "flash_cm9-10_cwm v6...." Download and copy to your sd card.
3. Boot into the sd-card and it should take you to CWM 5.x.x. environment.
I guess a backup of you current system would be a good thing (even though I admit to skipping that myself). To backup you'll probably need another card if you're using "The Albert Card" now, because I doubt it's enough room on that.
You navigate with the volume rocker, go back to previous menu with “power” and confirm choices with “n”
Choose “install zip from card” – “choose zip from card” – your CWM zip
See warning above!
4. Power off and prepare your sd card for ROM flashing. (If you’re working with just one card you will need to format it with SD Format or similar to get it back to full capacity.) Put your CM10 ROM zip and the appropriate gApps zip on the card.( It doesn’t matter if there’s other stuff on the card, so you don’t have to format it because of that!). I will not link to a specific ROM. Make your own choice but be sure it works for your model and also make sure you use the right gApps!
5. Reboot into Cyanoboot. This took me a couple of attempts to get right.
From powered down device, press power and right after that press and hold "n", You should boot into Cyanoboot and get the boot menu. Choose "Internal recovery" and you should get into new CWM
6. I don’t know how much clearing is needed, but I prefer to clear pretty much everything to make sure of a clean install. Cache and Dalvik I always clear.
***DO NOT format anything unless you knwo what you're doing! *** (See Satan's posts below)
7. Flash ROM and gApps same way as you flashed the CWM 6.x.x (install zip from card – choose zip from card) reboot and go!
How to burn an sd-image:
I use Win32Diskimager. Download link in Albert’s root topic (and numerous other places!!)
Unzip into a folder.
(I also copy my various img files to that folder to have them easily available)
No need to install, just run by doubleclicking the EXE in the folder.
Make sure the device letter really is your sd card.
Click on the blue folder and navigate to your img file, choose it and “write”.
It will take some time if it’s a large img, but that’s what the progress bar is there for, isn’t it?!
Nice work ,
But you should add 'do not format any partition ' warning. Android users coming from other devices might do this by default during flashing rom.
Almost every one with bricked tablets has tried formatting partitions.
Sent from my ST21a
Thanks Satan! I did not know that! Will do!
Good
Veronica had made sticky thread to reduce number of bricked tablets, but looks like some people missed it.
To be more specific,
Do not format rom, boot, bootdata, and factory.
http://forum.xda-developers.com/showthread.php?t=1644862
satan89 said:
but looks like some people missed it.
Click to expand...
Click to collapse
It looks like a lot of people miss a lot of things...
satan89 said:
Good
Veronica had made sticky thread to reduce number of bricked tablets, but looks like some people missed it.
To be more specific,
Do not format rom, boot, bootdata, and factory.
http://forum.xda-developers.com/showthread.php?t=1644862
Click to expand...
Click to collapse
+1000
Do not format especially the rom partition and, most critically, the factory partition which respectively contain a set of small files with device-specific unique data (not only Serial No. but also MAC address, public/private key certificates, etc.) and the backup archive copy of the same data files (/factory/romdata.zip).
Unfortunately, I've seen some "unbricking" tools (including some that are very frequently cited/recommended on these NT forums) reformat/zero-out and flash over these 2 partitions. The end result being, even in the event the "bricked" NT gets "restored to stock", depending on the specific tool used it could be carrying device-specific data of someone else's (e.g., tool developer's) NT.
EXACTLY!
satan89 said:
Good
Veronica had made sticky thread to reduce number of bricked tablets, but looks like some people missed it.
To be more specific,
Do not format rom, boot, bootdata, and factory.
http://forum.xda-developers.com/showthread.php?t=1644862
Click to expand...
Click to collapse
I think this is exactly what happened to my NT. Took me weeks of researching (I don't have a lot of free time) to figure out how to restore my 16GB NT.
Help
Im trying to single boot CM10 from sd card without touching nook os. I am using guide (CM10.0 Jellybean SDCard IMG for Nook Tablet (12/31) FINAL)
I have tried for hours using different methods also and cant even get it to boot to CM, no CM logo at all. I have a BNTV250 NT on 1.4.3. I have tried multiple sd cards, I am using a Sandisk 8gb class 6.
In a nutshell all I should have to do is
-Format the card with SD formatter,
-Extract the (Extract cm10_xxxxxx_sd_hd.img from cm10_xxxxxx_sd_hd.7z/rar)
-Use Winimage to write the image to the SD card, correct??
The Nook still refuses to boot into Cyanogen, just boots up normal every time!
same with every procedure i have tried,
Any pointers????
Have you tried putting the sd-catd in the powered down Tablet and then insert the charger cable, connected to the charger?
Many Tablets have difficulties booting into sd other ways,
asawi said:
Have you tried putting the sd-catd in the powered down Tablet and then insert the charger cable, connected to the charger?
Many Tablets have difficulties booting into sd other ways,
Click to expand...
Click to collapse
No, I have not, will try now.........ty
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
HOLY ****!!!! I LOVE YYOU!!:laugh::laugh::laugh::laugh::highfive::victory:
That worked, I cant believe it. Why is this not written anywhere??
LOL! :laugh: Glad you got it working!! :good:
Any clue of how to get rid of booting that way? I'm not always with a USB cable witj me.
Enviado desde mi Nexus 4 usando Tapatalk 2
I've never had to do it that way myself so I really don't know. You could try pressing the "n" buttons right after the power button and holding it for a few seconds.
Actually not being able to boot into SD card easily is the reason some install internally instead.
Sent from my NookTablet using Tapatalk 2
asawi said:
I've never had to do it that way myself so I really don't know. You could try pressing the "n" buttons right after the power button and holding it for a few seconds.
Actually not being able to boot into SD card easily is the reason some install internally instead.
Sent from my NookTablet using Tapatalk 2
Click to expand...
Click to collapse
Tried doping that with no luck. After 8 or 10 attempts magically boots todo cm. Thanks.
Enviado desde mi Nexus 4 usando Tapatalk 2
Alright, just got cwm 6.x installed and now ready to install rom, just wanting to verify that I should still "wipe data/factory reset" and "wipe cache partition"? That is different from "formatting" correct? I don't wanna brick this thing without confirmation. Thanks for the awesome guide!
edit: Ignore the wipe question, found it, thank again for the guide, I will let you know how the install goes!
ThePhantom97 said:
Alright, just got cwm 6.x installed and now ready to install rom, just wanting to verify that I should still "wipe data/factory reset" and "wipe cache partition"? That is different from "formatting" correct? I don't wanna brick this thing without confirmation. Thanks for the awesome guide!
edit: Ignore the wipe question, found it, thank again for the guide, I will let you know how the install goes!
Click to expand...
Click to collapse
Thank you very much for putting this together, it was very helpful!
grizzlayleslay presents:The Complete Guide on Tinkering with your
Motorola Milestone X2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Greetings and Welcome!
If you're here, you have a Motorola Milestone X2. You have 2.3.6 Gingerbread, and you probably hate the Blur stuff forced upon you in 2.3.6. We know. This is a dual-core phone and it feels like you're not getting the full potential out of it. Thanks to the courage and hard work of many members, we CAN get more out of this phone. Believe the impossible.
What follows is the most thorough guide on XDA for tinkering with your Milestone X2. There are many parts to this guide, and I recommend reading through all of it if you plan on tinkering with your Milestone X2.
Before going forward, I must repeat: This guide is for, and only for, Gingerbread 2.3.6 running on your Motorola Milestone X2.
I'm sure some parts of the guide can be utilized for the Droid X2 but considering that us Milestone X2 users are lumped into the Droid X2 forum and must frequently scavenge several topics before getting the documentation we need, this guide is written under the assumption that you have a Milestone X2 and that you're modifying it.
This guide is not for Android 2.3.4, 2.3.5, 2.3.batman, or anything NOT called 2.3.6. The Milestone X2 was shipped with 2.3.6 so this guide is written FOR 2.3.6, and will not be revised for any other version of 2.3. If you're not running 2.3.6 on the Milestone X2 and you choose to follow the guide anyway, that's your choice and I hold no responsibility for your gallivanting ways.
With that, let's go forward.
==================================================================
Table of Contents
Part 1: Back up the Personal Essentials
Part 2: Factory Reset Time
Part 3: Install and Update the Bare Essentials
Part 4: Rooting the Milestone X2 with 2.3.6
Part 5: Creating the Nandroid/BSR Backup
Part 6: Nandroid Restore Procedure
Part 7: Custom ROM Installation with DZK's CMOD10 2.9999999 Alpha
Part 8: Performance gains with CM10 and the MX2
Part 9: Performing an SBF Restoration on the MX2
==================================================================
REQUIREMENTS:
It is assumed that you have the following utilities handy before going forward:
A computer running Windows XP/Vista/7/8
A computer ALSO running Linux
A Motorola Milestone X2 with the USB cable that it came with when you bought it.
A Wall Charger for your Milestone X2
It is also assumed that you understand the following principles of Android tinkering:
Your mileage may vary.
I take no responsibility what you do to your Milestone X2.
I take no responsibility if you use a different phone NOT called the Milestone X2 and end up breaking it.
==================================================================
REFERENCES:
Part 4: Guide adopted from user clcrawl here: http://forum.xda-developers.com/showthread.php?t=1405077
Part 4: How to tell if your phone is rooted: http://www.androidcentral.com/is-my-phone-rooted
Part 5: Guide adopted from Moon Shadow here: http://forum.xda-developers.com/showthread.php?t=1318083
Part 7: DZK's original Thread: http://forum.xda-developers.com/showthread.php?t=1912280
Part 7: Lrs121's modification Thread: http://forum.xda-developers.com/showthread.php?t=1914238
Part 8: sbf_flash on Linux: http://forum.xda-developers.com/showthread.php?t=1321061
==================================================================
CREDITS:
This guide would simply not exist without the help & efforts of the following XDA users:
DragonZKiller (creator of the original CM10 mod for the Droid X2)
Lrs121 (creator of the port of dragonzkiller's port of CM10 for the Milestone X2, hoster of the nTelos sbf file we use)
clcrawl (creator of the original 2.3.6 Root thread for the MX2)
Moon Shadow - NM (creator of the Nandroid thread for the DX2/MX2)
imchairmanm (creator of the sbf_flash thread for the MX2)
Booga Booga (fellow MX2 user and all-around badass resource for creating this guide)
Part 1: Back up the Personal Essentials
If you have Contacts, back them up.
If you have files on your MX2 or SD card, back them up.
As always, before doing ANYTHING with your MX2, back up the important things you need regardless. If you don't back up your personal files, you risk losing them. So back them up. Put the files on a USB drive, CD, external hard drive, whatever. Keep it away from your MX2 where it can't fall in the crossfire of your modding.
Part 2: Factory Reset Time
Before going forward with any custom ROM's, it is absolutely imperative that you have a place to go back to should something go wrong, or if you want to revert back to the stock OS of your MX2. The best way to do this is to have the freshest, cleanest version of the stock OS on your MX2. Doing a factory reset gets you that freshest, cleanest version.
1) Go to your App Drawer, go to "Settings".
2) In Settings, go to "Privacy Settings".
3) Under "Personal Data" at the bottom, select "Factory Data Reset".
4) You'll be prompted with a message explaining all the important stuff about the Factory Data Reset. There are two checkboxes for erasing Internal and SD storage, this is not mandatory as it only wipes apps & media files but it's up to you if you want to do that. When ready, select "Reset Phone".
This process takes a varying amount of time, but eventually it will complete.
5) You're done!
Part 3: Install and Update the Bare Essentials
Now that the MX2's been reset, you'll have the opportunity to add your Google Account, and update apps. But wait! We want as barebones of a Gingerbread install as possible, so just update & install these apps:
1) Google Play Store
2) Stock Apps
3) Superuser (for Part 4)
4) Android Terminal Emulator (for Part 4)
5) You're done!
Part 4: Rooting the Milestone X2 with 2.3.6
Let's review before rooting:
You've backed up the bare essentials
You've Factory Reset your MX2
You've updated the Google Play store & the stock apps, AND installed Superuser AND a Terminal app.
Okay, let's go forward.
1) Install the Motorola Device Manager for Windows, here: http://www.motorola.com/consumers/v...009a0210VgnVCM1000008806b00aRCRD&pubid=987654
2) Restart your computer. Maybe you don't think you need to, but I will. Never hurts to be safe.
3) While your computer reboots, enable USB Debugging on your MX2. Here's how you do it:
Go to your "App Drawer", select "Settings", go to "Applications", select "Development", and select the checkbox for "USB debugging".
4) Plug your MX2 into your computer. At this point it's installing the ADB drivers, essentially allowing your computer to talk to your MX2 over USB.
5) Download this file. http://www.mediafire.com/?z8yb4acyjp08ahf
6) Extract the zip file to a location that is easy to get to, and make sure all the files are extracted to the same folder. For ease of use, I suggest making a folder called "Root" in the C: drive, and putting all the files in that “Root” folder.
7) Put your MX2 into Fastboot Mode. Here's how you do it:
Unplug the MX2 from the computer.
Shut the MX2 off.
Hold down the Volume Down Button while pressing the Power Button.
After the MX2 turns on you should see "Fastboot" at the top of the screen.
Press the Volume Up Button to enter Fastboot mode. Your computer may need to install drivers if this is the first time you entered Fastboot mode, so let this happen BEFORE proceeding.
8) Start a command prompt on your computer.
9) Type the following commands:
cd \<DIRECTORY> where <DIRECTORY> is the folder you created. If you created the Root folder in C:\ it would be cd \root.
moto-fastboot flash preinstall preinstall.img
moto-fastboot reboot
10) Wait for the MX2 to reboot.
11) After it reboots, execute the following commands (in the command prompt you should still have open):
adb shell
/preinstall/su
12) On your MX2 you should see a prompt to Allow or Deny Superuser access, select Allow.
13) Execute the following commands (in the command prompt you should still have open)
mount -o rw,remount -t ext3 /dev/block/mmcblk0p12 /system
cp /preinstall/su /system/bin/su
chmod 6755 /system/bin/su
14) If you haven't yet, install a Terminal app on your MX2. I recommend "Android Terminal Emulator": https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
15) Open the Terminal app.
16) You'll be faced with a text entry prompt in the form of a $ symbol. execute the following command:
su
17) You'll be prompted with SuperUser asking for permission. Select "allow".
18) If the prompt changes from $ to #, it means you're rooted.
19) You're done!
Part 5: Creating the Nandroid/BSR Backup
Now that we're rooted, it's time to make a backup of the MX2 for future recovery. This will come in handy if at any point, you decide to roll back to Gingerbread or if something weird/bad goes wrong.
If you're confused by the term "BSR", it's because the Nandroid backup process on the MX2 hijacks the Charge animation screen when you're charging your MX2 from a wall outlet. Technically it's known as the Boot Strap Recovery, but this is what we do to get a Nandroid backup of our MX2's.
Here's how we make a Nandroid Recovery:
1) Install the BusyBox app from Google Play: https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
2) Run the BusyBox app and grant it SuperUser permissions.
3) Download the "Droid X2 Recovery APK" here (yes, it will work for the MX2): http://www.markhm1972.com/MotorolaDroidX2/MOTODX2_Bootstrap_signed.rar
4) Using an archive utility like 7zip, extract the .apk file from the archive.
5) Plug the MX2 into your computer, and enter it in USB Storage Mode from the dropdown.
6) Copy the .apk file to your MX2.
7) Open a File Explorer application (or install one if you don't have it).
8) Navigate to the folder where you copied the .apk file and select it to install it. If you're warned that your phone isn't set to install non-Market applications, it will allow you to go into the Settings, where you can select the checkbox for “Unknown Sources”.
9) If it doesn't launch immediately, you can find it in the App Drawer as an app called "System Recovery".
10) Once System Recovery has been launched, select "Install Recovery".
11) Select "Allow"? when Superuser asks for permission.
12) Wait about 5 seconds to ensure the Recovery Install has completed successfully.
13) Unplug your MX2 from the computer, completely. Make absolutely sure that your MX2 is NOT plugged into a USB port on your computer or in a USB hub.
14) Plug your MX2 into a Wall Charger. Plug the Wall Charger into a nearby electrical outlet.
15) Be absolutely certain you have followed Steps 13 and 14 to the letter. Your MX2 should NOT, for any reason whatsoever in the known universe, be connected in any way/shape/form to your computer right now.
16) I am incredibly serious, make sure you have followed Steps 13 and 14 EXACTLY!
17) Double-check time. If you've followed Steps 13 and 14 like a good owner, you may skip to Step 18. Even so, it doesn't hurt to read the entire checklist again:
DOUBLE CHECK THE FOLLOWING!
Take the Motorola factory USB cable and unplug it from everything. The computer, the wall charging block, the MX2, EVERYTHING!
Plug the micro USB end into the MX2.
Plug the male USB-A end into the wall charging block.
Plug the wall charging block into the wall.
Make sure the MX2 is plugged into the wall charger and plugged into the wall. NOT a USB hub, not a USB port on a computer, Not anything but the wall charger, and the wall charger is plugged into the wall.
18) Select "Recovery Mode". In 3-5 seconds the MX2 will appear to reboot. What it is actually doing is performing the hijack of the Power Off Charge Mode of the MX2. The MX2 actually powers off, but because the BSR hijacks the Charge Animation screen (the battery with the fuel level showing the amount of charge), it will look like it is booting up. In a sense, it is, but it will boot into the Bootstrap Recovery. The battery will continue to charge as well.
If you followed the previous steps correctly, the MX2 will reboot into a screen saying "Droid X2 Recovery GFAN.COM".
19) Press the VOLUME DOWN BUTTON 6 times. This should highlight the option to "Backup & Restore".
20) Tap the power button. This selects the Backup & restore option.
21) Use the VOLUME UP or VOLUME DOWN buttons to select the memory location you would like to store the backup on. If you have not enabled the SD Card flip, or you don’t know what the SD Card flip is, store the backup on the External SD Card. I highly recommend backing up to an external SD Card.
Internal SD Card = the 8GB internal, non-removable memory. (The Internal SD Card has a little over 6.4GB of usable storage space.)
External SD Card = your removable MicroSD card.
22) Once you have highlighted your selection, tap the power button.
23) On the next screen, tap the power button again, since the Backup option is already selected.
24) Now, wait, the backup takes about 10 minutes to complete. Once it is complete, you should be back at the "Droid X2 Recovery GFAN.COM" screen, with a message at the bottom of the screen saying “Backup complete!”
25) Now press the power key since the menu selection is already on Reboot system now.
26) You have successfully made a bootstrap recovery backup of your Milestone X2.
Note: The bootstrap recovery backup does not erase old backups. You must do that yourself from within your preferred file explorer. The backups are located in /mnt/sdcard/clockworkmod/backup/YYYY-MM-DD.HH.mm.ss.
YYYY = the 4 digit year. 2011 for example.
MM = the 2 digit month. Such as 10 for October.
DD = the 2 digit day. Such as 24 for the 24th day of October.
HH = the hour in 24 hour time. Such as 14 for 2PM.
mm = the 2 digit minute of the hour. Such as 34 for 34 minutes
after 2PM, or 2:34PM.
ss = the 2 digit seconds the backup was created. Such as 17 seconds, or 2:34:17PM
Note: DO NOT add SPACES to any of the folder or backup names as this will BREAK your recovery!
27) You're done!
Part 6: Nandroid Restore Procedure
If you find that you need to restore a Nandroid backup, here's how you do it:
1) Make sure the MX2 is plugged into the wall charger and plugged into the wall. NOT a USB hub, not a USB port on a computer, Not anything but the wall charger, and the wall charger is plugged into the wall.
2) Now, power off the MX2. The MX2 will power down, then power back up and boot into the "Droid X2 Recovery GFAN.COM" screen.
3) Once in the recovery menu, press the VOLUME DOWN BUTTON 6 times. This should highlight the option to Backup & Restore.
4) Tap the power button. This choses the Backup & Restore option.
5) Use the VOLUME UP or VOLUME DOWN buttons to select the memory location (internal or external SD Card) you have your backup stored on.
6) Once you have highlighted your selection, tap the power button.
7) On the next screen, press the VOLUME DOWN BUTTON once to highlight the Restore option.
8) Now, tap the power button. This selects the Restore option.
9) Use the VOLUME UP or VOLUME DOWN buttons to select the folder that contains the backup you would like to restore. For example,2011-10-24.12.35.09/. Your folder will have a different name! Please keep this in mind.
10) Tap the power button. This choses the folder you have selected and offers a new menu.
11) Using the VOLUME UP or VOLUME DOWN buttons, select "Yes Restore".
12) Again, tap the power button.
13) Now, wait, the restore takes about 10 minutes to complete. Once it is complete, you should be back at the "Droid X2 Recovery GFAN.COM" screen.
14) Now press the power key since the menu selection is already on Reboot system now.
15) You have successfully restored a bootstrap recovery backup from your MX2.
16) You're done!
Part 7: Custom ROM Installation with DZK's CMOD10 2.9999999 Alpha
Now we delve into the nitty-gritty of getting the most of the MX2, all thanks to the XDA user dragonzkiller, whom has spent countless hours working on a port of CyanogenMod 10 (aka Android 4.1) to work on the Droid & Milestone X2.
BEFORE DOING ANYTHING ELSE, I HIGHLY RECOMMEND COPYING THAT NANDROID BACKUP FROM YOUR MILESTONE X2 TO A LOCATION NOT ON OR NEAR THE MILESTONE X2. Whether this is a USB Drive, CD/DVD, external drive, Dropbox, Google Drive, whatever. Put a copy there. Put copies in different places.
Now that you've copied your backup into one-or-more-but-preferably-more places, it's time to get the most out of our little Milestone X2.
First of all, again I give thanks to DragonzKiller for his work on this port of CyanogenMod 10. Without dragonzkiller, we wouldn't be here.
I must point out that us MX2 users have to use a port of DZK's port of CM10, by user Lrs121. DZK's port of CM10 includes a kernel_check during installation that will NOT work on the MX2, because it requires 2.3.4 in order to flash it. As the MX2 only comes shipped with 2.3.6, the only option is to bypass the kernel_check requirement.
User Lrs121 provides us with a port that bypasses this kernel check, allowing us to run DZK's port on our MX2.
So thank you, Lrs121, for providing us with this port.
Also, as an MX2 user you will HAVE to install the WiFi patch, or your Wifi will not work. Period.
So, here we go:
1) Download the following files:
The JellyBean 4.1.x "gapps" file: http://goo.im/gapps
The "cm10-20130112-unofficial-mx2.zip" file on Lrs121's Google Drive: https://docs.google.com/file/d/0BzuX6WLejxQwakVXcHVSV1R2c3c/edit
The WiFi Patch for the Milestone X2: http://www.mediafire.com/?e7cbyc9lmdj3p7g
2) Place these files on your MX2, preferably on an external SD Card. For convenience sake, I placed them in a folder called “cm10” on my external SD card.
3) Go back to Part 5 of this guide, Step 17. Run the double check. Unplug your MX2 from your computer. The MX2 MUST be plugged into a wall charger and plugged into an outlet.
4) Go to your App Drawer, select "System Recovery" and select "Recovery Mode". The MX2 will reboot into a screen saying "Droid X2 Recovery GFAN.COM".
5) Press the Volume Down button 5 times, highlighting “Install zip from SD Card” (this is your external SD Card). Press the Power button to select it. Press the Volume Down button once to select “choose from sd card”, and press the power button to select it. Navigate to your custom folder and select the cm10 zip file. Press the power button again. You'll be taken to a “Confirm install? THIS CAN NOT BE UNDONE” prompt. Press the Down Volume button 7 times to highlight the “Yes – Install cm10.zip” file, and press the Power button. Wait for it to complete installation. When it's done, it'll declare "Install from sdcard complete".
6) Repeat Step 5, this time installing the "gapps.zip" file. Wait for it to complete installation. When it's done, it'll declare "Install from sdcard complete".
7) Repeat Step 5, this time installing the "MX2_CM9_WIFI.zip" file. Wait for it to complete installation. When it's done, it'll declare "Install from sdcard complete".
8) Press the Down Volume button 5 times to select "Go Back". Press the power button to select it. Now, press the Down Volume button 3 times to select "Wipe DATA/Factory reset", and press the power button. Press the Down Volume button 7 times to select "Yes", and press the power button. Now, press the Down Volume button to select "Wipe CACHE partition". Press the Down Volume button 7 times to select "Yes", and press the power button.
9) You should be back at the main GFAN.com screen at this point, with the selection highlighted on "Reboot system now".
10) Press the power button to reboot your MX2.
11) WAIT. If you followed the steps correctly, the loading screen for CyanogenMod will appear. Soon enough, you'll be able to configure your MX2 and add apps.
12) You're done!
Part 8: Performance gains with CM10 and the MX2
The RAM in the MX2 is a bit limited, so we do have to keep in mind that while Android 4.1.2 gives us performance gains, this is no Nexus 4.
As user Booga Booga can attest to, less apps can mean greater performance. Here's what you can do to get even more out of your MX2.
1) Open the App Drawer, and go to Settings.
2) Go to Developer Options.
3) Scroll down to the "Drawing" heading.
4) Turn "Window Animation Scale" to OFF.
5) Turn "Transition Animation Scale" to OFF.
6) Turn "Animator Duration Scale" to OFF.
7) Reboot your MX2 (just because).
8) You're done!
Part 9: Performing an SBF Restoration on the MX2
If you're utilizing this part of the guide, that means you're either:
itching to go back to Gingerbread
you dun goofed (it's okay, we all do)
testing various builds of roms and wanting to start over
The SBF process is basically a reversal of installing your custom rom, where we revert to a stock version of Android. From there, we can then use a Nandroid backup to restore our MX2 to its former glory before we started tinkering. SBF-ing is a beautiful, metaphorical reset button.
For this guide, we'll be using the "sbf_flash" program and a Linux operating system.
Before going forward, I'm going to make this very obvious.
DO NOT USE RSD LITE UNDER ANY CIRCUMSTANCES WHATSOEVER.
I MEAN IT.
RSD LITE CAN REWRITE THE BASEBAND OF YOUR MX2, PERMANENTLY BRICKING IT FROM WORKING WITH YOUR CARRIER. THE BEST THING THAT CAN COME FROM USING RSD LITE IS THAT YOU'LL HAVE TO TAKE YOUR MX2 TO YOUR CARRIER'S HEADQUARTERS TO BE REFLASHED, WITH A SMALL CHANCE THAT IT WILL ACTUALLY BE RESTORED.
DO NOT MAKE THE SAME MISTAKE I DID.
DO NOT USE RSD LITE UNDER ANY CIRCUMSTANCES WHATSOEVER.
For SBF restoration on the MX2, it is imperative that we use "sbf_flash" for Linux. Yes, this means if you don't have Linux, you'll have to get yourself a copy of Linux. Any distro of Linux will probably work but for this guide I will recommend you use either Wubi or Ubuntu.
1) Acquire this SBF file from user Lrs121: https://docs.google.com/folder/d/0BzuX6WLejxQwWUJXQjBFUG1sZUU/edit?docId=0BzuX6WLejxQwMXlvYUswblVIZzg
2) Download Linux if you haven't already, and run it.
3) Download the sbf_flash program here: http://blog.opticaldelusion.org/
4) Put sbf_flash and the SBF file on your Linux install.
5) Open a terminal in the directory where you have the sbf file and sbf_flash program. Type "chmod +x sbf_flash". This will make the sbf_flash file executable.
6) Turn off your MX2.
7) Hold down the Power Button and the Volume Down button until the MX2 displays "Fastboot" above the normal Motorola start-up screen.
8) Press the Volume Down button until it reads "RSD". Press the Volume Up button to select.
9) Plug your MX2 into the computer using the usb cord. Wait a few seconds to allow your computer to recognize the device.
10) In the terminal (still opened in the same directory as the sbf_flash program and the .sbf file), type "sudo ./sbf_flash nameOfSbfFile.sbf" (obviously you're going to want to change the last part to the actual name of the sbf file you have on your computer) and enter your password when prompted.
11) Allow the program to work. It'll take several minutes and your MX2 will reboot at the end.
12) At this point you'll have reverted back to 2.3.6 Android under nTelos. Refer to Parts 3-6 for re-rooting your MX2, and restoring from the Nandroid backup that you kept safely hidden somewhere (but obviously don't do all of Part 5, no need to backup again).
13) You're done!
GOING FORWARD:
First of all I want to point out that this guide belongs to all of us. You'll find no ego trip here. All I've done is compile everything into one simple resource for us MX2 users to utilize and tested it out to make sure it worked. Everyone credited in the OP are the true trailblazers, as without their hard work I'd have nothing to compile together into a guide in the first place.
Even so, the most important principle of this guide is that it's comprehensive, easy to read, and easy to reference. Any and all additions/modifications must keep this in mind. A clean guide is a happy guide!
Anyway...
Critiques & Reviews
All critiques & reviews of the guide are welcome.
If you find a spelling/grammatical/formatting error, kindly point it out so that I can fix it.
If you would like to add other custom Rom's for the MX2 like CM7 or CM9, let's talk about it!
I've been contemplating this, as many of the parts to the guide require downloading files.
Would anyone else find it beneficial if I compiled these files into timestamped .zip's and uploaded them somewhere based on Parts of the guide? Think files like "Part4.zip" that would include all the files needed for rooting.
If so, where would be a good place to host them?
grizzlayleslay said:
I've been contemplating this, as many of the parts to the guide require downloading files.
Would anyone else find it beneficial if I compiled these files into timestamped .zip's and uploaded them somewhere based on Parts of the guide? Think files like "Part4.zip" that would include all the files needed for rooting.
If so, where would be a good place to host them?
Click to expand...
Click to collapse
Bayfiles, mediafire, Google drive, a private server. Any where really. Also what you said about rsd lite isn't technically true, it isn't that the base band gets overwritten just that there are specific files meant for each different carrier aka prl, eri, ect that get overwritten by rsd lite when. Flashed with the ntelos sbf. Also you may think of adding on the secondary way of rooting involving the scripts I wrote giving people multiple ways to do one thing. Plus I get the bounus of having people try it out and find ways I can possibly improve the process.
Sent from my Nexus 7 using XDA Premium HD app
Lrs121 said:
Bayfiles, mediafire, Google drive, a private server. Any where really. Also what you said about rsd lite isn't technically true, it isn't that the base band gets overwritten just that there are specific files meant for each different carrier aka prl, eri, ect that get overwritten by rsd lite when. Flashed with the ntelos sbf. Also you may think of adding on the secondary way of rooting involving the scripts I wrote giving people multiple ways to do one thing. Plus I get the bounus of having people try it out and find ways I can possibly improve the process.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Yes the scripts Lrs121 wrote are very, very helpful also as secondary ways of rooting. Worked for me like a charm, Saved time, I understood the process as I went through it and I became more knowledgeable of my device as a more-learned newly rooted owner. helped me appreciate the process more.
Sent from my Milestone X2 using xda premium
Recommended sticky!
I can't make it a sticky, as you don't have your own forum.
Sorry.
Can't you sticky it to this forum?
don't be scared it's only a phone
ogd x d2g x2 sg3
old ladies ^
eagleeyetom said:
I can't make it a sticky, as you don't have your own forum.
Sorry.
Click to expand...
Click to collapse
Could you please elaborate on what this means? If it's due to the fact that the guide is for the Milestone X2 and not the Droid X2, please keep in mind that the phones are essentially the same with incredibly minor differences (along with carrier preferences).
The exploits and methods used in this guide are very similar to the Droid X2, but I wrote it for the Milestone X2. When it comes to talking about our phone, mods tell us to post in the Motorola Droid X2 forum, ergo here we are :/
grizzlayleslay said:
Could you please elaborate on what this means? If it's due to the fact that the guide is for the Milestone X2 and not the Droid X2, please keep in mind that the phones are essentially the same with incredibly minor differences (along with carrier preferences).
The exploits and methods used in this guide are very similar to the Droid X2, but I wrote it for the Milestone X2. When it comes to talking about our phone, mods tell us to post in the Motorola Droid X2 forum, ergo here we are :/
Click to expand...
Click to collapse
The Milestone X2 doesn't have it's own dedicated forum. That's the reason for it not being able to be made a sticky (or atleast the way I understand it). Rules are rules. But ya never know unless ya ask
tallyforeman said:
The Milestone X2 doesn't have it's own dedicated forum. That's the reason for it not being able to be made a sticky (or atleast the way I understand it). Rules are rules. But ya never know unless ya ask
Click to expand...
Click to collapse
Thanks, that does explain it. Obviously I disagree with it since
The MX2 doesn't, and will likely never have, its own forum since it's so similar to DX2
MX2 users are directed to the Motorola Droid X2 forum for help
The guide is meant to stop MX2 users from searching everywhere for help
Maybe someone will reconsider and sticky it. Maybe they won't. At least the guide exists to help people, and that's my main concern more than anything.
Hello,
Last night, I tried to modify the Screen DPI on my tablet ASD Digital MID 162... After the device restart, splash screen not ending... I reset my build.prop to the default value, and make a wipe cache with Adb and instead of write wipe /cache, I write wipe only... And my device don't boot and I can't use adb shell... The error is : "Permission denied (13)"
Someonee can help me ? Please ><
(Sorry for my bad english, I'm french)
How did you modify the DPI exactly?
Through an app?
Editing the build.prop?
Laughing at you while eating Jellybeans
Sounds like a messed up build prop and the device is bricked..
Yes I've modify the DPI in build.prop file...
What can I do for repair the boot ?
One help ?
Gonna have to reflash. You pretty much wiped your device so you will need to reinstall the os
Wayne Tech S-III
I know that, I have to reinstall the OS.. But I don't have recovery mod on my tablet... The only one I have it's an recovery stock (I think, I'm not sure).. I can do "adb ls/", "adb pull and push" , that's all... One idea ?
[I've tried to push a shell in /system/bin in recovery mode, but I've got a error (permission denied), I want to push a shell for execute "flash_image" tools with an new OS .img file for solve the problem ]
I've had similar problems with my myTouch when I've done things it didn't like. Providing that you can boot to the stock recovery that gives you the options to reboot or apply update then your almost saved. Because if that's the case then ya can
copy the custom recovery.zip file over to the root of your sdcard (I used a computer for that as when I killed my phone it wouldn't boot past sock recovery or boot-looping)
rename it to update.zip then boot into stock recovery,
apply the update from sd and your device should, hopefully, temporarily start the custom recovery so that you can
wipe re-flash or restore from backup.
This all assumes that your device has a way for you to access the sdcard without your device.
Hope this helps/use at your own risk
Sent from either my SPH-D700 or myTouch3Gs
I go to make a meditation on this idea... The problem is that I can't do anythings with the "stock recovery", It's just a screen with an open [dead] droid with red exclamation mark, and that's all. Nothing to do when I push one touch like Volume - or +, but when I boot with another key as Power Up, A black screen appeared, and it's all... (I want to show a photo with a screenshot, but I'm a new user, I can't :'( , I've no luck !!!! >< )
SteakFrite said:
I go to make a meditation on this idea... The problem is that I can't do anythings with the "stock recovery", It's just a screen with an open [dead] droid with red exclamation mark, and that's all. Nothing to do when I push one touch like Volume - or +, but when I boot with another key as Power Up, A black screen appeared, and it's all... (I want to show a photo with a screenshot, but I'm a new user, I can't :'( , I've no luck !!!! >< )
Click to expand...
Click to collapse
That is not recovery that is the kernel panic screen. Only option is an Odin install of stock
SteakFrite said:
I go to make a meditation on this idea... The problem is that I can't do anythings with the "stock recovery", It's just a screen with an open [dead] droid with red exclamation mark, and that's all. Nothing to do when I push one touch like Volume - or +, but when I boot with another key as Power Up, A black screen appeared, and it's all... (I want to show a photo with a screenshot, but I'm a new user, I can't :'( , I've no luck !!!! >< )
Click to expand...
Click to collapse
Ok so I read the post about kernel panic screen and agree mostly, however, I've seen the panic screen and gotten past it with a combo of volume + and power button at the same time, it then returns an error message on how recovery wasn't able to be read from its expected source, it then blanks out for a moment and boots the stock recovery, from there I apply the update.zip that I renamed and placed there with a computer, and then everything is good again.
Note: I don't have the specific device you do, or know the method that you usually used to use to boot into recovery.
Usually, its a combo of two or three buttons like on my htc product it's volume up and power button and on my Samsung its volume down and power and camera button. Note: when I do actually get into a custom recovery on my htc the power button then changes to turning the screen off and on instead of selecting things, which made it a hair pulling experience until I figured out that the directional pad on my device was the select button. (Moral of the story, power button sometimes controls the power to the screen, sometimes its used for selecting things, odd but be persistent and try combos because I thought my phone was killed till I hit the power button a second time and the screen came right back on.)
Odin should resolve the issue though for sure if fiddling around with your devices' buttons get to be frustrating, I just figure that any time I touch a computer to re-root my phone I've not done enough trouble shooting.
One other thing you can try is a targeted google search
Eg: 'solved [device name] [issue with device] site:[address of site to search]
So for example when I had a problem with my Samsung I used
'Solved epic 4g bootloop site:xda
Note I had to shorten the site as I'm not allowed just yet to post links but you'll want to include the .com
You can also replace the site: with similar: to search sites that are like xda with similar results.
What's the name and manufacture of your device? I'll see what I can dig up for you.
Sent from either my SPH-D700 or myTouch3Gs
Good ! Thank's youuuuu !! I've can access recovery mod with combo of Volume + and Power... My device is "ASD Digital 162"... Tonight, I go to make an update.zip with an android OS img file... Thank's !!
Where I can find an image file of my Rom ?
This device don't have many popularity on google, and he have no constructor website... Where can I find a ROM or Custom Rom ?
For information, I've one another tablet (Exactely same device) arround of me.. Can I extract the ROM or a backup that could me restore the Android OS ? I don't want do stupid things with the other tablet also like I do this time...
(I want to precise... On my SdCard, a folder named "nandroid" has apparead , he content kernel file, system .img file, cache .img file, etc etc.., if you have any suggest on what can I do with it )
SteakFrite said:
This device don't have many popularity on google, and he have no constructor website... Where can I find a ROM or Custom Rom ?
Click to expand...
Click to collapse
I'll be seeing what I can dig up in the next day or so. Have you any links to shair; such as the guide(s) you've used?
SteakFrite said:
For information, I've one another tablet (Exactely same device) arround of me.. Can I extract the ROM or a backup that could me restore the Android OS ? I don't want do stupid things with the other tablet also like I do this time...
Click to expand...
Click to collapse
You could try it, though I wouldn't as internal hardware can differ inside identical devices, you could end up 'super' bricking your device which I don't think is a real term it just sounds less scary than 'muten' bricking. The phonomonon can be observed when someone flashes an epic 4g touch rom on to an epic 4g and things are never the same. Not saying that's the case just my perinoa speeking up here.
Actually I think there are guides floting around on how to make and scrub your own custom rom, maybe you could do a full copy of the working device though the usb debug bridge, scrub the user data and dependencies from the copy and push it to the not-yet working device... or you could blase the path allready well troden.
SteakFrite;40339439 said:
(I want to precise... On my SdCard, a folder named "nandroid" has apparead , he content kernel file, system .img file, cache .img file, etc etc.., if you have any suggest on what can I do with it )
Click to expand...
Click to collapse
now when you're going to your sd card are you talking removable sd or internal?
Some devices don't have an external or its inaccessible,
other devices make it confusing by also having a partition on the internall memory labled sdcard which looks a lot like the sd card that can be un mounted and re mounted (I believe it to be confusing because the sdcard is also lables sdcard),
And yet others are really easy to spot because its the only thing labled and removeable as an sdcard
Any who if your talking about viewing your sdcard with prisice then likely what your viewing is the old contents of the card (what ever you had on it before this learning experieance snuck up on you) and I would treat it like pizza from last night's party. Meaning that the backed up apps could be used and there could very well be a good backup in there if you made one in the before time, but I wouldn't force my device to choke down leftovers when I could start anew.
SteakFrite said:
Good ! Thank's youuuuu !! I've can access recovery mod with combo of Volume + and Power... My device is "ASD Digital 162"... Tonight, I go to make an update.zip with an android OS img file... Thank's !!
Click to expand...
Click to collapse
You're Welcome; knew you weren't out of options.
Make sure to reroot from the start of what ever guide you used (as a gard against myself and the decisions I make I always keep my costom recovery flash zip for all my devices in the root of my sdcard and labled as update.zip or whatever the manufacture's recovery software by defaults to looking for. That way I can always reinstall if the device still turns on.) as you'll likely want to flash and mod with furver, I know I always do, keep a clear head and it should all work out.
Sent from either my SPH-D700 or myTouch3Gs using XDA app
"it never hurts to help"
...
It's a external sd card... And the file and folder are lost.
Exist an universal Custom ROM Android 4.2 ? I didn't found any official rom for this tablet...
SteakFrite said:
It's a external sd card... And the file and folder are lost.
Exist an universal Custom ROM Android 4.2 ? I didn't found any official rom for this tablet...
Click to expand...
Click to collapse
Yeah just spent the last hour or so looking for asd mid 162 tablet in google, tried a few modifide search quaries, and such to no avail. Saw your question on a few other boards too. I've a feeling that you've run into the same problem with low popularity and lack of documentation. If you got any other discripters I can use for searching I'll be back on the case after work today
Sent from either my SPH-D700 or myTouch3Gs using XDA app
"it never hurts to help"
S0AndS0 said:
Yeah just spent the last hour or so looking for asd mid 162 tablet in google, tried a few modifide search quaries, and such to no avail. Saw your question on a few other boards too. I've a feeling that you've run into the same problem with low popularity and lack of documentation. If you got any other discripters I can use for searching I'll be back on the case after work today
Sent from either my SPH-D700 or myTouch3Gs using XDA app
"it never hurts to help"
Click to expand...
Click to collapse
On recovery screen, is marked "SDK : MID-A13-Android4.2-V1.0-20130121"...
This tablet is the 9' inch model of ASD Digital 142...
Looks like that's the rom, could try flashing it again, just google the 'a13 9 inch tablet' and you'll find info on allwinner.
Happen to know what the ASD stands for? All I'm getting is autism results. (Which putting the word autism in this thread and adding '[minus sine]autism' might help)
Sent from either my SPH-D700 or myTouch3Gs
I haven't understand...
I don't understand what you say... :/
Can you use easiest word or terms ? (If possible)
Sorry about that.
The first part of last post was discribing a search quary I used to find info on the rom you may be using. Looks like a cross platform compatible rom on the face of it but I'm still looking into it.
The second part of last post was stating that when I search for your devices' model 'asd digital' I'm getting results for human medical problems and not hardware related information. So I put the main word that was triggering that into this thread so that I can then search 'asd digital -autizem' and cut those results automaticly from the google search results.
Still working on this with you, just have split atention with trying to finish my first guide for android/linux dulebooting (unrelated to the issuess that curently plage you but still may be worth a look at when you've a system up and running again.)
At this point doing a restore from a working device's backup like you where saying might be the best bet on reviving the simi-bricked device, but I'll have to do some more reading before I really feel comfortible sugesting that you go though all that.
Now that you where able to boot a recovery screen; have you tried anything to get it back up and running? Such as restoring from a backup created after rooting the first time around?
Sent from either my SPH-D700 or myTouch3Gs using XDA app
"it never hurts to help"
link to guide for Debian Kit I'm working on for you.
https://docs.google.com/document/d/1ssVeIhdBuuy8CtpBP1lWgUkG6fR6oHxP20ToYPPw6zI/edit?usp=sharing
I POSTED EARLIER BUT IT NEVER SHOWED UP SO IM REPOSTING. sry for caps.
rooted my nook color and everything was fine. then i tried to root my nook tablet. searched all over the net for comprehensive instructions to do so and i found this
The first thing you need to do is extract the contents of file #1 and write the extracted img file to a Micro SD. If you are using Microsoft Windows then click the file named Win32DiskImager.exe, select the NT16or8gbV47SDimagefile.img, select your drive letter for your SD card.
If you are using Linux, then open up the terminal and CD into the directory where NT16or8gbV47SDimagefile.img is located. Once in the correct directory issue this command to write the .img to the Micro SD:
sudo dd if=NT16or8gbV47SDimagefile.img of=/dev/sdX
You must replace the X in sdX with the appropriate letter for your SD slot. There are many ways to get the correct letter but I use the program Gparted.
Ok, so now you have an SD card that will root your Nook Tablet. Let's boot into Recovey. Turn off your Nook if it is on, and connect the USB wire to your computer. Your Nook will now turn on and enter into ClockwordMod Recovery. Using the Volume Keys to move up and down and the N key to select, click on Install zip from SD. You will now see a zip file called Root_8gb-or-16gb-NTV4_7.zip. Highlight that file and press the N.
If all goes well, the operation will complete. You are now rooted. Press the Power button to go back to main Recovery menus and select Reboot and press the N key. Your Nook will appear normal. It is not. Press the N key and you will see a new option for Home screen. Clicking the new Home icon will take you to an Android looking desktop. Yay! We are not done yet.
Now, install ES File Explorer from the Play Store. Open the app and browse your Micro SD card. Look for a folder called Apps. In this folder you will see a file named Nook Recovery Flasher.apk. Click this file to install it. Once installed, click on Flash CWM Recovery. Now you do not need the SD card you made earlier to boot into Recovery. It is now part of the system.
Remove the SD card and connect it your computer and format it so that it is empty.
Copy the files #2, #3, and #4 that you downloaded from above to the SD card and insert it back into the Nook Tablet.
Remember how to boot your Nook into Recovery mode? Do it.
Select Install zip from SD again and install ONLY CWM_v6.2.7_emmc.zip. This will upgrade your recovery. Without upgrading, you will not be able to flash CyanogenMod. Once the operation is complete, use the power button go back to reboot the Nook. Boot it to Recovery one more time.
Now you can select the latest CyanogenMod file you downloaded to install it. After that, select the latest Gapps you downloaded. Reboot the Nook and you are good to go!!!
. i folowed all the instructions to the dot. but when i got the this step, "Remember how to boot your Nook into Recovery mode? Do it." and i did it. but when i rebooted it immediately tried to boot into recovery but got stuck on the cardboard box screen and it flickered none stop and would not proceed to recovery (CWM) menu. I tried everything i could think of and i found that if i reformatted my sd card with the CWM sd root img and put sd card into NT and boot up it successfully brings up CWM. from this i tried both normal cache wipe and advanced menu cache wipe and also tried wipe to factory settings and wipe battery stats, rebooted and it still gets stuck on the flickering cardboard box screen..........anyone have any ideas? i cant seem to boot it up at all past this screen. maybe i shud format system through sd-card cwm? but then i would have no OS, so how would i proceed with this. is it totally broke or wut? god i hope not:crying::crying::crying::crying::crying::crying:
If you aim to run rooted stock ROM, see http://forum.xda-developers.com/showpost.php?p=31271965&postcount=240.
If you aim to install custom ROM such as CM10.x internally on emmc, see http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1.
See also http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more background info on rooting & flashing custom ROMs.
wut ive got so far
digixmax said:
If you aim to run rooted stock ROM, see http://forum.xda-developers.com/showpost.php?p=31271965&postcount=240.
If you aim to install custom ROM such as CM10.x internally on emmc, see http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1.
See also http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more background info on rooting & flashing custom ROMs.
Click to expand...
Click to collapse
well i think wut u gave me is exactly wut i need. followed the custom rom tutorial and it worked fine to the point to where i first get to cyanoboot menu where i would have proceded to install cm10 and gapps. but i accidentally put the wrong cwm on the sd card and it said bad boot. (note it also said it disabled charging) so i go the right cwm boot img for it. but the fact that it disabled my charger i cannot get back into the cyanboot menu. anyone kno how i can reactivate charging? if not then im completely screwed because once it dies i wont be able to charge it again and it will be flippin useless. even worse than before.........sigh fml someone shoot me in the dome
The "charging disabled" message on the Cyanoboot screen does not mean what you think it means (i.e., charging is turned off on for good until you somehow turn it on again). If you're stuck on that boot screen, just hold down power button for 20-30 sec to turn it off and start over with the SD card with the right CWM.
Yeah, I always wondered about why it says charging disabled when you are in the cyanoboot loader.
That being said, you should be just fine. I recently had to restore, then reflash, then restore my 16GB Nook Tablet. I saw that message in the upper left hand corner and all I really thought was, huh I wander why they do that.
As the poster above me said, just burn the correct version of CWM (you need v6 or higher), load your CM10 and Gapps .ZIP files onto the card.
When you see the Cyanoboot loader hold down the "n" button for the menu.
Select internal recovery.
Select install file from zip.
Select your CM10 .ZIP file.
Wait a few minutes while it does it's thing.
Repeat the same procedure from the install menu for the gapps.zip file.
Once it is done, you can safely remove the SD card. Sometimes this will make the Nook reboot. But that's fine. You want it to reboot anyway. It should boot into CM10. Sometimes the first boot can take a while as it set's itself up. Once it comes up you should be good to go.
Post back if you have any questions.
A piece of advice. If you ever for any reason may need to restore the Stock OS/ROM ***DO NOT*** run any 5point or 10point multitouch installer. If you do and you forget to reflash the multitouch firmware, you will be unable to use the touch screen with the stock OS. Then you will have to reload CM10, reflash the screen firmware, then reload the stock OS. I was running CM10 for months and totally forgot that I did the 10point flash. Screwed me over for a bit. Learn from my pain, don't do that. 99% of all Android users I know (and I know a lot, I work in IT) use 1 finger most of the time and sometimes 2 for pinch to zoom. So in my opinion, you don't gain very much functionality from it and if you forget to reflash the 2 point touch firmware, you could end up with a headache. Just thought i'd throw that out there.
YAY!
Temetka said:
Yeah, I always wondered about why it says charging disabled when you are in the cyanoboot loader.
That being said, you should be just fine. I recently had to restore, then reflash, then restore my 16GB Nook Tablet. I saw that message in the upper left hand corner and all I really thought was, huh I wander why they do that.
As the poster above me said, just burn the correct version of CWM (you need v6 or higher), load your CM10 and Gapps .ZIP files onto the card.
When you see the Cyanoboot loader hold down the "n" button for the menu.
Select internal recovery.
Select install file from zip.
Select your CM10 .ZIP file.
Wait a few minutes while it does it's thing.
Repeat the same procedure from the install menu for the gapps.zip file.
Once it is done, you can safely remove the SD card. Sometimes this will make the Nook reboot. But that's fine. You want it to reboot anyway. It should boot into CM10. Sometimes the first boot can take a while as it set's itself up. Once it comes up you should be good to go.
Post back if you have any questions.
A piece of advice. If you ever for any reason may need to restore the Stock OS/ROM ***DO NOT*** run any 5point or 10point multitouch installer. If you do and you forget to reflash the multitouch firmware, you will be unable to use the touch screen with the stock OS. Then you will have to reload CM10, reflash the screen firmware, then reload the stock OS. I was running CM10 for months and totally forgot that I did the 10point flash. Screwed me over for a bit. Learn from my pain, don't do that. 99% of all Android users I know (and I know a lot, I work in IT) use 1 finger most of the time and sometimes 2 for pinch to zoom. So in my opinion, you don't gain very much functionality from it and if you forget to reflash the 2 point touch firmware, you could end up with a headache. Just thought i'd throw that out there.
Click to expand...
Click to collapse
YAY! i figured out how to get past the bad boot part. just be sure to be vigilant and press "n" asap when the screen boots up in cyanoboot......and i mean like THE second it pops up. that solved all my problems.......
but i dont understand the piece of advice part with the 5 point/ 10 point touch installer deal. ill do alil research on it to see wut it is and wut i got to do. if you care to send a link explaining it that would be super flippin awesome. and btw thx sooooooooooooooooo much. this forum has been the most helpful place. quick responses and accurate information. everyone i talk to rocks. i appreciate it so much. :victory:
The 5point and 10point touch is just that.
So you know how your screen responds to your touch input? And let's say you use to fingers to zoom in on a picture. That would be an example of 2 touch. Expand from there for more finger interaction.
Here's an XDA thread on the topic:
http://forum.xda-developers.com/showthread.php?t=769932
and nice Wikipedia article on how multi-touch works:
http://en.wikipedia.org/wiki/Multi-touch
Glad you are up and running.