I recently used Faria's How to and unlocked my phone, loaded his crossbow rom etc. My phone works flawless.
Now i am attempting to do a friends 8125 (g3)as well. Ive followed the how to exactly and im having a small problem. The first time i tried to downgrade to the buttons 1.05 rom, it froze up. I rebooted, and tried again, its hanging up showing 99% on the PC and 98% on the 8125 and WILL NOT MOVE. I also of course can not get an activesync connection due to the fact that the only screen i get on the 8125 is the 3 color screen. Anyone have any ideas? Quick responses would be greatly appreciated!
When applying ROMs sometimes it appears to stop at 98 or 99% but it isn't. You have to wait for a while - up to 10 minutes I suppose (worst case).
The three color screen is fine. Plug in your USB and the letters "usb" should show in the lower left hand corner. Start your ROM upgrade when you see this.
Let us know...
Related
Hi,
I have a Qtek9090 which I upgraded yesterday to Helmi BA WM2k5 AKU2.6 Beta (v.1.1.2 Beta).
Everything went fine and I do like it (apart from the usual problems with WiFi, BT,...).
However I got into a shock-state when I turned it on this morning after leaving it in the craddle during the night for charging:
It would turn on, but the screen was completly f..ked up!!!
I did a Softreset -> screen still messed up
I did a Hardreset -> screen still messed up
I did reflash the upgrade -> screen still messed up
I took out the battery for half an hour and put it back -> still the same
After many resets and so on, suddenly I got the color stripes again and the phone booted normaly. I did not even loose any data.
Next I put it to charge again and after a while (the screen went off meanwhile), I turned it on and guess: scrambled screen again.
This time, I did the Reset this way: battery-notch off, kept the Softreset pressed and simultaneously put the battery-notch on again.
Is this a known problem (shouldn't be - I searched the forum!)?
Why does this happen?
Any ideas???
Also, I have these questions:
- What is this selection one has to do after the upgrade for (2. and 3. item YES)? What should the first item be: YES or NO? Can this be the cause for my problem?
- Would it be wise to downgrade again? (In case this is a defect -> so I can try to claim warranty, if things get worse...)
- What is the patch for energy management for? Where can I download it, as the link in the Wiki does not work? (Has this to do with my problem?)
Thanks,
vma
The problem remains.
It does not seem to depend on the charging, but happens when the device is turned off for some time.
When I turn it on it will either work fine, or funtion with a wild flickering screen.
Arrggghhhh!!!
Am I the only one with this problem?
Cheers,
vma
Hi,
Some month have passed on this issue. The reason I did not post about it, was because I had to send my BA for repair and one never knows if the "enemy" is listening... Now the warranty has expired anyway and mey BA is fully working.
It may have been a coincidence, but one day after the upgrade the screen went mad and totally messed up. Only 1 Hardreset in about 100 tries would bring it back to normal for some period of time and even reflashing it with WM5 or 2003SE would not make it work normal again.
The screen would get messed up suddenly for no particular reason, normally during a standby.
At the end I had to send it in for repair, which was actually a good thing, as I complained about the loose stylo and bad working hardkeys, all within warranty.
I got a new key-pcb, backside and they reflashed the device with 2003SE.
I am almost sure that I must have done something wrong with the upgrade to WM5.
Strangely I was able to flash 2003SE onto it, though it did still not work properly: hours with messed screen and sometimes out of the blue I would turn it on and the screen was OK again for a few hours.
Could it be a bad cable connection, which got repaired as well? Was it just a software problem?
One of the things I was in doubt with: when you enter this menu to format the device, the instructions say to switch two options, but the menu on my device had three options. Sorry - I do not exactly recall the details.
Anyone with an idea, why my device went mad?
As a side-note: while WM5 was great, while it worked during the one day it worked. I specially liked to be able to turn the device completly off or being able to remove the battery without loosing data.
However: not having my beloved BA fo two weeks made me reconsider doing experiments on it. Since I have it back I did not reconsider flashing it again.
But I would like to understand what had happend...
Cheers,
vma
May I assume from the lack of replies, that this was a pure coincidence on my device?
Nobody else experimented this weird problems after upgrading to WM5?
I am considering upgrading my phone again, essentially because I am tired of being afraid of discharging the battery and thus losing all data...
Cheers,
vma
I have just been trying to upgrade my Wizard, I have done this many times before, I tried but failed with a few ROM's and last I tried Molski's latest, now, it is just dead, after I try a hard reset, I get the red blue green screen for a few seconds, I even see it connecting to the USB and then the screen just goes black.
Pleas help with anything
Sounds to me you're battery could be empty/dead
It was full last night, so I do not think this is the problem
It was full last night, so I do not think this is the problem
Try another battery and see.
And keep us posted
I agree, it sounds like your battery is drained. And since it goes to the boot loader, that means your battery will not charge on your phone. You'll have to borrow a battery that is charged, or get someone to charge your battery.
azmerlin said:
It was full last night, so I do not think this is the problem
Click to expand...
Click to collapse
What state did you leave the phone in over night? Was the battery removed, or was the phone fully off..?
Interesting. I seem to have a similar problem. I only get the boot loader screen.
But i can establish a USB connection and update my phone. It will go all the way to 100%. Then the phone will switch off and start new. But instead of loading the OS it goes automatically into the boot loader screen.
Any idea what went wrong here?
lingley said:
Interesting. I seem to have a similar problem. I only get the boot loader screen.
But i can establish a USB connection and update my phone. It will go all the way to 100%. Then the phone will switch off and start new. But instead of loading the OS it goes automatically into the boot loader screen.
Any idea what went wrong here?
Click to expand...
Click to collapse
Since you haven't told us what you were trying to do when this started, what rom you tried flashing, and what your current IPL / SPL are and whether this is a G3 or G4, no, we don't have any ideas on what is wrong .
Read and follow this:
http://forum.xda-developers.com/showthread.php?t=298613
I would suggest you try flashing your carrier's latest official rom to get a working device back.
Bricked
If install IPL 3.08 in G4, exist solution or not
One thing to add : if the battery is really low, then it will likely not charge or respond via USB. It is necessary to use the wall charger in this case. It must have something to do with the amount of charging current that can be delivered to a flat battery.
luisprieto said:
If install IPL 3.08 in G4, exist solution or not
Click to expand...
Click to collapse
I'm not sure if you are asking a question or what. But if you try to install IPL/SPL 3.08 on a G4 device, your device will be bricked (ie: dead). I did see where someone in the Wizard forum said they were able to do a JTAG recovery and get their G4 back.
mfrazzz said:
Since you haven't told us what you were trying to do when this started, what rom you tried flashing, and what your current IPL / SPL are and whether this is a G3 or G4, no, we don't have any ideas on what is wrong .
Read and follow this:
http://forum.xda-developers.com/showthread.php?t=298613
I would suggest you try flashing your carrier's latest official rom to get a working device back.
Click to expand...
Click to collapse
You are right, sorry.
I used to have Aserg3.12 Rom on my device (G4). It worked well for at least two months. Suddenly the phone crashed in the middle of a call and didnt react anymore. Hard Reset nothing worked.
I got somehow the Boot Loader Screen back and downgraded to the original rom (QTEK novid, 220734, 2207114). Problem was whilst it finished the upload process until 100% and restarted the phone, it got stuck at the OS loading page. After 1 minute the screen started losing its colour and turned white. If I soft or hard reset the same happens, it turns white at the OS loading page.
At some point I got through miraculously, it started up and everything was fine. I charged it, upgraded to smart1 wm6 v2 and everything seemed to work. However again some 10 minutes into a call, the phone crashed and back to square one. Downgrade to old rom, got again stuck at OS loading screen etc.
I then put it over night on the charger. The orange charging LED was blinking in 5-10 sec intervals. In the morning it was red. I started the phone again interestingly got through and got it running. Battery was fully charged. But again: 10 min into a call, the phone crashed. And trying to reboot I get to the OS loading screen, then it turns white. I put it back on the charger LED is blinking, guess I have to wait again for some hours.
Thanks for any help or suggestion,
forgot that:
IPL 2.15.0001
SPL 2.20.0001
Aserg3.12? smart1 wm6? Are you sure you've got a wizard? Aren't those prophet roms?
Hello, I am new to this site and the whole BA experience. I got my sx66 about a week ago and decided to upgrade the ROM to 1.33.51. Yes, from what I've gathered from reading it is also a little out of date, but I was trying to start out small. Well, at some point things went terribly wrong, everything seemed to be well, when all of a sudden my screen went blank and I was left with a screen that just says serial at the top and v 2.07 at the bottom. I have left the battery off for about 20 hours now, waitting on the backup battery to die(from what I understand my phone may be stuck in bootloader mode and this should fix it) Well, I just got home from work and the phone still says the same thing if I put the battery on. Any help or suggestion would be appreciated or even just a "Hey, your phones gone" would be as well, just curious to know what to do. Thanks!
Yes, you're in bootloader mode. It's now ready for upgrade.
If you put it in cradle, it will change from 'Serial' to 'USB', run the upgrade and do the (Record,Camera) reset with 'no,yes,yes' and press 'Mail' button.
Most of these are in the Wiki.
Guys,
I'm in front of a peculiar problem in my HTC Touch diamond; it started around 2 weeks back when I powered on the device it got stuck up at the point where it displays "Touch Diamond" in white fonts in black background...normally, after this point the version details flash in red font at the bottom right corner... But in this case it's getting stuck up at this point not displaying the version details like R 1.09.25.23 …. etc.
assuming that the battery charge is low, I put the device on charging, then after flashing the centre (round) button white light twice or thrice, the device start reboot again and again got stuck up at the "Touch diamond" point, if I continue to charge the set, this cycle starts repeating endlessly.
Then, to check, I got the battery charged in an external charger for 24 hours, and also procured a thick battery (Model. DIAM171, Rating: 3.7 V DC & 1340 mAh) too, and kept the device open for 48 hours or so. The device started smoothly and was functioning well for next ten days.
Then this insect called "new ROM" started biting my brain (?), and at first I had flashed an unsigned hardSPL v1.40 Olinex. Then Radio 1.09.25.23 and then the Sone wwe 2.1. All the flashes were done individually, and successfully.
And by the way, I'm no monkey to this flashing thing too, of course, the courtesy and credit goes to the whiz kids of XDA-Developers for the learning imparted on me. Earlier I'd flashed i mate KJam, then HTC ARTEMIS successfully too.
But, alas, after running the new rom nicely for a few calls, and after one more soft reset, it has come back to square one. That is, "when I powered on the device it got stuck up at the point where it displays "Touch Diamond" in white fonts in black background...normally after this point the version details flash in red font at the bottom right corner... But in this case it's getting stuck up at this point not displaying the version ......"
Please help...friends.... plzzzzzzzzzzzz...help....
By the way, the device is going to the Bootloader smoothly on pressing the volume down button while soft reset.
I tried hard reset the device by pressing the round button and the volume down button while soft reset the device and did hard reset it successfully. Still the problem remains.. plz buddy, plz help...
Yep, found your post...after replaying to ur PM
But I'll post here my answer in case that anyone else could also been interested in it:
"Sorry to hear this issue, although I haven't seen this post in the forum...
Ok. based on your story I think that this issue has nothing to do with the cooked rom you've flashed.
It seems more like an SPL problem. I'd suggest to flash the latest HSPL, the 1.93 one.
Till now none complained about such kinda issue... They bricked the phone or they didn't...But such kind of intermediate behavior never heard...
An other suggestion, try to flash with a branded ROM (try downloading the latest official for ur device).
Waiting for ur feedback.
Good luck!"
at last my Diamond is working again...
Warm regards to Shaks1979 & SeatOne for ur kind and quick response... anyway, my diamond is working again......Yeterday... I had started flashing the Radio... earlier the Radio version was 1.00.25.03 (that came with my phone from the factory) which was upgraded to 1.09.25.23 as the ROM Cooker i.e. Seatone is too using this radio ( SONE v.2.1 WWE by SeatOne)
Yesterday, I flashed the Radio version 1.00.25.05 and the phone started working again.
Guys, as soon as the phone started working, I had flashed two more roms, just to understand what went wrong, & the ROMs are (v6.4FullHDTFl by christonge) and (XBMOD_V2 by xboxmod). The flashings went smoothly. At this moment my phone is on XBMOD_V2 Rom & Radio 1.00.25.05.
After seating back, I tried to understand what went wrong, why the phone was not going beyond "Touch Diamond" display point (in white font) and getting stuck up at that point before the R.... G..... etc version details appear on the screen with font colour red and background black.
The problem was with the Radio 1.09.25.23; but the mechanism of the problem went tangentially above my head, I'm in total darkness. Guys, can anyone of you genius can throw some light.
I shall wait for your inputs in the matter.
I have the same problem. After rebooting ok it goes to start up and gets stuck at the touch diamond screen with info about the radio and stuff in red. It won't turn on for me to re-flash it.
So you just fully charged it and left it a while without the battery in then tried again and it worked
Any help would be great... 8-s
Hello
Ive finally got round to putting new radios and ROM on my diamond, a year after buying. Didnt want to before now incase i cocked it up (theres a lot of things to remember!)
Hard SPL went fine and i was putting the new radio on (1.00.25.05 in this case) when, at about 80% of the way through the install my pc froze (as its having a habit of doing at the most awkward times recently!)
I soft reset the diamond but now its at what i assume is the bootloader screen (?), its got red, green, blue and white bars and various writing, along with a message saying 'Upgrade ROM code error Please try again'
I had a hunt round and found something for another device saying how to get it back by loading a factory ROM through the bootloader menu but i dont know how to do this as i dont have a connection to activesync (phone wont go beyond this screen) etc.
If someone could explain in relatively simple steps it would help!
I should also clarify that the only way i can get this screen off is to remove all power but as soon as i put power back on it loads up direct to this screen again!)
When you device is in bootloader mode, you dont need active sync connection. just run the update utility and it will work without it, as it uses different drivers when connecting.
This turned out to be quite easy actually, i stumbled across the answer somewhere else!
Thanks for the help