I got this phone today, made some trade, and when I put in my sim card, it says no service, when I turn of the phone mode, it cannot be turned back on, and when its on, it says "no service", and the same sim card in the same location works fine, so what can I do? Will installing a new ROM fix this or should I give this phone back?
Just restarted the phone, says: "The SIM card is not valid.
You can still make emergency calls if your service provider supports it."
Same thing happens when there is no SIM card inserted.
you should remove the sim card and sd card and go through the entire first post of the tutorial thread linked in my signature.
start with mtty and a full format of the device using the line "task 28 55aa".
then downgrade to wm2003, including flashing the old radio and extrom, then resize the extrom and upgrade the rom and the radio again.
that way, your device was entirely empty for once, then you start again from the beginning. it might take 2 hours, but after that, it should fully work again.
or, at least you will know, if it is a hardware defect
It was a hardware defect, those metal contacts that reach the back of a SIM card we're screwed up, I guess, so I took a small screwdriver and kind of lifted them up for a better contact, and surprise, surprise, it worked.
Thank you for your reply, anyway.
Chef_Tony said:
you should remove the sim card and sd card and go through the entire first post of the tutorial thread linked in my signature.
start with mtty and a full format of the device using the line "task 28 55aa".
then downgrade to wm2003, including flashing the old radio and extrom, then resize the extrom and upgrade the rom and the radio again.
that way, your device was entirely empty for once, then you start again from the beginning. it might take 2 hours, but after that, it should fully work again.
or, at least you will know, if it is a hardware defect
Click to expand...
Click to collapse
LOL "task 28 55aa" what is this??? "task 28" will already do!!!! "55aa" is absolutely unnecessary and will be ignored
As same as "task 28 1111" or "task 28 abcd"... doesn't matter!
55aa reparts the extrom as far as i know. at least to my experience. i usually use task 28 to wipe the device before flashing, but once due to the "no service" issue i used task 28 55aa to restore the original partitions.
Chef_Tony said:
55aa reparts the extrom as far as i know. at least to my experience. i usually use task 28 to wipe the device before flashing, but once due to the "no service" issue i used task 28 55aa to restore the original partitions.
Click to expand...
Click to collapse
if you believe that
USB>rtask 0
Radio reset.
Click to expand...
Click to collapse
Or use this
Tnx for all ur help, but I quickly resolved a problem, didn't thought to do that in the first place. Anyway, battery seems really weak, it was about 50% when I went out biking and after an hour and a half of listening to music, it completely dried out. Backup battery was 100%, but still, the phone was off and was unusable. How do I switch to backup battery and should I? I'm really new into this.
what do u mean under:
USB>rtask 0
Radio reset.
RaZzor_Shine said:
what do u mean under:
USB>rtask 0
Radio reset.
Click to expand...
Click to collapse
which radio rom you have installed?
d-two said:
which radio rom you have installed?
Click to expand...
Click to collapse
Believe me i don't know i installed over your updater and thats all.
d-two said:
which radio rom you have installed?
Click to expand...
Click to collapse
i found out it's 1.00.0
RaZzor_Shine said:
i found out it's 1.00.0
Click to expand...
Click to collapse
Then please update to 1.15
you can find it here http://forum.xda-developers.com/showpost.php?p=7733172&postcount=3
d-two said:
Then please update to 1.15
you can find it here http://forum.xda-developers.com/showpost.php?p=7733172&postcount=3
Click to expand...
Click to collapse
It says it is not for my device.
RaZzor_Shine said:
It says it is not for my device.
Click to expand...
Click to collapse
put the device into bootloader mode and check again...
Related
Hi all. I'm trying to flash my XDA2s back from the iMate Rom to the original 02 image.
I have the .nb1 file on my computer. I let the handset sync using activesync. Then double click the image. It loads up the 'XDA OS Image Tool' which seems to work fine.
Then a command prompt widow pops up and says:
'ERROR: GetDeviceData - unspecified error
error getting devicedata'
Programme A v1.09 pops up and eventually an error message tells me
'cannot execute the remote communication program. Please make sure the USB/Serial cable is properly connected'
Any ideas? I'm a bit of a n00b still with this stuff and I reeeeaaaally need this returned to the original rom image.
cheers - Mike
mike freegan said:
Hi all. I'm trying to flash my XDA2s back from the iMate Rom to the original 02 image.
I have the .nb1 file on my computer. I let the handset sync using activesync. Then double click the image. It loads up the 'XDA OS Image Tool' which seems to work fine.
Then a command prompt widow pops up and says:
'ERROR: GetDeviceData - unspecified error
error getting devicedata'
Programme A v1.09 pops up and eventually an error message tells me
'cannot execute the remote communication program. Please make sure the USB/Serial cable is properly connected'
Any ideas? I'm a bit of a n00b still with this stuff and I reeeeaaaally need this returned to the original rom image.
cheers - Mike
Click to expand...
Click to collapse
Hi Mike,
Suggest you download the latest O2 Spec Complete shipped ROM, unzip it into another folder, add MaUpgradeUt_NoID and use this method instead. This should give you a completely standard O2 ROM..
More information can be found here:
http://wiki.xda-developers.com/index.php?pagename=BA_1.40.00_Upgrade
Let me know how you get on..?
Cheers,
PC
Cheers for the quick reply!
The thing is, its kinda on its last legs (whistling screen, loose stylus, rubber seal under screen coming out, dodgy down button, didn't enjoy my trip to poland etc) so I predict it will meet its end in the next couple of weeks and I'll need to pull an insurance job. I need to make it so they can't tell that I flashed it or it invalidates the insurance cover. Will they be able to tell if I flash it with the new 02 ROM that isn't the original?
mike freegan said:
Will they be able to tell if I flash it with the new 02 ROM that isn't the original?
Click to expand...
Click to collapse
Hi Mike,
My guess is as long as it's an original O2 ROM (that, quite rightly, would have been available to you anyway) they shouldn't have any issue..
One thing that would be a problem is if you have ever upgraded to WM5 and unlocked/unhidden your ExtROM as this would forever be known as your ExtROM wouldn't have a password..
My feeling is that provided you've never updated in this fashion, you'll be ok..
Others - Feel free to comment if you know different..?
Then again, if you're going through the Insurance where the phone has been dropped (off a Building, for example) where they had no ability to see it working, they'd be none the wiser, would they..? :wink:
I sure hope not I did upgrade to WM2005, and then back again, but I can't see an extended ROM anywhere.
mike freegan said:
I sure hope not I did upgrade to WM2005, and then back again, but I can't see an extended ROM anywhere.
Click to expand...
Click to collapse
Did you re-size the ExtROM, etc using the following procedure..?
Wiki said:
If you have not unhided and unlocked your Extended ROM yet
copy xda-developers_Unlocker.cab from the "Preparation\ExtROM unlocker - WM2003SE" folder to your device.
install it by tapping on it in filemanger
then go to start -> Programs -> ExtROM tools -> then first run "unhide", then "Unlock". Do a soft reset.
Setup the Storage size to get a full 60MB and not 43 MB
Copy Repart_DOC.exe from the "Preparation\DOC repartitioning tool" folder to your device and launch it.
Set size of Extended ROM to 128 kb (or a bit more, if you want a NOT working extended ROM)
Press "Format now!" and wait until it is done (A few seconds). You will see a message that it is done.
Soft reset.
You will get an error message about your storage, just press yes and wait a few seconds
Click to expand...
Click to collapse
Unless I'm mistaken, this process will change the password for the ExtROM..
Can others advise..?
Cheers!
D'oh, I can't remember! I recall setting the ext. rom to 128kb so I probably did. Darn.
i wonder if anyone could help me with my problem!
i can't upgrade / Install RADIO ROM (any) in my UNIVERSAL. what happens is that it doesn't starts and when rebooting it says NO GSM where the versions are mentioned in red.
my universal goes in the bootloader mode properly and the update or RADIO ROM Starts; but it stays on 0% and doesn't move ahead. after a while and error comes ERROR 114. Can't update RADIO ROM.
This all happened when i was trying to downgrade my radio rom from 1.14.01 to 1.13.00 this morning and it stopped at 66% with giving this messege.. cannot upgrade radio rom... since then i am unable to re-install radio rom. However i am able to install WIN CE ROM and EXT ROM but not radio ROM.
can you guys help me somehow?
farehmani.
farehmani said:
i wonder if anyone could help me with my problem!
i can't upgrade / Install RADIO ROM (any) in my UNIVERSAL. what happens is that it doesn't starts and when rebooting it says NO GSM where the versions are mentioned in red.
my universal goes in the bootloader mode properly and the update or RADIO ROM Starts; but it stays on 0% and doesn't move ahead. after a while and error comes ERROR 114. Can't update RADIO ROM.
This all happened when i was trying to downgrade my radio rom from 1.14.01 to 1.13.00 this morning and it stopped at 66% with giving this messege.. cannot upgrade radio rom... since then i am unable to re-install radio rom. However i am able to install WIN CE ROM and EXT ROM but not radio ROM.
can you guys help me somehow?
farehmani.
Click to expand...
Click to collapse
Radio rom upgrades are definately more reliable with the original cable. I have read somewhere in these forum that the mode of radio ROM upgrade is different from other ROMs (CE and Ext rom) this is the reason why it takes more time than the CE rom although the later is much larger in size. I suggest you try again if possible on a different PC. For some strange reason I can upgrade my Radio ROM only in my office PC.
d_ranade said:
Radio rom upgrades are definately more reliable with the original cable. I have read somewhere in these forum that the mode of radio ROM upgrade is different from other ROMs (CE and Ext rom) this is the reason why it takes more time than the CE rom although the later is much larger in size. I suggest you try again if possible on a different PC. For some strange reason I can upgrade my Radio ROM only in my office PC.
Click to expand...
Click to collapse
i have tried on 3 different computers but it doesn't work. also with original cable too. it is definately a software problem as no physical damage was made to my device. there must be something that fixes it.
still while upgrading Error 114. (UNABLE TO UPDATE RADIO ROM)
i wish i could find any help with this...
Farehmani
farehmani said:
i have tried on 3 different computers but it doesn't work. also with original cable too. it is definately a software problem as no physical damage was made to my device. there must be something that fixes it.
still while upgrading Error 114. (UNABLE TO UPDATE RADIO ROM)
i wish i could find any help with this...
Farehmani
Click to expand...
Click to collapse
Have you tried putting the unit into Bootloader before you start the upgrade - I find that more reliable?
apd said:
Have you tried putting the unit into Bootloader before you start the upgrade - I find that more reliable?
Click to expand...
Click to collapse
I too find that upgrade in Bootloader is more reliable.
To let you into a little secret.. I ALWAYS flash now in Bootloader mode.. I have only had a couple of "bad flashes" but all of them were direct from a running OS...
I have sent you a pm, that should solve your issue. Please check your pm's...
Take care,
-Jwrightmcps
farehmani said:
i wonder if anyone could help me with my problem!
i can't upgrade / Install RADIO ROM (any) in my UNIVERSAL. what happens is that it doesn't starts and when rebooting it says NO GSM where the versions are mentioned in red.
my universal goes in the bootloader mode properly and the update or RADIO ROM Starts; but it stays on 0% and doesn't move ahead. after a while and error comes ERROR 114. Can't update RADIO ROM.
This all happened when i was trying to downgrade my radio rom from 1.14.01 to 1.13.00 this morning and it stopped at 66% with giving this messege.. cannot upgrade radio rom... since then i am unable to re-install radio rom. However i am able to install WIN CE ROM and EXT ROM but not radio ROM.
can you guys help me somehow?
farehmani.
Click to expand...
Click to collapse
apd said:
Have you tried putting the unit into Bootloader before you start the upgrade - I find that more reliable?
Click to expand...
Click to collapse
yes... i have never tried to flash anything while being in the os. always switch my device to the bootloader first. I have BootLoader 1.01
Please help!!
apd said:
Have you tried putting the unit into Bootloader before you start the upgrade - I find that more reliable?
Click to expand...
Click to collapse
How to put the PPC in Bootloader (Qtek900)?
myname70 said:
How to put the PPC in Bootloader (Qtek900)?
Click to expand...
Click to collapse
Read the wiki - the answers are in there.
apd said:
Read the wiki - the answers are in there.
Click to expand...
Click to collapse
the problem is still there....
i have tried circumvent bootloader password too... and getting error like Win32 Error, Cannot read from the specified device when HEX of password is placed on the memory field of WinDbg.
Tried Another solution for NO GSM but no luck !!
okay here goes; your quoted link had point#5 for no GSM when booting so i followed it as given below.
Pls. see the comments in (( )) for how i conduct these steps and what value is returned.
[[[[--->
Problem 5: Device shows NO GSM when booting (( I'm having this problem ))
1) The radio stack is screwed, you don't get GSM signal and the phone says unknown SIM status
2) Device won't start after trying to unlock it with HTC Universal Unlocker (HTC_Uni_SIM_Unlock_v1)
Here is how to fix it:
1)Disable activesync on your computer by right click on activesync icon -> connection settings -> uncheck "allow USB connections". (( Done! ))
2)Put your Hermes (( Universal )) in bootloader mode
3) Connect device to computer using USB cable. (( Done with Original Cable ))
4) Open mtty.exe and select USB port, then connect.
Hit enter twice, you will see the "USB>" prompt. (( Okay but i usually get the USB> prompt with single hit of Enter ))
Type the following commands (do not copy paste!!!) (( I type them ))
USB> password 0000000000000000 (( Returns: HTCSPass1.CMˆËHTCEUSB> ))
USB> set 1e 1 (( Returns: USB> ))
USB> erase a0040000 c80000 (( Returns: HTCST ÚÈÒHTCEUSB> ))
USB> erase a0cc0000 c80000 ((Returns: HTCST ÚÈÒHTCEUSB> ))
USB> erase a1940000 640000 (( Returns: HTCST ÚÈÒHTCEUSB> ))
USB> set 1e 0 ((Returns: USB> ))
(( Then i close the window of MTTY and proceed to step 5 ))
5) Reset your phone and put it back in bootloader mode (( Here i take my Universal off the usb cable, soft reset it with the stylus and without letting it to boot i switch it into the bootloader mode again and get "Serial & v1.01" on the screen's header and footer ))
6) If your bootloader version is different than 1.04 then Flash Bootloader version 1.04 (( I simply ignore this step as this could be for Hermes users only not for UNIVERSAL Users - Pls. correct me if i'm wrong ))
7) Flash the patched radio used to simunlock the Hermes (( I do it with HTC_Uni_Unlock_v1 it has radio version 0.00.00 BUT still it gets stuck at 0% and after sometime gives the same error 114. Cannot Update Radio ROM ))
Your phone should be alive again (( Its Not ))
<---]]]]
i don't think i'm doing anything wrong here... just the step 5 of bootLoader Update to 1.04...
what comes in your mind ???
i'm desperately missing my pda. its begun to hurt now... please help me rescue my baybee....
farehmani
farehmani said:
i don't think i'm doing anything wrong here... just the step 5 of bootLoader Update to 1.04...
what comes in your mind ???
i'm desperately missing my pda. its begun to hurt now... please help me rescue my baybee....
farehmani
Click to expand...
Click to collapse
Don't worry, mate, you're almost there...
Don't worry about the bootloader version, that is just for the Hermes (Universal will be 1.01 or under for G3, 2.1 for G4). If it's under 1.01 it would be worth upgrading to 1.01 which you can find on the ftp.
SpyderTracks said:
Don't worry, mate, you're almost there...
Don't worry about the bootloader version, that is just for the Hermes (Universal will be 1.01 or under for G3, 2.1 for G4). If it's under 1.01 it would be worth upgrading to 1.01 which you can find on the ftp.
Click to expand...
Click to collapse
glad to know about my being almost there... still i wonder whats keeping me away from retaining my device...
i have already got BootLoader 1.01...
what other method should i apply to get it working again?????
I have the same problem, but not in Universal, but apache, jwright help me.
i have the same problem can smeone help
Try this
"Type "task 28 55aa" and hit enter.
This will restore the DOC partition to its original layout and delete all data
including the ROM!
Once finished you must use the "Original OEM ROM" (i.e. JASJAR WWE
1.30.76) that is made for your device and update with it (CE,Extended
and Radio).
Also if your device bootloader version is lower than "v 1.01" you should
update that first (before installing the OEM ROM, but NOT before "Task
28 55aa").
After this is complete you may then use your device again.
Please let me know how things work out for you...
Take care,
-Jwrightmcps"
It solve me...
i am having the same problem with exec it shows me no gsm and when i go to the device information it does not shows the radio ver and my phone imei is 0 can someoe please tell me how do i solve the problem i had read this tread but not understand it can someone please explane me how do i solve the problem
shedragon said:
"Type "task 28 55aa" and hit enter.
This will restore the DOC partition to its original layout and delete all data
including the ROM!
Once finished you must use the "Original OEM ROM" (i.e. JASJAR WWE
1.30.76) that is made for your device and update with it (CE,Extended
and Radio).
Also if your device bootloader version is lower than "v 1.01" you should
update that first (before installing the OEM ROM, but NOT before "Task
28 55aa").
After this is complete you may then use your device again.
Please let me know how things work out for you...
Take care,
-Jwrightmcps"
It solve me...
Click to expand...
Click to collapse
thanx for your suggestion!
i had tried this already... but the problem is beyon this...
i discussed with pof and he said that somehow i screwed up with the qualcomm chip where the radio bootload resides. so it needs replacement.
anyways... thanx budd... i appreciate your support too...
regards...
my hermes having this problem also ((
Recently I flash to WM6(tried every version) and still I have the white screen issues. So, I decided to downgrade to WM5. However, after the flash complete, my phone stuck at the at&t screen and do not want to proceed anymore. So, I have no choice to flash to WM6 Black 2.0.02 again. It works, but my storage is like below :-
Total 7.33MB
In Used 6.21MB
Free 1.12MB
Where does my memory gone ?
Thanks.
IPL 1.01
SPL 1.40 Olipro
try (using mtty) "task 32", "task 2a"
Should work?
yes, you have bad blocks in nand... "task 2a" should fix it.
Thanks, will try that after my breakfast. Cheers.
Sorry guys, my mtty refuse to connect to my device. I am in the bootloader now and it shows "USB" once I connect the cable. But mtty says cannot open USB port. Is there any where I can read on how to use mtty ? I am not an expert.
Thanks.
mtty use: READ THE W*I*K*I!
I'll give you a hint, turn off activesync before you open mtty...
LegolasTheElf said:
mtty use: READ THE W*I*K*I!
I'll give you a hint, turn off activesync before you open mtty...
Click to expand...
Click to collapse
Thanks, Legolas. Manage to get mtty to work. However, issue those two commands, does not fix the storage and white screen issue. Any other suggestion ? It checks all the block and they appear to be "good".
Thanks.
Missing a step?
lohthx1r said:
Thanks, Legolas. Manage to get mtty to work. However, issue those two commands, does not fix the storage and white screen issue. Any other suggestion ? It checks all the block and they appear to be "good".
Thanks.
Click to expand...
Click to collapse
I don't see in the log where you run task 32. Did it ever run?
LegolasTheElf suggested that step.
Hope that helps.
lohthx1r said:
Manage to get mtty to work. However, issue those two commands, does not fix the storage and white screen issue. Any other suggestion ? It checks all the block and they appear to be "good".
Click to expand...
Click to collapse
I think that means it fixed all those blocks. Guessing you may need to reflash now that it's reclaimed all that space. I sure would.
Reflash the OS after task 2a
THANKS A LOT !!! It fix my "missing storage" issue. Hope I am not asking too much, but it still does not fix the white screen issue. I read up the WIKI and task 28 is to format the NAND, should I try that ?
Cheers.
You *are* running 1.40.Oilpro SPL, right?
Yes, I am...could it be battery problem ? As when the whitescreen happen, I knock softly the phone on my palm and sometimes it will go away.
Cheers.
lohthx1r said:
Yes, I am...could it be battery problem ? As when the whitescreen happen, I knock softly the phone on my palm and sometimes it will go away.
Click to expand...
Click to collapse
Sounds like a connection problem with the screen, IMO.
I'd go with battery
Thanks all, I should try to exchange the battery with my friend and test it for few days.
Cheers.
Hi,
I'm using Artemis with one of Tom's ROM. The device was working well. But today suddenly the device won't start up - it is locked at the startup screen showing the SPL, IPL etc. I can enter the bootloader.
Can anybody tell me how to flash the ROM at this stage?
Flash from bootloader
Hi!
Please download an official rom and keep pressed the Power and Record buttons. You will see a screen with 3 colors (red green blue). Connect the USB cable and wait for Activesync. After this start the original rom flasher and follow the instructions. If you can start the Windows, you should flash the USPL again and you can flash cooked roms. If you flashed a new one, i think you should also upgrade the radio rom.
Sorry for my English
well i'll give it a try.
BTW will activesync work if the phone is not booting up?
sure it will, but make sure you have the only phone pluged in, nothing else, and disable all firewalls and antivriuses.
Good luck
i flashed with htc official rom and it worked first. after soft resetting a few time (due to program installation) the phone again back to earlier state.
it is showing:
ipl 3.13.0001
spl 3.13.0000
gsm 2.94.90
os 3.13.0.0
and stuck at this screen.
i tried to update the phone again with the same rom - but i'm getting error 270.
do i need to unlock cid before flashing?
but i can't use the uspl tool as i can't connect to activesync.
pls help.
make sure the battery is fully charged again.
Restart your PC, isbale ll antivirus and firewalls
Better if flashing in XP PC
put PPC in Boating status
Flash Shipped ROM
Specify which software caused you the trouble and do not install it again
CID unlock PPC
Flash any cooked ROM.
once i flashed the phone with the shipped rom successfully. The phone was CID unlocked then. But now when I try to flash the shipped again i'm getting an error message (error 292 or something - stating-invalid vendor id)
archat68 said:
once i flashed the phone with the shipped rom successfully. The phone was CID unlocked then. But now when I try to flash the shipped again i'm getting an error message (error 292 or something - stating-invalid vendor id)
Click to expand...
Click to collapse
you must unlock phone again.
I tried flashing the device with factory shipped ROM. but i'm getting Error 294-invalid vendor id message.
please suggest what to do?
chance are you have stuffed your bootloader...
start from scratch again by running uspl:
http://forum.xda-developers.com/showthread.php?t=311403
than flash your favorite rom again, ideally via sd-card-flashing:
http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing
greetz
thormdac said:
chance are you have stuffed your bootloader...
start from scratch again by running uspl:
http://forum.xda-developers.com/showthread.php?t=311403
than flash your favorite rom again, ideally via sd-card-flashing:
http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing
greetz
Click to expand...
Click to collapse
USPL needs activesync running. Can you tell me how to run USPL when I can't boot into windows?
well,
its been some time, but i am pretty sure uspl puts your device into bootloader and operates from there...
have you tried setting it into bootloader, connecting via usb and simply starting uspl?
running a normal setup-routine, there is no need to start it from wm either-simply put it into bootloader and start setup!
greetz
Well i tried that. But it seems that USPL doesn't work without activesync.
i've also tried flashing with SD card, but after a brief "Checking SD card content" message the phone goes back to bootloader.
Someone helpppp pls.
are u sure your sd card is correctly configured, according to the wiki entry- especially part "if above fails" ...?
if all steps fail, assumed you performed them correctly, you might try taking out battery and leave the device fully without power overnight...and restart it the next morning
I've used a 512MB SD card - formatted it- and copied the OS file as ARTEIMG.nbh - put the sd card in the phone and started the phone in bootloader mode.
I think there is nothing more to do.
I can enter the bootloader, connect the phone to PC in USB mode. So, I hope that my phone is not bricked.
But how to revive it?
if you are in bootloader, i dont see why you shouldnt be able to flash!!!
try another sd-card, use another xp computer, exchange the usb cable...
yust to be certain: have you left out battery over-night?
...and what are the details stated on boot-loader screen (numbers)?
oh, and I get the feeling you are not working exactly as told:
in your PC right-click on Computer, then select Manage
Select Disk Manager and then delete existing partition
create a new partition with max size 256MB
format this partition in FAT32
thormdac said:
(i)...and what are the details stated on boot-loader screen (numbers)?
(ii) oh, and I get the feeling you are not working exactly as told:
in your PC right-click on Computer, then select Manage
Select Disk Manager and then delete existing partition
create a new partition with max size 256MB
format this partition in FAT32
Click to expand...
Click to collapse
(i) See post no 5 for the details
(ii) You can not do this with a removable disk (SD card inserted through a card reader). Only works when you can get WM5Storage to work.
archat68 said:
(ii) You can not do this with a removable disk (SD card inserted through a card reader). Only works when you can get WM5Storage to work.
Click to expand...
Click to collapse
...i dont have my micro-sd-card-adapter at hand atm., but there sure will be possibilities formatting your sd card accordingly...try administrative tools/computermanagement/storage/diskmanagement under xp, boot your pc with a diskpartitioner like acronis disk director...
i can only advise you to keep trying...but as long as you can not say for sure sd-card-flashing is working correctly, i wouldnt give up...
and as far as flshing bootloader via usb/activesync goes, i can only say i once screwed my device due to insufficiant battery power during sd-card-flashing and thought it was bricked just at the point you are stuck now!!! - totally resetting it with the power-oiut-method, i.e. battery out overnight, revived it!!!
than agin i sure as hell did everything the way it was ment o be done...and nothing worked until i switched to another pc/ usb-cable!!!
so, to sum it up, DONT GIVE UP!!! bootloader is showing...so there must be a way to get this to work...
greetz
archat68 said:
I tried flashing the device with factory shipped ROM. but i'm getting Error 294-invalid vendor id message.
please suggest what to do?
Click to expand...
Click to collapse
Somebody please help me to revive my phone.
how can we help you, if you dont provide us any results of the steps suggested to you...ideally in a way so we can see what you actually did or didnt do, precisely as told ?!?
greetz
I actually have a new phone coming today because I had no idea what to do and when I called neither did Verizon.
I seen the GPS fix thread, downloaded all the necessary files, ran the first unlocker (.40) and it errored half-way through the process, I figured big deal I'll just run it again..
Well, my USB would show on the phone screen but in the bootload mode the unlocker programs couldnt detect my phone at all and I couldn't get out of bootload mode whether I hit soft reset or took out the battery. So I decided to try going ahead an upgrading, I tried the next step on the list (sprint rom) but the upgrade would error as well, then I tried the verizon one, error, and the just tried jumping back to the NFSFan ROM and it didn't even begin to error it said it wasn't allowed or something.
Anyways, I had no idea what to do... took it in to the store, they looked at it for awhile then told me to call a number, I tried the number and they attempted to wipe it from their side and couldnt do anything so they told me they'd send another one being I was still in my 1-year warranty.
Is this how you brick a phone? Having an error during an unlocker/upgrade? Or could I have fixed this if I asked here before I sent for a new 1? I don't mind because I'm hype for a brand new phone, I just wonder if it can be fixed incase this ever happens again.
next time use coke 2.31
vin255764 said:
next time use coke 2.31
Click to expand...
Click to collapse
to do the gpsfix you have to use coke .40, its not like its some old outdated thing the thread is from august everybodys been using it, all i want to know is if theres no return once an error occurs in the middle of an unlocker?
j18yo said:
to do the gpsfix you have to use coke .40, its not like its some old outdated thing the thread is from august everybodys been using it, all i want to know is if theres no return once an error occurs in the middle of an unlocker?
Click to expand...
Click to collapse
There is a fix
what is showing on the bootloader screen for the unlocker?
Also you may want to reflash a shipped ROM. I have had this happen on both Titans and Vogues and reflashing from the bootloader screen always solves the problem.
I'm assuming you have to flash via the SD card right? Because I tried doing it through the USB and all the ROMs would error because the unlocker never fully finished, I mean before all this my phone was unlocked by the 2.31 and I had the newest NFSFan running I just decided to go back for the GPSFix..
The bootloader screen wasn't froze, it showed the usual..
Upper right corner says "RUUNBH"
Then to the left top it says..
VOGU100
SPL-0.36.0000
CPLD-3
and Serial at the bottom until I put the USB in and it turns to USB.. but it doesn't get picked up by the unlocker if I try to re-run it
I guess I answered my own question.. to fix it I'd have to run the unlocker again from the SD Card so it finish's without error since the USB won't pick up right?
My problem is I've never ran anything from the SD card.. if anyone can tell me how you go about loading up an unlocker or ROM from bootload on the SD I'd appreciate it, this way when I get my new phone if I run into a similar problem I can fix it
j18yo said:
I'm assuming you have to flash via the SD card right? Because I tried doing it through the USB and all the ROMs would error because the unlocker never fully finished, I mean before all this my phone was unlocked by the 2.31 and I had the newest NFSFan running I just decided to go back for the GPSFix..
The bootloader screen wasn't froze, it showed the usual..
Upper right corner says "RUUNBH"
Then to the left top it says..
VOGU100
SPL-0.36.0000
CPLD-3
and Serial at the bottom until I put the USB in and it turns to USB.. but it doesn't get picked up by the unlocker if I try to re-run it
Click to expand...
Click to collapse
Try installing this driver on your XP computer http://www.4shared.com/file/101893703/a59b72a/WindowsHTCdrivers.html if you have Vista let me know and I'll give you a link fvor that one. It should then allow you to communicate via USB. Also to answer your next question on flashing from the SD. It is simple you copy the NBH file from a ROM to Root directory of a FAT32 card 2 gb or less. Rename the file to VOGUIMG.nbh place the card into PPC and place into bootloader mode. Then follow the instructions.
j18yo said:
I guess I answered my own question.. to fix it I'd have to run the unlocker again from the SD Card so it finish's without error since the USB won't pick up right?
My problem is I've never ran anything from the SD card.. if anyone can tell me how you go about loading up an unlocker or ROM from bootload on the SD I'd appreciate it, this way when I get my new phone if I run into a similar problem I can fix it
Click to expand...
Click to collapse
All you do is put the .nbh file on the root directory of the memory card(use a newly formatted/clean card). It may delete anything else on the card while flashing.
I would take out the battery. Put in the SD card then turn the phone on. If, like you say, you are stuck in bootloader mode then it should start flashing as soon as it powers up.
Thanks everyone, I received my new phone this was mainly incase it happened again, but I also figured out why I ran into my problem..
During the unlocker I thought I knew the process being I'd done it multiple times, I skipped the part where I unplug the phone from USB and plug it back in so it's no longer connected with ActiveSync... thats why my unlocker error'd, so make sure you don't do that lol
What was messed up is my computers been acting like a piece of ****, it wouldnt even read my SD card so that I could put a file on it, but I don't think I'd wanna do it that way I have all my stuff on my SD card if it erased it I'd have been pissed..
ActiveSync does work, for awhile I thought the USB was only charging my phone because my new one wouldnt pick-up ActiveSync.. no idea why.. but if I plug it in and wait around 10 minutes it finally connects.