Related
PLEASE READ THE *FAQ* BEFORE FLASHING OR ASKING QUESTIONS!!
This *Easy Guide* is for the all the Noobs that want a New Rom but are getting confused and dont want to brick their nice new phone.
I used Jockys HardSPL v3.29 and OliPros' CID Unlocker for this.
Before you start, backup anything on your phone that you might want to keep after the new Rom has been flashed because all contacts/ emails/ texts/ notes/ Internet BookMarks/ ect. WILL be lost!!
PimBackup is good and free (copy any mms attachments to your storage card or computer seperately)
If you get stuck in the Bootloader Screen (Tri-Colour Screen with text in the top left) go *HERE* (thanks to DaveShaw)
*STEPS 1 - 4 ONLY NEED TO BE CARRIED OUT ONCE. ONCE YOU HAVE FLASHED HARDSPL YOU DONT NEED TO DO IT AGAIN WHEN FLASHING NEW ROMS OR RADIOS*
*DO NOT start another process while the flashing process is taking place*
*DO NOT click off of the status bar... Let it stay in the foreground*
*DO NOT let the ScreenSaver activate*
(any of these can lead to a bad flash and possibly brick your phone)
1. MAKE SURE YOUR KAISER HAS AT LEAST 50% BATTERY POWER FIRST
2. Download and Unzip *THIS* File
3. Flash HardSPL 3.29 [ESSENTIAL]
Flashing via ActiveSync with USB Lead
1. Copy JumpSPL1.56-KAIS.exe, JumpSPL1.93-KAIS.exe and JumpSPL1.94-KAIS.exe to your device memory (NOT STORAGE CARD)
2. Pull out the battery and reinsert it (this step IS important) *DONT turn phone back on yet*
3. REMOVE SIM and SD CARDS!!
4. Turn phone back on and let it boot back into your operating system
5. Connect your phone to PC with a USB cable and wait until it syncs with your PC
6. Run File Explorer on your phone, browse to where you copied JumpSPL1.56-KAIS.exe on your device and run it (make sure the USB cable is still connected). If you get a white screen then reset your device and now try JumpSPL1.93 and lastly try JumpSPL1.94 if that one doesnt work.
7. CLick Continue on phone when prompted
8. After a few seconds the tri colour screen will appear on the phone and "USB" will be displayed at the bottom
9. Unplug the usb cable for 30 seconds and then Replug (phone will not re-sync but still says "USB" on the screen)
10. Right click on the Activesync icon in the bottom corner icon on the computer, goto connection settings, deselect "Allow USB connections" and click "ok"
11. Run the KaiserCustomRUU.exe file on your PC thats in the same folder as the HardSPL .nbh file and follow instructions (ticking boxes and clicking Next) *DO NOT re-enable USB Connections in Activesync*
12. Update will goto 100% (should take less than a minute), the Congratulations screen will be displayed on the PC and the phone will restart
13. Unplug USB cable from phone then REPLACE SIM and SD CARDS !!
14. Restart phone
*Remember to re-enable "Allow USB connections" in Activesync connection settings after a successful flash*
Flashing via MicroSD Card using cmonex HardSPL 3.29 [OPTIONAL]
FOR UPGRADING HARDSPL ONLY!! THIS WONT WORK UNLESS YOU ALREADY HAVE HARDSPL ON YOUR PHONE
1. Make sure your microSD is Formatted to fat32 (you dont have to delete all files but it is safer if you do)
2. Download Cmonex's HardSPL 3.29SD, unzip it and copy the 2 files into the root of your MicroSD Card
(KAISDIAG.NBH is basically an SSPL patched to load from SD without booting OS)
(KAISIMG.NBH is cmonex HardSPL 3.29)
3. Insert the microSD Card into the phone
4. Hold in the Power and Camera buttons, then press the reset button with the stylus for about 3 seconds until the BootLoader screen appears
5. It should say Loading / Update in progress and then to a screen saying SPL 1.00.OliNex
6. It should now say Press Power Button to flash or just flash the KAISIMG.NBH and then reset
7. At this point it should boot to the OS, if it doesn't then flash an OS (delete the previous KAISDIAG.NBH and KAISIMG.NBH from the SD Card and use Flashing Rom from MicroSD Card method)
8. After the Operating System loads, DELETE the KAISDIAG.NBH and KAISIMG.NBH files
*To check HardSPL version on your phone Enter Bootloader by Holding in the Power and Camera buttons, press the reset button with the stylus for 3 seconds until the tri-colour screen appears, then read the 2nd line which is the SPL version*
4. SIM and CID-Unlock [OPTIONAL]
For more reading go *HERE*
* YOUR DEVICE MUST BE SYNCHED WITH YOUR COMPUTER BEFORE RUNNING EACH STEP *
*Put your phone into Bootloader and update to a 6.1 Rom first if you get a black screen after Flashing the Patched Radio*
*If the program wont run u may need to install Microsoft .NET 2.0 on your computer to get it working*
1. Make a note of your current Radio in case you need to flash it back
2. Run KaiserUnlocker.exe, follow the instructions
(if you already have HardSPL on your phone you can skip straight to Step2)
3. After patched Radio has been flashed phone will restart and sync with the computer
4. On the Unlocker Program it should say Radio Patched at the bottom
5. Click on Step3 (Run Unlocker). This will bring up the Unlocker screen on your phone
6. If you want to check the status of your Sim Lock or CID Lock click the appropriate buttons
7. Click on Remove Sim Lock and Set CID, then click "Commit Changes"
* IF YOU DONT NEED TO FLASH A NEW ROM THEN PROCEED TO STEP6 TO PUT YOUR DESIRED RADIO BACK*
5. Download and Flash your Prefered Rom
Flashing Via ActiveSync
1. REMOVE SIM and microSD CARDS !!
2. Turn phone back on and wait until it syncs with your PC
3. Run the KaiserCustomRUU.exe from the Roms Folder
4. Once phone finishes flashing, resets and gets to the screen where it configures the stylus, HARD RESET
(press left and right softkey buttons on the front and hold in reset with stylus until message appears)
5. When prompted, Press "Send Button" (Green Call Button on Front) to Clear Data
6. When prompted, Press "Send Button" (Green Call Button on Front) to Restart Phone
7. Follow onscreen instructions to set up your New Rom
8. Once phone has gone through customisation procedure then replace Sim and microSD Cards
9. Turn phone back on and set up as required
Flashing Via MicroSD Card
1. Make sure your microSD is Formatted to fat32 (you dont have to delete all files but it is safer if you do)
2. Download your prefered Rom from the Kaiser Rom Develpoment Page and unzip/unrar it to your computer
3. Goto the Roms Folder and rename the .nbh file to KAISIMG.nbh
4. Copy the KAISIMG.nbh file to the root of your MicroSD Card
5. Plug the MicroSD Card into the phone
6. Hold in the Power and Camera buttons, then press the reset button with the stylus for about 3 seconds until the BootLoader screen appears
7. You will first see a tri-color screen with the phone and SPL Information at the top
8. A message will then pop up asking you to press the Power button to start the update
9. Press power button to start flashing
10. Once phone finishes flashing and says Update Complete, reset with the stylus
11. When it gets to the screen where it configures the stylus, HARD RESET
(press left and right softkey buttons on the front and hold in reset with stylus until message appears)
12. When prompted, Press "Send Button" (Green Call Button on Front) to Clear Data
13. When prompted, Press "Send Button" (Green Call Button on Front) to Restart Phone
14. Follow onscreen instructions to set up your New Rom
If you have a Tilt and have problems with the Hardware Keyboard after flashing just install *THIS*
6. Flash Prefered Radio if Desired [OPTIONAL]
Note: Most of the newer Roms come with a Matched Radio included but if you need to update your Radio then look here:
The Ultimate Radio Thread and find a Radio that matches your Rom.
*MAKE SURE YOU HAVE HARDSPL ON YOUR DEVICE AND AT LEAST 50% BATTERY BEFORE FLASHING*
Flashing Via ActiveSync
Sync your phone with the computer and run the KaiserCustomRUU.exe from the Radio's Folder
Flashing via MicroSD Card
Use same method as Flashing a Rom via MicroSD except after Radio has flashed, press the reset button with the stylus to reset the device.
7. Job done Well Done YOU DID IT.
I have attached all the files needed so you dont need to hunt around for anything. Good Luck.
*DISCLAIMER*
I take no responsibility for any fault, or damage caused by any procedures in this guide. No warranties of any kind are given.
Flashing your First Rom (For Noobs)
** FREQUENTLY ASKED QUESTIONS AND HELP WHEN FLASHING **
*BEFORE FLASHING A NEW ROM PLEASE PLEASE PLEASE READ THE LIST OF INSTALLED APPS INCLUDED IN THE ROM. ALSO READ THE ROMS THREAD FROM THE DATE YOUR VERSION WAS UPLOADED TO GET INFORMATION ABOUT ISSUES OR PROBLEMS SO YOU KNOW EXACTLY WHAT YOU ARE PUTTING ON YOUR PHONE*
1. What are the benefits of flashing a new rom?
2. What is the SPL (Second Program Loader)?
3. What are the different types of Unlock? (answer by DaveShaw)
4. What is a Radio?
5. What is Manila2D?
6. Whats the difference between Hard and Soft Reset? (and How to perform a Hard Reset)
7. After I flash a Rom I dont have any sound in calls and the camera is black
8. I get an Error Code when trying to Flash
9. Flash gets Stuck at 17% and wont finish
10. Screen on phone goes black after flashing Radio for Sim Unlocking
1. What are the benefits of flashing a new rom?
Flashing a New Rom basically gets rid of all the bloatware thats included on Stock Roms and Flashes a Clean, Optimized, Fully loaded Rom that will squeeze every ounce of speed and stability from your phone. Chefs usually include all the programs you are ever likely to need and because the Rom has been cleaned out you are left with more memory to play around with.
2. What is the SPL (Second Program Loader)?
Read *HERE* for more information.
3. What are the different types of Unlock? (answer by DaveShaw)
The three stages of unlock are:
SIM: Allows you to use SIM's from another carrier. Can be done using codes or unlocker programs on xda-devs.
Security: Allows you to flash radios from another device - It does other stuff, but this is all the casual user will use it for
CID: CID unlocking is an old concept, nowadays you flash HardSPL instead. This lets you flash any ROM, Splash or Radio (depending on sec unlock) to your device. N.B. the CID is the carrier ID (e.g. HTC__001). The stock SPL's only let you flash ROM's that match the CID in the ROM image with the CID on your device.
Also, SuperCID is an even older concept no longer valid on newer devices.
4. What is a Radio?
The Radio is the Firmware that works between the Operating System and the Cellular Hardware. It handles the Sound, Camera, GPS, Phone Calls, etc. The Radio must be compatable with the ROM's Operating System or you may experience problems with your sound and camera.
5. What is Manila2D?
Manila2D is a Great Today Screen Plugin that disables all other plugins and replaces them with a fully loaded interface that gives you easy access to your phones programs. It has a customizable number of Sliding Tabs at the bottom, each tab giving you a screen specific to your needs.
The Tabs are as follows: "Home" has a clock, alarm mode, call history and calendar. "People" gives you a picture contact for easy calling or texting. "Launcher" lets you set up a list of programs that are easily accessable from one screen. "Messaging" and "Email" give you a very attractive and easy way to read and manipulate your messages. An "Internet" Tab with easy Internet Browser launching and the option to add one press shortcuts. "Location" lets you access your GPS quickly via GoogleMaps and "Weather" has great graphics to let you see what its like outside without having to step out of your door. "Photo" and "Music" lets you view your Media quickly without the need to run a seperate program and last but not least "Settings" gives you control of your Sounds, Wallpaper and Communications.
For more information on Manila2D Development and to download it go *HERE*
Most aspects can be customized using a great program called M2DC which you can download *HERE*
Manila2D is a beta plugin still in development and doesnt work at all well in Landscape mode, so its best to use it in Portrait mode and then flip out your keyboard once you are in the program you need to use. If that bothers you then dont use it.
6. Whats the difference between Hard and Soft Reset?
Soft reset is basically the same as rebooting your computer. Its done by pressing the stylus into the little hole on the bottom of the kaiser to the right of the usb connector. It just restarts the kaiser if you have been doing alot of stuff on it and want to speed it up or after installing some software that needs a soft reset to complete the installation.
Hard Reset is completely different and you would be hard pressed to do it by accident lol. Its done by holding down the left and right soft keys and then pressing the soft reset button with the stylus for approx 3 seconds. You will then be given the option to press the green send button which will wipe all stored data on your phone and return it to the orginal condition it was in after first flashing it. Hard Resets are performed after flashing to make sure nothing was left from your previous Rom or if something goes wrong on your phone and you want to go back to a fresh Rom without reflashing it.
How To Perform a Hard Reset (from the Wiki): Read *HERE*
7. After I flash a Rom I dont have any sound in calls and the camera is black
The Radio has to match the version of Rom you flash i.e. WM6.1, an incorrect Radio will give sound and camera problems. Read The Ultimate Radio Thread to find a Radio that matches the Rom there are lots to try on there if one doesnt work then try another.
8. I get an Error Code when trying to Flash
Read *HERE* for a list of all RUU Error Codes and possible solutions.
9. Flash gets Stuck at 17% and wont finish
Enter recovery mode to finish flashing by following these steps:
1. From the Rom Update Utility on the PC click "Recovery"
2. Disconnect the USB cable
3. Remove the battery for 3 secs
4. Put the battery back in and power up the phone
5. At this point the tri colour screen should appear
6. Connect the USB cable
7. Click "Update" and the RUU installer starts again and flashes.
10. Screen on phone goes black after flashing Radio for Sim Unlocking
The screen is black because the radio that is flashed to the phone to unlock it is incompatable with your current rom. As long as you have flashed HardSPL then you wont have any troubles.
If you are planning to upgrade your rom to a new one then flash it via the microSD Card method and then go back after and do the Sim unlock stage (remembering to flash back a compatable radio after you finish unlocking it). If you dont want to upgrade the rom then you need to flash a radio that works with your rom (see The Ultimate Radio Thread).
Thanks for the excellent post. What does ** YOUR DEVICE MUST BE SYNCED BEFORE RUNNING EACH STEP ** mean? Do you mean just ActiveSync? Doesnt ActiveSync just sync contacts, calendar etc., so how does that matter ?
mindspawn said:
Thanks for the excellent post. What does ** YOUR DEVICE MUST BE SYNCED BEFORE RUNNING EACH STEP ** mean? Do you mean just ActiveSync? Doesnt ActiveSync just sync contacts, calendar etc., so how does that matter ?
Click to expand...
Click to collapse
Yes it means ActiveSync and when you sync your phone with the computer it links the 2 so that you can perform flashes or run programs on your computer for use with the phone.
Nice one.
I often wanted to write this myself, but couldn't find the time for another project.
If one of the Kind Mods would sticky it...?
Just my opinion... if the chef's linked to this page as part of their "Instructions" it would save a few newbie questions.
My first ROM flash, back in the Wizard days, was: find a nice ROM, read instructions in the ROM thread, which linked me to a similar thread, then flash the ROM. Tada.
Ta
Dave
MOD EDIT: Ask and ye shall receive. I wonder if you could put in in the Wiki Too?
JimmyMcGee said:
MOD EDIT: Ask and ye shall receive. I wonder if you could put in in the Wiki Too?
Click to expand...
Click to collapse
It's mostly in there already, it's just disorganised.
I'd love to re-shuffle all the info into a proper order, but I'm waiting for the wiki upgrade first.
Ta
Dave
Just two comments.
There are two methods to Security Unlock your phone. The first one is the one mentioned in this thread. It seems to work well for some but in my personal case, it didn't (well, I'm still not sure about it). What can happen if you follow method #1 is that although the Tri-color screen states "Security Unlocked", once you flash a new radio, that message will dissapear. If this means that the phone isn't security unlocked anymore is something that remains to be cleared up. I did change my CID and it did remove the simlocks despite the message dissapearing once you flash back your original radio.
The second method is the one described here: http://forum.xda-developers.com/showpost.php?p=1837147&postcount=1
This is the Jockey method. It is a little more complicated than method #1 but it allowed to unlock my device and have the "Security Unlocked" remain in the tri-color screen no matter what HardSPL and Radio I flashed since I unlocked it.
I'm not saying that method #1 doesn't work, I'm just saying that in my particular case, the "SU" message didn't stay permanently and since I had my doubts, I tried method #2 which worked flawlessly for me.
Good Luck
Tony
Nice work mate
Nice job.
May also be worth mentioning that points 1 through 4 only need be carried out on any phone ONCE. After which, you can download and flash new ROMs to your heart's content, until you find the one that's right for you.
Bryn
brynweb said:
Nice job.
May also be worth mentioning that points 1 through 4 only need be carried out on any phone ONCE. After which, you can download and flash new ROMs to your heart's content, until you find the one that's right for you.
Bryn
Click to expand...
Click to collapse
Done. Thanks for pointing out
Small Addition
I would like to add to this post....
While the flashing process is taking place, DO NOT start another process.
DO NOT click off of the status bar... Let it stay in the foreground.
DO NOT let the screensaver activate either.
Any of these things can take processor time away from the flashing process and could possible "hiccup" the flash, causing a bad flash and possibly (slight possibility) brick the device. Especially if you are replacing the SPL.
There are alot of posts that tell how for the newbs to flash their device, but I see ALOT of posts that say "I followed the directions, but still bricked, HELP"
I can only wonder if they are starting the flashing process then going to internet explorer (or some other browser) or loading another program to ocupy their time while the flashing is going on which is causing a bad flash.
My thoughts......
Excellent tutorial. Thanks.
But, can you explain what SPL and CID stand for.
Whats hardSPL (or softSPL for that matter) And why do i need to unlock my CID!
Thanks again!
RedMist said:
Excellent tutorial. Thanks.
But, can you explain what SPL and CID stand for.
Whats hardSPL (or softSPL for that matter) And why do i need to unlock my CID!
Thanks again!
Click to expand...
Click to collapse
Second (ary) Program loader
Carrier ID.
Have look here for more information on SPL's hopefully it will clue you in: http://wiki.xda-developers.com/index.php?pagename=SPL Questions?
Ta
Dave
StevesDesigns said:
I would like to add to this post....
While the flashing process is taking place, DO NOT start another process.
DO NOT click off of the status bar... Let it stay in the foreground.
DO NOT let the screensaver activate either.
Any of these things can take processor time away from the flashing process and could possible "hiccup" the flash, causing a bad flash and possibly (slight possibility) brick the device. Especially if you are replacing the SPL.
There are alot of posts that tell how for the newbs to flash their device, but I see ALOT of posts that say "I followed the directions, but still bricked, HELP"
I can only wonder if they are starting the flashing process then going to internet explorer (or some other browser) or loading another program to ocupy their time while the flashing is going on which is causing a bad flash.
My thoughts......
Click to expand...
Click to collapse
Added any additions to make this process easier to understand and safer are welcome.
StevesDesigns said:
There are alot of posts that tell how for the newbs to flash their device, but I see ALOT of posts that say "I followed the directions, but still bricked, HELP"
I can only wonder if they are starting the flashing process then going to internet explorer (or some other browser) or loading another program to ocupy their time while the flashing is going on which is causing a bad flash.
My thoughts......
Click to expand...
Click to collapse
That is a good idea to make sure that it is clear to new users. Personally, in my experience when a user says "i followed the directions, but still bricked, HELP" it is because they PRETTY MUCH followed the directions, but forgot something when they were reading. It's really easy to do, but often leads to mistakes and undesired results.
Hi, thanks your wonderful instructions, I flashed my tilt to hyperdragon III. Just a few comments:
You mention remove sd and sim cards. Please also mention at what stage it is safe to put them back into the phone.
In section 3 step 10, you mention follow instructions. I dont think one should try to active sync (it is part of instructions of the rom upgrade software) since we disabled usb connection in activesync.
Thanks a million
I can't thank you enough for this tutorial. I was having a hell of a time finding exactly how to do it. I followed this step by step and it was a breeze. I had the new 6.1 ROM on my tilt and it was just pissing me off so now (thanks to you) I'm running HyperDragon III.
SPIDERTECH said:
I can't thank you enough for this tutorial. I was having a hell of a time finding exactly how to do it. I followed this step by step and it was a breeze. I had the new 6.1 ROM on my tilt and it was just pissing me off so now (thanks to you) I'm running HyperDragon III.
Click to expand...
Click to collapse
Im glad it gave you the confidence to upgrade to a great new rom its the reason I wrote it. XDA is a caring and supportive community and there will always be someone willing to help out if you need it. Mark.
This all speaks on Flashing your ROM..but how about
simply Flashing the Radio? What steps should I follow..and yes I am a newbee.
babyface215 said:
simply Flashing the Radio? What steps should I follow..and yes I am a newbee.
Click to expand...
Click to collapse
To be safe, all of them.
** 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.
Tutorial/Walkthrough for flashing back to stock using RSD Lite (Unrooting a rooted phone by .sbf)
Tutorial Video can be found here... kind of... very close!
http://www.kimete.com/sbfrsd.html
= = =
The fine print: This information is provided without warranty. I can not be held responsible if you **** up. I simply wrote a walkthrough/tutorial. I did not produce the procedure or the steps. I just simply consolidated all the information into a single place with notes to make things easier to understand and execute. You are welcome to share this information anywhere you want. Please do credit me for writing it. Lastly, please link back to the original site if possible. I try to format the text in such a way that it is more easy to understand. Lastly, I ask that everyone who uses this pays it forward by helping others figure out their own phones. Now on to the procedure.
I am running Windows XP SP3/32bit.
= = =
Steps 1 and 2 can be skipped. You just need to download the latest version of the SBF file (currently 2.3.20). Link coming soon.
1. Download 2.3.20 SBF file for D2
You can find it here: http://www.iamthewalcs.com/Support-Files/Droid 2 2.3.2 SBF.zip
2. Extract the .zip file and put the .sbf file somewhere where you can easily find it.
3. Download RSD Lite 4.7. (RSD Lite 4.7 is not the same as RSD Lite 4.7.2)
[RSD Lite 4.9 works as well]
Reference: http://www.mydroidworld.com/forums/droid-2-how-tos/4393-how-sbf-flash-droid-2-a.html
RSD Lite 4.9 Here!
http://droid2files.com/tools/RSD Lite 4.9.zip
New: Download to RSDLite 4.7 with patch.
http://kimete.com/droid/RSDLite47patch.zip
There is a link to download RSD Lite 4.7 + patch here as well. Includes an installer (.msi) and the patch (.ini).
4. Install the program (rsdlite_4.7.msi) or RSDLite 4.9. Follow instructions until completion.
5. Next, extract the patch (pst_flash.ini) to the Motorola/RSD Lite folder. It'll ask you if you want to overwrite the file. Choose yes. (Don't think you need this for version 4.9, but don't quote me on that).
(My file path to place the file was: My Computer -> C Drive -> Program Files -> Motorola -> RSD Lite)
6. You'll need to have the Motorola Drivers. You probably already have them, but if you don't, you can get them here:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
KalenXI noted that you can't use the same Motorola drivers that you used for root from the other thread. You must use these updated drivers with MotoConnect. Thank you sir!
7. Now would be a good time to back up anything on your SD card to your computer. Plug in your Droid2 to the computer via USB cable. Pull down the notification menu/blind, choose USB connection, and then choose USB Mass Storage Device. Now there should be a removable storage in your "My Computer." Go through your SD card and back up your important things. Probably the DCIM and download folder. You should also make sure that your phone is set up to "Back Up Data." Go to the system menu (the 4 squares icon/button in the lower left), choose Settings, then Privacy, then make sure the "Back up my data" and "Automatic restore" are checked.
8. You now need to put your phone in bootload mode. In order to do so, power down your phone. Slide open your keyboard, hold the "up" key (the arrow closest to the enter button), and power on your phone. You should come up with a black background and text with something along the line of d2.35 and usb okay.
9. Now you can open RSD Lite. Go to your Start Menu, Program Files, and you should see RSD Lite. In the title of the newly open window, make sure the version is 4.7.
Edit: If you opened RSDLite and your device is not showing, you might need to open it as an admin. Go to program files/motorola/rsdlite/sdl.exe, and right cllick and run as an administrator. Reference by JonandRoid. http://forum.xda-developers.com/showpost.php?p=8000565&postcount=12
10. Wait a few minutes until your device shows in the table. It should say A955, port 1, connected, etc.
11. Toward the top of the window, there is filename/blank field. To the right of it, there is "..." button. Click it. Now find your .sbf with the open window that popped up. Select "Droid2_X6_2.2...SECURE.sbf", or the latest version of your sbf, and press open. Back to the program window, press Start (right next to the "...") Your phone should now start flashing the firmware to the phone. Just let it run it's course. It's going to reboot and start up again. You'll know when it is done when the Progress field in the table of RSD Lite says complete. This may take a little bit. Maybe 5-10 minutes.
After your phone reboots and doesn't get past the boot animation (wait at least 5 or 10 minutes),
a. Turn off your phone
b. Hold down X on the keyboard
c. Turn on your phone while continuing to hold X
d. When you get the Android guy with a '!' in a triangle push the search button on the keyboard (the magnifying glass button, two keys to the left of the space bar)
e. Select both 'wipe cache' and 'wipe data' from the menu.
f. Reboot your phone
If you do steps a-f, you probably won't need to do these following steps.
12. I do not know if this will work or not, but if it does, you guys might not need to do the rest unless you truly do want to fully factory reset your phone. This step is UNCONFIRMED.
To get back onto the Verizon Wireless network, dial *22899 and press send. It should update your phone and you'll be back on the network. (Referenced from ITGuy11 at the link below.)
http://forum.xda-developers.com/showpost.php?p=7933189&postcount=12
13. Your phone still has everyone on it. You'll probably realize that you now have no 3G or phone service and are roaming. Now you need to Factory Reset your phone. Go to the system menu (the 4 squares icon/button in the lower left), choose Settings, then Privacy, the choose Factory Data Reset. Follow the instructions and agreeing to wipe your phone clean. It will ask you to confirm, and/or ask you to enter your security pin/security pattern. It'll reboot itself and run its course.
14. Your phone will eventually be put back to factory settings. You'll then be greeted by the new user/account wizard. Follow the directions. They'll ask you to program/update your phone, enter in some login info, and then your phone will be back to brand new, just like the day you walked out of the Verizon store, except with the BackUp Manager service, all your applications and contacts will be downloaded back onto the phone!
That's it! That wasn't so bad was it?!
= = =
If you found this tutorial helpful, and would like to do something for me, please donate to my PayPal. I am short on rent by $100 this month. I am a student, and moving to a new place and I need to produce first months rent, last months, and a deposit. I am not expecting to profit from this tutorial. Honestly, I am just doing this to help others. I just need some help with rent this month. All donations are appreciated, even if it is a dollar. If everyone donated even a dollar or two, I'd be set! PayPal info coming soon!
Another edit: PayPal: [email protected]
Another quick note, I'll be adding references sometime soon. It is almost 5 in the morning and I want to go to bed!
This is awesome, thank you. This tutorial and your rooting instructions (with all of the extra clarification) are very helpful. I know it's not much but I am going to try to send a few bucks your way (from one poor college student to another? ).
USB debugging should also be enabled. It's found in the Settings -> Applications -> Development.
bcs296 said:
This is awesome, thank you. This tutorial and your rooting instructions (with all of the extra clarification) are very helpful. I know it's not much but I am going to try to send a few bucks your way (from one poor college student to another? ).
Click to expand...
Click to collapse
Thank you. Any little bit is appreciated. Just need to get to the end of the week.
wsfanatic said:
USB debugging should also be enabled. It's found in the Settings -> Applications -> Development.
Click to expand...
Click to collapse
Thank you, sir. I will post that in the tutorial in a moment.
= = =
Also, according to ITGuy11, you can dial *22899 to update your phone to get it back on the Verizon network.
http://forum.xda-developers.com/showpost.php?p=7933189&postcount=12
I am a fail. Didn't read the whole tutorial. Assumed it was like the D1 sbf. Ok still have an issue though, When i get to the bootloader RSDlite and my phone do nothing, still says im missing a certain driver for the phone S Flash driver not found. Anyone know why thats happening?
LosAngeles said:
I am a fail. Didn't read the whole tutorial. Assumed it was like the D1 sbf. Ok still have an issue though, When i get to the bootloader RSDlite and my phone do nothing, still says im missing a certain driver for the phone S Flash driver not found. Anyone know why thats happening?
Click to expand...
Click to collapse
I had that same error, upgrading to the latest Motorola drivers fixed it. I'd post a link but the forums won't let me so just search for "motorola drivers" on google, go to the first link, go to "USB Drivers and PC Charging Drivers" and download the "Motorola 4.6.5 Driver with MotoConnect" drivers.
KalenXI said:
I had that same error, upgrading to the latest Motorola drivers fixed it. I'd post a link but the forums won't let me so just search for "motorola drivers" on google, go to the first link, go to "USB Drivers and PC Charging Drivers" and download the "Motorola 4.6.5 Driver with MotoConnect" drivers.
Click to expand...
Click to collapse
That makes sense. I got my drivers from when I installed Easy Tether. Driver files were on the phone. That's probably why it worked. So, solution to the problem is downloade the latest drivers!
I think a youtube video of this is possible. Would people be interested in that?
darkonion said:
I think a youtube video of this is possible. Would people be interested in that?
Click to expand...
Click to collapse
I think your instructions are comprehensive and clear here, I wouldn't do it unless you've got time to burn. my 02.cents
Thanks! What is everyone's experiences with this tutorial? I want to make sure that it makes sense and is complete. I wrote it from memory after flashing my phone.
20:56:42, September 03, 2010
Line: 587
ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x19EC00 Command: ADDR (Error Code: e0030009),
Detailed Error Details: Direction of the Error=1000, Command Value=200000, Code Group Number=257
File: D:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
its still working afterwards, but lost root, etc. its now running 2.2.20, but I'm wary somethings messed up. should I root, install bootstrapper, and wipe, or just let it go (it still has all my apps and settings)
this is great....thank you sooo much. worked out perfect. just an fyi if you cant get rsd lite to recognize your phone on vista go to the ...motorola/rsdlite/sdl.exe and right click as administrator. wouldnt work before i did that. but everything was so smooth and great instructions, would donate but broke too..lol
kageurufu said:
20:56:42, September 03, 2010
Line: 587
ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x19EC00 Command: ADDR (Error Code: e0030009),
Detailed Error Details: Direction of the Error=1000, Command Value=200000, Code Group Number=257
File: D:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
its still working afterwards, but lost root, etc. its now running 2.2.20, but I'm wary somethings messed up. should I root, install bootstrapper, and wipe, or just let it go (it still has all my apps and settings)
Click to expand...
Click to collapse
I'd just let it go. Reroot and move on with your life! If something did go wrong, reflash again.
JonandRoid said:
this is great....thank you sooo much. worked out perfect. just an fyi if you cant get rsd lite to recognize your phone on vista go to the ...motorola/rsdlite/sdl.exe and right click as administrator. wouldnt work before i did that. but everything was so smooth and great instructions, would donate but broke too..lol
Click to expand...
Click to collapse
Glad to hear it works. I'll add the note onto the tutorial.
Ughh this is frustrating.. When i get to the part where i have to select the Droid2....SBF file, the start button isn't highlighted so i cant press it. but when i choose the other SBF file, it's highlighted
knoxx said:
Ughh this is frustrating.. When i get to the part where i have to select the Droid2....SBF file, the start button isn't highlighted so i cant press it. but when i choose the other SBF file, it's highlighted
Click to expand...
Click to collapse
Do you have updated drivers? Don't quote me on this, but maybe flash one file and then flash the other?
That's what I did, I flashed the other file (successfully) and rooted. Didn't bother factory resetting or anything.
Sent from my DROID2 using XDA App
And today I was having problems, so I used the bootstrap recovery to wipe cache and data, and then sbf'd from the bootloader
Sent from my DROID2 using XDA App
How exactly do you download the device drivers? Ive tried a million times and the link given on the motorola website just keeps giving me zipped up documents. Really starting to piss me off.
joeld82 said:
How exactly do you download the device drivers? Ive tried a million times and the link given on the motorola website just keeps giving me zipped up documents. Really starting to piss me off.
Click to expand...
Click to collapse
You are moving in the right direction. Inside the zipped file, there is the install file, .msi, I believe, that you double click to install your drivers and MotoConnect.
I have an unlocked Orange E650 (able to use now in Australia). It still has the stock rom on. I have tried to update it and I cant get the SDA Application unlock to work. If I were to do a factory reset or a windows update via the phone, would this revert it to being locked again?
Thanks ....
Depending on how you got the device "unlocked" the options for you may be more or less easy. Please read the post I made for another device there but reply in here for more.
It may be that the SIM unlock (I suspect this - as the Orange devices are usually SIM locked) was done in a very generic way that already has opened some doors for easier upgrade.
Can you tell how the SIM unlock was done? Was it a procedure (like offered at http://www.imei-check.co.uk/e650_unlock.php) or did you just supply your IMEI and got back a code?
In case of the imei-check procedure you already have received a SuperCID and upgrade are very easy once have the old OS application unlocked.
I'm not sure how it was done. I had it done about 3 years ago. At the time I could not work out how to do it myself so I ended up sending the phones to a place to unlock them. I don't know what method they used but I do remember them not finding it that easy to unlock them.
Is there a way I can look on the phone to see how it was done?
It is easy - just try to load the cooked ROMs right away - skip the unlock, and jumpSPL stuff. If this works you have received a superCID with SIM unlock.
If this fails you have to go the longer way of
- application unlock old OS
- load Soft SPL or JumpSPL
- load new OS
Sound easier than it is if you have no experience. All steps are described in the relevant ROM threads.
I've tried a few ROMs and not working straight from ROM. It gets to 3% or so and resets the phone and the application says there is a corrupt file.
When I use "SDA_ApplicationUnlock" I get a message "Phone is not unlockable".
Any ideas? Is it safe to do a factory reset or could I lose the unlocked status?
col320ce said:
I've tried a few ROMs and not working straight from ROM. It gets to 3% or so and resets the phone and the application says there is a corrupt file.
Click to expand...
Click to collapse
This is normal if the CID (Carrier ID) Check fails - you would be able to upload only Orange ROMs.
col320ce said:
When I use "SDA_ApplicationUnlock" I get a message "Phone is not unlockable".
Click to expand...
Click to collapse
This means that the remote access (via PC) to alter data on the device is not allowed per relevant security policy (the RAPI policy). You need to change that from the device itself using a tool that has signed privileges to do this. The only tool which can do it is a signed registry editor. Luckily some guys have wrapped the editor into a macro script which can even be installed via an installation procedure from the PC. I had prepared a tool-kit for my Hurricane Kitchen that includes some more steps that do not work on the Vox. You can however take the tools in the "Prepare Security..." folder also on the Vox. You find the package here. As you have already SDA Unlock, install (run the .exe on the PC) and execute HTC Unlock on the device (from Start -> Accessories). This will alter the RAPI Policy that you can execute SDA Unlock later.
col320ce said:
Any ideas? Is it safe to do a factory reset or could I lose the unlocked status?
Click to expand...
Click to collapse
Hard Rest will put the OS in the default state, so if you had HTC Unlock and SDA Unlock remove the application unlock (have you read my other post I recommended to read?), the SIM Unlock will not change - this is permanent. You would have to repeat the application unlock however as the default OS setting is that application execution is "locked" to signed applications.
I'm using 'HTCUnlock-CVS' and get the reply "error launching \regedit.exe"
Have I done something wrong?
It seems that the Orange guys have taken special care to make your life hard here. Reason for the observed behavior:
Usually the HTC certificates are installed on the HTC devices and any HTC signed application should so run on the device. As you see it does not - it seems that their devices have excluded the HTC default certificates :-(
But we should find a way to get that cracked open...
Microsoft has a security configuration manager tool: http://www.microsoft.com/download/en/details.aspx?id=998 which can handle security policies via the RAPI interface. It may be that it will not work for the same reason as SDA Unlock, but is worth a try. Install that on the PC and execute there when the device is on and connected via AS. When you see that the tool has recognized the connected device and received the security Config, then select Menu->Device->Add Development Certificates. Then select on the left side "Security Off" configuration and then push the "Provision" button. Hope that works.
There is still one more option (Gold Card) - but this is a little more complicated. Two ways to flash then, not sure if both work, but flashing via micro-SD will for sure.
You probably won't be surprised to learn that the Microsoft Security Manager didn't work but was worth a try. It says something like there is a 2 tier thing present.
I have seen reports on Modaco.com that claim to have done it this way: http://windows.modaco.com/topic/260617-how-can-i-application-unlock-orange-spv-e650/
A few questions:
Has the tool connected to the device, so did the right side identify the security setting of it?
When selecting the "Securuty off" and then "Provision", what happened?
Did you try to install the Development certificates?
---------- Post added at 01:04 PM ---------- Previous post was at 12:30 PM ----------
Also check out this post at MoDaCo: http://windows.modaco.com/topic/255845-spv-e650-de-brand-fix-pack-05/
It claims to fix the security issue as well.
Security Config Manager shows the same message when I either click 'Provision' or try to add development certificate. (see picture)
I followed the following instructions (similar to one of the links you sent):
Reset phone to factory defaults:
Resetting your phone to factory defaults will DELETE ALL contacts information, calendar etc etc. Make sure you have made a backup of this data before proceeding.
1. Make sure your phone is turned OFF.
2. Press and hold soft1 and soft2 keys. (The menu keys above the 1 and 3 keys)
3. Press and hold the power button for around 1 to 1.5 seconds. Then release the power button. But keep holding the soft1 and soft2 keys.
4. The phone boots and asks to press the Send key to restore to factory defaults. Keep the soft1 and soft2 keys pressed and press the Send key (the key with the green phone icon).
The phone will now reboot and will be now reset to factory defaults. This can take a while, be patient. Wait until the phone has fully restarted before proceeding with the next steps.
Unbranding and unlocking the phone
Now it is time to unlock the phone so it will run unsigned applications (which is needed for the actual firmware flashing)
1. Connect the e650 to your pc via active sync
2. Download MoDaCo_SPV_E650_de_Brand___Fix_Pack.PREP.CAB
3. Download MoDaCo_SPV_E650_de_Brand___Fix_Pack_0.5.CAB
4. Download RemoveSecurity.CAB
5. Copy all three CAB files to your phone.
6. Start explorer on your phone and run and install the MoDaCo_SPV_E650_de_Brand___Fix_Pack.PREP.CAB file
7. Next run and install the MoDaCo_SPV_E650_de_Brand___Fix_Pack_0.5.CAB file.
8. Reboot your phone
9. Once your phone is rebooted run and install RemoveSecurity.CAB
10. Reboot your phone.
11. Download SDA_ApplicationUnlock.zip
12. Run the SDA_ApplicationUnlock.exe inside the zip file. You should get a message that your phone has been unlocked.
13. Reboot your phone
Part 7 takes a long time and I'm not sure if it worked correctly. When I get to Application Unlock (12), I still get the same message that the phone can't be unlocked.
On the other link you sent I could not open http://spvunlock.rd.francetelecom.com/
Interestingly I did have another Orange phone (same s710) that I think was actually slightly newer, and I remember being able to use the application unlock application on it and updade the ROM. That phone however is now dead.
Sigh...
ok, let us then try the Gold Card Method, you need:
a micro sd card, any size (small is welcome), no SDHC (so not >= 4GB). It should be fresh formatted with FAT32
download revskills from http://psas.revskills.de/?q=node/6 and install on pc
run it on pc
connect device via AS, insert formatted SD card
in revskills go to menu -> calculators... -> Gold Card
Select Device Key: Vox
Push "Get CID from WinCE..."
Wait for Serial to change (device will prompt to allow itsutils to run) <- this may be a problem!
Push "Write Goldcard....to WinceSD"
done
Leave the card in the device and start your intended update with any Stock ROM other than Orange, e.g. S710 from HTC. The Gold Card will grant SuperCID during SPL phase but still needs a valid signed ROM, hence cooked ROMs will not work here.
If step 8.) does not work, you can use also use any other device for that as well.
Good Luck!
P.S.: what happened to your other device?!
I'll try it later today.
The other phone fell on the floor and no longer works (can't get any life out of it). I have it still for spare parts.
Part 8 didn't work ...
Why did you not drop THIS one?!
To make a Gold Card you need a WinMo device that can execute the itsutils and have the sd card inserted. It can be ANY WinMo device and it can be any version of OS (WM5 and up for sure, not sure about WM2k3 but also this should work).
Maybe you should try some Orange ROMs and see if there are some where the Modaco procedure works ok. I have one "ORANGE_1.35.61.1_4.1.13.60_03.18.90_Ship_phones_software.exe" which I could upload if this is not the one you have already.
---------- Post added at 11:51 AM ---------- Previous post was at 11:43 AM ----------
The Orange one comes from here:
http://www2.orange.co.uk/servlet/Sa...=Phone&pagename=Business&t=SMEDeviceDownloads
I dont have another WinMo device to use ...
I flashed the latest Orange ROM (which is what was already on the phone anyway) and no change.
If I can I flash an old ROM onto the phone will it potentially change the Orange security problems and allow Application Unlock etc to work? I've had a quick search and have not come up with an older ROM but I will search again if you think it might work.
This is a locked situation here. Orange Security settings on the old OS is preventing steps to open the door for updates. I doubt that older OS would be easier to handle - and I don't know of any that could straight away be flashed.
Just the sketch the routes you could go (and have went already some), there are 3 ways to get another OS loaded via the SPL:
Get a SuperCID to the device - this will allow any SW update via the original SPL. Not sure if this can be done on the Vox and how. I had one of my Tornado treated by imei-check.uk and they have done the SuperCID with the SIM Unlock. Ask them if this would happen with the E650 as well - costs you 10 GBP. Just like SIM-unlock, the SuperCID is permanent and survives any ROM update.
Get the Gold Card key activated while flashing - you need an application unlocked WinMo device though. Just for a short time, lend it from anyone who has one (really no matter if smartphone, with touchscreen or buy the cheapest on ebay - however you may have more luck with 1.). Let us see how dead is your dropped device:
when connecting the charger or PC connected USB, is the charge LED getting on?
when switching on (with charged battery) is the LED getting on?
Is the LCD white or not lighted at all?
open/close the SIM slot (there is a little switch inside) and retry.
Are there physical damages like cracked housing, ripped cables, detached USB socket or broken LCD?
It is hard to believe that you cannot get any life out of the main PBA just having dropped the device. You may well get it to a state where it could be used to write the Goldcard. You will need to dis-assemble it however if cables would need re-attachment.
Get the old OS application unlocked and load the new OS via patched temporary SPL (jumpSPL). Why not asking Orange for a solution to that problem? Tell them that you cannot load unsigned applications and that you want that restriction removed. They should be able to provide you with a signed cab-file that will do the needed changes - to get you going for the rest of the path.
Broken Phone:
Red light comes on for a few seconds when first plugged in then goes out.
Can't turn it on (nothing happens).
No major physical damage.
I have pulled it apart and checked the cable attachements etc.
Just send an email to Orange.
Surely you have you swapped batteries already, did you?
Yes, changed the battery. I can also confirm that it is unable to charge the battery.
Script removed/Effort "canceled" (see release notes)!
Dear fellow XDA'ers, i have written a quick and simple script to tie in all of the great work done by jcase and beaups that helps you root your Moto X. This script simply follows the instructions written by jcase and beaups and automates those scripts with a simple menu.
This script should technically work for "any" Moto X on "any" carrier, provided the methods contained within have the same success rate across all carriers. I do not have the capacity, nor experience, to trap for all situations.
This script ASSUMES that you already have the Motorola drivers installed and your device has successfully connected to your computer via USB Debugging Mode. If you need the drivers, they can be found here.
Instructions:
Download and extract this script on to your Windows Desktop.
Download ALL of the following to the same folder as the GO!.CMD ("640k's Moto X Root Script" Folder). These files should NOT be unzipped:
your specific 4.2.2 factory image.and/or 4.4 factory images (if you are on 4.4, you will need BOTH images).
jcase's RockMyMoto (4.2.2) and SlapMyMoto (4.4).
beaups' MotoWpNoMo.
Saurik's Cydia Impactor
Execute Go!.CMD and follow the on-screen prompts.
Links:
Moto X Firmware Page
jcase's RockMyMoto Thread
jcase's SlapMyMoto Thread
beaups' MotoWpNoMo Thread
Saurik's Cydia Impactor Page
Disclaimers:
I make no warranties of any kind regarding the accuracy or efficiency of this script or the processes contained within. This script was tested on a single device and was written based off of the instructions provided within these forums. You can perform these steps yourself!
jcase will NOT support the use of this script. Should you run in to issues with any of the functionality/procedures written specifically by jcase, you will not be supported by jcase unless you are following his methods.
beaups will NOT support the use of this script. Should you run in to issues with any of the functionality/procedures written specifically by beaups, you will not be supported by beaups unless you are following his methods.
Because I have compiled other's hard work into a command-line script, i have decided to distribute my script uncompiled. That way, in the event of major changes, significant errors, etc., that I don't have time to address, the user community can lend a hand. If you find my work useful, please Thank Me.
WARNING
Make sure your device is fully charged before beginning!
Some people have reported an inability to flash their device, have received "unknown errors", weird partition errors and general chaos during the flashing/imaging process. If this happens to you, try a different USB port. I have read threads/seen reports where sometimes USB 3.0 ports cause failures during this process. Change to a USB 2.0 port and try again.
[*]In general, it is difficult to completely brick your device using this method. As long as you can get to the fastboot menu, your device is recoverable. If your phone will not power on, you did not follow one of the two warnings above.
TIPS:
If "Waiting for device" seems to be taking a really long time (your device is ready, but the script hasn't picked it up yet), try either turning off USB Debugging and then back on, or try removing the USB cable and re-inserting it.
If you are on 4.4, looking for root, your device will be re-imaged two times with 4.2.2. Don't input your details until the 2nd time, to avoid having to repeat your effort.
Connect to your WiFi before enabling USB Debugging Mode to avoid IP Address errors. The batch script tends to get funny on some of the retries. I've tried working out most of the bugs.
I'm confident I haven't worked out 100% of the bugs in this script, although I've tried very hard. I've only tested it with one device, the XT1060. If you have issues, please do not PM me, post them here in the thread.
If for some reason the script abnormally ends or you close out of it, without running the cleanup process at the end, ADB will remain present and cause an error in the script, which will cause the script to fail. Browse to the folder with the CMD prompt and type "ADB kill-server" (kill-server is case-sensitive). This will get the script running again.
Thanks jcase, beaups, saurik and anyone else who has contributed to this effort!
Changelog:
1/9/2014: Initial Release. Only tested on one device. Better bug management within each step, more options at advanced menu, including ADB Debug Window. Removed auto-upgrade to 4.4. I suspect this is where my woes were.
1/9/2014: Removed ADMINISTRATOR requirement. I don't think this will do any harm, but it was creating conflicts with Windows 8.
1/9/2014: Changed TELNET conditions to trap for user interaction.
1/14/2014: Adjusted initial TELNET session.
1/14/2014: Corrected a type on line 366 (would have given an error).
1/15/2014: Re-worked TELNET routine again.
1/16/2014: Simplified menu options, included automated checking for write protection. This check will skip steps once WP has already been turned off.
1/16/2014: Included additional instruction, including more messaging and better message waiting.
1/16/2014: Added additional messaging for troubleshooting purposes.
1/16/2014: Corrected a bug related to BATCH language that was ending the TELNET steps.
1/17/2014: Made another adjustment to TELNET handling.
1/17/2014: Added additional error checking.
1/17/2014: Added some wait time on the second TELNET phase.
2/28/2014: Canceled script effort (ran out of time). With 4.4.2 released, none of the current root methods are valid or work.
BEFORE YOU START WITH ANY METHOD THAT REQUIRES YOU TO WIPE YOUR DEVICE, MAKE SURE YOUR DEVICE IS 100% FULLY CHARGED!! IF YOUR DEVICE SHUTS DOWN WHILE THE SYSTEM IS FLASHING YOU WILL BRICK YOUR DEVICE!!!
heck yes!!!!!!!!!!!!!!!!!!!
Hold the phone. The script at the very last step isn't working. Can't fix right now. My personal device doesn't have root, so it failed. Will need to troubleshoot.
Appreciate the effort put into this for the community
Sent from my XT1060 using xda app-developers app
ok so the script seems to be doing what it's designed to do, which is good. but i've borked my device testing it, which is bad. but i was able to trap for more conditions and provide a better menu system, which is good.
as soon as i can figure out if i can un-bork my device, i'll post the script back up.
My device has root. Script is back online.
I really appreciate your hard work. I've had trouble getting this to work by myself. I'd love to give this a shot later today. I had a few questions though.
You said to "install the script" after it is downloaded but what exactly needs to be installed? Also you said to put all the files in the install folder, but I'm not seeing an install folder in the extracted .rar.
I want to make sure the script runs smoothly so it would be best if I could see exactly how your files are set up. Would you perhaps be able to upload a screenshot?
Thanks!
flipfreak said:
I really appreciate your hard work. I've had trouble getting this to work by myself. I'd love to give this a shot later today. I had a few questions though.
You said to "install the script" after it is downloaded but what exactly needs to be installed? Also you said to put all the files in the install folder, but I'm not seeing an install folder in the extracted .rar.
I want to make sure the script runs smoothly so it would be best if I could see exactly how your files are set up. Would you perhaps be able to upload a screenshot?
Thanks!
Click to expand...
Click to collapse
so my original intention was to distribute this as a self-extracting EXE but because i wanted to share my work and XDA's attachment policy, i changed it to a rar.
just unzip it (anywhere). you'll get a "640k's Moto X Root Script" folder. make sure your .zips from the links above are in the same folder as the Go!.CMD and you'll be good to go.
640k said:
so my original intention was to distribute this as a self-extracting EXE but because i wanted to share my work and XDA's attachment policy, i changed it to a rar.
just unzip it (anywhere). you're get a "640k's Moto X Root Script" folder. make sure your .zips from the links above are in the same folder as the Go!.CMD and you'll be good to go.
Click to expand...
Click to collapse
Thank you! That clears things up. I'll give this a try later and let you know how it went
flipfreak said:
Thank you! That clears things up. I'll give this a try later and let you know how it went
Click to expand...
Click to collapse
based on my testing, unless something goes completely wrong, it should be pretty hard to completely bork your phone. if you get into a bootloop, the advanced menu can help you restore your system files as long as you can get in to the bootloader (usually you can).
640k said:
based on my testing, unless something goes completely wrong, it should be pretty hard to completely bork your phone. if you get into a bootloop, the advanced menu can help you restore your system files as long as you can get in to the bootloader (usually you can).
Click to expand...
Click to collapse
Hmm, well I tried it but it keeps telling me that 7za.exe is not in the folder, even though it is sitting right above Go!.CMD. Any idea why it would say this? I ran it as an administrator
flipfreak said:
Hmm, well I tried it but it keeps telling me that 7za.exe is not in the folder, even though it is sitting right above Go!.CMD. Any idea why it would say this? I ran it as an administrator
Click to expand...
Click to collapse
can you screen shot the window and your folder where the files are?
thanks.
640k said:
can you screen shot the window and your folder where the files are?
thanks.
Click to expand...
Click to collapse
Sure
flipfreak said:
Sure
Click to expand...
Click to collapse
did you extract the contents to your desktop? i'm guessing it's failing because you're technically not running the cmd file in the same folder. for example, windows will allow you to run files directly from a .zip, but it caches that file in to a temp folder somewhere. if you haven't unzipped the files, the script won't see any of the files.
i'm here to help, i want this to be successful.
640k said:
did you extract the contents to your desktop? i'm guessing it's failing because you're technically not running the cmd file in the same folder. for example, windows will allow you to run files directly from a .zip, but it caches that file in to a temp folder somewhere. if you haven't unzipped the files, the script won't see any of the files.
i'm here to help, i want this to be successful.
Click to expand...
Click to collapse
Yeah, the files are all extracted to my desktop. If I run it as an administrator, it gives me the error telling me that that 7za.exe is not in the folder. If I don't run it as an administrator, it tells me that it will abort and to press any key to continue. When I press any key, it brings me to the menu where it asks me what I want to do.
I'm not sure what I could be doing wrong. Maybe we should just wait and see if anyone else has this problem. It could be on my end.
flipfreak said:
Yeah, the files are all extracted to my desktop. If I run it as an administrator, it gives me the error telling me that that 7za.exe is not in the folder. If I don't run it as an administrator, it tells me that it will abort and to press any key to continue. When I press any key, it brings me to the menu where it asks me what I want to do.
I'm not sure what I could be doing wrong. Maybe we should just wait and see if anyone else has this problem. It could be on my end.
Click to expand...
Click to collapse
ok i'm seeing the same issue. it's isolated to Windows 8. troubleshooting now.
Windows 8 is running the CMD prompt from /WINDOWS/SYSTEM32... which is the exact problem i detailed earlier. i'm going to remove the admin requirement. i don't think it's necessary.
flipfreak said:
Yeah, the files are all extracted to my desktop. If I run it as an administrator, it gives me the error telling me that that 7za.exe is not in the folder. If I don't run it as an administrator, it tells me that it will abort and to press any key to continue. When I press any key, it brings me to the menu where it asks me what I want to do.
I'm not sure what I could be doing wrong. Maybe we should just wait and see if anyone else has this problem. It could be on my end.
Click to expand...
Click to collapse
download the new file and try it again.
640k said:
download the new file and try it again.
Click to expand...
Click to collapse
That got it working. I'm now stuck at attempting a telnet session. Should I restart? Here's a screenshot
flipfreak said:
That got it working. I'm now stuck at attempting a telnet session. Should I restart? Here's a screenshot
Click to expand...
Click to collapse
i was afraid of that. open the TELNET.ERR file with notepad and show me the contents. jcase stuck some user interaction in there that only occurs one time, so i was never able to trap it again.
thanks for your help.
640k said:
i was afraid of that. open the TELNET.ERR file with notepad and show me the contents. jcase stuck some user interaction in there that only occurs one time, so i was never able to trap it again.
thanks for your help.
Click to expand...
Click to collapse
No problem.
ÿýÿý ÿûÿû
~ $ [6ndalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
RockMyMoto 1.0
by Justin Case
PayPal Donations maybe sent to: [email protected]
Special thanks to saurik, you rock!
System is write protected...
Executing step 1...
To use RockMyMoto you most solve a
simple equation. This helps ensure
you are paying attention, and also
amuses JesusFreke and myself.
Solve for a:
a/24=70
Please type a whole number as your answer:
Click to expand...
Click to collapse