hey...please help...something went wrong on my first flash - HTC Vox

hello all,
after going through many files and threads here, i decided to update my rom to "Windows Mobile 6.1 for ported from Moto Q by Dr. Martin Gonzo"... (After removing the sd card...) First, i run the sda_application unlock...got a message "successfully unlocked. reboot sda" on my pc...i rebooted my vox. Then activesync connected again..Then i run "uspl_116_jockyw.bat"... it asked several que...like beta release, wish to continue or not...den remove sd card...etc...i'd already removed the card well before, so i acceptd all the prompts...and as per the readme file, i shud saw a penguin..waited for that...inbetween, on my vox...it prompted for two files "haret"..etc..i pressed yes on vox...din see any changes on vox for dat....and finally i saw a penguin on top left corner of my vox...some scripts were runnin in the middle...so small it was, couldnt read...i waited for screen to turn black/ bright... but wat i see was a mixed screen of penguin, some protion black(top and bottom black bars) and in between d usual green wm6 homescreen...i felt something went wrong..but tried to check by running "ROMUpdateUtility.exe"...wen i run it, vox automatically rebooted...and i got an error msg from ruu, could not connect to the vox..i started ruu again, (vox rebooted and active sync connected again)...ruu showed me current image version....and i pressed UPDATE button...i saw RGB color on my vox, and a usb connection established btw my vox n pc...then suddenly it showed 100% wid an error msg...on pc....(my vox automatically rebooted) the error message on pc was "image file corrupted"...and after that my vox not gettin connected to activesync.....
The phone is workin fine i tink, i can see the home screen n all...
where i went wrong...??
i wished sooooo much to see wm6.1.... but ......

Hello Rohit
This is how I do.Follow Instructions.
1) Connect your mobile with pc check whether its connected with active sync or not.
2) Use sda_application unlock.exe to unloc the mobile ..It will ask you to reboot.Dont reboot .Keep it as it is.
3)Then open uspl_116_jockyw.bat .Run it as administrator and it will as you to follow the instructions.just follow that .After all instructions the bat file will vanish.The screen of your mobile goes black.
4) Run Flash.exe from the ROM you downloaded.Wait for 10 mnts then it will reboot atomatically.
5) after reboot dont do anything ..Have some patience .it will do "cold reboot".It will take 5 mnts.
After this it will ask you to press OK to reboot .
Thats it .Enjoy Now.
Thanks
Yogusmilu

Related

ROM in XDA mini corrupted--HELP!!

i bought a XDA mini from ebay.when i received the device it is of german made and i am an indian.when i was trying to upgrade my ROM version,i got an error and failed to upgrade, since then it is not turning on .i tried to soft reset ,hard reset but it is fruitless.later i came to know that the software with which i tried to upgrade was for 'XDA ll'.how can i reinstall my original ROM now.moreover i noticed that something "USB v1.02" is being displayed when i connect it to the PC with USB cable and "SERIAL v1.02" when i disconnect it from the PC.
Can any one help me i have used my phone 1 month back.
Your device is now stuck in the bootloader & that's no problem. Just visit the wiki & go to the magician section. Explore it, especially the part about rom upgrading with exe method & download the 1.13WWE rom with the link on the magician main page (@ the wiki).
Then connect your magician (mini) to the usb & start the exe file (shipped-rom) you've downloaded. Now it should finish, if an error 120 comes up, use maupgradeut_noid.exe like described in the howto.
Your magician should be cured after this.
Regards, M
sir ,
i am new to these,I have been searching for the software of upgrade Would you please give me the exact link to download.
http://wiki.xda-developers.com/index.php?pagename=HTC_Magician
thank you sir ,It worked would you please tell mehow to close an apllication without using "Running programes" like media player etc
taskmanager
There are lots of taskmanagers to do this like spb pocket plus, mbutton... I'am using VJOkButt assigned to a hardwarekey by aeb button plus.
M

O2 XDA mini needs help!!!

Hi you guys!
Recently, My O2 have problems with the screen. When I touched on one area of the screen, it affected the area next to it or somewhere else. So, I decided to upgraded my O2 to another Rom, which was "WWE_11300_550_11200" which I had got from ftp://xda-developers.com/roms/magicians/. And it worked pretty well for 2 days or so. After that, that kind of screen problem returned. Then, I downloaded another Rom called "o2asia_11100_922_11100_ship" from our FTP server and upgraded my device with that Rom. The upgrade progress ended up with error of upgrading extended rom at 6%. Then, I tried again. But unfortunately I always was reported that there was 101 error which was "connection error" or 202 error which was "cannot receive data from device" and the screen only indicated "USB" at the top and "V1.02" at the bottom of it. I tried everything but the results were the same. I have no idea what was going on with my O2. Please you guys give me some advice on my problem and show me how to make it work. I really need your help right now. Thank you guys!
Hi,
Read this http://forum.xda-developers.com/viewtopic.php?t=46628 & try to run your update again. Maybe it's a good idea to reboot your pc first & don't worry when there's nothing displayed in the from rom fields.
M
Thanks oltp for those informations. I tried to restart the PC and run the device software update utilities but I got report of error 202 "cannot get device data". Either the screen indicating USB and V1.02 with the LED on red and the screen indicating USB and V1.02 with the LED off are the same result. I don't know what to do now. Anyone has experienced this kind of problem, please give me a guild to solve it. I look forward to hearing from you guys. Thanks in advance!
Have you tried dumping your rom on a sd-card? Maybe you still can flash it that way.
M
oltp said:
Have you tried dumping your rom on a sd-card? Maybe you still can flash it that way.
M
Click to expand...
Click to collapse
No, I haven't. In fact, I have no idea how to do it. Could you please give me more detail about how to dump my rom on a sd-card, OLTP? Since I have nothing to lose , I'll give it a try.
Thanks in advance!
Hi,
This is my standard description for dumping a rom on sd.
Backup is fairly simple:
- get ntrw.exe from the ftp ftp://xda:[email protected]/Magician/Tools/Backup_tools/
- get romupdate from the same location
- get a SD-card > 64MB
- make backup of everything you want to keep from your magician & SD-card. everything will be wiped!!
- fully charge your magician
- uncheck usb connection in Act.sync on your PC
- put your magician in Bootloader (camera & power & soft-reset at the same time for a few seconds) wait till screen fades & reads 'serial v1.0x'. Screen is very dark since backlight is of.
- connect usb, now the screen reads 'usb v1.0x'
- start romupgrade on your pc
- pick the magician connection in the listbox, wces something I belief
- now a screen pops up
- type d2s in this screen
- follow progress on pc & magician
- wait till checksum finishes
- get SD from the magician & put it into a cardreader. DON'T FORMAT!!!
- put ntrw in C:\
- start a command window
- type on commandline: ntrw read myrom.nb1 [sd driveletter]:
- follow progress
- error at the end is normal
- finished
- reset your device & restore backup
- Playtime
Regards, M

Treo Bricked?

I am unsure if my treo 750 is bricked or not (its been in a drawer for a while since my wife failed an update and couldn't load it anymore). I can connect it to my computer and load activesync and browse the device but i cannot use the device. The screen always loads.
If i do a master reset by pressing power and reset i can go through the initial setup (time and screen) but when i click finish the screen just freezes there, it'll go off and i can press the power to turn it back on but i can't run any aps or select anything.
I tried just about everything to load the at&t 2.25 again, tried sd method as well as activsync. SD just stays at that loading screen where it says rom ok but the progress never moves from 0% left it there for an hour. The activesync method usually loses connection or sometimes i get the error "image file corrupted" i've tried re downloading the rom also tried on 2 different xp computers and then finally resort was a vista hoping maybe there is some good in vista but nope.
When i browse the device from windows i can see all the files on the device maybe some system files on the treo are missing not allowing it to complete the load?
Any help with this would be highly appreciated since me being not so bright decieded to jump into the swimming pool with my brand new moto q9h and now i am phoneless unless i can get this treo to work.
I have tried to do the palm repair and it doesn't work either.
I've also tried to use the CheetahUnlocker it says image file corrupted after 7% but it does do enough to get my device to load up out of the bootloader and into the setup procedures but no further it won't load any further after i select finish. I am able to press keys to turn the backlight back and am able to browse the device via pc though the device is frozen.
1. download this: http://palmone.r3h.net/downloads.palm.com/Treo750_2_25_ATT_EN_SDUpdater.zip and this: http://forum.xda-developers.com/showpost.php?p=1565080&postcount=1
2. Extract the contents of each ZIP to a new folder
3. Rename cheeimg.nbh from the updater extract to RUU_signed.nbh
4. Place the file KaiserCustomRUU.exe in the same folder with the file RUU_signed.nbh
5. Connect your device to USB and ensure you get active sync connection and can browse the device.
6. Execute KaiserCustomRUU.exe and follow the prompts.
Hope this helps...
thanks for the quick response i actually haven't tried renaming to signed but i have tried the kaisercustomromruu i will try renaming and post results tonight forgot my laptop case in the wifes car.
Tried that method still no success, the progress bar doesn't move from 0% and after about 3 minutes it says the communication error [262].
The bootloader starts up showing ipl 0.20 and spl 0.24.0000 if that means anything.
It seems like half the software is on the phone and the other half is missing and not allowing the phone to be functional after the initial setup procedures (time date and screen).
Is there a way to force a rom to install via SD card, whenever i try the SD method it doesn't progress from 0% as well.
I've actually found out the system files are not all on the pda the windows folder is only 2 mb it would be great if a pda could work like that but we know they don't. I have a backup of another treo 750 but can't transfer files directly since files are in use when i am browsing the pda i was wondering if there is a utility like mtty we can use to send files to the treo?
Or maybe if i can just copy a file directly on to the device and the file can do the update direct instead of the sd method since sd method isn't working either?
When i attempt a SD card update i get the following
SPLASH1 - OK
bOOTLOADER - OK
GSM -
MICROP -
EXTROM -
OS -
It pretty much hangs for the last 4 items, won't progress any further than bootloader OK.
Any ideas? maybe my sd reader isn't working properly? i've tried 3 different cards.
erandhawa said:
When i attempt a SD card update i get the following
SPLASH1 - OK
bOOTLOADER - OK
GSM -
MICROP -
EXTROM -
OS -
It pretty much hangs for the last 4 items, won't progress any further than bootloader OK.
Any ideas? maybe my sd reader isn't working properly? i've tried 3 different cards.
Click to expand...
Click to collapse
Use MTTY and do a "Task 2a" then flash any ROM you want.
yup tried that one as well for it runs the commands correctly but when i try to install the new rom the progress doesn't move i've left it along for an hour or so and no progress and when i attempt the sd method that fails as well. This ones left me stumped, i had a wizard and that thing was easy to fix if anything got corrupted.
This is what worked for me. I had the Tri-color and could not load anything via USB or SD. I used Mtty ver 1.42 while the boot screen was up on my Treo750. make sure active sync is disabled. The only settings to change are USB and Flow Control(RTC/CTS)
The commands I used came from
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
I used almost every code on the screen but these are the ones that worked for me
Set 16 0
set 14 0
set 32
set 28 55a
erase
checkimage <<< If you get bad blocks do the next cmd
task 2a <<< I think this is what really help me out
task 8
The screen went black some say white. I shut down Mtty unplugged the cable and did the SD cheetah.nbh install and it worked. I have tried it twice and it has worked. Yes I screwed my phone twice trying to use a Dutty rom.
bluntz3000 said:
This is what worked for me. I had the Tri-color and could not load anything via USB or SD. I used Mtty ver 1.42 while the boot screen was up on my Treo750. make sure active sync is disabled. The only settings to change are USB and Flow Control(RTC/CTS)
The commands I used came from
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
I used almost every code on the screen but these are the ones that worked for me
Set 16 0
set 14 0
set 32
set 28 55a
erase
checkimage <<< If you get bad blocks do the next cmd
task 2a <<< I think this is what really help me out
task 8
The screen went black some say white. I shut down Mtty unplugged the cable and did the SD cheetah.nbh install and it worked. I have tried it twice and it has worked. Yes I screwed my phone twice trying to use a Dutty rom.
Click to expand...
Click to collapse
Tried all these and does not work for me too, in the same situation after all the commands run okay in Mtty. when rebooted it hangs on the windows mobile screen, and when tried with SD flashing, it hangs
SPLASH1 - OK
bOOTLOADER - OK
GSM -
MICROP -
EXTROM -
OS -
It pretty much hangs for the last 4 items, won't progress any further than bootloader OK.
Please help

RhodiumW Hard-SPL Release

preface for the people not reading ... some quick answers:
- our page on this Hard-SPL is always here: http://rhodiumw.htc-unlocks.com/hard-spl.php
- license: you will just have to run the program on the PC with phone connected, normally you will not notice anything about the licensing, it is totally free for personal use!
- if you need help with license issues (when it says you already unlocked a device), you can send your message at: http://support.htc-unlocks.com
[SIZE=+2]Hard-SPL Release Time!!!! [/SIZE]
[SIZE=+2]NOTE: This is NOT a SIM unlocker - it also doesn't unlock Security for other radios. if you need that, GO HERE[/SIZE]
[SIZE=+2]NOW UPDATED -> if you already installed HardSPL, you will not need this update. but if you are going to HardSPL only now, it applies to you (package will lead you to update link anyway).[/SIZE]
Preface: okay, it was released only this weekend! but trust me the wait was worth it as it works really great and smooth now!
Licensing information: it's like with previous Hard-SPL unlockers - every user gets one free use of the Hard-SPL, further use is subject to paying a small amount per device.
however, if you are a private user, you can have other uses free on request if needed, such as using it on a replacement device.
the license is valid forever and all this works as transparently as possible, so for normal users nothing is noticable; while businesses who need to unlock more devices than that, can use the link inside the program to send payment or contact cmonex or Olipro if you want to discuss bulk unlocking.
contact info is: via support link at our site
IMPORTANT: please do not use this contact info for asking help for problems unrelated to licensing unless you are a paying customer. other messages will not be answered - instead you can use this thread to post about your issues!!!
Preparations:
0) this package is for Rhodium CDMA-GSM worldphone version only (CDMA Touch Pro 2, not the original Touch Pro) devices. only RHOD400, RHOD500 modelids are accepted. this Hard-SPL supports WM6.5.
1) if you have Vista / Windows 7, WMDC update to 6.1 (or whatever is latest) is recommended.
Instructions: read this if unsure how to install Hard-SPL... if you are an experienced user then you'll probably not need to read most of this but if you are unsure or run into an issue, then you should read the following!
Steps:
1) download newest RhodiumW Hard-SPL package and extract this to an empty folder.
2) you must Have Phone Synced with PC in Windows Mobile!!! the device needs to be connected to Activesync or WMDC via USB cable. and it must not be in Flight/Airplane mode (i.e. the phone part should be on).
3) internet access is required as the program checks online for updates and for the license.
4) run Rhodium-HardSPL.exe on your PC, make sure it's launched from a local drive (not through network drive, etc.). running it on XP requires Admin logon, and Vista/Windows 7 will automatically prompt to allow it to run in Admin mode, so allow it please.
important: if you get an antivirus warning, please ignore it, it contains no harmful code (just used a packer to compress it). if you encounter DEP errors, then add it to the exception list in DEP settings.
5) follow steps as prompted in the Hard-SPL program. if this is the first run of Hard-SPL on a device after hard reset, you must select Automatic flash mode (the first button in Welcome screen).
notes: you should usually go for Automatic flash mode; the Manual flash option is only to be used as noted below - 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 please follow the instructions included in the error text. if no specific instruction is shown, then ask for help in the forums, but this should not ever occur (as this means a really fatal error occurred).
at this point the device did hopefully went to a black screen. this is the SSPL version, which is temporary. then RUU (Rom Update Utility) will instantly launch.
9) some notes: when RUU says it will perform a hard reset and cause data loss, do not worry, it is not going to do this. 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.
11) to confirm you got it installed, go into bootloader mode (tricolour screen!) and verify the screen shows 1.00.OliNex, which is the current Hard-SPL version.
More Notes:
NOTE 1: you will not see the SPL version during normal boot, that is the OS version, not SPL!
to enter SPL to check version, you need the following key combination: Power Button + Volume Down + Reset Button. means, do a soft reset while holding the "volume down" key and power key on the side of the device. hold these keys until you see a special tricolour screen which is the bootloader mode.
NOTE 2: this is unsigned Hard-SPL. 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, so if someone needs to revert to stock SPL for warranty reasons, a stock SPL downgrade package is posted on our site. use this relocker *only* if you need to return the phone for warranty, and only use it as last step - after reflashing stock OS and radio. see steps in the next post about how to reflash stock SPL.
NOTE 3: anyone having USB connection problems with the device after it already entered SSPL mode, please copy SSPL-Manual-Rhodium.exe from SSPL-Manual-RhodiumW.zip (available on our site), copy it to the device and run it. then once the screen has gone black, run the Hard-SPL package on the PC and you must select Manual flash option. *important*: make sure that the USB cable is plugged in and device is synced to Windows Mobile even if doing manual method.
NOTE 4: 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 will flash to make SSPL more secure. if you want to flash some other rom, then use shipped RUU or a customRUU if you need to flash cooked ROMs.
NOTE 5: supported OS versions: both 32-bit and 64-bit XP, Vista, Windows 7RC and later. Windows 2000 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.
Troubleshooting: and Step by Step on reflashing stock SPL: are in next post below!
Credits:
first, "OliNex" is a team which means: cmonex + Olipro
Olipro -> concept of EXE program that runs on the PC, Hard-SPL concept, server-side license code and maintaining the licenses.
cmonex -> HSPL package on PC, SSPL loader for windows mobile and SSPL binary. Hard-SPL binary. (SSPL loader: partially based on haret and old pof&Olipro jumpspl code),
[SIZE=+3]Donations are always appreciated, the Hard-SPL program will provide you with a link at the end of the process to make it easier. any little helps!!! Thank you![/SIZE]
and now enjoy!
-continued from first post-
Manual SSPL download: (added soon)
Troubleshooting:
firstly:
- read the instructions above.
- read the instructions above.
- read the instructions above.
nothing happens on the device, does not enter black screen mode:
- anyone having problems with the device crashing instead of entering SSPL, make sure you've used Automatic flash mode before to put the device in SSPL (if you hard-reset your device, you have to repeat Automatic flash mode at least once).
- please make sure you watch the device screen if it asks about running files (it probably won't, I made sure of that, but just in case, check, for example it can warn about model incompatibility).
- also you can try unticking advanced usb/network functionality in settings on the device. exact location of this will probably be: start menu / settings / connections / usbtopc applet.
general usb connection error problems:
- if you get connection error in RUU after the device goes to black SSPL screen: make sure device was still synced via USB to the PC at the point of it entering SSPL (the black screen) and do not try replugging please, that will probably just crash SSPL.
- it will take a few seconds for the RUU to detect the device, but do not worry, as soon as the USB connection is established in SSPL, RUU will see device. if not (happens very rarely), wait for RUU to time out (or wait a few minutes). then remove back cover, reset, it will boot OS again, then you can retry unlocking process.
- anyone having problems with the device entering SSPL without functional USB port ("ERROR 260 CONNECTION" RUU error), you can get SSPL-Manual-Rhodium.exe from attachment in this post, copy it to the *device* itself and run it. then once the screen is showing black, run the Hard-SPL package on the PC and select Manual flash option. please do not use Manual flash option for any other purposes
- try a different USB port
- try different USB cable
- do not touch USB cable during the process especially if it is already a bit dodgy
- also do not use USB hub
- you can also try rebooting your PC
- and you can try using another PC.
- another reason for USB connection error: if your PC takes too long to load the drivers (if your device is in bootloader for the first time it needs to do that), then if RUU times out, but device is still in black screen, just leave it there and re-run the Hard-SPL package when driver installation finishes - you must use Manual Flash option in such a case. I recommend to wait for Windows to take its time searching for the USB drivers, then click Next in RUU only when they are installed.
- finally, you can try disabling antivirus or firewall programs on the PC.
ModelID checking: if SSPL loader says it's for a different model or device, please make sure you are using the correct HardSPL package. currently this SSPL accepts only RHOD400, RHOD500 modelids i.e. the CDMA-GSM worldphone version, but if we get notified of another compatible RhodiumW version, we will instantly modify it to allow those models. check modelid by entering SPL tricolour screen manually and note what it says (RHOD400, RHOD500, or something else). note: RHOD1xx, 2xx, 3xx are not going to be compatible at all!
other issues:
- if device reports that Enterbootloader.exe fails to run (says missing component or corrupt signature or similar), try a hard reset.
- if device reboots instead of going to SSPL screen (black), which is very unlikely to happen, then contact us by PM to cmonex. do not PM OliNex user, that is not monitored frequently (and PM's to it are disabled now anyway).
- if none of the above help, read thread for further suggestions, if still nothing, make a post in thread describing all details about the exact situation.
how to reflash Stock/Shipped SPL: - STEP BY STEP - FOR WARRANTY REASONS ONLY!
0. please make sure you already flashed stock ROM and radio, because stock SPL flash is *always* the last step before sending the device in.
1. download the Relocker by clicking here, extract the zip and run the EXE on your PC
2. if you wish to replace RUU_Signed.NBH that got extracted, feel free to do so, but not necessary (this Hard-SPL will only allow overwrite with a SPL made by us). the included one is the 0.63.0000 stock SPL. 3. flash
4. verify if it flashed by checking version in tricolour screen, it should say 0.63.0000, not 1.00.OliNex.
About UPDATES:
-new release coming soon, fixes a specific problem for a small group of people-
-more troubleshooting tips soon-
Consider yourself... sticky
Thank you Olinex. Great WORK
thank you! can someone please tell me what this does for my vzw tp2? thank you so much .
buggs1a said:
thank you! can someone please tell me what this does for my vzw tp2? thank you so much .
Click to expand...
Click to collapse
In a nutshell, this basically will allow you to flash custom made roms and other assorted customizations.
Hey, thank you.
Does using this and then not putting a custom rom on it right away do anything bad? Like waiting for a 6.5.1 rom or something. Sorry if this isn't the right place. Forgive me please.
Crashes on vista x64 sp2 home premium. as soon as I click to open the hard spl exe it crashes.
You can wait as long as you want to flash another rom, custom or carrier. So no worries in holding off.
Thanks so much for answering.
Here's something.
Crashes on vista x64 sp2 home premium. as soon as I click to open the hard spl exe it crashes.
I just tried. I don't get it.
My mcafee doesn't have a trust app add feature that i can see so i turned off real time scanning to extract the file and then run it. Then the hard spl crashes when i try to run it. I hit auto flash and immediately it crashes.
What specific error message(s) are you getting?
Nothing specific. It just crashes and the windows app crash pops up. That's all that I can remember. Should I try again and look for something specific?
Also I would like to say that I connected the phone to my pc via usb cable and that's it. On phone opened the disk mode or active sync selection but I didn't touch anything in time then it disappeared. The phone showed up as a hard drive in explorer. I didn't do anything else when trying to run the hard-spl exe. Should I have?
Thanks a million.
You need to make sure you're connected to your computer and sync up with ActiveSync. Once that's all connected properly, then you can run hspl.
but how do i do that? i noticed just now i reconnected phone and active sync was selected on the phone, but nothing comes up on windows vista except the auto run and it says synch with media player or open to view files or do nothing.
Oh, Vista. Right. You'll need to use Windows Mobile Device Center then. Install that, reboot, then sync up with that (it's ActiveSync's replacment for Vista and Windows 7). Then you should be able to run hspl fine.
That you very much Oli, and to all the people who worked so hard on this! I just put it on my Verizon Touch Pro 2 and it went like a snap, but what software from you doesn't A nice donation is coming yer way me matey!
thanks. that did it.
i got to the part where it said make sure the battery has 50% or more. i said cancel and now my phone is off and won't come on. I disconnected usb and tried to turn it on and nothing happens. reconnected phone and tried to do this again and it told me i need to active synch again. but i can't turn on phone right now. I don't know what to do now.
Have you tried taking out the battery of the phone, reinserting it and turning it back on?
trying now except i dont know how to open it. ok my bad. had to remove stylus. it's on now.
Ok sweet. It rebooted the phone. Success I suppose. Now to find a rom.... But then I dunno what to look for. hmm...
lol
buggs1a said:
trying now except i dont know how to open it. ok my bad. had to remove stylus. it's on now.
Ok sweet. It rebooted the phone. Success I suppose. Now to find a rom.... But then I dunno what to look for. hmm...
lol
Click to expand...
Click to collapse
Glad you got it figured out. Have fun finding a good rom that suits you.
edit: since we don't really have much of a CDMA TP2 selection just yet, I'd recommend checking here. He makes a great ROM. Just be sure not to discuss ROMs in this thread.
I posted this at PPCGeeks also, but here is a problem I am having while trying to unlock in Windows 7 x64 using WMDC.
1. Ran the .exe
2. Screen pops up "Preparing to flash, press ok to wait. I press ok.
3. The screen goes black (like it's supposed to), Active Sync DISCONNECTS, and a box pops up: "Welcome to the ROM update utility...". I check the box "I understand the caution..." and click next.
4. The next box pops up "Follow the instructions..." and I check the box "I completed the steps..."
5. A box pops up: "Verifying the information on your PDA phone...please wait..."
6. About 30 seconds go by, and an error box pops up: Error [260]: Connection...
7. The screen remains black and the phone non-functional. I have to soft-reset the device at this point.
When I soft-reset in #7 above, the computer dink-donks like when you disconnect the UBS cable, so there's still some sort of connection the PC is recognizing. I tried a second time after installing the enablerapinew.cab (using auto mode) and got the exact same errors.
Any thoughts?

[SOLVED] - [Q] Fujitsu Simens loox N560 died after bad firmware

hi.
I'v got loox n560 that was upgraded to WM6.1-6.5 servel times without any problem.
the last time i did update, i did it accidentally with a bad firmware file(uncompleted download).since then, the device wont boot(just a white screen).and the pc wont recognize it.
any way to save it? or i made myself a nice paper weight?
thanks.
I think there was a way to put the N560 in bootloader mode by pushing some keys and soft-reset hole manually (the "monkey grip" it was called or something similar...) and with the file of the rom to be flashed in a SD card... perhaps you can google for information on this ancient -and more unsure that the cable one- flashing mode. Worth to try it better than have a paperweight...
Good luck!
I give you more information (shame that FIRSTLOOX information is not there anymore)
For manual bootloader mode: press On-Off button + left side button (voice recording) + stylus soft reset (for some seconds). Keep pressed On-Off and recording untill the dolphins appear.
I can't find references to flash from SD card. Anyway, for incomplete flashing, Newplowe gives this procedure:
"You should close process "wcescomm.exe" on PC in task manager. Then hold button record, power and puch reset after that you will come in boot loader. Run the program mtty.1.42 and select usb connect. If You will see the any error just start again mtty. Put command l c:\os_213u.nbf (You should put correct flash file in c:\ or use correct path to os_213u.nbf, l - like L but small). When it will done You should start PocketLOOX5xxFlashTool.exe and flash you PDA."
I got this reference from "http://forum.xda-developers.com/showthread.php?t=429148&highlight=flash+n560+card".
Good luck anyway.
this is very interesting...
i was able to put the device into boot loader mode and ran the command "L c:\os_213u.nbf" ("l" didnt work, but L did).
it did something to the device, a progress bar till the end of the screen.but the device didnt reboot.when i try to run POCKETFLASH program it couldnt connect to the device.
i runing windows 7, so i guess it the problem(ACTIVE SYNC is a XP PROGRAM).
i'll try installing XP on another computer and try this again.
thansks.
almost...
i have installed Windows XP just for this, and everything seems to go well, i connect with MTTY, put the l c:\os_213u.nbf command and the device respond.
the next stage i to flash with PocketLOOXN560FlashTool.
when i start it, i receive connection error, and then i go to recovery mode.the program try to communicate with the device, but i get at the end error that the ROM language is different than the language on the device.it says "(ENGLISH)" and there are also empty
()
Click to expand...
Click to collapse
at the end.
i doubled checked this with the original WM5 English rom, and its the same.
is there a way to change the language with MTTY?
any other ideas? its a shame to stop now after i can get a response from the device...
thanks.
The only idea I have is to check if after the failed flashing your N560 is still an "english" one. Perhaps the defective rom has changed the language of your device to something else...
If your device respond to communication with the XP computer, perhaps you could make a rom dump (in newplowe's page you can got tools for doing that) and check in the dump file with an hex editor which language actually has. You can always check newplowe's blog and forum (with google translator ), or ask him
Sorry i didnt post an update.
i have fixed the rom language.it had a gibberish mark at the end of the ENGLISH, after i have fixed that, .the device was flashed correctly and its working!
thanks for thelp guys

Categories

Resources