I have an old Hd2 (512mb) with a broken screen sitting in a draw. I had installed WP7 on it.
Looking at making this a back up phone if I can install android on it.
Trouble is since managing to get back to wm6.5, I have lost MAGLDR and spl now says 3.03.0000 instead of saying slp2.08.hspl as it did before. Also now I can not flash anything as it either have a crittical error and stopping (phone goes to % done screen then sits on 0% till crash alert on pc hits). I have tried flashing from the sd card and it goes to the white screen and says loading... then sits there.
Current specs
OS 5.2.21913 (21913.5.0.94)
Rom Ver. 3.14.4052.2 (04666)WWE
Radio 2.15.50.14
Protocol Ver. 15.42.50.11U
PB81100 HX-BC
SPL-3.03.000 XE
MicroP(LED) 0x05
MicroP(Touch) 0x30
Ok question is ... is this phone recoverable and how?
Many thanks in advance.
moved to general section. Booting a SD built from WM + clrcad+ haret is an option for you? there is a few roms GB, ICS even JB roms there ...
phone into bootloader - connect usb - run hspl4 - choose 2.08.hspl - back into bootloader - flash magldr
Thanks for the advice but already tried this.
Get all the way to installing then sits for 30sec and get critical error
more info
What is happening ...
phone connects & operates fine in wm6.5
phone connects via usb no problems both sync & hard drive modes work.
start hspl or any other flash app & it works detecting phone & spk version on it
goes to bootloader fine.
bootloader goes into usb mode fine
THEN bootloader either
with hspl bootloader becomes unresponsive/frozen, error message:
Critical Error
Flow: 00000006
Error Code: 00000011
Description: Unknown
with Rom/Radio/MAGLDR flashing will make it to the progress bar screen the sit on 0% until update error
After this need to do a soft reset or remove battery to restart phone, it then boots up into wm6.5 working fine.
don't start with winmo running, , the usb connection times out while the phone is rebooting.
Put the phone manually into bootloader, - connect usb - wait for serial to become USB and THEN run hspl.exe
perplexing
ok just tried this same results
I don't know what to think anymore about this as everything works upto the point that it actually flashes the software.
Even when I move the img file to th sd card and try to install from there it gets to the white screen then says loading... and freezes without bringing up fash or quit options.
Surely since its still working theres a way to make it flash again?
things that come to mind...
the OS on your PC can sometimes cause problems, , especially (but not always) 64 bit windows. If theres another pc in the house, try it.
corrupt usb drivers, if you;ve had the usb cable in teh same usb port all along, change it for a new one, and use a back mounted port, not a usb slot in eth front of the case (assuming a pc not a laptop)
corrupted spl of some kind. worry about this possibility later.
-
For me, the next steps would be:-
try another pc
then
try an sd card flash of the (correct) stock rom
then
report back
Success now halfway ...
Thanks for the help, finally got hspl, magldr and custom wm6.5 rom. Problem was with laptop 64bit win7, pc 32bit with virus scanner obstructing.
But all fixed now.
Now just have to find an android rom I want, figure out cwm ext4 ??? out. Radio 2.15 is bad, Radio 2.12 good then Radio 2.15 good ??
Got some figuring out to do nand vs sd, partition formats etc heads spinning again.
At least the phone is flashable again
Desire DL installed
Thanks for all the help. Finally got there android now installed on hd2. Very impressed. Will make a good back up for my one x.
Related
hi
guys i am newbie in upgrading and tried to run athena wraper and it died and after searching forums i still cant find cure ok so here it is i can do hard reset but it dosent help no boot up it still gives me ring round joystick good news is i can get it to bootloader screen (or at least thats what i think ) its red green blue and white screen with usb or serial (depending on cable )
screen reads
ATHE100
IPL-V0.90
ATHE100
SLP-V1.20.Olipro
now can any one help me ??
how can i upgrade rom with out device being detected by active sync every time i run upgrade utility it just comes up with connection error
still no luck
hi
still no luck
do i need special drivres to detect device if its in bootloader ?
it dosent show any thing in device manager when i connect it while its in boot loader
on running upgrade utility it comes back with error 260 connection error saying cannot find device (i am stuck in bootloader)
any advices ??
please help !!!!
The fact that you can still enter the bootloader means that it is not bricked, so first advice would be, as is so well presented in the Hitchhicker's Guide to the Galaxy, "Don't Panic".
Enter bootloader without any SD Card or SIM left in the Athena.
Then, plug it to the USB port, and see if it goes from "serial" to "usb".
Then try to flash first the Black Dual PK ROM available on the forum (in the WM6 section), or an official ROM available from the Wiki, for instance.
hi
tried to flash it with both and came out with same error
260 connection cant find device
and i cant even see any changes in devicemanager but it dose goes serial to usb when i connect
and my pc is not detecting the device (just like that depressed robot from hich hikers guide to galaxy )
Do you have Windows XP or Vista ?
Ecraseur said:
Do you have Windows XP or Vista ?
Click to expand...
Click to collapse
xp (pc i am trying to upgrade i also have vista on other pc which i havent tried yet should i try that ?)
nop no luck in vista ether same error still no connection
both pc have netframework 2
activesync in xp and mobiledevice center in vista
but after connecting device nothing happens in device manager there is no new device
(could it be beacouse of faulty cable? )\\(noi have tryed 2 different cable )
is it worth getting cradle ??
No no. I think the problem comes from the flash utility that requires that the Athena be detected prior to flashing.
I know that with the Universal, some flashing utilities could force flashing when connecting the device already in bootloader mode...
So there must be an easy way to bypass the device detection and go on with the flash process. I'll try and find out, and maybe one of the gurus will cruise by and find it for ya in the meantime.
In the meantime, don't freak out and be patient. Your Athena's not bricked, probably the ROM that's screwed up. We only need to find a way to do that exclusively from the bootloader (chich I know is possible, that's the whole point of the bootloader ).
vijay5264 said:
nop no luck in vista ether same error still no connection
both pc have netframework 2
activesync in xp and mobiledevice center in vista
but after connecting device nothing happens in device manager there is no new device
(could it be beacouse of faulty cable? )\\(noi have tryed 2 different cable )
is it worth getting cradle ??
Click to expand...
Click to collapse
Hi
Try a hard reset ( Volume down+reset) and then get into the boot loader(Camera+reset~10seconds) then flash the PK dual rom. Don't panic, Your athena is hard spl patched therefore not bricked. If that not works down load the exact official rom for your device flash that then flash the PK dual rom. try Redownload the rom again.
Good luck
HeartOfDarkness said:
No no. I think the problem comes from the flash utility that requires that the Athena be detected prior to flashing.
I know that with the Universal, some flashing utilities could force flashing when connecting the device already in bootloader mode...
So there must be an easy way to bypass the device detection and go on with the flash process. I'll try and find out, and maybe one of the gurus will cruise by and find it for ya in the meantime.
In the meantime, don't freak out and be patient. Your Athena's not bricked, probably the ROM that's screwed up. We only need to find a way to do that exclusively from the bootloader (chich I know is possible, that's the whole point of the bootloader ).
Click to expand...
Click to collapse
hi
thankes i think u understood the problem it is utility which fails before even starting beacouse of no connection see if u can find any thing
and yes i tryed hard reset and then tryed to flash with project black rom and i have downloaded latest t mobile rom from oficeal website but as i said before it fails with connection error it starts up and box says ''verifying information on your pda fone please wait'' and minut later it comes up with error 260 connection error '' please check following
1 your pdafone is connected to usb cable /cradle
2 usb cable connected to pc
(wich is basicly same if you try to nrun upgrade with out connectind pda )
(and yes i have tryed it with 2 different cables and it dose change from serial to usb)
some ting intrestin i foun in orignal update utility faq
ERROR [260] : CONNECTION
This error occurs when there is an “open port error” before upgrading the CE ROM image.
Solution: You can reset the device and run RUU again. If you still encounter an “OPEN PORT ERROR” again, reset your computer and try again.
is possible because device is in bootloader ?
or am i doing some ting wrong?
Reboot your PC, make sure you are not using a USB hub, try it with each USB port on the PC.
Pantaloonie said:
Reboot your PC, make sure you are not using a USB hub, try it with each USB port on the PC.
Click to expand...
Click to collapse
good idea but dident work after 4 on board ports and 2 hub ports no joy at all
by looks of it upgrade utility is trying to read info from my device and could be failing for 2 reasons
1 it is not detecting device
2 info in pda is corrupted and could not get any info from device
well thats my theory but not really sure any suggestions??
Is your PC running XP or Vista? I got the impression reading the post that XP machine works better in unlocking. I think the info was posted by Olipro himself if my memory is right.
eaglesteve said:
Is your PC running XP or Vista? I got the impression reading the post that XP machine works better in unlocking. I think the info was posted by Olipro himself if my memory is right.
Click to expand...
Click to collapse
it is running xp the one i am working on now (i do have 2nd pc running vista 64 bit )
but i am doing unlocking in xp
all i want to find out is dose device needs any drivers or dose it gets detected if device is in bootloader ?
if thats the the case i dont see any new devices in xp devicemanager
No no, it doesn't. Couldn't find it for Athena, but don't have much time lately, alas.
Maybe you should PM one of the gurus asking how to flash a ROM straight from bootloader without having the device detected by WinXP. I believe there's a small, easy manipulation to make, but can't remember it for the life of me. :-S
HeartOfDarkness said:
No no, it doesn't. Couldn't find it for Athena, but don't have much time lately, alas.
Maybe you should PM one of the gurus asking how to flash a ROM straight from bootloader without having the device detected by WinXP. I believe there's a small, easy manipulation to make, but can't remember it for the life of me. :-S
Click to expand...
Click to collapse
i found this in wiki and first three posts are empty but followed the procedure and downloaded all three roms and still no joy error
''Problems using the Athena Unlocker - the Black Screen of Death
Using The Athena Unlocker tool (developed by Olipro) is a 3-stage process. Most users get through the first stage but as they start stage 2, get a black screen where their device becomes unresponsive and so cannot proceed with the unlocking. See these posts
http://forum.xda-developers.com/show...&postcount=169 or http://forum.xda-developers.com/show...&postcount=176 or http://forum.xda-developers.com/show...&postcount=226
It is always recommended that you first take out your MiniSD card. You can then follow the instructions below.
* Get one of the ROMs in this link and extract it http://forum.xda-developers.com/showthread.php?t=314672
* Get your device into bootloader (the three-colour screen; You can get there by pressing the Camera key + Volume key + Soft Reset at the same time)
* Connect your device to your PC (even if the PC shows no sign of recognising it, it does) and the SERIAL shown on the screen of your device will change to USB)
* Hit the ROM Upgrade Utility and upgrade your device.
* Once the upgrade is completed, configure your device (Calibrate screen, set time zone, etc).
* Now continue with the Unlocker, to the end.
It is important to complete the unlocker to the end or else you will miss out on flashing your radio, with a common symptom of your gps not working.
Good Luck and enjoy your improved device!
''
now i am still stuck will it make any difference if i try it in different xp pc other then the one i started the process ?(and screwed it up)
Please ensure all software firewall or IP filtering apps are turned off then reboot the PC. After rebooting, confirm the apps are not running and blocking anything. If you are unsure, then try it from a freshly installed XP.
Put the device in Bootloader mode and try it again.
lpsi2000 said:
Please ensure all software firewall or IP filtering apps are turned off then reboot the PC. After rebooting, confirm the apps are not running and blocking anything. If you are unsure, then try it from a freshly installed XP.
Put the device in Bootloader mode and try it again.
Click to expand...
Click to collapse
good idea
i have already tryed with firewalls and virus protection off but doing it in fresh xp might just work small question do i need to install active sync or is it not needed (any way ill try both first without and then with )
ill report back in about 3 hours (i know i am sad and havent got a life but its worth a try )
Yes, the wiki confirms what I thought but didn't voice out loud as yet (I was sure about it for the Universal, but not for the Athena): the upgrade utility doesn't *require* that it be Activesynced. That's, as I'd said, te whole point of the bootloader.
If you still have problems uploading the new ROM to your Athena after following the wiki thing, then it *does* mean that there is some external factor playing dirty, so the firewall to check (and some anti-virus software also scan network connections) indeed is a good idea.
Keep us posted, and I'm keeping my fingers crossed.
First off, I have read every thread mentioning error 260, every wiki about upgrading, and have not been able to fix my problem.
I am trying to upgrade to Schap's newest 6.0 ROM, not the 6.1. I currently have the OEM 5.0 ROM that came on the device from AT&T. I can connect via activesync perfectly. No issues there at all. When I run the upgrade program, it gets all the way to the status bar showing 0% or 1%, then the phone and computer disconnect the activesync connection, the phone goes back to the today screen, and my computer shows error 260.
I have seen posts saying I need to install HardSPL. I tried that and get error 260 there also.
I have seen posts about installing JumpSPL, I tried that and it only locks the phone up. I must do a soft reset to bring it back to life.
I found the instructions on upgrading the ROM via the SD card. I followed those and renamed the .nbh file and copied it to the fat32 formatted sd card in the phone. Where do the rest of the files go??? The .nbh file cannot possibly contain the entire rom, right? The instructions leave that part out from what I can see.
Help!
Device is a AT&T 8525. Thanks!
okeven said:
First off, I have read every thread mentioning error 260, every wiki about upgrading, and have not been able to fix my problem.
I am trying to upgrade to Schap's newest 6.0 ROM, not the 6.1. I currently have the OEM 5.0 ROM that came on the device from AT&T. I can connect via activesync perfectly. No issues there at all. When I run the upgrade program, it gets all the way to the status bar showing 0% or 1%, then the phone and computer disconnect the activesync connection, the phone goes back to the today screen, and my computer shows error 260.
I have seen posts saying I need to install HardSPL. I tried that and get error 260 there also.
I have seen posts about installing JumpSPL, I tried that and it only locks the phone up. I must do a soft reset to bring it back to life.
I found the instructions on upgrading the ROM via the SD card. I followed those and renamed the .nbh file and copied it to the fat32 formatted sd card in the phone. Where do the rest of the files go??? The .nbh file cannot possibly contain the entire rom, right? The instructions leave that part out from what I can see.
Help!
Device is a AT&T 8525. Thanks!
Click to expand...
Click to collapse
Try a different USB port first, fire the device into bootloader mode manually and see if the device is detected by windows as "HTC USB SYNC"........use a hardwired port NOT a USB Hub aswell.
I tried a different USB port. It is not being plugged in to an external USB hub. I went into the bootloader screen and my computer makes the sound that a USB device was plugged in and it does show in the device manager as "HTC USB SYNC". What now?
Now try to do an update, Sounds like a problem associated with the connection of the device to your machine...usually caused by messed up USB drivers or a conflicting program.
Just tried. Same error again. Tried restarting the computer and tried it again. No dice.
this is the answer
hey man, how u doing. I was getting those errors too, I actually have a Tilt, I got error 200, and 260 trying to change my rom, I was about to give up. then I tried something I didn't think of, I updated my device center software from Microsoft and then miraculously everything worked after that. If you have XP update your Active sync software to the latest one and everything should work after that. Hope this helps.
and one more thing, make sure you install HardSPL v1 (or later when its released) first before trying to install the ROM.
I don't think anything is wrong with your usb drivers
I had actually checked to make sure I had the most recent version already and I do. I cannot install HardSPL either, since it gives me error 260 there also.
Error 260 is an open port error... I believe you have already tried resetting your device, but have you rebooted your pc prior to this procedure... I am grasping at straws for you, since you said you have tried soft resetting to no avail... I believe MrVanx stated to put the phone in bootloader mode and try to run the update utility that way... It works for me...
Can you try this on a different pc? If so, does it work? I have a post on another forum that you might find interesting... I did not compile it on my own, but cannot recall where I got it from... anyway, the link is HERE...
Hope this helps you out...
I have restarted the computer multiple times. I just tried it on my laptop and that did not work. I can boot the phone to the bootloader, but how do I install it from there?
That should be the easiest part... once you have it in bootloader mode, connect it via usb and then launch the update utility...
I get error 260 doing that also. argh!!!
i know how u feel
i had your problem several times. you want to know how i fixed it?
i didn't...
first i tried everything you and the guys mentioned and... nothing. then it worked the next day by itself.
the second time i couldn't connect i was really mad because the errors came sporadically. i tried installing AS, uninstalling, hard resetting the device, changing usb ports, anything logical and illogical and it worked on changing usb ports (but not on the first change).
now i'm at my girlfriends, had no problems until i saw farias new rom and wanted to flash it. guess what connection error
p.s. i've read trough and trough, but i've found no solution
what version and OS?
okeven said:
I get error 260 doing that also. argh!!!
Click to expand...
Click to collapse
yeah, I thought u would dget that again. i don't believe the error is originating from your phone, its more from the computer. what operating system are you using and whats the version number for activeSync or MS Device Center you are using?
I had that error on my home pc and on my girlfriend's laptop prior to updating my device center software. My pc is running Vista ultimate x64 and my girlfriend's laptop is running Vista Home Premium x32. I'm on her laptop right now, the version of device center is 6.1.6965. when I get home I will see which version is on my computer, I remember seeing "beta" on the one I got at home, lol, I didn't know Microsoft sent out beta software through its msupdate.
okeven, someone replied with good suggestions to the thread that u accidentally started over in the kaiser forum. you might want to check that out
I have version 6.1.6965 also. It does not say anything about it being a beta version, but with Microsoft, isn't everything in beta stage?
I did try the "official wm6 AT&T" version. Upgraded just fine. Tried upgrading to another one. Failed with error 260. What is different with the official upgrade program compared to the unofficial ones. THAT is the problem.
help
hi guys,
i have the same problem always the code 260, and also, my tytn's screen become within light, and without any boot number, ni radio, anything appears, please help me,,
thanks,
Finnaly
Hi guys
I also have the 260 problem but i resolved it:
1º- connect pda and make a active sync connection
2º run RUU
3º the 3-color screen will appear and update will stop with the 260 message error. be sure you can install the "qualcomm cdma technologies msm driver" at this moment, by an internet connection.
4º after the driver is installed, the word "USB" will appear in the white strip of the 3 color screen;
5º run RUU again and that´s all!
I´ve tried it in windows 7 ultimate 32-bit
hi,
I had the same issue on my second flash... I resolved it by ignoring all .exe's (which I like in general).
So I copied the .nbh onto the card, renamed to Kovsimg.nbh, bootlader mode, done
cheers
lxlx said:
hi,
I had the same issue on my second flash... I resolved it by ignoring all .exe's (which I like in general).
So I copied the .nbh onto the card, renamed to Kovsimg.nbh, bootlader mode, done
cheers
Click to expand...
Click to collapse
Hermes use HERMIMG.nbh ... kovsimg.nbh is for Xperia X1 ..
Hi gys, I think that this is my first post, but I want to share some solution for with you. The most important think with "connection" errors is to have HSPL installed correctly. I was trying to install on my HD2 universal ones, like Hard spl v7 and 9, but problems occured. So after trying everything, I found HSPL (on this forum) just for HD2. After that, everything wass like a charm
Hi,
I have had my 8125 for about 2 1/2 years now, love it!. Just the other day, it started locking up and giving me the white screen of death.
I tried to flash it with a rom, and it got to 99% and then lost connection. Tried to do the recovery, but that failed too.
I have found alot of good information from the smart and wonderful people on this forum and tried a bunch of stuff.. but I am now stuck.
Now, I can always boot into the bootloader, and it says USB over the left softkey, but no apps can connect to the phone.
I tried to use other RUU roms, HardSPL, SoftSPL, etc...I tried to unlock my CID using the thread in this forum, but SoftSPL couldnt connect to the phone via USB.
All apps error with "error unable to connect to device."
I have read the forum about having a bad mimi-USB port, but I dont think thats my case.
Please help! I am pretty close
Dell D620 CoreDuo 1.8Ghz; WinXP SP2
ActiveSync 4.5
IPL 2.25.0001
SPL 2.25.0001
end123 said:
Hi,
I have had my 8125 for about 2 1/2 years now, love it!. Just the other day, it started locking up and giving me the white screen of death.
I tried to flash it with a rom, and it got to 99% and then lost connection. Tried to do the recovery, but that failed too.
I have found alot of good information from the smart and wonderful people on this forum and tried a bunch of stuff.. but I am now stuck.
Now, I can always boot into the bootloader, and it says USB over the left softkey, but no apps can connect to the phone.
I tried to use other RUU roms, HardSPL, SoftSPL, etc...I tried to unlock my CID using the thread in this forum, but SoftSPL couldnt connect to the phone via USB.
All apps error with "error unable to connect to device."
I have read the forum about having a bad mimi-USB port, but I dont think thats my case.
Please help! I am pretty close
Dell D620 CoreDuo 1.8Ghz; WinXP SP2
ActiveSync 4.5
IPL 2.25.0001
SPL 2.25.0001
Click to expand...
Click to collapse
Ok,first,no other custom build rom will flash on it,except official stock rom of the carrieror,however, you can try wizard_love rom,as it has patched IPL/SPL (Bootloaders),so don't try to flash any other custom build,as its a G4,custom rom can only be flashed through SoftSPL or HardSPL.
Download official carrier's stock rom and wizard_love rom.
Secondly,
1.Disable activesync or rather uninstal it altogether,as its not needed during flashing a rom.
2.End process 'wcescomm.exe' in the 'windows Task Manager.
3.Clear and delete the 'Temp Folder' files
4.Run 'Disk Cleaner'
5.Disable all Anti Virus and Firewall.
6.Try to stop/disable all running programs in the background via 'Task Manager'
7. Get the battery fully charged,as many comm errors are due to weak or discharged battery.
After doing all this,get the phone in Bootloaders before connecting with pc via usb cable,there shudn't be any usb at the bottom of the Bootloaders,now connect with pc and check if usb appears at the bottom,if its there than,its establishing connection,go ahead and run official stock or wizard_love rom.Don't use the pc or play games or check emails,don't even do any word,excell or any office application.Check if any application/program interferes with the flash,either disable or remove that program.
Does the battery get charged through usb cable ? verify it.
If after getting the phone into bootloaders and connecting through usb cable,small usb doesn't appear,it means there's a connectivity problem,replace the usb cable and verify it again.Even try with another pc with winXP or change the usb input port of the pc ,put the usb cable in some other usb port on the pc.
Apart from all these,I don't find any reason for not getting the flash completed
Hi,
Thanks for the help.. I tried the wizzard_love rom, and then went to the NBD_v8.3 /w TouchFlo rom and thats awesome!
my biggest issue was not able to connect to the device although it looked like it should have.
on another thread someone said to leave the battery out for 5 mins. I did that and all of a sudden it started to connect consistantly.
After that I did the HardSPL and started flashing and all is well..
Thanks for your help!!!!
wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeForBeginners
i followed it very precise after reading evrything through twice..... and when i run " Easy Hard-Spl v7 beta v0.1" it says: "ERROR[260]:Connection. the update utility cannot connect to your PDA phone. please check that your usb cradle/cable is connected properly between the PC and your PDA phone. check the following, 1that the PC is connected to the PDA phone, 2 that the PDA phone is connected to the pc".... and it is... so what have i done wrong?
260
make sure you dont have the sim card in i have gotten that error from that also you may want to try and flash a stock rom first if you cant find it heer go to either your carriers web site or HTC their sight has many stock roms. ive been doing this a few years now but i am no where as good as most of the ppl here. good luck
didn't work, and now i tryed to do that pc sync as well ono doesn't work
do u have active sync or windows devive center on your computer ? have you been able to connect and view files on the phone through your computer using any of these programs? if so have you gone to htc and tried to flash the stock rom? you must remove sim card and memory card. next do a hard reset use the stylist and stick it into the tiny hole just to the right and slightly above the usb port then follow the instructions on the screen. after that connect the phone to the computer and link to active sync. then reinstall the stock rom. let me know how that works after that you should b able to flash hard spl then download it and just open it on computer it will install on the phone by itself dont load on memory card or phone memory directly let it do it through the computer.good luck let me know how you make out good luck
ps i know it may sound silly to reinstall origonal rom but sometimes there can be a corrupted file preventing you from upgrading, and its good practice lol
Does your phone can run the windows?
I mean does your pphone boots correctly?
or it is in the tricolor screen?
if it works, why you are trying the that new HSPL?
use the olipro version V7
be sure your PC has netframeworks 3.5, your phone dont has the storage card, have enough battery, good usb cable, and Windows XP.
if your device cant boots and its in tricolor screen... please search in the wiki to your country Stock rom and falsh it.. once it boots... apply the HSPL
+ Que PPC...
as you are the master of the hermes maybe you can help me i have a herm 100 that wont get past the screen align on any rom. you tap the X in the corners then it comes right back. i think it may be the radio but i cannot find anything that will work and stock rom doesn't go past 11% on install. spl 1.40. olipro ipl-1.01 m 05 s 04 B o6 . it does connect to active sync and i can open all the folders in it. all the links to radios are dead and i think i have to down grade spl first to install radio but i cant find that. anny help would be great. ive flashed the hell out of my fuse kaiser and pure and no problems but i rely liked this old phone and want to bring it back to life
im having problem with installing any rom... even stock rom cannot be installed. I have HSPL 2.08 installed. I can enter bootloader. The installation of rom goes through the version check window and then when i hit flash button it shows 0% and after 10 secs pops out window with error code 266 that it cannot get response from the device.
I also tried flashing from the stock sd card (2gb, FAT32 formated) with the stock nbh file renamed to leoimg.nbh but when i enter bootloader mode nothing happens and im stuck on the three coloured screen. I really dont know where's the problem.
I have already had several WM6,5 roms installed... i have tried WP7 and currently i have NAND Android and Magldr 1.12 and nothing happens even if i want to update it to 1.13. Only flashing that works is flashing SPL/HSPL. It works without any issues...
If anyone have an idea i would be very thankfull, because i have tried almost everything.
Please post the spl line from bootloader. Go look, don't just assume it's still what you think it is.
it shows:
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x50
janox1x2x3 said:
im having problem with installing any rom... even stock rom cannot be installed. I have HSPL 2.08 installed. I can enter bootloader. The installation of rom goes through the version check window and then when i hit flash button it shows 0% and after 10 secs pops out window with error code 266 that it cannot get response from the device.
I also tried flashing from the stock sd card (2gb, FAT32 formated) with the stock nbh file renamed to leoimg.nbh but when i enter bootloader mode nothing happens and im stuck on the three coloured screen. I really dont know where's the problem.
I have already had several WM6,5 roms installed... i have tried WP7 and currently i have NAND Android and Magldr 1.12 and nothing happens even if i want to update it to 1.13. Only flashing that works is flashing SPL/HSPL. It works without any issues...
If anyone have an idea i would be very thankfull, because i have tried almost everything.
Click to expand...
Click to collapse
Have you tried a different USB port or a different computer? If this does not work try another USB cable. As far as flashing from SD make a copy of your SD card on your computer and reformat it.I know you said it was already Fat 32 but sometimes it helps to theroughly clean your SD card, this is what reformating it will do. Once you have it reformated just put the ROM on it and try flashimg it again.
so i have finally fixed the problem. The problem was very simple. ROM flash utillity doesn't support USB 3.0 but anyway i don't understand why flashing with sd card doesn't work because i have tried several sd cards with various size.
janox1x2x3 said:
so i have finally fixed the problem. The problem was very simple. ROM flash utillity doesn't support USB 3.0 but anyway i don't understand why flashing with sd card doesn't work because i have tried several sd cards with various size.
Click to expand...
Click to collapse
It is not that it does not support USB 3.0.The problem was that your HD2 drivers cor the USB port you were using were most likely either nolonver correct or corrupted. This is a common probblem for some reason. Maybe samsamuel can post here again and explain it a little better. Glad you got your HD2 up and running again.
T-Macgnolia said:
It is not that it does not support USB 3.0.The problem was that your HD2 drivers cor the USB port you were using were most likely either nolonger correct or corrupted. This is a common probblem for some reason. Maybe samsamuel can post here again and explain it a little better. Glad you got your HD2 up and running again.
Click to expand...
Click to collapse
well im no engineer, but each usb port installs drivers individually for anything you plug in, so port 1, it installs the hd2 drivers, port 2, it installs them again, and sees them as two seperate instances. if you then mess with android, say, and/or wp7, and mtty, you replace those drivers with other drivers, but only for that port, so you can potentially end up with three sets of different drivers on three different ports, so you try something that requires winmo drivers, and the pc is trying to use the ones tweaked for mtty.
Only a theory, thats what usb does, whether thats really the problem, who knows. makes sense to me, so im sticking to it. ALways pays to find the device in hardware list and uninstall it now and again, including 'remove drivers'.
That being said, there could be something in the usb 3 theory in this instance.
well i cannot argue with you guys, because you might be right. But i tried two different USB 3 ports with the exactly same result and failed then i tried USB 2 port and succeded without any problems so maybe there's something about it