Related
Made a huge error.....didnt go through forums and read instructions before trying to Flash a German T-Mobile MDA Compact to a English ROM....
The device is completely dead....
Followed all the steps required to get it back up...It is refusing to do so though....
Used this thread:
http://forum.xda-developers.com/viewtopic.php?t=19500
One thing to note is that I am not using the AC charger, am using the USB cable to charge the phone.
Can someone please helpme...
Haven't got past the bootloader mode...
If you followed the instructions from the other thread, it should have started flashing.
Some things to check on:
1) Did you do a full d2s before you attempted the upgrade? It's always good to have something to fall back on.
2) If you can get to a bootloader screen, all is definitely not lost.
3) Sometimes, it takes 4 or 5 minutes for the "Press to flash" comes up on the screen so be patient with that.
4) Make sure you did exactly a 416 byte copy from the original rom file in to the new flash file.
5) You can only write an nb1 file from the pc AFTER it has been created from the pocket pc. If the SD card has been pc formatted, the nb1 file will write to it but the pocket pc won't recognize it and will just sit there at the bootloader screen.
HTH
I think I fired the MDA
Well I did not create the nbf file from the ppc, downloaded it from the the forum FTP. I do not have the backup of the nbf file. As I mentioned I did not read the forums before trying the update.
I just downloaded the T-Mobile ROM update and tried installing it. Obivousioly it didn't work, Game the dreaded the 112 error in the 3rd step.
Am not even getting the bootlader screen now..
Any ideas on how I can get this device up and running.?...
ok, need some clarification here. "What" are you trying to load (nbf files or nb1 files) and how are you trying to load them (SD flash or the standard USB based upgrade)?
Easy enough to check to see if your device can still get to bootload mode....hold the camera and power switches in at the same time and hit soft reset with your stylus. After letting go of those and you see either "Serial" or "USB" at the top of the screen, you should still be able to recover from this.
Tried with the nb1 files not nbf (sorry abt teh error)..
The bootloader screen was showing up ...unitll I tried the T-Mobile MDAcompact_vers11201
After the 112 error while updating...the device now refusing to get to the bootloader mode.
Have I fried the device and made it unusable....?
hey just got back the bootloader screen...
Take the SD card out, disconnect the USB and tell me what happens when you hold the power and camera buttons in at the same time, then hit the soft reset.
Also, has the unit been charged recently?
Its showing Serial v1.00...after the reset.
Its been on the USB chatge all along.....
Great. If you get Serial at the top, this can be recovered.
If you want a good T-Mobile 1.12 rom file, go here and use this one:
ftp://ftp.xda-developers.com/Uploads/Magician/tmobile-uk_wwe_ROM_1.12.00(thereapermanl).rar
Unpack it and follow all the procedures about copying the 416 bytes, rewriting the file, etc. from the other thread. I have tested this rom file and it installs ok.
Thanks for the encouraging words...
Will it work even if I do not have a backup of the original ROM on my machine?....I only have the tmobile.nb1 file which I got from the XDA forums.
Lemme try using that and editing it.
Thanks a ton for your help.
You might be a little stuck for an nb1 flash if you don't have an original flash back up but don't fear. You can go here and get this WWE1.12 file and just do a USB type upgrade:
ftp://ftp.xda-developers.com/Magician/Shipped_ROMS/WWE_11200_128_11210_ship.exe
I know this one works too. It's ROM 1.12, Radio 1.12 and Ext_ROM 1.12. When you try to run the upgrade program though, it might give you a Country ID error. If so, use the attached upgrade program instead. If this one gives you a Country ID error again, close the program and just run it again. I've been down all these roads already.
Lemme get this right this time: I will be doing the following
1. Install the ROM as you have mentioned. With the country id hack if necessary
2. Hopefully by now the device would be alive. If so will take a backup of the ROM on the SD card
3. From then on follow the instruction given in the doc.
Hope I get it righ this time else Its going to be a long night for me.
Lemme know if I have to do anything else.
Either ROM will work fine for you. It just depends on whether or not you want I-Mate stuff on it or T-Mobile stuff on it.
Doing the USB upgrade will put the I-Mate ROM on but after that, it should be working and you can then do an SD backup, follow the SD flashing procedures and get the T-Mobile ROM on.
Good Luck!
The masupgrateut is throwing up a ruu.dll error?...you seen that one before?
What sort of error? Not found?
yup...
I extracted the ROM exe and found teh file...copied it to the windows folder..and ran the no id program...no error this time round but the update is still giving a COuntry ID error...
Been looking at various posts...specially this one...
http://forum.xda-developers.com/viewtopic.php?t=14973
Thinks thats gonna help?
ok...two things.....just run it again. The no ID program sometimes does that on the first time 'round so just run it again.
Second, stick this at the end of the RUU.conf file:
[CHECKCEID_TYPE]=1
ran the program multiple times...still getting the COuntry ID error...
Are you running this program? MaUpgradeUt_noID.exe
...with the change in the RUU.conf file?
I just noticed something....did you extract all the files to a single directory and just run it from there or did you just pull a few out?
ALL the files have to be in the same directory. This is also where you need to execute the installer program.
All the time i try different ROMs on my XDA mini I get Checksum error at the end...(i replaced the 416 bytes of mine with destination ROM)
How serious is this error...?
Any tool to check the checksum before uploading to device.?
I found out some people mentioned that by soft reseting the device should work properly...
i haven't tried soft reseting after getting checksum error...
I'm abit comfused about byte replacing..some says 416..some 420..some 220...
Would you help me with thesae issues...
The number of bytes that need to be replaced is actually 412.
416 bytes will work too, but you're actually overwritting the first four bytes of the replacement rom with the ones from the backup, but in all the rom I've checked these four bytes are always the same...
If you copy LESS THAN 412 bytes, the rom loader will report "Not allow update!" and no update will be performed.
The checksum error is currently unavoidable because nobody has figured how to calculate it. Only your original backup of the rom will upload without the error.
iDG said:
The number of bytes that need to be replaced is actually 412.
416 bytes will work too, but you're actually overwritting the first four bytes of the replacement rom with the ones from the backup, but in all the rom I've checked these four bytes are always the same...
If you copy LESS THAN 412 bytes, the rom loader will report "Not allow update!" and no update will be performed.
The checksum error is currently unavoidable because nobody has figured how to calculate it. Only your original backup of the rom will upload without the error.
Click to expand...
Click to collapse
Thanks for your Technical Information...
If i change the the 416 Bytes and after updating checksum error appears...what should i do? i read in some threads that some people after getting this error have reset(soft) their devices and continued working with their new ROM...
Is it accurate action?
The soft reset is required after the update, because the device will still be in "boot monitor" mode. The reset is required even with your original backup rom (which will not give you the "Checksum Error").
iDG said:
The soft reset is required after the update, because the device will still be in "boot monitor" mode. The reset is required even with your original backup rom (which will not give you the "Checksum Error").
Click to expand...
Click to collapse
I mean after getting checksum error..soft reseting will make the device work properly with the ROM which has checksum error.
does it harm the Device..?
Let the bootloader finish the rom update and display the "Checksum error", the remove the SD card and perform a soft reset. The checksum error is unavoidable and completely harmless.
Hi, very new on here and very new to the Pocket PC and Imate JAM. I have read allot about backing up ROM and process to get big storage hack but almost everything I read is way over my head. Like what is the extended ROM?? Ssooooo, can someone take all of the latest TIPS and show me the BEST and EASIEST way to upgrading my Imate JAM??? I still have the original ROM but would like to upgrade to the newest 1.12 ROM and 1.12 Radio ROM. I then would like to know how to keep some Imate specific programs installed like Intellitype.(I dont use MMS) PLEASE!!! I will even paypal someone some money for providing this BASIC elementary school level BIG STORAGE upgrade. Please dont assume anything about my level of knowledge as it is VERY basic. Thanks in advance for taking on this challenge. By the way, in the end I would want the latest Imate JAM WWE ROM and Radio in English.(I live in United States and use T-mobile on the 1900mhz band)
bump bump bump
Ok... I think you won't get many replies, because what you are looking for has already been posted here many times. The big problem is that the info could indeed be burried inside very huge threads, so it will take a lot of reading to find it. But I'll try to summarize...
You will need to download the latest ROM for your Magician. Most likely you will want to stay with the ROM specifically designed for your device, for example from I-Mate. That way at least you can perform the ROM upgrade without any fuzz.
Log on to I-mate (or whatever) and download the latest ROM. Reboot both the PC and the Magician and execute the installer. After about 20 minutes, you are done.
You'll want to have access the Extended ROM, where all the standard settings and programs are stored. To do that, you will have to copy Extended ROM to a safe place, because when you have done the Big Storage thing, Extended ROM is gone, and so are these files. In order to get to the Extended ROM, you'll have to:
Hard reset the device after the ROM upgrade, as you are told on screen when the upgrade is finished. This means pushing the power button, while using the stylus on the reset button, located at the bottom of the device. The Magician resets and the setup routine begins. You are asked to perform calibration of the screen and time zone, before the OS is ready to run. Then, a few seconds after you see the Today screen, a 3 seconds countdown appears. At this exact moment you must perform a reset, which simply means pushing the button with the stylus again, this time without using the power button. Now the device will restart without installing files from Extended ROM, and more importantly, without hiding the Extended ROM.
Connect the Magician to the PC using ActiveSync and copy the folder Extended_ROM, located at root, to your SD card and make a backup on your PC. You are now technically ready to take on Big Storage...
But! Beware that If your skills are at the level you suggest, you may end up killing your Magician, instead of gaining Big Storage. This has happened to a lot of people, who then had to struggle their way into getting their device functioning again. Be absolutely sure that you are willing to take the risk, because you may end up cursing yourself for doing this.
Still happy going on? Ok... What's coming next is my edit of other peoples work, so I don't take any credit for it. Unfortunately I don't remember who wrote it either...
You will need to download and install the 'Backup Tools1' found on the FTP part of this forum, to perform the following steps. ftp://xda:[email protected]/Magician/Tools/
Backing up your current ROM:
Make sure you backup your ROM for 2 reasons. Firstly, because you will need to edit part of your ROM in order to be able to flash your Magician with the no extended ROM, and secondly, because you might need it either for flashing your phone in case of a malfunction so you can send it back under warranty with the original ROM, or for helping you to flash future upgrades.
Backing up your ROM can be done by connecting your Magician to the PC through the data cable when you first uncheck the USB connection of active sync.
If your Magician connects with ActiveSync because you didn't uncheck the USB connection in the active sync connection settings then you will not be able to backup your ROM to an SD memory card.
1. Before connecting your Magician you should bring it into the boot loader mode. This can be done by simultaneously pressing power + camera buttons and at the same time the soft reset button with the stylus.
2. After connecting your Magician to the PC through the USB in boot loader mode and having your SD card inserted into the Magician, you run romupdate.exe.
3. Then choose the USB connection in the connection settings of romupdate.exe window and click on ok. After that a terminal window will popup in that window.
4. Type d2s and press enter. Your Magician will start copying the ROM to the sd card. The screen of your Magician will be dark (no light), but you will see it counting up to 100%. When it reaches 100% it will say it is calculating the checksum. Give it some time till its done and it will say checksum ok.
5. After finishing the transfer of your ROM from your Magician to the SD card, put your SD card into an SD card reader connected to your pc. Your pc might pop up a warning message that says your SD Card is not formatted would you like to format? Click No and open a Command prompt (DOS) window.
6. Change directory to your root directory (cd c:\) and run the command ntrw read your_rom.nb1 x: where x is the drive letter of your sd card. That command will create the ROM Backup file of your ROM into your C drive root directory by the name of your_rom.nb1. Make sure you keep your_rom.nb1 in a safe place and use a copy of that file for the rest of the procedure. Note that after finishing the copy from your SD card to your_rom.nb1 file ntrw might give you an error, just don’t pay attention to it.
Patching you ROM:
1. Use Hex Editor to open the your_rom.nb1 file on your PC
2. Use the FIND function to locate "02 00 00 80 00 20 20 00 00" and change it to "02 00 00 b8 01 20 20 00 00". Note that this is a hex search, not ascii, so enter the search as 'Bytes'. You will find this pattern twice inside your ROM, and both should be changed.
Transferring your no extended ROM File from your hard disk to the sd card:
1. Get the fixed no extended ROM file to your C drive root directory run the command ntrw write fixed.nb1 x: in the command prompt window where fixed.nb1 is the filename of your fixed ROM and x the SD card drive letter. Wait till it finishes and move to the final step.
Flashing the Fixed no extended ROM to your Magician:
1. Put your SD card into your Magician and get your Magician to boot loader mode again (power+camera+reset buttons). On your unlighted screen you will see it says serial wait and after some seconds it will say (Press Power to flash).
2. Do as it says and it will start flashing. When your Magician reaches 100% flashing, it will check the checksum. Don't worry about the message Checksum failed - Flashing failed and soft reset your Magician. Please notice that the first boot may take something like 5 minutes, so don't worry about it.
When your device reboots, you now have a Big Storage Magician! If you need parts of the Extended ROM installed, like fax, MMS or whatever, you can simply click on the files inside the Extended_ROM folder you backed up earlier and they will install.
My guess is that by now you will have realized that there IS no easy way to get the Big Storage. Even though it sounds harder than it is, it does take some time and care to perform right.
There are other ways to do Big Storage, but this is the clean way. You don't have to rely on patchers, and you won't have your boot screen turned into something that another user think looks cool. This is the real deal with only 4 bytes getting changed, and you know for sure you'll have the right Extended ROM available as a backup, and that is as good as it gets!
WOW!! This is excellent and very well done. I am glad to be learning so much about these ROM's. Two questions before I tackle this(I know Im such a newbie)
Give me a couple days and I will report back on my progress.
Magician Extended Rom Unlocker Works!!!
Wow major thanks & god bless -- exactly follow your simple directions (add final reboot blue imate screen takes awhile) and wow - its done - now to change my pants....
After a few hours of struggling I finally got it working!!
Thanks HBK
:shock: wow...am imperessed...thanx HBK..
It's not a matter of not knowing how to make big storage (i've already did it a couple of times :wink: ),but the issue here is that u wrote a "manual"!!!!
thanx bro...hell am gonna copy every word u said and add it to my archive under "HBK big storage manual"... :wink:
Thanx again for ur time!!!!!
RAGO :lol:
Hi all,
Another newbie here, just wanted to checked before I tried this upgrade, but will this work on my XDA II mini?
Im soooo sick of having no memory, so I hope it is!
Deva
hey just a quick question thatnls a lot for the write up
what size sd card do you have to use
i used a 256 (only have that or a 1gig one) and the boot loader comes up with a message rom size too small
thedeva said:
will this work on my XDA II mini?
Click to expand...
Click to collapse
Yes, it will.
aaith said:
i used a 256 (only have that or a 1gig one) and the boot loader comes up with a message rom size too small
Click to expand...
Click to collapse
I tried using my 1 gig card and the hex editor wouldn't open it as it was too large (The rom will be the same size as your card). I then found the patch to automatically apply the big storage and it worked a treat. I don't have a 256 but I heard a fair few people use it for their upgrades....
HBK is the king. He's danish
good going babyy.. *thumbs up*..
i cant wait to reach home and try the procedure...
after waiting for so long, i finally got home, and sat down to install bigstorage by my new 256 mb card... but the problem isnt solved... why does it say 'card initialize is fail!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!'.. maaan im soo fuked..
castiwo said:
after waiting for so long, i finally got home, and sat down to install bigstorage by my new 256 mb card... but the problem isnt solved... why does it say 'card initialize is fail!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!'.. maaan im soo fuked..
Click to expand...
Click to collapse
r u using an SD or MMC?try an SD one....
RAGO :lol:
SD 128MB
It was almost the same with me? some errors with my SD 512 Kingston (back up done well, asking push the power, but after romupdate & ntrw nothing happen ), after the card died, was finding another one about friends. It was 128 mb Trancend good one. I did it with my 12.128.12 on MDA-Compact? then upgraded radio till 13 about month ago!
when i try to copy my modifiedrom.nb1 to the SDcard through ntrw... it says... 'the semaphore timeout period has expired'... wot does it mean?.. had it not copied rom to the sd card?... or shud i just ignore it.??.. reply as soon as possible..
Just wanted to know can this method of changing the hex code work on all the ROMs, like even ones that may be released in the future?? Or does the Hex code change for ech ROM version??
And what actually are you doing when you change 02 00 00 80 00 20 20 00 00 to 02 00 00 b8 01 20 20 00 00??
James
Will this work for the imate JasJar?
Sorry, to ask such a basic question, but this is all very new to me. I've been reading the site for the past week or so trying to get a handle on all the information. I definately want to remove the EXT_ROM from my JasJar to free up as much memory as possible. Will the procedure listed above (HUGE Thanks to HBK) work for my iMate JasJar? Thanks.
P.S. I do realize that this is a "JAM" thread, sorry for the overlap. I'm still trying to figure out exactly what is meant by "cooking" (which I'm guessing means "modifying"). Any help is definately appreciated.
card initialize is fail!!!
Hi guys, i also got the same prob with Castiwo ..card initialize is fail!!! i used SD 128MB Sandisk.. how to work it out? many tks
I've got a question. I understand that if you did the BigStorage patch, and then you restored from a backup when you didn't have the BigStorage patch, you'd have only wasted your time getting the BigStorage as everything would be over-written.
So here's my question. Does it work the other way around? I mean, if for example you had a backup (from Sprite, xBackup, or whatever else software) from where you had a BigStorage patch, then you restore from that backup onto a Magician with the original, unpatched ROM, would it work?
Hi I know the big storage hack is plastered all over this forum but i still cant get it right.Some one please help me!
Ive got a magician with rom version 1.13.00 WWE radio v. 1.12.00 (i used to have 1.12.00 but i upgraded it by accident.<I woz finkin of it anyway>)
I fink Ive tried every procedure possible but always have problems but basically this is what ive done:
1.Using OS image tool ive copied my rom to pc.
2.Ive changed the 80 00 00 thingy to b8 01.
3.Ive tried to use the os image tool to write it back t ppc but it comes with a usb/communication error in programme A.Im using this way because I have only 32mb mmc card.
Any help would be much appreciated,
Thanks
wiki
Try the wiki (top right link on the page) & go to the magician section. It contains a description howto patch a shipped-rom, the one you used to upgrade to 1.13WWE, & get BS. Apperently you missed this method.
Cheers, M
I already have all of them files.Wen I patch it the size goes right up then 'programme a' doesnt copy it over becuase its too big.it has 2 b excactly 32 i fink and after i patch it the size changes.
My main problem is getting the rom over 2 the magician.Since I dont have a card the only 2 ways i can fink are using osimage tool or program a, both of these im having problems with.I have roms that i have patched and changed the 416 bytes to my roms.I have roms that were patched and ive changed to my roms.I have roms made using byte copy.I just cant get any of them over!!
Thanks 4 ure help,
Gareth
I already have all of them files.Wen I patch it the size goes right up then 'programme a' doesnt copy it over becuase its too big.it has 2 b excactly 32 i fink and after i patch it the size changes.
My main problem is getting the rom over 2 the magician.Since I dont have a card the only 2 ways i can fink are using osimage tool or program a, both of these im having problems with.I have roms that i have patched and changed the 416 bytes to my roms.I have roms that were patched and ive changed to my roms.I have roms made using byte copy.I just cant get any of them over!!
Thanks 4 ure help,
Gareth
Stop,
You're going in the wrong direction. The BS from shipped-rom method is about patching the provider supplied exe file. & after the patch you run it like a regular rom-upgrade. No SD or MMC involved!!! It's a rom-update via USB like the normal update.
pls read it once again @ the wiki.
ok thanks im trying that now.Im stuck on getting nbfdec to run.Ive extracted it to the unzipped rom folder.I open ms-dos command prompt and drag and drop the .exe on the command line to save typing the path.The program runs but then it crashes.Can anyone help me?
Try putting everything in "C:\BS" saves a lot of typing errors including filename handling.
Ive done that now but I dont know how to execute the command.Do you think you could type the whole command for me?When I open command prompt it says this c:\documents and settings\rod simpson\> ive tryped typing in that command but i dont know how to put it in with the path etc.
Sorry for going on and on I cant get my head round it!
Thanks
garethsimpsonuk said:
Ive done that now but I dont know how to execute the command.Do you think you could type the whole command for me?When I open command prompt it says this c:\documents and settings\rod simpson\> ive tryped typing in that command but i dont know how to put it in with the path etc.
Sorry for going on and on I cant get my head round it!
Thanks
Click to expand...
Click to collapse
Hi Rod,
To go to C:\BS from your personal doc&settings type on the commandline:
cd \ [Enter]
now you should be in C:\
then type:
cd bs [Enter]
now you should be in C:\BS
Works for other directories too.
Cheers, M
Thanks, that helped me a lot.Ive done everything els now so I converted it back to nbf and then executed the maupgrade_noid.It checked device info then displayed the rom to and from screen and both were blank.I proceeded and it displayed the 'success' screen but nothing had actually happened on the ppc.Ive tried the other upgrade program and the one thats cracked on the site.
Any help would be much appreciated
Thanks
Did you reset after the update process finished? & if so did it boot normally? & if so did you look at the internal storage folder size? Cause that's the only thing that's changed & the ext-rom has disappeared. Oh & you shouldn't see the customization start after a hard-reset...
btw rom to & from shouldn't be blank, pls run the update program without patch cause I think the editing somehow invalidated the shipped-rom. The original upgrade program should work & if so you know what's going on. If the original program fails there might be something with your device.
So start the plain shipped-rom first to find out..
Thankyou!Its worked!!
I went from scratch and downloaded all the files again.This time i didnt put my own header in the file because i thought thats where i'm going wrong.My devicedata.txt file looked like gibberish to me and it wouldnt copy and paste in to hex editor.So i just left it.I changed the 2 values in the code, converted it and flashed it.Will not having my header cause problems?My storage is now 26.72mb is that right?
Thankyou very much oltp for your help.It's much appreciated.
I think this site is long overdue a donation from me.
Cheers m8
Thankyou!Its worked!!
I went from scratch and downloaded all the files again.This time i didnt put my own header in the file because i thought thats where i'm going wrong.My devicedata.txt file looked like gibberish to me and it wouldnt copy and paste in to hex editor.So i just left it.I changed the 2 values in the code, converted it and flashed it.Will not having my header cause problems?My storage is now 26.72mb is that right?
Thankyou very much oltp for your help.It's much appreciated.
I think this site is long overdue a donation from me.
Cheers m8
The header contains info about romtype & provider name, probably some things more I'm
not sure about. The reason for changing it is to avoid errors like the country id error. With the use of maupgradeut_noid it's less important.
One thing I'm questioning is the reason why some of us have probs with connecting to the, I believe, special O2 services. Some claim there not able to connect anymore... Can some other setting as well. I'm on T-Mobile & everything works fine.
Basically if the upgrade was succesfull, you have an enlarged storage & the rest of your device will be working as before.
Cheers, M
how much space would i have in my main memory now? i have a 64+64 system (O2 Xda Mini) now branded to T-Mobile 1.33 and now applied the new patch (BIG STORAGE) using the Wiki Information guides. However any idea how much FREE space on first reboot i should have.
did the first reboot...(soft reboot) after flash...its been 3 mins and just the T-Mobile Screen..how lng should i wait before i "think" its a bad flash?
nevermind got it
Total Main Memory - (FREE MEMORY) - 43.99MB Storage / 25.54 MB Programs! woo hoo this is HOT
shivam said:
did the first reboot...(soft reboot) after flash...its been 3 mins and just the T-Mobile Screen..how lng should i wait before i "think" its a bad flash?
Click to expand...
Click to collapse
First boot takes much more time than next boots.
Have fun, M
all,
look over here.
cheers!
Sorry to say, but it's old news. We got a thread about it for three months now I guess with that method. Problem is you always need to update first & then dump your rom again. & somehow not all dumps are accurate. The brick change with a SD is larger than with a shipped-rom.
M
I've done the requisite searching so now my post.
I'd like to dump my phone's filesystem and get files from the dump.
I do not have access to the OS. Only the bootloader.
Specs on the phone are:
Model: HTC Kaiser 120 (Bootloader says 130?)
OS: Windows Mobile 6.1
Rom version: Unknown
HardSPL: YES; v3.29
I figure that I'll need:
MTTY
a list of commands that will allow me to dump various portions of the NAND
a list of addresses that correspond to various parts of the filesystem on (in?) NAND
a program to rebuild the filesystem from raw memdumps
I remember it being mentioned somewhere that this was theoretically possible.
Thanks for your help and support.
(sorry about wordiness)
Wow, that sounds so good. I just wish I knew how to help Hope you find something, I'll be looking back here to see if anybody has any ideas. It would be handy to know how to do this incase I ever need to do it.
LoveMyPhone said:
I've done the requisite searching so now my post.
I'd like to dump my phone's filesystem and get files from the dump.
I do not have access to the OS. Only the bootloader.
Specs on the phone are:
Model: HTC Kaiser 120 (Bootloader says 130?)
OS: Windows Mobile 6.1
Rom version: Unknown
HardSPL: YES; v3.29
I figure that I'll need:
MTTY
a list of commands that will allow me to dump various portions of the NAND
a list of addresses that correspond to various parts of the filesystem on (in?) NAND
a program to rebuild the filesystem from raw memdumps
I remember it being mentioned somewhere that this was theoretically possible.
Thanks for your help and support.
(sorry about wordiness)
Click to expand...
Click to collapse
why you don't go to the TRI-Color screen and flash the rom again.. flash one Official like 3.34.721.2 from HTC
to go to the TRI-Color screen must pust together the photo button + Power button and after 2sec the reset all this together
and then connect the usb and flash the 3.34.721.2 htc official rom
b16b said:
why you don't go to the TRI-Color screen and flash the rom again..
Click to expand...
Click to collapse
I guess I sacrificed a few too many details in favor of avoiding wordiness. I know I'm a bit crazy, but I'd like to try to recover my files. Re-flashing would hose my files for certain no? I'm fairly certain that everything is mostly intact because if the phone is given five to ten minutes, it will get to the today screen. However it will be lethargic and wont connect to Windows via ActiveSync (thus ruling out itsutils for file grabbing right?). Anyways...
Simply put, file recovery is the goal. I'm OCD and not knowing what I've lost is driving me nuts. (heh...)
Thank you, and again, help and support is greatly appreciated.
(bold included for people who like to skim instead of read everything)
Sorry for necroposting, but I have the same problem with my Elf and this is the only thread about this problem that I could find so far.
Have you, by any chance, found a solution (and still remember it )?
My details:
Windows plays the loading animation and then is stuck. After a few minutes I get a white screen with black text and some garbled pixels at the bottom which says that Windows was unable to boot (because I may have installed some malicious software, yadda Microsoft fud, yadda) and that I can press the Send key to hard-reset the device, erasing all my data in the process.
The power led is also not active, so eventually I'll have to charge my battery in someone else's device in order to use mine again.
Hmm, it seems I am subscribed to this thread, even though I haven't really used my WinMo phone (or this forum) in about a year. Unfortunately, I don't think I every found a real solution. If i recall, I ended up waiting for it to boot and then copied my files to the SD card. Unfortunately, it sounds like you don't have that option so your data is probably toast :/.