Database Develop

ERROR: ITWriteDisk - An internal error occurred.

Okay, I have searched the forums, to no avail. I also no longer have the .bin files generated when I first ran lokiwiz, they were accidentally deleted by another individual who rebuilt a box before I had a chance to pull them off.
So basically, I am screwed, every command I try with lokiwiz or awizard results in the following errors
ps, I am trying to restore the original 8125 image, I have a functioning device, but I want to restore it.
...
CopyFileToTFFS(cidunlocked.bin:0, 0, 00010000)
ERROR: ITWriteDisk - An internal error occurred.
result=80072746
[19:15:05.84] Your phone is now CID unlocked....
Store the generated 'lock_backup.bin' file in a safe place. It can help to resto
re your device if anything goes wrong.
* Press [Enter] to continue

I'm having the same issue on a unit with the K-JAM_WWE_216901_2169101_020710_ship ROM....

I'm having the same issue on a unit with the K-JAM_WWE_216901_2169101_020710_ship ROM too.

lot's of people have that problem, whit that specific rom :S
me too, but there does not seem to be a solution yet...
for te topicstarter: flas another rom on your device and lokiwizard will work again

lokiwizard refuses to work, even after flashing the latest imate rom to it (although I am using the imate rom installer application), I guess I could try the ruu tool ..... ??

flash back to t-mobile rom, unlock it an flash back again to imate

I have no problems flashing to the imate rom, thats what I am running at the moment. Using the imate rom, I cannot run awizard or lokiwizard.

Johannus said:
flash back to t-mobile rom, unlock it an flash back again to imate
Click to expand...
Click to collapse
Is that possible?
From what I gathered, if you flash it to the iMate rom, the Extended rom portion becomes locked to the iMate Extended rom. You can't even reflash it back. Until someone comes out with a version of the full iMate rom with an unlocked Extended, or breaks up the iMate rom into GSM, OS, and Extended and you do it manually, I think it is impossible.
Or I could be totally wrong.

fuzzycuffs said:
I think it is impossible.
Or I could be totally wrong.
Click to expand...
Click to collapse
i think you are... cause i did it myself
and for the topicstarer: i know you cant use awizard nor lokiwiz, but if you flash your original T-mobile rom back, just like i did, then use awizard or lokiwiz to unlock the SIM and the CID. and after that flash the imate rom on your device again, your problem will also be solved!

Johannus said:
fuzzycuffs said:
I think it is impossible.
Or I could be totally wrong.
Click to expand...
Click to collapse
i think you are... cause i did it myself
and for the topicstarer: i know you cant use awizard nor lokiwiz, but if you flash your original T-mobile rom back, just like i did, then use awizard or lokiwiz to unlock the SIM and the CID. and after that flash the imate rom on your device again, your problem will also be solved!
Click to expand...
Click to collapse
Alright, then answer me this:
Can you take the iMate full rom, do that flash, and just then flash the TMO extended rom on top of that, so upon a hard reset it'll have the iMate GSM and OS roms, but then go through the stock TMO Extended rom updates (one of which will kill wifi)?
If so, that answers my question of going back to "bone stock." That's my concern with flashing to the iMate rom: 1) having a locked extended rom that I may or may not be able to revert back from, and 2) being able to go back to how the phone looked coming out of the box.

fuzzycuffs said:
Johannus said:
fuzzycuffs said:
I think it is impossible.
Or I could be totally wrong.
Click to expand...
Click to collapse
i think you are... cause i did it myself
and for the topicstarer: i know you cant use awizard nor lokiwiz, but if you flash your original T-mobile rom back, just like i did, then use awizard or lokiwiz to unlock the SIM and the CID. and after that flash the imate rom on your device again, your problem will also be solved!
Click to expand...
Click to collapse
Alright, then answer me this:
Can you take the iMate full rom, do that flash, and just then flash the TMO extended rom on top of that, so upon a hard reset it'll have the iMate GSM and OS roms, but then go through the stock TMO Extended rom updates (one of which will kill wifi)?
Click to expand...
Click to collapse
No, but you (1) don't have to and (2) DON'T WANT TO, as some of the T-Mobile CABs will kill things in the new release AND they're inferior anyway (the connection button is one of them!)
In fact, unless you want the OZIm client and the "SMS email triggers" you need to load only TWO of the T-Mo US CABs on top of the Imate ROM (by hand) to get full functionality. No problems with this approach at all (of course you don't get the T-Mo pukie home screen this way, but I don't want it anyway!)
I posted in one of the other threads where you asked this how to accomplish it.
If so, that answers my question of going back to "bone stock." That's my concern with flashing to the iMate rom: 1) having a locked extended rom that I may or may not be able to revert back from, and 2) being able to go back to how the phone looked coming out of the box.
Click to expand...
Click to collapse
Going back to how the phone looked out of the box is easy if you have an SD image of the original T-Mobile ROM and an SD card. No problem with that at all - as I've noted here repeatedly I have TESTED this and it works fine.

So let me get this straight, to get past the locked extended rom imate creates, I need to flash to tmobile to be able to flash bac the original cingular rom? Ah well, guess I gan stay with the imate rom till cingular releases an official rom release

k-jam, another brick in the wall (dead after rom update)

Hello folks,
Today I flashed with the ROM in thread 'T-Mobile USA 2.17 ROM (Custom)'. After it came up, I ran through the screen align and wizard. When it was all done installing extended rom etc it restarted on its own. After booting back up, everthing was really slow and there was no cell signal. The battery icon had an ! mark on it and when clicked, it says unknown battery. At this point everything keeps freezing and genrally not working including no activesync connection possible. I restarted into the bootloader and tried to flash again. It completed, but now I just get the tmobile boot screen, and eventually it restarts again, never completing the boot. This is when I notice that it doesnt seem to have a radio rom (GSM) version listed, but rather a gap where it should be. I ended up pulling the battery out and trying to get back into the boot loader again, and now I cant get it to power on in any way.
I guess that is enough said. The only other thing to note is that everything was working fine prior to the attempted update, I was merely hoping to get a performance boost, as I was using the original rom.
Any thoughts?
Thanks!
B. Ramsey

Fixed!
No other ROM would install, but in reading back through threads, I found a link to RUU_Prodigy_1081002_108_10910_TMO_US.exe. After installing this, I had my GSM rom back. Then everything worked. I think the not powering on issue had to do with the fact that it sat in the bootloader screen for several hours at one point. Since there was no standby, the battery was wasted. I am attempting to reflash it now to 2.17, we'll see.

No dice
After installing the 2.17 ROM, no more GSM, and same problems. I reflashed back to the previous and it works again..

Re: Fixed!
pterodyne said:
No other ROM would install, but in reading back through threads, I found a link to RUU_Prodigy_1081002_108_10910_TMO_US.exe. After installing this, I had my GSM rom back. Then everything worked. I think the not powering on issue had to do with the fact that it sat in the bootloader screen for several hours at one point. Since there was no standby, the battery was wasted. I am attempting to reflash it now to 2.17, we'll see.
Click to expand...
Click to collapse
THANK YOU SO MUCH for posting this! I also had a brick because of the same setup - trying to use the custom TMOBILE ROM. I had the same symptoms you did - basically non-responsive and no radio stack and no USB connection. I was not getting anywhere with any other ROM. Now, at least I have a working device.
Still no AKU2 though
Let me know if you manage to get an AKU2 ROM on your device!

That's worrisome. Do you know if the CID unlock was successful? (I think it's scripted into that custom upgrader)
If you're feeling adventurous, you could try intalling the custom 2.17 Cingular upgrader I made (it's on the FTP server). If that's successful, then the problem is with the T-MO upgrader. Based on all the folks having success with that T-MO upgrader though, I imagine the only issue might be a corrupt download. If the Cingular upgrader results in the same behavior, then the problem is either with the CID lock or some odd hardware problem.
I'm truly perplexed by the issue you're having..sure wish I knew how to help ya.

Thanks for the replies. My phone was already unlocked as it was purchased that way. I actually did get custom 2.17 tmo Rom to work, I just hadnt posted here yet. After flashing to the older rom, I flashed to the 2.16 Rom on clubimate.com. Then I had a working 2.16 with GSM. I figured what the hey and went ahead and tried the custom 2.17 Rom again. All is great, and FAST. I wish I could remember what custom Rom I was using before I think it must be the culprit. I cant remember, but it did have the extended rom free and open, total commander, and an unlocker.
Thanks

pterodyne said:
Thanks for the replies. My phone was already unlocked as it was purchased that way. I actually did get custom 2.17 tmo Rom to work, I just hadnt posted here yet. After flashing to the older rom, I flashed to the 2.16 Rom on clubimate.com. Then I had a working 2.16 with GSM. I figured what the hey and went ahead and tried the custom 2.17 Rom again. All is great, and FAST. I wish I could remember what custom Rom I was using before I think it must be the culprit. I cant remember, but it did have the extended rom free and open, total commander, and an unlocker.
Thanks
Click to expand...
Click to collapse
My device is a QTEK 9100. I was upgrading from the ROM on my device when I got it:
ROM 1.1.7.5 9/22/2005
Radio: 01.01.10
Protocol: 4.0.13.16
ExtROM: 1.1.7.105
My carrier is TMobile, so I figured the TMobile custom rom that was built off of the latest QTEK would be a good bet for me - but instead I ended up with no Radio.
I have the IMATE ROM you refer to - maybe I'll try to go to that as an interim step to get to the QTEK ROM I really want, since you had success with that method.
What I don't understand is why the Vanilla QTEK 2.17 (which is what I tried after the TMO Custom 2.17) gave me problems. I don't recall the exact error message, but basically it said it couldn't use that ROM on my device.

pterodyne said:
Thanks for the replies. My phone was already unlocked as it was purchased that way. I actually did get custom 2.17 tmo Rom to work, I just hadnt posted here yet. After flashing to the older rom, I flashed to the 2.16 Rom on clubimate.com. Then I had a working 2.16 with GSM. I figured what the hey and went ahead and tried the custom 2.17 Rom again. All is great, and FAST. I wish I could remember what custom Rom I was using before I think it must be the culprit. I cant remember, but it did have the extended rom free and open, total commander, and an unlocker.
Thanks
Click to expand...
Click to collapse
When you say it was already unlocked, don't you mean SIM unlocked? It would be unusual to buy a phone that is already CID unlocked.

I bought the unbranded k-jam from Simoncells.com. All I did was put my tmobile sim card in it and it worked. I guess I dont know the difference between SIM and CID unlocking.

Well theb that's where you went wrong, sim unlock refers to ur phone being able to use any world sim card...cid unlock refers to country Identification...if ur fone is not cid unlocked then wen u install foreign roms it will bugg up ur fone...dats wat happened to u and that other fellow pterodyne...I sim and cid unlocked my fone. ran the tmo 2.17 custom rom without a problem....plz do ur research on upgrading roms b4 u bash them...most factory fones don't come cid unlocked so I'd b surprised if urs did (tho it prolly came sim unlocked)...

Downgrading Upgrading LokiUnlock Overwhelmed and Confused Plz help

Ok I purchased a new Cingular 8125. It is a G3 Version. It was purchased with these settings
Original
Ipl 1.08
Spl 1.08
GSM 01.09.11
OS 1.8.11.1
New
Currently I Upgraded it to the HTC Release ROM from
HTC's website Settings now are
Ipl 2.25
Spl 2.25
GSM 02.25.11
OS 2.25.11.1
I want to use Risi's new 2.26 Rom but I can't CID/UNLOCK my phone. I noticed that there are MANY others here with the SAME problem.
I'm Begging for some assistance.
We need
1. Instructions on how to Downgrade to 1.8.11.1 so that we can use LOKIWIZ to unlock it. Thereby enabling us to use cooked up roms.
Been looking all over for the programs that are needed to do this. And I'm just as lost as ever. I definately do not want to brick my 8125 but I'm out of options.

http://forum.xda-developers.com/showthread.php?t=263116
Forget the warning at the top, I just used this method and on my new 8125 with the same firmware you are running and it worked fine. Take your time and follow directions. If you are not absolutly sure after reading the instructions stop and forget it. Download all the tools you need and do a dry run in your head.
Oh, I just found all this information a couple days ago by searching and spending time on the forum reading.

thanks man. im doing it right now the downgrading process hopefull it works. pray for me. if it does work ill have your children, build a shrine in our honor, and send 5 strippers to your house. if it fails i shall smite thee to hell on earth and take your first born.

well ive tried everything man. I went BACK to that old rom. Did the CIDunlock deal it apparently worked. But Nothing else does. It goes back to the old 1.xx rom then i made the mistake of upgrading to risis rom immediately. that didnt work. kept everything the same but installed the EXT rom. so i went BACK to the 1.xx rom unlocked again and then installed the 2.17 shipping rom. It instaleld but the OS stayed stuck at 1.xx. I ran risi and it only installed the ext rom again. I'm beginning to think my device can never support any cooked up roms and have given up. I'm installing the HTC shipped 2.25 rom now and hope that everythings all good and gravy again and all my numbers match up again. Hopefull this will be the case.

Backing up original ROM possible?

Hi guys.....Ive go an orange m700 uk Model
but would like to try some of these new roms that are popping up.....Is it possible to backup the original rom and then if needed flash back this at a later date.
Thanks

Any ideas on this guys?
Really would like to update to a better stable rom...butt need the option to get back the orange Uk rom
Is it possible to backup the original ram?
Thanks

How is it possible before upgrading new rom version? And how can I restoring original rom after upgrading if necessary? Please help...

Read this:
http://wiki.xda-developers.com/index.php?pagename=Trinity_HowtoReconstruct
If thats too complicated for you, see if you can manage this:
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoDumpRom (works for Trinity as well)
If you have a dump, you can reconstruct it. Except for Extrom, don't overwrite it if you want to keep the files there original.

hi i just took delivery of my m700 on Monday and have flashed it 3 times since then( dopod then htc official one but picked the wrong one with no gps then the right one with gps) with no problems also unlocked sim and cid every time as i didn't know if it was still unlocked
So just to help unlock it and flash with the htc gps rom and get some goodies installed
Robert

Backing up ROMS

I recently reflashed my Orange branded Kaiser with HTC's official ROM from thier website.
After flashing the unit, the radio refused to work, and had to send it back to HTC and they replaced the main board, luckily under warranty. The phone now works great.
I am considering flashing to a new ROM but don't want the same thing to happen again. Is there any way i can back up the exisitng ROM so that if it all goes wrong i can go back to what i had before.
I have done some searching but there does not seem to be anything concrete or a procedure to do this. Can anyone help. thnx

I beleive that method is outlined in the wiki.

SPB and/or sprite backup are Comercial Apps than can backup your phone.
We have a copy of the WM6.1 Offical Orange ROM untouched on XDA-Devs if you need to flash back to it.
Here is a thread discussing upgrading and unlocking your Orange Kaiser:link
and here is another discussion I had with an orange user about upgrading: link
Take some time to get familiar with the Kaiser ROM upgrading process and then follow the advice in those threads and you should be fine.
Thanks
Dave

Thanks Dave i will have a look.