Database Users

Flash storage usage??

I have searched the forum but could not find something of relevance.
It might sound stupid and maybe there is an easy explanation, but what I just don't understand is the following:
TyTN specs say 128meg ROM, 64meg RAM.
Looking at Start->Settings->Storage it tells me (translating from German):
File storage total: 56.22 megs
Program storage total: 48.80 megs
Then the usual stuff like 'used' and 'available'.
Of course there is the ExtendedROM which shows a total of 9.57 megs.
Where's the 128 megs gone or what am I missing here??? :roll:
Thanks for your help.
Cheers,
StonyA

the operating system basically. a perfectly intact copy is held in rom so that you can reinstall at any point using hard reset, this image is what you flash when you update your phone (same goes for your radio protocol).
hope this helps

herman3101 said:
the operating system basically. a perfectly intact copy is held in rom so that you can reinstall at any point using hard reset, this image is what you flash when you update your phone (same goes for your radio protocol).
hope this helps
Click to expand...
Click to collapse
Hello herman3101,
Thanks for your reply! Still a bit confused though. I understood the files stored in the "ExtendedROM" to be those who are used for reinstall.... ???
Even though, why doesn't it show Total ROM 128megs and xxx used???
I guess, I am still something missing :?
Cheers,
StonyA

The extended rom contains the customizations and patches that your carrier decides to put on, this is the way that different roms vary between carriers. The extended rom does NOT contain the operating system, this in a seperate hidden region of your rom (note that rom in this case has two variations of a meaning, one refers to the physical memory on your phone, the other refers to the image that is placed into that memory)
Think of that part of your memory as being an image of your windows xp cd rom, for normal day to day running its not needed as all the files it needs recide on your hard disk but when you come to reinstall you need to work of the cd. Same principle applies to that part of the rom. apologies if my analogy only makes sense to me, I have a habit of doing that.

Hey herman3101,
Many thanks for your explanation. Yes it does make a lot of sense what you are saying. Still don't understand why HTC does not openly show that, i.e. 128 megs rom, xxx megs used, xxx megs available.
Cheers & great weekend,
StonyA

Reversing IMEI-CHECK's Wizard Unlocker :)

Hey Folks,
After a long weekend of reversing I am about 95% done in reversing IMEI-CHECK's unlocker for the Wizard.
The application is protected by Themida which is in my view the leading protector on the market currently (yes better than execryptor).
The unlocker has Ring0 protection, Emulated API's, Resource Encryption + Lots more fun and games.
Now onto what I have found so far.
The GUI stuff:
Code:
set 1 0
set 5 ffffffff
set 2 0
set 6 000000
set 4 000000
progressbar 0 239 0 255 ffffff 100 0
shmsg 0 0 " . : | Wizard Unlock | : ."
info 1
shmsg 3 0 " ..detecting device.."
set 32 2
info 0
shmsg 4 0 " >>> Wizard found"
Is plain to see, but the evil work is well tucked away in a procedure which is pushed onto the VirtualMachine.
So I still need to fish that out (loooonnnng task)...
However the very most interesting part (I find) is the existance of a ROM inside the unlocker.
Now I am not sure if this is the bootloader/gsm rom however it certainly seems VERY interesting that it is included.
Download:
http://rapidshare.com/files/12763879/_00CC0000.mem
For those who wish to analyse it and let me know which it is and if anything has been altered.
It might well just be standard, who knows :S
The following tools are also 'picked up':
Filenames:
Code:
PORTMON.exe
SnoopyPro.exe
Device Monitor.exe
Window Titles:
Code:
Portmon Class
SnoopyPro
USB Monitor
Device Monitor
Serious Serious Kudos to the developer, Very impressive work indeed!
By making this, he has almost made himself a license to print cash.
Since he has NO terms about his programs what so ever then there is no legal problems with what I am doing to his application.
He is probably too scared of HTC anyway, since he is decompiling their firmwares in order to make the product. (Which is outlawed in HTC's terms)
Anyway....
Watch this space

Very interesting, would information gathered from the Wizard unlocker lead to cracking the Treo 750 unlocker? Or any other phone that imei-check supports for that matter?

Whiterat said:
After a long weekend of reversing I am about 95% done in reversing IMEI-CHECK's unlocker for the Wizard.
Click to expand...
Click to collapse
Great, will you disclose your findings? there was an earlier post about the unlocker for G4 wizards, here (see comment #36):
http://forum.xda-developers.com/showthread.php?t=284312
Whiterat said:
However the very most interesting part (I find) is the existance of a ROM inside the unlocker.
Now I am not sure if this is the bootloader/gsm rom however it certainly seems VERY interesting that it is included.
Click to expand...
Click to collapse
It seems that this is the patched SPL that is flashed on the first unlocking step, it is modified so that when it is told to flash an splash screen, it flashes the security area, overwriting the CID.
Whiterat said:
For those who wish to analyse it and let me know which it is and if anything has been altered.
It might well just be standard, who knows :S
Click to expand...
Click to collapse
I will load it at IDA and compare with a normal wizard SPL...
Whiterat said:
Serious Serious Kudos to the developer, Very impressive work indeed!
By making this, he has almost made himself a license to print cash.
Click to expand...
Click to collapse
Yes, the imei-check guys are doing great job with their unlockers... similar method is used in artemis unlocker too. They load a modified SPL in RAM and jump to its physical address from WinCE, this modified SPL shows the DOC ID in help of "set" command and allows flashing unsigned code, then they use obtained DOC ID info to patch the security area by sending a "fake" splash screen, same as in wizard unlocker.
Whiterat said:
Watch this space
Click to expand...
Click to collapse
I will

phoa not much point in me continuing!
You've got the whole lot there!
I'm a lover not a coder, I simply reverse in order to help others succeed.
Since you have all important info anyway, Not really going to be of much help here
P.S do you have any sigs for IDA or any scripts?
I dont like having to sift through manually as binary file......

Whiterat said:
phoa not much point in me continuing!
You've got the whole lot there!
Click to expand...
Click to collapse
Well I didn't want to discourage you on continuing the reversing process, I just pointed you to the thread where we discussed about the unlocking method a while ago...
I admire the fact that you reached that far only disassembling / debugging the binary, what we actually did to have the full process was capturing it with USB monitor; the unlocker can be tricked if you run the usb monitor process as one user, ant the unlocker as a different user, but imei-check seem to have corrected this 'bug' in newer unlockers.
Whiterat said:
Since you have all important info anyway, Not really going to be of much help here
Click to expand...
Click to collapse
We don't have _all_ the important info, we have the commands that the unlocker sends to the bootloader, but the data sent to flash the security area is actually different in every phone, so flashing what is sent in one phone to another phone will actually brick it.
I think it can be helpful if you manage to reverse the algorithm that the unlocker uses to generate the code which is flashed on the security area, this can't be done capturing usb traffic, this has to be reversed from the binary, and Themida is not easy to break as you sure have noticed
Whiterat said:
P.S do you have any sigs for IDA or any scripts?
I dont like having to sift through manually as binary file......
Click to expand...
Click to collapse
No sorry, i don't have any... I am not very used to IDA, started using it few months ago and still learning new things about it everytime I start it

Ah cool I will look into it a bit further
(Need to get a friend to code a tool to remove the junk code)
e.g
PUSH EAX
PUSH EDX
MOV EAX,2282
INC EAX
DEC EDX
POP EDX
POP EAX
Since it is popping those registers off the stack, its actually altered nothing
Themida is a cow, Because my friend didnt manage to make a start on the junk code remover (and I didnt realise there was a virtualised function) I just did each Import by hand (approx 4 hours lol)
Also rebuilt the OEP by hand too, not too hard since it was VC++6.
I have a G4 which I have unlocked with Imei-Calc (thus I have the key file, which I *think* might decrypt parts of the program, or possibly is part of an encrypted rom.)
3 Last things:
1. Can the G3/G4 chip be worked out by IMEI, i.e IMEI represents a date and the chips were only used after a certain date? or is this tool generic for G3/G4 ?
2. Do you have an SPL for 2.08.10
3. How can I dump my SPL (bearing in mind my only minisd has a full backup of my rom, Just in case crossbow gets a little ugly for my liking)
Ohh one last thing, kbdus.dll on Crossbow.....Is there a kbduk.dll as far as you know?
My Wizard has british keyboard and all the chars are shifted +1.....
Thats my next major task I think before continuing on this thing
Btw, To use the usb logger on newer versions of IMEI-CALC, just rename the exe and change the class name

Hi..Answer on the "Last Three Things"
1.) No one cannot identify G3/G4 with imei.If u lok carefully the place below yr battery u will find a"G4" written besides yr imei no.In G3, nothing is written.The most commeon way is to check IPL/SPL .001 in the end is G4.
2) Take a ROM which has 2.08 SPL. and use typho5.exe to dismantle the ROM parts.If ROM is release recently then you will find IPL/SPL for G3/G4 both.Chek the threads here..
3) As such crossbow ROM has no IPL/SPL..if u know what ROM u were using prior to that, u can apply above to dump yr ipl SPL..secondly you can do this with awizard1.3 beta.
I hope this helps

BA Disconnects as Update Starts

Hi,
Apologies in advance if I'm covering old ground.
I'm trying to re-flash a WM6 rom after my previous attempt just left me with the 4 colour screen permanently and as the links to mtty1.42.rar seem to be broken at the moment I decided to re-flash with a different rom.
the problem is that even though I can get the unit into boot-loader mode and the update software appears to see the BA when it checks versions etc. as soon as I hit the upgrade button the BA screen blanks and I get Error 112: CE ROM UPDATE ERROR.
I've tried different roms, different usb ports and different versions of activesync all with the same result.
Any help on this would be great and hopefully I haven't 'bricked' the unit.
Cheers
Duncan

Do you have PH20A2 or PH20B device?
mtty utility can be found using search button

It's a PH20B.
I've now found mtty after a fair bit of searching on other forums..now to see if I can make some sense of it's commands.
A further update: it seems that I've managed to corrupt just the OS part of the ROM. I managed a radio update successfully which means all the USB connection is fine for updating. It just can't access the OS part of the ROM.
Is there anyway to manually format that area of ROM so I can in effect install over clean unit? Infortunately I can't make sense of the mtty commands and don't know what memory address and for how log I should perform the format.
Cheers Duncan

try reflashing

You should know how to use search - however here is the link
http://forum.xda-developers.com/showthread.php?t=348030&highlight=mtty
(Is that hard to put "mtty" in the search field and set BA section only? )

Further update:
Now I don't even get the 4 colour screen. After soft and hard reset I get a dead device. I can put the device into bootloader mode (serial/usb) but as soon as the update software attempts to copy the rom across the screen blanks and I get the ROM Update Error.
Now my thought is to try and flash with the original rom for the device as I have another unit available but using the link from the BA wiki for dumping the ROM doesn't work. I have also tried searching for 'ROM Dump' within the BA section of the forum but there don't seem to be any definitive instructions for this, everyone just keeps asking why not use the wiki or search funtion....
I have used the wiki and the search funstion and I seem to be the first with this situation.
Soft Reset - Nothing
Hard Reset - Nothing
Bootloader - Able to flash the radio rom but as sson as i try to flash the OS rom the screen blanks and I get Error 112: CE ROM Update Error. When I take the device out of the cradle the screen comes back on with the Serial 2.xx screen and I'm back to square one.
I've tried to use the wiki to dump an exisiting working rom but the link on the wiki is broken. I have also searched the BA forum for these intructions but they're not covered as they're already in the wiki..... or not as the case is.
I appreciate you regular users get fed up with noobs coming on and expexting you to do all the work for them but so far I've spent 3 days searching both this site and others to try and resurect my device. I'm not dumb or lazy and would love to be able to do all this myself but without instructions I'm flying somewhat blind.
Any help would be great..... please??

[off topic]
no need for apologies...
we started once like you... some are far worse...
knowing one part and boasting with air on their heads...
since you managed to explain yourself on your first post.
knowing what to search (E.G. MTTY 1.42.rar)
you definitely searched the forum before you posted AND
you stated that the links are not working... that proves it.
we are the one who is sorry because some others think
that they are high and mighty, it sometimes blurs the opinion making.
i dont like opinionated people because i admit that am one too... sometimes...
but that doesnt mean i hate them...
[on-topic]
you never told us what happened when you tried the mtty procedure.
is your last post the result of your mtty experience?
please elaborate how did you end up with that... what did you do before you soft-reset and hard-reset?

SilverSamurai,
Thanks for the quick response.
After my last 'apparently' successful re-flash with Helmi's latest WM6 rom when I hard reset the device I had nothing but a blank black screen, no power LED or anything. Soft-reset was the same. I can reset into bootloader and the PC detects the device when I place it in the cradle. The first part of the update seems to work although it never detects the current OS installed, it always says upgrade from ' ' to 'ver 6.0.0' which is wierd because it always used to say the previous OS version. When I then hit next the progress bar shows on the PC but the BA screen immediately blanks and eventually the PC gives the ROM update error.
I have managed to re-flash the radio rom in this state which proved that I still have access tho the device from the PC.
Using mtty I can run through all the commands to recover from the 4 colour lines screen (even though I'm beyond that point).
USB>set 14 0
HTCST ÚÈÒHTCEUSB>task 28
DOC_format_HW+
DOCInfoTableinitHW+
Binary0:dwSize=80000
BINFS0:dwSize=0
FAT0:dwSize=1000000
FAT1:dwSize=2BA0000
All:dwSize=3C20000
USB>task 0
USB>
It's almost as if the last flash didn't complete and has left the area for the OS 'dirty' with what ever it did manage to flash. What I was hoping to try was to re-format the entire OS section of memory and then try to re-flash again. Using mtty it says you can format sections of memory by stating a start address and the length you want to format but I don't have clue what these should be.
I've tried flashing with WM6, WM5 and a compatible version of 2003 with the same result every time. I would like to dump a rom from another BA I have and try with that but as mentioned earlier the link for that is down at the moment.
I think that's about it. If you need any more info let me know.
Many thanks
Duncan.

let's relist the things you did.
USB>set 14 0
Click to expand...
Click to collapse
1. start OS after a reset
result:
HTCST ÚÈÒHTCE
USB>task 28
Click to expand...
Click to collapse
2. format doc (Disc-On-Chip)
result:
DOC_format_HW+
DOCInfoTableinitHW+
Binary0:dwSize=80000
BINFS0:dwSize=0
FAT0:dwSize=1000000
FAT1:dwSize=2BA0000
All:dwSize=3C20000
USB>task 0
Click to expand...
Click to collapse
3. do hardware clear boot.
Click to expand...
Click to collapse
since i dont want to experiment with my sole BA...
i tried to search for solution...
and with some of my computer instincts i came up with this suggestion...
try this command before "task 28"
"task 7 0" <-- this is the "Do flash ROM lock/unlock" command
"task 2a" <-- fix bad blocks on MFG bootloader and Storage
then try to reflash your BA.
my sources one | two
although it's not BA but i think mtty commands are generic.
it's worth a try.

SS,
Still no joy, it's exactly as it was before.
Just reading through some more posts for bootloader ant it seems at least one other person has the same problem - http://forum.xda-developers.com/showthread.php?t=345181&highlight=bootloader and no resolution posted for that either.
I think I may have got it beyond the point of return.
I've just tried to flash from the blank screen I end up with from the initial attempt and it still detects the device but fails in exactly the same way.

awww... im sorry to hear that.
but dont lose hope.
i'll try to read some more and search for solutions.
and i hope someone with the same problem as
yours that had their BA fixed comes to the foreground.
[off topic]
hmm... come to think of it... we're both Marvel SuperVillains

SilverSamurai said:
awww... im sorry to hear that.
but dont lose hope.
i'll try to read some more and search for solutions.
and i hope someone with the same problem as
yours that had their BA fixed comes to the foreground.
[off topic]
hmm... come to think of it... we're both Marvel SuperVillains
Click to expand...
Click to collapse
These steps are from my notes. Follow these steps. It worked for me last time i tried (3 months back)
2. Stop ActiveSync, by Task Manager (press Ctrl + Alt + Delete)
kill two processes rapimgr.exe and wcescomm.exe
3. put your device into Bootloader Mode by pressing Power + Record Button and Soft Reset.
4. Run mtty (from downloaded) Choose WCEUSBSH001
5. type "set 14 0" without the quotes to tell bootloader to boot the OS after reset.
6. type "task 28" to get your device formatted
7. type "task 0" to ask your device reboot
8. take the device out of the cradle, and manually reset it if it does not do that already.

i think he did all of those already,
that's why i posted this in response to his mtty experience.
wouldnt hurt to try it again though.

A bit more info:
I tried the mtty solution again but still the same result.
I finally managed to find the instructions for dumping and exisiting rom to SD card and pulled one from a working unit. I put the card into the faulty BA and booted into bootloader. Pressed 'Power Button' to flash from card and it appeared it was going to work........ until it got to 12% then it failed with the message 'Download Fail'. So still no better off.
What I'm going to try now as it seems anything is worth a try is use the address ranges used to dump the rom to try and format all 3 sections. See if that will give me a clean base to try and re-flash from the sd card. My only worry is if it will format the section of ROM used to store the bootloader info.
I'll post my results shortly.

Now I need to know how to get the bootloader password to enable me to use the 'erase' command through mtty.
The hunt coninues....

Yet more developments.
As the update from SD failed I thought I'd see if it was possible to dump the current contents of the rom to SD using the following
“d2s 80000000 02000000“
“d2s 60000000 00300000 sd a“
“d2s 70000000 01080000 sd a“
The first 2 commands completed fine and checksum was OK. On the 3r command 'd2s 70000000 01080000 sd a' it errored with the following result
USB>d2s 70000000 01080000 sd a
SD:Waiting for card insert.........
CMD3 for SD, it's OK, ready to get RCA from response.
SDetected one card
SD:ready for transfer OK
pc->drive.total_lba=1E8000
pc->drive.num_heads=0
pc->drive.sec_p_track=0
pc->drive.num_cylinders=0
pc->drive.block_size=200
pc->drive.features=0
pc->drive.RCA=B368
pc->drive.drv_type=40000000
pc->drive.securedAreaSize=0
pc->drive.securityDrv=0
pc->drive.busWidth=1
pc->drive.erasedSize=0
Total card size=3D000000
DOCInfoTableinitHW+
Binary0:dwSize=80000
BINFS0:dwSize=0
FAT0:dwSize=1000000
FAT1:dwSize=2BA0000
All:dwSize=3C20000
DOC_ReadBinary is fail: dwStartAddress=0,dwReadSize=40000.
DOC_ReadBinary is fail: dwStartAddress=0,dwTempReadLength=40000.
*DOC_ReadBinary is fail: dwStartAddress=40000,dwTempReadLength=40000.
*****************************************************************dwCheckSum of Storage=95609D16
cSectionNum=2
psImageSectionInfo[cSectionNum].dwCheckSum=0
psImageSectionInfo[cSectionNum].dwLength=1080000
Stored image of SD/MMC card checksum error!
Now my guess is the Doc_Read_Fail bits are the corrupt part of the rom. If I can find a way to repair these I could then try re-flashing the rom.

what was "task 2a"'s result?
i think that's the chkdsk option of mtty.
we're dissecting the innards of the bootloader.
little by little as we go along the way...
im learning something, i hope you can find the fix for your problem.

SilverSamurai,
Thanks for the help you gave but the unit has finally had enough and totally locked. No power or anything no matter how I try to reset it. I've tried charging for hours, discharging for hours, left the battery out for hours but to no avail. It seemed to take exception to me dumping the rom contents to the SD card. Maybe there was a hardware problem ?? Not sure.
I'll have to see if I can wangle another unit from the company I work for as we're currently selling a bunch that were purchased for a failed IT project on ebay.

it was sad to hear/read that.
anyways. at least we tried to revive it. but dont throw it away.
maybe someday there will be ways how to ressurect your BA.
Happy Computing! err... Mobile Computing!

[GUIDE] ~~[★The Complete Leo Flashing Video Guide★]~~ [Update 14/03/10]

★Useful Links★​ Official HSPL Thread - Bepe [The Actual HardSPL]​ Written Flashing Guide -Mskip [The Best Written Guide Around]
Official Rom Thread -L3v5y[Get All The Offical Roms (And SPL's) Here!]​ Official Radio Thread -Kholk[Very Useful Collection Of Radios]​ Custom Rom Mirrors -zzattack[Useful For A Good List Of Roms With Links To The Original Threads+Fast Downloads]​MTTY Thread - MysticGenius [Bad Flash? Constant Hard Resets? Check Out This Thread From MG!]​
★I Appreciate Comments, So If This Thread Helped You At All, Or If You Have Some Constructive Criticism, Then Post A Reply Letting Me Know★
★Hopefully this compilation of videos
I've been working on for the last week
or so should help you in any of your
queries about using HardSPL. Its designed
for complete noobies which dont know the
first thing about flashing.★
★Once you've watched a few, you will begin to
learn the different acronyms and be able to
recognize certain words and phrases in the
flashing process, but for now, heres a short
word list to get you started.★
★[Word List]★
LEOIMG.nbh/ruu_signed.nbh/[Randomname.nbh] - These are all the actual roms, the things you need to flash, usually they are called one of the first two names, but some rom chefs give their own names to the roms, but you can always distiguish which file you need as it will always be a "nbh" file and will always be the largest file in the archive/folder
SPL - Secondary Program Loader: Loads the actual OS. (The SPL is what lets you flash the different aspects of your device, however the stock SPL is 'CID Locked' which means only official releases from HTC can be installed.
HSPL - A 'custom' SPL created by the dark forces team (bepe and cotulla), this is CID Unlocked and it lets you install custom roms and flash any radio. The reason it is called 'Hard' is because it stays on your device after a flash, unlike 'Soft' SPL which is removed after a flash.
RUU - The official 'Rom Update Utility' from HTC which is used to do all your flashing from your pc, its essentialy a nice user interface for the SPL
CustomRUU - The custom Rom Update Utility from the dark forces team which is designed to be used with the HSPL
ROM - An operating system build from HTC, updated to bring you the newest functions and fixes
Custom/Cooked ROM - An operating system build built on a stock rom, these are created by 'Chefs or Cooks' who use 'Kitchens' to design their own roms to release to the community, these are usually alot better than stock roms and contain lots of custom tweaks from others in the xda community.
[More knowleadgable members please correct me on things I may have got wrong/ used the wrong termonoligy]
[Disclaimer: I will not be held responsible for any damage that may be caused to your device, and be warned flashing HardSPL WILL void the warranty on your device, however it can be removed, thus unvoiding it]
Ok onto the videos!
[Note/Update: In one or more of my videos I say that this will not work locked phones (as in, bought in a contract) this is wrong, HSPL does allow you to flash new roms on to contract phones (for example: flash a custom rom onto a tmobile phone) However it will not unlock the deivce]
1. How To Install HardSPL
[LINK][Estimated Time:7 Minutes]
[NOTE: PLEASE GO INTO YOUR BOOTLOADER BEFORE INSTALLING HSPL AND MAKE SURE YOUR CURRENT SPL IS 1.42.0000, IF IT IS NOT, THE INSTILLATION WILL FAIL!]
Description: This video is intended to run you through the very simple process of flashing HardSPL to your device.
Useful Links
¬HardSPL Thread
HardSPL
¬Windows Mobile Device Center 6.1 32 Bit
¬Windows Mobile Device Center 6.1 64 Bit
2. How To Flash a Custom Rom Via Active Sync (USB)
[LINK][Estimated Time: 10 Minutes]
Description: This video is supposed to show you the process of flashing a custom rom to your device using the supplied standard mini usb cable.
Useful Links
¬Direct Links For Most Custom Roms
¬Windows Mobile Device Center 6.1 32 Bit
¬Windows Mobile Device Center 6.1 64 Bit
3. How To Flash a Custom Rom Via Micro SD Card
[LINK][Estimated Time: 15 Minutes]
Description: This video is supposed to show you the process of flashing a custom rom to your device using the supplied standard micro SD card.
Useful Links
¬Direct Links For Most Custom Roms
¬Windows Mobile Device Center 6.1 32 Bit
¬Windows Mobile Device Center 6.1 64 Bit
4. How To Flash a Stock Rom
[LINK][Estimated Time: 10 Minutes]
Description: This video will show you how to install a stock rom back to your device, so it is just like the day you got it.
Useful Links
¬Official Roms
[IMPORTANT NOTE: YOU CAN NOT INSTALL STOCK ROMS USING AN SD CARD AS IT WILL REMOVE HSPL]
5. How To Flash a Radio
[LINK][Estimated Time: 7 Minutes]
Description: This video is supposed to show you the process of flashing a stock radio to your device.
Useful Links
¬ Radios
6. How To Uninstall HardSPL (Install a Stock SPL)
[LINK][Estimated Time: 25 Minutes]
Description: This video is the longest and is supposed to show you how to remove HardSPL from your device (usually done when sending the phone in for warranty)
Useful Links
¬Official Roms (For Stock SPL's)
WARNING: THIS WILL REMOVE YOUR CURRENT ROM AND INSTALL A STOCK ROM OVER IT
7. How To Flash(Install) A Custom Splash Screen (Thanks jeckyll for the first splash screen and teaching me how to do it)
[LINK][Estimated Time: 5 Minutes]
Description: This video is very quick and will show you how to install custom splash screens (the initial SS with the htc logo and white background)
Useful Links
¬HD2 Bios Splash Screens
¬How To Create A Custom Splash Screen (Thanks pof)
8. How To Flash(Install) A Stock Splash Screen (Uninstall Custom Spash Screen) (Thanks 6Fg8 For The Stock Splash Screen)
[LINK] [Estimated Time: 5 Minutes]
Description: This video is very quick and will show you how to install the original splash screen (the initial SS with the htc logo and white background) over your custom one (will get back warranty)
Useful Links
¬HTC HD2 Original Splash Screen (Thanks 6Fg8)
9. How To Perform A Task 29 Without MTTY(Thanks Doloop For Making This, and ShaDrac for repacking it into an easier single exe)
[LINK][Estimated Time: 7 Minutes]
Description: This video will teach you how to perform a task 29 on your Leo without having to go through the arduous process of installing all the drivers ect for MTTY. Task 29 formats your phone for a cleaner flash
Useful Links
¬Task 29 Thread
¬MTTY Thread (For Reference)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[REQUEST: IF ANY OF YOU GUYS KNOW HOW TO GET EMBEDDED VIDEOS WORKING ON THESE (VBULLETIN POWERED) BOARDS, SEND ME A PM OR POST A REPLY EXPLAINING HOW, I WOULD BE SO GREATFUL
[NOTE: YOU MAY LINK TO THESE VIDEOS AND USE THEM ANYWHERE WHERE THEY WILL HELP A FELLOW LEO USER OUT JUST BE SURE TO PROVIDE A LINK BACK TO THIS THREAD]
If Any Video Links Are Down/ Do Not Appear In Your Country, Post A Message In This Thread And I Will Try And Have It Up ASAP
(Stickied 26/1/10) Thanks
Recieved Donations [/COLOR][/U]
Turborider - 14/03/10 (Thankyou Very Much )

Top Tips, Useful Things & F.A.Q's!
For The REALLY Lazy Man - A Folder Which Already Contains The CustomRUU,
Just Drag And Drop Your Rom File (.nbh) In Here And Run The CustomRUU! **Download** (Extract The Folder From The Zip File)
Making any changes to your phone using HSPL WILL void your warranty, and even if you remove HSPL and, for example, you have a custom rom still on your phone, your warranty will be void. However you can revert anything you do with HSPL thus getting back your warranty, I will make sure each method is on this thread, just make sure to revert everything changed with HSPL before you remove it.
Can I flash backwards? as in - From 1.61 to 1.48. Yes you can, you can flash any rom to any other rom with HSPL (thanks mskip for filling me in )
Always back up your phone. I recomend SPB Backup, it can backup not only contacts, but your whole system (programs, reg tweaks ect) however you may encounter problems if you try to restore everything, because the backup may have been made on a different version of manila/windows mobile
Hard resetting after a flash is usually recomended, it will optimize the rom
Always bare in mind the 2 main different manila versions (2.5.XXXX), 1921 and 1922. 1921 is the older one and so has more mods and tweaks designed specifically for it. 1922 is the newest and not yet totally stable version which doesnt support much yet, (however patchs and updates are starting to surface such as one for HDWall and 25 Shortcuts
If you are getting good signal ect with your current rom, make sure you take note of the radio version, it may be a good idea to back your old radio after flashing a rom if signal is not as good
Usually you will not have to reapply HTC hotfixes as most cooked roms include them in the package, however make sure there arent any recent updates which may not have been cooked in.
Side Note: All camera tweaks from xda users are usually pre cooked in aswell. (Talk about instant meals!)
¬More To Come Over Time

~~~[★Useful Pictures★]~~~​
[Taking requests]
A Healthy HSPL'ed Bootloader​

well done mate this thread will help alot of plp,nice one

[QUOTE='[★]
3. How To Flash a Custom Rom Via Micro SD Card
[LINK][Estimated Time: 15 Minutes]
Description: This video is supposed to show you the process of flashing a custom rom to your device using the supplied standard micro SD card.
[/QUOTE]
Hi,
Nice work, but i dont agree with this video.
you DO NOT have to format the SD card every time you flash.
you just copy it over and and start the flash!
Nice vids though, just abit misleading! and to be honest takes a long time, I have 4Gb of data on an 8Gb card, for me to copy it off, format, flash and copy it back would take the best part of 90 mins!!
SS

SiliconSquirrel said:
Hi,
Nice work, but i dont agree with this video.
you DO NOT have to format the SD card every time you flash.
you just copy it over and and start the flash!
Nice vids though, just abit misleading! and to be honest takes a long time, I have 4Gb of data on an 8Gb card, for me to copy it off, format, flash and copy it back would take the best part of 90 mins!!
SS
Click to expand...
Click to collapse
Huh.. It takes me with my 16gb one about 5 seconds to quick format once Ive dragged things off, Ive heard it is a safe bet so Im gonna leave it like that unless loads moer people feel the same way, Thanks though

To the OP,
Well done for putting these videos up. Should help a few people to better visualise what they need to do.
@ Silicon Squirrel,
You may be right re your point on formatting but I see it as good practice as it forces people to double check that the card is formatted in FAT 32 (a common problem).
WB

wacky.banana said:
To the OP,
Well done for putting these videos up. Should help a few people to better visualise what they need to do.
@ Silicon Squirrel,
You may be right re your point on formatting but I see it as good practice as it forces people to double check that the card is formatted in FAT 32 (a common problem).
WB
Click to expand...
Click to collapse
Thanks And yeah thats a good point

wacky.banana said:
@ Silicon Squirrel,
You may be right re your point on formatting but I see it as good practice as it forces people to double check that the card is formatted in FAT 32 (a common problem).
WB
Click to expand...
Click to collapse
Ok, but once you have done in once you dont need to do it again!! the card doesnt just randomly change file system while in use!!
so yeah i agree format it ONCE the first time you do it, other than that it is a waste of time!
I have never in 15 years of using computers and flash memory EVER heard of that!
SS

[★] said:
Huh.. It takes me with my 16gb one about 5 seconds to quick format once Ive dragged things off, Ive heard it is a safe bet so Im gonna leave it like that unless loads moer people feel the same way, Thanks though
Click to expand...
Click to collapse
Dont get me wrong, it was a constructive criticism.
maybe you could note the fact that they only need to do it once, the first time, to make sure the file system is FAT32. then they would save much time in the future!
Also i wasnt saying the format would be long, i was meaning the copying on and off that is a ball ache!!
SS

SiliconSquirrel said:
Dont get me wrong, it was a constructive criticism.
maybe you could note the fact that they only need to do it once, the first time, to make sure the file system is FAT32. then they would save much time in the future!
Also i wasnt saying the format would be long, i was meaning the copying on and off that is a ball ache!!
SS
Click to expand...
Click to collapse
thats true, it IS a ball ache xD

Good vids and just to echo an above post that seeing it being done makes it so very simple and thanks very much, it certainly helps new people like myself get to grips quickly.
I'd just add in a couple of vids you might want to add a bubble of 'connect via active sync'
About the format thing, meh!.. you get a 2gig card with the phone which is useless really except for rom stuff and the like. I wouldn't bother moving stuff around, just swap the card over.
cheers!
R.

humungousfungusamongus said:
Good vids and just to echo an above post that seeing it being done makes it so very simple and thanks very much, it certainly helps new people like myself get to grips quickly.
I'd just add in a couple of vids you might want to add a bubble of 'connect via active sync'
About the format thing, meh!.. you get a 2gig card with the phone which is useless really except for rom stuff and the like. I wouldn't bother moving stuff around, just swap the card over.
cheers!
R.
Click to expand...
Click to collapse
Ok I'll get on that soon,
And yeah, I just use the 2gb one that comes with it too

Very helpful and clear videos

Thanks alot you just helped a noob here thanks

I think that this thread deserves a sticky.

Yep i vote for sticky aswell. admins please sticky this extremely helpful thread

gsingh7 said:
Yep i vote for sticky aswell. admins please sticky this extremely helpful thread
Click to expand...
Click to collapse
Fatherboard said:
I think that this thread deserves a sticky.
Click to expand...
Click to collapse
Thanks
Glad it helped
Most of the thanks should go to mysticgenius and mskip for teaching me though

[★] said:
Most of the thanks should go to mysticgenius and mskip for teaching me though
Click to expand...
Click to collapse
Whoop +1 for MG!!
although, you put the work in on this thread, and the vids are cool so you deserve credit too!!
Peace bro
SS

Thanks man

[REF] Help for Bricked Phones - TG01 Users, Be Aware!

Flashing different custom ROMs, some of us, sooner or later, are meeting ONE TERRIBLE PROBLEM - device getting bricked... Unfortunately, might happend...
With new developments of feropont we are getting, finally, updated (in the meaning of ballanced and smooth "relationship" between hardware and software) device. He, certanly, done jobs, Toshiba supposed to do before releasing the device.
... And it is real pain - inability to enjoy using such improved device...
As a members of xda-developers community, we become pretty skillsful resolving different problems - we have huge support over here - this is one of the reasons for opening this thread - to get help, and help others. Again - everyone of us can meet the problem.
I am a hard user of Windows Mobile from early years when Dell Axim just came to public. TG01 - my last device, in which I found full functional Pocket PC and pretty developed cell phone - all in one , and with my accurate attitude in using my "toy" I did not expect to fall victim of software glitch... But it happened!
My particular problem is really unusual – I cannot flash ANY custom made ROM (even earliest – see pere’s ROM table), But I am ABLE to flash any official ROM (!?)
We discussed the problem with feropont, he found it pretty unusual - I am inviting you to open discussion here, in one place, related to most common problems TG01 Users can meet… and hope, I'll find solution for my problem, as well.
Following, I would like to provide with links to previous answers to came across problems – all about TG01. (send me links – you consider helpful – will post them here in a first page).
Two brick variants from mirolg
Short Pins Illustration from kevinpwhite
TG01 Downloader TG01 Driver TGTool contains TG Tool
Smart Quote:
fxdjacentyfxd said:
1) always check .tsw file in prg directory via tgtool.exe software
2) from time to time I execute chkdsk utility to check SD card.
Only after point 1) and 2) I start sdll+ uploader.
Regards
fxdjacentyfxd
Click to expand...
Click to collapse
Another try...
Pere's TG01 Cooked ROMS' Table

eskyt said:
My particular problem is really unusual – I cannot flash ANY custom made ROM (even earliest – see pere’s ROM table), But I am ABLE to flash any official ROM (!?)
We discussed the problem with feropont, he found it pretty unusual - I am inviting you to open discussion here, in one place, related to most common problems TG01 Users can meet… and hope, I'll find solution for my problem, as well.
Click to expand...
Click to collapse
Hi.
What method of flashing You used to utlize ?
I can confirm only that using 3-pin metods ( as always I say - absolutely do not use this method if You really do not have to. ) should be involved only for official roms . Someone will say not true. I say I had always problems to flash custom roms utilizing this method so always, I repeat always, flash only any official rom this way. Never have had any problems with official roms but always problems with custom roms including "terrible" messages like "NAND flash error". Maybe flashing custom roms this method cause such big problems in the future ? It seems to be service mode not normal flashing mode so who knows what wrong can wait for us if rom is not official.
Anyway utilizing sdll+ software seems to be ok both for official and custom roms.
I have not had any slightest problem with it.
Sometimes people are gilty themselves. Flash strange custem roms with God knows where custom bootloaders and it is enough. For example, Nokser has bricked His tg01 and only JTAG can help him. Too much experiments with unknown matter and disaster is ready. Many people tried His last rom and who knows whether they are next candidactes to have unresolved problems with their tg01s.
Regards
fxdjacentyfxd

Flashing any device always has a risk attached, whether that be a Toshiba TG01 or a pc motherboard bios, still as long as procedures for flashing are followed correctly nobody should have many problems, but obviously bad things can happen, how many motherboards have died on a bios flash for example?
Flashing TG01 is no more risky than flashing other devices, however what you flash it with is the area where risk becomes involved.

I think what is needed is a tool for HTC devices called 'task 29' basically when we flasg custom ROMs over and over again, some roms are bigger than others etc, so they dont overwrite all system files, therefore, old system files from the previous ROM is left in the new ROM. this corrupts the phone, therefore you expeirience bugs. We need a tool like task 29.
but personally i dont/ havent faced any of these problems... *touch wood*

Thank yo guys!
To fxdjacentyfxd - thank you for sharing thougts.
I am exactly an example of "next candidacte" - I always was extremly carefull and used sdll+ only. I even did not know how to use3 pin method (feropont, many thanks him, instructed me).
I guess, (really just guess), my problem came from corrupted .tsw file - you know, we can see full sized file on memory card, when (factually) copying process was interrupted...
This is the riddle - what "changed" in the boot area, that compel my device to accept officials ROMs only (and only through 3 pin method), when customs (through sdll+) stopping it on Toshiba logo...
To olyloh6696 - yes, feropont had mentioned this future in privet correspondence - would be good to have it!
To (InsertNameHere) - "obviously bad things can happen" - supposed to be motto of this thread

eskyt said:
To fxdjacentyfxd - thank you for sharing thougts.
I am exactly an example of "next candidacte" - I always was extremly carefull and used sdll+ only. I even did not know how to use3 pin method (feropont, many thanks him, instructed me).
I guess, (really just guess), my problem came from corrupted .tsw file - you know, we can see full sized file on memory card, when (factually) copying process was interrupted...
This is the riddle - what "changed" in the boot area, that compel my device to accept officials ROMs only (and only through 3 pin method), when customs (through sdll+) stopping it on Toshiba logo...
Click to expand...
Click to collapse
Accordingly to what You wrote about corrupted .tsw file I forgot to mention that after every copy of new .tsw to prg directory on SD card I :
1) always check .tsw file in prg directory via tgtool.exe software
2) from time to time I execute chkdsk utility to check SD card.
Only after point 1) and 2) I start sdll+ uploader.
Regards
fxdjacentyfxd

fxdjacentyfxd said:
B] always [/B] check .tsw file in prg directory via tgtool.exe software
Click to expand...
Click to collapse
That is smart! Did not know it before. Hope, other users will take it into consideration...

eskyt said:
That is smart! Did not know it before. Hope, other user will take it into consideration...
Click to expand...
Click to collapse
Reading posts about bricked tg01s I got to conclusion that some bricks were really becuase of corrupted .tsw or logical errors on SD card. So I have always thought it is worthy to waste 1 minute to check .tsw in prg directory than irreversibly bricked tg01.
P.S. Your case is really very, very strange. To "damage" bootloader it accepts only official roms.... I can not belive in it. Must be other explanation.
Regards
fxdjacentyfxd

fxdjacentyfxd said:
Must be other explanation.
Click to expand...
Click to collapse
... - and I am trying to find solution...

i agree with olyloh6696's opinions
when we flashed roms so many times,maybe our phone's NAND flash appear some bad blocks.it's really like the problems in HTC phones.
Maybe use Tgdownloader flash an Official rom will helpfull with this problem.
Anyway,when we cook roms,tgtool always check if there's any error in our custom rom,and we just make changes in OS partition,didn't change/edit anything with the Bootloader or Radio.So i must say the most possibility that brickes our phone should be the Flashing Progress.

eskyt said:
This is the riddle - what "changed" in the boot area, that compel my device to accept officials ROMs only (and only through 3 pin method), when customs (through sdll+) stopping it on Toshiba logo...
Click to expand...
Click to collapse
It is similar I wrote in my first post. Typically ( I am not going to check more ) I am not able to flash rom via 3-pin method if rom is not official. It seems I have always had this feature. I had maybe free "bricks" since I have tg01 , because of my experiments with drivers and so that to flash any good rom via 3-pin it had to be always official rom ! Fortunately sdl++ works fine for any rom.
Did You flash many custom roms ? Maybe one of them is "this one" and it is worthy to find out which it is.
On the other hand as I remember tgdownloader has feature to upload different areas of the rom separately ( boot area too ).
Maybe someone brave could upload this method boot area ? If it works You could upload Your boot area too.
I know, it is hardcore
Regards
fxdjacentyfxd

ffboy2009 said:
i agree with olyloh6696's opinions
when we flashed roms so many times,maybe our phone's NAND flash appear some bad blocks.it's really like the problems in HTC phones.
Maybe use Tgdownloader flash an Official rom will helpfull with this problem.
Anyway,when we cook roms,tgtool always check if there's any error in our custom rom,and we just make changes in OS partition,didn't change/edit anything with the Bootloader or Radio.So i must say the most possibility that brickes our phone should be the Flashing Progress.
Click to expand...
Click to collapse
yes, as no tool exist, the best method for us is for every ROM flash:
1) Hard Reset Current ROM
2) Flash Stock ROM
3) Hard Reset Stock ROM
4) Flash New ROM
5) Hard Reset
You could even go as far as Reflashing the same ROM over the same ROM again to eliminate further errors.
This is the recommended precedure to follow, however I usaully miss out steps 1,2,3.

My bootloader is dead and i don't have a solution...
Maybe one... bay Riff Box

Nokser said:
My bootloader is dead and i don't have a solution...
Maybe one... bay Riff Box
Click to expand...
Click to collapse
Well, I remember wonderfull times when any bootloaders were in OTP ROM or EPROM. None possibility to "kill" the device. Today is to be cheap, easy, universal and we pay for it.
Regards
fxdjacentyfxd

fxdjacentyfxd said:
Today is to be cheap, easy, universal and we pay for it.
Click to expand...
Click to collapse
...So true.
By explanation of feropont official ROM supposed to "zap" like kind of bad blocs in a flash memory (if any exist...), but, as we can see on my example Toshiba is "writing" every thing above of exist information without "cleaning" inside flash like task29 HTC is doing... He also mentioned that problems, mostly, becoming not in a boot area, but later, on the level of (qoute) "kernel initialization, xip..." - I am not prepared enough technically to discuss this llevel, but it is seems for me like I will stay with Malaysian ROM for ever...

eskyt said:
...So true.
By explanation of feropont official ROM supposed to "zap" like kind of bad blocs in a flash memory (if any exist...), but, as we can see on my example Toshiba is "writing" every thing above of exist information without "cleaning" inside flash like task29 HTC is doing... He also mentioned that problems, mostly, becoming not in a boot area, but later, on the level of (qoute) "kernel initialization, xip..." - I am not prepared enough technically to discuss this llevel, but it is seems for me like I will stay with Malaysian ROM for ever...
Click to expand...
Click to collapse
The main trouble is that the TG01 really does not make a general cleaning of flash Task 29 by analogy HTC devices. Judging from the descriptions of problems, bootloader is absolutely not damaged, it allows you to upload the whole flash ROM is not just any official ROM. The problems begin during kernel initialization XIP at the first boot device on any custom ROM. Every chef in the community TG01 anyway does not collect the full XIP, all cut-ins debuggers and encryption (kd.dll hd.dll mencfilt and etc). Unfortunately I have no time but first and foremost I would like to cook a custom ROM with the full original XIP, that would finally remove the issues in which there were bad blocks of flash in the kernel XIP or OS.nb.
Thx

feropont said:
The main trouble is that the TG01 really does not make a general cleaning of flash Task 29 by analogy HTC devices. Judging from the descriptions of problems, bootloader is absolutely not damaged, it allows you to upload the whole flash ROM is not just any official ROM. The problems begin during kernel initialization XIP at the first boot device on any custom ROM. Every chef in the community TG01 anyway does not collect the full XIP, all cut-ins debuggers and encryption (kd.dll hd.dll mencfilt and etc). Unfortunately I have no time but first and foremost I would like to cook a custom ROM with the full original XIP, that would finally remove the issues in which there were bad blocks of flash in the kernel XIP or OS.nb.
Thx
Click to expand...
Click to collapse
Thanks feropont.
Very interesting. You mean that if I cook my rom not removing any .dll from original XIP I will have more "safe" rom. Have any of mentioned dll's like for debug any influence on rom speed ( can be switched on-off after flashing ) ?
Bootloder part seems to be possible be overwritten too in some cases. Example, Noksers works.
Regards
fxdjacentyfxd

fxdjacentyfxd said:
Thanks feropont.
Bootloder part seems to be possible be overwritten too in some cases. Example, Noksers works.
Regards
fxdjacentyfxd
Click to expand...
Click to collapse
Unfortunately I can disappoint you, this is not an example of a new bootloader, and the result work of a new OEM, in particular, changed the entrance to the bootloader. Bootloader by definition can not be in OS.nb, he placed in the common part of the file .TSW who all mistakenly called RADIO, and if elementary compared Hex, the differences are almost no. Located in the very first sectors and is called MIBIB_BOOT.
Code:
*** MIBIB_BOOT Region Info ***
Region 0: "MIBI " start: 0 size: 80 r-size: 32 Ver: 0x0000 SubVer: 0x0000
Region 1: "SIM_ " start: 80 size: 48 r-size: 0 Ver: 0x0000 SubVer: 0x0000
Region 2: "FSBL " start: 128 size: 32 r-size: 24 Ver: 0x0000 SubVer: 0x0000
Region 3: "OSBL " start: 160 size: 32 r-size: 24 Ver: 0x0000 SubVer: 0x0000
Thx

feropont said:
Unfortunately I can disappoint you, this is not an example of a new bootloader, and the result work of a new OEM, in particular, changed the entrance to the bootloader. Bootloader by definition can not be in OS.nb, he placed in the common part of the file .TSW who all mistakenly called RADIO, and if elementary compared Hex, the differences are almost no. Located in the very first sectors and is called MIBIB_BOOT.
Click to expand...
Click to collapse
I have always thought , this device starts as typical ( known from microprocessors equpipped with boot section ) always from bootloader part but other circumstances decides whether after power up bootloder:
1) boot the system and "jump" to it
2) do other action like flash upload - check 3-pin condition or condition forced by sdll+ software
That is why I do not understand why Nokser can have completely dead device and not damaged bootloader.
Regards
fxdjacentyfxd

Since moving to Android I noticed most roms come with an md5 to check against the downloaded copy before flashing, just in case there is any corruption. Maybe a good idea to take a similar approach with tg01 roms.
I don't own my th anymore but flashed it in excess of 100 times using both sddl+ and 3 pins and never had any problems.
Sent from my Desire HD using XDA App