Related
Upgraded to Dop ROM form original Imate ROM. Now I can't get back. Upgrade is stuck at 95%..or I get Error [296] "Upgrade only This NBF cannot be used on your PDA Phone.. Please get newrer NBF file" . If flash Dop again it works, but refuses to flash any Imate. I guess I'm not the only one here having this problem...many have posetd this problem in different ways but now one gave a concrete answer.
Please let try to solve this.
Thanks
whehe, i'll ask someone who flashed mine back to a JAMin (thought he did it with a-wizard, hope he can help you out).
only the OS itself can be flashed back, you manually have to replace the extended ROM with the JAmin one (total commander, delete existing extended ROM, transfer files through IR to exdended ROM, hard reset to install the extended ROM, bla).
the GSM ROM and the bootloaded itself cannot be flashed to an older version.
yeah, i know, it sucks
Thanks tCC for replying with this goosd news. As for the extended ROM replacment, that's OK and can be easely done.
I realy appreciate your assistance in this and awaiting your next post.
Hi,
i'm the one who flashed the JAMin of tCC. In fact, it's not that difficult. Just follow these steps:
- execute enablerapi.cab on your device (search on the forum for this cab file)
- download awizard, extract
- copy the jamin os rom to awizard\rom\Jamin\
- start awizard.cmd, make sure your device is connected through activesync
- select option 'w' to write the os rom. just follow the instructions.
- the flashing can take up to 30 minutes so be patient
-if the flashing has finished hard reset your device
I've uploaded the jamin os and ext rom to
ftp.xda-developers.com/Uploads/Prophet/JaminAwizard/
tya
swartb said:
Hi,
i'm the one who flashed the JAMin of tCC. In fact, it's not that difficult. Just follow these steps:
- execute enablerapi.cab on your device (search on the forum for this cab file)
- download awizard, extract
- copy the jamin os rom to awizard\rom\Jamin\
- start awizard.cmd, make sure your device is connected through activesync
- select option 'w' to write the os rom. just follow the instructions.
- the flashing can take up to 30 minutes so be patient
-if the flashing has finished hard reset your device
I've uploaded the jamin os and ext rom to
ftp.xda-developers.com/Uploads/Prophet/JaminAwizard/
Click to expand...
Click to collapse
First let me thank you swartb for replying and trying to help by posting and uploading. And of course tCC who offerd to help in the first place.
Second, the link for the file you uploaded is not correct, and if you allow me i think this is the right one:
ftp://ftp.xda-developers.com/Uploads/Prophet/JaminAwizard/
And as far as enablerapi.cab here is the thread for it:
http://forum.xda-developers.com/viewtopic.php?t=50768&highlight=enablerapi+cab
Currently I'm downloading them and will let you know the result.
Thank you both again
swartb said:
Hi,
i'm the one who flashed the JAMin of tCC. In fact, it's not that difficult. Just follow these steps:
- execute enablerapi.cab on your device (search on the forum for this cab file)
- download awizard, extract
- copy the jamin os rom to awizard\rom\Jamin\
- start awizard.cmd, make sure your device is connected through activesync
- select option 'w' to write the os rom. just follow the instructions.
- the flashing can take up to 30 minutes so be patient
-if the flashing has finished hard reset your device
I've uploaded the jamin os and ext rom to
ftp.xda-developers.com/Uploads/Prophet/JaminAwizard/
Click to expand...
Click to collapse
can you cid unlock after installing an older rom?
still it's not working...
Dear swartb,
I tried it many times over and over and I still get this error after waiting of 14-15 min. every time.
CopyFileToTFFS(acidunlocked.bin:0, 0, 00010000)
ERROR: ITWriteDisk - An internal error occured.
Please see the attached images.
Any solution? Thanks
Hi,
I don't remember if I did see that error message. But if do a hard reset after this error the os rom is not updated?
And be sure just to update the OS rom and not the other roms (radio, spl & extended) because that doesn;t work.
I have just completed this aWizard process and now need to hard reset, but the program "clear storage"is not there anymore.
How can I hard reset the prophet without the software?
I will post the steps here when it is done :wink:
Could ran the aWizard with the OS rom in the aWizard folder (not \aWizard\rom\jamin\ ) but could not find way to hard reset the prophet, so reflased back to Dopod.
Hope another person continues from here :wink:
Re: still it's not working...
ahegazi said:
Dear swartb,
I tried it many times over and over and I still get this error after waiting of 14-15 min. every time.
CopyFileToTFFS(acidunlocked.bin:0, 0, 00010000)
ERROR: ITWriteDisk - An internal error occured.
Please see the attached images.
Any solution? Thanks
Click to expand...
Click to collapse
Its because the CID of your device is still locked. And certainly you have IPL/SPL 2.00. or higher. Swart did it with no problem because he has an unlocked CID.
You have to downgrade your IPL/SPL to 1.xx (I still dont know the correct method) and then unlock CID and then you can flash any ROM you want
Re: still it's not working...
ahegazi said:
Dear swartb,
I tried it many times over and over and I still get this error after waiting of 14-15 min. every time.
CopyFileToTFFS(acidunlocked.bin:0, 0, 00010000)
ERROR: ITWriteDisk - An internal error occured.
Please see the attached images.
Any solution? Thanks
Click to expand...
Click to collapse
Its because the CID of your device is still locked. And certainly you have IPL/SPL 2.00. or higher. Swart did it with no problem because he has an unlocked CID.
You have to downgrade your IPL/SPL to 1.xx (I still dont know the correct method) and then unlock CID and then you can flash any ROM you want
Thanks. Guess I can live with it for now. The Dpod rom is quite stable. No soft reset for 2 days and response looks like quicker than after soft-reset 8)
Re: still it's not working...
Tamagochi said:
ahegazi said:
Dear swartb,
I tried it many times over and over and I still get this error after waiting of 14-15 min. every time.
CopyFileToTFFS(acidunlocked.bin:0, 0, 00010000)
ERROR: ITWriteDisk - An internal error occured.
Please see the attached images.
Any solution? Thanks
Click to expand...
Click to collapse
Its because the CID of your device is still locked. And certainly you have IPL/SPL 2.00. or higher. Swart did it with no problem because he has an unlocked CID.
You have to downgrade your IPL/SPL to 1.xx (I still dont know the correct method) and then unlock CID and then you can flash any ROM you want
Click to expand...
Click to collapse
Thanks Tamagochi, Yes you are right, I have I IPL 1.00 and SPL 2.15.0000
The problem now is how to dowgrade form 2.xx to 1.xx. What are those methods that would help? I can try all of them and see if it works.
Finally it's resolved
I'm back to my imate ROM. Detailes in here:
http://forum.xda-developers.com/viewtopic.php?t=52244&start=25
Hi everybody,
I made up a new version of pof's USPL for ELFIN based on SPL 2.20.0000. You should be able to flash SPL in the third step now.
Why a new version? Because USPL v1 is only for ELF (64/128MB), but not for ELFIN (128/256MB). Flashing the old ELF SPL in step three on a new ELFIN used to brick your device.
EDIT:
You can find the working release in the following thread:
http://forum.xda-developers.com/showthread.php?p=1964159#post1964159
Thanks to everybody who was willing to test this!
Tempting, tempting.
I still haven't reproduced that weird blue screen i once had on my ELF.
But like i just wrote i got's me an ELF.
Good luck finding resourcefull Gamblers.
If there's no luck just start a Donation round for a Bricked Device Garantee
djvw said:
insane people
Click to expand...
Click to collapse
We have a lot of those in this forum. People trying to flash first and then start reading .
Thanks for trying to get USPL working for the XL users!
ummmmm i just used to use the old uspl v1 and exit after step 3 than flash my rom, if you guys are really keen on testing this my new elfin will be here today or on monday and i will try it with my old one just to piss of rogers
shael said:
ummmmm i just used to use the old uspl v1 and exit after step 3 than flash my rom, if you guys are really keen on testing this my new elfin will be here today or on monday and i will try it with my old one just to piss of rogers
Click to expand...
Click to collapse
This is the kind of brave people we need ;-) Please test it and tell us if it's working as soon as you can. Thank you in advance!
Uploaded new version, please redownload in first post.
Nobody has tested this yet?
I think that a Elfin dopod owner can test this without problems, because if don't work he can flash the complete (and signed) dopod rom from bootloader to restore the original SPL...
http://www.dopodasia.com/download/R...7.1B_4.1.13.51_03.07.90_BLUE_Ship_Reduced.exe
i have a elfin locked on bootloader screen....can change my spl with this??
what ??? the UPSL 1.0 is for Elf only and not Elfin ??? what i dont understand is what do you guys mean quit at step 3 ??? I flashed my Elfin with UPSL 1.0 with all steps for more than 6 times so far and nothing has happen so far ... my SPL is the 2.20.2000 one ...
@jamezco:
that´s wrong.
You flashed those roms containing the USPL (start.bat). They automaticly quit the 3rd step and go directly to the Rom Utility to flash the new ROM.
If you use POF´s USPL v1 and you don´t quit after step 3, the patched Bootloader will be flashed from your devices RAM to the ROM, and this wil brick your ELFin. If you have done this, your actual IPL or SPL would be 1.11.xxx...
Sorry: could someone explain me whether it is strictly needed to use the USPL unlock (the one are treated in this post) to flash the PDA?
I mean: the bootloader in the rom package is not able to do that?
we need some thing to unloack direct from boot loader and no need to active sync
as far as i know this is not possible, cause you can´t access bootloader files...in bootloader mode.
same on pc, you can´t delete or replace files, which are open/inuse by another program...
STRAFALCIONE said:
Sorry: could someone explain me whether it is strictly needed to use the USPL unlock (the one are treated in this post) to flash the PDA?
I mean: the bootloader in the rom package is not able to do that?
Click to expand...
Click to collapse
The Rom Packages u can get here don´t contain a bootloader...and even if they would, the bootloader or the rom would have to match your model ID for flashing it to your device....so yes, it´s stricktly needed to CID unlock to flash Custom ROMs or ROMs with other vendor IDs.
Could someone help me? The USPL is needed for the flashing of ROM, or is it enough the bootloader of the ROM?
Sorry, I missed the answer of the post before
My eyes are crossing after 12 hours in front of the pc
Anyone tested already???
Come on guys,
somebody who can get official Roms from his provider should give this a try...
Hi all, not that i think myself insane but i have tried the USPL for my Elfin 128/256 Touch a few days ago . I have followed the steps and the screen turned white as mentioned by the installer after that it booted up fine again.
Everything seems to be working fine!
However, i have not seen any change to the device..
mb286 said:
Hi all, not that i think myself insane but i have tried the USPL for my Elfin 128/256 Touch a few days ago . I have followed the steps and the screen turned white as mentioned by the installer after that it booted up fine again.
Everything seems to be working fine!
However, i have not seen any change to the device..
Click to expand...
Click to collapse
You don't see any change in the device.... but if USPL works you can flash ANY rom from bootloader directly executing RomUpdateUyility, you don`t need to boot windows, activesync and white screen (temporary SuperCID) to flash, try.....
Go to RUU directory and execute RomUpdateUtlity instead of RUN.bat and see if you can flash any rom without 3% (corrupted) error....
1. i downloaded duttys rom
2. extracted the rom to my pc
3. ran hard spl(completed the process)
4. phone restarted and nothing changed
please help
running hardspl only installs hardspl
run the RUU for dutty's rom
gula187 said:
1. i downloaded duttys rom
2. extracted the rom to my pc
3. ran hard spl(completed the process)
4. phone restarted and nothing changed
please help
Click to expand...
Click to collapse
What you are doing wrong is posting this question in the wrong thread! Also might try reading here at dutty's wiki.
XtreMe_G said:
running hardspl only installs hardspl
run the RUU for dutty's rom
Click to expand...
Click to collapse
i followed all the directions but its still the same rom
Just read. . . what it says in the sticky that says "How to Flash a rom". . .
gula187 said:
i followed all the directions but its still the same rom
Click to expand...
Click to collapse
It does not sound like you did follow all the directions. You state that in number 3 you ran hard spl. Great. That only gets your device ready for receiving new ROMs....it does NOT actully put a new ROM on your device. Step 4 should be running the Dutty Rom .exe also.
There are other steps too. The Wiki and Sticky (hey that rhymes ) have lots of info, and in many cases, step by step processes. Try reading them again and see what you missed.
Best of luck to you. Once you get the process down, you can repeat and repeat and repeat.
After updating with Tomals 8.2, I softreset but then all blank
I get to bootloader in try to flas it again but CE updating stop in 7% and then error....
I try all the methods using mtty and use the tool...but no luck, it still stop at 10% when updating CE
Pls anybody help!!!!!
kotabunga said:
After updating with Tomals 8.2, I softreset but then all blank
I get to bootloader in try to flas it again but CE updating stop in 7% and then error....
I try all the methods using mtty and use the tool...but no luck, it still stop at 10% when updating CE
Pls anybody help!!!!!
Click to expand...
Click to collapse
Have youtried with a previous Tomal ROM?
It worked for me in a similar problem
Good luck
kotabunga said:
After updating with Tomals 8.2, I softreset but then all blank
I get to bootloader in try to flas it again but CE updating stop in 7% and then error....
I try all the methods using mtty and use the tool...but no luck, it still stop at 10% when updating CE
Pls anybody help!!!!!
Click to expand...
Click to collapse
Have you removed your SIM and SD card, before trying to re-flash?
I did
I had removed SD card and SIM card, but it stil stuck at 10%. But if I updated the radio, it will finish 100%, whwn it comes to Ext Rom and CE update, it just finished at 10%. Did I Brick my uni ? anybody can help ?
kotabunga said:
After updating with Tomals 8.2, I softreset but then all blank
I get to bootloader in try to flas it again but CE updating stop in 7% and then error....
I try all the methods using mtty and use the tool...but no luck, it still stop at 10% when updating CE
Pls anybody help!!!!!
Click to expand...
Click to collapse
Pls anybody help me too! same problem stuck up and updating stops at 7%
giving ce rom update error?
Do a hard reset first and clear the phone by pressing 0 when promted
report back
kotabunga said:
I had removed SD card and SIM card, but it stil stuck at 10%. But if I updated the radio, it will finish 100%, whwn it comes to Ext Rom and CE update, it just finished at 10%. Did I Brick my uni ? anybody can help ?
Click to expand...
Click to collapse
Try to flash each part one at a time, not all of them at the same time.
Note that this ROM do not work with some extended rom and that blank page at first was the reason of that. Flash your extended rom with the tomal's own extended rom. You can find it...(oh no it has been removed, I will try to upload it for you). After flashing the extended rom try ato re-flash the rom and at last try to re-flash the radio (If you need it). Beware that flashing extended rom will erase your own extended rom so try to find one and decode its files to have your customization files back...
Hope it works
I have problem uploading file try to search for "Tomal_extrom" yourself and I will try to upload it...
Tried to flash Tomals ext ROM...but wont work too....I'm hopeless, maybe I should say goodbye to my uni,.....
same
ah i just got the tomal_extrom @ vidmes.com/xda
and now i am going to try with it will revert back
i did try the ext rom but the process failed.
can anybody help with mtty v1.16 as given in uni manual?
thnks for the help anyways buddys
digitalir said:
ah i just got the tomal_extrom @ vidmes.com/xda
and now i am going to try with it will revert back
i did try the ext rom but the process failed.
can anybody help with mtty v1.16 as given in uni manual?
thnks for the help anyways buddys
Click to expand...
Click to collapse
Seems your DOC is corrupted and unable to write.
Use mtty tool and re-format it, I'm pretty sure that everything will be OK then. But make sure that you have disabled AS before executing mtty!
pls give the action step by step, im very hopeless
tomal said:
Seems your DOC is corrupted and unable to write.
Use mtty tool and re-format it, I'm pretty sure that everything will be OK then. But make sure that you have disabled AS before executing mtty!
Click to expand...
Click to collapse
pls can u tell me the process to do it?
thnks
the wiki is your friend: http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader
Do not try to use copy paste in MTTY, type every command.
Before doing this ( steps 1 to 17) beware that you must download an original rom to get the windows mobile rom, the radio rom and the extended rom ( see step 13).
Last time I took Tomal v8.2, his extended rom and radio 1.15, put all 3 in the RUU folder and runned the update utility. It will take arround 20 minutos to flash the 3 files. thx to TehPenguin you can get these files here: http://vidmes.com/xda/Uni/ROMs/Tomal/ and here: http://vidmes.com/xda/Uni/Radios/
Be advised that I've not read the other posts on the thread, so I don't know if you should try this process or not.
Cheers
ultravox said:
the wiki is your friend: http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader
Do not try to use copy paste in MTTY, type every command.
Before doing this ( steps 1 to 17) beware that you must download an original rom to get the windows mobile rom, the radio rom and the extended rom ( see step 13).
Last time I took Tomal v8.2, his extended rom and radio 1.15, put all 3 in the RUU folder and runned the update utility. It will take arround 20 minutos to flash the 3 files. thx to TehPenguin you can get these files here: http://vidmes.com/xda/Uni/ROMs/Tomal/ and here: http://vidmes.com/xda/Uni/Radios/
Be advised that I've not read the other posts on the thread, so I don't know if you should try this process or not.
Cheers
Click to expand...
Click to collapse
mtty do not format radio rom, so you don't need to re-flash it.
No progress
digitalir, did you make any progress ? I'm not....
Tomal, what do you mean about AS ?
Thx
kotabunga said:
digitalir, did you make any progress ? I'm not....
Tomal, what do you mean about AS ?
Thx
Click to expand...
Click to collapse
AS means active synchronize. Disable USB connection in AS. It has been written there bro...
kotabunga said:
digitalir, did you make any progress ? I'm not....
Tomal, what do you mean about AS ?
Thx
Click to expand...
Click to collapse
my friend,
active sync AS
ok
well i am just back on my chair so looking forward to do it right away
will keep u posted
tried ! but in vain!
yes i have already gone through the wikipage and tried it but after typing the command it just says its invalid command.
i have tried all the ways i can with mtty given in wikipage with no results positive.
pls can anybody suggest the commands for doc format
again thnks
hey!
after much gogling i got mtty1.16 and tried but it does not show the usb port.
so again googling does it support usb 2.0
i think it doesnt.
ok i will try on my old laptop with usb 1.1 tonight at home.
Tomal 1st thnks for ur help and valuable time
can u pls give the details for properly formatting the doc [pls.
any luck ? I dont....my uni still dead...tried with usb 1...no luck...
I upgraded the OS on my rom (I took a rom from the Jade forums and extracted xip and imgfs, a new 21728 OS) following http://www.bepe80.com/test/2/. It built everything ok and I followed the directions exactly. Except the only problem is when I flash it to my phone, the first screen comes up with the red text at the bottom, the console eMo text with the version and radio numbers, and then it freezes there and won't continue to boot. I can reflash via SDCard so I'm not worried about my phone. I just want to fix my ROM and upgrade it successfully. What did I do wrong? I need to get my rom to work. Please help? Any suggestions?
kickindrummerkid said:
I upgraded the OS on my rom (I took a rom from the Jade forums and extracted xip and imgfs, a new 21728 OS) following http://www.bepe80.com/test/2/. It built everything ok and I followed the directions exactly. Except the only problem is when I flash it to my phone, the first screen comes up with the red text at the bottom, the console eMo text with the version and radio numbers, and then it freezes there and won't continue to boot. I can reflash via SDCard so I'm not worried about my phone. I just want to fix my ROM and upgrade it successfully. What did I do wrong? I need to get my rom to work. Please help? Any suggestions?
Click to expand...
Click to collapse
You can re-flash using the bootloader mode and USB or using SD Card, don't worry I think all chef's have created a non booting ROM. It's probably just a bad XIP port.
Ta
Dave
thanks for you help. did you read my post completely? Flashing isn't the problem. "I can reflash via SDCard so I'm not worried about my phone". But thanks for your help, I just need to know why the port was bad because I followed the tutorial exactly. Any suggestions? Is the video correct with porting xip? Or do you have to do something different for kaiser?
kickindrummerkid said:
thanks for you help. did you read my post completely? Flashing isn't the problem. "I can reflash via SDCard so I'm not worried about my phone". But thanks for your help, I just need to know why the port was bad because I followed the tutorial exactly. Any suggestions? Is the video correct with porting xip? Or do you have to do something different for kaiser?
Click to expand...
Click to collapse
Try porting the XIP again. I'm not an expert on it. But Usually with cooking it's trial and error, try not to do everything at once. Do a step, cook a ROM, test it, try the next step and so on.
Good luck,
Dave
kickindrummerkid said:
thanks for you help. did you read my post completely? Flashing isn't the problem. "I can reflash via SDCard so I'm not worried about my phone". But thanks for your help, I just need to know why the port was bad because I followed the tutorial exactly. Any suggestions? Is the video correct with porting xip? Or do you have to do something different for kaiser?
Click to expand...
Click to collapse
what part of new xip did you put in new rom? the only part of new os xip that you use is shared xip(msxipkernel), the rest is from your original kaiser rom.
kickindrummerkid said:
thanks for you help. did you read my post completely? Flashing isn't the problem. "I can reflash via SDCard so I'm not worried about my phone". But thanks for your help, I just need to know why the port was bad because I followed the tutorial exactly. Any suggestions? Is the video correct with porting xip? Or do you have to do something different for kaiser?
Click to expand...
Click to collapse
I am trying to figure out the same thing as well! If did find out why, just let us know in here...
I think I fixed that problem by changing SYS!