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 blocked with USB/SERIAL V1.00 on the screen

Hi everyone,
i'm about to buy a mda compact. The seller says that he tried to update rom and the mda now is blocked with a screen USB/SERIAL V1.00
If I upgrade the rom how is described in the other topic is ok?
I had to say to know if i buy this one or no
I wait fiducious in your answers :lol:

HELLO
This device is only in bootloader mode so you can reflash it without problem.
There is a lot of topics in this forum to perform that. :wink:

I had to do a "simply" rom upgrade or some different operation? :?:
I have find that post on this forum http://forum.xda-developers.com/viewtopic.php?t=14973&postdays=0&postorder=asc&start=0
i had to what is described on it?

Beware though. I had once screwed my MDA during an upgrade and all it did was start iself in the bootloader mode. For some reason, I couldnt re-flash any ROM onto the machine and had to took it back to t-mobile and they replaced a new unit for me.

Mmm... this is a bad new... anyone help?

i had this problem too, all i did was kept trying to different roms till one finally worked
i Downloaded all the rom from the FTP site
1 finally worked then after that, i updated to the 1.12 Imate rom...
Can not tell you which one worked, but i had to copy it to a Memory card to do it
Maybe if you try the Windows Installers, 1 might work

hi Herian..
1st of all,as the guys said,ur phone is in bootloader mode....it's not a problem,so don't be affraid :wink:
if u have'nt performed a flash before,am gonna try avoiding u flashing unless it's the last resort...
so bro,do the following:
1-remove the battery and leave ur PDA more than 2 hours without battery(u don't need 2 hours but am taking it to the limit),so that the backup battery will drain,all old data in RAM will be lost...put the battery again...and:if it restarts and enters OS,then congratulations,but if it doesn't,so u have to go to step 2.
2-reflash ur device:
-althought ur device is a Magician(at least this is what i think),all the procedures mentioned in my post(here's the link :wink: ) http://forum.xda-developers.com/viewtopic.php?t=25830&highlight= should work with no problem,the main difference wil be entering the bootloader mode,but since ur already in it :wink: ,it not a problem anymore,this is why you have to follow my instructions starting with step 2(the link,ok).
my advice for u will be to download the 1.12.00WWE ROM from the ftp,coz it's the last one,and good luck bro
tell us the news,or pm me anytime,it will be my pleasure to help u
RAGO :lol:

First of all: hello, I am new here
I just got a Magician (MDA compact) and tried to update it. But it failed and now it is in the bootloader mode. When I try a new update, it stops in step 1 after a few minutes. On the Magician you can see "upgrade radio stack, please wait".
Any ideas? I am a little bit confused, so much money and now it doesnt't work

hi COnker..
u must upgrade ur device with the right OS,ur case happens when u try to upgrade with a different OS(eg:upgrading a magician with a Himalaya ROM),but with the same operator(eg:i-mate jam upgraded with i-mate PDA ROM,u pass country ID error,and run ClearJmpCode.exe,and it ends by a dead jam in bootloader mode... :wink: ).
so my friend,what u have to do,is to go to ftp,and search for a ROM update made specifically for Magician(try 1.12.00WWE),then follow my instruction in the above topic.....
good luck
RAGO :lol:

Noway
I had tryed several times whit a lot of MaUpgrade(finded on the ftp site) but noway... The upgrade show me a window with the version of current rom and the version of the upgrade rom... but is empty! Then, if i click on upgrade, after a few minutes the mdac shut down and the program give me a 150 error... i don't know what i have to do...

I have read in some post here that is possible to do a backup of rom on sd card and to restore it.
If some good guy send me his backup files can i relive my mdac?

Hi,
I had the same problem but i have found a way without upgrade it.
1. pull out your battery.
2. put in your charger ( not usb )
3. put in your battery and then again pull out your battery and then again put in your battery.
4. now you will see the phone is starting up and if you have calibrate your screen and the rest the phone gonna install allot of stuff but when its installing everything pull out your battery and charger.
5. put in your battery and press the power button and congratulations your phone is working again.
sorry for my english i am from belgium xD

Sorry wrong post...
Not seen the second page

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....

HELP...VERY URGENT!!

Guys i did a very stupid thing this evening. I flashed my Imate Jam using the MAupgrade_No ID and the Greek Qtek firmware.
The flashing was good but now my Jam cant go pass the first screen and continuously reboots. It says something about illegal rom used....and reboots
Any solution to bring back to the former situation?
Please respond...i am really desperate

OK i figured out how. On my panic i couldn't even think.
God Bless the "search" button!!
But how could i get past this problem with the greek version qtek rom? It is locked and although it lets me upgrade (using the No-ID) on the first reboot after flashing it rebbots all the time.
Any ideas?
Thanks

Yep proteus3000uk,
Get yourself a shipped rom from your own provider. Put your magician into bootloader (camera & power & softreset until it reads serial or usb, there will be no backlight) uncheck usb in the connection settings from activesync on your PC & connect usb. Now it will read usb. Start the shipped rom program.
Or download a dumped or Big Storage rom & follow sd-card
flash method including the copy of your id from (first 420 bytes or so from your own romdump).
Or send it back and pray/beg for warrenty.
First two options are preferred off course. I 'repaired' mine with the first option, while I only had a black screen. So no OS or whatever on the rom.
Goodluck, M

Well i think that the Greek Qtek ROM is the only ROM worldwide that is edited from its programmers to run a phone version check, even after it lets you install it on your phone.
If it finds a phone version other than Qtek (in my case Imate Jam) the phone cant get past the initial splash screen and keeps rebooting for ever!

Then put it into bootloader and flash it wit an i-mate rom. Dumped, shipped or BIG storage and get rid of this Qtek ... rom.
Have you tried anything else than this qtek rom and what were the results?

oltp said:
Then put it into bootloader and flash it wit an i-mate rom. Dumped, shipped or BIG storage and get rid of this Qtek ... rom.
Have you tried anything else than this qtek rom and what were the results?
Click to expand...
Click to collapse
The original english tom (WWE) works just fine (as it should anyway). The thing is i was trying to install the qtek GREEK rom in order to have proper Greek on my phone.
Unfortunately the suckers have locked the greek qtek rom and they have compiled the actual lock into the rom itself.
Although the rom is installed just fine using the No_Id prog, at the first reboot the phone hungs and then reboots for ever!

Please correct me if I'm wrong, but I belief you can actually revert your magician back to the WWE rom and now you want help for unlocking of the Greek qtek rom.
This doesn't sound VERY URGENT to me, cause you can use your device only not in proper Greek, OK?
Can't help you with the unlocking though, maybe Buzz, Anansky or one of the other bright developers can.
Regards, M

oltp said:
Please correct me if I'm wrong, but I belief you can actually revert your magician back to the WWE rom and now you want help for unlocking of the Greek qtek rom.
This doesn't sound VERY URGENT to me, cause you can use your device only not in proper Greek, OK?
Can't help you with the unlocking though, maybe Buzz, Anansky or one of the other bright developers can.
Regards, M
Click to expand...
Click to collapse
If you check my second post you will see that i figured out how to revert back to my original ROM just fine.Som bo prob with that.Please READ before you post.
Thanks

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!