Related
Ok I have searched the forums pretty hard the last couple of days, and I have not found anyone that has the same issue as mine. It's not too big of a deal as everything operates but it is an issue all the same. This is all of course after I have succesfully ran HARD SPL v7 and upgraded to Black 3.0.1. Basically I decided to use POF's SuperCid Unlocker 3a (yes I know if I had HARD SPL 7 then why go through the trouble of Unlocking my CID, let's call it a need to mess with things) and everything went succesful. Then after the fact I read that it is still good even if you have SuperCID to upgrade the SPL to 2.10 and have read some peoples signatures and it appears that they have succesfully done this. Here is my issue;
When I run the CustomRUU it autodetects my SPL no problems, HARD-SPL? is checked, everything seems to go fine until it gets to the boot loader, once it is there, the progress bar pops up, zings to 100% and then reboots, cool? no because it didn't actually upgrade anything everything is still the same. Ok, so I tried the format SD card and rename *.nbh file to HERMIMG.nbh and put only it on the card, when I go to bootloader it does a quick flash to the screen like it recognizes the image but then goes to boot loader and nothing changes (the flash is so quick I can't even read whatever message it may be showing). I have tried pretty much every flashing method I can come across. MTTY wont recognize that I even have a USB port so I have been unable to try that method. So two questions:
I have SuperCID, so should I continue to even bother to get to 2.10?
If so, is there anything else I can try? Or do I need to get MTTY to work and try that as that is really the only thing left?
Thanks for any and all help anyone can provide.
PuckX said:
Ok I have searched the forums pretty hard the last couple of days, and I have not found anyone that has the same issue as mine. It's not too big of a deal as everything operates but it is an issue all the same. This is all of course after I have succesfully ran HARD SPL v7 and upgraded to Black 3.0.1. Basically I decided to use POF's SuperCid Unlocker 3a (yes I know if I had HARD SPL 7 then why go through the trouble of Unlocking my CID, let's call it a need to mess with things) and everything went succesful. Then after the fact I read that it is still good even if you have SuperCID to upgrade the SPL to 2.10 and have read some peoples signatures and it appears that they have succesfully done this. Here is my issue;
When I run the CustomRUU it autodetects my SPL no problems, HARD-SPL? is checked, everything seems to go fine until it gets to the boot loader, once it is there, the progress bar pops up, zings to 100% and then reboots, cool? no because it didn't actually upgrade anything everything is still the same. Ok, so I tried the format SD card and rename *.nbh file to HERMIMG.nbh and put only it on the card, when I go to bootloader it does a quick flash to the screen like it recognizes the image but then goes to boot loader and nothing changes (the flash is so quick I can't even read whatever message it may be showing). I have tried pretty much every flashing method I can come across. MTTY wont recognize that I even have a USB port so I have been unable to try that method. So two questions:
I have SuperCID, so should I continue to even bother to get to 2.10?
If so, is there anything else I can try? Or do I need to get MTTY to work and try that as that is really the only thing left?
Thanks for any and all help anyone can provide.
Click to expand...
Click to collapse
Did you look on the bootloader screen to see if your SPL changed? To my knowledge the only place you can see it is in the bootloader screen (tri-color screen) And flashing Olipro's Hard SPL only takes a couple seconds so it sounds to me like it is working as designed.
Or are you trying to flash a different rom? If so then try deleting everything you have in the directory you are using and re-downloading. You might have over-written the file you want to flash with the HardSPL one. You shouldn't be using the hard spl wrapper to flash a rom in any case, i believe that is mentioned in bold at the top of the Hard SPL thread.
Ok nevermind I was able to get it to work and MTTY was the answer. This is the 2 steps I had to follow:
From the thread: http://forum.xda-developers.com/showthread.php?t=291723
sp3dev said:
Hi. I`ve finally found the way to connect mtty and run rom update utility in Vista. tested on rtm 6000.
First of all, connect your device when it`s in bootloader.
next, open Windows Mobile Device Center and in connection settings uncheck Allou USB Connections.
next, goto contol panel-administrative tools-services and start windows mobile device connectivity and windows mobile device 2003 connectivity
next, goto device manager and find your device and update the driver to the one from AS 4, i attached it, wceusbsh.inf.
then, kill wmdc.exe with any taskmanager
You are Ready. run ruu or connect MTTY. I guess that vista default driver uses another port, not WCEUSBSH001, that`s why we have to use the old driver.
Click to expand...
Click to collapse
Then Do This:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootloaderMFG
Flashing SPL-1.01 MFG instructions
Put hermes in bootloader mode (side ok + power button + softreset)
Connect Hermes to computer using USB cable.
Open mtty.exe, select "USB" from the dialog box, then hit Ok.
Hit enter twice and you'll see the "USB>" prompt.
Then type these commands: (note the use of 'lnb*s*')
USB>task 32
Level = 0
USB> lnbs SPL-1.01.nbs 50020000
USB> task 8
Device will reboot after this, with bootloader 1.01-MFG on it.
Once I was able to do all this I was succesfully at 1.01 at which point I ran the Custom RUU and upgrade to 2.10 without issue. Once again all right there in the forums, just had to be pieced together to find a solution.
Thank you all for all your dedication to these projects, you make owning a PDA more fun than I am sure was originally intended. I love messing with things.
I have also attached the necessary files from the original posts to perform this for anyone else facing this issue.
PuckX said:
Ok nevermind I was able to get it to work and MTTY was the answer.
Click to expand...
Click to collapse
Cool, glad you got it working
Ok...I have been through all the posts about upgrading etc. I still have a problem and I'm sure that I'm overlooking something....but I can't figure it out on my own. Here is what is happening (it does the same thing with every RUU that I've used...the DST fix...upgrading to WM6....etc)
1. I run the RUU and let it go through its routine (extract files, verify info on pc, etc.)
2. I check the box that says I have read the readme and click next
3. The next screen appears and it has the following steps:
Connect to the USB cable (check)
Establish an ActiveSync Connection (check)
Disable standby and hibernation on PC (check)
Make sure batter is > 50% (check)
Then I check the box and click next
4. I pick the update and click on the update button
5. I verify that I want to upgrade my phone from ROM verion x.xx.xxx to x.xx.xxx and click next
6. The program tells me that I am finally ready to update...and if I am sure I want to proceed to click next...so I click next
7. As soon as I click next...the progress bar comes up on my pc and my phone goes into standby mode (no bootloader...just standby). The progress bar never moves.
8. After a minute or two the RUU give me the ERROR [260]: Connection
9. I reboot my device and repeat steps 1-8
10. I reboot my device and my computer and repeat steps 1 - 8.
Now if I leave my device connected to the usb and close out the RUU after it gives me the ERROR [260], and then run the RUU again...when it is first verifying the information on my pc (before it asks any questions and before it tells me to connect my device) it will throw the device into bootloader mode. If I try to keep running the RUU while the device is in bootloader mode it give me the error that my device is not connected. I have tried and tried...maybe one of ya'll can help me. Thanks in advance
Chris
Some questions:
.) Is your desktop PC running XP or Vista?
If you have a firewall running, close it.
.) If you running Vista check this guide:
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=23&Itemid=27
.) What updates did you try to flash?
.) Did you install Olipros bootloader first?
gerald_s said:
Some questions:
.) Is your desktop PC running XP or Vista?
If you have a firewall running, close it.
.) If you running Vista check this guide:
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=23&Itemid=27
.) What updates did you try to flash?
.) Did you install Olipros bootloader first?
Click to expand...
Click to collapse
XP
No firewall
I tried to flash the WM6 from AT&T I assume its beta
and no did not install the Olipros bootloader
Ok...I think I found out how to do this...Ya'll can tell me if I'm screwing something up.
I go through all the steps listed above until it gets to the progress screen. When it gets there I manually put the the device in bootloader mode (Power, side ok, and reset). Once I do this...the progress bar starts moving. I will let you know if this works...
Hmmmm
Its not the way it should work but if it works its ok
You should have installed Olipros HardSPL first and then try to flash an official rom. If its working then something with your download is wrong.
What ROM is on there now?
Has the phone been CID unlocked?
Oli's CustomRUU is better, you may want to unpack the ROM and put the NBH in a folder with Oli's RUU and then do the upgrade.
BTW, gerald_s is right, you should not have to do that... what you may want to do is put the phone in Bootloader mode manually (while not connected to the PC), then plug in the USB, then start the RUU. That helps some people with 260 error.
I've got the same damn issue... it's driving me crazy. I had this occur when I flashed my Hermes100 from the stock version to Custel's. After about 15 starts and reboots it took. I'm now trying to get to Vp3G's 3.60 and it continues to give me the 260 error.
I am trying to figure out how to fomat my micro, but really hoping to find a solution over cable.
Hermes 100
IPL 1.04
SPL - 2.10 Olipro
Any suggestions?
You may be trying to flash a rom that includes the radio rom. What is your device? Is it possible that your device is a new x01ht with radio 1.14 and radio bootloader 0182? If yes, then you will get this error when you try to flash a rom with this method because during the flash it will be disconnected by the radio bootloader because it is not overwriteable. If you flash using the NBH file on the microSD, it will skip past radio and radio boot and just flash the other parts of the file.
mikebraeuer said:
I've got the same damn issue... it's driving me crazy. I had this occur when I flashed my Hermes100 from the stock version to Custel's. After about 15 starts and reboots it took. I'm now trying to get to Vp3G's 3.60 and it continues to give me the 260 error.
I am trying to figure out how to fomat my micro, but really hoping to find a solution over cable.
Hermes 100
IPL 1.04
SPL - 2.10 Olipro
Any suggestions?
Click to expand...
Click to collapse
If you are running windows XP, just connect the card to the computer, open MY COMPUTER, right-click the removable disk that is your microSD and then click format. Default in windows xp is to format using FAT32 filesystem which is perfect.
The thing is... if you dont know how to format a drive in Windows, should you be flashing your device yourself?
Which Solution???
I've got a Softbank X01HT with:
S/N: HT639
SuperCID <--- result of checking by mtty
IPL: 1.04
SPL: 2.10Olipro
GSM: 1.47.00.10
OS: 3.54.07 WWE
I tried to flash with new Schap 3.54c but the process would not be done coz ERROR 262 or ERROR 302. Fortunately, after failure of flashing, my device is still normal running. Then I tried to flash radio 1.51.00.10 but I got the same above. Once again, I have just tried to flash splash screen and I got the same result too. It mean my device can not upgrade anything !
Anybody here show me a solution that help my device to become a normal device, I mean it will be able to flash anything ROM as it would be! Don't tell me READ and READ, I had read so much . And don't tell me use MTTY again SPL1.01MFG, I think that is a final solution
Wantoknow said:
I've got a Softbank X01HT with:
S/N: HT639
SuperCID <--- result of checking by mtty
IPL: 1.04
SPL: 2.10Olipro
GSM: 1.47.00.10
OS: 3.54.07 WWE
I tried to flash with new Schap 3.54c but the process would not be done coz ERROR 262 or ERROR 302. Fortunately, after failure of flashing, my device is still normal running. Then I tried to flash radio 1.51.00.10 but I got the same above. Once again, I have just tried to flash splash screen and I got the same result too. It mean my device can not upgrade anything !
Anybody here show me a solution that help my device to become a normal device, I mean it will be able to flash anything ROM as it would be! Don't tell me READ and READ, I had read so much . And don't tell me use MTTY again SPL1.01MFG, I think that is a final solution
Click to expand...
Click to collapse
Have you tried flashing with your microSD?
Kevbodian said:
Have you tried flashing with your microSD?
Click to expand...
Click to collapse
I forgot to tell that, I had flashed through extra memory card yet, and could be done!
But I wanna flash ROM against CustomRUU through MS Active Sync as I had used before. Can you help me
i have a problem very similar to Chris. when i check the box "yes activesync is syncronised", and then the progressbar shows up and the phone goes into standby.
i've turned standby of in powermanagement options.
my os is XP
i use active sync v4.5
and this is first time i try this.
i've read something about this bootloader, i can get there but then i cannot sync with active sync. so i kinda stuck.
have been searching the forums and this was the same problem as mine but i don't understand your solutions.
//KufrA
--Problem solved--
i did all things without activesync,
1. start phone in bootloader
2. do the install
3. wait 0% to 100%, and done.
is there a problem with active sync or why do i have to do anything with it at all?
Hi all
Rather than hijacking other threads I thought it might be of help to others if I start a new one.
Having spent hours trawling thru the other threads I have now concluded that I need the help of one of the wise sages such as Cmonex or Olipro.
I decided that a thread might benefit others rather than just pm'ing them.
Ages ago i bricked my ameo.
I had upgraded to spl 3.5 and had been playing with one of michy's roms. Whilst the rom worked fine the boot-up splash screen had become corrupted, I also noticed that the camera had stopped working/initialising.
In an attempt to get the camera back I tried various other roms and decided to downgrade to spl1.2 so that I could go back to a stock rom. In a moment of stupidity I accidentally tried to reflash using a spl3.5 rom.
This resulted in a invalid model id message.
In desperation I did the old vol key down and reset pin. Told the ameo to restore.
From that point onwards the unit is no longer recognised by my pc, in the tricolour boot screen it initialises and says loading 0058002 and then displays
IPL-v1.00
SPL-v1.20 Olipro
I have tried the mtty option, using different computers and different leads, have even tried running the program from the root c: to no avail.
The problem is that whilst in boot loader screen on connection to the pc there is no usb option displayed, nor is there a usb option in the mtty drop-down list.
Pdajoy kindly suggested using a mini sd card to flash the unit. I purchased a micro sd with a mini adapter. Formatted the card to fat32, renamed the ndc file booted to the tri colour boot screen and hit reset. All that happens is that is tries to boot the old fecked o/s and gets as far as a blank grey screen and no further.
I really do miss my ameo- the screen on my touch pro is just too small!!!
Any help will be greatly appreciated.
Thanks
Hope is a typo error here, should be
"rename the RUU_signed.nbh to ATHEIMG.nbh"
Did you removed your SIM card before applying?
Sorry my bad for not warning you in advance.
Grey screen, you mean no text at all. Total blank grey?
Am just curious.
hi Pdajoy
I had renamed the files ATHEIMG.nbh, the reference in my post above is a typo. There was no sim in the phone either.
The screen after it tries to load the old corrupt rom is just a grey mass- nothing else, no text or images.
The two pics listed show the ameo booting and then the grey screen.
http://imaginarynumber.co.uk/ameo/IMAG0033.jpg
http://imaginarynumber.co.uk/ameo/IMAG0034.jpg
hi imaginarynumber,
Thanks for the photo.
hey 4.00 on screen, I believe your set is still spl 3.5
If it is my set, I will definitely flash AP4 again.
Best wait a little while for kind sage to drop by with to assist you.
Don't wish to see you bricks yours.
I have the same problem what can we do ?
I found a way to bring back the normal bootloader you just have tu press the reset button then you press the camera button and you will have your bootloader again
IT IS NOT WORKING you get back to the original bootloader but when you want to put back a rom even the official one after 1 percent it gets back to the grey screen PLEASE HELP
Srry athena works again place the mmty tool with mac bin file in the root of c and try again dont forget the task 32 command before the bin command that worked for me
I had the same exact problem (even the screen was the same) and didn't realize that the initial screen that shows up isn't the bootloader. fixed it by waiting for the grey/white screen, holding the volume button down then reset button and camera button + reset which brought me to the actual bootloader. From there I installed the latest AP rom, updated my radio and installed mitchy's 6.1
Big problem: Mac Address? Still getting dark screen and blue stripes!
Hi, I have follow the various steps above, however I cannot boot my Athena after words.
I am lost! I have followed exactly the steps:
1. disable activesync and put mtty into the C:/ root
2. connected athena as usb and booth with 3 colors screen
3. run mtty
4. done the cmk
5. selected port usb and created the .bin file for my SPL (1.2)
6. in mtty run task 32 and went up to: "code entrypoint unknow"
When I boot again my Athena I get the same dark screen with blue stripes:-(
You need to flash a rom
puffo said:
Hi, I have follow the various steps above, however I cannot boot my Athena after words.
I am lost! I have followed exactly the steps:
1. disable activesync and put mtty into the C:/ root
2. connected athena as usb and booth with 3 colors screen
3. run mtty
4. done the cmk
5. selected port usb and created the .bin file for my SPL (1.2)
6. in mtty run task 32 and went up to: "code entrypoint unknow"
When I boot again my Athena I get the same dark screen with blue stripes:-(
Click to expand...
Click to collapse
It looks like you did the wifi fixx correctly but the rom is still corrupted
Go into bootloader to confirm your SPL and then flash an spl appropriate rom
cheers
So, how to proceed now?
Dear Iakeman, all,
how can I confirm now my SPL and than flash the ROM?
I confirm that on my 3 color band screen I have:
IPL-v1.00
SPL-v1.20 Olipro
So, what is next??? If I just reset or restart the Athena in the normal way I will get back the dark screen with blue stripes and nothing will happen....
Do I have a this stage to install a new VM ROM? But I am wondering if I can do that since not sure that in this mode the Athena can communicate to my PC and so being able to upload on it any ROM....
puffo said:
Dear Iakeman, all,
how can I confirm now my SPL and than flash the ROM?
I confirm that on my 3 color band screen I have:
IPL-v1.00
SPL-v1.20 Olipro
So, what is next??? If I just reset or restart the Athena in the normal way I will get back the dark screen with blue stripes and nothing will happen....
Do I have a this stage to install a new VM ROM? But I am wondering if I can do that since not sure that in this mode the Athena can communicate to my PC and so being able to upload on it any ROM....
Click to expand...
Click to collapse
You have confirmed that you have spl1.2 by quoting what you have seen in the tricolor screen.
Get back into that screen , making sure you have removed the sim and sd card and then conect to your computer via the usb cable.
You would have downloaded an spl1.2 rom ( you previously stuffed the radio by trying to flash an spl3.5 rom) and then run the romupdateutility .exe .
then you should be sweet!
having read a reply of cmonex to another post I am starting to think that all hope is lost.
It seems that if windows is unable to recognise the phone it is possibly the case that it is completely f*cked!!!
It would be nice if someone could clarify this...
Which WM to ul now?
Dear Iakeman,
thank you so much for your kind reply. So at this stage I can try to upload to my Athena device, basically, any spl 1.2 rom of WM 6.0, or 6.1 or even the 6.5 beta?). Or I must start with spl1.2 rom WM 6.0 ?
Yes! It works!
Hello, after so much pain, I have follow the Cmonex post 33 to fix my broken firmware and now I have been able to upload properly the VM 6.5.
Many thanks!
imaginarynumber said:
I have tried the mtty option, using different computers and different leads, have even tried running the program from the root c: to no avail.
The problem is that whilst in boot loader screen on connection to the pc there is no usb option displayed, nor is there a usb option in the mtty drop-down list.
Thanks
Click to expand...
Click to collapse
just a thought.
Once you finished doing mtty, did you reenable usb in activesync as per this post
http://forum.xda-developers.com/showthread.php?t=387454&highlight=mtty&page=2
the other thought was is the usb cable and the usb port able to sync with other wm devices? maybe the slot on your athena is faulty?
Hi Lakeman
Thanks for the reply.
It is possible that the usb port is faulty but it seems improbable that this should have failed at exactly the same time as me stuffing up the O/S.
I will try to find the cmonex post to which I am refering later today (the one that suggests that the phone is stuffed).
Tnx
when i type task 32 show this plz help
Cmd>task 32
Level = FF
puffo said:
Hello, after so much pain, I have follow the Cmonex post 33 to fix my broken firmware and now I have been able to upload properly the VM 6.5.
Many thanks!
Click to expand...
Click to collapse
HI PUFFO,
WHICH Cmonex POST 33 R U REFERRING TO?
I M FACING EXACTLY THE SAME PROBLEM THAT U FACED AND AM WAITING FOR THE NEXT STEP.
KINDLY REFER ME TO THE POST SO THAT I CAN START USING MY ATHENA.
THANX
I need some expert help please! I have a Hermes (Orange SPV M3100) that I want to flash with a custom ROM but I am having a problem with ActiveSync losing the USB connection at the point that the device enters the bootloader screen. I am also unable to flash using the SD card method. I have flashed a Nike without any problems and I'm usually good with technical stuff so I think there must be something extra I need to do that I have missed. I hope that somebody can spare the time to help me solve the problem. Here are the details:-
I am trying to follow Mr Vanxs guide to flashing the ROM in windows Vista so that I can upgrade it from WM5 to WM6 and apply a custom ROM to load a new TouchFlo style OS. The first step in this process is to flash HardSPL using this guide but my problem with the USB connection won't let me do that. I have unlocked the device using Hermes Unlocker 3a so it is (or should be) SIM and CID unlocked and be SuperCID with HardSPL-1.40 (so maybe I can miss the Mr Vanxs HardSPL step?).
So, when I run the RUUWrapper.exe, choosing the Force option and accepting the messages I eventually get a prompt on the device. At this stage ActiveSync is connected. I click Yes on the device and it enters the bootloader screen which shows 'USB' on the tri-color screen but ActiveSync immediately drops the USB connection. The update then waits for a while then fails with Error 260. I have to do a soft reset to get the device out of the bootloader screen. When the device reboots the Activesync connection comes back to life.
I thought that I maybe don't need to HardSPL first so I tried just going straight to the ROM upgrade but I get the same problem.
Also, I tried following this link to flash using the SD card instead of USB but when I get to step 6 I don't see a confirm message - just the usual bootloader screen (it doesn't help that the screen shot doesn't appear on the link so I'm not even sure if I'm getting the correct screen). Any ideas?
I realise that an answer to this probably already exists somewhere on the forum but I have spent hours trawling through posts and I can't find it so I hope somebody has come across this before and can help me out.
Thanks guys!
Don't worry I solved it by rebooting my PC, skipping the HardSPL and flashing with an official ROM (HTC_TyTN_WWE_3.54.255.3_6275_1.48.00.10_108). I can now apply custom ROMs.
Am having a problem with unlocking a Hermes using the SIM_CID Unlock version 3A
I appear to be stuck in a loop with the unlock process. I appear to have got as far as having installed OliPro (while still being at bootloader 1.01) but keep getting error 262 UPDATE FAILED
I can then recover to the tri-colour screen and process as far as RECOVERY SUCCESSFUL
But I cant get as far as updating the radio or whatever else it unlocks towards the end of the process and no new ROM loads (if that is what the unlocker does?) The percentage screen appears but doesnt progress at all. Then I get ERROR 262 again.
Is starting to the bootloader screen a sign of a bricked Hermes? I can get SERIAL to show and can get it to change to USB on that screen when I plug it into a computer but cant get any proper communication with the unit from the computer with that screen in place: ActiveSync obvoiusly wont start. As I left the 3A unlocker, it said RECOVERY SUCCESSFUL but does that necessarily mean that I have a brick now? I thought that the installation of olipro by SIM_CID unlock version 3A means that the unit is now hard-unlocked?
(Yes, I did try Hard-SPL-V7.zip but cant set up any communication between the exe file and the tricolour screen)
If you are using XP, untick "Allow USB Connections" in activesync. Put Hermes into bootloader and connect to PC. Run RUU_Wrapper.exe. Should fix the problem.
I thought that tricolour screen meant that it is ONLY starting in bootloader mode?
ultramag69 said:
If you are using XP, untick "Allow USB Connections" in activesync. Put Hermes into bootloader and connect to PC. Run RUU_Wrapper.exe. Should fix the problem.
Click to expand...
Click to collapse
I am a bit lost: How do I get into bootloader mode? I thought that it starting in the tricolour screen meant that it had started up in boot loader mode? Is there some combination of pressing buttons and 'on' switches like on my Blue Angel?
As it appears to have got stuck in a mode while in an upgrade process which didnt work when this error occurred, when I get it started, what should I flash to get the bootloader updated, the SIM and CID unlocked so that I can choose which ROM to flash? Should I continue with the SuperCIM_CID unlock or Hard SPL?
I have fully unlocked another Hermes before and have been playing around with ROMs but this one seems to have worked out differently: I was under the impression that loading OliPro meant that it was unlocked?
(Sorry about that answer: I will try RUU_Unwrapper.exe again)
ultramag69 said:
If you are using XP, untick "Allow USB Connections" in activesync. Put Hermes into bootloader and connect to PC. Run RUU_Wrapper.exe. Should fix the problem.
Click to expand...
Click to collapse
I did what you said and immediately I unchecked the tick in USB, I heard that the computer was establishing communication with the Hermes
But nothing I could do would let RUU_Wrapper.exe Run and communicate with the device. It just kept reporting NO DEVICE.
So I tried the super SIM and CID unlock again and it tried installing OliPro again and couldn't do so, saying that (having communicated with the device) it couldn't communicate with the device either. I tried retrying a few times with no success and pressing NO with equally no success. So I tried canceling out of the application. it thought about it for about three minutes and then simply started communicating, running the upgrade program. Now it starts the update process and I can see the progress.
However it stops at 21% and doesn't move any further. It has been that way for a few hours now. not sure if it is charging while connected, I suspect not and am wondering what to do now which wont brick the unit??
V7 still wont run but v3A still will!
ultramag69 said:
If you are using XP, untick "Allow USB Connections" in activesync. Put Hermes into bootloader and connect to PC. Run RUU_Wrapper.exe. Should fix the problem.
Click to expand...
Click to collapse
So I tried the super SIM and CID unlock again and it tried installing OliPro again and couldn't do so, saying that (having communicated with the device) it couldn't communicate with the device either. I tried retrying a few times with no success and pressing NO with equally no success. So I tried canceling out of the application. it thought about it for about three minutes and then simply started communicating, running the upgrade program. Now it starts the update process and I can see the progress.
However it stops at 21% and doesn't move any further. It has been that way for a few hours now. not sure if it is charging while connected, I suspect not and am wondering what to do now which wont brick the unit??[/QUOTE]
This is getting curiouser and curiouser: This device both will and wont coopeate at the same time. But nothing I could do would let RUU_Wrapper.exe Run and communicate with the device. It just kept reporting NO DEVICE on error 260\.
So I tried the super SIM and CID unlock again and it tried installing OliPro again and couldn't do so, saying that (having communicated with the device) it couldn't communicate with the device either. I tried retrying a few times with no success and pressing NO with equally no success. So I tried canceling out of the application. it thought about it for about three minutes and then simply started communicating, running the upgrade program. Now it starts the update process and I can see the progress.
However it stops at 21% and doesn't move any further. It has been that way for a few hours now. not sure if it is charging while connected, I suspect not and am wondering what to do now which wont brick the unit??[/QUOTE]
This is getting curiouser and curiouser: (Especially if you arent too petrified about bricking it) I can perform the recovery successfully from whatever I do but cant get v7 to communicate with the device. However 3A DOES still communicate but still gets stopped at 0% on the progress chart. Is this a known problem, that SuperSIM_CiD wont work with OliPro already installed at 1.40? That it WILL get stuck at 0% or 21%?
Now I cant hard reset either: I dont get the white screen, it just goes back into the bootloader, still showing IPL 1.01 and SPL 1.40 Olipro.
(Especially if you arent too petrified about bricking it) I can perform the recovery successfully from whatever I do but cant get v7 to communicate with the device. However 3A DOES still communicate but still gets stopped at 0% on the progress chart. Is this a known problem, that SuperSIM_CiD wont work with OliPro already installed at 1.40? That it WILL get stuck at 0% or 21%?
Now I cant hard reset either: I dont get the white screen, it just goes back into the bootloader, still showing IPL 1.01 and SPL 1.40 Olipro.
The computer IS communicating with the device (as I said it does give the 'ding' showing that the computer knows it is there) but it wont hard reset! It just goes straight to the tricolour screen immediately on startup. Even using a three hand method of pressing both buttons, pushing the reset in and putting the battery in at the same time gave the tricolour screen. And Windows Explorer cant get into the device. It seems to see it but there is no tree at all. So I cant use the Post 1160 method to flash from an SD card.
Even more baffling, i have now flashed a stock ROM successfully and v7 STILL wont communicate with the Hermes!! In desperation I even moved the directory to the root of C: Are some of these devices encrypted differently from others? So suddenly it boots properly and I immediately did a hard reset and erased everything and now Guess what? It hangs at the Windows Mobile screen! Needing a hard reset all over again
Should I just keep on trying Super SIM and CID unlock again and again until it works? (I assume that I have no longer got OliPro on it, though it does show a SPL of 1.40) There must be a way of unlocking this unit but this total non-cooperation doesn't seem to be covered in the Wiki. Is there a version of the Hermes like the Wizard which is more difficult to unlock than the others?
Sorry to reply again when no one gave any ideas on my last posting but I am wondering, horror of horrors, whether this might be a hardware problem?
I am now stuck at the tricolour screen ( 1.01, SPL 1.40.Olipro)) which turns on whenever I put the battery in. Connecting to the computer doesnt make any difference and obviously I keep getting ERROR 260 which seems to be a connection error meaning that the computer either isnt connected to the device (or that some software is conflicting somewhere, which is unlikely as flashing to the stock ROM did work before I tried to run V7 again)
Is there any possibility that running SuperCID&SIM unlock (which has never completed) caused all of this and is there any rescue procedure or should I just assume that this is a hardware problem now (or should I do a fresh posting)?
Is it inherently suspicious that tricolour turns in when I just put the battery in AND that even though SERIAL changes to USB on the Hermes, running the v7 hard update utility causes ERROR 260? [Or cant you run V7 when you already have OliPro installed somehow?]
There IS communication: Though I reported in my last posting that I could flash the Cingular ROM, flashing to the Cingular ROM now gets consistently stuck at 14%, sometimes with an ERROR 264!