All I wanted to do was write to the write protected extended rom and that’s where my problems started!!!
I followed the procudure in the
http://forum.xda-developers.com/viewtopic.php?t=6470 forum
I down loaded a file from
http://www.c1au.com/iMatePDAROMS/ruu15283.zip
when unzipped it produced a file Ruu15283wwe_cdl which I ran.......(ok I know that it was a mistake.. yes I know I have made the classic newbie mistake)
It would appear to be an I-Mate updater and has updated my O2 Xda2 to an I-Mate. With the following
R 1.06.01
G 1337.16
D 1.52.00wwe
Now part of the reason I was able to install the new Radio Stack, New OS? and New Extended rom was because it was all in an .exe file which automatically did it.
What I would like to do now is return to the original O2 set up and forget trying to write to the extended rom.
I am a newbie and I have been silly, please can someone help me?
It seems that I can change the extended rom, which I have now back to my original Rom, which I made a back up of.
However the phone part doesn’t seem to be working....hum, I can install the down loaded (from this website) O2 version now and try that.
or I can role back to the imate software now as far as I knew the 2 parts of the phone were unconnected, so in theory what I have done should have effected the phone? Is this correct?
Sorted Yeah
Related
please help...
A few weeks ago I used the ER2003_edit program and created my own extended ROM, which installed fine.
Now the official O2 rom update is out it complains that the unit is not the right one and won't install
I cannot get the original O2 extended ROM in there, all the upgrade software complains about it being the wrong unit/county etc... how do I fix this??
I think the orginal rom is the second file on the O2 site called "Launch Rom". The original O2 extended rom files are on this forum somewhere, just search for "extended rom"
I already have the original extended rom files - they come with the new rom upgrade the file called MS_.nbf.
The problem is I cannot get the rom file loaded into the XDA, the upgrade software just complains about the unit being the wrong version or something and then exits
Hi, my brother is getting his xda 2 back and has asked me to install wm5 in it.
My questions are:
1. Do i need to simunlock his phone first, his phone is locked to smart philippines?
2. Is there anyway to backup his original rom, so i can flash it back in case he wants to downgrade back?
3. does upgrading your phone to wm5, simlock the phone again?
4 .Is it true that wm5 has problems regarding pocketie, camera button and loss of camera resolution?
Thanks in advance
1/3 roms and simlocks are never connected what so ever
changing rom will not sim lock or unlock (unless a tool to do so is autoloaded)
2 not sure what ppl mean if you have rom 1.72 and install 2005 and then install a 1.72 again you are back to your own rom not sure why one would want to backup the rom one had rather then just installing the same version again...
but if you mean your data then you can just use xbackup or spirite backup or activesync backup and restore that backup when you revert back to the rom version you had first.
4 if you read it in the 2005 forum and ppl dont have a fix you can find using search function then i guess so.
2. I wanted to restore the original rom, as in the rom itself. Just to be on the safe side.
the rom on your device is == 100% the same as the same rom version from the same operator's install files for that rom
so if you have 1.72 from tmobile and install 2005 and then get tmobiles install files for 1.72 and install that you have 100% the same device
with digital things everything is 0's and 1's
so there cant! be any difference between the rom from tmobile 1.72 you have and if you install 1.72 rom from tmobile
there is no hardcoded stuff which makes the rom of your device uniqe compared to every other device with the same rom
everything you need to know
http://wiki.xda-developers.com/index.php?pagename=Himalaya
http://en.pdamobiz.com/en/forum/forum_posts.asp?TID=62
Hi I made a very big mistake i flashed my cingular 8125 (g4) unlocked by IMEI-CHECK. I flashed it with molski aku 3.2 and when it reset the Cingular Extende Rom is the one that automaticaly gets lunched. So I unlocked my extended rom with Unlock_ext_rom_wizard_1 and reflashed again expectine that when config will be finished then the molski extended rom will lunch but no succes so I dont know how i errased the auto run on the extended rom and when i reboted it no my Cingular extended rom dont run and neither molski or farias I even cooked an extended rom but It have never auto runed again I do have backup of the original which I made with awizard 1.2 and other wiyh beta1.3 but I place it into phone memory or phone sd and it never runs I have to do it manually. Im tired of doing it manually and of it I want to instal another rom like molski's or Farias or maybe even cook my oun but I don't know how to make it autorun again. My extended rom in the phone is empty now because y got so p#$% with it that I erased it for compleate. I there a way that I can do it work again. Worst than this is that this damm (G4) dont let you do an sd backup image and the Cingular 8125 RUU2.25 its not intended to reflash a g4.
I think that the flash didn't work correctly. You should have Molski's extended rom after the flash. Maybe you're phone is still locked.
You can make the Cingular 8125 RUU2.25 rom work for you're G4. But you have to cook it yourself using risidoro's tutorial (here).
I'm not shure but I do know taht I have been able to upgrade with Farias & Molskis roms succesfully but never has got the extended rom wright now I downgraded back to • RUU_Molski.Biz_226102_22610105_022511_G4_WWE-30MB and It works great but no extened rom neither I have a backup of my rom but I have to install it cab by cab not very funny to do. Tried to do Extended rom cooking with Farias tutorial but nothing I'll try what you told me today and will let you know later.
It is a known problem that even unlocked, G4 8125 devices do not load the ext rom. Faria is aware of this.
Am trying to install xplore 1.1 on my G4 xda mini s.
The problem I seem to be having is getting the CID info and ROM info from Shelltools, it just says n/a for both.
I have copied and installed the cabs cert SPCS and enablerapi onto my device and installed them to main memory. Rebooted my device but I still get the n/a info showing.
All I get after installing xplore is a white screen. I then went back to the love rom and then back to my stock xda rom from the o2 site and tried to install xplore again with the same results.
It was saying that my stock o2 rom was a custom rom ??
I am now back on the love rom and get this info from shelltool.
This ROM includes:
9b000000 00a00000 d451b626 Extension Rom
80040000 03900000 7ce45b95 OS
92000000 00030000 07da0e96 Splash Screen
9d000000 00010000 5ce2e035 htc logo
blversion : crossbow
device : wizard
language : wwe
Brand : HTC
CID : n/a
ROM : n/a
IPL 2.21.0001
SPL 2.21.001
GSM 02.25.11
OS 2.26.10.2
Im doing something incredibly dumb arnt I ? I really have read mounds of information but cant find my solution. Can I flash from the love rom ? Do I have to put a certain stock rom on ? I just used the latest one from the O2 site.
Any help would be most gratefully received.
I just want WM6 !
maybe you have to have your phone CID unlocked. i had problems with the Mun rom and only after a few trys it worked (i went back to the love rom a couple times). look around there is another method to flash a rom into a cid locked phone.
hope this helps. best regards.
erik
But using shelltools when getting the rom info it says CID n/a ROM n/a. At that stage the rom you are using hasnt even come into it then has it ?
I thought shelltools worked with G4 CID locked ? Im sure others with MINI S using the standard O2 rom must have done it, which says to me that I must be doing something simple wrong ??
Anyone ?
i dont recall ever seeing any info in those boxes. This is just from my personal experience. If i flash again soon i'll let edit this post and let you know.
All I know is it wont flash to Xplore 1.1 from the Stock O2 rom on their website. In some screen grabs on one of the guides it has information in those two boxes.
I have run both the cab files required on my phone and done a soft reset afterwards.
I will try to flash from the love rom tonight, but I have a feeling it isnt going to work.
Anyone any experience of this particular problem or have an idea of whats going on ?
Just tried going from love rom to Farria and no joy.
Incidently I have just restored to the stock O2 rom again yet in Shelltool it shows up as BLversion : Crossbow ???? Surely thats not right ?
Manged to go from stock rom to Farrias rom ok. Then went from that to Xplore, but there were double entries in the system folder.
So then went back to stock rom and then to xplore and it worked.
All I could suggest to people having similar trouble, it keep trying. First two attempts I couldnt go from stock to Xplore.
Hello
Since a week or two I get color distortions on my screen (blue/yellow stripes), this seems a hardware/motherboard related issue, and therefore I'm returning my HD2 to the store.
For this reason I'm trying to flash my stock ROM back, namely _HTC_HD2_RUU_Leo_HTC_NLD_1.66.404.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship. It's one I got directly from HTC's product support site.
As I've come to understand, flashing the stock ROM from an microSD card, will immediately put the right radio back in place as well.
However, I tried to flash this leoimg.nbh (from microSD yes), but the flashing failed and I got a RUUNBH error. So using HSPL I updated my radio back to 2.08.HSPL, and from there back to a TMOUS radio, to reinstall my beloved ChuckyROM.
I almost thought my phone was ready for the trash.
Now the question is... what is the right way to get back to my stock ROM? Preferrably without potentially trashing my phone..
I'd like to get back to one of these:
_HTC HD2_RUU_Leo_HTC_NLD_1.66.404.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship
_HTC HD2_RUU_Leo_HTC_NLD_1.48.404.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship
_HTC HD2_RUU_Leo_HTC_NLD_1.43.404.1_Radio_Signed_15.26.50.07U_2.04.50_22_2_Ship
Edit:
I'm currently using ChuckyROM with TMOUS radio 2.11.50.26 which seems to be relevant as well since some people seem to have bricked their phone with a TMOUS radio.
Edit 2:
Solution that worked for me
I recommended this one.
_HTC HD2_RUU_Leo_HTC_NLD_1.66.404.1_Radio_Signed_15.30. 50.07U_2.06.51.07_Ship
It's the last update in the list you have.
Ore; depending from your country this one.
It's the one I use when I go back on stock Rom before I install cooked Rom.
RUU_Leo_HTC_NLD_1.66.404.1_Radio_CRC_Signed_15.32.50.07U_2.07.51.22_2_Ship
Yes, but it's also the one that "crashed" during the flashing. I'm looking for the correct steps to flash them.
I was using ChuckyROM with the TMOUS radio, and then all I did was rename the RUU_signed.nbh in the exe file to leoimg.nbh and put it on the microSD-card. Then reset my phone (and pressed volume down) and the flashing began.
Should I have done something else first/instead?
Thanks for the reply
Small bump
Quick update on this one.
I managed to get back to a stock rom with the following steps:
I downgraded HSPL by running HSPL2, and selected the "1.42.HSPL" version.
Then I extracted the .nbh from _HTC HD2_RUU_Leo_HTC_NLD_1.43.404.1_Radio_Signed_15.26. 50.07U_2.04.50_22_2_Ship, and flashed the whole thing (from microSD card).
Something weird happened during this step. I wasn't able to launch the flashing by doing a reset+vol.down. Instead I put the .nbh on my microSD AND started the RUU upgrade with ActiveSync.. somehow this magically triggered the install of the .nbh that was on my microSD. This luckily worked.
From here I got back to a ROM version that was available on the HTC product site, namely _HTC HD2_RUU_Leo_HTC_NLD_1.48.404.2_Radio_Signed_15.28. 50.07U_2.05.51.05_2_Ship. I just ran this update with ActiveSync, not from microSD.
AFAIK, it's now safe for me to bring it back for warranty! ^^