How do ya make an SD ROM from the .nbf files - MDA II, XDA II, 2060 ROM Development

Hi - i tried to update my xda2 (Himalaya) to the uk o2 rom from the installed uk vodafone rom. but it we bellys up. now all i get is a screen showing me serial v1.06 and then when i dock it onto the cradle it shows usb v1.06 (which i have been tols is the bootloader screen -but i am not sure as the xda1 bootloader screen sayd bootloader on it).
I have tried running the rom update again but have had no luck - the computer does not recognise the device - as it says there is no drivers for it (although i have activesync installed) - but was like that since i bought it - just been using bluetooth to install programs.
When i had a xda1 i had the same problem when changing roms and was able to fix the problem by making an sd image using OS IMAGE TOOL. But this program says 'unsupported file format' when i try to make an os image of the nbf files (nk.nbf, ms_.nbf, Radio_.nbf) to my sdcard.
Does ne one know how to make an os image of the .nbf files so i can put them onto my sd card and try and resolve the problem.
any other ideas welcome and much appreciated
thanks steve

much of what you seem unsure of is describet here
http://wiki.xda-developers.com/index.php?pagename=HimalayaBootloader
http://wiki.xda-developers.com/index.php?pagename=HimalayaHowtoCopyRom
like this
"you can connect to the bootloader, either via a serial cable, and use a terminal program like hyperterm. or via usb, and use mtty. make sure you have disabled the serial or usb connection in activesync, before trying to connect to the bootloader."

'usb port cannot open'
tried mitty just gives me 'usb port cannot open' although i have my xda2 in the cradle and pluged into my usb port. when i connect to the usb port it comes up on my screen - new hardware found - no drivers found - and keep popin up as if the xda2 was found then disapears then found. although i installed the drivers when i installed activesync (have both serial and usb turned off in active sync).
have rom upgrade from o2 and extracted the .nbf files
ms_.nbf
nk.nbf
radio_.nbf
is there a way to put them on an sd card so i can put it in the xda2 and boot from that??

not that i know of
my pc always found some ms driver thingy
when i connected my pda in bootloader mode
not sure if it took it off the internet when it found the device
or if i got it with activesync

i think the problem with my computer recognising the xda2 might be down to the cradle, as from i bought it, i have always had problems charging it - depending on what way it is sittin on the cradle. i have purchased a new usb to xda2 lead and hope this will help with this problem.

Related

XDA2 Restore from failed update

I fried my XDA2 by trying to update the older 60 version on the O2 site to my newer 66 rom version that came installed. I took a back-up before hand on to my SD card. Now that I have a card reader could somebody explain how to do the restore. The PDA, from what I have read, seems to be in bootloader screen - USB ver 1.06 showing, but does not sync with the PC although it shows up in "my computer". Many thanks in anticipation
I had exactly the same problem last week when trying to upgrade to 1.72 (mine is imate which came with 1.66).
the advice i got from the imate support was:
just put the xda in the cradle and plug the usb to the comp, run activesync (use the latest version : 3.71).
although activesync won't recognize the xda, just run the rom update from the computer, after a while you will notice on the device screen that it is being upgraded, it took about 30 minutes.
when finished just pull off the cradle and softreset, and things is normal again.... good luck

Help!!! My 8525 is bricked !!!

Just got my 8525 in the mail. I had the newest rom from cingular.
2.15.502.3 04/09/07 SPL 1.09
I tried to use the "HTC_Hermes_SIM_CID_Unlock_v3a"
I was able to get to the RGB screen where it said:
IPL-1.01
SPL-1.40.olipro
After that the progam said the device not connected.
I remove the battery, the program was able to flash to 28% and then
device not connected error again.
This time I remove the battery, reset, but when the program started
to verify my phone, it said error 260: connection. I tried a few times
but still the same. I am sure it's connected because the word changes
from serial to USB when I plug it in. I even try mtty to get out of the
RGB screen but no luck.
Can anyone help? I am almost going crazy!!!
Thanks.
Looks like it's my USB port that's very unstable.
Use another USB port from my PCI card and it finally recognize
my 8525..
whfew...!!!
I am relieved...

Is UPGRADING TyTn to WM6 using Bluetooth connection possible??

Hello everyone!
Can someone please advice me with my problem. I stopped syncing using the sync cable for over 6 months now since it (the mini usb slot on my HTC tytn) stopped working.
My phone must've fallen the wrong way or something coz i've tried using different cables to sync with my laptop, and my laptop couldnt identify the "device" that was being attached. I originally was able to use the cable before my phone fell, so I was able to configure the bluetooth connection after things got messed up. ( I understand that initial syncing can only be done via cable?)
I was so excited to upgrade to WM6... THANK GOODNESS I decided to "VIEW README" before I install the RUU! It specifically said the upgrade should be done using the cable... please HELP!!
Is there a way to upgrade without the cable, and use the BT connection instead? If not, where can I have my phone mini USB slot fixed?
I wish I hadnt dropped my phone! I cant figure though how the USB slot could have been affected by any type of fall??
I can still charge the phone using the USB slot, so I guess its not TOTALLY damaged.
I'd really really appreciate anybopdy's help! Thank you in advance guys!!
There is no way to flash through BT, but it should be possible to have your device upgrade through the storage card.
Read the wiki for more information
It might not even be the USB port affected through the drop but the CPU itself. In that case you might not even be able to flash via SD!
CPU damage? and flashing from Storage card
I gues it could be possible that my phone CPU was damaged... but I guess the fact that I still get to sync via BT is a good sign it's still ok. But thank you so much for the idea. I actually ran across that thread about flashing from the storage card... but i think I missed the instruction on where to get the "WM6.nbh" file to rename it to " HERMIMG.nbh" .................... the only .nbh file I saw when I opened the "RUU_Hermes_DOPODASIA_WWE_3.54.707.3_6275_1.47.00.10_108_Ship.exe" with Winrar was "SPL.nmh"
When unraring the file you will find another executable called RUU_Inside.exe
Unrar that one too and you will find the image file (nbh)
Thanx Junner and every1!
WOW! I'll try that... OK... I officially love this site! I guess I'll just have to wait for my computer to finish copying the files from my phone's Storage Device... It's been copying for over 2 hours now. BT transfer seems much slower... BTW, I hope it wont matter if my phone's IPL is 1.01 | SPL: 1.04 ..........
SSPL question
regarding the SSPL instruction: according to the readme file: " *** Usage ***
For flashing ROM copy sspl-XXXX.exe (XXXX stands for short device platform name
i.e. TRIN for HTC Trinity) to your device and run it. Standart bootloader prompt should appear on screen, ..."
--- is sspl-HERM compatible with my HTC tytn?
"....check SPL version number: if it ends with ".ds" then
everything is fine...."
------ If my SPL is just 1.04, without the .ds , what should i do then?
(Re)attach usb cable and run firmware update utility.
".....In case if something goes wrong during flashing you should flash your device with ROM accepted by standard bootloader (and have another try if you wish)."
------ what does that last statement mean?

USB loses connection.....cannot upgrade.

Hello, i'm trying to upgrade my device but facing a weird problem. The WMDC works fine and i can sync my device. When i run the RUU, it analyzes the rom and put the device in bootloader mode....
as soon as the device enters the bootloader, the usb loses the connection and says "cannot recognize the device" or "drivers not found" etc....and the RUU gives the error of "cannot connect to the device. make sure...."
I have tried this with the AthenaUnlocker as well as the AthenaWrapper. I'm currently on SPL 1.1 and want to upgrade to 1.2
Please help!
I have the same problem!
I want to install HSPL on my device. I cannot install this via SD Card so i tried it with USB. But after the bootloader the connenction was lost. Many times...
Can somebody tell me how to fix this problem?
Thanks
Edet: My device is a HTC HD2
This might not fit your problem, but ...
... try to connect your device to a PC/laptop with USB 1.1 - with my Ameo I have many "connection loss" problems with USB 2.0 speed, which occure only on heavy (data) load on syncing.
Disabling USB2.0 is possible on some machines within the BIOS.
If you got no PC/laptop with USB1.1 you can disable the USB 2.0 related driver in the Windows Device Manager (it works for me, in general). Therefor open the device manager and select the "View" menu -> devices by connection (or similar). Now search for the Athena entry attached to the listed USB hardware. Disable the "most-upper" USB controller the Athena is attached to.
OK, the last description might be confusing, but try.
Good luck (as this solution fits to your problem, as I am not sure)
What worked for me
junooni said:
Hello, i'm trying to upgrade my device but facing a weird problem. The WMDC works fine and i can sync my device. When i run the RUU, it analyzes the rom and put the device in bootloader mode....
as soon as the device enters the bootloader, the usb loses the connection and says "cannot recognize the device" or "drivers not found" etc....and the RUU gives the error of "cannot connect to the device. make sure...."
I have tried this with the AthenaUnlocker as well as the AthenaWrapper. I'm currently on SPL 1.1 and want to upgrade to 1.2
Please help!
Click to expand...
Click to collapse
I just spent the weekend trying to unlock my Athena and was having the exact same problem... USB would disconnect, errors 202, 267 . I finally was able to flash the Olipro bootloader, but had a hard time unlocking the radio. My device showed no radio under its properties, so I could not tell what radio version I had. Pressing "phone" would not bring the dialup screen. After so much sweat, I had to put it apart, only to find that the radio board connection to the motherboard was improperly seated, thus was having a bad connection. Once the connection was properly seated, the phone booted up to the emergency call screen, notified that there was no SIM card detected and when I looked in the device properties, the radio version was listed!. I then proceeded to unlock and flash the radio and this time the connection was not lost, the process completed without a glitch.
Hope that helps...

for Senior/expert only...HOW TO FLASH HARDSPL ON MY NIKI100? (I SEARCHED FOR WEEKS)

Hi, sorry for capitalized title...
I searched and tested for weeks for a solution in this helpful and very professional forum... but I still haven't found a trick for my problem:
I have a NIKI100 - 20key that ActiveSync doesn't recognize (usb port still charge in Windows environment but no data transmission seems to work).
I tried many PCs with many OS, and now I can say that THIS IS NOT A SOFTWARE PROBLEM (or not?).
So i tried SD flashing, and it works only with signed ROM, so I can't flash WM 6.5
Because of USB issue, I can't flash HardSPL.
MTTY doesn't find the NIKI on COM or USB port.
The question is:
Is there a way to flash HardSPL via SD or is there a signed ROM with WM 6.5??
THANKS A LOT IN ADVANCE!!!
ROM: 2.16.831.3
Radio: 1.65.29.22
NIKI100
SPL-1.22.0000
CPLD-4
Marshalll said:
Hi, sorry for capitalized title...
I searched and tested for weeks for a solution in this helpful and very professional forum... but I still haven't found a trick for my problem:
I have a NIKI100 - 20key that ActiveSync doesn't recognize (usb port still charge in Windows environment but no data transmission seems to work).
I tried many PCs with many OS, and now I can say that THIS IS NOT A SOFTWARE PROBLEM (or not?).
So i tried SD flashing, and it works only with signed ROM, so I can't flash WM 6.5
Because of USB issue, I can't flash HardSPL.
MTTY doesn't find the NIKI on COM or USB port.
The question is:
Is there a way to flash HardSPL via SD or is there a signed ROM with WM 6.5??
THANKS A LOT IN ADVANCE!!!
ROM: 2.16.831.3
Radio: 1.65.29.22
NIKI100
SPL-1.22.0000
CPLD-4
Click to expand...
Click to collapse
Can you tell me what happens when you connect your device with your computer, when it is already in bootloadermode.
You can turn the phone in bootloadermode to turn your device off and press then on/off button and camera button on the same time, and keep them pressed until bootloader appears.
If I'm correct you will see Serial in the white block, just let me know what you see in the white block when you connect the phone with the computer, if I'm correct Serial will change in Usb, if not just let me know.
Greetz,
Tnx for reply...
I see USB when I connect the cable, Serial when I disconnect the cable.
I'm searching for a SD-card-method for flashing HardSPL: is this a good idea or I'm just wondering ?
Marshalll said:
Tnx for reply...
I see USB when I connect the cable, Serial when I disconnect the cable.
I'm searching for a SD-card-method for flashing HardSPL: is this a good idea or I'm just wondering ?
Click to expand...
Click to collapse
Ok, can you tell me if you're device has a simlock ?
Greetz,
Hi.
No simlock.
Tnx.
Marshalll said:
Hi.
No simlock.
Tnx.
Click to expand...
Click to collapse
Ok thanks, I'll do some searching and see if we can fix it.
Regards,
Ok, if I where in your situation I should try it this way, just be aware that I can not test it because I don't have such a problem, and you can brick your device if it went wrong.
1. Copy sspl-1.16-nike.exe to your sd-card
2. Copy sspl-1.16-nike.exe from your sd-card to your device
3. Turn phone off and remove sim and sd-card
4. Turn phone on and connect device to your computer
5. Run sspl-1.16-nike.exe on your phone
6. Wait until usb appears in your device
7. Unplug and replug the usb cable
8. Now flash the HardSPL 1.22
If you can run the HardSPL you should be able to flash a wm 6.5 rom.
Rataplan said:
Ok, if I where in your situation I should try it this way, just be aware that I can not test it because I don't have such a problem, and you can brick your device if it went wrong.
1. Copy sspl-1.16-nike.exe to your sd-card
2. Copy sspl-1.16-nike.exe from your sd-card to your device
3. Turn phone off and remove sim and sd-card
4. Turn phone on and connect device to your computer
5. Run sspl-1.16-nike.exe on your phone
6. Wait until usb appears in your device
7. Unplug and replug the usb cable
8. Now flash the HardSPL 1.22
If you can run the HardSPL you should be able to flash a wm 6.5 rom.
Click to expand...
Click to collapse
All right from 1. to 7. but when I run flashin it shows error code 260 (unable to connect).
Is there a way to run SPL "JUMP" and then flash HardSPL via SD card? I think it's the only way to flash HardSPL
Rataplan is the expert one on this area,
but wath is your operating system? Seven or XP?
Because i just was able to hardspl on XP, all other things I was able to do on Seven.
Marshalll said:
All right from 1. to 7. but when I run flashin it shows error code 260 (unable to connect).
Is there a way to run SPL "JUMP" and then flash HardSPL via SD card? I think it's the only way to flash HardSPL
Click to expand...
Click to collapse
Did you try to run the HardSPL 1.22 from the bootloader ?
Let me explain a little bit better, did you connect your device with your computer when your device is in bootloadermode and then run the HardSPL 1.22
If this fails, you can rename your nbh-file, hardspl-1.22-nike-shipped.nbh into nikeimg.nbh, copy nikeimg.nbh into the root of your sd-card and turn your device on while pressing the on/off button and the camerabutton on the same time and follow the instructions on the screen.
Succes,
Rataplan said:
Did you try to run the HardSPL 1.22 from the bootloader ?
Let me explain a little bit better, did you connect your device with your computer when your device is in bootloadermode and then run the HardSPL 1.22
If this fails, you can rename your nbh-file, hardspl-1.22-nike-shipped.nbh into nikeimg.nbh, copy nikeimg.nbh into the root of your sd-card and turn your device on while pressing the on/off button and the camerabutton on the same time and follow the instructions on the screen.
Succes,
Click to expand...
Click to collapse
Yes, I tried all of this method...The PC can't recognize the niki in bootloader mode.
When I put HardSPL on a tested sd-card (renamed NIKEIMG.nbh), I'm stuck in white screen with "Loading...".
I found some method for flashing HardSPL via sd-card (for Kaiser: http://forum.xda-developers.com/showthread.php?t=433835):
is there a SSPL Jump for Niki that run from sd (as with Kaiser sd-method)?
BTW, I think this is the right way... I'm trying and searching!
For Openview:
I tried with many PCs with XP Pro and 7. The niki usb port seems to be broken (only charges, but no data connection).
Nothing seems to work. If anyone has somethig for flash SSPL and HardSPL from SD, please post!!!
Any other ideas???
I think we tried everything but unfortunally the answer is that it isn't possible to flash the hardspl via sd, the only person you can ask is cmonex, she is the only one who can set this straight.
Here is her User cp but she is a very busy lady.
If you fix it, plse post it in this thread it can help others.
Goodluck buddy
Ok I'll try to contact mrs. cmonex. Of course, I'll post any solution (hope to find one... ).
Tnx for all!
SOLVED!
I solved the issue!! It was only a hardware problem with HTC ExtUSB port!!!
I cleared the pin and resoldered the port on motherboard. Then I flashed HardSPL via standard method and now I can flash anything form sd-card!!
Thanks to all.
Mr. Rataplan, now we can close this post!
Thanks!!
Great Marshalll, I'll ask Electroz to close this thread.

Categories

Resources