i have a xda orbit and i am trying to flash it with o2 premium full rom. i have done things like removing the microsd and sim and have ran the cid unlocking utility which came in the package. it goes to 100 and the phone goes black and with a linux cartoon and goes white then. afterwards the update utility runs after accepting everthing it looks for the settings and give me an error saying check the cradle the error is 270. if i enable the active sync manually it installs and goes to 3% giving me an error 260 image corrupt pls help!
Have you tried flashing any other ROMs and have they worked OK?
yup all of them are doing the samething. but i noticed 2 files in the root of the phone memory and i found similar files in the rom package so i copied those two in the root. and then the romupdate utility dected my phone in the bootloader and it worked. i am not sure this way the reason i could be something else not sure.
Related
Dear Fellow Forum Members,
Followed instructions as per Xda_II_Upgrade.pdf, during installation got to a section where I got a message saying that the current rom is being erased a task bar was displayed which increase's in percentage as the job goes through. However the job was still at 0% completion when an error message was displayed saying the job had failed and the device needed to be undocked and a soft reset performed and then re-docked and to restart the process again. After performing the undocking of the device and software reset I get a message on the screen serial V1.0.1 when connected to the cradle the message changes to USB 1.01 and I cannot do anything else the unit does not boot into pocketpc, as you can imagine this is very frustrating as I depend on my xda2 to receive and make phone calls I would be very grateful any members know of any way to get around this problem. I must say I am a bit concerned a try and tested xda2 update has led to this problem.
Just run the update .exe file again with the XDA docked and it should just install the update again. It happened to my mate on Saturday with his XDA II and he just ran the program again.
Dave,
done as you said and all went thru fine you are a star thanks mate.
No problems it's good as a newbie to be able to actually help people.
upgrade xda2 rom ver 172187 dead os--connection error
i was trying to upgrde the rom from o2 website when error occured at stage 19% completed asking me to reset the xda2 . when i am trying to reset the xda 2 it does not boot it just shows the o2 screen with red letters of the version and does not even charge. my laptop cannot connect to xda2 and as a result i am unable to upgrade when i tried to run the 172187 .exe again it gives error 101: connection error
please help me out of this? thanks
I have an Atom Exec with ROM 20060721B1WWE, Radio RS00011. In the seeO2 website I saw an upgrade (Xda Atom Exec ROM Upgrade (ENG) 20060721B1WWE_RS00013) which is the same ROM but different Radio, supposed to improve quality of calls.
Anyway I went to upgrade it, followed the steps until it said it was uploading it and it would take up to 30 minutes. I went to do something else and when came back the pc screen was saying that the process finished successfully, saying that I had to do a hard reset of the Atom, wait for 30 seconds and then soft restart. I did all of that and all I got it's the O2 screen and doesn't go any further.
Following indication on this forum I launched the bootloader (camera button+reset), conected the usb cable, killed activesync and run again the updater.
The DSUU can see the Atom, says 'Device CE image version:0, Device Radio Image version: (blank) to CE Image version: 7210621, Radio Image version: R060822N_MN2ARC_RS00013.
When I click on Upgrade I get an Error message: Connection error, also on the Atom says '!!! Please use DSUU in OS mode and sync with Pc first !!! USB transfer Fail'
The only backup I did prior to this was using SPB Backup, nothing for the ROM. Is there any other way to upload the ROM?
From the Windows/Temp folder I got the files used by the DSUU:
Device Software Update Utility.exe
diskimage_Ver.nb0
EBOOT.nb0
ExtenderRom.img
nova_pda_033105.mot
vl1d_pda_Ver.mot
I've seen in other forums people recovering iPaqs or Axims using these files and software like romupdate, but I'm afraid it could get worse uploading the diskimage_Ver.nb0 as it is.
Anybody knows a workaround for this?
I ended copying diskimage_Ver.nb0 and eboot.nb0 to an miniSD card. Inserted it in the Atom and lauch the bootloader. It recognized the card and Rom file, started downloading it. After that I got few messages saying some files were missing.
Screen went blank and that's it. Now is completly dead, it won't restart or anything.
I'll have to send it to Hong Kong I guess.
I have tried to flash WM6 ROMs (both english versions available at wiki - pdaviet and orbit) to HTC original Artemis and every flash ends with error msg "The file \windows\cusTSK.exe does not exist", which is displayed after soft reset when it tries to install extrom.
Does anybody know where is the problem ? I have tried this flash several times, but always with this error ...
It sounds like you may have a corrupt extended Rom. I'd try flashing your original carrier ROM to fix it.
The error message is normal.
When I got the error the first time I boot the device (pdamobiz rom) I waited for 5 mins to see what happens. Then I simply made a power-off-power on to the mobile phone and the error never reappeared ever since. It works perfectly now!
I am not sure, but I guess this err msg is displayed when it tries to install apps from extrom, it is displayed after each hard reset. This is no limitation in functionality, everything works fine, only limitation is that there are no extrom apps installed, but these can be installed manually
I think the problem is that the program that changes the background in WM6 is not cusTSK.exe anymore. I don't know what is the program to do that in WM6 but maybe someone here knows. The error happens because on you extended rom there is a reference to cusTSK.exe. We need to know what is the name of the new program and then update our extended rom.
Sounds logically ...
Hi All,
I did some search, but it seems there's no Error 270 topic for a Touch Diamond. And surprisingly that's the problem I have. Here's the deal.
For a whole duration of the day I've been trying to upgrade to 2.03 ROM, which would my first ROM upgrade. I tried the ROM from the phone's importer site, the HTC site, xda site, all lof them with the same result. After the RRU reaches 100% the mobile goes to Tricolor with "Upgrade ROM code error" message and the RRU shows says Error 270.
I searched the forum and saw that some of the people suggested to burn different HardSPL versions, so I tried burning the 2.03 with various HardSPL versions, 1.24, 1.30, 1.93 are the few I remember, there were more, both signed and unsigned, the last is SPL-1.93.OliNex unsigned -> all of them installed nicely, with a clean reset after them but the following upgrade to 2.03 failed every time the same way, Error 270, as usual.
I use an original USB cable and an XP OS that, at the moment of RUUing, runs nothing but the RUU.
By the way, I also tried doing the upgrade from the internal storage. I renamed the ~100MB file to the name specified in the Noob Guide (DIAMIMG.NBH) and put it at the root of the storage device, but the bootloader gray screen says no image found (or something similar and goes directly to trying to find a USB host).
OK an Update (for whoever gets this problem after me).
I'm not sure why the installation from PC failed time after time - this is something for smarter people to find out.
I solved it by eventually managing to copy one of the numerous RUU_signed.nbh I tried, to the Internal storage, renaming it to the DIAMIMG.NBH and running the bootloader procedure.
Why didn't this work for a 6-10 times I did this before, I donno, the important thing that now it did, and I'm going to enjoy my diamond starting this moment.
Error Code 270
Dear Hunter_I
i have HTC Touch Diamond
i m facing the same problem. and i even dont know how to find the file and how to copy it in HTC internal storage
it is totally un accessible for me
can u help me in this regard
regards
Khurram
Dear Hunter_I
i have HTC Touch Diamond
i m facing the same problem. and i even dont know how to find the file and how to copy it in HTC internal storage
it is totally un accessible for me
can u help me in this regard
regards
Khurram
Hello,
I'll be happy to help to the extent I can.
But can you please specify where you stand right now?
I mean, what steps did you take already and where did you stop?
For example,
Do you have Hard SPL installed already?
What's the ROM you currently have?
Can your phone boot up correctly? Can it sync with your PC?
Is your phone locked?
Let me know some details.
I flashed the Cyanogen Mod 7 onto the phone about 3 months ago, and today tried a different ROM as my girlfriend's O2 card (It's a UK Orange phone) wouldn't work in it, and the SIM unlock code which I paid for wasn't working - the guy I bought the code from said it's probably ROM-related.
I've tried flashing a LeeDroid ROM, and an INSERTCOIN ROM but neither work. With Leedroid I get bootloops, and with the other it gets to a colourful background but nothing else on screen and no other buttons do anything.
I've gone into bootloader mode and tried just running an exe file (for example an HTC_WWE_BRAVO_date_version number_etc from the laptop with the phone connected via USB, but this doesn't work either.
At my wit's end now as I think I've bricked the phone...
Can anyone help at all?
Why does flashing ruu not work?
ur supposed to be in fastboot. not hboot when trying to restore using ruu
Thanks for the tip -
I get as far as an updating signature message for about 10 seconds, then it crashes out with:
ERROR [131]: CUSTOMER ID ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
This problem is easy to fix. Create goldcard with linux, put this in your desire and then flash ruu again:
http://www.nazriawang.com/2010/04/how-to-create-goldcard-with-ubuntu.html
I managed to successfully create a goldcard, but upon flashing the RUU .exe file, it gets to the 'updating signature' part (before the percentage completion bar has even started) and then crashes out with the following message:
Error [132] SIGNARURE (sic) ERROR
Please try to flash again with a different ROM update utility (or words to that effect).
EDIT: Now working. Thanks MatDroid!!