Related
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!!
Hi there,
My currently installed Rom was RUU-Prophet-G4-AKU2.2-2.20-2.47.21-Jester-r1.exe. (thank you jester for you good job)
Nevertheless, this ROM is in English and I wanted to downgrade to a French One before the selling of my device.
I have tried to install the downgrade kit detailed in this topic : http://forum.xda-developers.com/showthread.php?t=267344
The first step went OK but while trying to make the secnd step, my qtek is blocked at the boot splash screen showing the Jesterz picture and red information about the SPL and so on on the upper left corner... without starting... The USB connexion is not detected so I can't do anything... While trying to install any ROM, the USB connection is not detected ang I get an error message...
Did I kill my phone ?
Please help ! Tell me that it's not dead....
Don't worry, its nowhere close to being dead. If you have superCid, then use the SD card image to restore in bootloader mode. However, if the Cid is locked, then you would need a utility that can unlock Cid without Activesync mode (coz in your case, you would not be able to get an Activesync connection). imei-check.co.uk has a utility ($38 i guess) that unlocks Cid in bootloader.--- else show it to a professional. (in my country, I would have to shell out around $20 to get such a problem fixed at a mobile repair shop)
illanz said:
... The USB connexion is not detected so I can't do anything... While trying to install any ROM, the USB connection is not detected ang I get an error message...
Did I kill my phone ?
Please help ! Tell me that it's not dead....
Click to expand...
Click to collapse
Just take out the battery for about 10 minutes and re-insert. If it does not re-start, do a soft resert with the stylus and hopefully you should be fine
Hy,please help!
after downgrade, it doesnt work anymore.... i mean... i cant start the mobile!
after the downgrade i disable the USB data cable and now the mobile is dead... it doesnt starts from the ON/OFF Button and even if i connect the USB cable it makes nothing! No Led on... nothing! absolutly DEAD!!!
I have tried to put off the battery all night long with no result.. but I have achieved to reach the bootloader mode by pressing the camera button while soft reseting and keeping the camera button pushed...
OMG, I have been so scared ! ! !
Try this in order to reach the bootloader:
Hold down the camera button and reset the device. (Boot Loader Mode is: Press Camara + Soft Reset, then release soft reset and KEEP PRESSING camara button till appear the Boot Loader.)
it doesnt work
I seem to have a simular problem. this is my post in another topic. It seems to fit better here.
This is what I tired so far:....
I used the RUU_Prophet_2151327_21513121_021921_DOP_ASIA_WWE_S hip-NoVendorID and it often hangs and was slow with Push Email over GPRS.
I tried to find a way to downgrade but hadn't had time sofar. When I logged on XDA Developers Site I saw there was a new Image.
So I thought Great I dont need to find how to downgrade.
I don't know what G4 and G3 is so as everybody let's try the higest best one.
I uploaded the RUU-Prophet-G4-AKU3.3-Jester-b1
Wrong...
Now as previously stated I get to the multicolor screen with IPL 2.09 and the SPL 2.20..0001 on the screen and that's it.
I can get to the bootloader and load the same image again and get the same result.
I can load another image on and it loads to 80 Percent and says error [326] Invalid Command This NBF cannot be used with your PDA Phone. Please check your NBF file.
If I try an older Version it tells me upgrad only
And when I try to upload the G3 version it tells me error[300] invalid upgrade tool. This upgrade utility canot be used for your PDA Phone. Please get newer Upgrade utility.
Trying to use the nf.nbf or the G3 with the ROMUpdateUtility_NoID of the G4 doesn't work either.
If I would like to do the downgrade tool I need a Active Sync connection which I don't have.
I have no more thoughts. Please Help.
If you would have just read the forums better you would have known if your device is a G3 or a G4. (read this!).
Now it appears you have tried both for an update. Which may possibly have bricked your phone.
But... first things first. Can you get into the bootloader? (read wiki HERE on how to do that).
If you can still get into the bootloader then there is still a possibility for updating.
Try upgrading with the latest Qtek rom (note: this is an official rom, this one works for both G3 and G4! And since it's the latest you should be able to upgrade to this one).
Instructions quoted from another post of me:
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 here ) to upgrade.
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 is prophet and in that one 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
This should give you a good enough idea of what to do. This should work (new rom combined with no NoID updater).
However, if it's impossible to get yourself into the bootloader your options of upgrading your device are getting smaller.
Downgrading of a complete rom is only possible on a CID unlocked G3 (when it's CID unlocked you would know! because you would have done that yourself) and not on a G4 device.
Flasing a G3 device with a G4 rom or G4 device with a G3 rom might possibly turn your phone into a brick. This can easily be avoided by reading the forums properly and know what you are doing.
If anything (even if it's a small thing) is not completely clear to you about upgrading/downgrading your device I'd recommend not doing so.
edit: oh yeah... if you have a G4 device (which you should know by now) you cannot downgrade from this rom (well, only via a payed online service). And when you have a G3 device you could try and CID unlock it (read wiki + forums) before you want to downgrade, or don't downgrade at all.
But whatever you do, don't try to downgrade it without doing any of those things because you'll get into trouble. (to put it down bluntly)
illanz said:
I have tried to put off the battery all night long with no result.. but I have achieved to reach the bootloader mode by pressing the camera button while soft reseting and keeping the camera button pushed...
OMG, I have been so scared ! ! !
Click to expand...
Click to collapse
If you have reached the bootloader screen, just run my installer (or any official ROM) to get your phone working again.
My Prophet Died
I need help, to restore my Prophet, i upgrade wrong rom, i need will try the SD Backup, where can i see this process ?
Sorry my Inglish is too bad.
I've merged a couple of threads under this one, as they are all about the same problem (mostly)
Opening a new thread for the same problem isnt very useful
Hi RaptorRVL
Thank you very much for your patience in resuming all this for me.
I do try to read the forum but it isn't like a manual where you find the procedure stepby step. Like the G3 and G4 version I have newer come across until now. Sorry.
I tried the image you metioned and I have the result that at 80% it tells me error [326] Invalid Command This NBF cannot be used with your PDA Phone. Please check your NBF file
Any more thoughts?
As you seem to be an expert Can you let me know more about goldcard solution.
Cheers
Mick
From a readme I once found inside an update:
* ERROR [320~328] : INVALID COMMAND
These errors seldom occur. However, if one of these errors occur, it could not be recovered and the device had to be sent back to the customer service center. In this case, you have to flash a new ROM code.
Click to expand...
Click to collapse
Doesn't sound too good really. Maybe someone else here on the forums know what to do with this error :/
You did use the ROMUpdateUtility_NoID.exe and not the normal updater right? Can remember someone getting a similar error when using the wrong updater, but I'm not sure about that though...
edit: try doing a search on the prophet forums for "INVALID COMMAND" maybe there is a helpful post in there somewhere...
THANKS!! I was worried b/c i had the same problem today. I've been looking for so many threads abt this problem. Thanks for ur help guys!
same problem
so i have the same problem. I want to downgrade and it break at 95% invalid file. But now XDA is still alive. I can`t go into the bootloader but i tried this file: RUU_Prophet_220734_2207114_024721_NVID.exe
and now my Prophet is still running again. Hope i can help you. Good luck.
peter paul
P.S. sorry for my english, but its good to learn it again
Have a problem with unlocking my new G3 device (never had problems with the old one until it died ). When trying to downgrade/unlockcid using downgrade_and_unlockcid_v01 utility after executing dowgrade.bat I get following message: "could not update itsutils.dll to the current version, may be it is in use?"
tried to solve the problem by running SDA_ApplicationUnlock before trying to downgrade but still nothing. Dear Guru, please tell me, where the problem might be?
ok, found a kinda solution, will download pdamobiz app for aku2 , but don't know if it would work.
___________
nah, did not work any suggestions?
Still need one for G4.......anything ?
Hi,
Was changing the ROM on my Kaiser, using JUMPspl as I had got the white screen using Hardspl. During the upgrade got an error at about 18%, went through the recovery procedure only to get back to the Bootloader screen with the screen saying
SPL-1.93.0000
I think it should say something different here!
At the moment can only get the the tri-colour bootloader screen with usb at the bottom.
Please any help would be much appreaciated.
Thanks
If you are at the tri-color bootloader screen, reflash a ROM.
that's where the process starts at anyhow,the bootscreen.
But doesn't the SPL have to be either Hardspl or jumpSPL.
I have tried to do the rom update again but sticks on 0% and gives error 262
Alemaker said:
If you are at the tri-color bootloader screen, reflash a ROM.
that's where the process starts at anyhow,the bootscreen.
Click to expand...
Click to collapse
Not advisable if he has the default SPL still though which by the number appearing at the tri col screen it appears to be the case.
Try doing a hard reset and see if it boots into the original ROM then at least you will find out if it is bricked or not, however, i'm not sure it will work based on the fact you got part way through in the first place.
Hold down the keys directly next to the Send and End (green and Red) Hold in the stylus and keep them all held untill you get a screen telling you to press the green (send) key.
Tried the hard reset, takes me back into the bootloader. Any other ideas?
Hmm... ok then.... you are pretty much looking at a very expensive paperweight at this moment in time then.
Look at this thread...it "may" (i'm not promising anything but it may point you in the right direction) help you out. Let us know how it goes.
http://forum.xda-developers.com/showthread.php?t=361612&highlight=bricked
cmcmill01 said:
Hi,
Was changing the ROM on my Kaiser, using JUMPspl as I had got the white screen using Hardspl. During the upgrade got an error at about 18%, went through the recovery procedure only to get back to the Bootloader screen with the screen saying
SPL-1.93.0000
I think it should say something different here!
At the moment can only get the the tri-colour bootloader screen with usb at the bottom.
Please any help would be much appreaciated.
Thanks
Click to expand...
Click to collapse
Hate to joint the parade, but the exact same thing happened here - 18% now stuck at 1.93.0000
For anyone else reading this BEFORE flashing a new ROM please read, read and read again EVERYTHING related to flashing on this site, wikis and wherever else you can get info.
Another idea for you. Search around here for how to flash from an SD card that may solve the issue out for you. As previously noted though....READ READ READ and be 110% certain you understand what you are doing before you do anything.
http://forum.xda-developers.com/showthread.php?t=276963&highlight=stuck+bootloader
details some info for a Wizard, should it be the same for a Kaiser?
Will Mtty get me any further?
MTTY will at least give you a USB connection to the device it is worth a shot given your current situation.
There is hope!
I did a clean reboot of my PC and disabled my antivirus (avast) and was able to sucessfully reflash the new 1.62 rom (released from ATT site today).
Thanks will try the new 1.62 rom.
What commands can you use with MTTY?
tried the At&t rom gives me an error on the vendor id. Will try a HTC rom
I have tried multiple roms and they all give me the same error Error 294:Invalid Vender ID
Any ideas
Am starting to get worried because if the misses finds out that I have bricked the new phone, I am up to my neck i it.
If you are stuck in boot loader & would like some help via MSN Messenger, please PM me or look for me on MSM messenger at [email protected]. I will be available to help later this evening or tomorrow morning.
I have most of the files to fix these issues & can use MSN fileshare folders to help you.
Good chance that you can be up again in a matter of minutes
cmcmill01 said:
I have tried multiple roms and they all give me the same error Error 294:Invalid Vender ID
Any ideas
Am starting to get worried because if the misses finds out that I have bricked the new phone, I am up to my neck i it.
Click to expand...
Click to collapse
Invalid Vendor I.D. is cuz it's locked.
Had the exact issue myself and found a ATT ROM that will boot. It saved me bigtime, so I saved it. It's in one of the posts on one of the threads but I have the actual ROM, it'll overide that lock.- PM me if ya need it.
Got the same solution, Holy S**t about to have a heart attack. Tried nearly ever ROM out there, it was the Asia one that got me going.
Lesson learned: make sure you Hardspl after jumpspl.
Thanks for all the help folks
Glad ya got it fixed. One quick question?
Is your original ROM ATT or HTC ?
It is a HTC ROM. Done My Hardspl and got Sleuth v3.0 on it already
Happy days
Dear All,
Please kindly help me out of this.
Yesterday, My phone started to develop the "NO GSM: symptoms. At first, the phone ioccasionally turned off after it couldn't connect to the 3G network. Today, after reading nearly all the post concerning this "No GSM" symptoms, I applied the Mtty tools to desparately try to bring my beloved Uni back to life.
I applied that mtty.. I tried to upgrade it by using the shipped rom.. yet it said country ID error.. I reverted to use the MaUpgradeUt_noID.exe but the radio rom upgrade failed....
Are there any other solutions I can rescue my uni? I read it here http://forum.xda-developers.com/showthread.php?t=350349 that Radio Rom upgrade may be done through a SD card but the ftp link is dead and I can't get any files from there.
I miss my Uni so so much that I think I would buy another one if there's no way to save it... Please kindly help. all my gratitude.
Hi,
Please consider a new battery.
As strange as it may sound, one of my MDA Pro's had similar symptoms with battery at 70%. Replacing the battery with a new one fixed it right away.
The symptoms were:
- less network signal
- random turning off of radio
- could not access phone settings
- radio crash when trying GPRS connection
Also, on my other MDA Pro, I had problems like this, but they were caused by radio ROM 1.18. I changed to 1.15 and everything is fine since.
It seems that aging batteries are a major problem for weird issues. Just buy a new one at ebay and dont start flashing as a fool, cause you can risk a brick.
Cheers,
vma
My battery is actually new... just bought it 2 weeks ago.. and I tried the phone with both my new and old batt. still no luck -_-
I can't flash any radio rom now... is my Uni certified dead?
Any help would be great.. thanks
Try charging the battery first in another universal if possible, if battery is ok, put it in and try again, read Wiki and check if you can go to boot loader mode, check whether pc recognising the Uni once on etc.,
Read everything and the computer recognised my Uni ... tried MTTY tools to reset all the DOC partition in my Uni yet no way to reflash my radio rom again
I think as long as PC is recognising, dont consider it as DEAD. Its very much alive and keep hopes.
as I read through this forum, Radio ROM flashing is the most risky thing and often takes longer.
If you are not already considering, try only flashing radio rom and do not club with extrom etc, try redownloading the ROM or try a different version from a different link, unless you are particular about the one you are trying.
Always use the original USB cable supplied with the Uni.
Enter BootLoader mode by pressing and holding the power button and backlight button whilst performing a reset with the stylus. Connect Unit to PC to the USB port directly and not through a USB HUB.
Start flash again..
All the best
ronaldphl said:
Dear All,
Please kindly help me out of this.
Yesterday, My phone started to develop the "NO GSM: symptoms. At first, the phone ioccasionally turned off after it couldn't connect to the 3G network. Today, after reading nearly all the post concerning this "No GSM" symptoms, I applied the Mtty tools to desparately try to bring my beloved Uni back to life.
I applied that mtty.. I tried to upgrade it by using the shipped rom.. yet it said country ID error.. I reverted to use the MaUpgradeUt_noID.exe but the radio rom upgrade failed....
Are there any other solutions I can rescue my uni? I read it here http://forum.xda-developers.com/showthread.php?t=350349 that Radio Rom upgrade may be done through a SD card but the ftp link is dead and I can't get any files from there.
I miss my Uni so so much that I think I would buy another one if there's no way to save it... Please kindly help. all my gratitude.
Click to expand...
Click to collapse
From the problem behavior it seems your device got GSM locked, I'm afraid it's permanent. But at least try ...
1. Remove the SIM card
2. Must upgrade the bootloaded to 1.01 if it's a G3 (and not upgraded already).
3. Run the Buzz's CID unlocker tool and flash the radio (version 0.00) provided with the tool.
4. Do the HR and check the status