Hi Folks,
I followed the sticky and unlocked my G3. IPL and GPL were both 1.01. Then, I mistakenly upgraded to the AKU3.2 ROM (without radio) downloaded from the xda ftp site.
After the update, the device boots fine and every loads up. However, when I tried to connect to an USB ActiveSync to perform another rom update, nothing happens. Also, there's no battery information at all. It shows an unknown battery and the battery icon at the lower right hand corner is replaced by the charging icon, even though it's connected to any charger.
Is there a way to update ROM using the memory card (I have a 2 gig card) or I should throw this device out the window? I sincerely appreciate any guidance you may have.
Best,
NA
NeoAlpha1 said:
Hi Folks,
I followed the sticky and unlocked my G3. IPL and GPL were both 1.01. Then, I mistakenly upgraded to the AKU3.2 ROM (without radio) downloaded from the xda ftp site.
After the update, the device boots fine and every loads up. However, when I tried to connect to an USB ActiveSync to perform another rom update, nothing happens. Also, there's no battery information at all. It shows an unknown battery and the battery icon at the lower right hand corner is replaced by the charging icon, even though it's connected to any charger.
Is there a way to update ROM using the memory card (I have a 2 gig card) or I should throw this device out the window? I sincerely appreciate any guidance you may have.
\
Best,
NA
Click to expand...
Click to collapse
No matter what you say you didn't follow the instructions. You should have upgraded to a 2.x ROM image to get your IPL/SPL up to 2.x prior to doing anything. The best way is to use one from your carrier. This may help.
http://wiki.xda-developers.com/index.php?pagename=HTC_Wizard
http://forum.xda-developers.com/showthread.php?t=263116
http://forum.xda-developers.com/showthread.php?t=282498
http://forum.xda-developers.com/showthread.php?t=284292
I just liked the term "bricked" being used because it didn't work as expected. I suppose that term can be retired now, it doesn't really mean anything anymore.
I like how the term "Help" now means "do everything for me because I'm either too stupid or too lazy to read anything".
This whole site has depreciated in value to the point of depression.
rkwhyte2 said:
No matter what you say you didn't follow the instructions. You should have upgraded to a 2.x ROM image to get your IPL/SPL up to 2.x prior to doing anything. The best way is to use one from your carrier. This may help.
http://wiki.xda-developers.com/index.php?pagename=HTC_Wizard
http://forum.xda-developers.com/showthread.php?t=263116
http://forum.xda-developers.com/showthread.php?t=282498
http://forum.xda-developers.com/showthread.php?t=284292
Click to expand...
Click to collapse
Thanks for the info. I completely agree; mistakes were made in ROM update process.
In any case i think you can power up your phone in update mode (when you start the upgrade process it reboot automatically in this mode but you can force it) on the screen you see some coloured bars, if it start in this mode you can try to return to old rom
Activesync is not used at all in the upgrade process... you'll not need it... press the two buttons on the right side while resetting and try to flash an official rom that contains newer versions of the bootloader from the rainbowscreen. NOTE: make sure that it sais USB in the bottom left corner of the bootloader...
Good luck and remember that upgrading the rom CAN IN FACT BRICK YOUR DEVICE....
NeoAlpha1 said:
Hi Folks,
I followed the sticky and unlocked my G3. IPL and GPL were both 1.01. Then, I mistakenly upgraded to the AKU3.2 ROM (without radio) downloaded from the xda ftp site.
After the update, the device boots fine and every loads up. However, when I tried to connect to an USB ActiveSync to perform another rom update, nothing happens. Also, there's no battery information at all. It shows an unknown battery and the battery icon at the lower right hand corner is replaced by the charging icon, even though it's connected to any charger.
Is there a way to update ROM using the memory card (I have a 2 gig card) or I should throw this device out the window? I sincerely appreciate any guidance you may have.
Best,
NA
Click to expand...
Click to collapse
You found the sticky. You downgraded to the 1.05 (where the freak 1.01 came from I dunno..) You didn't upgrade to the T-Mobile per my suggestion. You haven't read my sticky all the way through because I relate my exact same issues of nearbricking..
Reboot your PC. Rerun the Button 1.05. If it still doesn't work use a friend's computer. This procedure works.
kyphur & mark - uh huh!
kyphur said:
I like how the term "Help" now means "do everything for me because I'm either too stupid or too lazy to read anything".
This whole site has depreciated in value to the point of depression.
Click to expand...
Click to collapse
Thank you for your help! Your words have inspired to find the solution.
markgamber said:
I just liked the term "bricked" being used because it didn't work as expected. I suppose that term can be retired now, it doesn't really mean anything anymore.
Click to expand...
Click to collapse
My sincere apology for referencing the term “brick.” I am new to this hobby and from what I have read in this forum, the term is fitting for my particular situation. I did not know that it was antiquated to the point of nausea.
You're asking for our help????
OK! WTF do you have to say to ME??? You didn't follow the guide so it's our fault?
I repackaged Faria's method so's even a child could understand it and already at leat 2 people can't go down the steps...
shish!
Dr Puttingham said:
OK! WTF do you have to say to ME??? You didn't follow the guide so it's our fault?
I repackaged Faria's method so's even a child could understand it and already at leat 2 people can't go down the steps...
shish!
Click to expand...
Click to collapse
My appologies, I think you have misunderstood. My question was not related to unlocking the device. Your instructions were extremely good, and I was successful in unlocking my device. In fact, I have revised your instructions in lieu of grammatical style. I am planning to perform several screen captures to make the guide more useful to others.
There's been alot of misunderstanding regarding my original post. I made a mistake and update the device with the wrong ROM. As a result, ActiveSync no longer works, so I came to this forum seeking additional assistance. I do not offer any dissenting opinions for your article. Your article is extremely useful and your efforts in preparing such article is commendable.
I Found The Solution! Thanks to All
The solution was to boot the device into Bootloader mode and then injecting with a new ROM. Unfortunately, the accepted method of entering Bootloader mode (holding the Communication and Voice buttons while reseting the device) did not work with my device. By doing so the device enters the hard-reset mode. A black screen with white letters offering the choice of restoring the device.
Inspired by Kyphur, Dromico, and _Nomad_, I began investigation alternative methods of entering Bootloader mode. I was playing with the device and by accident held down the "Voice Command" button and reseting. Ulreka! I entered the Bootloader mode and the "Rainbow Screen" appears, thus allowing me to inject a new ROM.
Thank You All!!!
Actually... the two buttons on the right side of the device is camera and voice command... keeping these buttons pressed while resetting gets you straight into bootloader mode... my post mentions nothing of pressing the communications button...
Dr Puttingham said:
OK! WTF do you have to say to ME??? You didn't follow the guide so it's our fault?
I repackaged Faria's method so's even a child could understand it and already at leat 2 people can't go down the steps...
shish!
Click to expand...
Click to collapse
Hey Steve, maybe we should hit the coffeeshops and get bricked.
kyphur said:
I like how the term "Help" now means "do everything for me because I'm either too stupid or too lazy to read anything".
This whole site has depreciated in value to the point of depression.
Click to expand...
Click to collapse
Good thing you're so perfect @ everything and that you've never made a mistake.
I love it when people become proficient in something and forget that they were new at it once.
The new people coming on board might have some great things to add. Everyone is a n00b in the beginning.
If you weren't so high and mighty you might realise that offering a helping hand can foster some great community moments and pull some good ideas into the forum.
So new is the same as illiterate? This isn't rocket science, apparently reading is.
Dr Puttingham said:
OK! WTF do you have to say to ME??? You didn't follow the guide so it's our fault?
I repackaged Faria's method so's even a child could understand it and already at leat 2 people can't go down the steps...
shish!
Click to expand...
Click to collapse
Plese show me where he was rude to you enough to warrant this type of exchange? I've read the replies to this thread 3 times and I don't see what warrants this type of rude and aggressive response from you.
ppl... pleeease...
take it easy
Related
ive posted before but really didnt get the answer i was looking for. all of this pocket pc smart phone stuff is new to me. i have the cingular 8125. my first pocket pc and it is all new to me. im trying to get the htc touchflo on my 8125. im like a baby learning how to walk haha as desperate as it sounds i need like a walk through of simple (non pocket pc savvy) how to install it all and everything like someone to hold my hand haha. sorry to sound so desperate and needy but any help is extremely appreciated.
First, we need to know a bit more info...is your phone locked or unlocked...stock rom, etc.
Secondly assuming everything is stock, you need to use the search button and search for lokiwiz, follow the directions explicitly.
Thirdly, search in the WM6 Wiz section for the rom that has the touchflo added...
I too was new and thought that if I said help I'm new, I'd be flooded with answers...I quickly discovered that the reasons the answers wouldn't come is because I didn't give enough info about my phone. A stock wizard is different from an unlocked wizard, which is different from an unlocked wizard running a rom from someones kitchen, and if your phone is a G4 then that's a whole different animal, etc...get the idea?? So to help, more info is needed about the phone itself. Power off, reboot...on the first page that pops up, there will be a few lines of info...copy those down with the numbers corresponding with it, then get back to us. "Knowing is half the battle" (famous philosopher=GI Joe). Hope this answer helps you.
thankyou.
i already unlocked my phone and went through the whole process im just not sure where to go from there.
ipl-2.26
spl-2.26
gsm-02.25.11
os-2.26.20.2
i just need to install the wm6 and toughflo im asuming i dont want to mess my phone up thats why im asking for help. thanks again.
AlexK
If you haven't flashed the T-Mobile OEM ROM yet and your IPL/SPL are still at 2.26, then you may not have unlocked your phone. I missed some of the reading first time around and this took me a while to catch, even though it was there in plain view. You may need to flash the Button ROM to get back to IPL 1.x as the lokiwiz only works with 1.x IPL.
Be carefull using the lokiwiz in the DOS window, and READ everything that comes up, especially notes like I/O error or unable to write, etc. . . If you try to flash a ROM and it appears that nothing has changed, then you're not unlocked, just going through the motions.
there is a thread here somewhere...unlocking for dummies or something like that...gives very detailed step by steps....follow this to the T. Then go to the WM6 threads section, choose the rom you want (download it), connect your phone via usb to the pc and fire up active sync. Run the loader to the rom you chose. The screen will go red and blue etc stripes and if done properly, a few minutes later it will say completed and reboot itself. DO NOT interrupt the loading process by disconnecting the usb before it's ready etc...re-install any third party apps or whatever, and you are good to go. NBo one can "hold your hand" you just need to try it until you do it. It's the only way to learn this stuff. Don't worry, I've thought I've bricked my phone so many times...MOST of the time, you can bring it back from the dead...unless you really fubar and rush things, don't read instructions properly, etc... good luck
Hello all! First of all, I am a total noob to ROM flashing and the like, so please be nice and bear with me. I am pretty sure I bricked my phone and I am sure hoping you guys can guide me out of this mess.
I have a Tilt and wanted to sim/CID unlock it and flash a cooked rom (had my eye on Dutty's latest Diamond). I spent some time reading up in the wikis, etc. and decided to give it a try. I was using Olipro's Kaiser SIM/CID Unlocker & Changer to start. I flased the SPL successfully and was in the process of patching the radio (Step 2) when - wouldn't you know it - I bumped the USB cord and knocked it loose from the PC. Uh oh. I tried to recover but it apparently did not work.
Now, the tilt will not turn on at all unless connected to the PC via USB. Once I connect the USB cord, the device just goes through a continuous loop of the splash screen, constantly trying to reset, but never getting past that point. Now, I CAN get to the bootloader screen by simply holding the camera button while the device is going through one of its resets. Once I get here, it just sits there at the bootloader until I unplug the USB, which powers off the device. On the bootloader screen, it shows the following:
Security Unlocked (at the top)
KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8
Now, since I could get to bootloader, I decided to try and reflash a ROM. I tried AT&T's original rom and Dutty's ROM. Both seemed to flash OK, but once complete I was still stuck with the same problem. HELP! Where do I go from here? I saw the instructions for frankenkaiser. Would that help? I did not want to attempt it without seeking guidance first. Any help is greatly appreciated!!!!
k
looks like your screwed...like a nail....
looks like your screwed...like a nail....
Click to expand...
Click to collapse
RU serious? There's nothing I can do from here?
moegdaog said:
looks like your screwed...like a nail....
Click to expand...
Click to collapse
Thanks Captain Productive.
To the Original Poster: You may still be able to save your Tilt. You will need mtty and a smart friend. Maybe if you look around you can find one. But, I recommend you compensate him for his time. If he is successful he saved you a $500 paperweight.
Would going through the frankenkaiser steps help?
kldalrymple said:
Would going through the frankenkaiser steps help?
Click to expand...
Click to collapse
Hmmm Probably Not.
If I have this understood correct When you reset your phone it goes directly into Bootloader? You can flash 100% a ROM but it still goes into bootloader?
Usually this happens because the bootloader thinks its still in flash mode. You have to use mtty to Clear that flag and boot it and All should be happy.
If I have this understood correct When you reset your phone it goes directly into Bootloader? You can flash 100% a ROM but it still goes into bootloader?
Click to expand...
Click to collapse
Well, not quite. First of all, when the phone is not connected to the PC, I can't get it to power on at all using any method. Once I connect to the PC, it acts like it is attempting to boot and goes to the AT&T splash screen. However, after staying on the AT&T splash screen for a few seconds, it simply resets itself and tries to boot again. It will continue in this loop unless I either hold down the camera button (which sends it into bootloader) or unplug the USB cord (which simply powers it off).
It should be noted that when I see the AT&T splash screen, I can not see the rom/radio version, etc.
kldalrymple said:
Well, not quite. First of all, when the phone is not connected to the PC, I can't get it to power on at all using any method. Once I connect to the PC, it acts like it is attempting to boot and goes to the AT&T splash screen. However, after staying on the AT&T splash screen for a few seconds, it simply resets itself and tries to boot again. It will continue in this loop unless I either hold down the camera button (which sends it into bootloader) or unplug the USB cord (which simply powers it off).
It should be noted that when I see the AT&T splash screen, I can not see the rom/radio version, etc.
Click to expand...
Click to collapse
well i can save your tilt but it will cost you. if you mess up don't blame me though. I've been there and somehow saved myself by basic computer knowledge and tools available on this forum. I have a wedding to attend in a few hours and I haven't slept yet but you appear in need of some help.
well i can save your tilt but it will cost you. if you mess up don't blame me though. I've been there and somehow saved myself by basic computer knowledge and tools available on this forum. I have a wedding to attend in a few hours and I haven't slept yet but you appear in need of some help.
Click to expand...
Click to collapse
Man, I'll take any help I can get at this point. Where do we start?
Sorry to keep bumping this, but can anyone help? I really need some assistance. Thanks!
kldalrymple said:
Sorry to keep bumping this, but can anyone help? I really need some assistance. Thanks!
Click to expand...
Click to collapse
PM, GSLEON3, he is the king of recovering " bricked " phones.
P.S. Just remember people spend many hours helping people around here, hours they could be relaxing with their families. So when all is said and done , make with the appreciation. Good Luck
PM, GSLEON3, he is the king of recovering " bricked " phones.
P.S. Just remember people spend many hours helping people around here, hours they could be relaxing with their families. So when all is said and done , make with the appreciation. Good Luck
Click to expand...
Click to collapse
Thanks, I'll definitely shoot him a note. If I can get this thing fixed, I don't mind ponying up some appreciation either!
Bump. Still looking for anyone who could help....please please please....
kldalrymple said:
Bump. Still looking for anyone who could help....please please please....
Click to expand...
Click to collapse
Start reading to get prepared for help ( or if you are feeling brave ) but make sure you understand EVERYTHING ! DO NOT get impatient and just jump right in.
If you mess up here, yea the kids get a $ 500 play phone. Be patient GSLEON will get back to you.
http://forum.xda-developers.com/showthread.php?t=371154
http://forum.xda-developers.com/showthread.php?t=372497
SUCCESS!!!
Never mind the requests for help guys, I got it breathing again! I used mtty and found I had a bunch of reversed/bad blocks. I simply downloaded the latest AT&T OEM rom from the HTC site and VOILA! I'm back up and going again! If anyone else ever runs into this problem, this thread was a lifesaver:
http://forum.xda-developers.com/showthread.php?t=380951&page=2
Whew, that's enough drama for one night. I will try to load a cooked rom later...
Big thanks to all who responded!
kldalrymple said:
SUCCESS!!!
Never mind the requests for help guys, I got it breathing again! I used mtty and found I had a bunch of reversed/bad blocks. I simply downloaded the latest AT&T OEM rom from the HTC site and VOILA! I'm back up and going again! If anyone else ever runs into this problem, this thread was a lifesaver:
http://forum.xda-developers.com/showthread.php?t=380951&page=2
Whew, that's enough drama for one night. I will try to load a cooked rom later...
Big thanks to all who responded!
Click to expand...
Click to collapse
Congrats to you!
A little inspiration for other newbies and GS gets to relax for rest of his weekend.
Well done.
Howdy, i have looked at all the guides, done loads of research into upgrading my Ignito.
I have tried to use the Olinex 1.40 and also the signed version....
But when i load it all up, go through the correct steps etc.. My phone screen looks like its just had some dodgy virus and looks like its about to die and then slowly turns off...
It then does a full reboot and its like i have a brand new phone again...
I am at a loss as to why it does this..
Anyone have any tips or tricks as to how to get around this problem ?
Any help at all will be very very welcome
Cheers
Sam
when you do the hard spl, you will only get a black screen and then it will reboot, just as you describe.
Hold the volume down key and then soft reset, if you see OLI anywhere, then it worked.
The problem is when i try the upgrade the screen seems to die aftera bout 10secs and then it says its fully done.
So there isnt enough time for the Hard SPL to be upgraded....
Anyone ?? Please....
The problem is when i try the upgrade the screen seems to die aftera bout 10secs and then it says its fully done.
So there isnt enough time for the Hard SPL to be upgraded....
Anyone ?? Please....
Click to expand...
Click to collapse
Maybe you could give more detailed information, what exactly are you doing, what does the PC end of the process say etc.
Can you take any screenshots, what SPL do you have now - the guide suggests that 1.93 could be better for you than 1.4?
Kim
It says complete after about 10seconds and then the phone reboots fully.
The current one i believe is 1.93.....
I have tried both of the Olinex versions to no avail at all.....
......
MuDvAyNeX said:
......
Click to expand...
Click to collapse
I guess no one is helping because you're not giving us enough information, procedure, XP or Vista, have you tried Hard-SPL 1.93, screenshots or better description of the problem.
Screen goes funny and then reboots just isn't enough
Kim
Well i have tried both of the Olinex versions both the 1.4 and the 1.93.
I am using windows vista and the mobile device center, its fully connected as i do a sync etc before hand.
I then load the Romloader that does the usual tick this, tick that etc.
Once that has happened i click the upgrade button, it then confirms i am going from the current SPL do the one i have chosen.
I click ok and then it goes to the progress section where it says it could take upto 10min, the screen on the phone then looks like it has got a virus and starts to look like its dying.
Meanwhile after about 10 seconds it tells me that upgrade is done, this is while the phone reboots and starts like its a brand new phone again with no changes that i can see...
In all honesty i can't see what i am doing wrong
Scrath what i just put, as i was typing that i was trying the upgrade via my mates XP laptop and it now says in the bootloader 1.93 Olinex...
I am going to guess this is upgraded... lol
MuDvAyNeX said:
it now says in the bootloader 1.93 Olinex...
I am going to guess this is upgraded... lol
Click to expand...
Click to collapse
Great, glad it's sorted, I was gonna say I don't have much experience with Vista (an' I don't want to )
I'm sure that I've read that there can be issues with the Vista device center(sic), A quick search of XDA-Dev will help.
If you want to eliminate the PC <-> Ignito pitfalls maybe try Suillers method of upgrading direct from the device Internal Storage.
Kim
I'm thinking of flashing to Dutty's rom, but have no idea on where to start. I have read through all sorts but its still all confusing to me. A step by step instruction/guide would be of great help.
Thanks
Dude, try the wiki, everyone has to do this.
Start here: http://wiki.xda-developers.com/index.php?pagename=HTC_Blackstone_Flash1
danprocter said:
I'm thinking of flashing to Dutty's rom, but have no idea on where to start. I have read through all sorts but its still all confusing to me. A step by step instruction/guide would be of great help.
Thanks
Click to expand...
Click to collapse
easy 4 step proccess
1. drop Touch HD into a padded envelope
2. mail it to me
3. ???
4. profit
danprocter said:
I'm thinking of flashing to Dutty's rom, but have no idea on where to start. I have read through all sorts but its still all confusing to me. A step by step instruction/guide would be of great help.
Thanks
Click to expand...
Click to collapse
Use the search Luke!
Sir.B said:
easy 4 step proccess
1. drop Touch HD into a padded envelope
2. mail it to me
3. ???
4. profit
Click to expand...
Click to collapse
You don't mean!
lmao you could make a lot of money in noob rom flashing
Hey Dan.
Someone here linked the wiki for the Touch HD. I know it's a bit overwhelming when you first entertain the prospect of flashing a new rom on your phone. You want someone to lead you through it step by step, you don't want to brick your phone, and you want to know which ROM is best.
I don't know which ROM is best, everyone has their favourite.
Start with Davidduek's V3-HP, or Dutty's 2.3 extreme.
They're both very good roms, the latest software, and you'll notice a big difference from the phone you have now.
As for how to do it. Overwhelming at first? YES. Impossible? NO.
Take things step by step. There is a complete step by step guide on the wiki.
Your fear of doing something wrong and killing your phone, it's something we all had at the start. I will say this, if you follow the steps (and remember to breath every now and again) you'll have your first flashed rom on your phone in no time. Not to mention, the high of actually getting it done (it really is gratifying)
So, go to the wiki, look for the guide. Follow it.
Good luck my friend, and don't worry, get it done.
Caid.
I had the same in the beginning as most tutorials somehow sound very risky, but in reality it is really easy.
I never backup my contacts, calendar or whatever, so that's up to you if you want to do that first.
I use USPL instead of HSPL as it should be safer for your warranty. I can go into technical details, but in my opinion that is not that important.
See it this way, normally you are not able to flash roms that are not officialy from HTC and USPL makes this possible. Simple as that.
I tried to make the tutorial as easy as possible:
STEPS
1. download USPL onto your PC (of course you need your PC for flashing) and download the rom you want to put on your phone and have them ready.
(Most rom zips contain the rom and an excecute file to start the flashing process, if it does only contain the rom, you have to download this excecute file seperately, it is called custom RUU, or you can take it out of a rom zip which contains it)
2. Go to ActiveSync properties in your PC's taskbar and disable "Allow USB Connections" option. (right click on the icon and you will see that option)
3. Turn off your phone
4. Switch your phone on in "Flashing mode" (you will see a tri-color screen) by pressing and holding "Power" and "VolDown" keys simultaneously.
5. Wait a couple of seconds
6. Connect a USB cable from PC into your phone and make sure the text "USB" appears on your phone's screen (in the white portion of the screen)
7. Start USPL by clicking on blac_uspl.exe on your PC.
8. On your phone, USPL text and some numbers appear.
9. Now you can run the exe file (custom RUU) from your PC and be sure the rom is in the same folder as this exe file.
10. Just follow the on screen instructions on your PC.
11. The flashing progress is shown on your PC and on your phone. When it is at 100%, wait until you get the message everything is ok on your PC. From that moment you can disconnect your phone and switch it on again and enjoy your new ROM!
It is recommended to do a HARD RESET on your phone after flashing to get optimum perfomance and stability inside your new ROM. See your manual how you can HARD RESET.
With the very greatest of respect to you stefh, the community would be far better served by your adding this excellent guide to the Wiki rather than addressing a specific post - otherwise this gets buried in the noise.
I tend to agree with earlier posters that we all had to sit down and invest time in understanding the process - resources such as the Wiki have been created for just such a reason.
Fundamentally if you have read the Wiki and still don't understand the process (or don't feel able to follow the steps) flashing ROMs is probably not where you need to be at this point in time.
I'd certainly see about getting this added to the Wiki though...
Thanks iain for pointing that out. I will put in on the wiki when I get home if it is appreciated.
I agree one should not Flash if one does not know what he is doing.
But when I look back on my personal situation.
I always used Symbian and in fact the Touch HD is my first winmo phone.
I have experience with doing all kinds of firmware flashes and "hacking" with a variety of equipment (Symbian phones, Sony Ericsson "standard" phones, PC equipment, popcorn hour, etc.)
And somehow I found it difficult to simply understand all the steps needed for a device like the blackstone. But when I just did it, it was so easy I was like: "Man! Why did I had any doubts?"
Same thing goes for that I do not understand why everybody always uses the codenames(concept names) for the phones like blackstone, topaz and rhodium as for someone new it is not as easy to immediately understand what it is all about. I guess there never was any bad intention on purpose, but I read a lot of stuff of which I think: damn why make it so difficult when it is so easy? It is like it is a sport or something to mask the simple terms
e.g. When we just talk about touch HD, touch pro 2, diamond 2 it gets much easier. I can understand it is done to keep people with less knowledge in this scene away, but not all new people to the scene are noobs.
Of course it is not my intention to insult people. I have really deep respects for all active people working their ass of creating (sorry cooking) new roms and stuff.
When I was a student I had all this free time to go deep and look everything up, but when you work, you do not have all this free time anymore but you still want to integrate in the forum and sometimes it is really nice if someone simplifies things for you. But of course I know a rush is never good. It is important to think everything through and of course to learn.
But is also important to give your girlfriend enough attention
I want to thank everyone on this forum that made my Touch HD what it is now Respect
well said sir!
Hi guys,
Well, I've searched the forum and get close...but no cigar. So, I'll go ahead and ask.
I have an AT&T Tilt, Flashed the 6.1 from XDA MONTHS ago, and have been running Slither's Cube...not even all the time...as well as the HTC Home Customizer.
Yep, that's it.
Well, I have purchased another Tilt with a busted screen (otherwise absolutely fine) for $30 and am waiting to afford a new screen for it...at which time I'll have a backup and then the Cooking and Flashing will begin in earnest!
But I digress. Here is the sequence of events, and where I am at now:
1) Went to hang up from a phone call (BT headset active) by pressing the "Hang Up" Button...no response from the phone.
2) Pressed the Power Button...no response.
3) Slid open the Keyboard...no response.
4) Held the Power Button...no response.
5) Dumped the battery and rebooted...AT&T Splash then Radio Info...stays right there. Screen will dim after awhile, but never goes out. Rebrightens when removing external Power.
6) Soft Reset...same result.
7) Only way to Power Down is dump the battery.
8) Removed SD and SIM...attempted Bootloader Screen
9) Bootloader DOES show up:
KAIS1*0
SPL-1.93.0000
CPLD-8
Serial
10) I don't remember if there was anything with "Serial"...like a number or such...when I looked at it last (when flashing 6.1) so that may or may not be significant. There's nothing there now.
11) My Radios show up as:
R 1.27.14.09
G 22.45.88.07H
D 1.62.00.00
I am avoiding Hard Reset or Re-Flash until I can at least figure out what happened...if anyone has any ideas...or find out that this is common and that's the best or only way to solve it etc.
Since I haven't found anything quite like this in the Forum, I'm presuming that it may not be so common and I may...or may NOT...be able to find a way back before going that path. As well, I really don't want to send it off for repair...although I have insurance and coverage through Hawk (our AT&T Provider) that would be reasonable for repair ($35) but perhaps inordinate for rreplacement ($175). I'd like to be able to resolve this myself, but not knowing what may be wrong leaves me only with Hard Reset and/or Re-Flash alternatives...if those will even work...so out goes the question:
Has anybody run into this or have any idea of why it happened or the BEST recourse to resolve it?
Thanks in advance for any and all info, y'all are awesome and I truly appreciate your help...
RAF
These phones freeze all the time. Software conflicts, too much running at once, and it just feels like screwing you when you need it most. And of course all of a sudden, the hardware just crashes and never works again.
It looks like a hard reset will solve your problems, unfortunately, unless you do regular backups, you will lose all your info.
Thanks denco7!
Well, this is the first time it has locked up that early in the boot...all others have been easily resolved.
Hard Reset is not an issue with Data...I do keep my phone (data) backed up and have most of my volatiles on the SD.
And, honestly, I don't mind having to reflash or reinstall my apps...at least not yet, once I start cooking my own I feel I'll get a bit testy when I have to 'start over'.
I should probably find a good full backup app to snapshot the whole phone, then just put it back on when things 'happen'.
I do have a full backup from December using the 'supplied' app, so it will at least have most of the tweaks in it.
I'm gonna do the Hard Reset and see if that clears this, but I must say I'm not that hopeful.
Not really an expert...not a noob either...but this technology is just not rocket science, and I can actually do that along with quite a bit more.
Don't ask me to write a driver tho...I respect anyone that has that kind of patience!
Suffice to say, this just doesn't "feel" like a resetable issue...but I'm game. I'll update once attempted.
Thanks again, see you on the other side...
RAF
Okay...no joy on the Hard Reset. Behavior has stayed the same. Kinda expected that tho...
Next stop, Re-flash the ROM. I'm gonna check on latest releases of 'Official' HTC ROMs...but if anyone has any suggestions I'm open.
I'm still hoping that someone out there knows what happened here, it would be helpful to know the 'why'.
Thanks again...
not so much a suggestion but a correction. You don't have a wm6.1 rom but actually have a wm6 rom because the radio you have flashed i.e. R 1.27.14.09
is a wm6 radio not wm6.1 and that radio is only compatible with the following roms:
AT&T 1.60.502.3
AT&T 1.61.502.2
AT&T 1.62.502.0
Q-Mobile 1.2 AT&T Version
(source for above info: http://forum.xda-developers.com/showthread.php?t=393182)
so make sure that your rom matches the radio you have. I would recommend that if flashing is not something new to you than go ahead and upgrade your rom and radio to wm6.1 rom and see if the issue presists.
hope this helps
first post you stated you have a 6.1 rom but your spl is for a 6.0 rom, either your not on a 6.1 rom or your on the wrong SPL and should HARDspl if your flashing custom roms.
Thanks Guys...
I had it in my head that I went to 6.1 when I flashed it last...went out and looked at the file and sure enough it was 6.0.
This is what happens when u have 7 kids, 6 female and 4 of those in college...I'm too broke to pay attention.
No not new to flashing, and when I can get home before 10-11p some night...or this weekend...that's my plan.
Looking for the best choice 6.1 to flash and attempt to bring it back, but still curious as to the behavior in the first place.
Thanks for pointing out my ADD, and all comments are welcome...
Hoping for the un-bricking soon...
RAF
Now I'm REALLY Currious...and Frustrated! A Little Help Please...
Okay,
So I flashed the latest HTC Factory ROM: AT&T Tilt Windows Mobile 6.1 Software (ROM Version 3.57.502.2 WWE).
I wanted to do something mild at first before taking too many big steps...'small steps Ellie, smal steps'.
Once the Bootloader was up with USB showing at the bottom, I was certain I would at least have a connection to the Phone.
Of course with no ActiveSync or recognition from the PC, I simply ran the EXE and ignored the one line about making sure ActiveSync had a connection.
The only oddity was that at 13%, the Phone went from the "% Screen" back to the Bootloader Screen for a few seconds then continued normally to sucessful completion.
When it rebooted, it stayed at the AT&T initial splash and now NEVER shows the Radio or Protocol versions...just the initial splash.
As well, it does not dim the backlight after awhile as it used to nor do I ever get a Power Light...just plain LOCKED.
There is also still no way to Power Down the Phone except for removing the Battery.
Although I've never used MTTY, I'm wondering if that is now my only hope...and am currious as to the proper procedure for this particular circumstance.
I'm still searching the Forum for MTTY uses and info, but I would be appreciative if one of the Seniors could point me in the right direction.
Also, if ANYONE knows what may have caused this glitch in the first place it would help me to determine the best recourse.
Thanks again in advance to all...
RAF
Rustafergi said:
Okay,
So I flashed the latest HTC Factory ROM: AT&T Tilt Windows Mobile 6.1 Software (ROM Version 3.57.502.2 WWE).
I wanted to do something mild at first before taking too many big steps...'small steps Ellie, smal steps'.
Once the Bootloader was up with USB showing at the bottom, I was certain I would at least have a connection to the Phone.
Of course with no ActiveSync or recognition from the PC, I simply ran the EXE and ignored the one line about making sure ActiveSync had a connection.
The only oddity was that at 13%, the Phone went from the "% Screen" back to the Bootloader Screen for a few seconds then continued normally to sucessful completion.
When it rebooted, it stayed at the AT&T initial splash and now NEVER shows the Radio or Protocol versions...just the initial splash.
As well, it does not dim the backlight after awhile as it used to nor do I ever get a Power Light...just plain LOCKED.
There is also still no way to Power Down the Phone except for removing the Battery.
Although I've never used MTTY, I'm wondering if that is now my only hope...and am currious as to the proper procedure for this particular circumstance.
I'm still searching the Forum for MTTY uses and info, but I would be appreciative if one of the Seniors could point me in the right direction.
Also, if ANYONE knows what may have caused this glitch in the first place it would help me to determine the best recourse.
Thanks again in advance to all...
RAF
Click to expand...
Click to collapse
If you cannot flash a 6.1 rom or install the correct hard spl I would not even attempt using MTTY. Go to the rom section of this forum. Look for "spl rollup thread" it is a sticky from DaveShaw. Pick any 3.xx hard spl's for 6.1 rom and download. Now download jumpspl and place it somewhere on your device other than your memory card. Now run jumpspl and follow the rest of the directions in that thread. After you installed the correct SPL find a 6.1 rom and flash your device. If your sound doesn't work change your radio to a compatible radio, which would be listed in the "ultimate radio thread" by alltheway.
These are the basics. Hope it helps.
Rustafergi said:
Okay,
So I flashed the latest HTC Factory ROM: AT&T Tilt Windows Mobile 6.1 Software (ROM Version 3.57.502.2 WWE).
I wanted to do something mild at first before taking too many big steps...'small steps Ellie, smal steps'.
Once the Bootloader was up with USB showing at the bottom, I was certain I would at least have a connection to the Phone.
Of course with no ActiveSync or recognition from the PC, I simply ran the EXE and ignored the one line about making sure ActiveSync had a connection.
The only oddity was that at 13%, the Phone went from the "% Screen" back to the Bootloader Screen for a few seconds then continued normally to sucessful completion.
When it rebooted, it stayed at the AT&T initial splash and now NEVER shows the Radio or Protocol versions...just the initial splash.
As well, it does not dim the backlight after awhile as it used to nor do I ever get a Power Light...just plain LOCKED.
There is also still no way to Power Down the Phone except for removing the Battery.
Although I've never used MTTY, I'm wondering if that is now my only hope...and am currious as to the proper procedure for this particular circumstance.
I'm still searching the Forum for MTTY uses and info, but I would be appreciative if one of the Seniors could point me in the right direction.
Also, if ANYONE knows what may have caused this glitch in the first place it would help me to determine the best recourse.
Thanks again in advance to all...
RAF
Click to expand...
Click to collapse
Wow! I think you missed the advice and wisdom given to you about NOT FLASHING a 6.1 ROM with the SPL for a 6.0 ROM...
Anyways, lets see if we can help... I don't think you are going to be able to flash a SPL, as you probably can't even get an active sync connection to copy over the files...
So, try getting into boot loader screen; you hold down the camera button and then press in the rest button and hold that until a tri-color screen appears...
Then tell us exactly what it says, just to make sure we know which SPL you have... Then I will post a link to the exact ROM you need to flash to hopefully bring her back to life.
If you are not able to get into boot loader, which wouldn't surprise me, someone else with more experience un-bricking will have to help.
Some Answers and Info...Still Confused
redbandana said:
If you cannot flash a 6.1 rom or install the correct hard spl I would not even attempt using MTTY. Go to the rom section of this forum. Look for "spl rollup thread" it is a sticky from DaveShaw. Pick any 3.xx hard spl's for 6.1 rom and download. Now download jumpspl and place it somewhere on your device other than your memory card. Now run jumpspl and follow the rest of the directions in that thread. After you installed the correct SPL find a 6.1 rom and flash your device. If your sound doesn't work change your radio to a compatible radio, which would be listed in the "ultimate radio thread" by alltheway.
These are the basics. Hope it helps.
Click to expand...
Click to collapse
pjcforpres said:
Wow! I think you missed the advice and wisdom given to you about NOT FLASHING a 6.1 ROM with the SPL for a 6.0 ROM...
Anyways, lets see if we can help... I don't think you are going to be able to flash a SPL, as you probably can't even get an active sync connection to copy over the files...
So, try getting into boot loader screen; you hold down the camera button and then press in the rest button and hold that until a tri-color screen appears...
Then tell us exactly what it says, just to make sure we know which SPL you have... Then I will post a link to the exact ROM you need to flash to hopefully bring her back to life.
If you are not able to get into boot loader, which wouldn't surprise me, someone else with more experience un-bricking will have to help.
Click to expand...
Click to collapse
Hi again,
Thanks to redbandana and pjcforpres for the responses...I thought I might not get anymore!
I'll start with pjcforpres,
First, my appologies if I have not been specific enough on my descriptions...I've been attempting to be more succinct (I'm not so good at that).
This was a Stock ROM Tilt, then I had flashed RUU_Kaiser_CINGULAR_WWE_1.62.502.0_radio_sign_22.45.88.07_1.27.14.09R2_Ship.exe quite awhile back...shortly after it was available.
I added Slither's Cube and the HTC Home Screen and Customizer and have run it that way since then.
Somehow, I got it in my head that I had flashed 6.1 but I was flat out mistaken...hence the comment in the earlier part of the thread.
Then we get to the #1 post in this thread...add some confusion and voila.
The ref'd 6.1 flash was also Stock...RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship.exe...and I thought I read everything, incl that it replaces the SPL.
Durring the flash, it pauses @ 13%, the USB disconnect 'bing' sounds and the Bootloader screen reappears showing SPL-3.02.000.
Then, the USB reconnect 'bing' sounds, goes back to the % screen and then completes the flash successfully.
My Bootloader screen is now:
KAIS1*0
SPL-3.56.000
CPLD-8
So...did I miss something and screw up? Or was I on the right track?
And redbandana,
It did successfully flash 6.1, but it still doesn't start...specifically, get passed the initial AT&T Splash.
Although I had already thought of going to JockyW's HardSPL 3.29, I cannot 'see' the phone in XP and therefore cannot get JumpSPL onto it...so, no HardSPL (unless I missed something else in the threads).
It DOES however give me the USB 'bing' sound when I go into the Bootloader...but clicking on the "Mobile Device" icon in Windows Exploder leaves a 'blank' right pane.
Before your post, I had read up on MTTY and noted the DON'Ts...like DON'T use task 2a!...and found several threads with commands.
None of the info commands seem to fuction, like info 2, info 7 or info 8 so I don't have much 'info' there.
One of the things I tried was 'task 28' to format the thing in case there was some corruption...this was the response:
Cmd>task 28
Format start
Storage start sector=0xC2C0, total sector=0xF000
Storage start block=800, total block=960
Total Bad Block in CE: 1
Erase physical block from 1091 to 2032
formatstorage Bad block found: 1397
formatstorage Bad block found: 1398
si backup: Erase physical block from 2032 to 2048
Format end
So I looked for 'bad blocks' on the Forum and there are suggestions to contact JockyW and GSLEON3 for more help.
I haven't as yet done this thinking I can work my way through this by searching the Forum and monitoring this Post.
My searches for MTTY Commands have shown me that there are different Commands for different SPLs, and the info is way scattered and confusing.
It is becoming clear(er) to me that I have an issue that is not that normal...or at least not with an intermediate level 'fix'.
That's why I asked for more help in the right direction, I feel like I've hit this pretty hard and done alot of footwork on my own.
I also feel like I'm running out of options and may resort to bugging JockyW and GSLEON3...unless there are any more suggestions
PLEASE let me know if there is more info that I can provide to narrow this down, or some procedure to attemt, or an MTTY comand that will give us more info, or another search in the Forum for something specific I've missed...or simply some PFM that can be performed...and I'll be HAPPY to comply!
Thanks again...and again...for the assistance, my grattitude and appreciation out!
RAF
I am going to be short and swet for the moment... my computer crashed so I am solely on my phone until I work again around 2 central time USA...
Good news is that there is a chance without MTTY to get you running, and if not, those with the knowledge are very hepful and patient.
I will do the searches tomorrow for the stock ROM you should try, and give a walk through on how to flash using a micro SD card.
I am out for now, and will get back to you as soon as I can tomorrow.
Patient and Prepared
Thanks pjc...if we can fix this I'll vote for you
I sincerely appreciate the assistace, and PLEASE let me know if there's any research I can do to facilitate.
If you're willing, let me know if I took a wrong turn somewhere or if I did something to make this worse...I like to learn from my mistakes (I AM pretty good at those...)
I just got the new screen for my backup Tilt and I'll be swapping that out tomorrow (uh...today) sometime, so I'll have a reference phone soon.
Askew but relevant, I'm on day 12 of a nasty cranial muscle spasm and 3 days into meds for it...so we'll see if I can stay focused
Thanks again and in advance...
RAF...Tilted
http://www.htc.com/us/SupportDownload.aspx?p_id=67&cat=2&dl_id=94
Try downloading from here... it is the 100% official AT&T Tilt 6.1 ROM, plus upgrade tool.
This includes everything you need, and is probably what you flashed already, but it sounds like you had a bad flash or something...
Make sure your computer doesn't go into hibernate during this process, and that you don't have anything running other than the update program and activesync...
Also, make sure when you run the update program, you right click and select 'run as administrator' or 'run as' then in the menu that comes after that select administrator.
If you can't establish an activesync connection, or if you are using Vista, and thus no Windows Mobile Device Center connection can be established, let me know, and I will track down the ROM by itself and the Radio by itself and walk you through that.
This should be the easiest fix, though, so we will try this first.
Been There, Done That...I Think ?!?
pjcforpres said:
http://www.htc.com/us/SupportDownload.aspx?p_id=67&cat=2&dl_id=94
1] Try downloading from here... it is the 100% official AT&T Tilt 6.1 ROM, plus upgrade tool.
2] This includes everything you need, and is probably what you flashed already, but it sounds like you had a bad flash or something...
Make sure your computer doesn't go into hibernate during this process, and that you don't have anything running other than the update program and activesync...
3] Also, make sure when you run the update program, you right click and select 'run as administrator' or 'run as' then in the menu that comes after that select administrator.
If you can't establish an activesync connection, or if you are using Vista, and thus no Windows Mobile Device Center connection can be established, let me know, and I will track down the ROM by itself and the Radio by itself and walk you through that.
This should be the easiest fix, though, so we will try this first.
Click to expand...
Click to collapse
1] Yep, same one I have already flashed several times to determine if there was a pattern.
2] ActiveSync will not connect...remember from #1 in this post:
1) Went to hang up from a phone call (BT headset active) by pressing the "Hang Up" Button...no response from the phone.
2) Pressed the Power Button...no response.
3) Slid open the Keyboard...no response.
4) Held the Power Button...no response.
5) Dumped the battery and rebooted...AT&T Splash then Radio Info...stays right there. Screen will dim after awhile, but never goes out. Rebrightens when removing external Power.
6) Soft Reset...same result.
7) Only way to Power Down is dump the battery.
8) Removed SD and SIM...attempted Bootloader Screen
9) Bootloader DOES show up:
KAIS1*0
SPL-1.93.0000
CPLD-8
I've never gotten passed the initial AT&T Splash since then...no matter soft hard reset flash the 6.0 ROM that was already on it or this 6.1 version.
Only difference is when I flashed this 6.1 ROM, the Radio and Protocol Versions that normally pop up at the bottom in red no longer pop up.
It now stays at the initial AT&T Splash, no versions, and never dims the backlight.
The ONLY time my Laptop 'sees' the Phone is when I put in into the Bootloader I get the USB 'bu-bingk'.
MTTY can see it, and the ROM Upgrades see it and run successfully...but Exploder can't and neither does ActiveSync.
Just to clarify that I've been there more than once...
3] Well, that I have not attempted...but all my previous flashes have gone fine (I am the only user on my Alenware Aurora m7700...and effectively I AM the Administrator), so I'll attempt that...(see next).
I downloaded, overwrote and ran this 6.1 ROM again...I set this XP install with me as the only Administrator (only user other than Guest), and I want to point something out that may be significant:
The Screnshots below show that there's no info in the Current Image Version area, I click on 'Update' and get the 2nd one.
(okay, sorry I haven't attempted very hard to embrace multiquote or embed a screenshot yet )
But this has happened every attemp to reflash after the initial sequence of events. As well, the same events recurred during the flash as all attempts before:
Durring the flash, it pauses @ 13%, the USB disconnect 'bing' sounds and the Bootloader screen reappears showing SPL-3.02.000.
Then, the USB reconnect 'bing' sounds, goes back to the % screen and then completes the flash successfully.
So...did I screw up somewhere? I really thought I had a handle on the 'small steps' that I took..it was the 'next steps' that I was mildly trepidatious about.
My understanding and instincts point to the 'bad blocks' errors durring the MTTY 'task 28' format, but I can't find anything pertinent to 'do' about it in the Forums...other than contacting JockyW or GSLEON3.
I want to try SOMETHING on my own before I go bothering them with a PM...although I've read (and even learned) alot here recently on TOP of what I had already learned over the last 2½ years, I feel I've got to at least attempt something before begging for help that way.
Still, I haven't found a path to get this basal into the core of the phone to noodle (safely mind you) around and become more adept so that I can solve these issues on my own...and it may be time to capitulate.
Let me know if you've spotted an error on my part...something I did or didn't do...or if there's another path I should take or search in the Forum I should look up.
Thanks ton again...and my appologies to all for my un-succinct pontifications...
(S)tilted...RAF
I don't think you are really doing anything wrong on your part, it just doesn't want to flash right... I had you try the stock stuff again just to make sure it was a clean download, and a clean flash.
I am not sure if it is the SPL not matching the ROM, or the Radio... The MTTY commands do indicate a problem with something not flashing right to the phone. Especially since that download has been recommended and successful so many times for people with a similar situation. I have done a fair amount of looking into this myself, and I have found a couple solutions:
1. Some people found success by flashing the same stock AT&T ROM 2 -5 times, and then it finally caught and worked right.
2. Others found luck by flashing a HardSPL, then new Radio, then new ROM.
3. They PM one of the greats... right now in the Kaiser area, JockyW is amazing! But is mostly focused on newer devices. I would recommend contacting mskip or DaveShaw. They have much more experience than I do, and should have a better idea of exactly what those block errors mean, and the solution....
If I were you I would try one last time doing a hard rest, you may need to hold down the 2 soft keys and the rest button extra long to get it to register... I would also try flashing that same upgrade 1 last time, followed by 1 last shot at a hard rest. If you still have the same stuff going on, I would contact those 2 guys and see what their wisdom says... mskip moderates the "NOOB flashing guide" thread and DaveShaw is a moderator for the Kaiser section in general.
Thanks pjcforpres...Contacting DaveShaw...Any Other Ideas?
Okay, one more time...and, no joy. Held the Soft Keys for 2 mintes solid for the Hard Reset, Reflashed, then another 2min Hard Reset.
I've resorted to sending DaveShaw a PM per the suggestion and will patiently wait for a reply.
In the mean time, if there's ANY other suggestions or a list of MTTY commands that run on the 3.56.000 SPL that can get info from the phone to help determine what the actual problem is or to correct bad blocks I'd be SERIOUSLY appreciative and VERY grateful.
Thanks to all who have responded, and in advance to all who may help from here...
RAF
A Little Updated Info:
Replaced the screen on my 'backup' Tilt, and flashed the RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_s ign_25.88.40.05_1.65.21.18_Ship.exe ROM thaT I had flashed on the 'bricked' one.
It had the same behavior @ 13%, so I'm certain now that the flash went fine...I am even more convinced, with all of the events and symptoms to this point, that the issue lies in the 'bad blocks' reported durring the MTTY task 28 format.
I've left a PM for DaveShaw...and I AM patient...but if there is someone that may be more appropriate for this question I'd like to contact them as well. If anyone knows the right Guru, please let me know.
Thanks again to all...
RAF
Well I'm here at last sorry for the delay in getting back to you - I'm not sure how much I can help you though .
Can you post the output of "info 2" and "info 8" from an MTTY connection to your bootloader.
Also, can you please clarify: are you stuck at the bootloader (red/green/blue) or the splash screen (with R G D)?
Thanks
Dave
DaveShaw said:
Well I'm here at last sorry for the delay in getting back to you - I'm not sure how much I can help you though .
Can you post the output of "info 2" and "info 8" from an MTTY connection to your bootloader.
Also, can you please clarify: are you stuck at the bootloader (red/green/blue) or the splash screen (with R G D)?
Thanks
Dave
Click to expand...
Click to collapse
Wow man, THANKS for just bein here!
That's just it Dave, none of the info commands in MTTY seem to return anything (see #10). I've used MTTY: ver. 0.01 2001 and ver. 1.42 1997-2001 and both report literally nothing for info 2 info 7 or info 8...just another Cmd> prompt. However, (also in #10) I get to the 'bad blocks' ref running "task 28":
Cmd>task 28
Format start
Storage start sector=0xC2C0, total sector=0xF000
Storage start block=800, total block=960
Total Bad Block in CE: 1
Erase physical block from 1091 to 2032
formatstorage Bad block found: 1397
formatstorage Bad block found: 1398
si backup: Erase physical block from 2032 to 2048
Format end
Remember, the stuff in #1 of the thread happens and then I went through all this digging...took it to where I could and posted.
This wasn't a HardSPL fail or a bad Flash... I had BEEN running stock HTC 6.0 WWE with Slither's Cube, the HTC Home Screen and Home Customizer.
RUU_Kaiser_CINGULAR_WWE_1.62.502.0_radio_sign_22.45.88.07_1.27.14.09R2_Ship.exe (flashed 07/20/08)
This isn't a RUUNBH issue either, and I can get into Bootloader and I'm not 'stuck' there...currently:
KAIS1*0
SPL-3.56.000
CPLD-8
I can flash stock ROMs all day long w/no errors...flashed HTC 6.1 WWE on my backup Tilt to be sure the behaviors were the same, and they are exactly.
RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship.exe runs FINE on the backup Tilt.
After flashing the HTC 6.1 WWE on the 'bricked' one however, there is no longer the R G D Radio Protocol info at the bottom of the AT&T Splash after the initial Splash...it was there before the 6.1 flash, and that's where it used to hang: Initial Splash, R G D, hang...backlight eventually dimed but never went out...battery dump only way off.
Now it hangs at the Initial Splash, NO R G D, NO backlight dim...still needs battery dump for off. It ACTS like it's lost it's damn mind...
I'm pretty sure I 'downgraded' back to the 6.0 mentioned above and went thru some similar steps to confirm, but I didn't write it all down and I'm way ADD so I can do that one again and record it all this time...unless that's a bad idea.
I very recently (like as I was searching I saw you had answered my plea...) found some other references to a MFG HardSPL that someone was thinking about working on to fix bad blocks, but I haven't read through it all yet. And, since Exploder and ActiveSync simply can't 'see' the phone, I'm not sure that I could get a HardSPL on the thing in the first place...'cause I can't get no JumpSPL on the phone itself...should've done that back when it was working I guess
I truly believe I'm at the 'needing guru help' level at this point, but if you see something I should do PLEASE point me that way and I'll dive right in. Also, like I've asked others, if you see something I did wrong or in the wrong order or whatever, please let me know that also...there's GOT to be something I can actually LEARN from this.
I warned you I tend to pontificate, but I hope that this clears up where I'm at. ANY help you can provide is fantastic and greatly appreciated, even if it's just to tell me to go somewhere else (I'm kinda used to that )
Thanks again, seriously...
RAF
In that case I have no idea. I think GSLEON3, jockyw2001 or cmonex are going to be the only one's who can help you.
Dave