Related
★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
NOTE: This is a thread for the build devs.
Users who want to try this solution themselves should head over to TheAgent1982's thread: RTL Support Project, or go to the Hebrew guide at htcaddicts.com.
Update: Hey devs. Just so you'd know, we're even willing to do the framework.jar patching for you!
All we ask from you is to deodex your builds, and include the patched framework.jar (which appears to be almost the same for all builds, barring sense/non-sense differences).
PM if you're willing to let us help
Hey devs
First of all, thanks to all the devs who are doing a great work with everything!
There's one thing though that's a pox on all Android builds (even native android devices), and that is full-on right-to-left support. What do I mean?
Sure, there are Hebrew (and I assume Arabic) fonts in Android, and MOST applications work just fine, with the notable exceptions of Gmail, Google maps, and most native Google-apps, who all display Hebrew backwards.
A far more stressing issue, however, is that ALL android applications without exception display numbers backwards in right-to-left texts (so 10 becomes 01, 12 becomes 21, etc. It can get really confusing really fast).
Any way, there exists a solution for both these problems that can USUALLY be fixed with a medium amount of experience on native Android devices, but requires a bit of a hassle for HD2 owners.
Hopefully, you devs can incorporate this fix to future releases, once the fixed files are obtained it shouldn't be too hard to spread in the future.
Here's the process:
BTW, This only works on completely deodexed builds!
First, you have to download this zip file. It basically contains the fixed files and some other stuff you devs probably won't need.
The fix then involves extracting 'framework.jar' from the phone, and extracting the 'classes' file thusly:
Code:
java -jar baksmali-1.2.2.jar -o classes classes.dex
Then, in the subsequently created "classes" folder, you need to replace the files in "/classes/android/graphics/" and "classes/android/text" with the relevant files in the aforementioned zip file (from the corresponding folders, of course, under "files/froyo/")
After that is done, you need to re-create 'classes.dex' using:
Code:
java -Xmx512M -jar smali-1.2.2.jar classes -o classes_new.dex
Then, replace the old 'classes.dex' in 'framework.jar' with the new one (after renaming it back to 'classes.dex', of course), and push the new and fixed 'framework.jar' back to the phone.
Reboot, and voila: full-on Left-to-Right support!
I'm sure you devs have far better ways of including these fixed files without having to edit the entire thing every time, but what would I know?
We would be extremely appreciative to all you builds devs if you could incorporate those fixed 'classes' files in future builds, it'll save us a ton of work.
Also, if any of you guys also need volunteers for beta-testing this solution (as I'm sure you don't have Hebrew content to test it with), feel free to PM me.
Thank you for listening, and keep up the great work!
((PS, thanks to member silverbluem who helped simplify the process))
+1
i use the htc sense to read sms so
the msg wont appear word4 word3 word2 word1
+1 for that. although i am using bifbif ver 1.2 with CM6 and its OK here.
i've test it on Mdj Evolution 2.3 and it work perfect:
i never copied the files to /graphic only to /text folder
to put the Framework.jar in the device because we dont have recovery mode
use this commands:
to pull the file:
adb pull system/framework/framework.jar
install the attached files
adb push (your file location/framework.jar) system/framework/framework.jar
after putting the file restart the device
restart might take 5-10 min first run after applying the file
thanks
silverbluem said:
i've test it on Mdj Evolution 2.3 and it work perfect:
i never copied the files to /graphic only to /text folder
to put the Framework.jar in the device because we dont have recovery mode
use this commands:
to pull the file:
adb pull system/framework/framework.jar
install the attached files
adb push (your file location/framework.jar) system/framework/framework.jar
after putting the file restart the device
restart might take 5-10 min first run after applying the file
thanks
Click to expand...
Click to collapse
This sure does absolve us of needing to use Linux and needing all that messy system.ext2 stuff. I'll give it a try.
Still, it'd be nice to have these updated files already incorporated into future builds.
Ambious said:
This sure does absolve us of needing to use Linux and needing all that messy system.ext2 stuff. I'll give it a try.
Still, it'd be nice to have these updated files already incorporated into future builds.
Click to expand...
Click to collapse
still need to figure out how to replace the graphic file
cause the view is not perfect without it...
Ambious said:
Edit: I tried this method, and while it DID boot, the solution didn't work - numbers still backwards, Google applications still reverse.
Click to expand...
Click to collapse
what rom are you using?
EDIT: the only thing that need to change to you is the phone book is now need to be RTL and the number backwards
Gmail need the Graphic file
silverbluem said:
what rom are you using?
EDIT: the only thing that need to change to you is the phone book is now need to be RTL and the number backwards
Gmail need the Graphic file
Click to expand...
Click to collapse
My WM rom is OzDROID2.0, my Android rom is MDJ FroyoHD 3.7
Well, the phone book was never a problem for me, only hybrid text/numbers like in text messages etc.
Anyway, turns out I didn't modify framework.jar correctly, so I tried again using the script, and this time the phone just won't boot (like when I used Linux, it just hangs at boot screen).
Edit: Tried all day, all combinations of 'texts' files and with or w/o the 'graphics' file, and it always either just didn't fix anything (when I did the fix manually), or didn't boot at all (when I tried the script). This got me to conclude that I must not be doing it right, or else it would fail to boot for me as well (at least, I'm not even considering me being able to totally fix it myself )
Not a week ago, i was referred to the Samsung Galaxy S's newest ROM which came from Orange..
The rom includes (to my understanding) all the latest fixes regarding left to right text and even a hebrew version of Swype
It is easily retrievable. Obviously, it isn't legal to extract their work and use it to manutfacture a widespread ROM... but you can use it for personal use if you want to check how to fix that annoying hebrew thing.
+1000
Thanks
nir36 said:
Not a week ago, i was referred to the Samsung Galaxy S's newest ROM which came from Orange..
The rom includes (to my understanding) all the latest fixes regarding left to right text and even a hebrew version of Swype
It is easily retrievable. Obviously, it isn't legal to extract their work and use it to manutfacture a widespread ROM... but you can use it for personal use if you want to check how to fix that annoying hebrew thing.
Click to expand...
Click to collapse
It COULD be used to reverse engineer some of the stuff, but I doubt it's similar enough to the HD2 builds to use it.
+1
Thanks
Hebrew RTL Support
For those who are asking, i have made a working framework.jar , time ago.
It is working for most FROYO Sence, CM6.+ does not need it...
BUT NOT Desire HD Sence ( Because is is odex files, not only *.jar).
If needed i will upload it, and put a tutorial how to make it work...
Good Day!
RTL HEbrew
Please do that !
Thanks
Framework.jar
Tomorrow i will post the file with short tut how to put it, i must say that Ambious bring a good tut directly from iAndroid
Any way, Ambious, if i will upload the file please stick it to 1st page.
For now, good night...
This fix is a must for all RTL language users.
As mentioned, CM6+ already includes the fix and is working pretty good!
Problem is, for some reason, CM6 builds are rare...
I tried a few Sense builds but eventually i came back to a CM6 based build
because of it's support for RTL languages.
Devs, please include this fix in you builds, to make them as much accessible
as possible.
Thanks.
TheAgent1982 said:
Tomorrow i will post the file with short tut how to put it, i must say that Ambious bring a good tut directly from iAndroid
Any way, Ambious, if i will upload the file please stick it to 1st page.
For now, good night...
Click to expand...
Click to collapse
I sure will!
Thank you
However, as a Sense user myself, I'm pretty anxious to see if a fix can be applied to any of the Sense builds (especially DesireHD, which is my current build).
Well Organized Post
I have made well organized post for it:
RTL Support Post.
I must say, it will NOT Work for Desire HD for now, because it is ODEX and jar combined, and as you have read at iAndroid, for now there is NO solution for it,
and i do not have the experience and time to learn and convert it, since i am a student.
But i will give it a try between the semesters...
Hey,
The HD2 Desire HD builds are fully deodexed.
Froyo HD 3.7 for example: http://forum.xda-developers.com/showthread.php?t=795914
Maybe you could use them for preparing a RTL fix for when the deodexed desire HD ROMS come and for us HD2 android users.
Cheers.
It may be my semi-n00bness, but all my attempts to create a fix for DesireHD 3.7 failed.
Also, trying the supplied fix in the thread above on MDJ Sense Clean (non HD based) failed, wouldn't boot.
Hopefully someone can get it to work, and better yet - that the devs will incorporate those fixes in their builds.
I build my custom rom's with oskitchen. With some imported windows mobile builds I get something wird after first boot: Device boots up, i can set provider information, set date and time, etc. When sense is started some time later the devices does not execute my shortcuts anymore. Says program not installed or not trusted. when ilook at the filesystem, the folders have strange chars and file system seems to be corrupted. Happened with 21658 and 23699 for example. Also imported build 28244 does not have this issue. Is it possible that this happenes because something in the sys of the imported kernel is not there and if so, waht files could that be?
I would first try a task 29 on your device to see if it helps (personally, I doubt it, but you're gonna do it sooner or later). Then, check to make sure that the files in your dump are all a-ok. You may be getting corrupted downloads or extractions, or maybe something is going on during cooking. Are you leaving out xip modules? If so, put them back in (e.g. cachefilt.dll).
Corrupted files
the thing is, on first boot everything seems to be ok. And it happens only in some of my imported windows mobile builds.
I have on build (28244) with rom builded it never happened.
Could it be that something has gone wrong in importing a windows mobile build that causes that described behaviour and how can I check it?
I am not sure but usualyy I use task 29 before flashing a new rom. I did it with my latest 28244 build and everything seems to be ok. My last 23699 build crashes after one whole day working without problems. That's strange. After that I flashed a 21658 which crashes after third boot.
Then flashed a new build with kernel 28244 again (new build to be sure, that oskitchen is still working correct) and this build is working again for the second day.
I keep my kitchen on a portable hard-drive, and I will occasionally scan the drive for errors (very rarely find them). You might load the nbh onto and sd card and scan it to see if there are issues. I have gotten corrupted directories before, but that was after using the storage card tool of sk tools to scan the main memory. I finally just decided the tool was buggy, so I don't use it on my main memory anymore (haven't had the issue since).
I think you can test archives with 7-zip to make sure they're ok. You should post screen shots, and maybe a build log. But if you have the same packages in the different builds, then I don't think it's a missing file issue. Cook iI a full xip, though.
Task29 before flash if you changing com branches.
Corrupted file system
Thx
device now working for three days without problems.
I think I will check for myself next time to always use task29 before a new flash
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
[DFT Freedom ROM] Mango 7714 SCHUBERT Custom ROM
About DFT Freedom ROM for Schuber see here
This ROM replace mango 7714 OS from Previous ROM
"multitasking" has been achieved
Wifi can not find the hidden features
Must use version 4.8 ZUNE
Sync Live is normal, download the xap from Market is normal
Download link
1)USA_CHT_CHS_JPN_KOR,
2)USA_ENG_FRA_ITA_GER_ESN,
3)USA_NLD_DAN_FIN_NOR_SVE,
4)USA_PTB_RUS_ELL,
5)USA_HUN_CSY_PLK.
IMPORTANT NOTES
1. Before doing any operations be sure you have battery level more than 50%!
2. You must had RSPL/HSPL install to your device , download RSPL/HSPL see this thread : http://forum.xda-developers.com/show....php?t=1195647
3. Supported OS: Windows XP, Windows Vista, Windows 7.
Warranty Issues
Be warned, using RSPL may void your warranty.
If you need to send your device to a Repair Centre, make sure that it looks like stock! Install stock official ROM before go to Repair Centre.
Disclaimer
This product is free to use at your own risk. We take no responsibility for any conflict, fault, or damage caused by this procedure. No warranties implied or otherwise, are given if you agree to use this product. No problems were found while testing this product on several different devices, your experience may vary.
Use of the Product for commercial purposes is strictly prohibited and to prohibit the use by xda.cn Forum.
It’s allowed to make cooking this ROM; it must be distributed as original release link ; for protected this site(XDA-developers.com) and our official DFT site, it's NOT allowed to distributed this ROM within 5 days,after 5 days free to distribute.
Official DFT site (Chinese)
DarkForcesTeam Aug.11,2011
Downloading now! I will report back very soon! Good job guys!
Cheers,
Shokouhi
Forgive me for asking but if Im from the US do I download USA_ENG_FRA_ITA_GER_ESN,?
JosepHenry said:
Forgive me for asking but if Im from the US do I download USA_ENG_FRA_ITA_GER_ESN,?
Click to expand...
Click to collapse
there is no password for this thing. as its asking for password, pls could you add the password so that everybody can enjoy it.
Downloading
Downloading now, will revert after upgrade.
I am having two problems with the DFT ROM with this version 7714 and previous version, 7713.
Problems:
1) I downloaded and put in the password "www.dft.so", the rar file extract and then at the end I get 1 crc error with "wrong passord" on the FINAL.nbh file, but it still extracts and looks intact.
2) I went ahead and put my Tmobile US HD7 in boot rom mode (with HSPL) and flashed with the ROMUpdateUtility.exe. I kept getting stuck at certain percentage and had to recover by pulling the battery.
The above problems happened on both the DFT 7713 and 7714.
I have Windows7 X64. I tried it on X86 Windows 7 but still no luck with those two problems.
I would like to add that when I flash other ROM (i.e. Ansar's), I have no problem.
Please help.
r0ark said:
I am having two problems with the DFT ROM with this version 7714 and previous version, 7713.
Problems:
1) I downloaded and put in the password "www.dft.so", the rar file extract and then at the end I get 1 crc error with "wrong passord" on the FINAL.nbh file, but it still extracts and looks intact.
2) I went ahead and put my Tmobile US HD7 in boot rom mode (with HSPL) and flashed with the ROMUpdateUtility.exe. I kept getting stuck at certain percentage and had to recover by pulling the battery.
The above problems happened on both the DFT 7713 and 7714.
I have Windows7 X64. I tried it on X86 Windows 7 but still no luck with those two problems.
I would like to add that when I flash other ROM (i.e. Ansar's), I have no problem.
Please help.
Click to expand...
Click to collapse
I recommend that you dowload the file again. I just extracted mine without any CRC error. Although it looks ok you do in fact have a corrupt ROM image.
StriderNZ said:
I recommend that you dowload the file again. I just extracted mine without any CRC error. Although it looks ok you do in fact have a corrupt ROM image.
Click to expand...
Click to collapse
with the 7713 DFT rom, I downloaded it 4 times! CRC every single time. I downloaded one from my work and the other 3 times from home.
any other suggestions? I'll try downloading again.
All of my systems have Microsoft Security Essential anti-virus. Maybe that's the problem?
r0ark said:
with the 7713 DFT rom, I downloaded it 4 times! CRC every single time. I downloaded one from my work and the other 3 times from home.
any other suggestions? I'll try downloading again.
Click to expand...
Click to collapse
try using an updated winrar, some older versions have issues. maybe this helps
pencilcase said:
try using an updated winrar, some older versions have issues. maybe this helps
Click to expand...
Click to collapse
I'd just tried that before your suggestion. Tried the winrar 4.01 (x64 and x86). Still no luck. This is driving me nuts!
I guess I'll try to download with another browser instead of Firefox which got some add-ons (i.e. adblock)
r0ark said:
with the 7713 DFT rom, I downloaded it 4 times! CRC every single time. I downloaded one from my work and the other 3 times from home.
any other suggestions? I'll try downloading again.
All of my systems have Microsoft Security Essential anti-virus. Maybe that's the problem?
Click to expand...
Click to collapse
I downloaded 2)USA_ENG_FRA_ITA_GER_ESN, and had no problem.. are you downloading a different file.. Maybe it is in fact a corrupt upload.
I had the same problem with 7713 archive. I just downloaded it again and it helps. Try to use some other browser? Maybe it helps.
Archive Password
Archive Password - www[dor]dft[dot]so. replace [dot] with period.
what is the changelog from 7713 to 7714
7714, 7713, 7712.
whats the diff?
they are the same thing.
becuase 6617 -7712 , there was a significant difference..
Magpir said:
7714, 7713, 7712.
what's the diff?
they are the same thing.
because 6617 -7712 , there was a significant difference..
Click to expand...
Click to collapse
normally , in the last few builds before rtm they take out debug software and enable futures that where disabled because developers don't use them
It is just me or this ROM is not Chevron unlocked or Jailbreaked like 7713?
r0ark said:
I'd just tried that before your suggestion. Tried the winrar 4.01 (x64 and x86). Still no luck. This is driving me nuts!
I guess I'll try to download with another browser instead of Firefox which got some add-ons (i.e. adblock)
Click to expand...
Click to collapse
Try downloading with download manager. i downloaded with IDM and dnt have any problem.
I have a feeling that the DFT team is incrementing the build. Not positive but 7713 and now 7714. I find it hard to believe that there are versions 7712, 7713 and 7714..
dotcompt said:
It is just me or this ROM is not Chevron unlocked or Jailbreaked like 7713?
Click to expand...
Click to collapse
Just installed it, and grabbed me an Angry Birds XAP , no problem to install it, and after install it works too.