Related
Hey there everyone, I am pretty new to this forum so I must apologize for throwing you all into the deep end. I recently purchased an o2 XDA mini S second hand from a guy on boards.ie here in Ireland. I got the phone and really liked it because it allowed me to get rid of my Dell Axim X3i and mp3 player and keep it all in one device.
After a little bit of more research I discovered that I could remove some of the bloatware from the o2 xda mini S by just hard resetting and choosing the basic option which I than did. Still not satisfied with the overall performance of the XDA I decided to try a rom upgrade. Not wanting to do a totall overhaul I decided to just do a radio upgrade first.
My device is sim unlocked, it was like that when I bought it. I used the latest wizard service tool to CID unlock the device before I even flashed the phone. I also used the wizard service tool to change the nk.nbf file within the o2 mini S radio update into 96000000-GSM.nb. I then used this file to write to the GSM radio code (Bdk 1) according to the wizard service tool in the hopes that it would upgrade my radio version.
Well when I restarted, nothing of the sort happened, on the boot screen I noticed I was now missing my GSM version and when the phone finally got into windows mobile, it did not pick up any signal even though beforehand it could. The phone also became super slow to the point where it was unusable.
I have gone into bootloader mode subsequently after reading on this forum and tried to reflash with a number of updates with active sync disabled and nothing else running with the phone connected via usb to the pc. None of the updates would even pick up the phone or allow me to flash it.
My phone is pretty much screwed, I have a spare so it is not that big of an issue but I would like to make this usable again if at all possible. So my question is how do I flash a rom while the phone is in bootloader mode?
P.S I forgot to include the Current boot screen details:
IPL - 1.05
SPL - 1.05
OS - 1.5.4.2
Hi,
You can use the Wizard Love Rom from here http://rapidshare.com/files/17792050/Wizard_Love_2.26.10.2_WWE_Novii_CF2.rar
Hey there, thanks for the advice, I did download that ROM but like I said before, none of the roms manage to flash my XDA because they all cannot seem to connect to it. Activesync does not even pick it up in windows mode, and even when I have it connected in bootloader mode via usb and I double click on the love rom, it goes through the motions but never managed to "verify the information with the pda"
Try a stock Tmobile ROM but not from bootloader. Also, I would check the activesync app on the device. Make sure it's set to use USB as the default connection method.
A few other steps to try...
Uninstall ActiveSync and install an older version. If still no go, try a newer version.
Try a different USB cable and/or USB port.
Try a different computer with XP, not Vista.
Try flashing it without the SIM card or any memory cards.
If all else fails, you can try the SD card flashing method. There are instructions in the Wiki on how to do it, but always a stock ROM.
Try this one... http://forum.xda-developers.com/showthread.php?t=311027
Updated IPL/SPL and radio 2.69
Hey Devis, I think I have come one step closer, I tried all the suggestions that you made. Except well now my phone will not even go into the operating system when I switch it on. It will boot and the version numbers show but then it just resets itself.
I tried a different usb cable and I am not using vista, tried a different pc and the same result. The one place I did have some marginal success was the sd card method.
Basically what happened is that It backed up the OS from my phone and then reloaded it, not exactly what I wanted since the OS and rom are both screwed on the phone so my question at this point is, is there anyway using the SD card method to load one of the stock roms onto my phone?
I searched around the net and found the opposite to the "r2sd all" function, would be the "s2d" function, would that allow me to flash the phone with a stock rom?
Thanks for your time, I am going to call it a night here in ireland and head to bed.
Ok, if the phone resets then you probbably have a dead/dying battery. Charge it for about an hour or so using the wall charger, not the USB cable. Try to restart it and see if you can get in the OS. I was looking in the SD card method thread and some guy was successful at restoring the image from the SD even though his OS had died. He then had a fully functional phone.
The other thing to do would be to get the image file from someone that has a living and breathing wizard, preferably one with a stock ROM. Since this method is the equivalent of making an image of a PC using Ghost, the restoration of such an image to your Wizard should work just fine.
Just make sure that the other Wizard is SIM and CID unlocked. Or just go buy a Wizard from the store, unlock SIM and CID, copy the image on the SD and flash your device. Or... since u've got a new Wizard in your hands, just take the freaking thing appart and swap the guts return the store bought wizard to the store saying that the thing just doesnt freaking work!
As for the AT commands... it is possible that s2d would workfor you, it doesn't work in my wizard. from what i have been reading it appears that the bootloader is password protected and that password is randomly generated. I haven't played long enough with it to figure out how to get the password.
It looks like you've got some "trial and error" processes ahead of you. There is a wealth of info on bootloader AT commands on Wiki, nothing for the Wizard though. But something may work... not sure.
I could try to get you a ROM dump from my Wizard but I already am on SPL/IPL 3.08 and running WM6. the SPL/IPL version alone wouldn't allow you to restore from my backup.
Hey Devis, thanks for your time, just woke up here, will work some more on the phone today and let you know what is going on
Hey Devis, I did not even get a chance to fiddle around with the phone today, from being able to switch on less than 24 hours ago, it does not even want to switch on now so I am going to officially declared it a brick and move on. Will see if anyone can fix it for me, spent way too much time already when I should be working on my dissertation, thanks alot anyway
Sorry to hear that...
I have bricked one phone myself in the past... my old Pana GD87 and I absolutely loved that phone. I know how you feel.
Good luck with your dissertation.
I was attempting to flash my ROM to wm6 crossbow, I used Lokiwiz 02b to CID unlock my G3 wizard. Then, I attemped to flash the rom using the RUU. The Shelltool .exe never finished flashing the rom (even after 1.5 hours), so I disconnected the USB and tried to re-sync Windows Mobile Device Center (using Vista 32) as per the directions, but it would not detect the phone. I then entered bootloader mode and tried to run the RUU that way, but vista crashed the program if no sync connection is found. So, I downloaded the latest t-mobile ROM, and flashed the phone through bootloader (curiously the flash seemed to work using t-mo's RUU) and it installed to 100%. However, the phone will not get past the white splash screen. This is what it displays:
IPL 2.26
SPL 2.26
GSM 02.25.11
OS 2.26.10.2
I tried to un-rar the tmobile exe to a new folder and replaced the nk.nbf file with the file from the crossbow ROM. The t-mo RUU wouldnt read it properly and it crashed. Now the phone is sitting on my counter with it's battery pulled out for fear it mat discharge completely. Since i can get into bootloader mode with the "USB" display at the bottom, I know the device isn't bricked, but what can I do to get it up and running and hopefully flashed to wm6 crossbow? Thanks for any help!
snootch said:
I was attempting to flash my ROM to wm6 crossbow, I used Lokiwiz 02b to CID unlock my G3 wizard. Then, I attemped to flash the rom using the RUU. The Shelltool .exe never finished flashing the rom (even after 1.5 hours), so I disconnected the USB and tried to re-sync Windows Mobile Device Center (using Vista 32) as per the directions, but it would not detect the phone. I then entered bootloader mode and tried to run the RUU that way, but vista crashed the program if no sync connection is found. So, I downloaded the latest t-mobile ROM, and flashed the phone through bootloader (curiously the flash seemed to work using t-mo's RUU) and it installed to 100%. However, the phone will not get past the white splash screen. This is what it displays:
IPL 2.26
SPL 2.26
GSM 02.25.11
OS 2.26.10.2
I tried to un-rar the tmobile exe to a new folder and replaced the nk.nbf file with the file from the crossbow ROM. The t-mo RUU wouldnt read it properly and it crashed. Now the phone is sitting on my counter with it's battery pulled out for fear it mat discharge completely. Since i can get into bootloader mode with the "USB" display at the bottom, I know the device isn't bricked, but what can I do to get it up and running and hopefully flashed to wm6 crossbow? Thanks for any help!
Click to expand...
Click to collapse
Well Friend I hate to say it but Using Vista is your problem... The drivers in WMDC are different from those of activesync and thus Vista cannot talk to your phone in bootloader.
Follow this thread here:
Updated!!(10/20/2007) UPGRADE YOUR PHONE WITH WINDOWS VISTA!!! PROVEN METHOD!
Once you complete the steps in that thread, flash the Official T-Mobile Rom. I will be online for the rest of the night so I will walk you through everything if you would like me to. My AIM, Yahoo, and MSN messenger addresses are all at the top of every one of my posts.
First off, let me thank you for your help, as well as the time you have put in the community helping people like me. I had updated the driver before, but I guess several attempted flashed had overwritten the driver. Just now, I followed the link you gave me, updated the drivers, and flashed the T-mobile 2.26 ROM. The problem still remains. The RUU goes to 100%, shows me the finish/exit screen, mu wizard restarts, but hangs at the white boot screen and does not go any further.
Anyone? Need to get this phone up quick, as I am starting a new job soon and need the capabilities. BTW, i'm going to put XP on this laptop in dual-boot and see if I can get the t-mobile ROM to load fully using XP.
snootch said:
Anyone? Need to get this phone up quick, as I am starting a new job soon and need the capabilities. BTW, i'm going to put XP on this laptop in dual-boot and see if I can get the t-mobile ROM to load fully using XP.
Click to expand...
Click to collapse
If you can manage that, you will be set. All you have to do is create a hard drive partition and install xp to that partition.(from what I know anyway)
OK, i'm gonna try that (my internet is dropping every 5-10 secs, so it'll take a little time) I do have one question though- Last time I used Loki's unlocker, I unlocked the SIM, then the CID unlocker. After the CID unlocker, it locked me out of the phone. The OS wouldnt load unless I provided an unlock code. Then i reflashed it, then the problems started. I think i didn't have it CID unlocked properly. Plus having my miniSD in the slot probably didnt help things either. I've read the directions several times, and I dont see what i'm doing wrong. Could you maybe shed some light on what i'm doing wrong? Thanks!
EDIT: Also, I forgot to mention that I tried to do a hard-reset (hold wireless manager + voive command buttons + soft reset) and when you press the send button, it tells me unable to format FAT volume or something like that. Upon reading around, it seems like i'm having the exact same problem as this poster: http://forum.xda-developers.com/showthread.php?t=338315
snootch said:
OK, i'm gonna try that (my internet is dropping every 5-10 secs, so it'll take a little time) I do have one question though- Last time I used Loki's unlocker, I unlocked the SIM, then the CID unlocker. After the CID unlocker, it locked me out of the phone. The OS wouldnt load unless I provided an unlock code. Then i reflashed it, then the problems started. I think i didn't have it CID unlocked properly. Plus having my miniSD in the slot probably didnt help things either. I've read the directions several times, and I dont see what i'm doing wrong. Could you maybe shed some light on what i'm doing wrong? Thanks!
EDIT: Also, I forgot to mention that I tried to do a hard-reset (hold wireless manager + voive command buttons + soft reset) and when you press the send button, it tells me unable to format FAT volume or something like that. Upon reading around, it seems like i'm having the exact same problem as this poster: http://forum.xda-developers.com/showthread.php?t=338315
Click to expand...
Click to collapse
Although,many have successfully flashed using vista,but I'll suggest in your condition flash through WinXP. Download the official carrier's Rom from it's website.
1. Disconnect your phone from the usb cable,shut down any firewall,disable any Anti virus,Reboot your PC.
2. On your Desktop PC, open Microsoft ActiveSync, then go to File >Connection Settings >Remove the Selection from “Allow USB Connection with this desktop computer”
3. On your PC Open windows Task Manager...>Tab Processes...>wescomm.exe...>End process
4. Power off the phone completely (Not stand-by,shut off completely),or you may take the battery out for few seconds
5. Make sure your phone is not Connected to the PC via USB cable and remove the dummy Sdcard or mini-Sd card
6. Get your phone into Bootloader mode (Multicolor screen) by pressing camera button + Power on button
7. Reconnect your phone to the Desktop PC using the USB Cradle and the Charger MUST be Connected to the Cradle (Be sure that your battery is charged over 70%)
8. "USB"will appear on the bottom of the screen of the Bootloader (Multicolor screen)
9. Run the Upgrade again and it will work fine without any problems.
10.Never use Bluetooth sync for the Upgrade
While upgrading, the ActiveSync program will not go on, however the upgrade is running.Please be patient when you're flashing your device, even if 98%. It can wait a little bit, 5 ~ 7 minutes.
Don't cancell the flash or get the phone off the usb cable till it confirms "Congratulations" or stops with an Error!!!
Hope it'll recover back to it's default status,good luck
I'm going to assume I don't have to CID unlock it until I want to switch from the T-mobile 2.26 ROM? I am about to install XP dual-boot shortly. I'll post my results when it's done. Thank you.
snootch said:
I'm going to assume I don't have to CID unlock it until I want to switch from the T-mobile 2.26 ROM? I am about to install XP dual-boot shortly. I'll post my results when it's done. Thank you.
Click to expand...
Click to collapse
As long as you are going to keep T-Mobile 2.26 on your device or are restoring T-Mobile 2.26, you do not have to CID unlock but should you decide to change to another Rom, you will need to CID unlock.
Good luck on the dual boot. There is a detailed tutorial in my Signature if you would like to take a look at it. After I can restore my crashed laptop, I am going to take care of the dual boot also.(I have to do it again... )
I really want to put WM6 on my wizard, and customize it the way I want it. Do you have any favorite WM6 ROM? All day yesterday I spent trying to add a WinXP partition to my Vista laptop. Not fun. First, I shrank the only partition on the drive (where Vista is installed) using Disk management, the Diskpart.exe to create a new 2.5Gb partition to install XP on. I rebooted the labtop with a XP disk, and installed XP on the partition. After the laptop restarted the first time, it did not come back up (black screen, no CD activity), So I changed the boot options in BIOS to HDD, and the Vista partition responded with "Error loading operating system" on a black screen. So now, i've got a laptop with a corrupted Vista install, A partition with partially installed XP on it, a XP disk that just quits working, and my wizard is shot. Normally something I can deal with if I had my desktop, but unfortunately my entire house is packed up in storage, i'm living in a hotel, and the laptop and phone are all i've got. SO, against my better judgement, I went to the store and bought a Vista home basic upgrade DVD to fix my vista partition, and now i'm back on the net- and going to try anothe XP disk. Whew- what a pain in the ass.
snootch said:
I really want to put WM6 on my wizard, and customize it the way I want it. Do you have any favorite WM6 ROM? All day yesterday I spent trying to add a WinXP partition to my Vista laptop. Not fun. First, I shrank the only partition on the drive (where Vista is installed) using Disk management, the Diskpart.exe to create a new 2.5Gb partition to install XP on. I rebooted the labtop with a XP disk, and installed XP on the partition. After the laptop restarted the first time, it did not come back up (black screen, no CD activity), So I changed the boot options in BIOS to HDD, and the Vista partition responded with "Error loading operating system" on a black screen. So now, i've got a laptop with a corrupted Vista install, A partition with partially installed XP on it, a XP disk that just quits working, and my wizard is shot. Normally something I can deal with if I had my desktop, but unfortunately my entire house is packed up in storage, i'm living in a hotel, and the laptop and phone are all i've got. SO, against my better judgement, I went to the store and bought a Vista home basic upgrade DVD to fix my vista partition, and now i'm back on the net- and going to try anothe XP disk. Whew- what a pain in the ass.
Click to expand...
Click to collapse
It's better if you use 'PartitionMagic' software to create partition and install WinXp,as it has much advanced features as compared to built-in Disk Management.It also has the option to create a partition in the same one partition to install new OS.
I tried that first, too bad it doesnt work in Vista.
Woo Hoo!!! Success!!
Alright! I got it fixed! What I did:
1- Spent $42 on a CID unlocker from: http://www.imei-check.co.uk/m3000unlock.php
After i recieved the files from the via email (about 10 minutes) I ran their unlocker program with the file they emailed me. This CID unlocked the wizard.
2- I flashed button's ROM: http://rapidshare.com/files/18212239/CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe.html
I had to flash it twice until it showed a IPL/SPL of 1.01
3- Followed this post: http://forum.xda-developers.com/showthread.php?t=276963&highlight=splash+screen+freezing
(make sure you use a blank SD card, as it will require you to format the card to make it useable again after your'e done)
4- Remove battery, and restart phone, BOOM! Button's ROM works fine!
5- Now upgrade to any ROM you like (WM6 etc.)
snootch said:
Alright! I got it fixed! What I did:
1- Spent $42 on a CID unlocker from: http://www.imei-check.co.uk/m3000unlock.php
After i recieved the files from the via email (about 10 minutes) I ran their unlocker program with the file they emailed me. This CID unlocked the wizard.
2- I flashed button's ROM: http://rapidshare.com/files/18212239/CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe.html
I had to flash it twice until it showed a IPL/SPL of 1.05
3- Followed this post: http://forum.xda-developers.com/showthread.php?t=276963&highlight=splash+screen+freezing
(make sure you use a blank SD card, as it will require you to format the card to make it useable again after your'e done)
4- Remove battery, and restart phone, BOOM! Button's ROM works fine!
5- Now upgrade to any ROM you like (WM6 etc.)
Click to expand...
Click to collapse
Congrats ! that's the easy way.....
Yeah, I got tired of screwing with it, and I did it all in Vista!
PLEASE READ THE *FAQ* BEFORE ASKING QUESTIONS!!
IF YOU HAVE A CDMA DEVICE THEN GO *HERE* FOR INSTRUCTIONS ON HOW TO HARDSPL
IF YOU NEED TO HARD RESET OR ENTER BOOTLOADER YOU CAN FIND INSTRUCTIONS *HERE*
Before starting, backup anything you might want to keep after the new Rom has been flashed as all contacts, emails, texts, notes, Internet BookMarks WILL be lost!!
PimBackup is good and free (copy any mms attachments to your storage card or computer seperately)
*ONCE YOU HAVE FLASHED A HARDSPL ITS PERMANENT. 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
*FLASH HARDSPL BEFORE FLASHING ANY CUSTOM ROMS*
1. YOUR DEVICE MUST HAVE AT LEAST 50% BATTERY POWER FIRST BEFORE ATTEMPTING EACH STAGE
2. FLASH HARDSPL
The Original HardSPL Thread is *HERE*
IMPORTANT: Each user gets 1 license, or perhaps 2-3 on request if needed (valid forever and works as transparently as possible, so it won't be a problem at all)
you can send a request for 1-2 more devices for private user (free) at http://support.htc-unlocks.com (ONLY at this link, not in PM).
NOTE1: This package is for Rhodium (Touch Pro 2, not the original Touch Pro) devices. CDMA-GSM worldphone version is not accepted (RHOD400, RHOD500 modelids), that will have its own HardSPL later. This HardSPL supports WM6.5
NOTE2: If you have Vista or Windows 7, update WMDC to v6.1 *HERE* first
Flashing via ActiveSync with USB Lead (thanks to OliNex)
1. Download HardSPL package from *HERE* and extract to an empty folder
2. Synch Phone with PC in Windows Mobile!!! It has to be connected to activesync or WMDC via USB cable and it must not be in Flight/Airplane mode (i.e. radio should be on)
3. NEW: Internet access is required as the program checks online for updates and license
4. Run Rhodium-HardSPL_V2_00R3.exe on PC, make sure it's launched from a local drive (not through network drive, etc.). XP requires Admin logon and Vista/Windows 7 will automatically prompt to allow it to run in Admin mode, allow it. If you get an AntiVirus warning please ignore it, it contains no harmful code (just used a packer to compress it).
5. Follow steps as prompted in the HardSPL program. If this is the first run of HardSPL on a device after Hard Reset, you must select Automatic Flash Mode (first button in Welcome Screen)
NOTE: You should usually go for Automatic Flash Mode. The Manual Flash option is only to be used as noted below and you must only attempt the Manual Mode option if Automatic Flash Mode or SSPL-Manual.exe already put device in black screen. Any other errors triggered while running in Autoflash Mode will have to be fixed as instructed in the error message.
6. It will ask you to wait while it prepares for the flashing, press OK
7. Now it should go through without any error messages, if one does pop up then follow the instructions included in the error text. If no specific instruction is shown then ask for help in the thread, but this should not ever occur (as this means a really fatal error occurred)
8. At this point the phone hopefully went to a black screen (reporting version as 1.01.C-SSPL only using "info 7" in mtty), this is the SSPL version, which is temporary. Then RUU will instantly launch
9. NOTE: When RUU says it will Hard Reset do not worry, it is not going to do that. Also when it says the flash will take 10 minutes ignore that, it will only take a minute or so
10. SPL flashes, device automatically reboots, job done
*Go into BootLoader Mode (do a Soft Reset while holding the "volume down" key on the left side of the device. Keep holding the "volume down" key until you see tricolour screen which is the bootloader mode, then release it) and verify the screen shows 0.85.OliNex, which is the HardSPL version*
NOTE1: This is unsigned HardSPL. No limitations on flashing ROMs (except of course some Radio roms). Also this has overwrite protection against HTC RUU's overwriting HSPL with a stock one. See steps in the Original thread about how to reflash stock SPL.
NOTE2: Anyone having USB problems with the device after it enters SSPL mode, download SSPL-Manual-Rhodium.exe, copy it to the phone and run it. Once the screen has gone black, run the HardSPL package on the PC and select Manual Flash option.
*IMPORTANT* Make sure that the USB cable is plugged in and device is synched to Windows Mobile even if doing manual method.
NOTE3: Do not use this RUU for anything other than SPL flashing (i.e. hardspl or stock spl restore)!!! Nothing other than SPL's made by Olinex team (using OliNex custom cert, which is not public) will flash to make SSPL more secure. If you want to flash another rom then use shipped RUU or Rhodium customRUU if you want to flash cooked ROM.
3. DOWNLOAD AND FLASH YOUR PREFERED ROM
NOTE: Check the Roms Thread for any specific Flashing instructions. If there arent any then you can use the following guide.
Flashing Via ActiveSync
1. Download your prefered Rom from the Rhodium Rom Develpoment Page and unzip/unrar it to your computer
2. REMOVE SIM and microSD CARDS!!
3. Turn phone back on and wait until it syncs with your PC
4. Run the CustomRUU.exe from the Roms Folder (if one isnt included then download it *HERE*)
5. Follow onscreen instructions to set up your New Rom
6. Once phone has gone through the customisation procedure then replace Sim and microSD Cards
7. 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 Rhodium Rom Develpoment Page and unzip/unrar it to your PC
3. Goto the Roms Folder and rename the .nbh file to RHODIMG.nbh
4. Copy the RHODIMG.nbh file to the root of your MicroSD Card
5. Plug the MicroSD Card into the phone
6. Enter the BootLoader screen, you will first see a tri-color screen with the phone and SPL Information at the top
7. Follow the On Screen instructions to start the update
8. After flash has completed, press the reset button with the stylus to reset the device.
4. FLASH PREFERED RADIO (OPTIONAL)
For more information about compatible Radios go *HERE*
Flashing Via ActiveSync
1. Sync your phone with the PC
2. Run CustomRUU.exe from the Radio's Folder and follow the instructions (if one isnt included then download it *HERE*)
Flashing via MicroSD Card
Use same method as Flashing a Rom via MicroSD Card
5. JOB DONE. Well Done YOU DID IT!!
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
FAQ for Flashing your First Rhodium Rom
FAQ
1. What Operating systems are supported for Flashing HardSPL?
Supported OS versions: 32bit and 64bit XP, Vista, Windows 7RC and later. win2000 was untested, and pre-RC win7 (lower than build 7100) is explicitly not supported. Also the program may be unstable or not work on Virtual systems, so it's recommended to try outside Virtual OS software. Also version verify: if HardSPL package says V120R in first Welcome dialog title (and version 1.20 in About box) it is the latest version, not some crappy beta/old version.
---------------------------
2. Why is it recommended to remove the Sim Card and microSD Card before Flashing?
microSD Card removal is recommended just in case any self booting programs or UC setup files are on there that might interupt or conflict with the setup procedure after flashing.
Sim Card removal is recommended because as soon as your phone reboots after flashing your phone will be live and if you get a call or text message during the initial setup it might interfere and ruin the setup.
If you flashed with both the cards in it should be fine as long as none of the above situations happened. Just be aware for future flashes
---------------------------
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 (radios intended for your device only need Hard SPL) - 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 Hard SPL instead. Hard SPL lets you flash any ROM, Splash or Radio (depending on sec unlock) to your device. The stock SPL's only let you flash signed ROM images that match the CID & Model of your device. N.B. the CID is the carrier ID (e.g. HTC__001, or VODAP100).
Also, SuperCID is setting your CID to a value that allows you to flash other signed (shipped) ROMs, even if the CIDs are different after removing Hard SPL. - SuperCID is performed by the Olipro unlocker.
---------------------------
4. What is the difference between ROM and RADIO?
The Rom is the operating system and included patches, tweaks and programs. The Radio is a seperate part of the firmware on the phone that handles all communation related matters such as signal, gps, bluetooth, camera, wifi and sound. Newer Radios to include improvements or fixes in older version, or even just to compliment an existing Rom or network so a newer Radio isnt neccessarily better. Radios also need to be matched to the correct Rom so you cant just put any Radio and Rom together.
---------------------------
5. How do Stock ROMS differ from Cooked ROMS?
Stock Roms usually have extra 'bloatware' added which take up extra space on the phone. Custom Roms are stripped down to provide more space and most are tweaked to provide a faster more stable Operating System. Every chef is different so you have to look around the forums to see which Rom is best for your needs.
---------------------------
Post #3 for mskip
Post #4 for mskip, just in case
Great post for people thats new
Nice one Mark.
Dave
i have to say, that no matter what color font, special &$^#%@ that you use, someone will NOT follow the directions. This is a VERY in-depth guide!
slimsuse said:
i have to say, that no matter what color font, special &$^#%@ that you use, someone will NOT follow the directions. This is a VERY in-depth guide!
Click to expand...
Click to collapse
Too true....I remember how scared I was when doing my first flash on my Wizard though. Somethin like this at the time would have put my mind at ease (would have probably scared me to death even more at the same time! ).
It's funny how, with experience, that fear fades away and you just flash as if you've been doing it all your life. Some people will learn the hard way...others will read, read, read like I did many years ago! (as they most definitely should)
Nice post mskip.
When flashing a new ROM via Active Sync, is it really necessary to remove the SIM-card and SD-card? I didn't and the flashing did go well. No problems at all!
Just extra precaution against wiping your cards out or God forbid getting incomming phone signal during flash and having that interfere!
slimsuse said:
i have to say, that no matter what color font, special &$^#%@ that you use, someone will NOT follow the directions. This is a VERY in-depth guide!
Click to expand...
Click to collapse
Unfortunately flashing HardSPL on a Rhodium is a very in depth process and no shortcuts can be taken for the safety of the phone.The purpose of this guide is to give someone the whole process from flashing HardSPL to changing the Rom or Radio and save them having to keep 4 or 5 screens open with all the different information.
I remember when I first flashed my OLD Hermes many many years ago (god that makes me sound old haha) I was trying to pull all the information I needed together and ended up with over 15 pages all with different information and different methods on how to do the same thing and it took months off my flashing life.
I only made this up last night and the HardSPL information is taken directly from the creators thread. I will go through the HardSPL section and try to "dumb" it down so its easier to understand but if people want to customise their device then they HAVE to be prepared to follow all the steps to the letter and not complain that its too hard or too in depth.
This is the third one stop flashing guide I have written and the other ones have helped thousands of people flash their phones, the fancy fonts and colours are just their to help point things out
Any improvemants or additions are welcome (although my 10000 character limit has already been reached so if I add something then something else has to be taken off)
no problem to flash an official rom later?
you talk about : "CDMA-GSM worldphone version is not accepted (RHOD400, RHOD500 modelids)"
i'm the owner of the european htc touch pro 2, is it supported or not? thx
admix said:
no problem to flash an official rom later?
you talk about : "CDMA-GSM worldphone version is not accepted (RHOD400, RHOD500 modelids)"
i'm the owner of the european htc touch pro 2, is it supported or not? thx
Click to expand...
Click to collapse
Yes.
Dave
admix said:
no problem to flash an official rom later?
you talk about : "CDMA-GSM worldphone version is not accepted (RHOD400, RHOD500 modelids)"
i'm the owner of the european htc touch pro 2, is it supported or not? thx
Click to expand...
Click to collapse
Once you have HardPSL on your phone then you are free to flash Official or custom Roms as you desire.
Im sure the Touch Pro 2 is supported but if you are unsure in any way then ask in the developers thread.
Ok I've got a question. In the starting post is sais that the HARD-SPL is permanent. Is it really permanent, or can you change the HARD-SPL later on when updates are brought out?
I guess it is permanent in a way that it won't be removed after you reflash you device. But it can be altered right? (Because there are updates brought out for HARD-SPL also
quarintus said:
Ok I've got a question. In the starting post is sais that the HARD-SPL is permanent. Is it really permanent, or can you change the HARD-SPL later on when updates are brought out?
I guess it is permanent in a way that it won't be removed after you reflash you device. But it can be altered right? (Because there are updates brought out for HARD-SPL also
Click to expand...
Click to collapse
It means it cannot be replaced by a stock SPL. There is a flag in the Hard SPL to prevent it from being overwritten. You must use SSPL to change the SPL version - PS the relocker in the Hard SPL thread will revert you to Stock SPL if need be.
Dave
Mark, you forgot SD card Flashing - RHODIMG.ngh
Would you be able to add it when you get chance?
Dave
i flashed my first rom yesterday but didnt remove my sim or SD card
everything seems ok , can it cause problems?
DaveShaw said:
Mark, you forgot SD card Flashing - RHODIMG.ngh
Would you be able to add it when you get chance?
Dave
Click to expand...
Click to collapse
Sorry Master
When I was writing the guide I didnt see anything about microSD Card flashing so I thought it best to leave it out. Plus I knew that you would pick up anything I left out
I will add it to the Rom and Radio flashing steps but I totally maxed out my post already. Any chance you can bung me another 5000 characters I promise I will pay you back next week Failing that I will have to do some drastic rewording or spread the guide over the first 2 posts
combat goofwing said:
i flashed my first rom yesterday but didnt remove my sim or SD card
everything seems ok , can it cause problems?
Click to expand...
Click to collapse
microSD Card removal is recommended just in case any self booting programs or UC setup files are on there that might interupt or conflict with the setup procedure after flashing.
Sim Card removal is recommended because as soon as your phone reboots after flashing your phone will be live and if you get a call or text message during the initial setup it might interfere and ruin the setup.
If you flashed with both the cards in it should be fine as long as none of the above situations happened so I wouldnt worry about it too much. Just be aware for future flashes
After looking through the varying questions concerning the same topic and, subsequently, not seeing the right answers - within the right timeframe (e.g. within the past month or so), I decided that a new thread was needed. So here's it is:
A branded G1 (mine, T-mobile, Germany) is what I want to downgrade so that it may be rooted and upgraded with a custom ROM. The problem, I am finding, is not that the instructions aren't correct. Rather, it's that a piece of the instruction set doesn't exist. Namely, the revskills.de website. I mention this because I have tried, repeatedly, to boot with the DREAIMG.nbh in order to downgrade and have consisitently (after numerous downloads from different sites) received the same error - 00028002 (or something like that) while trying to load it. I eventually learned that some phones needed a "goldcard" so I set about trying to do that. Got the CID, reversed it, etc. but the part about going to psas.revskills.de is the killer. The site is down and apparently, no other method of changing the carrier ID exists (or, if it does, the method is too ugly to mention, let alone comprehensible by someone like me, a not-so-good-programmer). Worse yet, all the instructions involving the generation of a goldcard also involve this website and consequently, because of the aforementioned down-status of the site, renders all instructions moot (Grade: D for relying on unreliable sources). So, back to the question: does a method exist outside of what I have mentioned? Where can I find it? Does it have a cost attached to it?
If you've read this far it means that full words and sentences don't confuse you (in light of so-called "l337sp33k") and I applaud you. I will applaud you even more when a well thought out and not-so-glib answer unriddled with blog cliches and platitudes can be found as a reply to this post...
Seriously, if you don't know an answer, a link to check out or someone I can refer to, don't waste your time (or mine) with a the standard "you need to read this and that rules before asking a question" reply. I have trolled through this forum and a few others for the past 2 days looking for the answers to the question of downgrading and finding not the right answers that are specific to this problem (yes, I've read thropugh cyanogenmod wiki, read through the wiki here for dream/g1 phones, gsm programmer's sites, android dedicated sites, etc...ALL of them point to revskills for the goldcard gen (except for one which allows dowloading a perl prog to compile yourself to make the goldcard - I'm not so good with perl yet)
If you need to check the website go here:
psas.revskills.de/?q=goldcard
it's not working for me, whether through proxies in the US, netherlands, britain, frnace, or germany. My only conclusion is that it has been shut down.
Thanks for you attention and I really appreciate some advice from one of you that may be able to shed more light on this.
Incidentally:
SD Card: Hama 2GB Micro SD(formatted fat32)
Droid/HTC G1 phone has been factory reset to:
Firmware: 1.6
Kernel: 2.6.29-00479-g3c7df37 [email protected] #19
Baseband ver.: 62.50S.20.17U_2.22.19.26I
Build No.: DRC 92
are you going on that non exiatent site to download the qmat thing? maybe try looking for it as a torrent file... use bittorrent or something and see if it's out there... i wish i knew how to help more, but i never needed to do anything like that...
stupid question but did you try both dreaimg files? rc29 and rc7?
both img files
Yes, I tried both. The US version gave me the same response as the European one. Tried qmat 5.0.2 and got nowhere with it (i ran out of time before I could figure out everything it could do - apart from simply reversing the cid). The only way to create a gold card seems to be through revskills...kind of a raw deal for the rest of us, if you ask me.
yeahh haha this sucks im not sure what you can do... hopefully someone sees this who can help you. sorry
I am currently trying out the alternate root method from your guide. Something's working...the build version is now CRB43 and I have cupcake (1.5) installed - I think. I shoudl be able to go through the guide in order now, right?
yeah if you have 1.5 than all you need is a custom recovery installed and you have root access... i prefer amonra recovery.. than you can flash radio and spl and go even further by flashing the newer 2825 radio and 0013d hboot
I just have to update my phone account with a data plan (forgot I didnt have one and cant sign in to google without it). Fortunately, it's cheap and takes only a day to update.
OK, so i worked the alt recovery method, but I can't sign in to google. (I used the AMON_RA recovery img.) I can't do anything now. The phone is (for all intents and purposes, bricked. I then tried to do the work around to get the wireless turned on at the touch me screen. It doesn't work. Still no root access. trying to go back to stock rom, no go. Still get the "Not Allow" 00028002 error. Haven't seen the fast boot screen lately. I try the back arrow from the boot loader screen...nothing. Even went so far as to try the HTC site boot unlocker method. HTC Sync installed, android sdk installed, etc. got the drivers in win7 x64 to acknowledge the phone being plugged in...it even recognozed (once) as the HTC Dream/G1, after that never again. This is nuts! It's funny as well as highly annoying. I'm running out of ideas and could use some suggestions...
Thanks
incidentally, the link to "DREAIMG.nbh" in the unrooting section connects to a download of the update.zip file. So, the link is misplaced or something...
good news, the gold card gen sit is back up, however, I can't connect to the phone with adb...I have tried the workaround but I guess the image on this thing is still not rooted. I'm out of ideas what to do, I cannot sign in to google (registration work around) and I can't connect with adb to all the other work to change things. This phone is hosed (and I will absolutely not go to T-mobile (in germany) they're even worse here than in the US...
Here is the link that I found for dreaming.nbh file.
http://www.megaupload.com/?d=NAAS5VBS
See if that works.
So, I am resigning myself to never getting this fixed. I have a rom I cannot access because the data plan on my sim card is for Maxxim, while the rom sets everything up as T-Mobile. Maxxim support will not give out the APN info and, to top it off, the wireless work around does not work because the cupcake dreaimg.nbh and amon_ra recovery image still do not allow root access. I'm lost, got a "working brick" phone, and I'll be damned if I go crawling back to t-mobile whether here in Europe or the US! Thanks for the help anyway...
yeah sorry bout that will fix the link, but its the same one you use to 'downgrade' on the Root method.. just brings you to 1.0, then flash the update.zip to 1.5 or 1.6...
so you cant flash the DREAIMG.nbh file? and you cant do anything via recovery?
but your device works if you had a data plan.. lol wow all i can think of is trying to flash the orange.nbh or get the DREAIMG.nbh to work..
Yeah, tried the orange.nbh as well and I get the same error for every nbh I try:
"00028002 Not Allow". It's really weird that all the nbh do not work...it's almost deliberate. The only root that worked was the alternate root, but wouldn't that have let me flash other roms? Interesting that it didn't.
Good that this G1 is a spare, but I would still like to get it working. I've found a use for it at work but it needs to be rooted. Will post back shortly with results from the DREAIMG.nbh and orange.nbh (if need be).
Incidentally:
Bootloader screen:
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
SEP 2 2008
Does this give you any ideas? I can get to the recovery console but it does not necessarily mean I have root (as far as I've seen to this point). I mean, if I were able to register the phone without a data plan (using the wireless connection) I think I would be ok. I did have a point when I was able to connect to the phone via adb (but the phone was registered).
I know I don't have root because I am unable to do the <enter>reboot<enter> thing in the reg bypass method. How did that happen? -I've got no idea...
Another thought, Is there another way to install drivers on my windows machine so that the phone is recognised by adb (even though it's not regitered and I have no way of turning on debugging)? Is there a way to alter the build manifest so that USB debugging is on by default thereby allowing me to connect via windows?
Its painful to read threads like this..
Do you still have your sdcards CID from the OP?
If so using the sdcard you have the CID to make the goldcard on your computer, tben takethe orange nbh rename it to DREAIMG.nbh and place it onthe root of the sdcard.
Then flash the orage nbh and use fastboot to install the 2708+ radio/spl/custom recovery (ra or clockwork)
If you dont have the CID find a device (likely a friends phone) that can read the CID and pick up from there. (notice no adb, and only fastboot after flashing an nbh with an engenering spl)
(I didn'tsay it earlier as the goldcard site was down...)
How to I go about reading the CID on another phone? I am not too familiar with the process. I have a nokia X2. Will that work through a bluetooth connection? (it's my wife's phone and I don't want to try anything with that one until I am absolutely sure.
If you could point me at something I could read on how to do this, I would be exteremely grateful...
Thanks
the site http://psas.revskills.de/?q=goldcard is odwn for me, so I can´t create my gold card.
Any other way to access the site?
I'm following the CM guide for my inspore 4g, but when I searched this forum, this thread came up
So here's my final result:
* Followed steps in the guide for alt root method (nothing else worked but that) - gained root.
* Restarted in order to follow thorugh with the radio upgrade
* No root
* Reflash the ROM
* still no root
* Cannot connect adb to device
* Windows sees it only as USB (even after uninstalling and pointing the hardware to the Android SDK USB Drivers
So I've come into an infinite loop:
* Can't gain root without a goldcard (or some ability to take the NBH apart and modify the kernel - DEFINITELY not my strongest skill...
* Can't get a goldcard without being able to read the CID
* Can't read the CID without connecting with adb
* Can't connect with adb without USB Debugging on
* Can't turn on usb debugging without a) registering phone (no data plan) or b) having root access to type in the commands at reg screen (with SIM Card in) or initial screen (without SIM card)
I've tried every ROM I could find, used the Android Kitchen tool (to modify the ROMs I've found, adding root access), I've read every guide I could get my hands on, as well as trying to extract the nb files from the NBH (in hopes of spotting what I needed to change in order to enable the phone to come on with wireless ON). I have been unsucessful. Is the phone now a paperweight?
I appreciate and respect any suggestions (I've already thought of buying a new phone - so that suggestion is out ;-) ).
Thanks
Hello everyone!
I recently installed Android Froyo 2.2 (Incubus26Jc's Super FroYo RLS15 All Language), following mainly this thread http://forum.xda-developers.com/newthread.php?do=newthread&f=602, and also reading many others, about hardspl etc.
Everything went perfect! The phone workes just fine, full functioning!
My problem is that, after deciding to go back to windows mobile for selling my phone, I followed these steps :
"Switching back is very easy. All you gotta do is download your favorite WinMO rom, and rename RUU_Signed.nbh to KAISimg.nbh and place it on your SD card along with KAISDIAG.NBH.
Place the SD into your Kaiser and hold the Power button and camera button down, then take your stylus and hit the reset button. Follow the instructions on the screen to flash your Kaiser. When the flashing is done you should be back to running Windows Mobile."
I downloaded the shipped rom RUU_signed_WWE_1.56.405.5_22.45.88.07_1.27.12.17 but the update process stopped at about 1/3, and the phone rebooted with Android OS.
Also, when I press the power button+camera button, for a new update flash, after the three colors screen(KAIS130, SPL-3.07.0000, CPLD-8), the message "Loading..." appears and stucks.
I guess, my phone no longer has hardspl, and there is no way to put it back, neither put back the signed rom, if there is no WM os????
Any help/suggestions???
Thank you very much, in advance
I suggest you follow the tutorial switch back to Windows Mobile by Dukenukemx ~ http://forum.xda-developers.com/showpost.php?p=6461906&postcount=1
looks like a really lost hardspl. Maybe this will help you get back to windows http://forum.xda-developers.com/wiki/index.php?title=Kaiser_stuck_at_bootloader
aris0602 said:
I downloaded the shipped rom RUU_signed_WWE_1.56.405.5_22.45.88.07_1.27.12.17 but the update process stopped at about 1/3, and the phone rebooted with Android OS.
Click to expand...
Click to collapse
One question:
What version radio was on the phone BEFORE attempting a WinMoBlows flash?
It looks like the shipped rom had the 1.27.12.17 radio included in the bundle and, if so, this would explain the error in flashing.
One thing to check would be at the bottom of "Settings" page, touch "About Phone". Towards the bottom you will see "Baseband Version". The numbers at the end are your radio version and should be the original radio numbers. If it says "1.27.12.17", you've found one problem...
I would say follow dukenukem's post and try to reflash HardSPL again.
I haven't run into this problem yet since I will probably never sell either of my Kaisers... lol.
same problem at my place...
installed android, about 2 month ago, wanted to switch back to win and couldnt do it that simple as say "Switching back is very easy. All you gotta do is download your favorite WinMO rom, and rename RUU_Signed.nbh to KAISimg.nbh and place it on your SD card along with KAISDIAG.NBH. " in Dukenukemx's tutorial.
I have tried everything putting on sd card many ROM's Hardspl's, then i found this on my pc RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88. 07_1.27.12.11_Ship when i try to flash via usb (manually enter bootloader and connect usb cable) it get to 1% and reboots and ond rom update software says ERROR [294] : INVALID VENDER ID and above Exit button says: VER4-KBKV5867-HUEbc568-KBKV58670...
and when i try same rom to flash via sd card it says
Loading...
Checking...
0028002
Not Allow
with any other it stay's at 0% on phone and nothing is showed, then on RUU says ERROR [262] : UPDATE ERROR and down is button Recovery, tried a lot's of times nothing...
Then i saw that you PoXFreak said to check radio in baseband mine is 1.65.17.56
any sugestions please?
Another user with problems...
Tried a return from android to windows mobile because of the random locks that were happening in android (also some other weirdnessess...)
Now when it is put a microSD with kaisimg or kaisdiag it goes into white loading screen and stay there...
(tried flashing Kaiser_HTC_ASIA_HK_WWE_3.34.721.2, that seemed to be the one who came with my phone)
The baseband message somebody talked above shows only "HTC"
When in tricolor bootloader the following is showed:
security unlocked
KAIS***
SPL-3.28.0000
CPLD-8
(Still gonna try updating it connected to the computer, seems like usb and serial dettection are working, for it will dettect the charger connection and start showing USB in the lower part of the screen, battery got very low overnight, still needing to charge it to really do some test)
_____________
Update:
Flashed ok through USB, just entered tricolor bootloaded, connected usb and executed the original rom installer.
hello everyone
I used to have this kind of problem.. my hard spl broke when i tried to flash a stock wm rom from android.
In my opinion, each stock roms comes with specific SPL, radio version, etc. It means that when you are trying to flash stock rom, you also flashing new SPL. the problem is, the new SPL broke your hard SPL so you won't be able to flash anything to your kaiser except your original stock rom which comes with your kaiser.
you can find some stock roms for kaiser here : http://shipped-roms.com
Since I'm only sure that my kaiser originaly comes with WWE version I almost tried all the WWE stock roms there, but my search ended when I flashed RUU_Kaiser_CINGULAR_WWE_1.62.502.0_radio_sign_22.45.88.07_1.27.14.09R2_Ship.exe, this rom works for my phone and it seems that only this rom didn't give me "invalid vender ID" message.
so, keep trying to find your original stock rom
and after you managed to flash your stock rom, don't forget to flash hard-SPL again if you still want to mess around with your kaiser.
good luck
Another way to do it, albeit a little tougher, would be to use Oli's NBH tool and remove the SPL and radio from a stock rom. That way you get to keep the radio and SPL while flashing a stock rom.
Keep in mind that some WM roms only like certain radio versions, and you may end up having to flash an older (or newer) radio to find what works best.