Related
** PLEASE, READ THE GUIDE BEFORE FLASHING **
Flashing a device is a risky process, and you definitively have to know that your device might not boot correctly, or not boot at all. You must also notice that this method is being tested and some components of your Polaris will not working at the moment. Take into consideration that there are developers that are sharing all their work with us, but although they're really good at their job, they all have their lives. So, if something just doesn't work, please, be patient*
NAND Boot for Polaris! Made possible thanks to DZO!
This method will allow you to start Android without the need of Windows Mobile. It will just boot like if the device had a native Android OS installed onto it.
- You may see this guide really long, but it's because I tried to detail every step and I put lots of URLs to make the process easier for beginners It's not than difficult as it seems!
Step by step guide:
Needless to say that you need to have HardSPLed your device first!
1. CHOOSE YOUR ANDROID BUILD
You can install try to install any build from the Kaiser and Vogue forums. They should work for Polaris:
I personally recommend to start with Myn's Warm Donut Release 5.
You can choose it in two different screen resolutions
240x320 (my favorite) - http://download219.mediafire.com/t0lnxmijgEjg/1drm2jqwjzn/myn-WarmDonut-04-24-2010-240x320-110.zip
320x480 - http://download533.mediafire.com/ml1jxoyomIDg/miw2uzjjzjq/myn-WarmDonut-04-24-2010-320x480-160.zip
If you want more info, check its thread: http://forum.xda-developers.com/showthread.php?t=619980
Download the build. It may be a compressed file containing an androidinstall.tar.
Copy this androidinstall.tar under a folder named andboot at the top level of your SD Card. The file path should be /andboot/androidinstall.tar.
You're now ready to flash the OS loader.
2. -OPTIONAL, BUT RECOMMENDED. ERASE YOUR ROM.
To be sure that you won't have problems with the flashing, you should use a tool that executes the called Task 29 to clean the NAND memory in the device. This helps the flashing goes OK and minimizes the chance of a bad flash.*
Fortunately, there's such tool: It can be downloaded HERE (big thanks to leppa).
It's a hacked flashing tool. To make it work you will have to select a dummy .NBH file. Use the .NBH file you want, preferably a small one. You can use the one that you will download in step 3.
You it finishes the operation, your phone will NOT boot. Don't worry. This is normal. We will make it boot soon.
More info HERE: http://forum.xda-developers.com/showthread.php?p=6227425#post6227425
3. FLASH THE ANDROID OS LOADER TO NAND
You will need a .NBH in order to boot from NAND. It's usually named polaimg-panel[x]-[resolution]-[date].nbh.
I personally recommend to flash of the .NBH files by DZO dated 07-May-2010. They are listed on his site: http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
Choose one according to your paneltype and resolution. Your paneltype depends on its maker. You should try from 1 to 3 to see which one works for you.
Flash the .nbh file you downloaded with your prefered tool (I used CustomRUU.exe for Windows).
To flash your device you might have to put your Polaris in bootloader mode. To enter this mode you have to do the following:
Press and hold the camera button.
Press reset while you hold the camera button. Release it (the reset button).
Hold the camera button until the colored bars screen appears.
If it doesn't work, remove the battery, wait for some seconds, put it back and try again.
When the colored screen (Hard SPL) is shown, you are ready to flash it using the flashing application (CustomRUU.exe, for example).
4. INSTALL YOUR BUILD
When you're done flashing, your device will boot. You will now attempt to install your build using the file androidinstall.tar.
You'll see lots of text lines scrolling while it boots. Now, pay close attention to the next step.
The system will prompt you to press and hold the center button of the DPad (in the middle of the jog-wheel) to start the Android Installer. It's a message like "Press x to launch the installer". Don't forget to hold it until the installer is shown!
The installer will eventually start.
A list of options should appear (in text mode). Use the jog-wheel up and down to navigate. D-pad center to select.
Choose your installation options (I selected System on NAND, Data on NAND). Don't choose any other option unless you know what you're doing.
Install it! (if it ask you to wipe the data, select yes).
Wait for the installer to finish.
The menu should appear again.
5. INSTALL THE SPECIFIC UPDATES FOR POLARIS
Due to particularities in our devices, some hardware like Wi-Fi and Bluetooth won't work properly if you don't apply some updates first.
You will need a file an androidupdate.tar to apply to the just installed system.
You can download it HERE (thanks to l1q1d).
When applied, the installer will be shown again.
You now have to select Fix permissions to avoid problems.
Don't exit the installer: soft reset your Polaris instead.
YOU ARE DONE! Your Android system will boot after some minutes.
Things that should WORK:
Phone calls: incoming/outcoming
Texting (SMS)
Data connection (GPRS/3G)
Wi-Fi
GPS
Bluetooth
Things that DON'T WORK:
USB Storage Mode
USB debugging is unstable.
Tethering
Camera (in Eclair)
Headset
Bugs/Issues:
Sometimes Wi-Fi hangs while is being disabled and prevents the device from suspending correctly (it won't sleep and the screen will turn of every time you press a button).
Data connection goes down from time to time and it won't reconnect until you go to the Modem application, disconnect, connect again and wait it to connect.
Audio Input: faulty and unusable with most of applications that use it.
* Enjoy and feel free to donate to our GREAT developers.
* I donated to our developers, and I'm from Spain. As everybody know, Spain is falling like a fainted Pokémon thanks to Zapatero (Mr. Bean II). If I can donate, how couldn't you do it?
I'm trying now.. Sorry my english...
They state that it's valid also for HARET:
if you're doing it with haret, extract basefiles to your sd, plop the androidinstall.tar into the same folder, and boot, hold down volume up just like the nand people (but don't pick nand to store the files, it won't work)
Click to expand...
Click to collapse
I've tried with the specified basefiles and plemen's Android 2.1, but I had no luck.
I noticed that when I press run from HARET and the progress bar fills up, it vibrates two times. Then, it seems that the device is hung, but after 15 seconds (or more), it boots. However, I didn't complete the rootfs-less setup process. It complaints about this:
Unable to open persistent property directory /data/property errno: 2
Click to expand...
Click to collapse
Anyone?
Wait, does this mean its totally an Android ROM? If so, COOL!
haven't tried yet ^^
Did you take the last package on sourceforge for the Eclair 2.1 Build? The files on Mediafire was corrupted.
I think there is no speed improvement with this, it's "only" an easier way to install and upgrade the system.
This is NOT "totally an Android ROM".
i can't install with this method
is there a "how to" or forum thread somewhere cause i get
sh: 2: unknown operand
losetup: /dev/block/loop1: No such file or directory
Failed
Failed to reach system.img on SD Card
Click to expand...
Click to collapse
during setup it complains "cant create folder /system cause file already exist"
i put basefiles at the root of my sd card and the vogue .tar in a folder call /andboot
all taken from here http://sourceforge.net/projects/androidhtc/
I think that you must flash a nbh that only works in vogue yet. I try to flash but it stop at 33%. I think that we must wait.
luzbel_es said:
I think that you must flash a nbh that only works in vogue yet. I try to flash but it stop at 33%. I think that we must wait.
Click to expand...
Click to collapse
Yeah, same problem. It's impossible to flash now with any package for Vogue or Kayser...
We have to wait for DZO's work to port .tar and . NBH for us...
Hi fellas:
I carried out research about the new boot up method, and it seems it will be compatible with our beloved Polaris. But it still needs some fine-tuning, first of all due to the fact that the new installer is started holding down VolUp, but this button isn't correctly recognized with the current bits.
In other words, we should wait before trying out this one. Vilord is aware of this issue.
Stay tuned!
Hi SuperJmn,
Of course I wait for ...
I look every day in the Vogue/Kaiser thread and hope we can to flash our Polaris next time.
Thanks.
Android should work much more faster after flashing... Can't wait to try this
manu33xtro said:
Hi SuperJmn,
Of course I wait for ...
I look every day in the Vogue/Kaiser thread and hope we can to flash our Polaris next time.
Thanks.
Click to expand...
Click to collapse
Hey
I have pola100 with pcar latest non-3d, Im trying my luck to get android started but with the latest files (img, rootfs, zImage) I am not able to. tried hell lot of combinations.
can you suggest me which one would I use, I downloaded some from sourceforge!
but I read that the new rootfs is for nand....
please friends guide me to right downlaods and versions for a near perfect android installation
Thanks in advance....
Niranjan
Hi! The new method is not only for NAND, but also for SD booting. It has some incompatibilities, so it's working for Vogue for the moment (Vogue owners are a bit more lucky than us in terms of development).
We are waiting for @vilord, @DZO and other authorities to fix the appropriate files.
I will contact them right after I end up writing this
Updated information for NAND boot. Thanks DZO!
Can you give us some feedback? Does it run better, smoothier than before? Or nothing about that?
it work but this resolution is not userful for me. No more speed than haret method, wifi and camera not work, system freeze some times. Do you have this problems?
How to put device in bootloader
Hello,
I've installed Android on my POLA100 (NAND method). Until now it's working fine. When I tried to put my device in bootloader mode, after installing Android, surprise... the combination (camera button pressed + stylus reset) isn't working.
If you used this: Eclair build you should download this update too: update for qvga and put androidupdate.tar from this archive on the andboot folder on your sdcard near androidinstall.tar.
After installing the system like SuperJMN said you'll have to press the power button one more after system reboot and choose update... from the menu,then quit when the menu reappear.
WIFI,Camera,Bluetooth doesn't work on this build(the only one I've tested with this new method)
Thank you SuperJMN for posting this,I hope it will remain for a long time on the front page and many thanks to DZO,VILORD,JAMEZELLE,PLEMEN and all other guys for the hard work.
Polaris
Hi,
for polaris you push power button, and boot menu works(NAND and SD).
The issue is that Wifi is not working now.
I try several builds.
So it seems not depending on the system?
Regards
How to put device in bootloader
Solved it. I put my device in bootloader by pressing the camera button + stylus reset when Android loads. I don't know if it worked because I removed my SD card and on the screen appeared "Waiting for SD card" but in that moment I've reset the device in bootloader.
Ok, so I just took the tutorial written by Slimdizzy and have modified it for Windows users, as he stated he was using a Mac, and a lot of people seem to be having issues getting this working. Go easy on me this is my first TUT write up, I hope it helps......If anyone has a correction or a suggestion please let me know.
Credit goes to Slimdizzy for his original post here:
http://forum.xda-developers.com/showthread.php?t=750888
When I rooted my Telus HTC Desire the first time it was hit and miss, if I remember correctly I did it 3 times until it worked 100%, by this I mean Unrevoked/Root ran without hitch, and after running Unrevoked I was able to reboot into Android, and then reboot back into recovery on my first try without any weirdness.....
The following steps are what I did to get my drivers installed and working the first time, rooting the phone, installing Radio 5.09.00.20, and getting a custom ROM installed (I used OpenDesire)
First things first you need the drivers, this is the most important part. Nothing will ever work for you if you don't have the right drivers installed.
Drivers:
1. Download the Android SDK here: http://dl.google.com/android/android-sdk_r06-windows.zip
2. Unzip and place the files in C:\Android. You can place the files wherever you want but my steps will use this location.
3. Run SDK Setup.exe , if you get the Failed to fetch URL error, hit close and then go to Settings and enable Force https://. Then click on Available Packages, near the bottom you will see USB Driver Package, place a check mark beside it and then click Install Selected.
Alternatively you can try using these drivers, they have worked for other users but I have not installed my drivers using this method so I can't say how well they will work.....
http://www.unrevoked.com/rootwiki/lib/exe/fetch.php?hash=908951&media=http%3A%2F%2Fwww.unrevoked.com%2Frecovery%2Fandroid-usb-driver.zip
4. Android SDK will download your drivers and place them here C:\android\usb_driver.
Now plugin your Desire with USB Debugging enabled (Settings --> Applications --> Development). Windows will prompt you for the device drivers, point windows to the C:\android\usb_driver folder and it should do it's thing. YOU MUST BE SURE TO INSTALL THE ADB DRIVERS, without those Unrevoked will not run.
5. Once all your drivers are installed, you can verify them by checking with the Android SDK
Open a DOS prompt (CMD in the Run box) and navigate to C:\android\tools and then type "adb devices", it should return a funny device name/ID, if you see a device listed then you are good to go, if you don't then repeat these steps until you do, check your Device Manager for an uninstalled device/driver.
***UPDATED***
Steps for Rooting:
***Follow these steps after you are 100% sure you have the drivers right!***
***DO NOT plug you Desire into your computer yet***
1. Goto http://unrevoked.com and download the software
2. You now have a choice of recovery, Amon RA has released an SLCD version of his recovery, which in my opinion is much better, it has a few more features than Clockwork. I recommend Amon RA, but the choice is yours.
Amon RA Recovery v1.7.0.1 R5 SLCD: http://dl.dropbox.com/u/4481275/recovery-RA-desire-v1.7.0.1-R5-SLCD.img
Clockwork v2.5.0.7 SLCD:http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.7-bravo.zip
3. Go to HBOOT, this is done by shutting down your phone and powering on the device while holding the Power button down and pushing Volume down at the same time, once HBOOT is loaded do a wipe (Clear Storage). You can navigate the menus by using the volume rocker and the Power button to select your option.
4. Load Unrevoked and load the custom SLCD recovery file on your PC:
Goto File>Custom Recovery and point it to the recovery image that you downloaded in step 2.
5. Restart your phone, it will take a few minutes because you did a wipe, just wait it will load (up to 5 minutes). As soon as the welcome screen loads plug your phone in to the PC and Unrevoked should do it's thing. If Unrevoked doesn't start, then hit the Menu button go to Settings --> Applications --> Development and enable USB debugging.
6. The phone will restart a couple of times, and will look like it's hanging on the HTC screen but it's not! If the HTC screen is present for more than 5 minutes pull your battery and start again ( I had to do this a couple times myself). If Unrevoked pauses half way through its process, it could be because for some reason you don't have the proper drivers installed. You can load them as Unrevoked does the root process, while the phone is rebooting if Unrevoked pauses and Windows prompts you for a driver point it to the C:\android\tools directory and it will load the drivers and Unrevoked will continue its root process.
7. When Unrevoked is finished you will be left at the recovery screen,
8. *** VERY IMPORTANT*** Before restarting do a "wipe cache partition", "factory reset". And now would be a good time for a Nandroid Backup
9. Now reboot, and Android should load. Check for Superuser Permissions app, if you see it you're good if not restart from step 3.
10. Shutdown and load HBOOT, wait a few seconds for SD card (you'll see something try to load quickly), then load recovery again, it should load everytime without issue now.
It may take a few tries, but just follow these steps and it will work.
Steps for flashing radio, and custom ROM:
1. Grab a custom ROM from the forum, I used OpenDesire: http://forum.xda-developers.com/showthread.php?t=712615
OpenDesire comes with a nice reboot to Recovery feature built in.
2. Once zip is download, copy it to your SD card
3. Get the updated radio needed from here: http://www.mightyrom.com/mrx/MRX/Bravo/Radio/Signed/32.44.00.32U_5.09.05.30_2.zip
4. Reboot into recovery by powering on the device while holding the Power button down and pushing Volume down at the same time. Select Recovery with the Volume rocker and then click the power button to launch it.
5. Select "install zip from SD card" using the trackpad and select the radio zip that you download in step 3.
6. Let it do its thing (could take up to 10 mins to finish), use the back button to get to main menu and select "reboot system now" with the trackpad. If your phone hangs after rebooting wait at least 10 minutes before pulling the battery, it could be finishing the radio update.
7. Once rebooted check that the new radio is good by loading HBOOT (you should know how to do this by now) and at the top it will show you're radio version.
8. Load recovery again and select "wipe cache partition", "factory reset" (for the 3rd and final time). Then select "install zip from SD card" using the trackpad and select the ROM zip that you download in step 1.
9. The new ROM is now installed, restart the phone and wait up to 20 minutes (it shouldn't take that long) for the new ROM to load, DO NOT PULL YOUR BATTERY UNTIL AT LEAST 20 MINUTES HAVE PASSED.
You should now have your phone rooted, new radio installed, and a new custom ROM loaded.
Sorry for such a long post, but I found all these steps necessary to get the end result.
If I have missed anything or if anyone has comments / corrections post them here and I will try to keep the tutorial updated and easy to use as possible.
Great post man. I found the "dont plug the phone in yet" part out the hard way. I thought I had busted it on the 1st try!
Couple of things.
USB debugging is under development in Apps. (not a big deal)
Those unrevoked drivers worked great for me, I followed the instructions in the HTML doc that came with the zip. I have heard there are extra drivers needed for windows 7, and you have to be sure your running unrevoked as an admin.
Once I was rooted, I used RomManager to get the newest clockwork and flashed it. I used rom manager to flash the rom, HBoot to flash the radio, and did it backwards. Seems to not make a difference.
Thanks for doing this!
Edit: you forgot the most important part! Always Nandroid backup, and copy all the files from the SD card as soon as you are rooted incase something goes wrong.
Below may be wrong info, but it is what happened to me.
//////////////Extra tip, if you format an SD card, be sure you copy back the clockwork files before you unmount the card. I didn't and could not boot at all untill I copyed all the files back. I went straight to a nandroid without trying to boot into android, so I don't know if I messed up Android, but I know it would not boot to anything untill I fixed the SD card.
////////////////////
ajanu said:
Extra tip, if you format an SD card, be sure you copy back the clockwork files before you unmount the card. I didn't and could not boot at all untill I copyed all the files back. I went straight to a nandroid without trying to boot into android, so I don't know if I messed up Android, but I know it would not boot to anything untill I fixed the SD card.
Thanks for doing this!
Click to expand...
Click to collapse
Can you elaborate on this? I'm assuming Clockwork recovery is stored on the SD card?
BIGGGG THANKS, I will try tonight.
Below may be wrong info, but it is what happened to me.
//////////////Yes there is a folder called clockwork mod, in there were my nandroid backups. I copied everything on the SD back and Clockwork booted, so I can't say for sure, but I'd assume all you need is the clockwork folder. There are other folders that look like system folders that may also be important./////////////
ajanu said:
Great post man. I found the "dont plug the phone in yet" part out the hard way. I thought I had busted it on the 1st try!
Couple of things.
USB debugging is under development in Apps. (not a big deal)
Those unrevoked drivers worked great for me, I followed the instructions in the HTML doc that came with the zip. I have heard there are extra drivers needed for windows 7, and you have to be sure your running unrevoked as an admin.
Once I was rooted, I used RomManager to get the newest clockwork and flashed it. I used rom manager to flash the rom, HBoot to flash the radio, and did it backwards. Seems to not make a difference.
Extra tip, if you format an SD card, be sure you copy back the clockwork files before you unmount the card. I didn't and could not boot at all untill I copyed all the files back. I went straight to a nandroid without trying to boot into android, so I don't know if I messed up Android, but I know it would not boot to anything untill I fixed the SD card.
Thanks for doing this!
Edit: you forgot the most important part! Always Nandroid backup, and copy all the files from the SD card as soon as you are rooted incase something goes wrong.
Click to expand...
Click to collapse
This is exactly the part I wanted, when I had to use nandroid
ajanu said:
Yes there is a folder called clockwork mod, in there were my nandroid backups. I copied everything on the SD back and Clockwork booted, so I can't say for sure, but I'd assume all you need is the clockwork folder. There are other folders that look like system folders that may also be important.
Click to expand...
Click to collapse
I believe this is misinformation.. only reason because I was having that endless HTC frozen screen so I formated my SD card, the FAT32 partition and the EXT3 partition in windows using Paragon Partition Manager, finally got back into recovery, wiped everything from cache to davlik cache as well.. then installed my rom.
If Clockwork was stored on the SD card.. I believe it wouldn't have booted.. got a little confused there. However, the Nandroid backups are stored on the SD card.. that I know for sure!
quazis said:
I believe this is misinformation.. only reason because I was having that endless HTC frozen screen so I formated my SD card, the FAT32 partition and the EXT3 partition in windows using Paragon Partition Manager, finally got back into recovery, wiped everything from cache to davlik cache as well.. then installed my rom.
If Clockwork was stored on the SD card.. I believe it wouldn't have booted.. got a little confused there. However, the Nandroid backups are stored on the SD card.. that I know for sure!
Click to expand...
Click to collapse
These devices make no sense to me. Maybe I didn't help anything with the copy and just trying to boot a few times would work. I would expect things to work or not work, but they work intermittently some times. Certainly increases the confusion/frustration levels.
Wouldnt be using the latest radio and using "recovery-clockwork-2.5.0.7-bravo.img" instead of the old one be better?
Juggalo_X said:
Wouldnt be using the latest radio and using "recovery-clockwork-2.5.0.7-bravo.img" instead of the old one be better?
Click to expand...
Click to collapse
Link has been updated to reflect the latest Clockwork recovery version.
Thank you!
Blowtoke said:
Link has been updated to reflect the latest Clockwork recovery version.
Thank you!
Click to expand...
Click to collapse
No problem and here is a link to the new radio if you want to update it. it appears to be much better then the one linked in tut. Here it is
Juggalo_X said:
No problem and here is a link to the new radio if you want to update it. it appears to be much better then the one linked in tut. Here it is
Click to expand...
Click to collapse
Radio link updated as well, thanks!
quazis said:
I believe this is misinformation.. only reason because I was having that endless HTC frozen screen so I formated my SD card, the FAT32 partition and the EXT3 partition in windows using Paragon Partition Manager, finally got back into recovery, wiped everything from cache to davlik cache as well.. then installed my rom.
If Clockwork was stored on the SD card.. I believe it wouldn't have booted.. got a little confused there. However, the Nandroid backups are stored on the SD card.. that I know for sure!
Click to expand...
Click to collapse
What is EXT3 partition ?
I would like to get more details about the sdcard ? I make my backup with nandroid and after I format the sdcard....so if I want restore the back up from Nandroid, it will not be there....sorry for the noob questions
fourire said:
This is exactly the part I wanted, when I had to use nandroid
Click to expand...
Click to collapse
This step has been added to the guide....thank you!
fourire said:
What is EXT3 partition ?
I would like to get more details about the sdcard ? I make my backup with nandroid and after I format the sdcard....so if I want restore the back up from Nandroid, it will not be there....sorry for the noob questions
Click to expand...
Click to collapse
Ext3 partition is for A2SD, I never touched my SD Card until I was rooted, updated radio, and loaded a custom ROM. I can't say whether or not the SD card plays a role in freezing during boot to recovery or not? But like I said I never partitioned my SD until after everything was done.....
Very good tutorial !
Thank you
After all that, what's about the apps, contacts, calendar ?
And for this file: 2. Get the needed recovery image from here: http://koush.tandtgaming.com/recover....0.7-bravo.zip... is it for slcd ?
fourire said:
After all that, what's about the apps, contacts, calendar ?
And for this file: 2. Get the needed recovery image from here: http://koush.tandtgaming.com/recover....0.7-bravo.zip... is it for slcd ?
Click to expand...
Click to collapse
Recovery-clockwork-2.5.0.7-bravo.zip has been confirmed to work with SLCD, the link has been updated.
Thanks!
ok - at step 8
8. *** VERY IMPORTANT*** Before restarting do a "wipe cache partition", "factory reset". And now would be a good time for a Nandroid Backup
Can someone point me to a nandroid backup tutorial.
Blowtoke said:
I've posted a question on the Clockwork forum to find out if the latest version (recovery-clockwork-2.5.0.7-bravo.zip) works with SLCD, once I get an answer I will update the link if necessary.....for now it's reverted back to the old recovery img that I know works....
Thanks!
Click to expand...
Click to collapse
It works ive flashed it as my recovery img
ok so i loaded MotoFrenzyv05a so my milestone would have android 2.2 an its working great. So what i wanted to do next was to load the update : MotoFrenzy-v0.5c-update-nosign.
As the instructions say:
(download the latest attached zip , and inside you find a MotoFrenzy-vx.xx-update-nosign zip , which you copy to your sdcard into the folder /OpenRecovery/updates and recover from OpenRecovery menu.
Patches only match the release which it is made for. so 0.1 release has patches 0.1(a-z) and so on. you cannot use 0.1a on a 0.2 release.)
i dont have a folder named openrecovery on my sd card, so i tried a bunch of stuff pretty much an i just dont know if i have it on or not, if someone could jus tell me how step by step how to install this update (MotoFrenzy-v0.5c-update-nosign) i would really appreciate it.
And also after install the new MotoFrenzyv05a . i cant seem to find any networks to connect to on my phone, ive searched for my network telus countless of times and nothing, please help, thanks
Hello, I don't own a Milestone yet, but am planning on buying one and have done lot's of research, so I guess I could take a shot at helping you out.
Since you've been able to "install" (which is actually restore) MotoFrenzy, You probably already have root and some sort of recovery environment. Since the term 'openrecovery' doesn't ring a bell, let me ask this, do you know of the term 'adbrecovery'? Or do you remember how you installed MotoFrenzy?
In case you don't, I'll walk you through to installing Openrecovery.
I recommend using the OpenRecovery Mod by G.O.T. since that one has more features and is just my personal preference.
You can download it from: http://groupoften.wordpress.com/g-o-t-s-openrecovery/ look for "click to download (V1.04a)"
Once you downloaded the file, extract it and copy the "OpenRecovery" and "update.zip" to the root (top most folder) of your sd card.
Now you put the update in the /OpenRecovery/Updates folder.
Once you've done that, reboot your phone into the OpenRecovery menu by pressing power+X (for recovery 90.78) or power+Camera (for recovery 90.74)
Note that the recovery's of 90.78 and .74 don't have anything to do with what you've just done. Just try out both key combinations.
Once you've done that you should see a triangle. Now you have to press camera+volume UP and select install update.zip
Now you should be at the OpenRecovery Menu and that's as far as I can help, but it should be pretty self-explanatory (or something)
Hope that helped!
whenever i try to go back into recovery, it goes to the normal one instead of openrecovery. i have to apply update.zip every time. anyone else have that problem? otherwise it works fine. installed the theme, root, memhack, jit...
you have to apply the update.zip everytime it sucks but its not that bad ....
Motofrenzy is 2.1 not 2.2
Sent from my Milestone using XDA App
mousiope said:
you have to apply the update.zip everytime it sucks but its not that bad ....
Click to expand...
Click to collapse
thanks
thought i did something wrong. oh well. updates pretty quick anyway
Disclaimer: flashing is a lot more risky than rooting so proceed at your own risk. This has only been tested with the G2x.
This uses the free VirtualBox (from Oracle) and a 900 meg vitrual machine I created to allow flashing recovery (clockworkmod or stock) from a mac. If you run into any problems with the first download link, try the second (it requires free registration).
This will give you a running linux virtual machine that has g2x root/unroot, clockworkmod (and stock) recovery flashing, and the android sdk (including adb) set up. You can root or unroot as well as flash clockworkmod recovery or the stock recovery using some double-clickable scripts. The android sdk is on there too in case you want to play around with adb. The clockworkmod version installed is 3.1.0.1 external with ext4 (http://forum.xda-developers.com/showthread.php?t=1086687) but you can download other versions and flash them pretty easily - just check the Readme.txt in the nvflash folder.
The clockworkmod flash here is the mac equivalent of http://forum.xda-developers.com/showthread.php?t=1056847 - though this thread just uses a linux virtual machine to get it done.
The username and password on the virtual machine are both "android" (without the quotes of course).
Requirements:
a few gigs of hard disk space
about 300 megs of RAM
intel mac
a sense of adventure
download virtualbox and the extension pack from http://www.virtualbox.org/wiki/Downloads
http://download.virtualbox.org/virtualbox/4.0.8/VirtualBox-4.0.8-71778-OSX.dmg
http://download.virtualbox.org/virt...alBox_Extension_Pack-4.0.8-71778.vbox-extpack
install virtualbox
install the extension pack (just double click it once virtualbox is installed)
download the linux virtual machine (thanks to propain4444 for the hosting) http://articulatevisuals.com/g2x/virtualbox_image_32bit_0_3.tar.bz2 or (requires free registration for this one) http://www.4shared.com/file/19DywhVS/virtualbox_image_32bit_0_3tar.html
decompress the virtual machine download (double click) if it didn't happen automatically
in virtualbox choose Machine -> Add… from the menu bar and choose the android_g2x.vbox file inside the android_g2x folder created by the decompressed virtual machine download
once the vm boots up you'll see the root/untoot and nvflash folders on the desktop with double-clickable scripts inside
After following the requirements above, to connect your phone for flashing with nvflash do the following:
plug the USB cable into your mac
turn the phone off
remove the battery
hold down volume up and volume down then plug the USB cable into the phone
Nothing will happen on the linux vm (unless you ran the tail_kernel_log.sh script in the nvflash folder) but you *should* be able to then run the flash-clockworkmod-recovery.sh script. If it doesn't see your device try disconnecting from USB and doing the steps above again. If you want more visibility into whether or not it's connected then double-click the tail_kernel_log.sh script and watch for a line to appear when you plug your phone in (with volume buttons held down of course).
If this helped you please click the Thanks button on this post. Thanks to baykakes for helping with the initial testing and propain4444 for the registration free download hosting. Countless thanks and credit to krylon360 for the updated ClockworkMod, Chris Soyars (ctso) for the initial test2 ClockworkMod and linux scripts in the g2x forum that motivated me to do this, koush for ClockworkMod and many others here whose knowledge helped make this possible.
YEY you posted it!
Once everything is downloaded IT'S REALLY EASY FOLKS!
Hey OP, thanks for developing and posting this. I can confirm that this works well and that it is really easy once the necessary files are downloaded.
I'm a newb, but after all these steps are done we should be able to save the stock ROM and I can download another ROM?
Mikeglongo said:
I'm a newb, but after all these steps are done we should be able to save the stock ROM and I can download another ROM?
Click to expand...
Click to collapse
That's exactly what you should be able to do. If you get it all installed and run the flash-clockworkmod-recovery.sh script successfully then you can do the following.
In preparation, download your ROM of choice to some place on your MicroSD card. If it's cyanogenmod you'll also need to install google apps. If you want to download it to your MicroSD card (gapps) and you'll install it later with clockworkmod. Once this is done back up the stock ROM:
power off the phone
hold down power and volume down until you see Android with a bunch of app icons then release both buttons
when the screen with red text comes up press volume down to scroll to "backup and restore" then hit power button to select
Backup should be highlighted so hit power to select
wait for the backup to complete
Now you should have a folder in /sdcard/_ExternalSD/clockworkmod/backup with a timestamp and the contents of your backup (the path may vary if you're on something other than the stock ROM). At this point you'll want to
navigate to "wipe data/factory reset" and let it complete
navigate to "advanced" => "Wipe Dalvik Cache" and let it complete
finally back to "install zip from sdcard" -> "choose zip from sdcard" and find the zip file with the ROM you downloaded above and install it
if you installed a ROM like cm7 that requires the google apps separately choose "install zip from sdcard" again, "choose zip from sdcard" and find the gapps zip you downloaded and install it
When it finishes you can reboot and setup your new ROM. You can of course backup the new ROM like you did before. At any point you can reboot into recovery (power off then hold power and volume down) and use restore to restore a previous backup.
worked great, thanks so much for your work!
Awesome, this might actually be what I was looking for, a big thanks to you.
Just one question, since T-mobile is sending me a new phone, shoud be here by thursday, might as well not install NVFLASH until thursday correct?
Mikeglongo said:
Awesome, this might actually be what I was looking for, a big thanks to you.
Just one question, since T-mobile is sending me a new phone, shoud be here by thursday, might as well not install NVFLASH until thursday correct?
Click to expand...
Click to collapse
Yeah, assuming you need to send your current one back you might just wait for the new one. Though you could flash cwm now, backup your stock ROM, flash some new ROMs just for fun then restore the stock ROM and flash the stock recovery before sending it back :-D. This virtual machine also includes my easy root/unroot scripts as well...
I may be able to host the VM image for you - Send me a PM if interested.
So, this is the "full" clockwork flash for a mac right? Not the "fake" one i keep hearing about.
Basically, this is flashing clockwork as described here (only, for a mac):
http://forum.xda-developers.com/showthread.php?t=1056847
propain4444 said:
So, this is the "full" clockwork flash for a mac right? Not the "fake" one i keep hearing about.
Basically, this is flashing clockwork as described here (only, for a mac):
http://forum.xda-developers.com/showthread.php?t=1056847
Click to expand...
Click to collapse
yes, the real clockworkmod as described in that thread. it's the external sdcard version of the 3.1.0.1 with ext4 support - though you can download and flash other versions if you want (see the Readme.txt in the nvflash folder)
jnichols959 said:
yes, the real clockworkmod as described in that thread. it's the external sdcard version of the 3.1.0.1 with ext4 support - though you can download and flash other versions if you want (see the Readme.txt in the nvflash folder)
Click to expand...
Click to collapse
Thanks - Let me know if you're interested re: hosting the VM.
Since I'm most likely flashing this way, what's a VM? Just because I'm a newb
Mikeglongo said:
Since I'm most likely flashing this way, what's a VM? Just because I'm a newb
Click to expand...
Click to collapse
virtual machine. in this case it's a linux computer that runs in a window on "virtual" hardware. that's what VirtualBox provides - the software to emulate a computer and allow you to run these virtual machines.
i went this route because nvflash is only available for windows or linux machines. a windows vm would not be free but a linux vm is and the nvflash (and root/unroot) tools run quite well on it, in fact arguably better than on windows since you don't need any device drivers
Ooops sorry I wrote in here meant to message you
How do you do the internal SD flash recovery?!
Mikeglongo said:
How do you do the internal SD flash recovery?!
Click to expand...
Click to collapse
Check the read me file in the g2x folder of the downloaded package. I think all you have to do is put rename the recovery file in the nvflash folder. Someone correct me if I am wrong, but I think the script is made to flash by name. So as long as you rename the file you want and rename the old file (so it is not flashed) you should be good.
Sent from my LG-P999 using XDA App
Edit: Nevermind.
gshine said:
Edit: Nevermind.
Click to expand...
Click to collapse
So did it end up working? Normally you need to watch the terminal that opens up and read the text in it. That should tell you when it's done, if it's successful, and what to do when it's finished.
Yes. not sure what happened on the first try, but the second one worked fine. I've backed up my original ROM, and installed CM7. I'm happy...for the moment!
jnichols959 said:
So did it end up working? Normally you need to watch the terminal that opens up and read the text in it. That should tell you when it's done, if it's successful, and what to do when it's finished.
Click to expand...
Click to collapse
**** USE AT YOUR OWN RISK ****
The following is posted so that I may share what I've done. It was done by me and for me. If you use it for you, then you take responsibility for whatever happens. This could, potentially, cause problems. It certainly will void your warranty (though it's pretty easy to undo this with no obvious signs.)
Install ClockworkMod Recovery and roots your P6210 tablet.
DO NOT ATTEMPT TO RESTORE ANY CWM BACKUP MADE WITH ANY OTHER VERSION/REVISION. IT WILL BREAK THINGS. THIS VERSION IS NOT BACKWARDS COMPATIBLE. JUST START WITH FRESH BACKUPS AND BE HAPPY.
WHAT THIS DOES:
Installed from recovery, this .zip will first ensure that it's running on the Samsung GT-P6210. If you have a different model, don't waste your time downloading it. It won't work. I have a P6210 to test with. I don't have any other 7 plus tab, so I can't test any other 7 plus tab, and therefore won't even act like it might work. If you want to try it anyway, you should have the knowledge to repair whatever you break - in which case you'll also have the knowledge to unpack this zip file and do things the manual way.
(starting with 20111210, a backup of the recovery is no longer made. I feel this is no longer needed as there is a confirmed working ODIN package people can use to restore their tablets with.)
Next, a new version of the clockwork mod recovery is installed.
(starting with 20111210, old backups are no longer purged. If you are upgrading from my original CWM recovery (previous to Dec 9th), please manually delete old clockwork recovery backups, as they are NOT VALID and will destroy your normal boot operation if you attempt to restore with a proper/current version of this recovery.)
Finally, the tab will be rooted. This only involves copying a tiny file (called 'su') to the system. In order for most android apps to make use of that, however, another application must be first installed. (See "Finishing SuperUser installation" below.) I considered putting that "SuperUser" application as part of this package, but it's really very easy to get it from the market.
INSTRUCTIONS:
Put the installation zip file on your tablet's external SD card. If you don't have an external SD card, you won't be able to install this. MicroSD cards are cheap. If you have a tablet that costs 399 USD, you can afford to spend a few extra dollars/euros/pesos/whatever on a microSD card. Just get one. Not only is it required for installing this from the factory recovery, but it makes a great place to back things up to. A nice 16GB card is suggested. 32GB is better. You'll need AT LEAST 1GB for this recovery. If you have a previous version of CWM already in-place, you won't need the storage card.
You can download the .zip file directly to your tablet and then possibly use the built in "My files" applet to move it to extStorages/SdCard, or you could download it to your computer and use "adb" to push the file to /mnt/sdcard/extStorages/SdCard, or you should be able to get it there with "Kies." If you have the proper adapter, you could also attach the microSD card directly to your computer and just copy it there. It doesn't matter HOW you get it on the card, as long as it's on the card.
After the zip file is on your microSD card, and the microSD card is inside (and recognized by) your tablet, then you need to...
Boot into recovery mode.
If the recovery version banner is "CWM-based Recovery v5.x.x.x", then you already have a version of CWM installed and should skip ahead to the proper section. If the banner is "Android system recovery (3e)", then you have the factory recovery and should continue with...
Installing from factory (3e) recovery:
Use the volume up/down buttons to move the highlight up and down, and the power button to select the highlighted option.
1. Select "apply update from external storage"
2. Select the file you placed on your storage card (starts with "p6210_CWMR".)
3. Sit back and watch it run. Read the information that is being sent to the screen. If there's an error, it'll display some message. If it works, it'll display a message starting with the word "Done!"
4. Select "reboot system now."
You now have a CWM-based recovery installed, and your tablet is rooted.
Please skip ahead to "Finishing SuperUser installation"
---------------------------------------------
Installing from CWM-based Recovery
Use the volume up/down buttons to move the highlight up and down, and the power button to select the highlighted option.
1. Select "Install zip from sdcard"
2. Select "choose zip from internal sdcard" (which will actually point to the external card.) (If you are upgrading and chose not to put the .zip on the external microSD card, you might need to select "choose zip from sdcard" instead.)
3. Select the file you placed on your storage card (starts with "p6210_CWMR".)
4. Select "Yes - Install (whatever filename you selected)"
5. Sit back and watch it run. Read the information that is being sent to the screen. If there's an error, it'll display some message. If it works, it'll display a message starting with the word "Done!"
6. Select "+++++ Go Back +++++"
7. Select "reboot system now."
---------------------------------------------
Finishing SuperUser installation
Install the SuperUser application directly from the android market:
https://market.android.com/details?id=com.noshufou.android.su
....
Post-installation Notes and Issues
It's a known issue with the version of CWM used in this recovery that the "internal sdcard" actually references the built in storage on the tablet. So, if you want to back up to your microSD card, choose "backup to internal sdcard". I'm retaining this issue to stay "compatible" with other CWM recoveries of the same version number. (won't fix)
The .zip package displays an incorrect version identifier/date when version 20111209 is being installed. (It's shows a banner with the date of 06-Dec) (cosmetic)
This recovery is NOT compatible with firmware updates via Kies (and perhaps not via other samsung official methods.) In order to perform a firmware update, I suggest the following procedure: First, perform a CWM Recovery backup, then use the ODIN package found elsewhere to restore this tablet to a factory state. Let Kies upgrade the tablet to whatever version it wants (give it a few tries in case multiple upgrades are needed.) Then re-install this recovery, and perform an "advanced restore" (or "advanced restore from internal sdcard if you made the backup using the similar option.) From there, restore "data." That will leave the entire firmware update in place. (boot is the normal boot kernel; system is what people like to call a ROM here, but is the samsung pre-installed apps; and data contains the applications you install and all your data.) Then "go back", wipe the cache partition, advanced, and wipe the dalvik partition. HOWEVER, please note that I have no way to know if any given samsung firmware update is "compatible" with this restore unless I've tried it myself. It's compatible with everything released up to the date of this note (10-Dec-2011), but I can't predict the future.
Donation?
I don't take donations. If you have spare money (I don't), please donate it to the Salvation Army, Red Cross, or just find a homeless person on the street and give them something. My favorite charity is the Shriner's Hospital for Children. (yes, I am.) If you'd like to thank me, there's a button at the bottom of this post dedicated to that. If you don't want to thank me, that's okay too.
Changes for 20120107:
Brought the recovery kernel up to date with the normal boot kernel. The only impact should be that if you keep crashing any time you boot normally (and before you are able to perform any action), you can now boot into recovery to _hopefully_ be able to retrieve the /proc/last_kmsg as a diagnostic tool.
Reduced the size of the .zip quite a bit.
Changes for 20111210:
* A backup of the existing recovery image is no longer being made. I feel this is no longer needed, as an ODIN package is now confirmed to be working that people can use to restore their tablets to a factory state.
* Old clockworkmod recovery backups are no longer being deleted when installing this. If you are installing this or newer from my CWM recovery previous to Dec 9th, 2011, please manually delete all those old backups. If you attempt to restore them, please be prepared to download ODIN and a factory ODIN image, as you'll need it in order to get your tablet working again. You've been warned...
* The issue that was causing backups to the tablet's built-in storage to fail has been corrected.
Changes for 20111209:
* Issues with getting into recovery are resolved.
* a backup of the recovery is only made if there is no sign of a previous version of this same recovery in place
Credits
Most obviously, Koush for his wonderful clockworkmod recovery. It's the basis of this entire project. Entropy512 for pointing me in the proper direction on a couple of things, pershoot mods to CWM for the Galaxy Tab 10.1 that I ported over to this one (due to the different partition structure of honeycomb devices.)
Links are below...
Take care
Gary
thanks gary, how might we be able to tell if this will be kosher with 3g version? do we need to --dump all pit via heimdall to ensure all partitions match up,etc? Thank you for your speedy work.
chrisrotolo said:
thanks gary, how might we be able to tell if this will be kosher with 3g version? do we need to --dump all pit via heimdall to ensure all partitions match up,etc? Thank you for your speedy work.
Click to expand...
Click to collapse
It's not kosher at all. I didn't wash my hands before compiling it, and had bacon bits on my salad for lunch. Sorry.
Thanks Gary. I have been watching your progress for about a week and you are like a put-bull. Amazing. u da man!!!
Pit bulls would be shamed as wussies. Many great devs possibly have a touch of Asperger's syndrome (with MUCH better socialization skills!) which, with tasks like this, is a benefit! At the very least just plain tenacious! lol
Thanks Gary. I've learned a lot just following along reading the discourse between you and others like Entropy. Appreciate it.
garyd9 said:
It's not kosher at all. I didn't wash my hands before compiling it, and had bacon bits on my salad for lunch. Sorry.
Click to expand...
Click to collapse
ahhh , close enough. anyways what could we do to find out without actually flashing this to possible incorrect partition??
chrisrotolo said:
ahhh , close enough. anyways what could we do to find out without actually flashing this to possible incorrect partition??
Click to expand...
Click to collapse
Which "3g" model do you have? The tmobile one or the international one?
I'm trying to narrow down which is the GT-P6200 and which is the SGH-T869!
I'm working with someone via PM and email to get the information needed for the SGH-T869, and I think it'll be pretty easy to get a recovery together for it, but other people will have to test and validate. I think this is the tmobile version...
international p6200
Soft Brick(kinda Sorta - well not really). Using defult 3e recovery. Tab would boot up, but would not go into recovery at all. Nada Nada. Thought it might have been some leftovers from other stuff I have been trying, so I odin3'd the factory image, did a wipe all and tried it again. Same difference. The only thing I could really think of was maybe I had a corrupted download.
funny thing is that it would boot up into the OS. Just not into recovery. will keep trying as I really want a way to make nandroid backups.
otamctech said:
Tab would boot up, but would not go into recovery at all.
Click to expand...
Click to collapse
No need to ODIN... that's why the package creates that backup recovery image. However, you said it's booting normally, correct? If so, it's not broken or bricked (and I experience the exact same thing.)
For some odd reason (that I haven't been able to figure out), after I flash a non-stock recovery, its very difficult to get the tab into recovery mode. Some times I get it instantly, and some times I have to try several times in a row. Are you using adb? If so, it might be easier. Power off the tab, plug it into your computer, and eventually the tab goes into a "low power mode" where you see the battery gauge but nothing else. From there (again, assuming you have adb installed/working), you can just run "adb reboot recovery" That usually gets me into recovery. 90% of the time.
If not, just try again. If you see the samsung animation starting, press/hold the power button to turn it off again, then press/hold volume up again... etc. It's a PITA, and a major annoyance of mine.
Two things about it make it REALLY annoying for me. First, I'm using samsung's own kernel for this... but I'm just repacking the initramfs portion of it. Second, if you put the factory recovery back, it's easy to get into recovery again.
chrisrotolo said:
international p6200
Click to expand...
Click to collapse
I'll get to that one eventually. I'm commited to do the tmobile one next, and I REALLY need to concentrate on my full-time job (the one that pays me a salary) which only leaves me a couple hours each day.
take care
Gary
absoultely, take your time. Is there a certain battery percentage requirement to get into either stock or CWM recovery say 50% or 60% minimum? we had this issue on dell streak 7. Let me know if I can help with partition layout or anything for p6200. thanks.
chrisrotolo said:
absoultely, take your time. Is there a certain battery percentage requirement to get into either stock or CWM recovery say 50% or 60% minimum? we had this issue on dell streak 7. Let me know if I can help with partition layout or anything for p6200. thanks.
Click to expand...
Click to collapse
No hard requirement I'm sure - but flashing at below 50% is just a stupid reckless risk, plain and simple as that.
If you are having issues getting into recovery after flashing this...
Here's a procedure I've come up with that has allowed me to get into this recovery 9 out of 10 attempts (and it doesn't require any special connections to a computer.) Please read all the steps before starting so you're prepared for what comes next. It'd really be annoying to have recovery finally pop up, but you weren't paying attention so the tablet turned off.
power off the tablet
Throughout this entire process the volume UP switch should be held and not released. This is the side of the volume switch closest to the power button. Once you see your recovery screen, you can release the volume switch (and any other button you might be holding at that time.)
Press/hold Volume Up (constant)
Press the power button, hold it down for 2-3 seconds, and release it.
You'll see the Samsung logo screen for a few seconds...
Instead of the expected recovery screen, you might see the samsung boot animation with music. If so, immediately (without releasing volume up), press and hold (and keep holding) the power button. Don't let it go this time.
The tablet will appear to power off after holding the power button for a few seconds, and then will power back on a second or two later.
(you're still holding that power button, right? how about volume up? Good.) Again, you'll see the samsung logo screen for a few seconds...
Instead of the boot animation, recovery should pop up this time. Release the power button as soon as it does or you'll just turn the tab back off again. You should also release the volume UP at this point.
(If you've flashed my recovery, please try this. If it doesn't work, please take the effort to reply to this post so I can know what people other than myself are experiencing.)
Take care
Gary
updated OP with:
Post-installation Notes and Issues
I'm aware that after flashing this, it is difficult to get back into recovery. I'm not sure WHY, but it's fairly consistantly a pain in the rear. However, I have found that following the steps in the following post seems to work (at least for me) 9 out of 10 times. (I was distracted on the 10th try, so not sure if it worked or not): http://forum.xda-developers.com/show...6&postcount=14
Remember above I mentioned that when this package installs, it creates a backup of the old recovery? Well, it does that no matter what recovery was in place. So, if you install this package with a factory recovery, that backup will be of the factory recovery (which is probably what you want.) If you install this package a second time when you already have the CWM Recovery installed, you'll overwrite that factory recovery backup with a backup of the CWM recovery (which makes no sense.) I'd strongly suggest that after you FIRST install this package, you make a copy of that backup recovery image file (and full filename is displayed when it's created), and stick that copy someplace safe. Perhaps just rename it and copy it to your SDcard or computer. A good name might be "p6210_factory_recovery.img"
The Tab 10.1 could be difficult to get into recovery too.
Usually, the following works for me:
Press and hold VolUp
Press and hold Power until the screen turns on (this is slightly different from your instructions)
Release Power but keep holding VolUp until Recovery shows
__________________
somebody9 said:
I was wondering if anyone knows what needs to be deleted in order to get rid of that pesky pop up menu you get by pressing on the Chevron/Arrow in the middle of the bar.
Click to expand...
Click to collapse
Please start a new thread for a new topic. Try to keep this one isolated to the CWM recovery.
garyd9 said:
Please start a new thread for a new topic. Try to keep this one isolated to the CWM recovery.
Click to expand...
Click to collapse
Sorry about that. Post removed.
Garys method of booting into recovery works fine. I'm just going to post it in linear format.
1. Press the power button and select Power Off
2. Press the volume up button (closest to power button) and do not release until the recovery screen is displayed
3. Press (do not hold) the power button
4. The static Galaxy 7.0 Tab Plus screen will display (possibly twice)
5. When the animated Samsung screen displays, press and hold the power button
6. The static Galaxy 7.0 Tab Plus screen will display
7. Release all buttons when the recovery screen displays.
This works every time for me