Flash ROM problems - it refuses to flash - MDA III, XDA III, PDA2k, 9090 Software Upgrading

Ok, I am having a difficulty in flashing ROM using MaUpgradeUt_noID.exe and/or BaUpgradeUt.exe
Using MaUpgradeUt_noID.exe
I have the system rom (Aku's version) and a radio rom (1.5). Next, I run MaUpgrade tool; it detects the device flash as follows:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Okay, you might have questioned why is the device v5; that's because it worked before with baupgradeut tool, but right now, it doesn't work anymore and I wasn't sure how I managed to get it to work in the first place. The main reason I wanted to upgrade again was the radio rom (the connection is really bad) and the transcriber failed to function properly as an extended rom but that was like months after I did this. I often had to reset the device to fix those issues.)
Then after pressing Next, ActiveSync (I tried final version 4.5 as well as an older version 4.2 - both failed) would then get disconnected and ma utility will give me a Connection problem error as follows. I have to reset the PDA device to get activesync reconnected.
Using BaUpgradeUt.exe
Now this is the annoying part. I loaded the GetDeviceData.exe on the PDA and obtained the following:
Code:
P H 2 0 B 1 W W E AT%CID? 5 . 0 4 . 1 0 . 1.02.10 % 4
Removing all of the spaces, I get something like this:
Code:
PH20B1 WWE AT%CID? 5.04.10. 1.02.10 % 4
I wasn't able to find the device operator. So I just edited EditFix.bat like this (and of course, I run this batch - both files are modified (nk and radio_ ones)):
Code:
xda3nbftool -sd PH20B1 -sl WWE -so "" ms_.nba
xda3nbftool -sd PH20B1 -sl WWE -so "" nk.nba
xda3nbftool -sd PH20B1 -sl WWE -so "" radio_.nba
where I also tried to replace "" with T-MOB101, XGULB001, and XGULA001. (since the device is a Siemens SX66 purchased on ebay) All failed and returned a model error.
Is there anything I should do?

Your operator code seems to be deleted (should be sth like T-MOB101 - read here: http://wiki.xda-developers.com/index.php?pagename=GetDeviceData ). Now you can only use MaUpgradeUt_noID.exe untill you repair it (anyway operator code is not needed after all) by installing ROM with correct Operator code for your device (if you know/remeber it) set by operator or you using xda3nbftool.
Apart from this, you seem not to follow the procedure: you should put BA in Bootloader mode, not leave ActiveSync mode when you initiate upgrade.
Please post your results here, when you finish.

pichus said:
Ok, I am having a difficulty in flashing ROM using MaUpgradeUt_noID.exe and/or BaUpgradeUt.exe
Using MaUpgradeUt_noID.exe
I have the system rom (Aku's version) and a radio rom (1.5). Next, I run MaUpgrade tool; it detects the device flash as follows:
(Okay, you might have questioned why is the device v5; that's because it worked before with baupgradeut tool, but right now, it doesn't work anymore and I wasn't sure how I managed to get it to work in the first place. The main reason I wanted to upgrade again was the radio rom (the connection is really bad) and the transcriber failed to function properly as an extended rom but that was like months after I did this. I often had to reset the device to fix those issues.)
Then after pressing Next, ActiveSync (I tried final version 4.5 as well as an older version 4.2 - both failed) would then get disconnected and ma utility will give me a Connection problem error as follows. I have to reset the PDA device to get activesync reconnected.
Click to expand...
Click to collapse
Hello,
I've the same 101 error...
I don't really understand how to find a solution to upgrade without that problem...could you help me ?

Once I had a problem like this one and I figured out that I could not flash my device + radio at the same time.
Try removing the radio.nbf from the folder where MaUpgradeUt_noID.exe and then try to flash your device.
If it works, then remove the nk.nbf from the folder, put back the radio.nbf and try to flash it.

Tks.
I've put a topic for that.
It seems to be a Vista OS problem...

eleger91 said:
Tks.
I've put a topic for that.
It seems to be a Vista OS problem...
Click to expand...
Click to collapse
I confirm everything. Same problem for me with Vista. Upgrade is possible only under Xp. Maupgrade is not compatible with Vista. Someone should make a Vista version of it.

Nope not only vista. my xp home is having excatly the same problem. Completely stuck now and getting PreSetUSB along with other error msgs now on the device.

hi all of you
how can I fix sam problem

I'm having the exact same problem as you guys. anyone managed to find a work around to it ?

try this workaround...
1. avoid Vista... use XP
2. flash in BOOTLOADER mode. (press and hold Record+Powerbutton then softreset) then just ignore if the Device info FROM is missing... just click upgrade.

Hi Silver Samurai,
I am flashing in Winxp using bootloader mode and Maupgrade. Doesn't seem to work. I have followed everything in the wiki step by step. Such as disabling activesync.
Really don't know where i have gone wrong.

mtnbikefreak said:
Hi Silver Samurai,
I am flashing in Winxp using bootloader mode and Maupgrade. Doesn't seem to work. I have followed everything in the wiki step by step. Such as disabling activesync.
Really don't know where i have gone wrong.
Click to expand...
Click to collapse
what error numbers are you getting?
when does it fail?

Well i make a hard reset (No for the first option and yes to the 2nd and 3rd options.) After that leaving it in bootloader mode - showing serial and bootloader version number v2.08.
I make sure that activesync (usb connection is disabled). Close wcecomm.exe and other files related to activesync in taskmanager. Connected the usb cable and it changes from serial to usb. Invoked the Maupgrade noid.exe. It hangs there indefinately for more than 30 mins showing the screen that it is checking the xda. If i pull the cable out, it immediately shows device error.
I know that there is nothing wrong with the cradle as i can connect to activesync in normal mode and install programs / files.
I can still boot up after that with wm2005 helmi. Cannot seem to erase the rom. Funny thing is that with wm2005 my sd card cannot be detected. Previously with wm2003 it can be detected. However when the screen is off, and when i insert the sdcard, it does turn on. Likewise when i remove the card and the screen is off, it would also come on. But that is a total different aspect altogether. Anyway i figured that if i can reflash to the official wm2003 rom, it would solve that problem.
Sorry for the wall of text, but i just wanted to fully describe the problem i am facing. Could it be that the DiskOnChip is already corrupted ? Don't think that it's the Intel SRAM/Nand Flash chip as it's only 128Mbits. which only stores the bootloader.

is there an SD Card inserted when you are trying these procedures?
can you try both with or without it?
try without an SD first
please post your result.

Yes i have tried both with sd card and no sd card. If the SD card is inserted, in bootloader mode, the serial won't change to usb until i eject the sdcard. The screen would just get stuck showing the msg, checking the xda.

Related

[UPDATE April 3rd] WST v4.2.2 - Wizard Service Tool

Ok guys, here you have latest version of my tool
I decided to open a new thread because the original one was getting too big (my opinion at least) so if you want to know more about first versions then visit the old thread: http://forum.xda-developers.com/showthread.php?t=295038
EDIT: (2008-04-03)
I know it's been a while but things kinda busy lately... but here you have released the latest update which includes the changes present in the log below.
Change log:
v4.2.2 (2008-04-03)
-Added some "Device info" routine error checking;
-Replaced "Exit" button that was removed in last version (got too used to it);
-Fixed bugs with non-declared variables;
-Added possibility to try CID unlocking if IPL and SPL versions differ (IPL 1.xx & SPL >2.xx) due to failed downgrade (which has been proved to work HERE . Thanks Monktrump )
-Changed PagePool routine to allow editing value even if only one pattern is found (tested successfully in "Slim Edition v2.2" and "Snn Edition")
v4.2.1 (2007-10-10)
-Fixed User Area reading routine for G4 (size is different from G3);
-Fixed RADIO reading routine for G4 devices (thanks to itsme, once again);
-Fixed "Device Info" routine to display RADIO values for G4;
-Fixed "Device Info" HardSPL display info (wasn't showing values);
-Fixed "DOC has no value" bug;
-Fixed crash upon canceling 'device detection' routine;
-Removed "Exit" button because of above bug;
v4.2 (2007-10-05)
-Changed the version's numbering system. WST is no longer beta as someone pointed out so i remove the leading '0';
-Added HardSPL detection (checks for the string "Olip") for G4 devices;
-Fixed User Area reading (partition handle recognition wasn't working for G4 devices);
-Added size and signature check to OS.nb files to be flashed (safer to write OS now!);
-Improved Write ROM routine to display the progression of OS and Ext_ROM zones writing (no more freez&wait);
-Fixed a bug in key index (CID) routine that caused errors in key#22;
-Fixed a bug that was leaving WST process running even after closing program in some occasions;
-Added a 10MB option to the Poolpage routine;
v0.4.1.0 (2007-09-19)
-Fixed a bug in read/write ROM routines where a variable wasn't initialised properly and would crash program;
-Restored some commented code that prevented SPL check in CID unlocking routine (didn't check G4 nor G3 SPL 2.xx);
-Fixed IPL dump from memory to generate an exact copy of an original IPL;
-Added code to Extended_ROM option to COPY files to HDD (forgot to move code while porting functions);
-Improved 'PagePool' routine code (more time to read program messages);
-Added IPL version to "Device Info" routine;
-Added 'Check nk.nbf' routine (to know what chunks are in a nk.nbf)
v0.4.0.0 (2007-09-12)
-Cleaned up some code and fixed a lot of errors resulting from new REXX interpreter version;
-WST is now PORTABLE, i.e, no longer requires the install of Reginald interpreter and doesn't write to registry;
-Replaced the log window (list control) with a text entry to allow selecting and copying the information;
-Added more info to "Device Info" feature: cleary states if it's a G3 or G4, shows date of SPL, shows name and -visibility status of extended_rom;
-Removed 'Repair IMEI' section and placed the button in 'General options' (works the same way as previous);
NOTICE: Thanks to itsme that updated his itsutils it's now possible to change IMEI in G3 without the need to downgrade to 1.xx and also on G4 CID unlocked!!!
-Eliminated the Extended_ROM window and moved the functions to the main script;
-Added 'Format ROM' option to ext_rom;
-Added a patching for the PagePool that doesn't rely on a fixed address (looks for pattern);
-Added option to read IPL from memory;
-Fixed the read SPL routine to detect G3 or G4 device (now produces a replica of the SPL.nb);
-Added an option to read ALL ROM sections at-once and also automatic file naming;
-Fixed an issue with files being saved with spaces in their names (pdocread limitation, though);
mestrini
PS:
latest version ZIP already includes the windows DLL (msvcr71.dll) needed by Win2K and XP not up to date...
EDIT:
I had to remove version 4.2.2 from April 2nd to remove a debugging instruction i forgot and that was crashing WST.
I didn't change the version number so check if you have latest 4.2.2 from April 3rd!!!
EDIT2: (2008-04-12)
I removed v4.2.1 as the downloads kept increasing which i assume may be from external linking. This way people weren't getting the latest version
reserved for pics
Pictures of features:
1- PagePool
You can use the button to change the page pool that will take effect after a soft reset. if you just want to check the value you simply cancel the procedure and nothing will be written to ROM
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2 - Check DOC chip version (G3 or G4??)
Select the "Device Info" button and wait for program to finish. Once finished check SPL version and the info about the Gx generation of your device.
3 - Check CID lock status
Use the "CID Actions" button and then the "Read CID block" from the drop down list (selected by default)
Once finished you'll be presented with the CID value (referring to the service provider code) and the corresponding status (unlocked in this case)
Enjoy...
Thanks mestrini!
It is fully working now without any problem.
Thanks Mestrini !
Great tool you got there man. Congrats !
Please read this post...can your tool read the build number wrong ?
anichillus said:
Great tool you got there man. Congrats !
Please read this post...can your tool read the build number wrong ?
Click to expand...
Click to collapse
Yes, it sure is possible because my tool grabs some some .dsm files from the \Windows folder and reads the build values present inside. I guess that not all the .dsm files have the build updated or are used from older builds. It's done this way because some kitchen builder (can't recall who) directed me that way.
Now if anyone knows a 'safer' way or a specific .dsm file that has the most recent build value i'll update my tool.
Anyway, thanks for the feedback m8s
Am I missing something?
I'm planning to load WM6 on my Wizard (T-Mobile MDA Vario II) but wary of bricking it, so when I came across references to WST I was very pleased. I'm hoping it will let me take a backup of the existing ROM that I can reload if my attempts at a WM6 install fail.
I downloaded WST and read the readme.txt file. I ran the installer, checked my Wizard is connected via USB and ActiveSync is happy. All is good so I fire up WST.
It looks great - very neat and no confusing stuff in the UI. Well done!
I note the bit about needing to enable RAPI stuff before anything else, so that's what I do. The tool seems to connect and run the cabs and then completes without reporting any problems, but then if I try any other option I get a message telling me a device was detected but one (or both) of RAPI
Communications and Applications Policy isn't enabled.
Do I need to do something else before I can use this tool?
Can I enable RAPI maually outside of the tool before I begin?
That is strange. Have you tried closing WST and then open it again? That's the problem of most cooked ROMs nowadays that are already RAPI enabled and it's possible to let something pass by when writing that procedure.
That is strange. Have you tried closing WST and then open it again? That's the problem of most cooked ROMs nowadays that are already RAPI enabled and it's possible to let something pass by when writing that procedure.
Click to expand...
Click to collapse
I tried that. My current ROM is not cooked. It's the one shipped by T-Mobile (I'm scared of breaking anything so I want to take a backup of this ROM before I try swapping it out for WM6).
Since then I've also done a soft reset on the Wizard and a reboot on my PC (Win XP Pro) but I get the same problem
There doesn't seem to be anything in the options or setup within the device to enable RAPI or unsigned apps. Do I need a registry editor too?
Just in case it's significant:
ROM version is 2.21.2.6 WWE
ROM date is 3/9/06
Radio version is 02.19.11
Protocol version is 4.1.13.09
ExtROM version is 2.21.2.109
Thanks for supporting WST - this is great!
Sorted!
I copied the .cab files from the WST folder (created when I installed WST) on to my Wizard and ran them from the Wizard UI.
Now WST can talk to my device! Yayy!
Yes I am missing something.
When I read the original messages I misunderstood the purpose of WST. I got the idea that I'd be able to copy my current ROM as a backup before I started fiddling (loading WM6).
Having got WST to talk to my device I now find I was mistaken. There doesn't seem to be the option of capturing the whole ROM for use as a backup, so I'm no nearer (except I do have a neat way to interrogate my device now - that's cool!)
So, what do other people do about safeguarding their original setup - or at least making sure they will be able to reload an official ROM if necessary - before trying new ROMs?
Am I just being over-cautious? Does everyone just jump in without thinking about a safety net?
Tulaine said:
When I read the original messages I misunderstood the purpose of WST. I got the idea that I'd be able to copy my current ROM as a backup before I started fiddling (loading WM6).
Having got WST to talk to my device I now find I was mistaken. There doesn't seem to be the option of capturing the whole ROM for use as a backup, so I'm no nearer (except I do have a neat way to interrogate my device now - that's cool!)
So, what do other people do about safeguarding their original setup - or at least making sure they will be able to reload an official ROM if necessary - before trying new ROMs?
Am I just being over-cautious? Does everyone just jump in without thinking about a safety net?
Click to expand...
Click to collapse
You can backup your ROM but you must do it in several steps (or one step but will several files)
Later you can pack the files inside an RUU and flash back to phone or use WST to flash them back (OS & Ext_Rom at least)
Installed and running. Using the Start|Programs|Wizard Service Tool!Wizard Service Tool shortcut, found that I needed to modify the working folder, that is, remove "files" from the path. Running XP Home SP2. Installed to defaults.
Like the ability to save the Device Info to the clipboard. Useful as is providing a filename template including the date when saving ROM Zones
mestrini said:
You can backup your ROM but you must do it in several steps (or one step but will several files)
Later you can pack the files inside an RUU and flash back to phone or use WST to flash them back (OS & Ext_Rom at least)
Click to expand...
Click to collapse
A few questions about using WST to upgrade a Wizard, getting close to doing so on a G3 with the current ROM versions 1.-- that is now CID unlocked.
From what I am reading here WST will write ROM Zones as and when but should care be taken such as upgrading the IPL/SPL zones at the same time between soft resets?
I also note previous comments that the version relationship between the IPL/SPL and the OS should be maintained but looking at some of the cooked ROMs these sometimes look to mix the version 2 and 3 IPL/SPL zones with the different OS versions including whether it has WM5 or WM6. Indeed, have read that some feel that there is limited value in going above the version 2.-- IPL/SPL zones. Is there a rule of thumb here that can be checked, versions of particular files in the OS against the version of IPL/SPL or is it only version 1.-- IPL/SPL that can cause dependency problems with later OS ROMs?
Thanks for every ones contributions here.
mick.j said:
Installed and running. Using the Start|Programs|Wizard Service Tool!Wizard Service Tool shortcut, found that I needed to modify the working folder, that is, remove "files" from the path. Running XP Home SP2. Installed to defaults.
Click to expand...
Click to collapse
There was a similar complaint in version 0.2 but i don't see how that "files" ended up there. It installs perfectly on my system. Please paste here the full path you got.
mick.j said:
A few questions about using WST to upgrade a Wizard, getting close to doing so on a G3 with the current ROM versions 1.-- that is now CID unlocked.
From what I am reading here WST will write ROM Zones as and when but should care be taken such as upgrading the IPL/SPL zones at the same time between soft resets?
I also note previous comments that the version relationship between the IPL/SPL and the OS should be maintained but looking at some of the cooked ROMs these sometimes look to mix the version 2 and 3 IPL/SPL zones with the different OS versions including whether it has WM5 or WM6. Indeed, have read that some feel that there is limited value in going above the version 2.-- IPL/SPL zones. Is there a rule of thumb here that can be checked, versions of particular files in the OS against the version of IPL/SPL or is it only version 1.-- IPL/SPL that can cause dependency problems with later OS ROMs?
Thanks for every ones contributions here.
Click to expand...
Click to collapse
The big difference lies between 1.xx and 2.xx. Everything else should be safe. WM5 or WM6 can be run with IPL/SPL 2.xx or 3.xx and also with any 2.xx radio
But since your device is CID unlocked you should consider upgrading your Wizard via RUU
WST
This program is Awesome many many thanks!
The last version before this one worked perfectly.
mestrini said:
There was a similar complaint in version 0.2 but i don't see how that "files" ended up there. It installs perfectly on my system. Please paste here the full path you got.
Click to expand...
Click to collapse
Checked the WST folder in Program Files and it had the following folder tree.
Wizard Service Tool\
Wizard Service Tool\Files\
Wizard Service Tool\Files\Temp\
Wizard Service Tool\Files\ Files\
Wizard Service Tool\Files\ Files\Temp\
Un-installed and deleted the respective folders in Program Files. Reinstalled and the "start in" path is "C:\Program Files\Wizard Service Tool" and opened OK whereas in the previous install it had been "C:\Program Files\Wizard Service Tool\files"
Looks like some residue from the previous version may have affected the path.
The big difference lies between 1.xx and 2.xx. Everything else should be safe. WM5 or WM6 can be run with IPL/SPL 2.xx or 3.xx and also with any 2.xx radio
But since your device is CID unlocked you should consider upgrading your Wizard via RUU
Click to expand...
Click to collapse
I was looking to bypass installing a full ROM to update Radio, IPL and SPL and then installing an OS of choice but your advice is well taken and thanks for clarifying the version issues that I had.
Regards.
GateArray said:
The last version before this one worked perfectly.
Click to expand...
Click to collapse
That is not very helpful. Now i know there's a bug in it but not what it is or how to try and fix...
Pls give more details as how you got there and what did you do
mick.j said:
Un-installed and deleted the respective folders in Program Files. Reinstalled and the "start in" path is "C:\Program Files\Wizard Service Tool" and opened OK whereas in the previous install it had been "C:\Program Files\Wizard Service Tool\files"
Looks like some residue from the previous version may have affected the path.
Click to expand...
Click to collapse
What OS are you running? XP Pro English? It may also be related to a specific OS version? Anyway, I'm glad you sorted it.
mestrini said:
That is not very helpful. Now i know there's a bug in it but not what it is or how to try and fix...
Pls give more details as how you got there and what did you do
What OS are you running? XP Pro English? It may also be related to a specific OS version? Anyway, I'm glad you sorted it.
Click to expand...
Click to collapse
Here I am
SO: W2000 server english
I have tried to re-install ver 0.3.0.3 and it works fine
I also have tried to "clean" old version before install 0.4.0.0.... same problem
I tried to uninstall the compiler REXX from CP
same result still....
Tomorrow next tests.
Hold. You're getting it as soon as WST starts?

Upgrading SX66 to WM 6

Hi, I need your help. I read some of the XDA tutorial and I don't understand it.
Can someone guide me, step by step, how to upgrade to Windows Mobile 6 from 2003? I don't want to mess anything up, and currently have none of the files.
read wiki there is a upgrade wizard which will guide you
xplode said:
read wiki there is a upgrade wizard which will guide you
Click to expand...
Click to collapse
"I read some of the XDA tutorial and I don't understand it."
On it it says...
"If you plan to easily revert back to WM2003 or you don't want those extra MBs (Mega Bytes) on your BA, skip the next steps."
Also it says
"In WM5 and WM6 you are not using your RAM as storage for programs or documents anymore. Instead of RAM you are using Storage - because as we said before, no data is lost when your battery runs out.
Because of this, it's a good idea to merge your ExtROM with Storage to one "BIG Storage". (You will not install anything from ExtROM. You're not using non-persistent memory for storing programs anymore. Instead of ExtROM you can use SD or MMC card (Memory card), or install the hotfixes once after the flashing)"
Is there a way I can keep 2003, and also WM6? Or can I only have one in my phone? Do I do those steps? Do I skip them?
http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM6_WizzardUpgrade1_WM2003SE0
I just need someone to guide me step by step, where I can ask questions, etc.
I also need tips, and information.
Do as xplode said. Follow the Wizard.
As per your question, [highlight]do not skip steps!!!![/highlight] All instructions are there for a reason!
And finally, you cannot have a dual boot on the Blue Angel. You can have either 2003 or WM6, but not both at the same time. You can always flash back and forth...
If you have questions, please search before you ask. And then, if the answer is not found, then ask someone.
I'm kind of stuck now... Not sure if I'm in bootloader mode or not, and when I run "MaUpgradeUt" it says "ERROR 150: ROM UPGRADE UTILITY ERROR"
...What do I do now?
if you are in botloader mode on your screen thould be Serial or USB (when connected to pc) if you want i can guide you over skype or msn or icq
I would love if if you could.
Please add XeneRoX @ Hotmail.com (separated it so a spammer bot doesn't catch it)
XeneRoX said:
"I read some of the XDA tutorial and I don't understand it."
Click to expand...
Click to collapse
Me too I did not understand the wiki when I used to be a newbie here, but I kept on reading it until my brain hurts, but what do you know I got it after reading the whole wiki for 3x.
On it it says...
"If you plan to easily revert back to WM2003 or you don't want those extra MBs (Mega Bytes) on your BA, skip the next steps."
Click to expand...
Click to collapse
It simply means that if you are OK with the default settings/partition of the internal storage/memory of you BA then skip the next steps which I dont recommend!!!
Also it says
"In WM5 and WM6 you are not using your RAM as storage for programs or documents anymore. Instead of RAM you are using Storage - because as we said before, no data is lost when your battery runs out.
Click to expand...
Click to collapse
In WM2003SE BA use RAM as a storage medium hence if the BA resets itself in anyway you lost everything in it, unlike in WM5 and WM6 onwards we use SD CARDS as storage medium hence even if we SR (Soft Reset) or HR (Hard Reset) our BA nothing will be erase on the SD card, so those pics of naked girls, those asian scandals on your SD Card won't be erase..lol
Because of this, it's a good idea to merge your ExtROM with Storage to one "BIG Storage". (You will not install anything from ExtROM. You're not using non-persistent memory for storing programs anymore. Instead of ExtROM you can use SD or MMC card (Memory card), or install the hotfixes once after the flashing)"
Click to expand...
Click to collapse
same thing, if I were you I will follow all the steps and will not skip..not even one step!
Is there a way I can keep 2003, and also WM6? Or can I only have one in my phone? Do I do those steps? Do I skip them?
Click to expand...
Click to collapse
Yes there is a way you can keep your WM2003se stock ROM...you can use ROM DUMPER..BUT...I don't recommend that because...sorry to say...if you are having a hard time upgrading you BA even if WIKI is there then you'll get a very hard time with ROM DUMPER .
You can only have one OS INSTALLED at a time on a PPC. I emphasized INSTALLED because you can have android copied on you SD even if you have one OS INSTALLED on your BA...does is sound clear? Hehehe
NOW....
Before you upgrade your BA keep this is mind...it's a warning...a WARNING so you will not sue xda-dev or any BA ROM cooker if something BAD happens to your BA. But don't worry 1 out of 1000 BA owners brick their BA while upgrading. Because they upgrade their BA with 10% battery life. Where did I get the 1 out of 1000 statistics? Just a guess..a wild guess but it's near to reality
WARNING
IF YOU PROCEED, YOU MAY TOAST YOUR PHONE. THERE'S NO COMEBACK. THERE'S NO GETTING ROUND THIS. READ THE INSTRUCTIONS FIRST OTHERWISE YOU'LL PROBABLY BREAK YOUR PHONE PERMANENTLY. THIS WILL VOID YOUR WARRANTY. DO YOU UNDERSTAND? DO YOu? ANSWER ME YOU...lol
Click to expand...
Click to collapse
- Download unlocker.cab DOWNLOAD HERE
- Download Repart_Doc.exe DOWNLOAD HERE
- Place both of them somewhere on your Pocket PC. For example in \temp but anywhere is fine. All the command below are to be executed on your Pocket PC, not on your PC.
- Install xda-developers_Unlocker.CAB by tapping on it in filemanger (from the directory where you put it earlier)
- Then go to start -> Programs -> ExtROM tools -> then first run "unhide", then "Unlock".
- Do a soft reset. (you know how to do a SR, right?)
- Once your Pocket PC is restarted, locate the Repart_DOC.exe file with your filemanager and start it.
- Set the size of Extended ROM to 128 kb (which is already the default).
- Press "Format now!" and wait until it is done (A few seconds). You will see a message that it is done. (You will get an error message about your storage, just press yes and wait a few seconds.)
- Soft reset your Pocket PC.
NOW YOU ARE DONE WITH THE FIRST PART AND I HOPE I AM MAKING IT EASY FOR YOU AND FOR EVERYONE.
Now, I RECOMMEND you to use Windows XP and of course Active Sync 4.5.
1. Download the BA ROM that you desired. It can be WM6, WM6.1 or WM6.5 and you can find all the download links of this ROMs on our BA wiki (and I am the one who updated that and put those links.)
2. Save that ROM on your computer. (anywhere will do) If it is zipped or rar, then unzip it or unrar it.
Here are the files that should be inside that ROM folder (well this are the files that I have every time I flash my BA, just correct me guys if some of this are not really needed):
EnterBL.exe
GetDeviceData.exe
HTCRUU.dll
RUU.dll
BaUpgradeUt.exe
MaUpgradeUt_noID.exe
HTCRUU.conf
RUU.conf
vbscript.dll
nk.nbf
SetOperator.bat
3. Temporarily remove your SD Card (it may work for you with the SD card still in your BA, but you may not be able to enter USB mode when cradled).
Just remove your SD Card from you BA and the SIM card too just to make sure.
4. Put your device into Bootloader mode by pressing and holding the "Power" & "Record" buttons, and then press the Reset Button. Ooops before I forgot make sure you do a Hard Reset on your BA first.
Press and hold the "Power" & "Record" buttons, and then press the Reset Button until “Serial” shows on screen.
(Some BlueAngel shows "Serial" at the top and "V2.07" at the bottom.)
NOTE: The screen will not be backlit, so it may appear the phone is not in bootloader mode.
Look carefully.
When the USB sync cable is inserted into the phone and the computer, "Serial" will change to "USB", provided that the phone detects the connection.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. Connect the phone to the sync cable/cradle.
7. Now you can execute the installer file. (BaUpgradeUt.exe or MaUpgradeUt.exe) You will see this window:
8. When the upgrade is completed, you must perform a Hard Reset.
When the bootscreen, aka. the colored stripes is displayed, wait more, you are booting. The welcome screen to set up your device will appear shortly ...
Put back your SD Card and you SIM card.
And there you go...I hope this makes upgrading easy for you and for everyone else. Did I missed something guys? Let me know.
WOW this is the longest post I've ever had since I started here...hehehe...just killing some TIME.
Yes!!!!!!!!!!!!!!!!!!!!!!!!
But is awsome men! really good work this is really a clean explanaition an dmaybe a refreshed how to upgrade....! truly!
thanks thanks thanks hehehe

hello experts of x1 xperia need help

hello sir,
i am new member of this forum.also i proud to be part of this forum.
i have one X1 XPERIA. BEFORE IT WAS CHINESE/JAPANESE LANGUAGE.
SO I ASK TO GSMHOSTING.
THERE I FOUND SOME SOLUTION. LIKE:
0. Make sure x1 is hard-spl first
1. Make sure your micro-sd is formatted w/ fat-32
2. rename the image file (normally "ruu_signed.nbh") to Kovsimg.nbh, copy that to the micro-sd, and put that it your X1,
onto the storage card root
3. Make sure X1 is disconnect to your PC to avoid goes to serial mode (AC power source is OK)
4. Bring x1 to boot-loader mode by turning off the x1 completely. Hold the "volume down" button on the right,
and hold the power on button until you see the tri-color screen.
5. Then follow the on-screen instruction
THEN IT SAY TO UPGRADE TO POWER BUTTON, I PRESS THEN PROGRESS
BAR COME IN SCREEN. THEN FULL UPGRADE SET LIKE RESTART....
BUT NOW ON WHITE LIGHT COME THIS WORD (LOADING.....)
TILL HERE I DO SUCESSFUL BUT NOW SET HANG ON (LOADING...)
I LEAVE 3 HOUR BUT SAME.
SO I REMOVE BATTERY AND PUT AGAIN AND POWER ON
COME ON SCREEN
TRICOLOUR & THERE IS SOME THING LIKE THIS:
CONTINITY UPGRADING ROM, PLEASE WAIT, THEN GO LOADING......
HOW TO REVIVE IT????
NEED HELP SIR.
Do you have a card reader?
If so, plug into PC and check if the ROM is indeed on the card and correctly named.
Device needs a full charge, this is imperative.
It is not a good idea to interrupt a ROM flash.
Report back with answers and I'll try to get you back up and running.
sattar_00977 said:
hello sir,
i am new member of this forum.also i proud to be part of this forum.
i have one X1 XPERIA. BEFORE IT WAS CHINESE/JAPANESE LANGUAGE.
SO I ASK TO GSMHOSTING.
THERE I FOUND SOME SOLUTION. LIKE:
0. Make sure x1 is hard-spl first
1. Make sure your micro-sd is formatted w/ fat-32
2. rename the image file (normally "ruu_signed.nbh") to Kovsimg.nbh, copy that to the micro-sd, and put that it your X1,
onto the storage card root
3. Make sure X1 is disconnect to your PC to avoid goes to serial mode (AC power source is OK)
4. Bring x1 to boot-loader mode by turning off the x1 completely. Hold the "volume down" button on the right,
and hold the power on button until you see the tri-color screen.
5. Then follow the on-screen instruction
THEN IT SAY TO UPGRADE TO POWER BUTTON, I PRESS THEN PROGRESS
BAR COME IN SCREEN. THEN FULL UPGRADE SET LIKE RESTART....
BUT NOW ON WHITE LIGHT COME THIS WORD (LOADING.....)
TILL HERE I DO SUCESSFUL BUT NOW SET HANG ON (LOADING...)
I LEAVE 3 HOUR BUT SAME.
SO I REMOVE BATTERY AND PUT AGAIN AND POWER ON
COME ON SCREEN
TRICOLOUR & THERE IS SOME THING LIKE THIS:
CONTINITY UPGRADING ROM, PLEASE WAIT, THEN GO LOADING......
HOW TO REVIVE IT????
NEED HELP SIR.
Click to expand...
Click to collapse
Hello!
Try this, then flashing again:ftp://x1:[email protected]/XperiaX1/TOOLs/X1_HardSPL_Utility.zip
Your spl is:spl-0.72.OliNex? If it is not the spl-0.72.OliNex version (check it on the tricolour boot screen ) will not succeed then the flashing.
HARD-SPL XPERIA X1 INSTRUCTIONS
Flashing Olinex Hard-SPL will not hard-reset your device
Nothing will be changed (except the SPL)
But it is recommended to backup your info first, just in case
1- Charge phone at least 50% (90-100% recommended)
2- Sync device, be sure activesync finishes syncing
3- Run "X1_HardSPL.exe
"
4
- Follow the on-screen instructions
WHAT YOU WILL SEE:
When "Loading..." bar shows in PC, check device screen
Phone goes into "bootloader mode" (tricolour screen)
Hard-SPL flashes automatically and device reboots
Done
TO CONFIRM A SUCCESSFUL HARD-SPL:
Go into bootloader mode (hold vol down key and press power)
Verify in the tricolour screen: "0.72.OliNex
"
augie7107 said:
Do you have a card reader?
If so, plug into PC and check if the ROM is indeed on the card and correctly named.
Device needs a full charge, this is imperative.
It is not a good idea to interrupt a ROM flash.
Report back with answers and I'll try to get you back up and running.
Click to expand...
Click to collapse
yes sir i make full charge battery.
and i rename to file "Kovsimg.nbh"
but sir how long time it take this process (approx.)?
oliolioli said:
Hello!
Try this, then flashing again:ftp://x1:[email protected]/XperiaX1/TOOLs/X1_HardSPL_Utility.zip
Your spl is:spl-0.72.OliNex? If it is not the spl-0.72.OliNex version (check it on the tricolour boot screen ) will not succeed then the flashing.
HARD-SPL XPERIA X1 INSTRUCTIONS
Flashing Olinex Hard-SPL will not hard-reset your device
Nothing will be changed (except the SPL)
But it is recommended to backup your info first, just in case
1- Charge phone at least 50% (90-100% recommended)
2- Sync device, be sure activesync finishes syncing
3- Run "X1_HardSPL.exe
"
4
- Follow the on-screen instructions
WHAT YOU WILL SEE:
When "Loading..." bar shows in PC, check device screen
Phone goes into "bootloader mode" (tricolour screen)
Hard-SPL flashes automatically and device reboots
Done
TO CONFIRM A SUCCESSFUL HARD-SPL:
Go into bootloader mode (hold vol down key and press power)
Verify in the tricolour screen: "0.72.OliNex
"
Click to expand...
Click to collapse
yes sir i am sure this is spl-0.72.OliNex
and i have "X1_HardSPL.exe .
but problem is that how to sync with pc? in this condition?
No need to sync with PC to flash via SD card.
If you have the ROM on the card and Hard_spl on the device, follow instructions listed in the thread.
DO NOT sync with PC until flash is complete.
augie7107 said:
No need to sync with PC to flash via SD card.
If you have the ROM on the card and Hard_spl on the device, follow instructions listed in the thread.
DO NOT sync with PC until flash is complete.
Click to expand...
Click to collapse
"Hard_spl on the device" I ALRADY DO THIS BEFORE. AND ROM IS IN THE CARD
AS RENEAME "Kovsimg.nbh".THIS FILE ARE .NBH FORMAT & SAME FILE IN RAR FORMAT.
BUT STILL SAME ONLY LOADING......(in blue colour) in white display light.
sir, it take how long time????
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after that set show only this from last 1 hour.
i confused? how long will take??
not 100% as I'm very much an amateur at this , but that kovsimg file is WAY too small. What are you trying to flash on it??
If a full rom, the size will be in tens or probably a hundred and more MBs.
And a successful flash has taken me about 10 minutes in the past, but I've only done it twice.
the "kovsimg.nbh" is incomplete, it should be a lot bigger like the above poster has said, at least 70mb.
Im not sure if having a capital K has any affect.
Where did you get your rom from?
Sorry, im not familiar where the "Loading..." comes from.. is that before or after where you press the Power Button to start flashing the kovsimg?
Edit: nvm, loading is just before kovsimg.nbh is found. You will need to download the rom properly. Check the file size and make sure its big as in 100-200mb, and place it in the root of the storage card with the name "kovsimg.nbh" lower case.
That is correct.
The file you are showing is most likely the Hard_spl file which is about that size.
A full Rom runs from 130MB to 220MB depending on contents.
cykalu said:
the "kovsimg.nbh" is incomplete, it should be a lot bigger like the above poster has said, at least 70mb.
Im not sure if having a capital K has any affect.
Where did you get your rom from?
Sorry, im not familiar where the "Loading..." comes from.. is that before or after where you press the Power Button to start flashing the kovsimg?
Click to expand...
Click to collapse
"Loading" is normal. It will move from 1% to 100% as the ROM is flashed.
Yeah. I just went to the bootloader to check it out again.. normally i just spam the power button till it starts flashing.. hence i dont remember such a text
But ya.. it shows up just before it confirms the location of a proper kovsimg.. but i thought it would say "invalid image file" which happened to me once.. not get stuck in "Loading.."
I usually flash my phone once every week or two.. new releases of cooked roms are just that great ;D
esudl said:
not 100% as I'm very much an amateur at this , but that kovsimg file is WAY too small. What are you trying to flash on it??
If a full rom, the size will be in tens or probably a hundred and more MBs.
Click to expand...
Click to collapse
THANKS BRO.
U CAN GIVE ME FULL ENGLISH ROM PLEASE?(NOT RAPIDSHARE)
i search rom's but all rapidshare link,it's need premiur account.i don't have that. thatsway i need free (without account)
link.
There's a fine selection of roms on this forums.. worth checking out to see which one is for you, each has its features and specialties.
The question is.. do you want WindowsMobile 6.1 or 6.5? Want TouchFlo3D? 2.1 ("TR", faster, stable, less ram and battery usage) or 2.5? ("Leo", experimental, slightly sluggish and drains more battery than TR, but nicer looking and better "Home" screen); you can skip TF3D and opt for SBP Shell tooo...
My favorite is agent_47's Valkyrie Firestorm (Rhodium\TOPAZ) @ http://forum.xda-developers.com/showthread.php?t=512050
But be careful when installing your own applications as it may conflict with the rom and causes it unstable ._. if you want a lot apps you want to install, you may want to not use TF3D (you can use the rom but you can disable TF3D in home settings, which is normally defaulted to "Titanium (WinMo6.5)" home screen )
Edit: You can download from Rapidshare for free when you click the "free user" button which should be next to the "premium user" button and wait around 30-50 seconds before it allows you to download; you don't need a premium account ^_^
cykalu said:
There's a fine selection of roms on this forums.. worth checking out to see which one is for you, each has its features and specialties.
The question is.. do you want WindowsMobile 6.1 or 6.5? Want TouchFlo3D? 2.1 ("TR", faster, stable, less ram and battery usage) or 2.5? ("Leo", experimental, slightly sluggish and drains more battery than TR, but nicer looking and better "Home" screen); you can skip TF3D and opt for SBP Shell tooo...
My favorite is agent_47's Valkyrie Firestorm (Rhodium\TOPAZ)
But be careful when installing your own applications as it may conflict with the rom and causes it unstable ._. if you want a lot apps you want to install, you may want to not use TF3D (you can use the rom but you can disable TF3D in home settings, which is normally defaulted to "Titanium (WinMo6.5)" home screen )
Edit: You can download from Rapidshare for free when you click the "free user" button which should be next to the "premium user" button and wait around 30-50 seconds before it allows you to download; you don't need a premium account ^_^
Click to expand...
Click to collapse
it is WindowsMobile 6.1 . already say it was chinese/japanese lang.
so i want english. if you recomand any rom's good. my costumer give too tension me. thatway i need help to this.
Actually i from nepal here too slow the internet.thatsway i try to download
come too much problem in rapidshare.therefore i need another link.
thank you.
Well, I'd say go for Agent_47's Valkyrie Firestorm (Rhod/Topz) version 5.0.28005, download it from his FTP.. I downloaded from that on a 56k dialup speed (capped internet.. bloody Australia) which took 6 hours and it came out perfect
Check out his thread @ http://forum.xda-developers.com/showthread.php?t=512050; sorry i cant hotlink people's stuff.. so you'd have to visit their thread
If you have time to play around a few roms to test with, i'd recommend MrRusch & WildChild - Untamed @ http://forum.xda-developers.com/showthread.php?t=568918
Also, check the other cooks' work too
cykalu said:
Well, I'd say go for Agent_47's Valkyrie Firestorm (Rhod/Topz) version 5.0.28005, download it from his FTP.. I downloaded from that on a 56k dialup speed (capped internet.. bloody Australia) which took 6 hours and it came out perfect
Check out his thread @ http://forum.xda-developers.com/showthread.php?t=512050; sorry i cant hotlink people's stuff.. so you'd have to visit their thread
If you have time to play around a few roms to test with, i'd recommend MrRusch & WildChild - Untamed @ http://forum.xda-developers.com/showthread.php?t=568918
Also, check the other cooks' work too
Click to expand...
Click to collapse
thank you bro help me.
at last i want to know this files also flashing via sd card?
any others file also keep in sd card??
please add me to your massanger
id is : [email protected]
thank you.
You can flash any kovsimg straight from a SD card, just make sure it's named correctly and it's placed in the root. You can have other files/folders on the SD card as well, it wont affect it, so no need deleting everything before flashing. The only file that will be used in the flashing of the device is whatever's named kovsimg.nbh (sp?) and nothing else.
One advice after flashing is.. hard reset the device straight after. Hardreset as in pressing and holding the two silver softkeys then press and release the power button, follow the instruction (press R and then Spacebar on the hardware keyboard). You can only hardreset when the device is off first.
Hard Resetting will get rid of a lot of problems which didn't occur for other people until the applications you install on top conflicts with the system (mostly with TF3D)

[Testing] Bigger ROM size.

Hi
I managed to use extrom as a part of rom, just like 2k3 does it, but some better.
This rom is 6.5 23140 fully provided, with EzInput, MS Office 2010 and Esmertec Java
I also got 236% in tcpmp benchmark, comparing to 157% in 23668. All important drivers are moved to xip to speed anything up.
Sounds good enough ;>?
Also I activated media control in lockscreen and fixed Internet Explorer
After installation you will get 2 partitions, root \ and Storage.
Some screens:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to install? It's not that easy, read it carefully:
1. Download MTTY attachment, download Rom (link above).
2. Put your phone into bootloader and put into crandle
3. Run MTTY and click USB button. Then type in white field "task 28" without quotes and wait 5 seconds. Some confirmation informations should appear.
4. Close MTTY, Unpack Rom, run Upgrade.exe, having 3 files is important (nk, ms_ and upgrade)
5. Flash normally. Updating process will take more time than always!
6. After upgrade completed, take hima out of crandle, JUST RESET, Do not hard reset!!, and IMMEDIATELY put into crandle!!.
7. Wait until installation message will apear, after reading click Continue and then wait until device get rebooted. 5 minutes is okay to wait.
8. When device rebooted, don't do anything and wait until Debug message will appear, saying Extrom got unblocked, then click on OK.
9. Installation finished, click FINISH! and wait some seconds, after doing all stuff Welcome will appear.
10. Tap on screen, calibrate screen, set time, and enjoy
Link to this test:
http://www.4shared.com/file/ArKkI1Ls/Ext23140test.html
this looks like another hima historic hurdle has been passsed !!
will be trying soon..
sounds cool,real good about being able to use extrom as a part of rom...amazing !!
one small question in step 6. you mention JUST RESET is that just a matter of pressing the reset button and no other button ?
or is it a RESET where you have to press a few buttons at the same time like when you put the hima in bootloader mode ?
keep up the amazing work !!!
Nice aero, to see, that you go, where noone else ever had been before!
aero you are a legend!!
I of course WILL be trying this!
EDIT: There is no usb button there is only com1 and com2 in a drop down menu.
help!!
flyboyovyick said:
aero you are a legend!!
I of course WILL be trying this!
EDIT: There is no usb button there is only com1 and com2 in a drop down menu.
help!!
Click to expand...
Click to collapse
advanced15 said:
will be trying soon..
sounds cool,real good about being able to use extrom as a part of rom...amazing !!
one small question in step 6. you mention JUST RESET is that just a matter of pressing the reset button and no other button ?
or is it a RESET where you have to press a few buttons at the same time like when you put the hima in bootloader mode ?
keep up the amazing work !!!
Click to expand...
Click to collapse
If there is no USB do this:
Disable USB connection in Activesync
Remember to have himalaya in bootloader mode and on USB, lol obvious
If none of this helps, tell me what windows do you use
--
With JUST RESET i mean JUST RESET, just put anything in reset hole and don't press anything
aeroflyluby said:
If there is no USB do this:
Disable USB connection in Activesync
Remember to have himalaya in bootloader mode and on USB, lol obvious
If none of this helps, tell me what windows do you use
--
With JUST RESET i mean JUST RESET, just put anything in reset hole and don't press anything
Click to expand...
Click to collapse
I use windows 7, it shows com1-3
flyboyovyick said:
I use windows 7, it shows com1-3
Click to expand...
Click to collapse
Also did you installed this driver? (Vista = 7)
http://forum.xda-developers.com/showthread.php?t=428469
// This formatting mess is required because some people repartitioned theirs DoCs to remove EXTRom, so I don't really want to know what would happen without it.
When I upgrade,there are : error 112
why can it happens?
what will I do?
thanks
testing it now... will post report after... finger crossed..
done it..working now..
one question.. since memory in main is almost full thus this means i cant no longer install some programs?
main storage memory only now 1.58mb and programs 65.62mb,while storage is 15.96mb....
jonrols said:
done it..working now..
one question.. since memory in main is almost full thus this means i cant no longer install some programs?
main storage memory only now 1.58mb and programs 65.62mb,while storage is 15.96mb....
Click to expand...
Click to collapse
Why not to install on \Storage ?
It's not removeable
When I upgrade,
error 112
can you help me
arifurrokhman said:
When I upgrade,
error 112
can you help me
Click to expand...
Click to collapse
Hi arifurrokham,
If i'm not mistaken you've disabled the allow usb connections in the activesync connection settings before running mtty to show usb. After finished running mtty just enable the allow usb connections before running the upgrade to address error 112. Hope this helps
japo_g said:
Hi arifurrokham,
If i'm not mistaken you've disabled the allow usb connections in the activesync connection settings before running mtty to show usb. After finished running mtty just enable the allow usb connections before running the upgrade to address error 112. Hope this helps
Click to expand...
Click to collapse
This shouldn't because Upgrade tool disables AS automatically.
RUU LOG
08:04:09 Connection with USB
08:05:57 Begin stage 1
08:06:27 CE Erase retry 1
08:07:08 CE Erase retry 2
08:07:48 CE Erase retry 3
himalaya screen : serial
v 1.03
when I update : error 112
AERO...Can you help me...
excellent aeroflyluby !!!
i have run this excellent stuff..
all working good so far....
question ? after looking at the "ms_.nbf" with "er2003edit" i see that most of the actions to make extrom as part of rom is done with this.
with you permission? would it be possible to use this "ms_.nbf" with any "nk.nbf/ROM" so i could have the AMAZING extrom as part of rom on any ROM i like...
is this possible? if i follow the exact same guide but just change the "nk.nbf" ?
aeroflyluby keep up the great work !
advanced15 said:
i have run this excellent stuff..
all working good so far....
question ? after looking at the "ms_.nbf" with "er2003edit" i see that most of the actions to make extrom as part of rom is done with this.
with you permission? would it be possible to use this "ms_.nbf" with any "nk.nbf/ROM" so i could have the AMAZING extrom as part of rom on any ROM i like...
is this possible? if i follow the exact same guide but just change the "nk.nbf" ?
aeroflyluby keep up the great work !
Click to expand...
Click to collapse
Look, extrom have cabs, autorun, some exe's and config. ROM part is to unhide extrom, then run autorun and after installing all, device will reset, clear.exe will unblock extrom to write on it and clear it, after that extrom is mounted as Storage. clear.ink from startup is removed and last operation is to run Welcome screen.
To use it on any rom you need to unhide your extrom and run autorun.
RUU LOG
08:04:09 Connection with USB
08:05:57 Begin stage 1
08:06:27 CE Erase retry 1
08:07:08 CE Erase retry 2
08:07:48 CE Erase retry 3
himalaya screen : serial
v 1.03
when I update : error 112
AERO...Can you help me...please
or somebody....
I hope can use AERO ROM
aeroflyluby said:
Why not to install on \Storage ?
It's not removeable
Click to expand...
Click to collapse
sir aero, yes i can install apps on storage but those apps that needs to be installed on ram cannot be for instance spb mob shell... is there a way o increase ram size like in xda 2s?
thanks again..
jonrols said:
sir aero, yes i can install apps on storage but those apps that needs to be installed on ram cannot be for instance spb mob shell... is there a way o increase ram size like in xda 2s?
thanks again..
Click to expand...
Click to collapse
I can't really understand you. You got 108 free ram and I think you won't get any better

[Q] X1i HardSPL Error 262

Hi,
I cannot flash 0.78.OliNex Hard-SPL on my new X1i: The progress bar stays at 0% until the timeout, then Error 262. I tried everything (no sd-card, no sim, hard reset, compability mode etc.), no avail.
My new X1i has the image version 1.05.932.7 (03/24/09), the bootloader reads:
KOVS110
SPL-0.78.0000
MicroP1-787
MicroP2-707
The type is AAD-380001-BV.
Radio is 1.14.25.55, protocol 52.65.25.34J, extended protocol 1.0.11809.7229.
Software ID is 1213-6439, version R3AA007, user id 1215-3303, user version R15A, content version PA10.
I noticed that the installed WME 6.1 is modified compared to the old X1. In particular, during my first attempt, a WM6.1 warning message with a red boundary popped up, indicating that proceeding could harm the phone (yes/no). I checked yes, and since then, the message does not come up anymore. Probably the ROM is not in Olis compatibility list, so I looked for unsigned HardSPL, but found only the Image Version 1.00.Diamond, so I did not flash it (probably it would brick my X1i). Any idea would be very much welcomed, I want to get rid of WM6.1 and flash WM6.5.3.
Thanks a lot for any hints.
BTW, I've posted this thread alredy in the X1 General forum and realised only now that this forum might be a better choice, sorry for that.
Next try
Hi,
I found the recommendation below and tried, but no avail as well.
Does anyone know an unsigned HardSPL by Oli for the SE X1?
Any help appreciated.
_________________________________________
xidesu
3rd August 2010, 09:33 PM
Default HTC Touch Pro, Fuze HardSPL Error 262 FIX
Alright, this is how i fixed my 262 error after ripping out all my hair for a week.
- Plug your phone into any working usb port (make sure Active sync is up and running)
- Run RaphaelHardSPL-Unsigned_190_1_3.exe and on the first screen pop up, 9 files will be created in the directory you run the .exe from.
- Copy these 9 files to another folder because you will be clicking cancel on the pop up which will in turn erase the 9 files it created.
- Click cancel on the pop up.
- Go to the folder in which you copied these 9 files to.
- Run ROMUpdateUtility.exe and the same screen pop will appear as before.
- Follow the prompts and it should work.
don't flash bootloader-stuff from other devices, never! Oo
try flashing hardspl 0.72 via usb first (the old one), then flash 0.78 as an "update".
Next step, but still not working
Well, I was able to flash APP_SW_X1i_GENERIC_UK_1213-6450_CDF1215-1832_KOV_R1AA017
from the SD card, and I have now SPL0.72.0000 on my X1.
ROM Version:1.02.931.3
Date: 08/29/08
Radio: 1.06.25.29
Protocol: 52.43.25.24U
Software ID: 1213-6450
Version: R1AA017
However, X1_HardSPL still terminates with Error 262 as before. Flashing OliNex's HardSPL via SD card (RUU_Signed.nbh renamed to kovsimg.nbh) does not work either. I still cannot flash my Dynamics GTX 2.3.5 GER ROM.
Any ideas?
BTW, I tried with a desktop and a laptop, both XP SP3 and Active Sync 4.5 on various USB ports. I disabled Security Options via X1_Tweaks. Everything seems to work, only flashing HardSPL still fails.
At least, I am a step back now ;-)
Bingo!
I succeeded. The solution has been:
- Establish an Active Sync connection via USB.
- Copy the file Xperia-SSPL-Manual.exe to the root directory of a FAT32-formatted SD card (no SDHC, an elder one). SSPL-Manual is the basic part of OliNex bootloader.
- Unpack HardSPL by starting it or use RUU_Kovsky files in a directory of the PC hard disk. Make sure that the proper RUU_Signed.nbh file is in this directory (the HardSPL image by Olimex in the version you whish to complete the basic SPL started onthe X1)..
- On the X1, open the file manager and start Xperia-SSPL-Manual.exe by clicking on it. The X1 switches to the boot loader mode indicating HardSPL 0.52 by OliNex.
- On the PC connected to the X1, start ROMUpdateUtility.exe.
In my case, the flashing went very quickly to 100%, and I have now HardSPL0.78OliNex on my X1. Now I can proceed (Task29, image flashing). At least I hope so.
My assumption about the the problems I faced: My X1 had a quite recent firmware which probably blocked any change of the SPL and allowed only generic signed images to be flashed, no cooked ones. Xperia-SSPL-Manual.exe bypasses this lock by applying an OliNex cracked routine, thus allowing to overwrite the SPL. At least I think so.
Done.
My Dynamics GTX 2.3.5 GER ROM is now up and running. THX a lot for the great support of this forum!
Thanks for instructions I have same problem with my X1.
You're welcome.
It has been worth the troubles - the Dynamics ROM is great, and until now, I found no hickups.

Categories

Resources