Database Info

2 TOTALLY dead JAMs- bigstorage and 1.12WWE ROM

I think i must have the worst luck or else I'm doing something stupidily wrong...
I fried my device when trying to apply the bigstorage hack on ROM version 1.12WWE.
A week later my mate asked me to do the same on his JAM- same thing again- device just totally fried!
I had successfully applied the bigstorage hack on both the above devices with the original T-Mobile Rom (1.01 or something)- this went without a single hitch.
The method I used was using the 'Bigstorage software'
Do i need overwite the first 416 bytes even if im using my own rom and not a downloaded one?
What am I doing wrong?? This has really got me frustrated now.
Any insight as to what I could be doing wrong would be very much appreciated.
Thanks

Quite a few people have reported to get a totally "dead" magician using the "Make BigStorage" method. The good news is that when they return the machine to the service center, it can be fixed.
This is different from the "stuck at bootloader or splash screen" cases, which can be easily recovered by the user without the need to return it for repair.
It is much more safe to use the "edit two bytes at two locations" method to get BigStorage.

Talents- I was guessing that it would be you to reply- much appreciated for that . I was/am 99.9% confident that the service centre would get it working again. My frustrastion comes from figuring out what I am doing wrong. I am stumbled even with professional background (IT/PCs!).
So is it just my worst luck- or could I have done something wrong, unknowningly?
As much I want the latest ROM and bigstorage- i dont think i can run that risk again- even with the 'two bytes' method.
P.S. I was using a 128MB SD to perform hack- surely this is enough?

I recently did the bigrom hack, and had the same problem. after the device took the hacked rom, i soft reset, and it stayed on the boot screen for 25 mins.
I re-flashed the original non edited dumped rom to the device and it worked, copied the hacked rom to the card, and tried to flash again....and it worked.
My heart stopped when i just hung on the boot logo originaly.
Imp

Impossible,
From what I can gather the problem that you had is (was) not fatal... when I performed the bigstorage hack the device was TRUELY dead- nothing showing on the screen whatsoever... as Talents has also mentioned.
Anyway I had it sent off to the repair centre and have a brand new JAM back. Performed the 'two bytes' bigstorage method (thanks to Talents) and all is running well

Glad you didnt loose will in the upgrade.
Where abouts did you have to send your dead handset to, how long did it take to get a replacement.
Imp

In the end performing the upgrade was purely for the fact of doing it for the sake of it and frustration.
My original JAM was only about 2 and bit months old so it was still under warranty- returned to the place of purchase- T-mobile centre.
My one took 8 working days for me to get back but my mate's one took only 3 days.

Hello,
I experience same trouble as u all, still wasn't able to get the big storage to work. Let me tell u what I already tried:
Had a good working Dutch Orange M500 device with 1.06 original ROM. Udated it to 1.11 WWE I-mate ROM, no prob. Opend the storagespace with the mksBigStorage method, no problem,had 27MB free.
Updated to latest 1.12 original new Orange ROM via USB-cable method, no problem.
Now I want to open bigstorage on this original Orange 1.12 ROM, and no matter what I try, I cant get it to work.
-Tried yesterday all day, got a backup from CLEAN Orange 1.12 ROM, edited it with mksbigstorage program, no success at all. Got through all the steps, it goes to 100 %, checksum fale, upgrade fail message. Now it is stuck in bootloader mode.
-Edited original clean ROM with "edit two bytes at two locations" method, got through all the steps, it goes to 100 %, checksum fale, upgrade fail message. Again stuck in bootloader mode. Funny thing was that when I edited the rom, I only found 1 location in the ROM to edit, not 2. Went through it with the following query in the Bytes field: 02 00 00 80 00 20.
Maybe this is my mistake? Anyhow:
- got an external reader today, after trying all day yesterday with internal reader. Doesn't seem to make any difference, no matter what method, still no big storage. Did the whole process again, both metods. No luck until now. WHAT AM I DOING WRONG???

Yoho, I did it! It turns out that my 128 MB SD-card is giving me trouble, when I used the 512 card it finally worked!!

MDA_C hangs at 99% ce rom upgrade and splash screen

Hi all,
Have purchased a German MDA_C and flashed it to the latest dutch WWE rom (1.13). I use the NOID updater and get an error message at 99% of the update.
After this my MDA hangs at the splash screen (but showing updated rom and radio versions).
Doing a lot of soft and hard resets I managed to get by the splash screen 1 time...
Tried a lot of different rom versions but each time I get the same problem
I've read that the SPLASH screen problem is more or less common but I wasn't able to find a solution on the forum.
Now I made one stupid mistake... I did not backup the original rom...
Any suggestions how to get up and running?
Thanks in advance...
BuDDaH

The very first boot takes a long time, 15 mins for some! If you're not waiting for around 15 mins ....

Thanks for this valuable information kta.
This time I waited 1 hour after upgrading just to be sure.
same result. flashing stops at 99% of the CE Rom.
Hard reset shows splash screen with version numbers (radio 1.13 rom 1.13 wwe) and then just hangs.

From bad to worse
So I had a MDA_C that did not boot further than the splash screen.
Updated using the MaUpgradeUt_noID.exe. Thought I'd give the SD way a try since I already tried about 6 different roms all with the same result.
First I made a backup to SD card of what was in my MDA using romupdate.exe
extracted the file to my HD.
After extracting (and securing the device ID) I tried rebooting my MDA.
Now things got worse!!! instead of the splashscreen I now have the BLACK SCREEN......
Have tried resetting and hard resetting dozens of times (more like a thousand times) and only occasionaly the splash screen comes up. :roll:
But over the last couple of days I only managed to get the bootloader 1 time (and at that time there was no SD card inside) :shock:
this is behaviour I haven't read about on the forum.
Guess I will have to get it serviced.
Is there anyone on the board that has an address in the Netherlands that can flash or repair my mda? Not sure T-Mobile NL services German devices...
Thanks!

Not dead yet?
Here's some more info.
My 'almost dead' Magician is showing signs of life.
I had the BLACK SCREEN.... (first couple of lines of pixels were not black)
After thousands of hard and soft resets (soft resets seemed to have the best results) I managed to get into the bootloader!! Flashed with an older rom and at least I'm getting the splash screen again. (but still getting an error at 99% of update of the CE rom).
I'm updating using the exe in bootloader mode btw....
Since there's always an error at 99% when I use the exe method and the device is not booting I thought about giving the SD method a shot.
My device didn's show the SD option but fortunately tadzio explained about the MBR (didn't even know a SD card had one!!! :lol:
http://forum.xda-developers.com/viewtopic.php?t=32849
When I decode a nbf file using nbfdec.exe and flashing afterwards I get a message that my ROM is to small.
Size is same as nbf file.
How do I correctly decode a nbf file?
Thanks for the help.
BuDDaH

Don't use a nbf, get a dumped or bs rom from the ftp & follow instructions with copying bytes etc.
M

Ok OLTP I'll skip the nbf decoding route.
Think one of the problems is the way the newer roms are encoded.....
Saw you're using a 1.13 bigstorage rom?
That one is not on the ftp is it?
Modified your own rom image?

Hi BuDDaH,
I downloaded at the Dutch TMO site the shipped-rom, unzipped the exe file & decoded the nk.nbf nbfdec. In this nk.nb1 I altered the usual BS bit patterns and re-encoded the nk.nb1, again with nbfdec, to the nk.nbf. After that it was just running, the extracted, upgrade program & it worked like the usual shipped-rom upgrade. you might have to use the maupgrade_noid version, sometimes twice.
This method is better described in the thread about upgrading to radio 1.13 which you can add along the road as well.
So yes I made it myself, not so fond of using other people's rom unless I have to. Please don't let anyone be offended by this, cause a replaced bit can cause serious harm, like I encountered myself, with my own corrupted rom-dump.
Good luck, M

Just wanted to update you all on the latest status.
I managed to flash a german rom (as I've got a German device) although I always get an error message at 99%.....
Fist it just stuck on the splash screen but this somehow deteriorated. Now I get a black screen covering about 5/6th of the screen. the first 1/6th shows a part of the splash screen. No backlight and it hangs.
No more bootloader so I need to have it serviced (anybody knows what the techies do with such a device?)....
Now the question remains where.
T-Mobile NL refuses to service it since the IMEI is unknown to their system
T-mobile Germany doesn't have a service center but only takes repairs through a T-Punkt shop..
Any ideas?
Thanks,
BuDDaH

Latest update...
I sent it in for repair and it turns out that the ROM is damaged and the phone needs a mainboard replacement..... which costs about the same as a new unit...
Anyone got a spare one laying around for me?
So much for my Magician!
Cheers,
BuDDaH....

Sorry to hear...did you try another SD card?

Yep I did; but unfotunately the situation deteriorated and I'm completely unable to get into bootloader mode.....
Well.. :idea: maybe I must see this as a great opportunity to get wild with a set of scewdrivers

Hey BuddaH,
There enough people interested in the parts here at the forum, so there's a tiny brightside on your adventure :-(, man i do feel sorry for you.
Regards, M

Yup, i need some parts also

BuDDaH said:
Yep I did; but unfotunately the situation deteriorated and I'm completely unable to get into bootloader mode.....
Well.. :idea: maybe I must see this as a great opportunity to get wild with a set of scewdrivers
Click to expand...
Click to collapse
You probably ran the battery down. I don't think it charges unless the ROM is working. That is why it is highly recommended that you start with a full charge before commencing a ROM update.

Hi Stevedebbi,
Even in my situation the it still seemed possible to charge the battery (at least the red light went out and the battery got hot).
Sent my device to apexlaptops.co.uk cause they claimed they reflash...
Got the reply back that they couldn't get it too bootloader mode and were unable to repair. (guess they could not do some JTAG debugging).
I may be able to buy a working device that's damaged on the outside....

Please help! My S200 has died

I installed the latest LSVW ROM a few weeks ago and I was very happy with it.
Today I got a crash of my S200 (run out of memory). My S200 gets stuck in a totally white screen after the QTEK logo has been disappeared during a soft reset. So I have to do a hard reset. However, after the hard reset my S200 get stuck in the red-green-blue colored screen (bootloader) and will not go any further.
Can somebody help me bring my S200 back to life?
I read some articles about flashing from the bootloader, but all the ROM updates cannot find my S200. They really need a ActiveSync connection and I am not able to make one....
Can somebody please help me?

ehm, when you can get into bootloader you should be able to plugin your device and do an update via usb.
However, you should do this from an official rom. Not a rom based on PDA mobiz or something, that needs a guest activesync connection afaik.
To quote myself (for instructions):
erm... well you could try the 2.20 qtek rom which seems to be working well for quite some people (found here).
Although you have to make sure you read that thread good and use the ROMUpdateUtility_NoID.exe (found on ftp) to upgrade (or you download RUU-Prophet-G4-AKU2.2-2.20-2.47.21-Jester-r1.exe and take the ROMUpdateUtility_NoID.exe from that using WinRAR, but it's wasting bandwidth a bit ).
Update instructions:
1: With the qtek 2.20 rom you need to extract the zip and the exe file in the zip with WinRAR.
2: Then there is one folder called 'OutputFile' and a folder called 'RUU_TOOLS'.
Inside the RUU_TOOLS there are some other folder (prophet -> WWE), when you go through them and in the WWE folder you see a bunch of files (readme.doc, enterbootloader.exe etc etc).
You need to copy ROMUpdateUtility_NoID.exe to the WWE folder with all the files. And you also need to copy the 'nk.nbf' file to the WWE folder (from the 'OutputFile' folder).
3: And then you need to put your phone in bootloader mode and run ROMUpdateUtility_NoID.exe to upgrade, which should work nicely then.
Click to expand...
Click to collapse
Hope this might help you out.
Very weird btw the device just crashed itself and now you are stuck in bootloader! Doesn't sound too good
Did you heavily overclocked it or something?

RaptorRVL tahnk you very much for your support, but it dis not solve my problem.
I tried it several times. I had a lot of 260 errors and at last I got a 320 error. So it seems that there is something terribly wrong with my device. I think I have to return it to QTEK.
I did not overclock my PDA, so that could not be the cause of this. I was just driving home using TomTom Navigator and the error message 'Out of memory' (error message from WM5 not form TTN) appeared on the screen with an OK option. I pressed the OK button (only thing I could do), the S200 soft resetted itself and got stuck in the totally white screen after the QTEK screen with the version numbers.

Sounds like faulty hardware indeed, perhaps bad memory or a bad motherboard. All the stuff is intergrated anyway, so they just throw the old internals away and get some new stuff in there for you.
Hope they fix it fast!

Phone dead after upgrading with Faria's rom

Hi!
Can anybody help me?
I was upgrading with faria's roms.
It all went ok until it reached 99%. after waiting for around 5 minute at that point, it sad that there was a communication error with the phone, and i need to do some recovery actions(remove from the usb, remove the batteries) It said that if i can see 3 bars, then everything is ok.I could see it, so i restarted the upgrade utility. But it did not want to do anything. It said to get a newer version of the upgrade utility. and my phone remained in that 3 color state, having 3 messages on it: IPL 2.16 then on the other corner saying RUU, then in a next row SPL 2.16
Can anybody help me to fix this phone?
Thank you in advance

ghola_2 said:
Hi!
Can anybody help me?
I was upgrading with faria's roms.
It all went ok until it reached 99%. after waiting for around 5 minute at that point, it sad that there was a communication error with the phone, and i need to do some recovery actions(remove from the usb, remove the batteries) It said that if i can see 3 bars, then everything is ok.I could see it, so i restarted the upgrade utility. But it did not want to do anything. It said to get a newer version of the upgrade utility. and my phone remained in that 3 color state, having 3 messages on it: IPL 2.16 then on the other corner saying RUU, then in a next row SPL 2.16
Can anybody help me to fix this phone?
Thank you in advance
Click to expand...
Click to collapse
Mine did something similar - PC Blue-screened about half way through the upgrade and left the Wizard at the Bootloader screen. I tried to re-run the upgrade and it said I needed a different version of the upgrade utility. I just re-installed the WM6 MB version and this worked fine, once it was back up and working I re-ran the Faria upgrade and it worked fine.
I think if you just copy the 'nk.nbf' file from Faria's ROM and use the upgrade utility from the MB version it will work.
HTH
Andy

ok.. here are the steps.. its very easy.. i had the samething..
your phone is probably CID locked.. so what you need to do is just download the original tmobile ROM.. and connect the phone and install the original ROM.. You didnt birck the phone because you get the bootloader screen.. which means, you can still save the phone..
anyway.. connect the phone via usb and install after you install the original wm5, download the shelltool from here and follow the instructions.. and install the ROM via shelltool.. Then you should be good to go with the new
wm6.
http://forum.xda-developers.com/showthread.php?t=271043&highlight=CID+unlock

DR.P'S UNLOCKING THREAD worked wonders for me.
BTW, after following Dr. P's instructions and loading Faria's ROM, my MDA took approx. 13-15 minutes at 99% before I hit the glorious 100%. Like a wise person before me said, patience is a virtue. I waited until the 5 minute mark, got up, used the restroom, grabbed an ice cold Pepsi and then waited some more.

Flashing Nightmare: Stuck at Boot Screen + 264/274 Errors!

Yup, first time disaster. I followed the guide here, installed the necessary Cert_SPCS.cab/EnableRapi.cab files, rebooted, and then started the Shelltool update...only to belatedly notice a notification screen on my 8125 asking if I wanted to run one of the programs.
I said yes, but even though the update completed, my 8125 is stuck at the boot screen.
Worse, I reset the 8125 into boot loader mode and tried to flash back, only to get a 300 error. I tried to use an updated RUU and ROM set, only to get 264 or 274 errors.
Any hope here, or did I just manage to brick my 8125?

Are you trying to flash an offical rom while in bootloader mode?

Yup. Tried to flash the official 8125 ROM from HTC. Tried to flash a number of different ROMs, actually - I always get a 264 or 274 "Communication" error, except for the official ROMs, which gave me a 300 error.
Not looking good here...

this has helped me with bad flashes
http://forum.xda-developers.com/showthread.php?t=298613

Been there, done that. In fact, that was the thread I first read. I've tried to flash to Wizard_love, but I get a 264 error.
From what I've read in the RUU Docs, a 264/274 error is rare, and fatal in this case. It's not looking good...
(On the bright side, the iPhone release has created a flood of used 8125's on eBay )

I did a little searching for you,
http://www.google.com/advanced_search?q=+site:http://forum.xda-developers.com&hl=en&lr=&as_qdr=all
I read some were how to flash a phone that has errors, I couldn't find that post. Maybe someone else here knows of that post You didn't mention is your phone G3 or G4 I did find this post, doesn't look good. I hope someone has a better answer for you, good luck.
http://forum.xda-developers.com/showthread.php?t=304456

Another post I found for you.
http://forum.xda-developers.com/showthread.php?t=294107

Thanks for the links, unfortunately it's still a no-joy situation here.
This is a G4 Cingular 8125 - sorry I forgot to mention that earlier.
ActiveSync was set to allow USB connections, and I've tried using the official RUU update utility from HTC for the Cingular 8125 with the 8125 in Bootloader (3 color) mode - I get an error 274.
I then tried the Wizard_Love version - error 264.
Next, the MB WM6 ROM - error 300.
Finally, in desperation I try the Shelltool app method again, even though I can't copy over the necessary bootloaders. It hangs up mid-flash, as expected.
Can't go forward, can't go back. Looks like I've got myself a brick...sigh...

upd: ahh, it is g4.....
so ignore whats below
it IS NOT brick ,trust me i had exactly same prob while testing cooked ROM - all yyou need is to download chinese rescue ROM, THEN flash it by its RUU, then RUU wLOVE, then flash ..anythin(g3)...and then flash IPLSPL, as it will be unequal, usually.
its unclear, why RUU cant do flash sometimes, but i believe, that you do not have brick( i had same situation 3 times = 14 flashes..;/ but machine is alive !)
of course, you may have same errors with chinese..if connecting, reconnecting etc is not working, then...use any rescue ROM closest to original, old hogs. check your firewall, and remember - SR device before EACH try - oterwise you surely will have 300 error - 1 try for each reset, no more.
chinese rescue ROM(you MUST flash wlove after that 1), or shelltool will lead you to...3bars.;/
http://pda.oleyek.com/ROM/Others/RUU_Prodigy_1070302_103_10703102_CMCC_CHS_Ship.exe
if its not working...maybe that 1..
http://rapidshare.com/files/29657481/RUU_TMobile_US_226102_22610105_022511_WWE_Ship_tmob_rom.exe
maybe other...
wizard love rescue ROM:
http://rapidshare.com/files/8651097/Wizard_Love_2.26.10.2_WWE_Novii_CF2.rar

Just a "happy ending" update:
Was just about to buy a new 8125 on eBay, when I gave it another try - hard reset the device twice in a row, then tried again to flash back to the original Cingular 8125 ROM -- it worked!
Then, in a fit of flashing madness, I went ahead and flashed one of Faria's latest WM6 sets -- and it worked as well!
So, not only don't I have brick, I actually got it upgraded. Whew...

pls help for flashing rom
pr0naLd said:
this has helped me with bad flashes
http://forum.xda-developers.com/showthread.php?t=298613
Click to expand...
Click to collapse
I have spent 24 hrs flashing my qtek 9100 sim free - i think it is the g4 as IPL IS 2.17 / SPL 2.17 NO ZEROES THOUGH . IT DOES SYNC BEYOND 99% AND THE HELP WINDOWS COMES OUT - IT GOES BACK TO THE BOOTLOADER SCREEN ( 3 - 4 LINES OF RED BLUE GREEN ). PLS HELP AS I AM DYING TO GET THE WM 6.0 ONTO MY WIZARD. thanks and appreciate.
[email protected]

BOWERS said:
I have spent 24 hrs flashing my qtek 9100 sim free - i think it is the g4 as IPL IS 2.17 / SPL 2.17 NO ZEROES THOUGH . IT DOES SYNC BEYOND 99% AND THE HELP WINDOWS COMES OUT - IT GOES BACK TO THE BOOTLOADER SCREEN ( 3 - 4 LINES OF RED BLUE GREEN ). PLS HELP AS I AM DYING TO GET THE WM 6.0 ONTO MY WIZARD. thanks and appreciate.
[email protected]
Click to expand...
Click to collapse
Kindly confirm its a G3 or G4 before flashing. This will help you out. http://forum.xda-developers.com/showthread.php?t=298613

wizard G4 boot ok but jump to B/L screen
its aliveeee its aliveeeeeeeeee