Good day, everyone.
I am trying to upgrade bootloader on 5 Himalaya machines (XDA-II) to version 1.06 taken from buzzdev.net (current bootloader 1.02). I cannot find the procedure for the update. Running himaupgradeut.exe with boot1.06.nb0 file in the same directory does not work. I googled around and searched FAQs on this website, searched forum on buzzdev, but cannot find anything. I know it is possible, as I have one XDA-II with bootloader 1.06. Somehow I managed to upgrade it a year or so ago, but forgot how I did it... am I plain stupid or something? ;-)
Related
Okay, hope this will help some people who like me upgraded to the WAXX 1.72 Rom recently, and now want to upgrade to the 'official' 1.72 1.81 Rom from O2.
Initially, the downloaded package from O2 refused to upgrade stating it had errors, which I believe were "country code" errors.
However, I downloaded the modified Himalaya Upgrade file posted by The Hobbit http://forum.xda-developers.com/viewtopic.php?t=12512 and then placed the XDA II in bootloader mode by pressing the power key, navi-key and reset button.
Place the unit (which should now read Serial) into the cradle. The screen should now say USB. Make sure that the modified Himalaya Upgrade file is in the same directory as the official 1.72 1.81 files, and double click it.
The upgrade process should now be OK !
(Well it is for mine, as I'm in the midst of upgrading whilst I write this)
Have fun !
Mark
Well done . Very useful information .
For those people for whom it doesn't work - look at my post here. When I tried the updated HimaUpgradeUt many moons ago, it wouldn't work for me.
Thanks
Thank You!!
I tried another method posted in the forum that "worked" (I know, its at my own risk yadda yadda yadda) and got a hosed XDA.
I was stuck on the bootloader for an hour while I tried to get the update to run without country code errors.
I was in the midst of trynig to edit the .nbf files to match the country codes installed on it when I found this post, followed it and wahoo! its updating now.
I used the official o2 files I downloaded myself so I know this should be a clean rom.
The reason I did this was that with the previous one It kept freezing when I delete files. no idea why. I had to reset it, then when i deleted a file again, wham it froze. I did a hard reset, and it didnt seem to lock up after that, so I carried on for a month or so then it started again. This didnt link in with any new software i can remember installing.
Im hoping that problem goes away with the new o2 rom. Fingers crossed
its been a while since ive been here.. lots of new developments..
good
Sorry if this is a repost. But I have SPL-1.04 and I can get into the bootloader but won't go as far as windows boot screen. I tried all the methods that were on this Forum and Wiki, nothing prevailed.
I flashed a rom that was not made for my phone, I just realized but I hoped that I could get out of it. I flashed my phone before with jasjam 1.20.305.104
USBmonitor stops at rbmc temp.txt usiing any radio 1.14 update
can't update the rom because I think my radio is corrupt.
I have been trying all the methods for 5 days straight, even leaving it update for a whole day, but usbmonitor is just stuck on rbmc temp.txt
when updating with a rom it just has !....... or something like that and the process stops and ends making me believe that it's just because I don't have Activesync.
Any help would be appreciated, I will be going to softbank later this week if I can't find a solution... damn my stupidity!!!
Hello all,
I got a friend of mine who came to me with a device-password locked Hermes, which password he cannot recall (actually his girlfriend...). I said I would be willing to give him a hand to unbrick the device. The problem is that I cannot install any ROM on the device, coz I got an error connection right after the screen goes white and the percentage count should normally start.
So I put the Herm in Bootloader (spl-1.06) and try to flash the OliPro Bootloader. The procedure goes correctly until the step where the upgrade itself should begin, counting from 0%... here, I got:
ERROR [262]: Update error: communication error.
I also tried to flash a ROM directly, but since my Bootloader is 1.06, I didn't find a CID match ROM, so it also failed. The Herm is now not bricked, but it stays at the password input screen, so cannot enter windows properly.
Any help on this?
Thanks,
Ionutz
Interesting since you are trying to go around something HTC probably did not want for people to go around due to security....
agovinoveritas said:
Interesting since you are trying to go around something HTC probably did not want for people to go around due to security....
Click to expand...
Click to collapse
yes, i grih you,and normally i wouldnt even try to do such thing, if it hadnt been for a friend of mine which i know.
besides i would like to learn more stuff about my Herm and this is one thing I havent seen discussed here, although i keep reading xda forums for such info.
just found the solution: i flashed another ROM with same CID since my BL was 1.06, but with BL 1.04. After that, I managed to flash any other ROM and automatically upgrade the SPL to 1.10 or 2.10 Oli accordingly.
If any of you interested and dont get the short explanation, PM me.
cheers,
Io, owner of 2 kicking TyTn's
BL 1.06 didnt allow devices with a different CID to be flashed,
eg: my TyTN had the CID: QTEK001 so i couldnt flash a ROM destined for a device with CID: VODAP001
But BL 1.04 had a bug where you COULD flash any ROM to the device regardless of the CID, the first attempt shows a vendor ID error, then try again and it will flash no problem.
The simplest way I would have got past the device security problem would have been a hard reset.
mrvanx said:
BL 1.06 didnt allow devices with a different CID to be flashed,
eg: my TyTN had the CID: QTEK001 so i couldnt flash a ROM destined for a device with CID: VODAP001
But BL 1.04 had a bug where you COULD flash any ROM to the device regardless of the CID, the first attempt shows a vendor ID error, then try again and it will flash no problem.
The simplest way I would have got past the device security problem would have been a hard reset.
Click to expand...
Click to collapse
I know the details about BL 1.04 vs 1.06, thats why I flashed a BL 1.04 ROM, but with the same CID QTEK_001, or smth.
I have to admit though that I never ever thought about doing a simple hard-reset. I guess it would have been to easy, I jumped to more complicate scenarios. Thanks for the help anyway, i gotta learn that.
Thanks mrvanx, glad I read down the whole thread to the part about a simple hard reset working. I lent my 8525 to a friend, thinking he might be interested in buying it, then he didn't have the money, and after I listed it on ebay today, I charged it up to flash to ATT stock, found it password locked, called my friend a few times just getting his voicemail, so tried flashing, and it said the Hermes wasn't connected to the PC...
I figured there would be a solution here at XDA..and POOF, like magic here it is!
So yes, all I had to do was a hard reset, tested and it works, and it was simple, so thanks again mrvanx, although this thread is very old, glad I found it LOL!
Hey guys.
Yes, I'm new here, but not new to phones or computers by any means - trust me.
In any case, what happened was I downloaded the XDA Live version of Windows Mobile 6 for my Hermes (originally Rogers branded) and installed it.
Then, I discovered the actual forum here, and saw Schaps' version of WM6 pro and I want that badly. Regardless of which version I'm trying to upgrade to, I get the same issue.
Here it is:
When I connect the phone normally with ActiveSync and try to upgrade to Schaps' ROM (or Dutty's, or the official one, or the T-Mobile one, or the Qtek one, anything), I get a 260 error saying that my USB cable isn't properly connected. Now I've seen and tried the fixes for that error with no luck. The other error I occasionally get is one saying that my device code isn't correct or something or other. And another one is that my image file is corrupt and that I should check my update utility.
What do I do?
ANY HELP would be greatly appreciated!
Thanks in advance!
P.S. My bootloader version is 1.11 (I think) as per the following screen during bootloader:
HERM200
IPL-1.01
(The following part is in yellow below the above part)
HERM200
IPL-1.11
I had the same problem.
I then upgraded the boot loader with hard-SPL:
http://forum.xda-developers.com/showthread.php?t=296722
Now it's working fine and I can load any ROM.
Cheers
Pat
I successfully upgraded to SPL-1.10, with the same result (no change).
I'm really unsure of what's going on with this...but I really need to upgrade to Schaps' TouchFLO ROM - and should be able to easily...
When you upgrade the rom, chose hard-spl (safe).
Good luck
Patric
Hello,
i am trying to install a the old WM 6.0 on my O2 XDA because the Hermes does not start every time i turn it on. The Problem is that the install stops at 12 %. After five our six trails the install rans through this point and completes the install. But this WM 6.0 has the problem that it will not boot every time, the phone-functions does not work every time and so on. So i tried to reinstall the OS and now i'm standing on 12 %.
The WM 6.0 install comes directly from O2.
Here the dates out of my bootloader:
HERM100
IPL-1.04
HERM100
SPL-2.10.Olipro
Sorry if my question is a little bit stupid. But my english is very bad (as you can see ) and so i can't find an answer.
Can someone help me?
Try to reinstall the shiiped carrier rom. The rom it originally came with.
Do this using the sd card method. Its safer, especially if you are flashing a radio rom.
Check for bad blocks. This could cause the original symptoms you said. Look in the upgrading ection for instructions...
Cheers...
Thanks for the infos, but i have phoned with O2 today. They will repair or exchange my device.
No my question is if i am allowed to change the bootloader to "SPL-2.10.Olipro" because i have done that
Or should i try to downgrade to an older version? Do you know which version was first on the device?
Thanks
push. Could someone help me plz?
If you're trying for a warranty service then it would be best to downgrade spl. However, you may not be able to....
Search the wiki for instructions, they are there...
Cheers...
Hmm damn, do you think they won't exchange the pda with the changed bootloader?
As you remarked it semms to be hard work to replace the bootloader by an old version.
There is a chance they MAY charge you for repairs or replacement. This can be VERY ouchy....Lotsa $$$.
Perhaps i should ask the hotline if it's okay or not. Even better than paying bills for sending in an bricked Hermes.
NOT OK... Changing the SPL on your Hermes is instant void warranty. You need to change it back.
Any idea on which version?
No one any idea which SPL original is on a Hermes?
Hey!
Now i have tried to downgrade to 1.10 Olipro, have installed a WM 6 Rom from HTC but nothing happend. The device works for the moment, but i am sure that the device will break down the next days again.
Any other idea how to downgrade to SPL 1.11? I am running out of time
No idea? Anyone? Running out of time (warrenty) ^^