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
Related
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
★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
Hi,
My name is Wen from WMPoweruser and we recently decided to take up your case and try our best and get a ROM for the TG01. At the current status the chances of the TG01 getting a cooked ROM is currently low because the lack of a HardSPL, but I got word of another method of flashing.
EDIT: I3v5y is working on it, and soon enough we will have enough for his test device, and the ROM status is currently unknown, just doing some research as to if we can move some things around and tweak it to get a result. He is a professional at that.
Total $250.... We have enough for a UK TG01
Status
Unlocker/Flasher:Searching for a method of unlocking.. with the help of some people and Flar
ROM:We have more than enough cooks for that sadly only one in the UKThanks,
Wen
Hi wen, i'm very glad to hear this news you are giving us.
TG01 users will be very excited and happy when the custom works on the TG01
i don't mind donating to help the TG01 be able to have custom roms on it.
Also is it possible to hardspl the TG01 like you can hardspl the xperia x1 (my old phone)
Thanks, sam
sagam12 said:
Hi wen, i'm very glad to hear this news you are giving us.
TG01 users will be very excited and happy when the custom works on the TG01
i don't mind donating to help the TG01 be able to have custom roms on it.
Also is it possible to hardspl the TG01 like you can hardspl the xperia x1 (my old phone)
Thanks, sam
Click to expand...
Click to collapse
Thats is what I am trying to find, and is what our biggest problem is
There is a method to push the rom flashing using the pins beside sim card holder.
Read here:
FINALLY!! there is a way to ressurect dead TG01's after flashing:
1. Format SD card (FAT32)
2. Copy SDDL+.exe(not sure if it's needed)
3. Copy whole PRG folder with desired .tsw update (i think best will be the one dedicated to your language version
4. under sim card slot you'll find black plastic sticker (little bit hard to remove)
5. after removal of plastic sticker there are 3 pins
6. put battery back turn phone on
7. shorten 1 and 3 pin with cable and push reset button
8. white screen should come up and bootloader will load rom from your SD
9. Voila! Your TG01 is alive
tested by 2 spanish TG01 users and by polish TG01 user.
In case I'm not responsible for any damage you make by trying this method.
Hi Wen,
Custom ROM can be possible.The rom is decrypted by cotulla, but the resultant .nb0 has a wiered structure.It is still has some extra bytes, which has a weired parition table.Working on it as how to normalise.Hex copy paste also doesnt work properly.If this is done, then I am risking my tg01 for custom rom development.
Wen(WM) said:
Hi,
My name is Wen from WMPoweruser and we recently decided to take up your case and try our best and get a ROM for the TG01. At the current status the chances of the TG01 getting a cooked ROM is currently low because the lack of a HardSPL, but I got word of another method of flashing.
I want to get all the current information about ROMz for the TG01 like HardSPL status, Cooks, Dumps and anything else that could help us get this ROM started and cooking. We currently have 8 cooks at hand and if we can get some help getting a HardSPL or anything going, we can have a good ROM released fast from someone like NRG, Shadowline, Ark, Captain Throwback or any of our good cooks, but they do need a test device. So if anyone wants to donate let me know so I will add a Cotton, but I am sure no one does.
Thanks, and I hope we get cooking soon
Wen
Click to expand...
Click to collapse
Hi Wen,
I think there is no need to create HardSPL for TG01. Protection of TG01 is half-broken.
First, we've got program called ".TSW Tools", that helps to decrypt encoded .TSW image file. You can get the software here: http://cotulla.pp.ru/Misc.html
Second, when we have .bin image, we need to decrypt it.
@Globalbus form forum.pdaclub.pl told us something about the .bin:
1. The block of image that could be intresting begins at 0x50F4000 and goes to the end.
2. MBR tells us the following arrangement: ULDR, XIP, IMGFS, FAT (with initiation sector)
3. Checksums:
Every 0x200 bites some trash (0xFF)
Every 0x200 bites some checksum (CRC32?)
And NAND control blocks.
I translated it the best i could. I hope, that I helped you.
Come on, everybody with expert knowledge get it on now, i will donate..
get this started
RE
kosiek said:
Hi Wen,
I think there is no need to create HardSPL for TG01. Protection of TG01 is half-broken.
First, we've got program called ".TSW Tools", that helps to decrypt encoded .TSW image file. You can get the software here: ...
Second, when we have .bin image, we need to decrypt it.
@Globalbus form forum.pdaclub.pl told us something about the .bin:
1. The block of image that could be intresting begins at 0x50F4000 and goes to the end.
2. MBR tells us the following arrangement: ULDR, XIP, IMGFS, FAT (with initiation sector)
3. Checksums:
Every 0x200 bites some trash (0xFF)
Every 0x200 bites some checksum (CRC32?)
And NAND control blocks.
I translated it the best i could. I hope, that I helped you.
Click to expand...
Click to collapse
WOW this sounds good even though i don't understand half of it lol
also, wen i've donated $5 hope it helps, only small but i don't even work so sorry can't be more than $5
Good luck!
So here is a resume of all work made by TG01 user or not:
1- Dump OEM/SYS TG01 (by ABM30) =
http://forum.xda-developers.com/showpost.php?p=5500122&postcount=253
2- Tool to extract file from .TSW (by cotulla) =
http://cotulla.pp.ru/Misc.html
Quote:
we can decode tsw files to bin but TG01 bin differs little bit from standard bin images here is what an experienced cook said:
The important to us part of image starts 0x50F4000 till endof
MBR looks:
-ULDR, XIP, IMGFS, FAT (with initiation fragment)
Checksums:
every 0x200 bajts (0xFF)
every 0x200 bajts checksum (CRC32?)
And standard NAND control blocks.
3- Force bootloader to flash any official rom after wrong flash (by nico101)=
http://forum.xda-developers.com/showpost.php?p=5487567&postcount=245
i have my own sim unlocked TG01 that i am also will to donate for testing purposes if needs be.
but i would like it back and hopefully not bricked either, but we apparently have debricking instructions!!
come on cooks lets get cooking!!!
And the ball is rolling Will be donating as soon as payday hits
I can provide Wm6.5 O2 21856 DE dump and rare WM 6.1 PL (wasn't relased officially it's from show off phone for polish orange
We have I3v5y working on the ROM and we he says it should not be too hard, so lets just hope and he is going to need a test device
Very good news.
Thank you so much!
Fantastic news Thankyou very much!!!!!
well so far I have 20 and the device is 450 and I guess if we are close, I will take over the rest, also the flash method is the one that you guys said, so ya.
Wen(WM) said:
We have I3v5y working on the ROM and we he says it should not be too hard, so lets just hope and he is going to need a test device
Click to expand...
Click to collapse
Thats Good News
so good
It is a fantastic news really and thx to Wen, I hope the ROM will be release very soon.
And my device is a japanese version, hoping the unlock method.
Wen(WM) said:
well so far I have 20 and the device is 450 and I guess if we are close, I will take over the rest, also the flash method is the one that you guys said, so ya.
Click to expand...
Click to collapse
Don't panic it will come.
I plan to pay 50e but i forget my account paypal since longtime.
I just need to active it.
I have $110 so far, so 1/3 of the way there.
The SMT5600 is app unlocked and, I think, Super CID (via lokiwiz02_173 but how verify?) but no ROM changes as of yet as I want to make a backup of the original ROM before proceeding further.
After problems getting a term program to work (now using nueTTYConsole on Vista) I am able to get what appear to be complete ROM backups.
Procedure summary:
WinHex zero fill 64MB SD
USB bootloader SMT5600 with 64MB SD
r2sd all (via nueTTYConsole-12-v0.1-spackr)
SD back to PC [no to format query]
psdread E: 0 31328768 ipl.bin (using itsutl050119)
Status messages from the r2sd all command appear to be good and complete but no two backups, using the exact same procedure, are ever identical when binary compared with WinMerge. Size is, of course, the same but WinMerge always reports 'two' differences in what seems to be the same general area of the images: The first is very near the front of the image (WinMerge reports as 'lines', line 3) and the other at the very tail end.
Is that normal (maybe because TIME, or some other dynamic variable, changes or scratch storage?), is there a better backup procedure, and how can I verify the backups are good before I flash a new one and forever lose the original?
Thanks in advance for any enlightenment offered.
To check if it works - just restore the backups before doing anything else.
Follow the whole procedure (including psdread and - after reformatting the card - psdwrite again) to restore your device via the card. As a first try leave out the device external activities and restore immediately afterwards from the card just written.
For me it works well (on the SDA 2 - where no official update exists, a Hurricane device - but this generic handling is identical afaik) and the difference in the backups are normal.
Mind that the size of the read/write to card includes the bootsector, so don't miss the last 512 bytes. As far I remember there were two different size readings with two methods to verify the image size. The r2sd size is smaller than the size of bytes different to null on card.
To check for SuperCID enter "info 2" in the terminalprogram, it should report HTCSuperCID at the end.
tobbbie said:
To check if it works - just restore the backups before doing anything else.
Follow the whole procedure (including psdread and - after reformatting the card - psdwrite again) to restore your device via the card. As a first try leave out the device external activities and restore immediately afterwards from the card just written.
Click to expand...
Click to collapse
Thanks for the reply
Yes, I thought about doing a test restore, but, considering the problems I'd already had, wasn't sure if it might do something like not mention there being a 'problem' till it was half way through, leaving me with a scrambled ROM.
I take it you're saying it'll checksum first and no even start if things don't look good?
tobbbie said:
For me it works well (on the SDA 2 - where no official update exists, a Hurricane device - but this generic handling is identical afaik) and the difference in the backups are normal.
Mind that the size of the read/write to card includes the bootsector, so don't miss the last 512 bytes. As far I remember there were two different size readings with two methods to verify the image size. The r2sd size is smaller than the size of bytes different to null on card.
Click to expand...
Click to collapse
Hmm. I saw the confusion about SMT5600 image size but I'm not sure what you're saying here about the bootsector and "different to null."
Speaking of which, what would be wrong with just making a 64M save and, ok, you've save a pile of extraneous 0's along with it but, so what? Might be irritating if I were putting it on rapidshare but for a personal backup is there any down side to it?
tobbbie said:
To check for SuperCID enter "info 2" in the terminalprogram, it should report HTCSuperCID at the end.
Click to expand...
Click to collapse
Thanks. Good to know.
Something apparently went wrong somewhere because I didn't get that report but I'll try again.
The r2sd is a command that HTC has implemented in the SPL (Secondary Program Loader). I am not aware of checksums or other safety measures - it will as I noticed following the procedure detect if there is an image on the card, which type of image and if you want to restore.
The difference in size is that r2sd reports one size "x" after the image was taken, but if you count the bytes until when the card shows the zeros you will notice that this offset on card is 512 bytes larger than the r2sd reported size. So when using psdread you have to take the larger size. Indeed it is no problem to write more to the file and restore more as well with psdwrite. The restore procedure in the SPL will anyway know how much to restore - it just needs to find ALL bytes, including the last 512
I think there is no risk attached to the procedure, go ahead!
The only danger is if something goes wrong with the IPL (Initial Program Loader) or SPL because they open the door to the device handling.
Sadly you MUST deal with SPL to upgrade to WM5+ afaik, so be very sure to select the right IPL and SPL that matches your device HW (OMAP 730, 750 or 850) and intended OS Version. Also take care not to enter any command in the SPL except the ones you are supposed to enter - it may kill your device as well. Do never use "format all" or "doctest" - you have a brick then.
tobbbie said:
The r2sd is a command that HTC has implemented in the SPL (Secondary Program Loader). I am not aware of checksums or other safety measures - it will as I noticed following the procedure detect if there is an image on the card, which type of image and if you want to restore.
Click to expand...
Click to collapse
Well, I am certainly no expert on this thing but r2sd spits out a wealth of information, including checksums, and I was sort of guessing based on what I'd do if I'd made it. Just that, if you're going to calculate them, it seems a shame to not use them. But, hey, I've seen stranger things done.
tobbbie said:
The difference in size is that r2sd reports one size "x" after the image was taken, but if you count the bytes until when the card shows the zeros you will notice that this offset on card is 512 bytes larger than the r2sd reported size. So when using psdread you have to take the larger size. Indeed it is no problem to write more to the file and restore more as well with psdwrite. The restore procedure in the SPL will anyway know how much to restore - it just needs to find ALL bytes, including the last 512
Click to expand...
Click to collapse
Oh, OK. I wasn't going by r2sd. I opened it up in WinHex, found the end of data, and compared that to the size mentioned on "Backup your Typhoon ROM - WinMo @ MoDaCo." The 'corrected' number there matched well enough.
But now that I think of it, I did that because I *did* look at r2sd and it seemed too small. So you've explained it. Good.
tobbbie said:
I think there is no risk attached to the procedure, go ahead!
Click to expand...
Click to collapse
How can there be no risk if it doesn't check anything?
tobbbie said:
The only danger is if something goes wrong with the IPL (Initial Program Loader) or SPL because they open the door to the device handling.
Click to expand...
Click to collapse
Oh, I think I see what you mean. You're suggesting that if I've cut the ROM image short then only that part will fail but the loader should still be good so I could recover by burning another (good) ROM image.
Well, perhaps, but that would mean I don't have a valid backup and couldn't make one since it would be trashed in the bad flash. Or so it seems to me.
tobbbie said:
Sadly you MUST deal with SPL to upgrade to WM5+ afaik, so be very sure to select the right IPL and SPL that matches your device HW (OMAP 730, 750 or 850) and intended OS Version. Also take care not to enter any command in the SPL except the ones you are supposed to enter - it may kill your device as well. Do never use "format all" or "doctest" - you have a brick then.
Click to expand...
Click to collapse
I was thinking of going straight to WM6.x per
karhoe.net/guide-upgrading-htc-feelertyphoonamadeus-to-windows-mobile-6-update-september-06-2008.html
which involves changing the loader first via Patched_RUU
Do you think going to WM5 first is a safer procedure?
I said I was not aware of any checking - but as I have not written the SPL, I simply do not know it. You are right that reporting stuff like this makes it highly probable that upon restore a check on the image should be done before restoring. Try it out, if you like
WM5 or WM6 does not make a difference what the SPL is concerned. Afaik you have to use the same anyway. The device is tight in memory anyway, so don't expect miracles.
Go ahead, either dare it or leave it...
tobbbie said:
I said I was not aware of any checking - but as I have not written the SPL, I simply do not know it. You are right that reporting stuff like this makes it highly probable that upon restore a check on the image should be done before restoring. Try it out, if you like
Click to expand...
Click to collapse
Hehe. Yeah.
I was sort of hoping someone else had already stepped off that cliff and could tell me what the ground was like before I dove in
tobbbie said:
WM5 or WM6 does not make a difference what the SPL is concerned. Afaik you have to use the same anyway. The device is tight in memory anyway, so don't expect miracles.
Go ahead, either dare it or leave it...
Click to expand...
Click to collapse
The primary aim was to get bluetooth a2dp but the incentive may have diminshed, depending on how another project works out.
Thanks again for the help.
I would not bet on A2DP - I have it in the Tornado and the CPU use is much higher due to additional compression on the BT interface. Player + BT overhead is getting to average above 80% CPU (depending no the settings, but for good quality is like this) - it will also drain your battery much faster.
The Typhoon, Hurricane and Tornado have identical good analog Audio capabilities (I measured them with RMAA - see www.rightmark.org) and make a perfect music player as they are.
If your device is SuperCID you can take any other Typhoon ROM - you must just be sure that r2sd will save your bootloader + OS if you want to go back to WM2k3. I have done this already on my Amadeus (and went back to WM2k3) and this can still serve as a nice musicplayer.
tobbbie said:
I would not bet on A2DP - I have it in the Tornado and the CPU use is much higher due to additional compression on the BT interface. Player + BT overhead is getting to average above 80% CPU (depending no the settings, but for good quality is like this) - it will also drain your battery much faster.
The Typhoon, Hurricane and Tornado have identical good analog Audio capabilities (I measured them with RMAA - see www.rightmark.org) and make a perfect music player as they are.
If your device is SuperCID you can take any other Typhoon ROM - you must just be sure that r2sd will save your bootloader + OS if you want to go back to WM2k3. I have done this already on my Amadeus (and went back to WM2k3) and this can still serve as a nice musicplayer.
Click to expand...
Click to collapse
I admire people who can make these flash things work because it never does for me. I've now got an SMT5600 that will do nothing but display a rainbow boot screen and error out regardless of what ROM I try.
That's why I didn't try this till I had a new phone.
Hey that thread has a long history - what happened in the meantime?
3 colour screen does not mean the device is dead yet. You still have a bootloader that works and this is the thing to start from in any case.
What do the lines tell in the 3 color bars?
Did you already upload the changed SPL (I think it was 1.09) that allows to flash ROMs of WM5 or WM6 on that original WM2k3 device? If so, the you need to revert back to old SPL first before you can upload the original ROMs again.
tobbbie said:
Hey that thread has a long history - what happened in the meantime?
Click to expand...
Click to collapse
I put it on hold pending a new phone and other things cropped up.
Frankly, I had 2003 pretty well tricked out with SmartToolkit and gStart.
tobbbie said:
3 colour screen does not mean the device is dead yet. You still have a bootloader that works and this is the thing to start from in any case. What do the lines tell in the 3 color bars?
Click to expand...
Click to collapse
I swear it wasn't a troll but no sooner than I posted it wouldn't flash I managed a flash and I'm not sure why this worked when the others failed.
I was trying to verify the hard spl, getting info, etc. To make that easier I turned 'ui' on during boot and, just for chuckles expecting nothing, I tried flash again. You know, the definition of 'insanity'. Low and hold the dern thing flew.
As far as I know nothing was different other than 'ui' on. Same tools, same wm6.5 bin file, etc.
tobbbie said:
Did you already upload the changed SPL (I think it was 1.09) that allows to flash ROMs of WM5 or WM6 on that original WM2k3 device? If so, the you need to revert back to old SPL first before you can upload the original ROMs again.
Click to expand...
Click to collapse
You have no idea how helpful mentioning "1.09" is. The SPL flash program opines something like changing to v 5.000 but that number shows up no where and no where does it tell you to look for '1.09'. There are other confusions, like saying the existing device was 'Orlando' (I think it was), but I guess that's moot now.
Anyway, it's now running WM6.5 and I have a new toy to fiddle with inbetween playing with Android on my Tilt 2.
Thank you for the help.
Glad it worked now
The older (wm2k3) devices could only be updated with a binary transfer protocol (the .BIN file - which can be confused with other ".bin" in the scope of cooking in general). To enable the reception of the MTTY command "l" (for Load) and the execution of the related actions, the SPL must be in "UI" (User Interface) mode - this is the key for further flashing - and it must be mentioned in all such upgrade manuals. Also mind that other terminal programs (like TerraTerm) have not implemented that protocol. So only MTTY works for that purpose! As I am struggling currently with porting a Tornado ROM to the Hurricane I have come quite deep into that topic recently.
Are you having the WM65 from aleut now on the device? I think it is very tight on RAM now, so what are the memory key-data from settings->about after a reboot? You should repeat that with the standard home screen (Windows default) which is less memory greedy.
The way back to WM2k3 is not so easy as you must replace the SPL with the original one first before you can get back to the original OS. Whenever you mess with SPL it is a potentially dangerous action as failure doing that right will result in a bricked device.
tobbbie said:
Glad it worked now
The older (wm2k3) devices could only be updated with a binary transfer protocol (the .BIN file - which can be confused with other ".bin" in the scope of cooking in general). To enable the reception of the MTTY command "l" (for Load) and the execution of the related actions, the SPL must be in "UI" (User Interface) mode - this is the key for further flashing - and it must be mentioned in all such upgrade manuals. Also mind that other terminal programs (like TerraTerm) have not implemented that protocol. So only MTTY works for that purpose! As I am struggling currently with porting a Tornado ROM to the Hurricane I have come quite deep into that topic recently.
Click to expand...
Click to collapse
So I discovered after missing the little '0' in the instructions.
tobbbie said:
Are you having the WM65 from aleut now on the device? I think it is very tight on RAM now, so what are the memory key-data from settings->about after a reboot? You should repeat that with the standard home screen (Windows default) which is less memory greedy.
Click to expand...
Click to collapse
Yes, I originally flashed Aleuts 6.5 but I've since reflashed with his 6.1.
tobbbie said:
The way back to WM2k3 is not so easy as you must replace the SPL with the original one first before you can get back to the original OS. Whenever you mess with SPL it is a potentially dangerous action as failure doing that right will result in a bricked device.
Click to expand...
Click to collapse
Yep, flashing SPL is the most vulnerable but I don't think I'll be going back to 2003. Although, I might try WM5 if that has more free memory.
With most things I plan on using installed there's 8.5Meg free at boot and while that sounds laughable by today's standards there's only 22Meg total for a more impressive sounding '38% free' Although, as soon as you touch the thing almost half of that is gone.
I gave my Dad my old blackstone when my Desore turned up.
He has winged that he can't get the marketplace and about all those general WinMo issues that people have (it dead etc)
I can't find a clear message on the status of NANDROID for blackstone.
TIAD8s site has NAND versions that are missing bluetooth or other funcitons
It appears there are basic functions that are lost according which kernal is being run.
I'm willing to do one completely convoluted install just to get Froyo style on my dads phone but only once. I never have trouble with new flashing procedures (slow and steady wins the race) but I don't want to hand him back the phone broken especially as he uses hands free in the car
So - can anyone say categorically that a NAND version work fully?
Categorically: Not yet. Wondering if ever...
Forget it...
Think Tiad8 only has test team working on a NAND build anyway?
Not seen it in action yet
Kernals?! ....
I find deliberate typos (NOT TEXT SPEAK) can get people to engage.
olly230 said:
I find deliberate typos (NOT TEXT SPEAK) can get people to engage.
Click to expand...
Click to collapse
Is that also why you called it a "Desore" instead of Desire?
lol, you made a typo or you just didn't know. No need to try and rationalize it .
t8 let people wait and wait.
though it's good to try, we don't know whether he really works on it as he start many threads to other device besieds HD.
arrrghhh said:
Is that also why you called it a "Desore" instead of Desire?
lol, you made a typo or you just didn't know. No need to try and rationalize it .
Click to expand...
Click to collapse
Desore was a proper typo, I'll put my hands up to that
Tiad8's just kidding us, it will send to test team files from NVIDIA Tegra device. Only RUU_signed is working, but I think it's my modded LK Bootloader from Rhodium (with modified mtype). Something's wrong with this nand.
I have runned this but touchscreen not working properly and I don't have GSM.
MietasSR said:
Tiad8's just kidding us, it will send to test team files from NVIDIA Tegra device. Only RUU_signed is working, but I think it's my modded LK Bootloader from Rhodium (with modified mtype). Something's wrong with this nand.
I have runned this but touchscreen not working properly and I don't have GSM.
Click to expand...
Click to collapse
I thought you were part of his developer team because he now give credits to you for your ruu and recovery.img (at last he ist starting to do this: giving credits) in the NAND download post.
With your post here I had to smile a little: now your name is connected to the "null nands" for many consumers in tiad8's forum. Even I thought you're part of it now and that's why I tried the build yesterday again: Boot partition to small and Kernel not working.
I think now it's getting to the critical point in the NAND experiments: correct or good partition sizes for NAND (some members there startet to change partition values in the image files with a hex editor) and more important: building a working kernel with modules for Blackstone NAND.
Until now all experiments reached a few preparing goals: getting a working .nbh for starting into fastboot, getting a recovery.img for a working CWM etc.
But now (if I am completely wrong please correct me, I really want to know) you have to change partition and ram parameters in clk and hope you will spare the protected parts.
And after that: Kernel and Modules for Blackstone on Nand. I am starting to believe here would be the real point for developers.
I started to build Kernel and Modules, a Boot Environment (initrdgz) from git and packed them with changed parameters in a Tinboot-Package. I can flash with the .nbh, I can boot, I got a lot of errors in init first, but I succeeded in running and loading the kernel, I get access to the changed mtd partitions etc. Debugging on Blackstone with Echo "" ist quite funny.
I got stuck when I tried to cp files from SD card to the /system partition (which is mounted r/w) - I can cp files from / to /system anyway. Big ?? for me. But I like to play with it a little more, because I learned a lot.
ThaiDai said:
I thought you were part of his developer team because he now give credits to you for your ruu and recovery.img (at last he ist starting to do this: giving credits) in the NAND download post..
Click to expand...
Click to collapse
Me Too!! Does this mean you are working on different things?