WM6 freezing with alarms while charging - 8125, K-JAM, P4300, MDA Vario ROM Development

I've tried different WM6 roms until now and I always faound a little issue with them.
When I leave my MDA plugged with the wall charger and during the carghe starts an alarm set before, the OS freezes without playing alarm and needs a soft-reset.
I'm wondwering if this issue has been alrady discussed, because even I used the search I found nothing.
Is it a problem of new WM6 Roms or simply an issue of my MDA Vario?

yu
going to test this now
ok i put it on the charger and set an alarm 2 minutes ahead
it works fine..
probably u have this issue with the IPL/SPL
i suggest you go to the procedure of unlocking the device and update it to the rom u wish
see my topic: rom flashing

My MDA is all unlocked, so i don't know if is really an IPL/SPL issue.
Anyone else had this issue?

yu
believe me its a SPL issue due to not having removed the sd card while updating the device. it is in use whereas it cannot update this way.
i suggest u flash rom crossbow reloaded as it is an improved version of the one u have now
please do exactly as i stated in the flash rom topic i gave
re-run the whole thing including unlocking
make sure u dont have any cable or whatever connected to the device
only this usb cable to the pc and make sure the battery is fully loaded as it
will give stupid errors as it assumes its full and ur battery meter wont match
very strange indeed but it seems to be the case..
in the end you'll be happy coz it runs flawlessly without strange errors

I'm going to try now... thanks for hints!

solved
da_jojo said:
believe me its a SPL issue due to not having removed the sd card while updating the device. it is in use whereas it cannot update this way.
i suggest u flash rom crossbow reloaded as it is an improved version of the one u have now
please do exactly as i stated in the flash rom topic i gave
re-run the whole thing including unlocking
make sure u dont have any cable or whatever connected to the device
only this usb cable to the pc and make sure the battery is fully loaded as it
will give stupid errors as it assumes its full and ur battery meter wont match
very strange indeed but it seems to be the case..
in the end you'll be happy coz it runs flawlessly without strange errors
Click to expand...
Click to collapse
Ok, sorry for my skepticism, you were right and now all is working ok!
Thank you again!

Related

Killed my 8125

Well I guess I bricked mine ulness someone knows something I don't. I was doing a flash, running nothing else and XP did a memory dump and blue screen of death while 8125 was 54% done. Guess I have a paperweight now.
I am sure I'll get flamed for my post but thank God the Cingular ROM doesn't need an actual Active Sync connection. As long as you are in RBG bootloader screen and the USB comes on when you plug into the PPC, the factory ROM can repair the unit.
Possible Reviving Techniques For (appeared to be) bricked Wizard
See the following link and read, read, read.
http://wiki.xda-developers.com/index.php?pagename=HTC_Wizard
Very good I do remember reading that post from when I first joined here, guess I just panicked. I must mention however that none of the WM6 ROMS i have would flash only the stock one would.
When you have a bad flash you ALWAYS should go back to an official rom. This will guarentee that you get back to a complete IPL/SPL and Extended ROM. If a flash goes bad, any (and all of them) could be corrupted and flashing a custom rom won't help (since most all of the custom roms don't include any of those pieces).
n3rxs said:
Well I guess I bricked mine ulness someone knows something I don't. I was doing a flash, running nothing else and XP did a memory dump and blue screen of death while 8125 was 54% done. Guess I have a paperweight now.
Click to expand...
Click to collapse
Reboot your pc....
Your device should be in bootloader mode still
Connect and flash the same ROM....it should pick up right where it left off
If this doesn't work, flash your factory rom
As long as your device powers up....it's not bricked
The same thing happened to me once on my wife's laptop
Yeah this was on my company laptop. I was flashing Faria's RealThing for the 1 hundredth time.

stock on 0% flasahing rom

hello everybody
i started to flash a new rom
Ruu_Signed_Duttys_WM6.1_5.2.19700_Hybrid V2_1_65.14.06[No_CubeV2]
and i think i followd all the instractions but after starting the flashing it stock on 17% after removing the battery as the program said it wont go over 0%
firs i installed kaiser-HardSPLv1 and after that i started to flash the rom and its not working.
pls tell me what to do to save my nice phone
dannt
speebman said:
hello everybody
i started to flash a new rom
Ruu_Signed_Duttys_WM6.1_5.2.19700_Hybrid V2_1_65.14.06[No_CubeV2]
and i think i followd all the instractions but after starting the flashing it stock on 17% after removing the battery as the program said it wont go over 0%
firs i installed kaiser-HardSPLv1 and after that i started to flash the rom and its not working.
pls tell me what to do to save my nice phone
dannt
Click to expand...
Click to collapse
"think" you followed all the directions?
sorry for my bad english or leak of knolge in this part of the world i just read so much regarding this subject ant the more i read the more i got confused
so i just sow the first logical faq and followd him, plz i need my phone all my life is in their, help me.
danny
speebman said:
hello everybody
i started to flash a new rom
Ruu_Signed_Duttys_WM6.1_5.2.19700_Hybrid V2_1_65.14.06[No_CubeV2]
and i think i followd all the instractions but after starting the flashing it stock on 17% after removing the battery as the program said it wont go over 0%
firs i installed kaiser-HardSPLv1 and after that i started to flash the rom and its not working.
pls tell me what to do to save my nice phone
dannt
Click to expand...
Click to collapse
Things that will help others help you:
1. where are you located?
2. who is your provider
3. what ROM WERE you on?
4. ok - you had a phone that was working - and you did:
a. what did you do first?
b. second?
c. etc.
Your message KINDA indicates that you flashed a ROM and had issues - so you THEN flash HARDSPL? was that successful?
Bill
im from israel but my phone is from uk i think, my original rom was the HTC 6.1
i just run the kaiser-HardSPLv1 program and then i started flashing the rom duty 6.1 rom and it stoped at 17% like the program said i removed the batery and started the flashing prosse again but now it doesny even go above 0%, now im stock in the tri color screan
its writen
kais130
spl-3.28.0000
cpld-8
and usb in the littel whait screan
speebman said:
im from israel but my phone is from uk i think, my original rom was the HTC 6.1
i just run the kaiser-HardSPLv1 program and then i started flashing the rom duty 6.1 rom and it stoped at 17% like the program said i removed the batery and started the flashing prosse again but now it doesny even go above 0%, now im stock in the tri color screan
its writen
kais130
spl-3.28.0000
cpld-8
and usb in the littel whait screan
Click to expand...
Click to collapse
you don't have hardSPL installed..! surprise, surprise
u don't have hardspl flashed from bootloader info u provided. flash hardspl be4 flashing any roms.
please search and read; this has been answered many times.
p.s. use the new hardspl by jocky which is a sticky in this forum.
speebman said:
im from israel but my phone is from uk i think, my original rom was the HTC 6.1
i just run the kaiser-HardSPLv1 program and then i started flashing the rom duty 6.1 rom and it stoped at 17% like the program said i removed the batery and started the flashing prosse again but now it doesny even go above 0%, now im stock in the tri color screan
its writen
kais130
spl-3.28.0000
cpld-8
and usb in the littel whait screan
Click to expand...
Click to collapse
OK - I do not think that you got the HARDSPL installed on your phone correctly - BECAUSE - I believe that it would say OLIPOF or JOCKY on it and it does not.
I have not seen the new HARDSPL 328 and 329 but it LOOKS like to me that you did not successfully get the HARDSPL on your phone.
Personally - I would scan the message boards for GSLEON3 (user name) and send him a private message - there are many others that can help you and he or others MAY come trolling by and take pity on you - but at the moment he is the one that helps people in your situation the most from what I have seen.
I would NOT continue to work on it myself as you can definitely mess your phone up permanently. Does your phone still go into boot loader mode? If so - can you flash the required HARDSPL onto your phone?
Find a message that GSLEON3 has left and then lik on his name and send him a private message - he is very nice - BUT - he is VERY busy - continue to be nice and he will most likely get you back and running.
Bill
first of all thank u for the help
but, wich one i need? 28 or 29?
and how do i do this spl if i cant copy them to my device.
danny
speebman said:
first of all thank u for the help
but, wich one i need? 28 or 29?
and how do i do this spl if i cant copy them to my device.
danny
Click to expand...
Click to collapse
Danny -
Deep cleansing breaths here ok?
1. personally - I would PUT BACK what ever you had on your phone and get it running again - trying at this point to get ot to go to a different ROM is not a good idea right at this minute.
2. 28 and 29 from what I read makes no difference - users try each one to see which one works better on THEIR flashed ROM.
3. What I would do is look for the HARDSPL that goes with what you had loaded to begin with - or the actual SPL that came with your original ROM and put that one back.
I would be stuck here because I have to use JUMPSPL on my phone because I get the white screen - but I THINK that (don't quote me because I do not do it this way) if you don't get the white screen you can just flash the HARDSPL to your phone without JUMPSPL (having to be able to copy something to your phone.
HOWEVER - if you cannot or do not know how to continue from reading the WIKI - you MUST request help from a professional - I have already recommended one. (GSLEON3)
Bill
my active sink is not seeing the devais, maby MTTY? wil help
speebman said:
my active sink is not seeing the devais, maby MTTY? wil help
Click to expand...
Click to collapse
Based on your current track record, I wouldn't suggest you use MTTY as you have a VERY HIGH probability of bricking your phone (ie: it won't ever be usable again).
so im fu--.
Can you get the phone into the bootloader mode? Turn the phone off (pull the battery if you have to) then press and hold the camera button while you turn the phone on. You should get to a tri-color screen (this is the boot loader). Now plug in the USB cord and see if it switches from saying Serial to USB. If so, you can try flashing AN OFFICIAL ROM THAT WAS MEANT FOR YOUR PHONE (ie: Don't try to put an offical AT&T rom on an Orange). When you run the RUU program it will tell you that you need to have ActiveSync working, but don't worry about that. If your phone in bootloader shows USB, you can continue on.
BUT AGAIN... You need the Official rom that was meant for your device. Since you are not HardSPL'd you have to do it this way.
If you don't understand any of that, or have questions, don't just try it hoping you get it right...
As stated previously, it would be well worth you time to get someone like GSLEON to assist if you can.
mfrazzz said:
Can you get the phone into the bootloader mode? Turn the phone off (pull the battery if you have to) then press and hold the camera button while you turn the phone on. You should get to a tri-color screen (this is the boot loader). Now plug in the USB cord and see if it switches from saying Serial to USB. If so, you can try flashing AN OFFICIAL ROM THAT WAS MEANT FOR YOUR PHONE (ie: Don't try to put an offical AT&T rom on an Orange). When you run the RUU program it will tell you that you need to have ActiveSync working, but don't worry about that. If your phone in bootloader shows USB, you can continue on.
BUT AGAIN... You need the Official rom that was meant for your device. Since you are not HardSPL'd you have to do it this way.
If you don't understand any of that, or have questions, don't just try it hoping you get it right...
As stated previously, it would be well worth you time to get someone like GSLEON to assist if you can.
Click to expand...
Click to collapse
thank you!!!!!!1
i have flashed to my priviuas rom the original 6.1 htc rom and now its ok!!!
tnk
speebman said:
thank you!!!!!!1
i have flashed to my priviuas rom the original 6.1 htc rom and now its ok!!!
tnk
Click to expand...
Click to collapse
Cool. Glad that worked for you.... NOW, your next task is to read and understand ALL the steps before you try flashing a custom rom. HardSPL that sucker (but understand and follow EVERY step before you try that) and then you should be good to go...
my only problem is that their are so many strings of information and so many threads even wiki is confusing.
i will try to do this after i will make some order it all of this.
tnx again 4 the help
danny
speebman said:
my only problem is that their are so many strings of information and so many threads even wiki is confusing.
i will try to do this after i will make some order it all of this.
tnx again 4 the help
danny
Click to expand...
Click to collapse
Yes it is, but if you read this sticky at the top, it should help (start with noob guide which is the first link I think):
http://forum.xda-developers.com/showthread.php?t=369282
speebman said:
my only problem is that their are so many strings of information and so many threads even wiki is confusing.
i will try to do this after i will make some order it all of this.
tnx again 4 the help
danny
Click to expand...
Click to collapse
Not to be mean but if you have red Wiki and looked at threads here and they "don't make sense to you". You really have no business flashing a rom. If you don't understand what you are doing sooner or later you will brick your phone from your lack of knowledge and it will be no ones fault but your own.
I am really surprised people were willing to repeat what has been typed out hundreds and hundreds of times on these forums.
Welcome to XDA

OH GOD!! is my Uni dead? NO GSM

Dear All,
Please kindly help me out of this.
Yesterday, My phone started to develop the "NO GSM: symptoms. At first, the phone ioccasionally turned off after it couldn't connect to the 3G network. Today, after reading nearly all the post concerning this "No GSM" symptoms, I applied the Mtty tools to desparately try to bring my beloved Uni back to life.
I applied that mtty.. I tried to upgrade it by using the shipped rom.. yet it said country ID error.. I reverted to use the MaUpgradeUt_noID.exe but the radio rom upgrade failed....
Are there any other solutions I can rescue my uni? I read it here http://forum.xda-developers.com/showthread.php?t=350349 that Radio Rom upgrade may be done through a SD card but the ftp link is dead and I can't get any files from there.
I miss my Uni so so much that I think I would buy another one if there's no way to save it... Please kindly help. all my gratitude.
Hi,
Please consider a new battery.
As strange as it may sound, one of my MDA Pro's had similar symptoms with battery at 70%. Replacing the battery with a new one fixed it right away.
The symptoms were:
- less network signal
- random turning off of radio
- could not access phone settings
- radio crash when trying GPRS connection
Also, on my other MDA Pro, I had problems like this, but they were caused by radio ROM 1.18. I changed to 1.15 and everything is fine since.
It seems that aging batteries are a major problem for weird issues. Just buy a new one at ebay and dont start flashing as a fool, cause you can risk a brick.
Cheers,
vma
My battery is actually new... just bought it 2 weeks ago.. and I tried the phone with both my new and old batt. still no luck -_-
I can't flash any radio rom now... is my Uni certified dead?
Any help would be great.. thanks
Try charging the battery first in another universal if possible, if battery is ok, put it in and try again, read Wiki and check if you can go to boot loader mode, check whether pc recognising the Uni once on etc.,
Read everything and the computer recognised my Uni ... tried MTTY tools to reset all the DOC partition in my Uni yet no way to reflash my radio rom again
I think as long as PC is recognising, dont consider it as DEAD. Its very much alive and keep hopes.
as I read through this forum, Radio ROM flashing is the most risky thing and often takes longer.
If you are not already considering, try only flashing radio rom and do not club with extrom etc, try redownloading the ROM or try a different version from a different link, unless you are particular about the one you are trying.
Always use the original USB cable supplied with the Uni.
Enter BootLoader mode by pressing and holding the power button and backlight button whilst performing a reset with the stylus. Connect Unit to PC to the USB port directly and not through a USB HUB.
Start flash again..
All the best
ronaldphl said:
Dear All,
Please kindly help me out of this.
Yesterday, My phone started to develop the "NO GSM: symptoms. At first, the phone ioccasionally turned off after it couldn't connect to the 3G network. Today, after reading nearly all the post concerning this "No GSM" symptoms, I applied the Mtty tools to desparately try to bring my beloved Uni back to life.
I applied that mtty.. I tried to upgrade it by using the shipped rom.. yet it said country ID error.. I reverted to use the MaUpgradeUt_noID.exe but the radio rom upgrade failed....
Are there any other solutions I can rescue my uni? I read it here http://forum.xda-developers.com/showthread.php?t=350349 that Radio Rom upgrade may be done through a SD card but the ftp link is dead and I can't get any files from there.
I miss my Uni so so much that I think I would buy another one if there's no way to save it... Please kindly help. all my gratitude.
Click to expand...
Click to collapse
From the problem behavior it seems your device got GSM locked, I'm afraid it's permanent. But at least try ...
1. Remove the SIM card
2. Must upgrade the bootloaded to 1.01 if it's a G3 (and not upgraded already).
3. Run the Buzz's CID unlocker tool and flash the radio (version 0.00) provided with the tool.
4. Do the HR and check the status

RUU error (262) update error

Hello guys...
Iam not new, and i have already flashed my first(it was wasted not by my fault)KAISER, it was one year ago and i did it with HARDSLPv1, and lately added some new roms cooked by sakajati(respect)...
Yesterday i bought new one(but one year old) so i tried to flash him as well, i have used HARDSPL 1.93, and then i tried to put Sakajati"s 4th feb ROM, but i come across one big trouble, everytime i try to put it on i encounter the same RUU error:
ERROR [262] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process. Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue. Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.
what to do...????
i am very afraid that i destroyed my Kaiser...???
what it means that Wince is destroyed...
Please help me, i am desperate...
Iam not new,
Click to expand...
Click to collapse
But the solution could be found here (search)
If you see the tri color screen everythng is ok, just win mobile is destroyed. Try to flash a rom from your sd card
Thank you very much...
I hope it will work, i really did search for about an hour and tried to put rom on sevral times, but i didnt find nothing 100% secure, i dont want to indanger the unit any more that i did...
thanks again, i will try it tommorow morning at my job, thats where my SD card is...
)))
greganovak said:
Thank you very much...
I hope it will work, i really did search for about an hour and tried to put rom on sevral times, but i didnt find nothing 100% secure, i dont want to indanger the unit any more that i did...
thanks again, i will try it tommorow morning at my job, thats where my SD card is...
)))
Click to expand...
Click to collapse
Part of the problem is that 1.93 is a jump spl and should be used to upgrade to Hard spl 3.29 or 3.56, not as an spl on its own. You need to run jump spl 1.93 from your device and make sure you are connected to your computer, when you see the bootloader you need to unplug your USB, count to 10 and plug your USB back in then flash a hard spl to your phone! Again 1.93 is not a Hard Spl by itself, it is only a middle man to flash a Hard Spl.
I think the best would be to flash a stock rom at first, cause therefore you don't need an other bootloader. Then flash Hardspl (3.29 if you have a kaiser or 3.56 if you have a tilt) and then flash any rom you want
i obviusly have a lot to learn, mate how do I asses if I have TILT or KAISER, what is the main difference...
[email protected]: i have already DL the stock rom before i posted the tread, i hoped on that resolution if there were no answer...
in about 10 hours from now i will get my hands on my tilt/kaiser and hope to arranged the mess i done; I drop by in any case at that time and notify you about condition and my successes...
p.s.:sorry for my poor english...
greganovak said:
i obviusly have a lot to learn, mate how do I asses if I have TILT or KAISER, what is the main difference...
[email protected]: i have already DL the stock rom before i posted the tread, i hoped on that resolution if there were no answer...
in about 10 hours from now i will get my hands on my tilt/kaiser and hope to arranged the mess i done; I drop by in any case at that time and notify you about condition and my successes...
p.s.:sorry for my poor english...
Click to expand...
Click to collapse
It realy doesnt make that much of a difference, I have a tilt and I use 3.29 and I would recomend it to anyone over 3.56 so flash either one, they will both work! And your english is great so no need to say sorry!
greganovak said:
i obviusly have a lot to learn, mate how do I asses if I have TILT or KAISER, what is the main difference...
[email protected]: i have already DL the stock rom before i posted the tread, i hoped on that resolution if there were no answer...
in about 10 hours from now i will get my hands on my tilt/kaiser and hope to arranged the mess i done; I drop by in any case at that time and notify you about condition and my successes...
p.s.:sorry for my poor english...
Click to expand...
Click to collapse
A Tilt is a At$T branded Kaiser, a TyNT II is a HTC branded Kaiser. Tilt has a different keyboard and OEM rom., only differences. People say use 3.56 if you have a Tilt because that is an AT$T Spl, but I use 3.29 on My Tilt and it works great so it doesn't really matter.
hey...
nothing seems to work...
I have tried to put default rom dl from here: http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs but the problem is that it is not bootable from SD, that has to be because the USB conection isnt on (i selected the 3.34.721.2) so i given up that way
Then i flashed the HARD spl 3.29(have kaiser) via SD steb by step first with this instruction: http://forum.xda-developers.com/showthread.php?t=433835; and it dint go through
so i tried with this instruction: http://forum.xda-developers.com/showthread.php?t=420683
it didnt work either, they are the same I know(noticed later);
So problem is that i stuck at WHITE screen that says "LOADING..."
nothig else...???
finally i manage to load/boot the htc rom from xda-wiki site, but i have to chose another one
I have tried to put default rom dl from here: http://wiki.xda-developers.com/index...me=Kaiser_ROMs but the problem is that it is not bootable from SD, that has to be because the USB conection isnt on (i selected the 3.34.721.2) so i given up that way
Click to expand...
Click to collapse
Hey man, nice to see that your device rewakes, you can flash every rom from sd card, simply rename the nbh file to kaisimg.nbh than restart into bootloader and it will automatically take the one from the card
Unfortanly, althought i would like you to be right, you are not. When i tried to do it via SD, i stuck at white screen saying LOADING...(blue) and nothih further... and i tried also the Cmonex_s Hard SPL3.29_SD which also stucks at same screen
So now (after updatig with default rom) that i have basicly normal working device i startet from the top. Using @mskip"[email protected] tutorial called: Flasing your first rom (for noobs); it all goes well, till i start to update RUU(sakajati 4 feb) if it matters, and i tried both (spls 1.56 and 1.93), it stops updatig at 17% and notrhin else then works just puting back the HTC default rom from wikiXDA side(thank god for that)
i am thinking of MTTY, although i dont know what it does guys here almoste all say it fix bad rom flash, but i am not sure if thats my main problem, i rahter think it has something with spls...
if someone has some good advice i will be very grateful...
greganovak said:
Unfortanly, althought i would like you to be right, you are not. When i tried to do it via SD, i stuck at white screen saying LOADING...(blue) and nothih further... and i tried also the Cmonex_s Hard SPL3.29_SD which also stucks at same screen
So now (after updatig with default rom) that i have basicly normal working device i startet from the top. Using @mskip"[email protected] tutorial called: Flasing your first rom (for noobs); it all goes well, till i start to update RUU(sakajati 4 feb) if it matters, and i tried both (spls 1.56 and 1.93), it stops updatig at 17% and notrhin else then works just puting back the HTC default rom from wikiXDA side(thank god for that)
i am thinking of MTTY, although i dont know what it does guys here almoste all say it fix bad rom flash, but i am not sure if thats my main problem, i rahter think it has something with spls...
if someone has some good advice i will be very grateful...
Click to expand...
Click to collapse
Hi,
I couldn´t flash my Kaiser via SD at the first time and tried something that worked.
The SD´s are formatted in Fat16 usually, try to format to Fat32... It seems like a stupid thing, but worked for me.
Reagards and good luck.
SD must be formated FAT32, to work, also I sugest a smal card, 512 or something like that, SHDC usual doesn't work
I have 1GB SD and its not shdc, so thats ok.and i have done it right now, like you two guys said so i formated it with FAT32 but still no succes.
I guess that this tree lines in red/green/blue screen arent right:
KAIS130
SPL-3.02.0000
CPLD-8
i thing this SPL has to da something to do with all this mess a have done
I have flashed a couple of roms( i had three devices) and i flashed a few for my friends and all was OK till now, and i dont know what else to do...
greganovak said:
I have 1GB SD and its not shdc, so thats ok.and i have done it right now, like you two guys said so i formated it with FAT32 but still no succes.
I guess that this tree lines in red/green/blue screen arent right:
KAIS130
SPL-3.02.0000
CPLD-8
i thing this SPL has to da something to do with all this mess a have done
I have flashed a couple of roms( i had three devices) and i flashed a few for my friends and all was OK till now, and i dont know what else to do...
Click to expand...
Click to collapse
Yes, you still have a stock spl on there. It needs to be hard spl'd before you flash anymore. Check out the stickies at the top of the forum.
hi again...
Well, I respect the "rules" of forum, thats why i wouldnt ask for insructions that are already written(thanks for the authors) with that i mean stickys, because i read them, almost all...
But I still tried once again, and I came across the same thing, i stuck at 17% when loading RUU or if i choose the VIA SD i stuck at white screen with blue text saying (LOADING...)...
nothing else helps than loading the dafault ROM by HTC... as i already said once again...
if i manage to solve the problem i will be in touch; what do you thing about MTTY
Edit 1:
i have done everything as it says in the instruction, and just like some of you "replyed" me...
but i always stuck at 17%when loading RUU, when i flash it with SPL 1.56 or 1.93 i never get stuck at white screen it always apeare the mentioned SPLs nimbers and some other text in yellow but when i then load RUUs i stuck at excatly 17% nothing less nothing more
edit 2:
yupi....yupi
i made it...
http://forum.xda-developers.com/showthread.php?t=354061 here is my lifesavior...
those instruction were the one that helped my problem...
it is very nice to ba a part of this community....

[Q]Fuze undetected on any PC, just charges

I am in deep trouble here and could really use some help please. My ATT Fuze is not being detected by any PC and i have tried everything from different wires to changing everything on the fuze it self. Now my only option is to exchange it but i don't have the original OS because i am using NRGs Rom and hard SPL it about 4 months ago. Now to my question, is there anyway i can revert it to stock ROM and SPL with micro sdhc card? I need some steps please because i cant find a way to do it. Would i have to change the OS and the SPL to return if there is anyway please let me know.
darkreborn said:
I am in deep trouble here and could really use some help please. My ATT Fuze is not being detected by any PC and i have tried everything from different wires to changing everything on the fuze it self. Now my only option is to exchange it but i don't have the original OS because i am using NRGs Rom and hard SPL it about 4 months ago. Now to my question, is there anyway i can revert it to stock ROM and SPL with micro sdhc card? I need some steps please because i cant find a way to do it. Would i have to change the OS and the SPL to return if there is anyway please let me know.
Click to expand...
Click to collapse
First, what OS are you running on your PC.
Second, have you disabled/Enabled "enable faster data" in Settings/Connections/USB to PC?
Third, Have you deleted the partnership and tried to reestablish it?
Doesn't seem to be a warranty issue.
Fuze Reply
First of all thanks for your reply.
I have tried it on 4 different computer but unfortunately same result on vista and XP, on my phone i am using NRG july version rom.
I have disabled and enabled faster data in but doesn't seem to matter.
I tried everything, i reinstalled windows mobile device but doesn't seem to matter. When i ended the partnership it wasnt being detected after it or before it.
Cant i exchange it because its a faulty phone? Also can u please tell me if i can revert it to att stock rom and spl with a micro sdcard because i am going to buy a card reader. I really don't want to toss this phone and waste all that money please help!
darkreborn said:
First of all thanks for your reply.
I have tried it on 4 different computer but unfortunately same result on vista and XP, on my phone i am using NRG july version rom.
I have disabled and enabled faster data in but doesn't seem to matter.
I tried everything, i reinstalled windows mobile device but doesn't seem to matter. When i ended the partnership it wasnt being detected after it or before it.
Cant i exchange it because its a faulty phone? Also can u please tell me if i can revert it to att stock rom and spl with a micro sdcard because i am going to buy a card reader. I really don't want to toss this phone and waste all that money please help!
Click to expand...
Click to collapse
Yes, you can revert via SD card.
Do Radio and ROM first, then do stock SPL last.
Rename each RAPHIMG.NBH (one at a time) on a FAT32 formated card 2gb or smaller.
Go into bootloader mode and it should flash from there.
I would test your USB connection after you flash back to stock ROM before you flash the stock SPL to see if it may have fixed your issue.
Huh
Thanks a lot man!
Now the hard part , why do u say a card 2gb or smaller?
So i can revort the SPL with a micro sdhc card also? can u tell me where i can find this stuff, i am really sorry for the trouble and would really appreciate it if you can tell me step by step because i am a noob
Hopefully ATT exchange it for the usb issues , gotta check with them after this. Thanks
darkreborn said:
Thanks a lot man!
Now the hard part , why do u say a card 2gb or smaller?
So i can revort the SPL with a micro sdhc card also? can u tell me where i can find this stuff, i am really sorry for the trouble and would really appreciate it if you can tell me step by step because i am a noob
Hopefully ATT exchange it for the usb issues , gotta check with them after this. Thanks
Click to expand...
Click to collapse
I've heard that anything over 2 gb will cause an issue but I have done it from an 8gb card.
Start here for issues encountered.
Basically once you find your ROM Radio and SPL, extract the files so you can see the .NBH files for each.
1. Take the ROM file and rename it "RAPHIMG.nbh " without quotes.
2. Place it in the root of your storage card and enter bootloader mode (Volume Down + Reset), the phone will read the image file and begin to load it.
Do this for each file but wait until the first file has loaded.
Radio.nbh will be renamed to RAPHIMG.nbh
SPL.nbh will be renamed RAPHIMG.nbh
As one is done loading, remove it from starage card and put the next one on and repeat step 2.
Another thread regarding SPL.
I hope this helps you and sorry I don't have the time to walk you through it.
Just read first then you'll know what to expect.
Bruce Inman said:
I've heard that anything over 2 gb will cause an issue but I have done it from an 8gb card.
Click to expand...
Click to collapse
my best guess is just in case the bootloader doesn't have drivers for SDHC cards... my x51v has drivers for SDHC in WM, but flashing requires SD cards because the bootloader doesn't read SDHC
revert SPL or no?
Hey thanks bruce!
One more question, should i revert the SPL even tho i changed the radio and os. When i go to ROM version it says 1.95 but is that the SPL? Also you think ATT will take the phone back with the phone not syncing reason or do i have to make up some other stuff up? O btw the 8gb kingston card worked fine for reverting it and it still doesnt detect the phone
darkreborn said:
Hey thanks bruce!
One more question, should i revert the SPL even tho i changed the radio and os. When i go to ROM version it says 1.95 but is that the SPL? Also you think ATT will take the phone back with the phone not syncing reason or do i have to make up some other stuff up? O btw the 8gb kingston card worked fine for reverting it and it still doesnt detect the phone
Click to expand...
Click to collapse
To be safe I would revert the SPL as well.
The 1.95 is the ROM build base.
You want to revert back to stock SPL 1.90.
I can't second guess what AT&T will cover or not but you may want to "further your cause"....
Best of luck!!!
in my experience (my UK t-mob vario is back at repair right now) - DONT revert the SPL if you cant do it from the USB.
Obvisously you have a different setup to me, but when i tried to revert my phone to stock for exactly the same fault (no usb sync, regardless of pc or cable / phone rom, state etc etc) i managed to get the phone to refuse to boot due to a spl / rom difference. As i couldnt load from usb - i couldnt flash anything new, and as i had managed to overwrite hard spl - i couldnt flash what i wanted from the SD card! (if i could get the usb to work, i could fix it all - but as that was the problem i had to send it off fubar)
For some reason (god knows why!) it appears that t-mob are repairing my phone under warrenty despite the spl error but i wouldnt advise getting yourself in the same situation, as i was 100% expecting it to come straight back to me!
My personal advice is send it off with the correct rom, radio & splash screens (and remove security unlock if required) so the phone looks stock - the only difference will be the spl version. They probably wont notice!
1.90 or 1.95
Thx for the info guys, my new phone is coming and it took me about 2 to finally on its way. About the SPL, mine says 1.90 and that was when i first did the hard spl to change roms. What is the stock SPL 1.90 or 1.95? at loading it hows me 1.90 olinex i think...also i can change it if needed with my 8gb sdhc card or no?
I had a problem with my PC not detecting my fuze a few weeks ago. I found out it was my new firewall blocking the connection. I disabled the firewall and it worked like normal.
If it were me i would try to connect again after you flash the stock rom. If there was something wrong with the usb it still wont work. If it connects to activesync the maybe it was your ROM, or something else.
Just a suggestion

Categories

Resources