Related
Quick question as I know this has been covered for other devices. Is the process of changing the boot splash image the same as on devices like the universal and the wizard?
Thanks.
James
It seems from some further googling that the answer is no for the simpler solutions, but still possibly yes for the process of making your own rom with something like mkrom...
not possible yet on the Hermes, see the "rom cooking" (very experimental) method described here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlashing
and more info on NBH format:
http://wiki.xda-developers.com/index.php?pagename=Hermes_NBH
Thanks pof. Didn't find that on the wiki when I looked!
ok, if anyone has bad blocks, I have finally managed to patch the SPL to allow you to flash a valid SPL and repair them.
later this will be integrated into Hard-SPL... so now, you can flash garbage, and not worry!
Wow, that is great work. I just feel like flashing just cause
BRILLIANT... i think the biggest reason for most ppl (not me though.. im on my second tytn ! ) not playing and cooking their own rom versions was the fear ....WHAT IF???
so let the cooking begin for the masses!
zohaer21 said:
BRILLIANT... i think the biggest reason for most ppl (not me though.. im on my second tytn ! ) not playing and cooking their own rom versions was the fear ....WHAT IF???
so let the cooking begin for the masses!
Click to expand...
Click to collapse
yes, we're celebrating over in the IRC at the moment after this little triumph.
Where is the SPL..I think I am the one who needs it most cos I hv only 13 MB of storage left
hdubli said:
Where is the SPL..I think I am the one who needs it most cos I hv only 13 MB of storage left
Click to expand...
Click to collapse
yes... I'm not releasing this for general consumption, I'm going to port it into Hard-SPL and release that properly.
However people such as yourself who have a pressing need for it should PM me with your e-mail address and I'll send it to you.
to use it; you need either to have a booting OS, or Hard-SPL installed, either will do, but please note that SPL-1.11.Oli is not ideal, so if you can get into windows mobile to flash it via SSPL, then please do so.
also, when you message me, if you're not terribly competent, then tell me so and I'll make an RUU for you
Wahoooo!!!!
This truely is the time for Hermes.
Olipro, you cease to amaze me my friend. Your work just gets better and better. Look forward to a release.
S.K.
Olipro said:
ok, if anyone has bad blocks, I have finally managed to patch the SPL to allow you to flash a valid SPL and repair them.
later this will be integrated into Hard-SPL... so now, you can flash garbage, and not worry!
Click to expand...
Click to collapse
well done Oli you are always on the ball. I hav a couple questions for you as I am quite interested in your work.
A bit of history first ..
Bad blocks are usually a result of process varieances in manufacturing of the NAND ROM and are marked by factory to identify them. To overcome low yields, companies that design ROM memory include extra or redundant blocks that can be addressed in the need to overcome bad blocks. (hence u dont lose storage space)
If we obtain bad blocks during the lifetime of our device that were not already there during initial manufacturing/fabrication, it is because a physical failure has occured while writing to that block numerous times.
So as there are reduntandant blocks in our ROM to suffice for bad blocks, does your technique use the "skip block method" where it identifies physically damaged bad blocks (that were a result of many read/writes) or does it use the "reverse area block method" where one good NAND block is used to keep track of all bad blocks in the ROM and the others not listed in the block table are used for data storage etc...
Or on the other hand, a block may not be defective (physically that is in its silicon process) but the value FFh may have been written to it at byte 517 in the first two pages of the block. In this case, the hermes will identify it as a bad block but in reality it isnt. Reason is that the value FFh at byte 517 is what is written to the first two pages of the block at the manufacturing factory to identfy blocks that have a manufacturing defect.
Looking forward to your reply.
Cheers,
jasjamming said:
well done Oli you are always on the ball. I hav a couple questions for you as I am quite interested in your work.
Looking forward to your reply.
Cheers,
Click to expand...
Click to collapse
if the SPL fails to write an address, it marks the block down as being ****e, therefore, if you flash with mine, whilst it will ignore them, if a write fails too, it'll just get re-marked as being bollocksed.
While I know virtually nothing about NAND ROM, I know that with regular ol' bad SDRAM, sometimes writing works, but then when you read a value back in, it's different from what you just wrote. So things like memtest86 write and read back to make sure it's all good. If the same or something similar is true for NAND, maybe the bad block verification should be changed to be safer.
Awesome work
Most excellent work olipro!!!!
We are coming even closer to the unbrickable device!!!!!
LOL once this is all widely used the manufacturers will notice a drop in repairs hehehe, thanks to the hard work of people like yourself
Olipro said:
if the SPL fails to write an address, it marks the block down as being ****e, therefore, if you flash with mine, whilst it will ignore them, if a write fails too, it'll just get re-marked as being bollocksed.
Click to expand...
Click to collapse
thanks OLI, understood, btw, i love the brit terminology, it has actually worn off one me, i tend to use ****e a lot in my everyday life.
Transcript of the glory moment
-:- [Users(#xda-devs:8)]
[ pof ] [ rob-ix ] [ erg_ ] [ bwesty ] [ mouseym ]
[ Olipro ] [@ChanServ ] [ LegolasThe]
[...]
[03:37am]<pof> ok, flashing 3%
[03:38am]<pof> now, for the 2nd time this night.. if it works i go to england & kiss your ass
[03:38am]<pof> 33%
[03:38am]<Olipro> haha
[03:39am]<Olipro> "if not, I go to england and kick you in the balls for keeping me awake"
[03:39am]<pof> LOL
[03:40am]<pof> 100%
[03:40am]<Olipro> don't hold your breath
[03:40am]<Olipro>
[03:41am]<pof> OLIPRO OLIPRO OLIPRO!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[03:41am]<pof> YOU DID IT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[03:41am]<Olipro> \o/
[03:41am]<pof>
[03:41am]<LegolasTheElf> oli - you rock!
[03:41am]<pof> back on normal SPL without bad blocks!!!!
[03:42am]<LegolasTheElf> and factory marked are ther still?
[03:42am]<pof> LegolasTheElf: yes
[03:42am]<Olipro> now I have to port that into SPL-1.11, **** it
[03:42am]<pof> hahah
[03:42am]<Olipro> nah, it's ok
[03:42am]<Olipro> I'll do it in a pinch
[03:42am]<Olipro> but no ****ing way am I doing it tonight
[03:42am]<Olipro> I'm buggered
[...]
Olipro said:
if the SPL fails to write an address, it marks the block down as being ****e, therefore, if you flash with mine, whilst it will ignore them, if a write fails too, it'll just get re-marked as being bollocksed.
Click to expand...
Click to collapse
I'm not sure if I fully comprehend it:
Your SPL simply ignores the bad blocks and does not touch they "bad block flag". Therefore your SPL will have no way of knowing if a block is indeed bad or just wrongly flashed?
Wouldn't a "proper" repair solution be a tool that resets all "bad block flags" so that the real SPL will remarkt they only if they are actually bad?
The way I understand it this SPL is a workaround to get a bad block-bricked device back to work:
1) Flash your fixed SPL
2) Flash a proper ROM
3) Revert to original SPL (or Hard-SPL that doesn't ignore bad blocks)
Or is it meant to be left on the device, ignoring bad blocks forever? If yes that would somehow question the neccessaty of bad block flags in the first place.
I hope you understand my question and I look forward to your reply.
ZakMcRofl said:
I'm not sure if I fully comprehend it:
Your SPL simply ignores the bad blocks and does not touch they "bad block flag". Therefore your SPL will have no way of knowing if a block is indeed bad or just wrongly flashed?
Wouldn't a "proper" repair solution be a tool that resets all "bad block flags" so that the real SPL will remarkt they only if they are actually bad?
The way I understand it this SPL is a workaround to get a bad block-bricked device back to work:
1) Flash your fixed SPL
2) Flash a proper ROM
3) Revert to original SPL (or Hard-SPL that doesn't ignore bad blocks)
Or is it meant to be left on the device, ignoring bad blocks forever? If yes that would somehow question the neccessaty of bad block flags in the first place.
I hope you understand my question and I look forward to your reply.
Click to expand...
Click to collapse
where it physically can't write data to the block (because it actually is bad) the idea is that this block is still not written to and moved to the next block since it's genuinely bad and a write fail has occured.
I see, so why did HTC use the flags anyways? If the SPL detects wrong flashes and skips those blocks?
ZakMcRofl said:
I see, so why did HTC use the flags anyways? If the SPL detects wrong flashes and skips those blocks?
Click to expand...
Click to collapse
because HTC are morons, and they have chimps working for them.
bad block checker algorithms are standard in the NAND flash ROM industry, for e.g samsung has developed algorithms to avoid bad blocks.
probably just wanted to save time during a flash and thought they were being clever by auto-skipping non FF blocks
As I understand it, Olipro's patch removes the bad block checking implemented on the SPL by HTC; the standard SPL checks if the byte 517th of a NAND page is != FF and subsequently stops writing into it, so they _are_ actually avoiding to write into "bad" blocks.
Hello everyone, first post. been reading a bit and I am gathering up the knowledge and courage to Unlock and flash my Alltel touch pro.
Was reading on PPCGEEKS thread on unlocking the phone and the version that I understand that I would want to use is 0.37 but it mentions no MFG commands, what are they? I did a search within the "Raphael CDMA" on MFG commands and the results really didn't answer my question.
Also what are the advantages to flashing my touch pro.
Thanks for any help,
Steve
MFG Commands are those that are ran at the boot loader. These commands are VERY DANGERUS!!! one is set 16 0 which boots your device from the bootloader, others are rtask a which i think activates the phone and rtask c which i think activates usb communications. When you flash your phone it really executes commands like these in the flashing app. if you dont know what they are dont even think about playing with them. if your doing something for the experts they'll tell you exactly what commands to run. it IS possible to erase EVERYTHING on your phone with these commands. Hope this helps
the set 16 0 is not a MFG command btw it is a standard spl command. The biggest addon MFG adds is access to mess around with radio data
Please report your observations. I'm thinking about doing the same, but avoiding any mistakes or issues you may have run into may help!
How did it go?
How did your phone perform?
What did you get?
What did you lose?
Give up the dirt!
-Much Mahalo to you and yours,
TikiKai
Please excuse my lack of experience on the matter.
But my main confusion comes from after a couple hours well of reading and yet still not quiet understanding.
I'm buying a HD2, but I'm interested in converting it over to the Android platform.
However after watching countless videos and reading endless posts - I think I've scared myself into a not knowing where to start now.
I initially came across some pretty cool links wish sounded helpful (and for the most seemed pretty straight forward)
<Examples>
youtube.com/watch?v=3gUwaJYWrdc
youtube.com/watch?v=Gqedm-sUBc8
youtube.com/watch?v=W6Thh-zHGgo
But then confusion after reading of things like finding out the best radio software suited to my region (which by the way is Trinidad), and HSPL3 and the ROM... I am wondering if I might just end up bricking my phone.
So I found out what the stuff means (as seen below) - but I'm still kinda well overwhelmed.
spl = Secondary Program Loader. Think of this in the same sense as bios on a pc. (it sets where your system boots from, intialises sub system process etc)
sspl = soft spl (this allows you to flash another spl or hardspl).
hardspl = hard spl .. basically it allows flashing of any rom. It protects you from bricking your device. If you have a bad flash it just forces the phone to load into bootloader, from where you can flash another rom using pc or storage card to get your phone working again. Using a hardspl you can flash any carrier rom without cid unlocking your device first.
radio is the part of the rom which manages the attena
Please if anyone is able to shed some light on the best way of me going about brining in the android OS to my HD2 - it would be greatly appreciated (given what ever the lastest most stable build would be)
Regards...
Also, whats the possibility of a dual boot straight from the phone?
people have reported that android works on stock roms so there might not be any need to flash a custom rom....... apparently a radio newer than 2.08.xx..... is required......
See this thread for that debate.....
Even if there is then all you need to do is follow the instructions in the Rom development section stickies and you cant really go wrong......
If you have a tmous hd2 then you might want to follow the instructions in the tmous section to avoid any potential radio mismatch problems......
Running android is as easy as putting a folder on your SD card and tapping two files in the right order........
Ok there might be quite a bit of trial and error in finding a build you like/works well....
And yes there are programs out there that will give you the option to choose between WM and Android on startup.....
personally I'd reccomend mskips version which you can find in the themes and apps section.........
Happy fiddling......
Thank you so much for the post and for the link you included to the guide.
I have seen a lot of useful information from just there alone. It's appreciated.
One thing I didn't quite follow however, was when you said 'tmous' hd2.
I'm assuming this is an abbreviation for a carrier of some sort?
The one I'm supposed to be getting is an unlocked version btw...
tmous = (T)-(Mo)bile (US) version as it has the 1GB ROM in it; the Euro version only has 512MB.
TriniKing_CE said:
Thank you so much for the post and for the link you included to the guide.
I have seen a lot of useful information from just there alone. It's appreciated.
One thing I didn't quite follow however, was when you said 'tmous' hd2.
I'm assuming this is an abbreviation for a carrier of some sort?
The one I'm supposed to be getting is an unlocked version btw...
Click to expand...
Click to collapse
As br0adband said above, tmous just refers to the american version of the HD2,
its easy to spot as it has a big fat double chin, tmobile written under the earpiece and green/red buttons to dial/hangup.......
if thats the version that you end up with then you should make sure any rom/radio your flashing is "tmous compatible".......
the wrong radio can kill it....... just stay away from anything with ".51." in the name.....
Good luck for when it arrives...... expect a lot of late nights tweaking.......
if you are sure you'll use android, why do you buy a windows phone?
i think thats nonsense...
just buy a desire hd and be happy.
DN41
DN41 said:
if you are sure you'll use android, why do you buy a windows phone?
i think thats nonsense...
just buy a desire hd and be happy.
DN41
Click to expand...
Click to collapse
+1...That makes no sense. Unlike the rest of us, we bought the HD2 knowing what it was all about, then later found that Android would be possible later.
Buying HD2 a year later knowing that you want to convert to Android is silly. Or it is because the HD2 might be cheaper than the newer HTC Anroid phones?
You have missed most of the fun there was in seeing the HD2 develope; from custom ROMs, to Cookies Home Tab, to Android etc etc. Jumping in now after all the blood, sweat and (tears) has taken place probably wouldnt provide you with the same level as enjoyment as I believe that the HD2 is running out of steam. Although there is the possibilty of WPS7 on NAND plus Android to consider.
The main reason for opting for the HD2 is that the price is alot more reasonable for me at this time. The specs are obviously better on the Desire HD and while the original Desire also already has the android platform, their prices are a little more steep for me as they came out just this year alone.
So during my searching around I came across this thread titled:
[GUIDE]The ULTIMATE n00bs guide to the HD2-HardSPL, Android, ROMs, Radios and more!
http://forum.xda-developers.com/showthread.php?t=808015
It seemed really detailed and what not - However, it clearly stated that it was solely for the T-Mobile (US Version) and not Internationally Unlocked ones.
Is there a similar thread where this might be found?
I don't see why it should be specific to the tmous, the only thing to watch out for is the potential radio mismatch... .
Sent From 1998 Via 56K Dial Up
Ok so within the this time which I am still just eagerly anticipating the arrival of my HD2 (which by the way is my first smart phone ) - I've continued to read more threads and posts, but some confusion still seems to exists on the various topics for terms for me.
For instance - I seem pretty clear on the fact that getting an android build on my HD2 is as simple as picking a ROM and then extracting the files correctly to my SD card and run the CLRCAD & the Haret files. - So then why I am still so confused...?
I think the main reason stems from a fear of not wanting to destroy my first modernized phone.
But aside from the basic process I briefly stated above, I have no idea what would be required of me to make the best of my modd-ing procedure.
I have seen links including a 1GB data.img dowloand - what is this for exactly?
I have read and understood that there are advantages of implementing HSPL on your device - but how does it fit into the already 'simplified' 4 step process listed above whereby you just download, extract and run the 2 files?
(...further to that whats the difference between HSPL, HSPL2 & HSPL3 - aside from updated versions I assume, would there be a reason for opting to use an older version?)
How do I determine if I am going to need to change my Radio version from what would already be included within a ROM I select? - and similar to my HSPL inquiry
(What's the main difference between the radio versions?
Wouldn't the highest number [most recent version] be the best?)
Further random (yet related...) questions:
RUU - Would it be necessary or make modd-ing any easier?
cotulla - Is this a single developer or a developer group?
NAND - Is this basically the main memory which holds the OS? - If so is there an actual way to now startup with Android on the HD2 - without WM starting at all and without any user interaction what so ever?
And finally...
When I eventually get my HD2 in hand, is there any information or details specific from my phone, which if provided could make it a easier to receive help on my goal?
If someone takes time to answer my questions - Thanks much in advance!
TriniKing_CE said:
Ok so within the this time which I am still just eagerly anticipating the arrival of my HD2 (which by the way is my first smart phone ) - I've continued to read more threads and posts, but some confusion still seems to exists on the various topics for terms for me.
For instance - I seem pretty clear on the fact that getting an android build on my HD2 is as simple as picking a ROM and then extracting the files correctly to my SD card and run the CLRCAD & the Haret files. - So then why I am still so confused...?
I think the main reason stems from a fear of not wanting to destroy my first modernized phone.
But aside from the basic process I briefly stated above, I have no idea what would be required of me to make the best of my modd-ing procedure.
I have seen links including a 1GB data.img dowloand - what is this for exactly?
I have read and understood that there are advantages of implementing HSPL on your device - but how does it fit into the already 'simplified' 4 step process listed above whereby you just download, extract and run the 2 files?
(...further to that whats the difference between HSPL, HSPL2 & HSPL3 - aside from updated versions I assume, would there be a reason for opting to use an older version?)
How do I determine if I am going to need to change my Radio version from what would already be included within a ROM I select? - and similar to my HSPL inquiry
(What's the main difference between the radio versions?
Wouldn't the highest number [most recent version] be the best?)
Further random (yet related...) questions:
RUU - Would it be necessary or make modd-ing any easier?
cotulla - Is this a single developer or a developer group?
NAND - Is this basically the main memory which holds the OS? - If so is there an actual way to now startup with Android on the HD2 - without WM starting at all and without any user interaction what so ever?
And finally...
When I eventually get my HD2 in hand, is there any information or details specific from my phone, which if provided could make it a easier to receive help on my goal?
If someone takes time to answer my questions - Thanks much in advance!
Click to expand...
Click to collapse
ok, where to start..... lol
il answer briefly because im posting from my device.....
your 4 step process is solid. no problems there.
you cannot brick your device with android.
the data.img is basically a file that pretends to be the phones internal storage, so if you download the 1gb file when you run android your phone will think it has 1gb of internal storage (things will obviously just be stored on your sd card, it doesn't actually affect your devices memory)
theres not much point worrying about the radio until you get the device and see which one you have, chances are it wont need to be changed.
unless your changing the rom/radio you wont need to use hspl
cotulla is widely regarded as being the driving force behind these kind of things, obviously there were/are lots of talented people involved but cotulla is probably the name your most likely to see being mentioned.
ruu - software tool that alows you to flash a rom.
included with stock roms, custom roms require a custom ruu but it is usually bundled in with the rom
nand - you pretty much nailed it, its not yet available though
when you get the device post the info from the settings - about phone/software info
hope that helps and sorry if I missed anything.....
Thanks a lot for your response!
conantroutman said:
ok, where to start..... lol
when you get the device post the info from the settings - about phone/software info
Click to expand...
Click to collapse
After my long anticipated wait - It has arrived.
Here are my initial specs:
OS version
5.2.21892 (21892.5.0.89)
Manilla version
2.5.20121412.2
ROM version
2.13.531.1 (90963) WWE
ROM date
04/28/10
Radio version
2.10.50.26
Protocol version
15.39.50.07U
Any advice?
Your Radio is above the minimum requirement for linux to boot so you're good to go. Download an android build you like the looks of from the Android Development section and extract the Android folder and place it in the root of your SD card.
Run CLRCAD then HaRET or get an android boot loader like THIS, THIS, or THIS to make the process easier.
Okay so after using my HD2 a bit on and off over the past 3 days or so - switching between Windows & Android, I'll summarize:
First off, the android build which I am currently running off of my sd card is:
darkstone HD2Froyo v1
Release date: 26.07.2010
Its pretty decent and all but, I have a problem that I keep on encountering and I'm not quite sure whether its just me (something I didn't figure out) or if its an incompatibly issue with my current WindMo ROM (2.13.531.1 (90963) WWE) or something. Or maybe just a glitch / bug in the build itself
I can't seem to get back access to my desktop at times once I open a browser (or some other apps / games as well); even after I attempt to close it off.
...One just simply reopens once I close off the last one...
This inability to regain access to my desktop at that point means I have no further access to any further applications either unless I start over. (or unless its an app which was previously opened - as I can then hold down the home button to see recently (previously) opened apps.
I'm wondering if I should try another build? (any suggested ones?! / any known problems with this build)
Also as my version is an unlocked T-mobile phone - would it be wise to follow through with an upgrade on the ROM from T-mobile's site?
T-Mobile HD2 MR Software (Version 3.14.531.1)
http://dl.htc.com/ruudownload/t-mobi....aspx?pid=leo2
EDIT:
I'm also the following message constantly and I'm thinking it might have something to do with the problem I'm getting.
This version of LauncherPro Beta has expired. Please go to http://www.launcherpro.com/ to get the latest version.
No suggestions...
I was simply copping some music across from my pc to HD2 with ActiveSync and I think I didn't d/c properly. Now my HD2 won't start up.
It just freezes on the Stick Together screen
(which contains the ROM, Radio info below)
I attempted to reset with the small red button, I tried pulling the battery completely. It still just comes back to that screen once I place the battery back in and FREEZES.
Attempted to go into bootloader by:
Taking out the battery. Placing it back in.
Press volume down, while pressed press the power button.
The colored screen comes up:
PBB1120 SS-B3
SPL-2.10.0000 8G XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x50
Someone please HELP!
Today I ran into a strange situation. While trying severald Andorid builds (mostly RAM based), I lost the ability to run unsigned executables.
I'm currently on stock T-Mobile 3.14 ROM, and do not wish to HSPL yet. Normally the way to fix this was removing and replacing the battery, effectively resetting any flags set. However even that does not work.
Is there an easy solution to this situation?
Nevermind, a re-flash fixed the situation
Solution
Go to the page and read it:
www mobilejaw com
/articles/2009/09/removing-application-lock-on-windows-mobile-standard-devices/
This worked for me. Nice software MobilControl.