HELP: can't flash original rom on G3 wizard. - 8125, K-JAM, P4300, MDA Vario Software Upgrading

Facts:
QTEK 9100 IPL/SPL 2.17
After HTC logo it goes to QTEK logo, then fades to white and reboots.
After x number of reboots it sometimes boots Windows WM5. No radio though.
Story is long, sorry.
I wanted to upgrade my phone to WM6 last summer.
Since I was careful not to brick my phone i ordered help from IMEI-Check.co.uk.
I got the code and the software and got busy.. It did'nt work however.
First time it seemed to go fine at first but later it reported to have lost communication with the device. On reboot it would display the problems on line 4 and 5 above. I followed advice and reflashed the device with original rom. Now the device was fine again.
I retried the procedure but got the same problem.
again I tried to reflash original rom but now RUU reported "Invalid Vendor ID"
I sent the device to repair but got it back in the same condition I sent it. "Moisture damage". I opened the device but found very litte evidence of moisture damage.
The device have been sitting in a box ever since, I bought a TYTN, but now I would like to see if there is really nothing I can do to bring my Wizard back to life.
Any good advice will be very appreciated.
Regards
/m

Since warranty is void and you already opened the phone i suggest you get an old tooth brush and some alcohol and give a good 'sponge bath' to it just in case there's some short circuit happening in a hidden place. Be sure to have it well dried before inserting the battery (leave unassembled for some hours or use a hair dryer from a large distance)
After that get phone in bootloader mode and write a 1.xx ROM to it to attempt CID unlocking via free procedures.
If that goes well just upgrade to a 2.xx ROM (with IPL/SPL) and then to WM6
good luck

I will try it
but can there really be a short circuit if the device has been in a box for 6+ months? I suppose it's possible.. I'll let you know.

Related

IPL and SPL = brick

Well today I tried to just do the IPL and SPL flash from the tmobile rom. Apparently, thats a bad thing. Thank god for Warranty. Bricked it almost instantly. That will be the last time I try that.
Nope -- sorry. Warranty won't cover bricking/flashing your phone with anything other than an official ROM.
Your best bet is to try to get it back into bootloader and reflash. If that can't be done, you've acquired a really expensive paperweight.
nottoosmart said:
Well today I tried to just do the IPL and SPL flash from the tmobile rom. Apparently, thats a bad thing. Thank god for Warranty. Bricked it almost instantly. That will be the last time I try that.
Click to expand...
Click to collapse
Define "brick". You aren't saying what it does or doesn't do (ie: what exactly happened to make you say its bricked). You also haven't said if its CID unlocked (I assume it is since your sig seems to indicate you were running WM6). You also aren't saying if this is a G3 or G4 device (the IPL/SPL you list in your sig would indicate G3, but you have to be sure of that).
Try turning the phone off (if it still powers on and off. Or remove the battery if you can't get it to turn off, then put the battery back in once its off). Then plug in the USB cable, press and hold the camera button, then press the power button to turn it on (with the camera button still pressed). If you get the rainbow screen with the USB indicator in the lower left, you can then try using that to downgrade to a 2.x ROM (T-Mobile 2.26 shipping one is good) or all the way back down to the Button 1.05 ROM.
Provide more details and one of the gurus may be able to assist. And details of exactly what you did to get to the point you are at would be very helpful too (either to assist you, or to help others learn not to do whatever it is that you did if it is truly "bricked").
It will not turn on. It is a hardware issue. And according to HTC within the warranty, the only issue they will not cover is any physical damage caused to phone. I had it boot to os then it just turned off. Never to turn back on again.
Basically I extracted the IPL/SPL from the TMobile 2.26 os. Tried just flashing those but I dont think i set them correctly in the nk file. As for power, It gets none. So i cant even get it to turn on.
Its a G3 fully unlocked. Ive been working on writing my own version of WM6. I might wait now after this little deal.
Well, after getting my replacement today, I tried to power it up and it wouldnt. Took the new phone and battery to Service center. Apparently what happened is that the battery shorted out and killed the phone. Battery was covered under accessories warranty. So hopefully tomorrow i will be up and running.

wizard wont turn on after o2 rom update

i have been updating and trying different roms over the last couple of days, i decided last night to revert back to o2 xda mini s original rom downloaded from o2, uploaded the wizard-love rom then started the updsate as instructed, followed the instructions and it installed, however when i soft reset during the 3 second customisation period, the device shows no sign of life, and wont turn on............................................i would like to know if i have bricked my phone, or there could be other reasons, before i go to the expense of getting repaired.
the only info on the device i can remember was i had the wizard-love rom installed before the upgrade and it is a G4 device and i am gethering it is(was)CID locked.
Many thanks in advance for any assistance someone/anyone can give
I think the o2 rom you were trying to load contains IPL/SPL. On a G4 this could mean a bricked phone. Still, I think I've heard people using their carriers rom on their G4 without problems? Could someone confirm this? I always take out the IPL and SPL and recook the rom just to make sure.
You don't even get to the IPL/SPL screen? You could try putting it onto the wallcharger for serveral hours and try again. Good luck!
i hear you and thanks for reply, only tried that rom as it is the only o2 rom and actually says it is the factory one for my phone, so must admit , presumed it was compatible....................while i am writing does anyone know of a way of reviving this problem, even if it means a price,
regards
just to update, no ipl/spl screen or life at all , tried the wallgharge but nothing as yet, regards
cid locked
are you getting any response from the phone at all? if not leave the battery out for at least two hours then put battery back in and just charge from the wall without turning on the device for at least an hour. if it still doesnt turn on whatsoever its bricked!
if thats the case then do as i did last year when i accidently bricked mine and claim that you lost your phone to your insurance
good luck
mark
no responce at all, will try your suggestion , however as i bought it off ebay no insurance and no contents ins also, never mind .............easy come easy go
regards
another update, contacted ok xda repair center and as it is " bricked " will cost me in the region of £185, so not sent..............however thanks for the help everyone , much appreciated
good to hear that your enjoying your phone again..
just be very very carefull nextime..
-004
thanks for the reply, not using phone as still bricked , so bit the bullet and have just pusrchased an xda orbit, however will not be updateing roms for a while , at least until i get some use out of the phone
regards

I Think Its Bricked!!!!!

OH MY GOD I WAS TRYING TO GET MY PHONE BACK TO FACTORY DEFAULD AND IT WENT TO SWITCH THE PHONE INTO BOOTLOADER AND IT SAID IT WAS A COMMUNICATIONS ERROR AND THE 8125 NEVER CAME BACK ON , THE CHARGER LIGHT DOESNT COME ON IF I PLUG IT IN TO THE WALL CHARGER, BUT IF I TAKE THE BATTERY OUT THE SCREEN WILL GO WHITE FOR A SHORT SECOND AND THE CHARGER LIGHT WILL FLICKER
DO YOU THINK ATT WILL TAKE IT BACK I HAD IT 6 DAYS AND IT WAS HARD SPL 2
Srry for my bad english
You should have a 30 day warranty on the device from store you purchased it from. If not, just contact HTC support if the device will not boot.
so just make up some excuse to send it to att
Be careful when trying to lie to AT&T or T-Mobile. If your device is CID unlocked then your warranty is void. They may not realize this at first but once they dis-assemble the device for refurbishment they will and they may be able to trace it back to you so just be really careful.
can you get into bootloader mode?
are you sure the battery was charged enuff to reboot again?
try changing the battery if you have another fully charged one adn try to get into bootloader ode if you can then youre fine dude
dharvey4651 said:
Be careful when trying to lie to AT&T or T-Mobile. If your device is CID unlocked then your warranty is void. They may not realize this at first but once they dis-assemble the device for refurbishment they will and they may be able to trace it back to you so just be really careful.
Click to expand...
Click to collapse
Don't try to scare of people!
I exchanged my MDA three times no problem for CID unlocked half years ago! it will not void your warranty!
cgigate said:
Don't try to scare of people!
I exchanged my MDA three times no problem for CID unlocked half years ago! it will not void your warranty!
Click to expand...
Click to collapse
A friend of mine screwed up a G4 8125 he had (I tried to warn him about not flashing anything he found) after he had CID unlocked and flashed some rom from another website (it wasn't from here). He sent the phone in to Cingular telling them that the phone had quit working. They sent him a replacement with no questions asked. About 1 month later he received his old phone back with a letter stating his warranty had been voided due to software upgrades they had found he had done, and he had a charge on his next bill for $399 for the replacement phone they had sent him. He fought Cingular for a couple of months over it, but they held firm to what they had found had been done, and last I knew he finally just paid the bill (over time).
So, I'm glad you were able to do exchanges with T-Mobile, but I know first hand someone that got burned trying to do this, and Cingular did know what had been done. Its not an urban legend, or a story just to scare people. Using tools here will void your warranty. I think in most cases the carriers will not determine this (Like yourself, another friend of mine that I put Crossbow Unloaded on his phone, had issues, and Cingular replaced it with no issues), but it does happen...
mfrazzz said:
A friend of mine screwed up a G4 8125 he had (I tried to warn him about not flashing anything he found) after he had CID unlocked and flashed some rom from another website (it wasn't from here). He sent the phone in to Cingular telling them that the phone had quit working. They sent him a replacement with no questions asked. About 1 month later he received his old phone back with a letter stating his warranty had been voided due to software upgrades they had found he had done, and he had a charge on his next bill for $399 for the replacement phone they had sent him. He fought Cingular for a couple of months over it, but they held firm to what they had found had been done, and last I knew he finally just paid the bill (over time).
So, I'm glad you were able to do exchanges with T-Mobile, but I know first hand someone that got burned trying to do this, and Cingular did know what had been done. Its not an urban legend, or a story just to scare people. Using tools here will void your warranty. I think in most cases the carriers will not determine this (Like yourself, another friend of mine that I put Crossbow Unloaded on his phone, had issues, and Cingular replaced it with no issues), but it does happen...
Click to expand...
Click to collapse
Thank you.
I do not lie to people or try to scare them... I am merely looking out for people. Fortunately when I received my handset exchange, I had a G4 that was not CID unlocked and I just put the original firmware back on it before sending it in since it was hardware reasons that I sent it back.
now im scared and dont know what to do the battery was fully charged
i was trying to frlash the original rom and the phone bombed when it went to bootloader,
No need to be scared. I was just looking out for your wallet.
Are you using Vista? Vista cannot talk to your device in bootloader mode.
Also, I highly doubt your device is really bricked. It takes something really stupid to brick your device. Unless you flashed a G3 IPL/SPL to a G4 device or vice versa, your device cannot be permanently bricked. There's got to be a way to fix it.
List all information about your device... service provider, model of phone, IPL/SPL, Whether you think it is a G3 or G4, and a history of everything you did to your phone since you started messing with it.
Hopefully with all of that information, we can figure out what you did wrong to cause this and hopefully find a solution.
Try to get back into boot loader.
Pull the battery out, then put it back in
Hold camera button and press the power button.
It should take you to a rainbow screen (bootloader mode)
If it does, then you are ok. No harm no foul...
Then try and reflash the latest Cingular 2.25 release available from HTC's website
If it does not turn on, then you probably toasted the battery or the mainboard. HTC has a long warranty on hardware issues. They dont cover the battery, but AT&T will, if the phone replacement does not get your phone back up. This is what happened to me. All you have to do is tell them you plugged the phone into charge (which you were doing without even knowing it) and then the phone went dead, never too boot again.
Thats exactly what I told them, with my CID unlocked G3. They replaced and I was all good.
Everyone has a diffrent tale to tell so take the advice as just that. Someone elses experience. Hope this helps.
Its a 8125 g4 the hard spl cingular not sim unlocked the phone's light flickers when i take the battery out i purchased the refurb one and i was reading att's website it said somethin about they will charge you the online price well its only 80 bucks just in case
i knew i shouldve traded with my neice for her G3 , I ordered three 1 g4 and 2 g3's
i Was going to tell them exactly that but i wanted to check here because u guys r smart by the way i charged it this morn and went to flash it back to factory and it bombed do you think the battery is dead
Ok, so enough with the horror stories (my intent wasn't to scare you, but just make it clear, I have seen AT&T back charge someone, so you (and others) can understand the risks)...
Now, lets see if we can recover this device for this guy...
First thing first. Pull the battery out of the phone and leave it out for an hour (or more).
Next - Pull your SIM card out. Make sure the contacts are clean on the card. Put the SIM card back in and make sure its seated well.
Now, put the battery back in. Try to turn on the phone (I doubt it works, yet, but lets give it a shot). If by chance the phone does turn on (most likely to the bootloader mode, then hook up the USB cable and try flashing the Official rom for this device.
If it doesn't turn on (what I expect), then pull the battery again and leave it out for 15 mins. While the battery is out, try to turn on the phone once. This is just to discharge any charge that may be in the device.
After 15 mins, put the battery back in and DO NOT TRY TO TURN IT ON. Now, get your AC wall charger for your phone, and plug your phone in. Again, do NOT try to turn it on yet, just plug it in. Let it stay hooked up to the wall charger for 1 hour without doing anything else to the phone. I'm hoping that at some point during this time, the battery charge light may come on. If the light does come on then let it charge up.
If the charge light still doesn't come on, then leave it plugged in and try to turn on the phone. I'm hoping by this time it will work. If it doesn't then you may have to do a search on these forums for JTAG and look at the hardware option of getting your phone back (I've never done a JTAG operation so I can't help you with it. In the Wizard forum there were discussions of this last winter / spring where someone rescued their bricked phone.
Hope this helps...
just waitin and hopes this works if it does how can i repay you? Free computer software (not Warez) a legit purchased program
the-equinoxe said:
Usage:
-connect your device
-Start hard_SPL-G4.exe
-Push the "Check DOC" button
-> The tool now checks whether your device is truly a G4, if not, it will give you an error and stops.
-> after this a dos box pops up, and it loads the softSPL to your device, to enable hard-SPL flashing.
-> then a Rom Update Utility will start, ONLY proceed if your screen is white!
-Proceed with the upgrade, it will only take a minute.
After reboot the IPL version is : 2.21.0001 and the SPL is 2.21.olip
Now you have Hard SPL
You can flash the ROMs with the RUU in the ROM package, should you have trouble with upgrading, try Mun's RUU (thanks for the tip Boto).
So no need to downgrade before upgrade anymore.
But don't flash ROMs containing IPL/SPL.
_____________________________________________________________________
As I have mentioned before in this post:
You shouldn't try to update ROM's with IPL/SPL after HARD SPL.
BUT: If you want to update IPL/SPL for G4 after hard SPL, do as following:
-disassemble ROM with IPL/SPL of your liking
Usage: typho5.exe -x nk.nbf
-reassemble the ROM or IPL/SPL with NKnbftool.
Make shure you only use G4 IPL/SPL for your G4, those are the IPL_2 and SPL_2 files created by typho5.exe.
-copy the nk.nbf you just created to SOFT SPL Folder
-start Soft SPL and flash the IPL/SPL.
You will lose the hardSPL though!
Typho5.exe and nknbftool are available in most kitchens.
Click to expand...
Click to collapse
I already did most of the work for you. Linked below is the Official AT&T IPL/SPL 2.25.0001 in nk.nbf format with SoftSPL. Just download from the megaupload link below and use SoftSPL to flash the new IPL/SPL. This will remove HardSPL and you should be able to restore the AT&T Official Rom.
REMOVE HardSPL
EDIT:: I know this is not much help to you now, but should you be able to get your device to turn back on, this is what you're going to need to do.
look man I had experienced a problem if it is like yours I can tell you what I did to solve it?
I had a problem in I-mate jamin G3 after upgrading with a wrong rom It doesn't work
If i connect the device to the charger it lights with the 3 color screen
but if i connect it to the usb it flicker with no connection to activesync.
I went to the service center and they told me I have to replace the mainboard
this meant that about 400 $ in my country.
I searched this forum until I found a thread guided me to resolve my problem without changing my device's board.
abc12345 said:
OH MY GOD I WAS TRYING TO GET MY PHONE BACK TO FACTORY DEFAULD AND IT WENT TO SWITCH THE PHONE INTO BOOTLOADER AND IT SAID IT WAS A COMMUNICATIONS ERROR AND THE 8125 NEVER CAME BACK ON , THE CHARGER LIGHT DOESNT COME ON IF I PLUG IT IN TO THE WALL CHARGER, BUT IF I TAKE THE BATTERY OUT THE SCREEN WILL GO WHITE FOR A SHORT SECOND AND THE CHARGER LIGHT WILL FLICKER
DO YOU THINK ATT WILL TAKE IT BACK I HAD IT 6 DAYS AND IT WAS HARD SPL 2
Srry for my bad english
Click to expand...
Click to collapse
I read somewhere on this forum that if you want to flash in bootloader mode, you have to switch off USB connection in ActiveSync, go into bootloader mode and then connect the phone to the PC. After that flash your original ROM.
I also had an issue that my wizard battery would not charge. I used an third party USB wall charger, that wasn't good enough... I had to use the HTC wall charger to recharge the battery, it has a little more power.

I-Mate K-Jam scrambled screen since flashing

Hi Everyone this is my first post on xda Developers so go easy on me
Ive been reading alot about flashing to upgrade the wizard/K-Jam to use WM6 and thought i quite liked the idea, so decided to investigate further.
Im new to flashing phones/PDA's but not new to the concept of firmware and EEPROM flashing and PC's etc.
I thought as afirst timer i would follow the newbies guide posted in the "best ROM" thread.
It all looked quite straight forward so i proceeded to the first step of unlocking.
My wizard is a G3 so i followed the G3 guide and flashed with the "button ROM" and all seemed fine and the phone booted up fine etc, i then thought id reboot again (for some reason, just to double check all was well) and upon boot up the screen was scrambled i could see colours etc in the scrambled mess as if it was the blue windows splash screen ans then i got the Ping the phone usually makes of first boot that prompts fot the screeen alignment wizard, but the screen was still scrambled.
It looks kinda like when a laptop screen cable is broken so i thought maybe my cable has come loose from the mainboard, i decided to open the phone up and check,
No the cable was fine, i chcked all the connectors inside and put the phone back together.
Booted up, Still scrambled
I then decided to cut my losses and reflash to the standard Imate K-jam Rom, so i went and downloaded that from imates website and reflashed.
booted up, still scrambled
Have i somehow bricked my phone?
Has someone come accross this before, and got any idea of a soloution?
It seems to me like there is something wrong with the screen but why would i go wrong when flashing a ROM ?
Any help would be much appreciated.
Many thanks
DigitalMetal
i think k-jam is g4 atleast mine is g4. this is only the hint that u might hav flashed wrong rom.
mine is G3 as it doesnt have the trailing numbers after the spl it just says 216 not 216.00.00 ...etc ....etc so i think im correct in saying mine is a G3 and i flashed with a G3 ROM.
And when i flashed the Button ROM it was OK untill i restarted because i saw the splash screen and the screen alignment wizard.
Once the screen went bad i reflashed it with the genuine Imate Kjam rom and its still bad.

Kaiser dead from water

So a couple years ago I had a Kaiser (AT&T Tilt version) go for a swim in fresh water, I was pretty quick about taking the battery out and then I let it dry for 3 days before trying to turn it back on. Now a few years later I have since replaced that Kaiser with a new Kaiser and then an amazing HD2 that we all know and love. I have been tinkering around with the water damaged kaiser for a while now trying to resurrect it and here is my question, I know of all these tricks people say work ( rice, Isopropal alcohol, ect) but this is besides the fact that the phone hasn't been attempted to turn on in over a year, I'm sure it's dry.
I can successfully boot into HSPL any day of the week, and I also successfully flashed the stock AT&T WWE rom back to the phone, but it still gets stuck on the first screen (The white AT&T branded screen) so the real question is, does anyone have any more ideas to try to get the phone to boot, Is it possible some specific component or micro-controller is fried? I would say it's not totally dead since I can get into the HSPL boot loader and flash the Stock rom, however I tried a few WP 6.1 and 6.5 roms and they get an error code when I attempt to flash. I beleive it was error code 274?
Any help or suggestions would be hreatly appreciated, thanks.
chamele0n said:
So a couple years ago I had a Kaiser (AT&T Tilt version) go for a swim in fresh water, I was pretty quick about taking the battery out and then I let it dry for 3 days before trying to turn it back on. Now a few years later I have since replaced that Kaiser with a new Kaiser and then an amazing HD2 that we all know and love. I have been tinkering around with the water damaged kaiser for a while now trying to resurrect it and here is my question, I know of all these tricks people say work ( rice, Isopropal alcohol, ect) but this is besides the fact that the phone hasn't been attempted to turn on in over a year, I'm sure it's dry.
I can successfully boot into HSPL any day of the week, and I also successfully flashed the stock AT&T WWE rom back to the phone, but it still gets stuck on the first screen (The white AT&T branded screen) so the real question is, does anyone have any more ideas to try to get the phone to boot, Is it possible some specific component or micro-controller is fried? I would say it's not totally dead since I can get into the HSPL boot loader and flash the Stock rom, however I tried a few WP 6.1 and 6.5 roms and they get an error code when I attempt to flash. I beleive it was error code 274?
Any help or suggestions would be greatly appreciated, thanks.
Click to expand...
Click to collapse
Well, I'm no expert because I got a TyTn but what I can say is that you can check out the wiki fir unbricking options. And also remember that some moisture can still get trapped even after a year. Maybe leaving it under the sun will help evaporate all the water? Anyway, good luck fixing it!
My uncle had one, but he dropped it and the metal but broke; so it became a hazard because of the sharpness. Then he gave it to the insurance company and got an iPhone!

Categories

Resources