Related
I have a g4 8125 and tried to flash black diamond 2.0 using shelltool. I followed all the instructions, but I may have messed something up. I installed the enablerapi and certspcs files on my phone, but i realized later that i did this after turning off my radio. After flashing I made a hard reset, and now it just comes to the cingular splash screen and shows my ipl, spl, gsm and os (which it says is 6.0.0.0) and doesn't load anything. Anyone have any ideas? It won't connect to activesync either.
edit: sorry for my ignorance, thanks for the help though!
Please refrain from posting WITHOUT using the search bar. This question has been answered more than a million times.
For starters, hold down the camera + power button whil poking at the reset button
Hello there.
This is my first post, and I hopefully pray that I don´t get a "Please Do a search" kind of answer as I have been doing a hard search through the forum but haven´t found what I´m looking for. Probably I´m just using the wrong search terms but english is not my native language so I´m not sure how to look up for this issue.
First, I unlocked the sim of my device by sending it to a third party. Afther that, the phone came with a Wizard-Love OS installed, and finally I got excited and started to mess around with the Shelltool to get the device upgraded to WM6. (It´s a G4 by the way).
First I successfully upgraded to wm6 wee htc wizard v5.2.660, but then I found that the keyboard mapping was all wrong with the shown special characters (they weren´t where they were supposed to be at all), so i tried messing up with the registry trying to select a local language for spanish with no success at all....
Also I was having some issues trying to connect to internet via wi-fi even when I did get connected to the network, but did not test it hard enough.
Then I went farther trying to "shelltool" a Black Diamond 2.0 Touch rom, but then everything became a real mess... The Shelltool said that it was finish only like 4 to 5 minutes after starting so I disconected and Hard Reseted the unit. Don´t remember if I disabled the radio before flashing it, nor if I had the sd card installed on the device at the flashing momment, but definetly i had reinstalled the cert_spcs and EnableRapi cabs prior to this seccond attempt.
After the hard reset, it started but freezed on the first screen showing the ipl, spl, gsm and os (which it says is 6.0.0.0). Then I hard reset like two more times, with no luck. Then I entered on the bootloader mode, but after trying that for a while the phone stopped responding. It did not turn off, so I removed the battery. Then when I put the battery back the unit did not turn on at all. Even it did not show the charging red light when I connected it to the usb nor the wall ac adapter. I was devastated... I leaved the unit with the battery out all the night and the next day I reinstalled the battery to see that the device did turn on and did charge, but still it was locked on the splash window.
I tryed to reflash the unit using the bootloader under windows xp, after killing the activesync connection and using the wizard_Love_2.26.10.2_WEE_Novii_CF2 rom. The unit showed a progress bar so the pc and after 10-12 minutes it was done. I Hard reseted the unit but then it always started on the bootloader screen as if I was pressing the camera button.
Hard reseted, soft reseted, battery out and in, no luck. Then it went dead again. It did not turn on at all and no charging light. Once again i leaved the unit all day without battery and send it to the friend that had unlocked the sim for me. He just called me and told me that the unit was now up and running again with wizard_love rom. I´m really not sure how he did it. Probably i did something with the sd inserted when it was supposed to be out. I did flashed the wizard love on bootloader with the sd inserted but i´m not sure if that could have make the mess.
I would like to know if anyone have had this kind of lock up and how to deal with it (how much time to leave the battery out, etc). Also I will love to know how did my friend (he wont tell me as is it´s bussines and he charges for it) finally restarted my unit flashing wizard_love again, as I´m still too curious to not try to flash my unit again and probably be on the same mess once again.
Thanks in advance.
That's a lovely 1st post. If every one is to be like that.. it would be just to nice to help others.
Anyway, this may not sound logical, but I get problems with Shelltools when I do not have the official ROM flashed before another flash. What I would suggest is that, you ought to have an official ROM (check Wiki to download your official ROM flashing EXE), which seems to get me out of trouble a few times.
Also, it maybe wise to check your battery before any flashing attempt, make sure it is 100% (60% will do mostly, but in case of an emergency, that 40% helps). It cases where a phone doesn't go charge/bootloader, it is battery problem. The overnight thingy that you've done, probably rest the battery long enough to boost it to a charge (e.g. how you get a blink when you switch off a torchlight for period of time on a low batt).
Good also among your information, tell us the IPL/SPL/Radio on the ROM you are using.
Hi all,
I've been reading on this wiki/forum for a few weeks and finally yesterday night I had some time to install Prophet VIII on my qtek 200. I installed all apps I had running before and it all worked well.
Now I remember reading something about the "Lock" setting, but didn't exactly remember what and couldn't find it back either. I set it to prompt for a simple pin (3412) and even set my hint to 3412 in case i'd forget. After fiddling around a bit too much, things got messy and had to reset the device. Guess what, I got the device lock prompt and it wouldn't accept my pin code.
It also didn't retain clock settings (went back to 31/08/2006 12:00AM) and some small settings i changed in the control panel either. What's causing this?
I reinstalled everything, now everything works again but I couldn't find anything about this device lock thing, so i didn't enable it for now. Doesn't this feature work in custom roms?
Thanks.
This feature doesn't work with WM6...period.....
Has nothing to do with the cooked versions, but is a glitch in the original microsoft programming.
I'm using PDAViet Mysterious 1.0 and have got the same problem on the Lock setting after a soft reset.
After entered the PIN code, nothing would happen if I click the "unlock" button. It neither unlocks the phone, nor displays a error PIN messagebox. Nothing!
Soft Reset doesn't help. Everytime it asked for the PIN code, and I cannot unlock it since the unlock button seems useless.
At last I had to do a hard reset to restore the system.
I found a unique combination when the lock seems to loose the password and wouldn't allow to access even after soft reset; however every thing seems to be working internally i.e. it receives calls; txt. But it does not synz with Outlook and unlocks.
This happens when I turn off the phone and plug it into the charger and then turn on the power.
Does anyone know any remote-registry tools that can allow to override the password.
Strange thing.. So if I went out and bought a brand new WM6 phone, the lock wouldn't work either?
After upgrading to WM6, every works perfectly. But then, it seemed randomly, the display is blank/ all white, but I can the phone is still functioning, because i can tap on the screen and get the tap sound. Soft reset and hard reset doesn't work. I'm doing the hard reset blindingly since the display is showing nothing, guessing the key push (i pressed record-camera 3x then mail button). I'm pretty sure it did the reset because after about 30 secs I get the beep that comes on when the screen is showing Tap to setup your device.
I figured it might be a loose lcd cable, but if go into the bootloader, power+record+reset. The display works fine! Showing Serial V 2.07.
I took apart the BA anyways and made sure the lcd cable is firmly attached. It didn't work.
Sometimes the phone would go back to normal randomly, or if I let the backup battery drain, but not always. When it goes back to normal, the clock is always reset to 2004 12:00 AM.
Can anyone help me? Is it possible to have a loose LCD connector which won't be able to show normal display, but can show the bootloader normally? Or is it caused by something else?
Here are other things about my BA that may or may not be related to the problem:
-Can't use DOC_Repart to resize storage, I'm getting the FL_IOCTL_FORMAT_PHYSICAL_DRIVE failed as described here http://forum.xda-developers.com/showthread.php?t=255585
-When upgrading the upgrade program can't detect my current OS version (showing blank under "Your device is about to be update from:"), but otherwise the upgrade works fine.
-I tried Helmi R0, PDA Viet , and xplode's 6.00 roms. They all give me the same problem
Thanks.
I am also experiencing the same issue... currently phone is at white scren, but using My Mobiler i can see my desktop and see that the phone is fully functional, just white screen so cant use...
Mine too. I can see the display working perfectly using SOTI pocket controller pro. So the phone seems to be functioning except for some reason the screen is showing all white screen.
cubangt, are using an extended battery or the standard battery that comes with the phone?
Have you tried flashing with a different rom??
Sorry, I fear my message won't be useful at all for you, but I'll post it just for the record. I hope you can find the solution to your problem anyway!
My BA now can't show anything but a white screen because of what I think is damage to the screen cable (while sliding the display the backlight goes on and off...).
But the cable is not loosely connected, it is sort of strongly bent at one point, and maybe some contacts got kind of cut. Now it does not work anymore, but some time ago switching it off and the on again used to do the trick: the display would be readable again (even though with annoying colours, stripes and so on). I don't think this is your case, but I'd like to warn the newbies like myself that they should care not to lose any piece while changing the LCD on their BA: I think I probably forgot about some sort of protection which could avoid damages to the cable in its movement.
As for the missing version number when upgrading, the same has always happened to me.. I think.
Ok, sorry for my English, I would have had some troubles with exposing these few silly things even in my mother tongue... bye... and good luck.
I tried 3 different WM6 roms. And if I remembered correctly this also problem also occurred for a brief while I downgraded to WM2003SE while trying to resize the storage(which failed).
Yeah I'm not sure if mine is a hardware problem, since I can always go into the bootloader and the display works fine there.
I have new info to add though. I found out I can reliably get rid of the problem by draining the backup battery. Now I have a new question, since draining the battery takes a while, is there a way to reset the phone as if the backup battery is emptied (and return my display to normal)? If I can find a way to simulate this, then I can actually use my phone again, even if I have to do this once a day.
Obviously soft reset doesn't work. And I don't wanna do a hard reset either. Maybe the experts here now what kind of data is reset when all batteries are completely drained.
Thanks for the help
hmmmm
quick thinking.....i was working on my phone tonight and came across this thread.....if not grounded properly it could be that you statically fried a component in the process?
hi peopple. i have a htc touch p3450 with 128/256, the problem is when i turn off the device and then turned on appears the blue screen on windows mobile and the the device restarted and i have to calibrate the screen, put the hour, the password, and this steps, its like the device had a hard reset everytime i turned off. sometimes the device turned off from it self and i had to push the camera botton, volume up and reset with the device turn on, after few minutes the device starting again like the same way like i say you some lines before.
ok, the other day i try to find the way to fix my device, but i found a problem, better say two prolems. my device dosnt entry in a boot loader mode, and i try millions times on millions diferents ways and nothing happens. the second problem in this moments my device are totaly dead, only turn on the blue screen and i made the hard reset and nothing, dosnt start like before, i cant made anything. i try with a gold card anda nothing all result impossible
please experts i need yours help!!!!
peopple sory for my english, its so bad!! im from argentina!
i hope you can understend me anda try to help me
first of, sounds like your backup battery is dead, you tried charging overnight? That should hopefully charge it. Secondly, what else have you trid from the rom section? Have you flashed a custom rom?
If not, and overnight ac charge doesn't help the backup battery, do you still have warranth, as it could be worth returning to htc?
Stu
I think there's something wrong with your phone, with the phone's memory because it keeps forgetting things, try to make contact with your provider or HTC
Caution
Your problem can only be guessed from the info you have given
If it does something similar to a Hard-Reset every time you power on/off
then it can be a problem with the flash memory, or you can have a corrupted ROM
If its completely bricked (no backlight) and you head to the HTC Service center, and they find that you have custom ROM modifications they will most probably deny you warranty and/or service
Good luck
I personal think it has been overheated, buy/get/try a new battery and it will work again. turn it off and get a cooler or something like that and cool the phone and let it for 1 day on your table or somewhere and hard-reset the next day.
Cero92 said:
Hi all, i just got a Qtek 9090 with WM2003 (ITA). I upgraded to WM6.1, but now it has some strange problems: first of all, when it goes in standby, sometimes it doesn't wake up. If i have to reset it, most of times it doesn't boot (it shut down before WM loads) or i get R: None G: None and i have to reset again (otherwise the phone won't work).
The lock at the boot doesn't happen when the phone is connected at the USB port (i think that's because it charges, maybe it's a battery problem?)
Another thing is that i can't turn it off: if i hold pressed the power button, it deactivate the backlught but the device stays on, and if i make another long press, i get the backlight back again... I had this problem also with WM2003, maybe it's normal?
What do you think? Whan can i do?
Click to expand...
Click to collapse
Have you make a HardReset?
The correct HardReset, not only reset and press Power button!!!
See in my HowTo Section...
and why not WM6.5.5 see here
yep, hard reset is a good start, but about your other problems:
the device does not really turn off, like other phones. pressing the power button makes it go to hibernate, the display turns off, depending on your settings, it locks the hardware buttons and it shuts off wi-fi, it hardly uses any energy but gsm/gprs stay on.
the device seems to be off, yet the phone is one and you can be called. that is the closest you get to switching it off. when you turn on airplane mode, the battery consumption is even less so there is not really a need to turn it off.
pressing and holding the power button always was for the backlight. many other devices open up a shutdown menu when you do that, that would allow you to turn it off, soft reset, or switch off the backlight, but for the BA, that is not the standard. however, if i read it right, d-two is working on remapping the power button, probably for that cause.
the R: none G: none issue is known and not a problem with your phone, whenever you run out of power or remove the battery for a second, the next boot will be w/o radio (R and most roms don't allow booting without it. that's why you get stuck there and have to perform a soft reset. back in the days of wm2003 i used to remove the battery when the device froze to reset it w/o the stylus, because it didn't matter then. with cooked roms, it is different, just like the booting splash screen or the way to perform a hard reset, many things change on a cooked rom.
the issue with waking up from standby, or the SOD (standby of death) is an issue, that most likely has something to do with a backup, restored after flashing another os, or maybe you didn't perform a hard reset, as stated by d-two. you should do that, now that the device is still new, you have nothing to lose
also, read through the tutorials posted by d-two and myself, whether you missed anything while flashing.
The "real" hard reset is the one i can get by pressing camera + record button and reset? If so, i already did it after flash (i use d-two 6.1 Manila ROM in WWE)
It shows me 3 options, i put on YES "Clean Registry Hive" and "Format Storage" then i press the mail button, the screen become white for a while and the next boot al seems to be ok.
It seems, because after some time i get again the "standby of death" and, if i press the reset button, the most of time it won't boot up again (it turns off before i can get to WM), if it works phone doesn't. All these boot problem can be avoided by connecting the phone to the usb cradle, so maybe it's also a battery problem, i think...
@ d-two: i'll try your new ROM, however before i've tried your 6.1 ROM
I've already read your guide because i've got Windows 7 and i couldn't flash without your tutorial
NEWS: installed d-two new ROM, after flash i made the hard reset selecting the second and the third options, then i get the blank screen and, when viewing the htc screen, it shut down itself like it did before
As always, with the usb connected, it has no problem :\
It can be battery power - battery is old, and it doesn't provide current [A], or voltage drops [V] and phone think, it's empty.
Maybe you can try with new battery, or buy 2 nokia bl-4c batteries and repair orginal battery (somewhere on forum there is a tutorial about that - but use bl4c, not bl5c like in tutorial - bl5c are too thick to fit)
n0rbi666 said:
It can be battery power - battery is old, and it doesn't provide current [A], or voltage drops [V] and phone think, it's empty.
Maybe you can try with new battery, or buy 2 nokia bl-4c batteries and repair orginal battery (somewhere on forum there is a tutorial about that - but use bl4c, not bl5c like in tutorial - bl5c are too thick to fit)
Click to expand...
Click to collapse
That's what i was thinking (and that's i hope it isn't)... Now with another recharge cycle it seems to be good also with cooked ROMs, i hope it's solved
Maybe you just have to charge/discharge it for 4-5 times, and it will restore it's capacity. Mine BA was turning off when battery indicator was showing ~60-70%, and now I'm waiting for new battery (i destroyed original )
"charge/discharge it for 4-5 times" does not have an effect on Li-ion kind of batteries. This is probably a software problem. When you turn your phone on (after removing a battery) it always shows "None" for R and G, so just press Reset button and it will be ok. I use Reset to power it on Then you can flash 6.5.5 which doesn't have problems, and do a hard reset. There should be no problem at all..
I also got the problem with the stock ROM :\
The R: None G: None error is the less important problem
Got any luck fixing it? I've had similar problems before, sometimes it turned itself off when the battery was at 60% in WM2003. Did you update to d-two's 6.5.5?
Yes, now i'm running d-two's 6.5.5 ROM.
No, i still had the problem Yesterday i called to the assistance service and they said me to remove the battery and after a while recharge it.
I put off the battery yesterday at 16 and i put it again in the phone this morning at 8, i charged it but i still have the problem
This evening i called again and they said me that i have to send it back, i'll flash the original ROM and send it on monday.
That's a shame, i really like this device, even if it's not mine, my sister uses it and she's not a pro user, what a waste
Didn't understand, what "assistance service"? This is very old phone, I just can't believe it has some kind of warranty
I have another battery, and using it the device turns it off sometimes while it's in the stand-by mode! Don't know why, the voltage on it is fine, I have measured it while working...
marko_serb said:
Didn't understand, what "assistance service"? This is very old phone, I just can't believe it has some kind of warranty
I have another battery, and using it the device turns it off sometimes while it's in the stand-by mode! Don't know why, the voltage on it is fine, I have measured it while working...
Click to expand...
Click to collapse
I bought it on an eBay market and it offered 60 days warranty. It's not official HTC/Qtek warranty, but it doesn't make difference, as long as the device will work
If for you it happens only when it's in standby, maybe you just have the standby of death, the problem Chef Tony was talking about at post 3?
Cero92 said:
I bought it on an eBay market and it offered 60 days warranty. It's not official HTC/Qtek warranty, but it doesn't make difference, as long as the device will work
If for you it happens only when it's in standby, maybe you just have the standby of death, the problem Chef Tony was talking about at post 3?
Click to expand...
Click to collapse
My Roms have no SOD
This is when vbase32 have all 01000000 base adress !!!
Search about SOD!!
No, this happens only with my old battery. I'll try it out now with this new ROM!
I was trying to understand his problem
Just to know, what kitchen do you use?
Cero92 said:
I was trying to understand his problem
Just to know, what kitchen do you use?
Click to expand...
Click to collapse
First i have create my own kitchen but then i have found the OSBuilder and this is the best kitchen ever
With this kitchen you can look the Vbase32 for SOD!!!
Well, i trust you that your ROMs doesn't have SOD problem, in fact this happened to me also with the shipped WM2003 ROM, it's a real hardware issue
Cero92 said:
Well, i trust you that your ROMs doesn't have SOD problem, in fact this happened to me also with the shipped WM2003 ROM, it's a real hardware issue
Click to expand...
Click to collapse
I think so, sorry
d-two said:
I think so, sorry
Click to expand...
Click to collapse
No problem, i'll send it to the assistance on monday, i hope it won't take too much time :\
Cero92 said:
No problem, i'll send it to the assistance on monday, i hope it won't take too much time :\
Click to expand...
Click to collapse
good luck But very cool that you have warranty