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.
Related
Please dont tell me to read the other threads on this issue. Your better off skipping this topic and moving on to the next. I preffer this to go untouched with no replies than to have smart ass comments. Ive been reading pages and pages on how to do this for weeks with no luck. Theres about a few dozen options and with all the suggestions I have no idea where to start, nor what programs to download first, understand what these terms mean, etc. Maybe this isnt my cup of tea and I shouldnt even be attempting this but thats neither here nor there cause the fact of the matter is I screwed things up. Now Im looking for some help from the community.
Its getting real expensive and I need a serious expert who has patience and is very thurough. This is my second unit and I still have the 1st one that is still bricked as well. This is the situation for both. When I go to setting>system>device info, there was no radio version, no protocol version, no IMEI, and the call duration info was zero. I was able to use both units for thier PDA functions but not the phone prtion. I was attempting to SIM unlock and SuperCid em both. Now they are both stuck in bootloader. Im not sure what went wrong but I have done 3 other 8525's with success also updated roms and reverted back and no problems. I just cant seem to get the bricking undone. Now Ive done tutorials on housing swaps, step by step and provided pics as well. You know what, people still ask how to do it. Its a fact guys. some people just need a little more direction than others. What Im trying to say is Im looking for help not criticism, Im a grown man and the last thing I need is for some young punk to flame me,or telling me to read cause Its already been done. I can easily buy another phone but Im willing to learn how to get out of this bricking crap. So its back to reading. TIA
Heres How You Do It
I know how you feel because last night i bricked my 8525 cingular, Okay, If You Can Start Up Your DEvice All You Have to do is reset it to te factory condition and that would help you, unfortunatley all of your data would be lost, but its better than a bricked expensive phone. Oh, but your stuck in bootlaoder, well i have good news for you your not bricked your just stuck, go to the att website and a download and update and the update should recogize your phone even though the computer dosent, after that you have a brand new updated 8525 and that should get you out of bootloader.
ivan345 said:
I know how you feel because last night i bricked my 8525 cingular, Okay, If You Can Start Up Your DEvice All You Have to do is reset it to te factory condition and that would help you, unfortunatley all of your data would be lost, but its better than a bricked expensive phone. Oh, but your stuck in bootlaoder, well i have good news for you your not bricked your just stuck, go to the att website and a download and update and the update should recogize your phone even though the computer dosent, after that you have a brand new updated 8525 and that should get you out of bootloader.
Click to expand...
Click to collapse
Really??? This seems too easy. I'll try anything at this point. So you say its not bricked,just stuck in bootloader? So there is hope? Thats def bice to hear. I'll give it a shot. Thanks
LOL. Tried and and same problem. It sounded too good to be true. Thanks for the tip though
I'm not trying to be smart (believe me, I'm not equipped to do that!) just trying to help determine the exact state so that someone may be better able to help.
You say the phone's are stuck in bootloader, but that you're able to look at the device info on them, and use them for their PDA side. I always thought stuck in bootloader meant that when you switched it on, it came up with the multi-coloured bars but got no further (as if you'd reset it while holding the power and side OK button). Do you mean that the phone's work as normal but have no PHONE side of things, or can you get no further than the bootloader screen when trying to start them up?
Like I said, not trying to split hais just trying to get the exact symptoms for someone cleverer than me to help.
OK by the sounds of it you are definatly NOT stuck in bootloader.
firstly can you please answer the following questions from the wiki:
1. Which is your SPL version?
Put your hermes in bootloader mode (side ok + power button + softreset), the SPL version appears in yellow letters on the upper side
2. Which is your radio bootloader (HTC_BOOT) version?
If your radio version is <=1.27 your HTC_BOOT is 0106 or 0107, the only exception is Softbank X01HT 1.14 radio which has HTC_BOOT 0108
If your radio version is >= 1.30 your HTC_BOOT is 0108
If you don't know which is HTC_BOOT, but you have bootloader 1.01 MFG, 1.10.Oli or 1.04 you can access to the radio bootloader using the command 'rtask a', then type 'rversion' and hit enter (you won't see anything in the screen when you type rversion, because the radio bootloader has no echo, this is normal).
3. Is your device able to boot Windows Mobile OS?
This one is easy: If can you see your today screen and use your phone as a PDA means you can boot OS. If you only see the splash screen, bootloader screen (tri-color) or windows mobile splash screen you can't boot OS.
4. Do you see "No GSM" message in red letters on the first splash screen?
Reset your hermes, you will see some numbers and letters appear in red and disappear after a few seconds... your radio version is there, but if your radio is corrupted for some reason, you will see 'No GSM'.
5. Does your OS rom have KITL enabled?
Hold COMM MANAGER and POWER buttons together and reset with stylus, if you see the message "Select KITL Transport" your OS rom has KITL enabled, otherwise not.
Click to expand...
Click to collapse
Please post the answers back here when you are done.
Stu has an excellent point. Need to know the exact state of the 8525. Exactly what you have done to it....
Example: I used Pof's free HTC SIM unlock and SuperCid program. It appeared to complete successfully. However, now when I start the 8525 up it automatically goes into the tri-color boot loader screen. I had not applied anything else to the 8525 prior to trying to unlock it.
Also, there is a sticky for dead hermes. I bricked mine as well, and was able to get passed it. I posted in the sticky. If you post in that sticky, then someone else may benefit from what you find out. Keeps everything in one place
jeffreyj900 said:
Stu has an excellent point. Need to know the exact state of the 8525. Exactly what you have done to it....
Example: I used Pof's free HTC SIM unlock and SuperCid program. It appeared to complete successfully. However, now when I start the 8525 up it automatically goes into the tri-color boot loader screen. I had not applied anything else to the 8525 prior to trying to unlock it.
Also, there is a sticky for dead hermes. I bricked mine as well, and was able to get passed it. I posted in the sticky. If you post in that sticky, then someone else may benefit from what you find out. Keeps everything in one place
Click to expand...
Click to collapse
Yeah, but, if you used V3a to unlock it, you actually got Oli's BL as part of the deal--hence why you can unbrick it easily!
WELP no smartass comments HUH? Well if you ****ed up 2 phones like this you really must be doing something wrong there buddy. your phone is not stuck in bootloader if you can see the device info thats for damn sure. first thing load SPLV7 on your phone then flash a a complete ROM including radio and OS and then you should be all fixed and if that dont work there is a WHOLE thread just for BRICKED phones so go read like you said you whrere doing.... To me its sounds like you dont have a clue what your doing since you have done this to 2 phones and if you did have a clue your first thing would have been to load SPLv7
so go enjoy your not really bricked bricks
and if i remember right your one of the fools that was making fun af elf because he charge people like you to fix phones over at hofo... so take your problem over there or call elf for some one on one and eat some ****....
Click to expand...
Click to collapse
I gotta give you a lot of credit for that post. Me and a few other members had a bet that it would take less than an hour before the first idiot would surface, Thanks LOL. Who the hell is elf, and I would like to see the post that I had made making fun of anybody. If your gonna try to put someone on blast, back it up. Its assholes like you that a community can do without. Your a true idiot man. No1 needs you around here with that type of attitude. I dont blame you though, I blame your parents for having you. Your mom should have flushed the toilet when she had you then we wouldnt have a piece of **** like you in this world, shame on her. They should be ashamed of themselves for they way you have turned out.
I was able to do all the PDA functions prior to gettting my phones stuck in bootloader. That is were I am now. I got myself stuck in bootloader while trying to load HardSPLv7. I had not done any type of mods or upgrades prior to doing this.
Elf, I want you and that moron to post topics if me bashing you, I cant imagine me doing that. I am 30+ years of age, 3 children and a beautiful wife. I dont have a lot of time, nor do I have the time or care to flame other on these forums. I know that I look to people here and other forums more than they will need me. So please back up that what you are saying and I make sure that I make it an effort to put in my sig that I am an idiot and that you are god. If this it was gets you thru the day, so be it. Just back them comments up. Its a bad tag to put on someone.
My phone reads on tri color screen
Herm100
IPL-1.01
HERM1
SPL-1.40. Olipro
I can do anything other than see this bootloader screen.
(directed at the OP)
Instead of wasting your time replying to posts which are off topic why dont you answer the question posed in my reply...then we can get your two Hermes devices back to working order. Otherwise a mod will inevitably lock this thread and you will be back to square one.??
mrvanx said:
(directed at the OP)
Instead of wasting your time replying to posts which are off topic why dont you answer the question posed in my reply...then we can get your two Hermes devices back to working order. Otherwise a mod will inevitably lock this thread and you will be back to square one.??
Click to expand...
Click to collapse
When I recieved the phone there was no radio version displayed nor was there a protocol version. I also noticed that there was no IMEI that was displyed under the device info. While I was attempting to load the HardSPLv7, that is when I got stuck.
Bro I need serious step by step instructions on this. I've taken all that had been posted about this stuff and a have a pile of info about it. Theres not a whole lot I can do in the boot mode si Im trying to make sure Im doing the steps properly. The info I have given is based on the 8525, I'll work on the TYTN after. Thanks
My appologies.. I just checked HoFo.. You were not one of the idiots on there, as far as I can tell..
Sorry.
Click to expand...
Click to collapse
Appology accepted. Im not worried about man. I got other things to worry about.
Again can you PLEASE answer the questions in my reply?? I need an answer to all FIVE of them, a simple task which will give us the correct status of your device, even if it seems stupid...do it. (the questions im referencing to)
mrvanx said:
Again can you PLEASE answer the questions in my reply?? I need an answer to all FIVE of them, a simple task which will give us the correct status of your device, even if it seems stupid...do it. (the questions im referencing to)
Click to expand...
Click to collapse
1.SPL-1.40 Olipro
2.Dont know. Is there a way to check this now that I am in boot mode.
3.NO.
4.NO
5.Not sure. How can I find this out in the stage Im in
FLiPinoy9oNe6 said:
1.SPL-1.40 Olipro
2.Dont know. Is there a way to check this now that I am in boot mode.
3.NO.
4.NO
5.Not sure. How can I find this out in the stage Im in
Click to expand...
Click to collapse
OK, right you need to flash ANY ROm that contains an OS only, DO NOT try flashing a ROM which has a radio or SPL etc...
Follow my WM5 Downgrade Guide, this will take you through the steps necessary, select the relevant ROMs by HTC and Cingular (found in the wiki).
If that works as desired then update to HArdSPL v7 for both devices then flash a new radio.
mrvanx said:
(directed at the OP)
Instead of wasting your time replying to posts which are off topic why dont you answer the question posed in my reply...then we can get your two Hermes devices back to working order. Otherwise a mod will inevitably lock this thread and you will be back to square one.??
Click to expand...
Click to collapse
wont lock the thread since the guy needs help... but instead i will play janitor and clean it up... since some people will never learn to play nice...
More to the point, have you managed to fix them using the procedure i described?
mrvanx said:
More to the point, have you managed to fix them using the procedure i described?
Click to expand...
Click to collapse
No sir, Ive got two computers working on this right now. One to look at replies and the other to do the update. I had to get a bite to eat so Im back at it. Im trying to connect to sync but not working. Im reading up again on this Sd card deal and mtty so Im trying.
Yes ofcourse i forgot, once you have rebuilt the nbh to make an OS only update (OS,Ext ROM and the 2 splashes) you cant update as normal because there is no activesync connection...the sd card technique is what you need to do. After the device can get into OS and connect over activesync you can do the rest (HardSPL and Radio).
ok mrvanx, after using device monitor I fianlly got a connection and tried downloading a rom. Process goes thru and at 12% it stops and gives me the 262 error message. I do wat it suggest when getting the message with sof reset and try again, still same error.
flash from a damn SDcard and be done with this **** man... your wasting time half assing around... flash an OS.nb from your card and then do all that was told to you from above... this is the only way you will get your hermes working again
mrvanx said:
OK by the sounds of it you are definatly NOT stuck in bootloader.
firstly can you please answer the following questions from the wiki:
Please post the answers back here when you are done.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=9664136#post9664136
Sir please help me
1 HERM100
IPL-1.01
HERM100
SPL-1.40.Olipro
2 - rite now dont show while OS is on
3 yes OS loads ok
4 (yes) No GSM shows while boot
m 05
s 04 No GSM
B 06 D 3.57
5 I can't find as comm manager button confused
Problem:
use RUUWrapper.exe to Updata, final step, then Phone Screen stays in 0%, the RUU programs shows a 302 Error. when I did what it told me to, everythings happened again.
First happened when I updata my Radio from 1.51.00.00 to 1.47.00.00
and happened again when I updata the ROM (OS only)
Q:
1. How to solve this?
2. After I upgrade the Radio to 1.51.00.00 I can't hear the others clearly when pick up a phone. try to up the volume, but useless, which version will be OK?
3. any REG modify solution?
I try to modify the REG
HKEY_CURRENT_USER ->
ControlPanel ->
SoundCategories ->
InCall ->
InitVol ->
DWORD Data
6 to 9
but seems no change
I had the same problem and most likely noone will help you on this board.... I read the forum, then asked for help and still no educated replies... I feel like this forum is run by HTC producers and they make you brick the phone and force you to and go buy a new one !!!
hanissusa said:
I feel like this forum is run by HTC producers and they make you brick the phone and force you to and go buy a new one !!!
Click to expand...
Click to collapse
This thread was hardly 1 hour old and you make a rather rude statement. This forum is supported by volunteers, not people that sit around all day waiting for posts to come in and find a solution that drops out of no-where.
hanissusa said:
I had the same problem and most likely noone will help you on this board.... I read the forum, then asked for help and still no educated replies... I feel like this forum is run by HTC producers and they make you brick the phone and force you to and go buy a new one !!!
Click to expand...
Click to collapse
You are not going to make any friends this way mate. If you want quick solutions then read all the material that's on here and search for the answer yourself.
If you don't want problems then leave your phone in its standard state.
WB
@camus_dvd: have you checked out the wiki? There may be a solution there. If not, you need to give us more info?
Have you ever successfully flashed before?
Give us Versions? Windows, ActiveSync, .NET, ROM, RUUWrapper (e.g. is it the custom or a standard shipped), etc.
Did you try removing the battery for a couple minutes?
Did you try connecting while in bootloader mode, instead of in normal state? (e.g. put phone in BL, THEN attached USB, then run updater)?
These answers will help us help you.
Oh, and about the volume issue, try using the google search link in my sig to search the forum for "hermes low volume tweak" or something like that. I had a similar problem, but cannot remember the tweak. I do not THINK It was the one you posted.
Heck - onew final edit. I got curious and did the searching. You will find a thread HERE and it references a tweak in the wiki HERE HERE . Hope this helps.
@hanissusa: sorry you did not get any "intelligent" answers. If you are unhappy, you are not a prisoner here.
If you want quick solutions then read all the material that's on here
Click to expand...
Click to collapse
I spent 3 days reading the forum, trying all kinds of methods to unbrick it, however it still dead. Is it considered a quick solution ?
Anyways, I successfully flashed my device and made SUPER CID, so its fully unlocked. Thats the only flash I have done prior to upgrading the radio bootloader. I hold 2 computer science degrees and I could understand most of the stuff discussed on this forum, however it didnt solve the problem.
The reason I tried to flash my radio bootloader is because suddenly the phone started to freeze(about every 30 mins). I thought may be the operator has a new radio version so I need to upgrade in order to get the best connection and most importantly never have my phone freezed again.
Did you try removing the battery for a couple minutes?
Click to expand...
Click to collapse
Tried about 20 times, still unable to flash radio rom with any of the available versions. Always freezes at 0% thru RUU, if I use SD card method freezes in the 10-15% range. I am able to flash everythin, including SPL, operating system, but not the radio rom !!!
Did you try connecting while in bootloader mode, instead of in normal state? (e.g. put phone in BL, THEN attached USB, then run updater)?
Click to expand...
Click to collapse
Tried that as well. Tried using MMTY, checksum gives me radio error.
sorry you did not get any "intelligent" answers
Click to expand...
Click to collapse
I got several answers of this type:
"Go read Wiki"
"Go try this method"
and I have done all of it and nothing helped the problem.
You can consider above answers very intelligent, however I did not get a single anser form POF or Olipro - people who actually created this software and know most of the tricks.
for me same problem, only that i can't use my device anymore( : I tried to install another rom, Hermes_WM6_WWE_vp3G_v3[1].61.0_ATT_Full.rar and Touch_I_interface_beta.zip and crashed. and now, i enter in bootloader, if i want to make super cid it tells me to connect the pda even if is connected. and if i try to install other roms is stuck on 0%
hanissusa said:
I spent 3 days reading the forum, trying all kinds of methods to unbrick it, however it still dead. Is it considered a quick solution ?
Anyways, I successfully flashed my device and made SUPER CID, so its fully unlocked. Thats the only flash I have done prior to upgrading the radio bootloader. I hold 2 computer science degrees and I could understand most of the stuff discussed on this forum, however it didnt solve the problem.
Click to expand...
Click to collapse
I wonder what kind of institution gave you said degrees? I have a degree in Japanese and Linguistics but I suck at both.
hanissusa said:
"flashed my device and made super CID, so its fully unlocked"
Click to expand...
Click to collapse
Flashed and superCID does NOT mean fully unlocked. If you can read programming and or networking text books, I don't understand what is so hard about the wiki?
If you read everything and actually tried to understand it all, then you would know that flashing the radio is inherently dangerous and that 9/10 times the radio is not the issue.
camus_dvd said:
Problem:
use RUUWrapper.exe to Updata, final step, then Phone Screen stays in 0%, the RUU programs shows a 302 Error. when I did what it told me to, everythings happened again.
First happened when I updata my Radio from 1.51.00.00 to 1.47.00.00
and happened again when I updata the ROM (OS only)
Q:
1. How to solve this?
2. After I upgrade the Radio to 1.51.00.00 I can't hear the others clearly when pick up a phone. try to up the volume, but useless, which version will be OK?
3. any REG modify solution?
I try to modify the REG
HKEY_CURRENT_USER ->
ControlPanel ->
SoundCategories ->
InCall ->
InitVol ->
DWORD Data
6 to 9
but seems no change
Click to expand...
Click to collapse
Read here:
http://forum.xda-developers.com/showthread.php?t=332565
then here:
http://forum.xda-developers.com/showpost.php?p=1177210&postcount=5
or from here:
http://wiki.xda-developers.com/
then read the stickies and do a search.... it's all been discussed before
does exists any way to upgrade my dead tytn from storage card? I have an Qtek S200 and a HTC P3300 (if i can use them to restore my dead tytn). please all. I don't know what to do with him
Is there a senior, experienced member on this forum from London, UK ? Please help me fix the radio, beers and drinks are on me.
ady_uaic said:
does exists any way to upgrade my dead tytn from storage card? I have an Qtek S200 and a HTC P3300 (if i can use them to restore my dead tytn). please all. I don't know what to do with him
Click to expand...
Click to collapse
Is this what you are looking for?
http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlashing
@hanissusa,
Why don't you just send your device back to the repair centre, foot the bill, and put it all down to experience? You may have a hardware problem that nothing on here might solve.
You might be better off going down that route than going through the pain of trying to sort it and not getting anywhere. Also stops you p**sing people off on here. You can't claim that just because you have had a bad experience we should all stop flashing our devices.
We are all aware of the risks and if we can't fix it then its put your hand in your pocket time and send it back to be repaired.
Good luck with it; hope it all works out.
WB
thx a lot. I will try it, 'cause i'm tired to use all kind of stufs
my first SPL was 1.03 but after a try of upgrading ROM it was modifed in 2.03 and i think this is the problem. does anyone knows how to modify it?
how can i downgrade my SPL ?
pi$$ing people off ? hey chill back I am just giving experienced advice to other people, just as you do. The fact that our opinions are different does not mean that you are right and I am wrong.
Anyways, I have T-Mobile MDA, as far as I udnerstood HTC repair would not care to fix it ?
hanissusa said:
pi$$ing people off ? hey chill back I am just giving experienced advice to other people, just as you do. The fact that our opinions are different does not mean that you are right and I am wrong.
Anyways, I have T-Mobile MDA, as far as I udnerstood HTC repair would not care to fix it ?
Click to expand...
Click to collapse
Have you called the repair centre to see whether they will fix it or not? Your worse case scenario is that they say no. There again they might say yes, especially if you are willing to foot the bill, or put you in contact with another company who can sort it out for you.
I really do hope you can get it fixed; however I think you have started out on the wrong footing on this board and you may well find that people on here now just don't want to help you out (please don't shoot the messenger).
Good luck with it.
Cheers
WB
ady_uaic said:
how can i downgrade my SPL ?
Click to expand...
Click to collapse
You can't without a running OS setuped on your device. If you don't have the HardSPL you should try to flash with the default flasher AND a rom matching your CID.
If there is a rom matching your CID out you may have quite good chance to get your hermes back to live. Toying without hardspl is a really bad thing
and that hardSPL how can i do it?
Have you called the repair centre to see whether they will fix it or not?
Click to expand...
Click to collapse
Which centre should I call if I live in London, UK ? Maybe somebody wants to help me fix this and get paid ?
Hi guys. Mass apologies for my stupidity, but here goes...
I have now spent over 2 days on this site reading all that I can, but I am at a loss and desperate for your expertise!
I am running a UK Tmobile Vario 2. I was having problems with the phone crashing constantly and not getting any signal at all so I installed WM6 yesterday hoping this would help. Its not crashing as much, but its still not getting any signal.
After reading loads of threads and posts all over the place (I have read enough WIKI to make my eyes bleed), I think I need to update the radio version. This is the information I can gather from my phone:
Bootloader info-
Herm300
IPL-1.04
SPL-2.03
I cant figure out how to enter commands in bootloader to gather any more info I tried the mtty.exe thing with no avail. When I go to "device information" it reads like this:
ROM version: 3.60.110.4
ROM date: 09/05/07
Radio version: SAYS NOTHING!!!!
Protocol version: SAYS NOTHING!!
IMEI: SAYS NOTHING!!
When I do a soft reset I get red letters and numbers appearing and not the "no gsm" message.
This is a 2nd hand phone off of ebay as my original phone was stolen. I have contacted Tmobile, but they refuse to help me as its not the original phone that I bought.
I would be most grateful for any help you can give me!!
Thanks,
April
OK, firstly.....flash hardspl.........instructions here
Next flash ANY radio......try version 1.48.00.10.
with the device booted up and synched with Activesync, download the radio ROM, unzip and run the RUUprogram (the only exe in the zip).
select autodetect, it should highlite SPL v2.10 and tick the "HardSPL?" box.
go through each screen and accept everything......the radio will be flashed.
Hopefully your device will work properly after this.
uh oh...
Thanks so much for your speedy response. Obviously I managed to screw this up.
got to this stage
"select autodetect, it should highlite SPL v2.10 and tick the "HardSPL?" box."
It didnt autodetect, so selected SPL v2.10 and ticked "HardSPL" box manually. Went through all the other bits and when it starts to do its thing it just sits at 0% then i get error message "ERROR 262: UPDATE ERROR. The rom update utility has encountered communication errors during the update process. THe program will guide you step by step to recover from the errors so you can continue with the update."
So I followed the recovery process instructions several times. Nothing has worked. Have tried restarting my computer and doing a hard reset on phone, and stuck with the bootloader screen reading IPL 1.04 and HERM300 SPL-2.10.01Olipro.
Manage to get back to this stage
"select autodetect, it should highlite SPL v2.10 and tick the "HardSPL?" box."
and go through the ticks but always ends up with error message 262.
SORRY!
Sorry to hear about your problems.
Was it the official T-Mobile WM6 ?
If so it was another 1.50 Radio!
I have same now!
http://forum.xda-developers.com/showthread.php?t=357275
I read in another thread try putting phone in fridge for 15mins first without the battery.
Good Luck
fridge vs. floor
Yes, it was the official WM6 from T-Mobile.
Im worried now that my limited experience with flashing, cooking, and now crying will leave me with a proper "brick".
I will try the fridge thing, if I ever get it to loads WM6 again but for the mean time, I will continue to throw it on the floor.
What do you mean by it was another 1.50 radio? I dont know what version I once had, but as suggested by mrvanx, I was trying to upload the 1.48.00.01.
Again apologies for my complete ignorance, but Im sure there are others that share my stupidity and will benefit from me asking goofy questions. If anyone else has any more simpleton advice on how to revive my poor phone, I would be much obliged!
Thanks,
April
The 1.50 radio bit; If it was the official T-Mobile WM6 upgrade, then your radio will have been 1.50 (I am pretty sure)
I dont know what else to do!!??
Ok since trying to update my radio from nothing to 1.48.00.01 and receiving error message 262 during the update, my phone now only goes into bootloader mode reading the following:
HERM300
IPL-1.04
SPL-2.10.0lipro
I have tried the following to bring it back to life (but not in any particular order):
- restarted my pc several times
- made sure my Windows XP SP2 was up to date
- made sure I had .net framework up to date
- hard reset on phone
- soft reset on phone
- leaving battery out overnight
- updating SPL to 2.10.0lipro (again) doesnt get to any percentage, just straight to error 260
- updating radio to 1.48.00.01 (again) - wont autodetect. tried radio button SPL2.10, then just force safe, then just HardSPL. each option dies at 0% then error message 262)
- reinstalling TMobile version WM6 (again) - dies at 11% - error message 262
I saw the post by pof "How to unbrick your bricked hermes" and the solution was to "Flash any radio in NBH format", but I cant figure out how to do that!? (I have tried clicking on the nbh file in the downloaded radio folder, but dont know what program to use to unload all the info. Have also looked at all the links on "Radio sudden death issue knowledge consolidation" and nothing has helped.
Sorry again guys, but can someone please help
If not, does anyone want to buy my brick?
alachlan said:
Sorry again guys, but can someone please help
If not, does anyone want to buy my brick?
Click to expand...
Click to collapse
Dude - there are enough bricks around these parts to build a 500 story repair centre! All we need is MS to merge their NT, CE and ME technologies into CEMENT then we can hold all the bricks together
Error 260 (comms error) is usually caused by using Vista without "fixing" it or Win2K/XP without the .net framework on it
Error 262 is USB port not available - turning hermes off and on (or removing the battery if that fails) at that point and putting it manually into bootloader usually cures that one then continuing with the flash.
Incorrect.
Its more than likely this Vario II was irepairably bricked before the TC bought it, the Radio upgrade is failing on a Tmobile official ROM (which includes a radio) and on a standard CustomRUU upgrade for the radio only.
A "checkimage" command in mtty would probabaly return a failed radio checksum and following on from that the mtty commands to get into the radio bootloader will fail (rtask a......then rversion).
Also there may be a corrupted CID on the device which again isnt good.
Ive seen these types of bricks MANY times.
Sorry dude, looks like your Hermes was a paperweight when you bought it.
Never thought of that - shameful given the amount of radio investigating I've done recently Too busy on 260's with part flashes from people not installing .net (also the amount of hits you should be getting to your vista guide now is scary!)
Still say we should collect up all the bricks and build a repair centre
Mikeapollo said:
.....the amount of hits you should be getting to your vista guide now is scary!....
Click to expand...
Click to collapse
73039 hits according to the site
Pretty much the only fatal brick now is a damaged radio/CID flash. If there was a way for Olipro/Pof/Us to flash a hardspl type package in place of the radio bootloader then it would be solid.
What type of mortar should we use?
mrvanx said:
73039 hits according to the site
Pretty much the only fatal brick now is a damaged radio/CID flash. If there was a way for Olipro/Pof/Us to flash a hardspl type package in place of the radio bootloader then it would be solid.
Click to expand...
Click to collapse
Yup.. Must admit I think that's the one thing that will not happen anytime soon as the interactions between bootloader, radio bootloader and the radio PLA/PIC is a tad complex... It'll be a very difficult thing to test and even finding a suitable vunerability is difficult - certainly beyond my abilities presently. Though the same was said 12 months ago about the No-Wifi issue and Olipro led some excellent progress in that area...
Mind you - the key to fixing CID/radio bricks is to educate the masses not to make them in the first place and not to just blindly execute whatever they stumble across - more of a challenge than rewriting the bootloader by hand on paper tape and almost as frustrating
Oh... as for Mortar... we could have a mass scrape of all that weird dirt stuff that "grows" under the "invisible-until-you-open-it" edges of the screens and around the battery cover and add a drop of water
Wonder if it's the electronic equivelent of belly button fluff?
does that mean its dead?
Thanks for all the entertaining posts guys. Just to clarify things, Im running XP SP2, and the phone did actually work for about 3 months until suddenly one day it gradually started dropping signal, until the signal vanished completely.
Are you guys trying to tell me that my phone is completely dead then? Could I have prevented this by knowing what the hell I was doing or was it a fault of the phone?
With regards to the mortar issue I think a combination of tears and sh*t would do. I think I would build a big wall around the jackasses who release products that arent completely stable but still charge us an arm and a leg for them. (excuse my grumpiness)
Oh and just wanted to say that since my vario has been out of action, I have been relying on the trustiest brick Ive ever owned, my XDA IIs. This thing has been dropped so many times and is held together with super glue, but it does the job and gets on with things, just not very quickly.
Thanks again for all the help.
alachlan said:
Thanks for all the entertaining posts guys. Just to clarify things, Im running XP SP2, and the phone did actually work for about 3 months until suddenly one day it gradually started dropping signal, until the signal vanished completely.
Are you guys trying to tell me that my phone is completely dead then? Could I have prevented this by knowing what the hell I was doing or was it a fault of the phone?
With regards to the mortar issue I think a combination of tears and sh*t would do. I think I would build a big wall around the jackasses who release products that arent completely stable but still charge us an arm and a leg for them. (excuse my grumpiness)
Oh and just wanted to say that since my vario has been out of action, I have been relying on the trustiest brick Ive ever owned, my XDA IIs. This thing has been dropped so many times and is held together with super glue, but it does the job and gets on with things, just not very quickly.
Thanks again for all the help.
Click to expand...
Click to collapse
By the sounds of it you might have a permenant brick but unless i had your device here and actually went through everything myself i cant be sure. take a read through the sticky thread above this one about unbricking......it will take some time to read through but you will see what techniques are used to try and revive the device.
when cid corruped with spl 2.03 and not have gsm no solution can not flash with sd card when you see that level=fff only when level=0 in mtty console can use sd card for flashing rom.
THIS TIME ONLY SOLUTION TO UNBRICK HERMES WITH SPL 2.03 NO CID AND IMEI -
SENT Imei-check to fix this ??
?
uuuummm....
Thanks mbsshop1302gsm for the response, but did I mention that I have limited knowledge on this stuff? So the more basic the instructions are, the better.
Thanks,
April
HEY ALL,
I AM A FAIRLY EXPERIENCED USER WITH WM DEVICES, IN FACT I HAVE PUT TOGETHER SOME DECENT ROMS FOR THE KAISER, BUT I AM PRETTY NEW TO THE ADVANTAGE AS I JUST PICKED ONE UP LAST WEEK. PLEASE EXCUSE MY IGNORANCE IN THIS ISSUE, AS IT SEEMS JUST AN ISSUE OF ME MAKING AN EXTREMELY "ROOKIE" MISTAKE.
I HAVE READ, READ, READ AND READ SOME MORE, AS ONE SHOULD ALWAYS DO, BUT SOME HOW I GOT MYSELF INTO SOME TROUBLE WHILE RUNNING THE ATHENA UNLOCKER ON MY ADVANTAGE X7501... BIG TROUBLE...
I RAN THE UNLOCKER, AND FELT PRETTY COMFORTABLE WITH THE PROCESS, BUT WHILE THE UNLOCKER WAS RUNNING, AFTER IT ALLOOWED ME TO BACK UP MY SPL, IT WAS RUNNING SCRIPTS AS USUAL, AND I RECIVED AN UNUSUAL WINDOWS ERROR WITH THE UNLOCKER APP (PROGRAMS HAS EXPERIENCED ABNORMAL ACTIVITY OR SOMETHING TO THAT EFFECT...) THEN GAVE ME THE OPTION TO CONTINUE OR QUIT, SO I CHOSE CONTINUE, BUT THE DEVICE DID NOTHING MORE AND THE UNLOCKER BASICALLY FROZE. THE PC WAS "OK", AS FAR AS NOT BEING FROZE UP, BUT THE UNLOCKER WOULD NOT MOVE ANOTHER STEP! AFTER WAITING NEARLY AN HOUR, I DECIDED TO DISCONNECT (BAD IDEA, I SHOULD HAVE KNOWN BETTER, I REALIZE THIS PROBLEM IS BY ALL MEANS MY OWN FAULT!).
AFTER DISCNNECT, DEVICE APPEARED FINE UNTIL FIRST SOFT RESET, THEN I GOT NO BOOT, NO BOOTLOADER WITH ANY KEY COMBINATION, AND NOTHING ELSE. I CAN GET DEVICE TO WHAT WOULD NORMALLY BE THE STANDARD BL SCREEN, BUT NO OLIPRO SPL, NO WRITING AT ALL, AND NO SERIAL OR USB WHEN CONNECTED OR DISCONNECTED FROM PC! ALL I HAVE IS TRI-COLOR SCREEN WITH NO WRITING, REGARDLESS OF KEY/RESET COMBINATIONS THAT I HAVE TRIED, WHICH I BELIEVE ARE ALL OF THEM!
I AM OUT OF OPTIONS, I WAS HOPING SOME OF MY FELLOW XDA FOLKS COULD HELP AN "IDIOT" IN NEED! I WOULD CERTAINLY APPRECIATE IT !
ALSO I WOULD GLADLY PROVIDE ANY MORE INFO IF NEEDED FOR FURHTER ADVICE. THANKS IN ADVANCE.
Hey All,
Thanks For All Of Your Helpful Advice, Unfortunately, I Think Im In A Little Deeper Than That
Bairda(Alex), I Looked At Your Screen Shots From Your Post, And Yea!!! That Is Exactly What My Device Looks Like!!! I Can Load The Bootloader, But Tricolor Only!!!! No Letters/ Version Numbers/ Anything!!!! I Really Dont Know What Else To Try, As I Know How To Flash A Rom From The Storage Card, But I Cannot Even Get The Bootloader To Load Properly!!! Any Advice Alex- Or Anyone Else?
Again, Got Disconnected After Having Issue With 3 Step Unlocker, After 1st Soft Reset, No Boot/ No Os/ Not Bootloader Screen With Ver Numbers And Spl/.... Only Tricolor With No Writing!!! I Have Attatched Alex's Thumbnails, As It Is Exactly What Mine Is Doing... (hope Thats Ok Bairda (Alex!))
Also, Just Note That I Am Running Vista Home Premium, With All The Latest Updates/service Packs...
Please See Pics And I Would Appreciate A Minute Of Anyones Time To Get This Thing Going... Also, I Would Of Course Be Willing To Make A Donation Of What Ever I Can Scrounge Up For Some Assistance On This Issue!
Thanks So Much!!!
Attached Images
OK EVERYONE, MY PROBLEM IS RESOLVED, BUT I WANTED TO POST EXACTLY WHAT HAPPENED FOR EVERYONE TO SEE, ESPECIALLY FOR NEW FOLKS... AFTER HAVING THE ISSUES ABOVE, I CONSULTED WITH MANY PEOPLE TO TRY MANY, MANY METHODS OF RECOVERING THE DEVICE. ALL ATTEMPTS TO RECOVER WERE UNSUCCESSFUL, AS IT APPEARS THAT I USED THE INCORRECT UNLOCKER!!!
BASICALLY, THE UNLOCKER THAT I USED IS THE OLDER ONE, THAT SHOULD NEVER BE USED ANYMORE! AFTER THE SPL WAS ERASED, THE PROCESS ENCOUNTERED AN ERROR BEFORE IT WAS ABLE TO RE-FLASH THE NEW SPL. I HAPPENED TO CALL HTC AS A LAST RESORT, AN ONLY TOLD THEM THAT MY PHONE WOULD NOT TURN ON. I THEN SENT IT TO THEM, AND THEY TOLD ME THAT EVEN THOUGH I PURCHASED THE DEVICE USED, IT IS STILL UNDER WARRANTY DURING THE APPLICABLE DATES (WHICH IS 15 MONTHS FROM DATE OF MFG).
SO IN SHORT, THEY REPLACED MY MOTHERBOARD, AS THEY FLASH MEMORY CHIP WAS UNABLE TO BE RE-FLASHED. LUCKLIY, I WAS ABLE TO GET MY DEVICE REPLACED AT NO COST, BUT THIS MISTAKE COULD COST SOMEONE A $1000 DEVICE!!!
AS A RECAP, I AM LISTING A LINK TO THE GOOD ADVANTAGE X7501 UNLOCKER, AND A LINK TO THE OLD ONE, WHICH SHOULD NOT BE USED FOR THE X7501, IN MY EXPERIENCE... IT WAS ALSO CONFIRMED BY A REPUTABLE SENIOR MEMBER THAT THE OLD/BAD UNLOCKER SHOULD NOT BE USED AS WELL.
-GOOD/SAFE X7501 UNLOCKER: (FILE CALLED ATHENAWRAPPER, IN FIRST POST): http://forum.xda-developers.com/showthread.php?t=316846
-BAD/OLD X7501 UNLOCKER, READ 1ST POST: http://forum.xda-developers.com/showthread.php?t=315831
HOPE THIS INFORMATION IS USEFUL FOR EVERYONE! IF ANY OF THIS IS INCORRECT, PLEASE FEEL FREE TO COMMENT, BUT THIS IS WHAT MY EXPERIENCE LED TO.
__________________
HTC ADVANTAGE X7501 AT&T TILT 8925 VERIZON XV6700
THEQUARTZGUY said:
HEY ALL,
I AM A FAIRLY EXPERIENCED USER WITH WM DEVICES, IN FACT I HAVE PUT TOGETHER SOME DECENT ROMS FOR THE KAISER, BUT I AM PRETTY NEW TO THE ADVANTAGE AS I JUST PICKED ONE UP LAST WEEK. PLEASE EXCUSE MY IGNORANCE IN THIS ISSUE, AS IT SEEMS JUST AN ISSUE OF ME MAKING AN EXTREMELY "ROOKIE" MISTAKE.
I HAVE READ, READ, READ AND READ SOME MORE, AS ONE SHOULD ALWAYS DO, BUT SOME HOW I GOT MYSELF INTO SOME TROUBLE WHILE RUNNING THE ATHENA UNLOCKER ON MY ADVANTAGE X7501... BIG TROUBLE...
I RAN THE UNLOCKER, AND FELT PRETTY COMFORTABLE WITH THE PROCESS, BUT WHILE THE UNLOCKER WAS RUNNING, AFTER IT ALLOOWED ME TO BACK UP MY SPL, IT WAS RUNNING SCRIPTS AS USUAL, AND I RECIVED AN UNUSUAL WINDOWS ERROR WITH THE UNLOCKER APP (PROGRAMS HAS EXPERIENCED ABNORMAL ACTIVITY OR SOMETHING TO THAT EFFECT...) THEN GAVE ME THE OPTION TO CONTINUE OR QUIT, SO I CHOSE CONTINUE, BUT THE DEVICE DID NOTHING MORE AND THE UNLOCKER BASICALLY FROZE. THE PC WAS "OK", AS FAR AS NOT BEING FROZE UP, BUT THE UNLOCKER WOULD NOT MOVE ANOTHER STEP! AFTER WAITING NEARLY AN HOUR, I DECIDED TO DISCONNECT (BAD IDEA, I SHOULD HAVE KNOWN BETTER, I REALIZE THIS PROBLEM IS BY ALL MEANS MY OWN FAULT!).
AFTER DISCNNECT, DEVICE APPEARED FINE UNTIL FIRST SOFT RESET, THEN I GOT NO BOOT, NO BOOTLOADER WITH ANY KEY COMBINATION, AND NOTHING ELSE. I CAN GET DEVICE TO WHAT WOULD NORMALLY BE THE STANDARD BL SCREEN, BUT NO OLIPRO SPL, NO WRITING AT ALL, AND NO SERIAL OR USB WHEN CONNECTED OR DISCONNECTED FROM PC! ALL I HAVE IS TRI-COLOR SCREEN WITH NO WRITING, REGARDLESS OF KEY/RESET COMBINATIONS THAT I HAVE TRIED, WHICH I BELIEVE ARE ALL OF THEM!
I AM OUT OF OPTIONS, I WAS HOPING SOME OF MY FELLOW XDA FOLKS COULD HELP AN "IDIOT" IN NEED! I WOULD CERTAINLY APPRECIATE IT !
ALSO I WOULD GLADLY PROVIDE ANY MORE INFO IF NEEDED FOR FURHTER ADVICE. THANKS IN ADVANCE.
SORRY FOR LONG POST, JUST TRYING TO PROVIDE AS MUCH INFO AS POSSIBLE...
Click to expand...
Click to collapse
Hi
You could try Hard Reset BY Volume down+Stylus reset. if it turns on and load OS then you can use the unlocker again without Sim and Memory card(but your pc must have netframe work 2.0 installed and updated). If your device failed to load OS then you have to find the original rom for your device (which you can download from this website "use the search function") then unlock your device with olipro's latest unlocker.
Good luck
I got this once when I tried to flash from the memory card.
Remove both memory and sim card and battery for 10 mins.
make sure you are disconnected from the puter.
put battery in and hold the camerabutton all the way in and press the reset pin and hopefully you will enter the bootloader proper.
Which version of olipros unlocker did you use
Try to use the last version as it is less prone to trouble and works better on x7501
see this post as well(though not exactly your problem)
http://forum.xda-developers.com/showthread.php?t=374734
I would also recommend flashing from an xppro machine with the latest activesync
just reinforcing above post as well
I had a similar problem which I outlined here...
http://forum.xda-developers.com/showthread.php?t=368312
Notice the screenshots about a third of the way down.
Does your Advantage bootscreen look like this?
-Alex-
try inserting an SD card and boot to this strange bootloader screen
does it say Loading (then No image found)?
also, i assume you mean the PC does not see the device either?
what athena version have you all got? x7501? brand new? maybe HTC changed something about them...
Still No Luck!!! Any More Advice? It Would Be Appreciated...
Hey All,
Thanks For All Of Your Helpful Advice, Unfortunately, I Think Im In A Little Deeper Than That
Bairda (Alex), I Looked At Your Screen Shots From Your Post, And Yea!!! That Is Exactly What My Device Looks Like!!! I Can Load The Bootloader, But Tricolor Only!!!! No Letters/ Version Numbers/ Anything!!!! I Really Dont Know What Else To Try, As I Know How To Flash A Rom From The Storage Card, But I Cannot Even Get The Bootloader To Load Properly!!! Any Advice Bairda (Alex)- Or Anyone Else?
Again, Got Disconnected After Having Issue With 3 Step Unlocker, After 1st Soft Reset, No Boot/ No Os/ Not Bootloader Screen With Ver Numbers And Spl/.... Only Tricolor With No Writing!!! I Have Attatched Alex's Thumbnails, As It Is Exactly What Mine Is Doing... (hope Thats Ok Bairda (Alex)!)
Also, Just Note That I Am Running Vista Home Premium, With All The Latest Updates/service Packs...
Please See Pics And I Would Appreciate A Minute Of Anyones Time To Get This Thing Going... Also, I Would Of Course Be Willing To Make A Donation Of What Ever I Can Scrounge Up For Some Assistance On This Issue!
Thanks So Much!!!
PLEASE FEEL FREE TO PM IF YOU HAVE ANY INFO AT ALL THAT COULD HELP A GUY OUT! THX!
if it can't load an image from SD and PC (with XP) can't see the device, then it needs to be sent back, if possible under warranty
bad choice
hay there first time some thing like that happen to me i was stuck for hours but then i got into boot loader in flashed the pk 3.0 and it worked so if u can see the olipro 1.20 thing then its all good and if u cant then mabee ur f***d that type of error u got its supose to cum near the end
THEQUARTZGUY said:
Hey All,
Thanks For All Of Your Helpful Advice, Unfortunately, I Think Im In A Little Deeper Than That
Bairda (Alex), I Looked At Your Screen Shots From Your Post, And Yea!!! That Is Exactly What My Device Looks Like!!! I Can Load The Bootloader, But Tricolor Only!!!! No Letters/ Version Numbers/ Anything!!!! I Really Dont Know What Else To Try, As I Know How To Flash A Rom From The Storage Card, But I Cannot Even Get The Bootloader To Load Properly!!! Any Advice Bairda (Alex)- Or Anyone Else?
Again, Got Disconnected After Having Issue With 3 Step Unlocker, After 1st Soft Reset, No Boot/ No Os/ Not Bootloader Screen With Ver Numbers And Spl/.... Only Tricolor With No Writing!!! I Have Attatched Alex's Thumbnails, As It Is Exactly What Mine Is Doing... (hope Thats Ok Bairda (Alex)!)
Also, Just Note That I Am Running Vista Home Premium, With All The Latest Updates/service Packs...
Please See Pics And I Would Appreciate A Minute Of Anyones Time To Get This Thing Going... Also, I Would Of Course Be Willing To Make A Donation Of What Ever I Can Scrounge Up For Some Assistance On This Issue!
Thanks So Much!!!
PLEASE FEEL FREE TO PM ME OR EMAIL ME AT [email protected] IF YOU HAVE ANY INFO AT ALL THAT COULD HELP A GUY OUT! THX!
Click to expand...
Click to collapse
Sorry that you are having the same problems that I did. Unfortunately, I can't bring you much comfort as I tried everything that I could find or was suggested. I searched every post and put out multiple cross-postings (that is a real sign of desperation for me!). Ultimately I had to get a new unit from Amazon as I could NOT get it back from the land of rainbow death that you see in the pics. I am no expert with the Athena/Advantage but I am also pretty experienced with computers and rarely ever get myself into a no-win like this. It takes alot for me to give up and declare a piece of equipment beyond my ability to fix, but this was one of those times.
I think that I traced the eventual cause to one (or a combination) of the following:
- Leaving the SIM and the Mini SD in the unit during the flash process
- Some glitch when using vista with the bootloader
- Using an older version of the OliPro unlocker (very likely the cause)
- Somehow panicing during the unlock and interupting the upgrade. You MUST do all three steps of the unlock to be safe.
I repeated the unlock with replacement unit being careful to use the latest bulletproof unlock and had no problems. But the original unit did have to go back.
I sincerely hope that you have better luck! Tell me how it turns out! If there is any other info you think you might be able to use from my experience, please ask away!
-Alex-
bairda said:
You MUST do all three steps of the unlock to be safe.
Click to expand...
Click to collapse
nope, the second and third steps are only for sim unlocking
But if you what to uprage a new Radio you have to do a SIM unlock?
cmonex said:
nope, the second and third steps are only for sim unlocking
Click to expand...
Click to collapse
I stand corrected.
I would caution though, that for new users it would be best to follow the procedure through all 3 steps. As I understand it there is no harm in doing this other than the increase cost in time and effort and may be less confusing and safer then just doing the first.
Is this correct?
-Alex-
marthynovak said:
But if you what to uprage a new Radio you have to do a SIM unlock?
Click to expand...
Click to collapse
nope, it's got nothing to do with the radio version
it's another area where simunlock info is stored
bairda said:
I stand corrected.
I would caution though, that for new users it would be best to follow the procedure through all 3 steps. As I understand it there is no harm in doing this other than the increase cost in time and effort and may be less confusing and safer then just doing the first.
Is this correct?
-Alex-
Click to expand...
Click to collapse
well it can't do much harm, of course less flashing means less risk, and step 2 and step 3 both flash a radio.
as a newbie i'd imagine it's easier to just do step 1 because step 2 can cause corruption to the OS so it needs to be reflashed and the black screen scares the newbies etc.
What I have noticed reading this board too is that sometimes the type of USB cables used matters. I do not know why, but this happened to me too. I failed at step #2 and couldn't figure it our why. To resolve this I changed everything. From computer to usb cables to fresh files, to restore old image and re-tried the process and it worked.
Also one thing I noticed is that the old unlocked is linked allot instead of the new unlocker which is almost bullet proof. Some folks did download the old unlocker and tried it on their x7501 and bricked their device....
Palonek's Business Management Systems and development http://www.edward-palonek.com/
Problem Resolved!!! Please Read, Very Important Information!!!
OK EVERYONE, MY PROBLEM IS RESOLVED, BUT I WANTED TO POST EXACTLY WHAT HAPPENED FOR EVERYONE TO SEE, ESPECIALLY FOR NEW FOLKS... AFTER HAVING THE ISSUES ABOVE, I CONSULTED WITH MANY PEOPLE TO TRY MANY, MANY METHODS OF RECOVERING THE DEVICE. ALL ATTEMPTS TO RECOVER WERE UNSUCCESSFUL, AS IT APPEARS THAT I USED THE INCORRECT UNLOCKER!!!
BASICALLY, THE UNLOCKER THAT I USED IS THE OLDER ONE, THAT SHOULD NEVER BE USED ANYMORE! AFTER THE SPL WAS ERASED, THE PROCESS ENCOUNTERED AN ERROR BEFORE IT WAS ABLE TO RE-FLASH THE NEW SPL. I HAPPENED TO CALL HTC AS A LAST RESORT, AN ONLY TOLD THEM THAT MY PHONE WOULD NOT TURN ON. I THEN SENT IT TO THEM, AND THEY TOLD ME THAT EVEN THOUGH I PURCHASED THE DEVICE USED, IT IS STILL UNDER WARRANTY DURING THE APPLICABLE DATES (WHICH IS 15 MONTHS FROM DATE OF MFG).
SO IN SHORT, THEY REPLACED MY MOTHERBOARD, AS THEY FLASH MEMORY CHIP WAS UNABLE TO BE RE-FLASHED. LUCKLIY, I WAS ABLE TO GET MY DEVICE REPLACED AT NO COST, BUT THIS MISTAKE COULD COST SOMEONE A $1000 DEVICE!!!
AS A RECAP, I AM LISTING A LINK TO THE GOOD ADVANTAGE X7501 UNLOCKER, AND A LINK TO THE OLD ONE, WHICH SHOULD NOT BE USED FOR THE X7501, IN MY EXPERIENCE... IT WAS ALSO CONFIRMED BY A REPUTABLE SENIOR MEMBER THAT THE OLD/BAD UNLOCKER SHOULD NOT BE USED AS WELL.
-GOOD/SAFE X7501 UNLOCKER: (FILE CALLED ATHENAWRAPPER, IN FIRST POST): http://forum.xda-developers.com/showthread.php?t=316846
-BAD/OLD X7501 UNLOCKER, READ 1ST POST: http://forum.xda-developers.com/showthread.php?t=315831
HOPE THIS INFORMATION IS USEFUL FOR EVERYONE! IF ANY OF THIS IS INCORRECT, PLEASE FEEL FREE TO COMMENT, BUT THIS IS WHAT MY EXPERIENCE LED TO.
THEQUARTZGUY said:
OK EVERYONE, MY PROBLEM IS RESOLVED, BUT I WANTED TO POST EXACTLY WHAT HAPPENED FOR EVERYONE TO SEE, ESPECIALLY FOR NEW FOLKS... AFTER HAVING THE ISSUES ABOVE, I CONSULTED WITH MANY PEOPLE TO TRY MANY, MANY METHODS OF RECOVERING THE DEVICE. ALL ATTEMPTS TO RECOVER WERE UNSUCCESSFUL, AS IT APPEARS THAT I USED THE INCORRECT UNLOCKER!!!
BASICALLY, THE UNLOCKER THAT I USED IS THE OLDER ONE, THAT SHOULD NEVER BE USED ANYMORE! AFTER THE SPL WAS ERASED, THE PROCESS ENCOUNTERED AN ERROR BEFORE IT WAS ABLE TO RE-FLASH THE NEW SPL. I HAPPENED TO CALL HTC AS A LAST RESORT, AN ONLY TOLD THEM THAT MY PHONE WOULD NOT TURN ON. I THEN SENT IT TO THEM, AND THEY TOLD ME THAT EVEN THOUGH I PURCHASED THE DEVICE USED, IT IS STILL UNDER WARRANTY DURING THE APPLICABLE DATES (WHICH IS 15 MONTHS FROM DATE OF MFG).
SO IN SHORT, THEY REPLACED MY MOTHERBOARD, AS THEY FLASH MEMORY CHIP WAS UNABLE TO BE RE-FLASHED. LUCKLIY, I WAS ABLE TO GET MY DEVICE REPLACED AT NO COST, BUT THIS MISTAKE COULD COST SOMEONE A $1000 DEVICE!!!
AS A RECAP, I AM LISTING A LINK TO THE GOOD ADVANTAGE X7501 UNLOCKER, AND A LINK TO THE OLD ONE, WHICH SHOULD NOT BE USED FOR THE X7501, IN MY EXPERIENCE... IT WAS ALSO CONFIRMED BY A REPUTABLE SENIOR MEMBER THAT THE OLD/BAD UNLOCKER SHOULD NOT BE USED AS WELL.
-GOOD/SAFE X7501 UNLOCKER: (FILE CALLED ATHENAWRAPPER, IN FIRST POST): http://forum.xda-developers.com/showthread.php?t=316846
-BAD/OLD X7501 UNLOCKER, READ 1ST POST: http://forum.xda-developers.com/showthread.php?t=315831
HOPE THIS INFORMATION IS USEFUL FOR EVERYONE! IF ANY OF THIS IS INCORRECT, PLEASE FEEL FREE TO COMMENT, BUT THIS IS WHAT MY EXPERIENCE LED TO.
Click to expand...
Click to collapse
Hi there,
Thanks indeed for the important info. I haven't yet tried the unlocker. But to my understanding the link " -BAD/OLD X7501 UNLOCKER, READ 1ST POST: http://forum.xda-developers.com/showthread.php?t=315831"
points to the latest version of the unlocker. The file I have downloaded is dated in November 2007. This is not correct? And what does the wrapper mean?
Could you please explain? I bought my X7501 in the US, but live in Europe and such a mistake could be totally fatal!
Thanks for your feedback.
Regarding The "bad" Unlocker....
Hey Dodonian / Everyone,
Yea, I Agree That It Is Somewhat Confusing About The "latest" Unlocker Version, But While Dealing With The Issues I Have Had Lately, I Spoke With Olipro, Who Makes The Unlocker, And When I Sent Him The Link That I Labeled Bad In The Last Post, He Replied That It Appeared I Had Tried The Older One, And That The Link To The Other One Labeled "good" Was Infact The Best One.
I Could, I Guess, In Some Way Be Mislead Here, But Just For Your Info, I Did Just Receive My Fixed Advantage X7501 Today, And Immediately Ran The "athena_wrapper" Which Is Availible On The "good" Link That I Posted. It Ran Good And Flashed Directly From The Bootloader. Afterwards, I Was Able To Flash My Own Custom Rom With No Difficulty, And All Went Well.
Hope This Answers Your Question!
---ryan
THEQUARTZGUY said:
Hey Dodonian / Everyone,
Yea, I Agree That It Is Somewhat Confusing About The "latest" Unlocker Version, But While Dealing With The Issues I Have Had Lately, I Spoke With Olipro, Who Makes The Unlocker, And When I Sent Him The Link That I Labeled Bad In The Last Post, He Replied That It Appeared I Had Tried The Older One, And That The Link To The Other One Labeled "good" Was Infact The Best One.
I Could, I Guess, In Some Way Be Mislead Here, But Just For Your Info, I Did Just Receive My Fixed Advantage X7501 Today, And Immediately Ran The "athena_wrapper" Which Is Availible On The "good" Link That I Posted. It Ran Good And Flashed Directly From The Bootloader. Afterwards, I Was Able To Flash My Own Custom Rom With No Difficulty, And All Went Well.
Hope This Answers Your Question!
---ryan
Click to expand...
Click to collapse
Thanks Ryan!
I see. I know that the X7501 is sold unlocked in the US and therefore only the 1st step of flashing the SPL would make sense. That means that if run the athena wrapper, all will be OK for flashing radio, ROM etc. I that correct?
Two more questions, if you don't mind.
1.Did you need to install .NET to run the Athena wrapper?, or is it kind of pre-installed mostly?
2.What is your experience with the cooked ROMs? Running stable? Can you flash back the original ROM if required?
Thanks
Dod.
I ran the 'wrapper' this week, step 1 only, so I could upgrade the radio driver. I first ran the bad unlocker and got the 'black screen of death', but after reflashing a good ROM, then the good 'wraapper', then the latest radio all is well.
Hi,
First of all, here are the facts:
0- I've an EU RAPH1000 CID: RAPH__023.
1- I'm always using HardSPL on my device. (SPL 1.90 OliNex)
2- I'm always flashing from my Micro-SD
3- I've flashed for the first time from AS the latest ATT test radio (1.12.25.19 OS AKU 1.4.6 Build 20771), nothing special.
4- My TP hangs on the first screen at boot (the screen showing the RADIO/Protocol/ROM versions and hangs).
5- I can access to the bootloader screen (tri color). I gues now that I can reflash. (great news)
6- I reflashed back my old RADIO (.25.01) - device still bricked.
7- I reflashed back different OSs - device still bricked.
8- I've tried the Raph system Diag 5.02c nbh. made the whole function tests - All the tests were OK but the "F/T 1" USB sync doens't work ? (I dunno how to test that) - The device still bricked.
9- I've formated the nand - The device still bricked.
10- I'm thinking about to use remote access to see what's happening inside the device using mtty but I dont know the different commands ( and I dont wanna kill all my chances ) so this is why I ask you some help.
Can any one tells me the mtty diag/edit commands () ? is there something specific about using mtty on RAPH ? which is the latest version ? is the access password the same for all HTC devices ?
BTW, did you have the same problem before on RAPH, and of course do you have any advise for me ?
I know I can use my warranty, but I ask here for a technical "do it your self" support . I want to understand, some of the Nand/Flashing hacks and make a full use of my devices, thanx to the xda community experts.
Your help will be really appreciated, for me and perhaps for future RAPH users.
Cheers
/torpie13
u can try flashing an os that already has a radio included. check these out http://forum.xda-developers.com/showthread.php?t=487994
http://forum.xda-developers.com/showthread.php?t=478657
best of luck
alcadeias said:
u can try flashing an os that already has a radio included. check these out http://forum.xda-developers.com/showthread.php?t=487994
http://forum.xda-developers.com/showthread.php?t=478657
best of luck
Click to expand...
Click to collapse
This was the ROM that caused the brick on my device .
torpie13 said:
Hi,
First of all, here are the facts:
0- I've an EU RAPH1000 CID: RAPH__023.
1- I'm always using HardSPL on my device. (SPL 1.90 OliNex)
2- I'm always flashing from my Micro-SD
3- I've flashed for the first time from AS the latest ATT test radio (1.12.25.19 OS AKU 1.4.6 Build 20771), nothing special.
4- My TP hangs on the first screen at boot (the screen showing the RADIO/Protocol/ROM versions and hangs).
5- I can access to the bootloader screen (tri color). I gues now that I can reflash. (great news)
6- I reflashed back my old RADIO (.25.01) - device still bricked.
7- I reflashed back different OSs - device still bricked.
8- I've tried the Raph system Diag 5.02c nbh. made the whole function tests - All the tests were OK but the "F/T 1" USB sync doens't work ? (I dunno how to test that) - The device still bricked.
9- I've formated the nand - The device still bricked.
10- I'm thinking about to use remote access to see what's happening inside the device using mtty but I dont know the different commands ( and I dont wanna kill all my chances ) so this is why I ask you some help.
Can any one tells me the mtty diag/edit commands () ? is there something specific about using mtty on RAPH ? which is the latest version ? is the access password the same for all HTC devices ?
BTW, did you have the same problem before on RAPH, and of course do you have any advise for me ?
I know I can use my warranty, but I ask here for a technical "do it your self" support . I want to understand, some of the Nand/Flashing hacks and make a full use of my devices, thanx to the xda community experts.
Your help will be really appreciated, for me and perhaps for future RAPH users.
Cheers
/torpie13
Click to expand...
Click to collapse
if you can goto bootloader you can flash other rom again.(using Activesync to connect PPC&PC. in that case the ROM data can also be trasfered, be sure that your battery must be over 50%).
try to flash ship rom including radio, I thing your phone works again
torpie13 said:
This was the ROM that caused the brick on my device .
Click to expand...
Click to collapse
did u try the non att wwe version?
Did you try to hard reset your phone instead of trying to flash roms ?
When you tried to reflash an O/S or Radio, was it by activesync or the memory card?
BBowermaster said:
When you tried to reflash an O/S or Radio, was it by activesync or the memory card?
Click to expand...
Click to collapse
From the Micro-SD, no success
Kirakira said:
Did you try to hard reset your phone instead of trying to flash roms ?
Click to expand...
Click to collapse
Many times but no success
alcadeias said:
did u try the non att wwe version?
Click to expand...
Click to collapse
I've tried EnergyROM too. no success
I dunno if It there 's bad blocks on the Nand ? and how to access to the OEMSBL ? any one knows ?
torpie,
formatting the NAND wouldn't work-- are you doing it ala frankenkaiser? since you're using olinex' harspl the mtty commands for formatting the NAND are blocked.
you may have hit a bad NAND block and unfortunately in the section where the radio is being written. I had this case on my kaiser and even if I formatted it, bricked it, revived it, reflashed it, I can't get passed to the OS radio screen anymore. So off you go to warranty
torpie,
Correct me if I am wrong.
I thought the test AT&T ROM has a SPL 1.65 which will be flashed over your existing Hard SPL.
You may have to reflash Olipro's Hard SPL 1.60 first before flashing to other OS ROM.
pfcsabre said:
torpie,
formatting the NAND wouldn't work-- are you doing it ala frankenkaiser? since you're using olinex' harspl the mtty commands for formatting the NAND are blocked.
you may have hit a bad NAND block and unfortunately in the section where the radio is being written. I had this case on my kaiser and even if I formatted it, bricked it, revived it, reflashed it, I can't get passed to the OS radio screen anymore. So off you go to warranty
Click to expand...
Click to collapse
I'm using Raph system Diag 5.02c nbh to format, call duration was reseted to "0". But I dont know if/which partition was wiped ?
wmserver said:
torpie,
Correct me if I am wrong.
I thought the test AT&T ROM has a SPL 1.65 which will be flashed over your existing Hard SPL.
You may have to reflash Olipro's Hard SPL 1.60 first before flashing to other OS ROM.
Click to expand...
Click to collapse
As I'm using HardSPL, this one is write protected (?) and the new one wont overwrite it. I'm still having SPL 1.90 OliNex at boot loader
- But I don't know if the HTCEPassWord for RAPH is the same as the reversed one for the DIAMOND ?
- I don't know either if I can mount the partitions thru SPLbootloader/ RadioBL to retrive my DATA ? with mtty/qmat /dev/BlockDevice ???
- the device is in "security locked" state.
wmserver said:
torpie,
Correct me if I am wrong.
I thought the test AT&T ROM has a SPL 1.65 which will be flashed over your existing Hard SPL.
You may have to reflash Olipro's Hard SPL 1.60 first before flashing to other OS ROM.
Click to expand...
Click to collapse
That is not correct. I used the Test ROM for the radio and then immediately flashed another ROM after that. And I just confirmed by checking bootlloader and it is still 1.90
torpie13 said:
I'm using Raph system Diag 5.02c nbh to format, call duration was reseted to "0". But I dont know if/which partition was wiped ?
Click to expand...
Click to collapse
You remind me of rotohammer, you may want to pm him or cmonex
Here is his thread before: http://forum.xda-developers.com/showthread.php?t=435527
I'm not sure about this, but I recall from cmonex (or olipro) that the format command (task 2a) they've disabled it in the hardSPL (current one we are using).
Just to know, Is the HardSPL based on an MFG ?
Can I use the "info X" to check for bad NAND ?
If it's the case, is it safe to "task 2a" to recover this bad NAND ?
I just wanna be sure before proceeding
pfcsabre said:
You remind me of rotohammer, you may want to pm him or cmonex
Here is his thread before: http://forum.xda-developers.com/showthread.php?t=435527
I'm not sure about this, but I recall from cmonex (or olipro) that the format command (task 2a) they've disabled it in the hardSPL (current one we are using).
Click to expand...
Click to collapse
thank you, but I already saw that thread, but for my case I didn't modify anything special. And BTW this thread don't explain how they did to recover the situation.
ATM I'm reading allot about different IPL/SPL bootloader & AT commands. I'ts more comfortable with Putty (copy/past) so will use that (I m a lazy man I know). TBH, I wanna know what's wrong on my device, and try fixing things before using my warranty. (I don't even know if it still apply)
Here is the sammary:
1- charge your battery.
2- remove the SIM and SD cards.
3- inter the bootloader.
4- connect to the PC via USB cable and make sure the screen shows USB.
5- flash the latest stock ROM here http://www.genghis.be/_HTC%20Touch%20Pro_RUU_Raphael_HTC_Europe_5.05.401.1_R_Radio_Signed_Raphael_52.58.25.30_1.11.25.01_Ship.rar
6- when it comes to the ALIGN SCREEN part, hard reset.
7- preferably reinstall the HARD_SPL.
8-if it doesn't work, you may have needed to buy the Rhodium anyway... goodluck
torpie13 said:
thank you, but I already saw that thread, but for my case I didn't modify anything special. And BTW this thread don't explain how they did to recover the situation.
ATM I'm reading allot about different IPL/SPL bootloader & AT commands. I'ts more comfortable with Putty (copy/past) so will use that (I m a lazy man I know). TBH, I wanna know what's wrong on my device, and try fixing things before using my warranty. (I don't even know if it still apply)
Click to expand...
Click to collapse
I didn't imply your case as the same with rotohammers'. I told you, you remind me of rotohammer-- he doesn't want to return his TP for warranty unless he knows what's happening to it.
And if you've read about that thread already you won't be asking the task 2a if it's safe. I've told you before it has been disabled/removed in the hard spl that we're using.
AND if you really, really read that thread, the solution to that even though you say "this thread don't explain how they did to recover the situation." was a MFG SPL.
pfcsabre said:
I didn't imply your case as the same with rotohammers'. I told you, you remind me of rotohammer-- he doesn't want to return his TP for warranty unless he knows what's happening to it.
And if you've read about that thread already you won't be asking the task 2a if it's safe. I've told you before it has been disabled/removed in the hard spl that we're using.
AND if you really, really read that thread, the solution to that even though you say "this thread don't explain how they did to recover the situation." was a MFG SPL.
Click to expand...
Click to collapse
You're right; I've missed some critical information about "task 2a" but what i've learned is that this one will wipe the whole NAND (OEM , SPL , OEMSBL ...etc) and it's important to reflash at least the HardSPL just before applaying a task 8 (before reboot). Task 2a is indeed a dangerous command, so it's normal that they've disabled it
anyway, I didn't mean to hurt you by my answer. just to tell you that I've seen that thread. In that case please forgive me
I'm trying my last hope, flashing the whole stock ROM with the MFG SPL. And try to see what happends.
Cheers
Great News,
I've successfully restored my NAND using a Complete & stock ROM update (5.05) from the HTC Website.
Now I'm trying to understand what's happening, and how to avoid this problem again.
When I type the "info 8" command in the SPL shell, this is the output:
Cmd>info 8
info 8
--- 2K bytes sector version ---
DEVICE NAME=hynix_h8BES0UQ0MCP
DEVICE ID=0xBC
DEVICE MAKER ID=0xAD
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 4 (0x4) is reversed block
BLOCK 5 (0x5) is reversed block
BLOCK 7 (0x7) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 9 (0x9) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 15 (0xF) is reversed block
BLOCK 16 (0x10) is reversed block
BLOCK 17 (0x11) is reversed block
BLOCK 18 (0x12) is reversed block
BLOCK 19 (0x13) is reversed block
BLOCK 20 (0x14) is reversed block
BLOCK 21 (0x15) is reversed block
BLOCK 22 (0x16) is reversed block
BLOCK 23 (0x17) is reversed block
BLOCK 24 (0x18) is reversed block
BLOCK 25 (0x19) is reversed block
BLOCK 26 (0x1A) is reversed block
BLOCK 27 (0x1B) is reversed block
BLOCK 32 (0x20) is reversed block
BLOCK 134 (0x86) is bad block
BLOCK 805 (0x325) is bad block
BLOCK 979 (0x3D3) is bad block
BLOCK 981 (0x3D5) is bad block
BLOCK 991 (0x3DF) is bad block
BLOCK 1227 (0x4CB) is bad block
BLOCK 2038 (0x7F6) is bad block
BLOCK 2099 (0x833) is bad block
BLOCK 2244 (0x8C4) is bad block
BLOCK 2258 (0x8D2) is bad block
BLOCK 2289 (0x8F1) is bad block
BLOCK 2441 (0x989) is bad block
BLOCK 3570 (0xDF2) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x900
Partition[2], type=0x25, start=0xF40, total=0x11940
Partition[3], type=0x4, start=0x12880, total=0x28740
CE Total Length(with sector info) = 0x94D4400
CE CheckSum Length(without sector info) = 0x9440000
Click to expand...
Click to collapse
I see that some Bad block are in there from the Block 134 (0x86) block to the BLOCK 3570 (0xDF2). btw I dont know what the reversed block means ?
ATM, I'm using the stock SPL 5.05.
So to recover these bad block, I think It's possible to "task 2a" or "task 28", but what I'm supposed to do after these commands ? lnb the HardSPL ?
I really wanna be sure that the bad block wont bother me in the future
your help will be appreciated
Cheers
It is perfectly normal for a brand spanking new device to already have bad blocks on it. I bricked mine trying to port a radio from a different device. The 100% brand new device they sent me already had 6 bad blocks. The original I bought from the store had 7 bad blocks from the very beginning.
Reversed blocks are perfectly fine. No need to worry.