I am Johnny-come-lately to this debranding scheme. I am in America, but I chose to downgrade to the Euro Rom. Half of it was a success, the other half a failure. The four lines on the top all said okay. The installation that follows went about a line and a half and errored out with the line: wrong or improper sign, which I suppose could be short for "signature". Anyway when I rebooted the phone it got to the HTC screen and froze right there. Also it is in the boot loop. I tried reinstalling the Rom, but it gave the same results. I haven't been able to install SPL 2.05 either. I would like to move forward. But without an OS on the phone, nothing else recognizes it. I have been using the GC method with a single card reader and an SD card. I gave an 8Gb SanDisk flash drive a try but to no avail. I have also tried the various naming variations that are employed here and there. So what does the error message mean? What are my chances of going forward with the Cingular rom so as to finish HSPLing it. Or going back to a shipped or stock rom.
EDIT: I have access to the bootloader and SPL mode.
Thanks to all of you for your unfailing support to us neophytes.
Mercurybird said:
.. I gave an 8Gb SanDisk flash drive a try but to no avail...
Click to expand...
Click to collapse
Try to find non-SDHC card for gold-carding.
The best result is SD 1.0 — up to 2 Gb. That what I do always - no issues on any type of thumb drive or card with reader. Other guys here have also success with SD 1.1 which is up to 4 Gb. But 8 Gb will not work.
AndrewSh said:
Try to find non-SDHC card for gold-carding.
The best result is SD 1.0 — up to 2 Gb. That what I do always - no issues on any type of thumb drive or card with reader. Other guys here have also success with SD 1.1 which is up to 4 Gb. But 8 Gb will not work.
Click to expand...
Click to collapse
My card is HD and is a single card reader. I have a 1Gb and a 4Gb thumb drives. No luck with either of the sticks, but the HD card works. I'm going to take another path. I need the file; IMG_Eternity_Cingular_US_1.10.502.04_Radio_16.23.0 2.26_A… (Radio 16). I'll be able to move forward with that. Where can I download it at?
Mercurybird said:
My card is HD and is a single card reader. I have a 1Gb and a 4Gb thumb drives. No luck with either of the sticks, but the HD card works. I'm going to take another path. I need the file; IMG_Eternity_Cingular_US_1.10.502.04_Radio_16.23.0 2.26_A… (Radio 16). I'll be able to move forward with that. Where can I download it at?
Click to expand...
Click to collapse
AndrewSH is correct; I had your exact same problem but before I get ahead of myself; your device must read x310e after you install the Euro ROM; if it doesn't you're dead right there. You may be the exception but no high capacity card worked on the two Titans I did; however, I did successfully use a PNY 4 GB thumb drive; a red one in fact that comes in a two pack - red/blue thumb drives from Wal-Mart with a Y cable. I tried an 8 gigger; no dice. When you flash SPL205; you need to be really, really patience; you might say to yourself this is not doing a damn thing...give it a solid 30 minutes before you give it up for dead; out of the blue my device came alive about 15 minutes into it and successfully updated the SPL by saying bootloader ok and radio ok. I cannot stress enough how important this 2nd step is and have the patience to wait it out. You only format your thumb drive/micro SD card once; that's it; all you have to do after that is remove the 1st ROM and replace it with the baby ROM from SPL205. One more thing, if you haven't renamed the image do so...change it from ETERIMG to ETERDIAG...those 8 letters that's it. "diag" behaves differently than "img". And look, I realize this stuff makes for boring reading but read all the threads on HSPL not just the Titan; I'm not implying you read everything here...but specific to HSPL and Windows Phone 7, you bet...regardless of device. I don't want to sound like a grouchy old man here but it took me 4 days to get this right and I did a level of reading I've never done before here and I've been flashing phones a long time; there's no quick fix solution here and to be frank, it's a crap shoot; it may and again it may not work. I rewrote my own experience here...read it and do exactly what I say, no shortcuts. One day I will sit down and rewrite the darn thing in common sense language. I can't stand a tutorial written over my head and there are a few here who do great stuff but are thee worse teachers. It reminds me of a calculus teacher teaching 2nd graders..nope! I realize this is frustrating...join the party! Your phone will work after the initial flash to either the Cingular 1.10 or European 1.09 but it's like stepping back in time. And unless you're really living in a cave, there is a stock Microsoft ROM for the damn thing. Don't ask me how much sleep or the lack of sleep I got during those 4 days. There's no comparison between locked and truly unlocked; once you turn this beast loose there's no going back.
berrywr said:
AndrewSH is correct; I had your exact same problem but before I get ahead of myself; your device must read x310e after you install the Euro ROM; if it doesn't you're dead right there. You may be the exception but no high capacity card worked on the two Titans I did; however, I did successfully use a PNY 4 GB thumb drive; a red one in fact that comes in a two pack - red/blue thumb drives from Wal-Mart with a Y cable. I tried an 8 gigger; no dice. When you flash SPL205; you need to be really, really patience; you might say to yourself this is not doing a damn thing...give it a solid 30 minutes before you give it up for dead; out of the blue my device came alive about 15 minutes into it and successfully updated the SPL by saying bootloader ok and radio ok. I cannot stress enough how important this 2nd step is and have the patience to wait it out. You only format your thumb drive/micro SD card once; that's it; all you have to do after that is remove the 1st ROM and replace it with the baby ROM from SPL205. One more thing, if you haven't renamed the image do so...change it from ETERIMG to ETERDIAG...those 8 letters that's it. "diag" behaves differently than "img". And look, I realize this stuff makes for boring reading but read all the threads on HSPL not just the Titan; I'm not implying you read everything here...but specific to HSPL and Windows Phone 7, you bet...regardless of device. I don't want to sound like a grouchy old man here but it took me 4 days to get this right and I did a level of reading I've never done before here and I've been flashing phones a long time; there's no quick fix solution here and to be frank, it's a crap shoot; it may and again it may not work. I rewrote my own experience here...read it and do exactly what I say, no shortcuts. One day I will sit down and rewrite the darn thing in common sense language. I can't stand a tutorial written over my head and there are a few here who do great stuff but are thee worse teachers. It reminds me of a calculus teacher teaching 2nd graders..nope! I realize this is frustrating...join the party! Your phone will work after the initial flash to either the Cingular 1.10 or European 1.09 but it's like stepping back in time. And unless you're really living in a cave, there is a stock Microsoft ROM for the damn thing. Don't ask me how much sleep or the lack of sleep I got during those 4 days. There's no comparison between locked and truly unlocked; once you turn this beast loose there's no going back.
Click to expand...
Click to collapse
I know what you mean, I know what mean... I have been reading a lot also. But coming late to the process, where all the posted links are dead, has left us late bloomers at a disadvantage. Thank you so much! Yeah I read the threads, and the tutorials. They were not QUITE clear enough, But the one thing I noticed right off the bat was, a LOT of people failed to simply read those posts. I read them and I can tell you that every one of them made the picture clearer. The European file errored out with a "wrong sign" or some such. So I don't even have a Rom in my phone. So I couldn't charge my battery. I bought a great little plug-in charger that I can put my battery in and charge it. Then I discovered that in Zune update mode that it will charge. So I've been doing that. I still have boot mode and PLC mode- and update mode. So I can still flash. So here goes nothing!:laugh: Thanks a cool million!
berrywr said:
AndrewSH is correct; I had your exact same problem but before I get ahead of myself; your device must read x310e after you install the Euro ROM; if it doesn't you're dead right there. You may be the exception but no high capacity card worked on the two Titans I did; however, I did successfully use a PNY 4 GB thumb drive; a red one in fact that comes in a two pack - red/blue thumb drives from Wal-Mart with a Y cable. I tried an 8 gigger; no dice. When you flash SPL205; you need to be really, really patience; you might say to yourself this is not doing a damn thing...give it a solid 30 minutes before you give it up for dead; out of the blue my device came alive about 15 minutes into it and successfully updated the SPL by saying bootloader ok and radio ok. I cannot stress enough how important this 2nd step is and have the patience to wait it out. You only format your thumb drive/micro SD card once; that's it; all you have to do after that is remove the 1st ROM and replace it with the baby ROM from SPL205. One more thing, if you haven't renamed the image do so...change it from ETERIMG to ETERDIAG...those 8 letters that's it. "diag" behaves differently than "img". And look, I realize this stuff makes for boring reading but read all the threads on HSPL not just the Titan; I'm not implying you read everything here...but specific to HSPL and Windows Phone 7, you bet...regardless of device. I don't want to sound like a grouchy old man here but it took me 4 days to get this right and I did a level of reading I've never done before here and I've been flashing phones a long time; there's no quick fix solution here and to be frank, it's a crap shoot; it may and again it may not work. I rewrote my own experience here...read it and do exactly what I say, no shortcuts. One day I will sit down and rewrite the darn thing in common sense language. I can't stand a tutorial written over my head and there are a few here who do great stuff but are thee worse teachers. It reminds me of a calculus teacher teaching 2nd graders..nope! I realize this is frustrating...join the party! Your phone will work after the initial flash to either the Cingular 1.10 or European 1.09 but it's like stepping back in time. And unless you're really living in a cave, there is a stock Microsoft ROM for the damn thing. Don't ask me how much sleep or the lack of sleep I got during those 4 days. There's no comparison between locked and truly unlocked; once you turn this beast loose there's no going back.
Click to expand...
Click to collapse
Did I do it!? I did the files correctly. Here is what it says;
P139100
HSPL2.5. 160015.3(137079)
eMMC SND 15188MB
CotullaH(F:81,ID:1,V11,B:F8)
Radio-16.23.06.10
When the phone starts up, I still see the HTC logo in green. So did I do it!? EDIT: BTW, when I restarted it, I had about 10 updates waiting for me. They were all AT&T apps if I'm not mistaken.
Mercurybird said:
Did I do it!? I did the files correctly. Here is what it says;
P139100
HSPL2.5. 160015.3(137079)
eMMC SND 15188MB
CotullaH(F:81,ID:1,V11,B:F8)
Radio-16.23.06.10
When the phone starts up, I still see the HTC logo in green. So did I do it!? EDIT: BTW, when I restarted it, I had about 10 updates waiting for me. They were all AT&T apps if I'm not mistaken.
Click to expand...
Click to collapse
Looks good. Now you have to make a decision - what custom to flash to your phone. Most of the customs here need Radio ver 17. As for me - I was using ver 17 for almost a year but than I returned to radio ver 16 - better signal quality and faster network detection (but it's absolutely the local problem of your carrier and coverage - so try by yourself). I wanna say that ver 16 and ver 17 radios need different roms - because of different OEM part. So choosing your custom - pay attention on the radio ver needed in rom description.
Thanks AndrewSh- Thanks everyone!
AndrewSh said:
Looks good. Now you have to make a decision - what custom to flash to your phone. Most of the customs here need Radio ver 17. As for me - I was using ver 17 for almost a year but than I returned to radio ver 16 - better signal quality and faster network detection (but it's absolutely the local problem of your carrier and coverage - so try by yourself). I wanna say that ver 16 and ver 17 radios need different roms - because of different OEM part. So choosing your custom - pay attention on the radio ver needed in rom description.
Click to expand...
Click to collapse
Thanks! The finish seemed so anticlimactic. The struggle, the doubt, the fear, the frustration, the lack of answers, a clear path to move forward on. Now that that is over I'm feeling much better. When it came down to it, my SD card started dying. The thumb drives didn't work. Then out of the blue I put the second file on my 1Gb stick and it flashed like a champ. Then the last file flashed over the same easy way.
I'm thinking about the Deepshining Rom. I like the way it looks. I'm looking for substance, but I'm also looking for eye candy. I run Windows 7- glass, aero... Then I set up a Windows 8 machine for my wife at work. They took the glass and aero out of it. Yuck. The stock Titan Rom looks like Windows 8. Deepshining looks like it has a glass aero look to it. Vivid colors also.
Hey thanks so much for your patient, helpful tutelage for everyone in helping to get us going. I couldn't have done it without the myriad of genuinely kind people here. Thanks EVERYONE. THANKS A COOL MILLION!
Related
While walking a colleague thru his first WM6 upgrade last night, I happened to notice that my IPL had somewhere reverted to 1.00 Well, I just couldn't have that, and set out to re-up it to 1.04
Reflashed it to Vodafone OEM ROM, which for some reason also requires flashing any Radio Rom to get it past the Windows splash screen. Still showed IPL 1.00
Flashed it with the SIM-CIM unlock files, got the IPL up to 1.01
Next, still really wanting to get back to 1.04, and not being happy with a device that was running any and all ROMs I was throwing at it, I tried MTTY and tried to force 1.04nb on it, it wouldn't take it, but it didn't quit.
Then, about 4 am, I got really clever, took the 1.04.nb file, ran it thru nbhtool and made a .nbh file.
Put that on the SD card as HERMIMG.img, and fired up the bootloader.
The file flashed quickly, and gave me the Whoopie, it Worked message.
So, I removed the card, and did a soft reset. And that was the last thing the little guy ever did, reset to dead.
Good thing is our company has these things laying about like some companies have ball point pens, so getting replacement took just minutes.
Now I stick strictly to the guides, improvisation is best left for other folks.
This has been another in the continuing series "Noobs and our toys, how we break em".
... and you admit to the whole world that you are a total idiot?
... I'm convinced
You got balls kid, I'll give you that....
More Like This in the Wiki
Thanks for the excellent HOWTO
I'll try your procedure in a couple of months time when it's time to buy something more exciting (Toshiba Portégé G900, i-mate Ultimate 7150 or Nokia E90 -- which one shall it be?).
Actually you should have thanked him for the HowNOTTo!!
Not if you're looking for a good reason to buy another phone
simple said:
Actually you should have thanked him for the HowNOTTo!!
Click to expand...
Click to collapse
That's kinda what I was going for... don't get too cocky too soon, and learn from my dorkup. And no, I don't mind admitting I bricked one, I know that many of the senior guys must have too at some point, there are those that have, and those that will.
One thing though, in the 4 or 5 months I've had a Hermes, it has been amazing to see the evolution in tools and utilities that have evolved. Now I just have to keep straight in my noob brain which tools are cross compatible.
This is exactly what happened to my hermes... I sent it to be repaired 2 months ago.. and it is still being repaired I don't know how on earth this can take so much time. They've been saying they are waiting for some "parts" for 5 weeks now :>
Isn't it a bit strange?
Okay today I intentionally bricked my phone. Not once, not twice, but 6 times with three bad ROM's (long boring day) and pulled the USB during the flashing at around 20%-95% as well as other no,no's
The experiment. To see how fast, and what I would use to unbrick it. Now being stuck in an all white screen or bootloader might bring fear or tears to some, but what I discovered is probably the best and easiest way to get your phone back to life in a relatively short amount of time.
If this has been covered before or mentioned elsewhere I didn't see it so I apologize if thats the case.
After I bricked each time I simply hooked up the usb cable to my pc. As you know when you are bricked or stuck in a loader Active Sync does not launch. What I found was that if you use a factory WM6 AT&T ROM it will still connect via usb and will flash said ROM 100% of the time restoring you're phone to a working state.
Now I did this 6 times today and it worked every time. I mean I really f'd with this second phone unplugging, Task Manager'd out during a flash, hard reset during a flash, etc. Every time it worked.
Hope this helps.
Well, you have been only lucky for 1 reason:
You always 'bricked' your device when it was in the middle of flashing the OS! This does not really matter as long as BOOTLOADER and CID are intact!
Do the same experiment but this time pull the plug at 15% and you will most likely fail to recover from that! At around 15% is the moment where the CID block gets written to the phones ROM.
Be very carefully that you do not 'brick' your device earlier because of in the state before 15% IPL and SPL are getting flashed! If you destroy the bootloader you can't do anything anymore!
If you are going to try that out please flash your phone first with the nbh from the CINGULAR WM5 (it is in the wiki) by using CustomRUU! CINGULAR WM5 has KITL enabled and you will be able to 'unbrick' your device by using the GUIDE in the WIKI.
I WILL NOT BE RESPONSIBLE IF YOU BREAK YOUR DEVICE TO A POINT OF NO RECOVERY POSSIBLE!
CID block is never written to the phone, it's just an area of storage inside the GSM chip.
however, if incomplete code is flashed to the GSM chip, the radio AT interface cant' boot... and then there's no way of talking to it, hence making it now dead.
On a different note, if the Radio Bootloader is in the middle of flashing (although I believe 0108 is persistent) and the connection is broken, you're now royally ****ed.
So, the GSM chip is not in the phone then?
<just kidding!>
However,
pulling the plug around 15% will most likely end in a brick! That was where I had my pc crash - thankfully KITL was enabled!
Tried again
Okay I did this at 12% and then at 16% (could not time it right for 15%) and I was able to recover. If I am just one lucky bastard, and this is highly against the odds, I would say don't do this on purpose like me.
My only point of the experiment was to see if I was to ever brick, at least I knew of one possibility that would recover it. And when looking at it like that it was a success.
Now that all is back to normal, I have HARD SPL.7 and have no issues.
ihavetinyballs said:
Okay I did this at 12% and then at 16% (could not time it right for 15%) and I was able to recover. If I am just one lucky bastard, and this is highly against the odds, I would say don't do this on purpose like me.
My only point of the experiment was to see if I was to ever brick, at least I knew of one possibility that would recover it. And when looking at it like that it was a success.
Now that all is back to normal, I have HARD SPL.7 and have no issues.
Click to expand...
Click to collapse
HARD SPL? try a different SPL and then try it again...
Oh yeah... Try to kill your bootloader too... And if it's like one of my devices
(HTC Charmer with a black screen... Only the power led lights up for half a second when I press the power button)
then try to flash your "holy" rom
eh, i don't understand why people call it bricking if only the OS needs a reflash
I wasn't clear. The phone was never hard SPL'd till after the experiment when I decided to lock the ***** up to keep it safe from doing more stupid stuff. The os flash wasn't all I crashed out on. I did this with this on purpose with the radio versions as well.
ihavetinyballs said:
I wasn't clear. The phone was never hard SPL'd till after the experiment when I decided to lock the ***** up to keep it safe from doing more stupid stuff. The os flash wasn't all I crashed out on. I did this with this on purpose with the radio versions as well.
Click to expand...
Click to collapse
then you are crazy
There are 2 possible explanations for your "luck":
Either the ROM you're flashing contains nothing but the OS and maybe the EXTENDED ROM in which case it does not really matter if you pull the plug because of your BOOTLOADER and GSM will remain intact or your FLASHING UTILITY 'ignors' the BOOTLOADER / GSM flash and writes only the OS and EXTENDED (which would have the same effect as case 1 when pulling the plug!).
However,
flashing an entire ROM takes a while, especially between 12% and 30% if you flash IPL / SPL / SPLASH / GSM / OS / EXTENDED - there is enough time to pull the plug at 15% because of it takes almost a minute until it jumps to 16% ...
I don't want to animate you to try that out because of sooner or later you will brick the device for sure!
Can you host the ROM file + flashing utility you used for your experiments, so, that we can download it and take a closer look?
ihavetinyballs said:
I wasn't clear. The phone was never hard SPL'd till after the experiment when I decided to lock the ***** up to keep it safe from doing more stupid stuff. The os flash wasn't all I crashed out on. I did this with this on purpose with the radio versions as well.
Click to expand...
Click to collapse
The world belongs to renegades and mavericks...
I did it with TNT's latest as well as VP3G 3.62
OK I'll bite where is WM6 AT&T ROM?
I have a bircked phone tytn (tried to unsucessfully unbrick around 50 times), not sure why or where it bricked.
Can reload but sticks at screen alignemnt EVERY TIME.
Was given as a challenge (failed so far).
If I could find this and it worked I be happy chappy long time.
If it works of mine it will work on anyone's.
Give it up dudes (or duedess if there is one out there).
Here is the secret. Use the bundled WM5 Cingular ROM from HTCs download site.
ihavetinyballs said:
Here is the secret. Use the bundled WM5 Cingular ROM from HTCs download site.
Click to expand...
Click to collapse
Do you have a link, filename or even better can post on Rapidshare?
Edit: btw, the moniker is hilarious!
rob8 said:
Do you have a link, filename or even better can post on Rapidshare?
Edit: btw, the moniker is hilarious!
Click to expand...
Click to collapse
He gave you the info you need. Go to HTC's site. Or use google.
K since i took the time to post this I might as well link it.
Go to the bottom of this page.
It is about time to give out a WARNING !!!
People, do not try to brick your device and trust in that you can recover from that by using the ROM from the HTC's website! This is not a magic tool and it won't bring your Hermes back to life if your device is really screwed up! There is nothing in the Cingular ROM what 'magically' does the trick! IHAVETINYBALLS was either just lucky or he isn't really bricking his device (consciously or unconsciously).
If you do not believe me ask other senior members with lots of experiences, such as OliP ...
However, I know there is no way of stopping fools to do foolish things, so, go ahead, destroy your expensive toy! You can always find a new one on eBay ... !
For all the retards who don't get it. (meaning the point)
To the dip**** retards who don't get the point. Like I said, I am probably just lucky. And like I said again, DO NOT try this unless your phone is stuck and ****ed, it was just an experiment. I have two 8525's one I bought as a refurb from AT&T for $99 and another one that was from an angry owner who threw it away at the AT&T store (as it was bricked and now "useless") and I pulled it from the garbage bin. Recovered it (just did a hard reset and put in a new battery and factory ROM and did a few experiments.
It didn't cost me anything and I did put a warning out there. The point of it all was that if you give up on bringing it back to life, maybe just maybe you should try this out.
Obviously if your phone is working just fine, don't do this or your a ****ing retard. Its meant for bricked or stuck phones as a possible recovery as it worked on said phone numerous times in various states of bad flashing and various types of ROMs.
This phone is now running vp3G 3.62 and now has HARD SPL.7, and Radio 1.54.07 and is running flawlessly.
So one mans brick/stuck frustration is making for an excellent spare / backup for me.
trying now
ok - have hybrid brick (no KITL, screwed CID and radio)
if everyone crosses their fingers at the same time maybe it will help???
will post back results!
Bugger
thanks for giving me hope! but alas...no good
hopefully someone else can figure out how to get back from a hybrid brick of no KITL and SPL 1.09
I decided to play with the Debug Tool 3.2 and found all the Flash flags were set to 0. I saw there was a setting for Radio Flags. I set it to 8, wrote it, rebooted, just to see if there was any change in EDGE/3G capability (I have a Euro TP and I'm in the US). Since that didnt have any noticable effect, I changed the Radio Flags to 65535 , rebooted. The Phone showed the ToucHPro boot screen, then displayed the red version numbers and thats it.
I did a hard reset to reinit everything, no help. I reflashed the radio, no good either. Just reflashed the OS to DCS 1.5, still stuck.
Perhaps theres a way to reset the flags via MTTY in the bootloader, or through an AT command. If anyone has any ideas to try, let me know.
Edits:I just viewed the DebugToolAp.html and I think i know what I did wrong. Since I wrote a value of 65535 (16 bits, all ones), Im guessing the debug app properly converted it to hex and wrote 2 bytes instead of one, overflowing into the next location, where each 1 bit disables a piece of hardware. All 1's in that location would disable everything.
Now to figure out where that flash is and how to set those 2 locations back to 0's. I'm guessing I'll need a MFG SPL that has rtask enabled.
The Debug Tool calls the flash "PureFlash". Anyone know anything about it? Perhaps I can use JTAG to write to it? (I have a Wiggler)
Edit: running info 8 reports that I have 8 bad blocks, and based on similar symptoms posted on xda, the trick seems to be to run task 2a to fix the bad blocks, then task 28 to re-format the flash. But task 2a doesn't seem to do anything.
UPDATE: All the damage I did was repaired from remote by cmonex. I've learned my lesson, leave the tinkering to the experts!
dude if you want to brick your TP,instead of bricking it send it to me. i would be glad to accept.
lover said:
dude if you want to brick your TP,instead of bricking it send it to me. i would be glad to accept.
Click to expand...
Click to collapse
I'll keep that in mind next time I feel like wasting $1000
I can hear the interweb say "You dumb ass!".
rotohammer said:
I'll keep that in mind next time I feel like wasting $1000
I can hear the interweb say "You dumb ass!".
Click to expand...
Click to collapse
well kudos to you sir for bricking it and still keeping cool
maybe you can get some ideas in frankenkaiser-- it's connecting via radio SPL (OEMBSL) and I remember there is a read/write operation in there.
pfcsabre said:
well kudos to you sir for bricking it and still keeping cool
Click to expand...
Click to collapse
I'm not sweating it until someone who knows better tells me I done hosed it!
I still have a Kaiser and a Hermes, so I can still make calls
I'm browsing the the strings in HARD-SPL and see a lot of references to related bits, so I'm hoping theres a simple command in there to run to reset it.
rotohammer said:
I'll keep that in mind next time I feel like wasting $1000
I can hear the interweb say "You dumb ass!".
Click to expand...
Click to collapse
well attempting to brick sounds like wasting to me.
hehehe, if you want to brick flash a kaiser radio on raphael
I'm more of a dumb ass now
Update: True to the saying "A little knowledge is dangerous", I've succeeded in making matters worse.
Realizing task 2a wasn't working in HARD-SPL, I flashed back to the stock SPL, did the task 2a and then task 28. But now I can't flash HARD-SPL back, I just get "error 262". Flashing HARD-SPL from the SD Card just hangs on the loading message (never gets to the bar graph).
Since the CID is HTC_032 (Eastern European), I can't even try a SHIPPED ROM as I can't find one yet.
Running info 8 I only get checksums for SPL, not IPL. And I still have bad blocks.
I'm guessing the only thing left is to wait for a modified SPL that I can load into RAM, jump to it, and then try reloading HARD-SPL.
I'll stop fscking with it now, if I make it any worse then I know its JTAG time.
Send it back for warranty... if YOU cant boot, then THEY cant too and see that you have modified the rom
licht77 said:
Send it back for warranty... if YOU cant boot, then THEY cant too and see that you have modified the rom
Click to expand...
Click to collapse
Thats no fun I rather sit with it and wait for one of the big guns to advise.
I would suggest you pm cmonex , explain what you've done, and see what she recommends.
hey there, I'm checking this thread as per your PM.
classic case of reading BUT not reading enough. and also messing around more even after realizing something is wrong.. I hope you agree
I'll first try to correct all the wrong information mentioned here...
1) the debugflags have nothing to do with the 3G enabling.
2) task 2a is only useful for hermes, you're lucky it didn't kill the SPL totally. why do you think it is removed from hardspl otherwise.
3) task 28 is a plain hard reset, same as the button combo for hardreset. (BTW, many touch pro's have the same number of bad blocks, mine included, god knows why)
4) JTAG is not as simple as that. what devices have you jtagged before? any devices that have no publicly available documentation for it?
5) frankenkaiser will not work on a diamond/touch pro, because the normal USB interface is disabled in oemsbl command line and in dload mode. please no one should try setting any bootmodes in oemsbl command line!!! instant brick if you set 1, 2, or 3. and by brick I really mean brick, this touch pro right now can still boot SPL so not a true brick.
6) there is no IPL since kaiser came out. now radio bootloaders boot the SPL, not IPL.
7) if you have no shipped rom for this, you're in a much bigger trouble than originally even if you manage to unset the flags. btw there is a way to unset them, but the way I know of will only work with hardspl, we'll see if there is any other way. but again, your biggest trouble isn't the flags right now.
ok, i'll reply to your PM too and see how to go from there.
next time do not play around that thing what uu dot know deep enough....
rotohammer said:
I'll keep that in mind next time I feel like wasting $1000
I can hear the interweb say "You dumb ass!".
Click to expand...
Click to collapse
Next time you want to throw away $1000 consider donating it to a worthwhile cause. There are lots that need the money!
topspeclt said:
Next time you want to throw away $1000 consider donating it to a worthwhile cause.
Click to expand...
Click to collapse
I don't give to charities, only to hackers!
Man I really feel for you, Ive been there and done that only it was a Hermes I'd cooked and flashed a bad rom heart broken at the time.
ratcom said:
Man I really feel for you
Click to expand...
Click to collapse
I got what I deserved fair and square. Let that be a lesson to all the kiddies out there. There's still a .0005% chance that it an be saved. If not, then it becomes spare parts when I get a new Fuze
Let do a second chance, bro... give it back to the seller for warranty...
Another hope....
KChauJen said:
Let do a second chance, bro... give it back to the seller for warranty...
Another hope....
Click to expand...
Click to collapse
I thought about that, but no, thats not my style.
On the bright side, I flashed HyperDragon III Opal onto my Kaiser last night and I have to say its quite impressive. It's like having a Touch Pro, but faster! Cheers to Sakajati!
Just as cmonex said ..
but in my opinion it isn't bricked at all ... it's just waiting for the right spl and oemsbl to rewrite the config flag.
We'll have a look at it.
Cya,
Viper BJK
I remember GSLEON3 taking his Kaiser out of action with a task 2a for month's until Franken Kaiser came along.
Don't give up, I'm sure Viper and cmonex can get it sorted.
Ta
Dave
Hi Friends,
Everything was fine until my HD2 it turned off and since then ( two weeks ago) all it shows me when I turn it on is a black and white striped page( it goes to bootloader mode though and everything is fine,! it's not a hardware problem) . I've tried everything you name it,( Flashing via SD card, Using Mtty, Usin diff radios, and a buch of other stuff) I have the T-mobil insurance plan where I'll tell them the problem and they will send me a new phone, all I need to do is to get rid of that CotullaHSPL so that they wont find out that the phone has been messed with. So, My question is how do you recover to the original SPL, ((I've tried uninstalling the HSPL and it goes all the way to 100 but once the phone restarts and I go to bootloader it still shows me "CotullaHSPL"
Thanks,
Amir Najafi
its a reasonably common problem, , radio gets stuck, flashing appears to work but doesnt.
there are some out there threads about chilling it for half an hour, flashing certain test roms and the like, but there is no real answer to it. (not taht ive seen)
you could always try flashing a non tmous stock rom, (with a 51 radio) and hoping it takes enough to brick it completely, or go for the ten seconds in a microwave option, but ive always thoughtthe danger of exploding teh screen a bit much.
samsamuel said:
its a reasonably common problem, , radio gets stuck, flashing appears to work but doesnt.
there are some out there threads about chilling it for half an hour, flashing certain test roms and the like, but there is no real answer to it. (not taht ive seen)
you could always try flashing a non tmous stock rom, (with a 51 radio) and hoping it takes enough to brick it completely, or go for the ten seconds in a microwave option, but ive always thoughtthe danger of exploding teh screen a bit much.
Click to expand...
Click to collapse
I have accidental on the phone worse comes to worse, I'll just do that, I've heard of freezing it for half an hour, but would that really work?!
lol, no idea, ,
i can imagine a scenario where corrupt software is overpowering the hardware so much that it is failing, and that cooling it may allow it to work past its thermal limits just long enough to flash, , , but its more like an old wives tale, an urban legend really, doing somethng just because someone else did it and it worked i think, luck of the draw. 1 - freeze phone - 2 - into bootloader - 3 - sacrifice chicken - 4 - flash hspl - 5 - recite ' arr ay dee eye ohh ' over and over - 6 - flash radio.... hehehe.
samsamuel said:
lol, no idea, ,
i can imagine a scenario where corrupt software is overpowering the hardware so much that it is failing, and that cooling it may allow it to work past its thermal limits just long enough to flash, , , but its more like an old wives tale, an urban legend really, doing somethng just because someone else did it and it worked i think, luck of the draw. 1 - freeze phone - 2 - into bootloader - 3 - sacrifice chicken - 4 - flash hspl - 5 - recite ' arr ay dee eye ohh ' over and over - 6 - flash radio.... hehehe.
Click to expand...
Click to collapse
HA HA HA HA HA HA HA HA HA
That is the funniest sh*t I have heard all day.
Now as for the op's problem, if the phone feels hot after you try the flashing or after you leave it on for a while then you might have a processor that is slowly frying itself are causing itself to lose it's connections to the mother board because of the heat.
I know you said you tryiex everything but go get yourself a cheap 2GB SD card and format it even though it is new and the use it to put you ROM on e ergonomics time you try a ROM and try to flash via your SD card. If one ROM does not work delete it from the SD card download another and copy it to the SD card and try to flash it. One of them had got to eventually flash. Just be aware that if you flash any official ROM via SD card it will revert you back to SPL and you will have to reflash HSPL
I've tried the chilling thing btw, lol, it didnt work hahaha
I did one flash...to TNT version 4xx, and I loved it...but I'm finding I'm getting lots of Google Framework errors and generally just kind of want to start from scratch, over again.....go back to the latest version of the official viewsonic roms.
Sadly I didn't use clockwork or anything so I think my original files are history
I know there are lots of threads, and I tried to follow one about snagging a rom and moving it to the Root and all it does is re-install TNT I think I am "not getting something".
Can someone walk me through this....
The force closes can be fixed by re-partitioning your sd card. Part 1 Step 7 in this tutorial:
http://forum.xda-developers.com/showthread.php?t=865245
But partitioning will erase everything, and is usually done after installing cwm and before flashing a rom.
You really don't want to go back to stock, especially if it's only to gain stability. All the force closes will go away when the tablet is properly formatted.
If your looking to go back to stock, I like nvflash, but there are easier ways.
http://forum.xda-developers.com/showthread.php?t=861950
Force closing is a known issue that can be easily fixed by repartitioning your internal sd card to the right specs. It has nothing to do with your newly flashed rom.
What you need to do is back up all your data on the sdcard and then go into clockworkmod advance and repartition to 2048/0.
Added by edit.
To be honest, your original post tells me the gtab isn't for you. I say a mainstream device like the ipad is more for you. Here is why. In order to use the gtab, you need to do the following things.
(1) Install clockworkmod.
(2) Use clockworkmod to repartition to fix the force closing issue.
(3) Use clockworkmod to flash a new rom.
And you're done. The entire process takes about 10 minutes at most.
Again, steps 1-3 should take you 10 minutes at most and the device is ready for use. If you find yourself frustrated by one of these steps or that you're spending more than 20 minutes, then the gtab is not for you and you need to get a mainstream device.
goodintentions said:
Again, steps 1-3 should take you 10 minutes at most and the device is ready for use. If you find yourself frustrated by one of these steps or that you're spending more than 20 minutes, then the gtab is not for you and you need to get a mainstream device.
Click to expand...
Click to collapse
This recommendation is of course assuming you have no determination whatsoever, and are incapable of learning anything new.
brettdwagner said:
This recommendation is of course assuming you have no determination whatsoever, and are incapable of learning anything new.
Click to expand...
Click to collapse
Look, for most people this device is a toy. I use it at work, and I suspect most people don't do this. Let's admit it. Modding a device isn't for everybody.
I went into modding the gtab as a total android newbie. And yet it took me all of 15 minutes to figure out how to install clockworkmod, repartition, and flash a custom rom. Then a week after I flashed a custom kernel.
You just can't ask everybody to go through the headache of modding a device if they have neither the will nor the time.
I said 15 minutes because that was my first time ever modding an android device. After that first time, it took me about 5 minutes to do my second device.
It's a simple process to go through. If a person gets stuck on any of those 3 steps, then I think it's best that they get a mainstream device. The gtab just isn't for everybody.
HeadRusch1,
I think you can handle modding the gTab. If you understand how a file system works, can extract a zip, and have already flashed a custom ROM then your about 90% of the way to a smooth running gTab. As mentioned above, you simply missed one step.
I understand the "10 minutes or forget it" argument, however I think it's wildly inaccurate when gauging a new user's potential competency with the gTab. If you find yourself frustrated then go read some more, search for a solution, or ask a question. It should take a long time to get comfortable modifying Android devices, there are tons of loosely documented best practices, but don't bail early because it's hard.
PS.
This assumes your looking for a device to tinker with. Goodintentions is right for users who are looking for iPad equivalent. I just assume that users looking for a cheap iPad rarely make it as far as XDA. And if they have, then it's a good opportunity to encourage further exploration.
The reason I gave the 20 minutes advice is because I've seen too many people buying the gtab thinking they got an ipad. The gtab isn't mainstream at all even though it's outsold a lot of the mainstream devices out there (ahem xoom) by several orders of magnitude. Customer support for the gtab is almost non-existent. And don't hold your breath for updates from viewsonic.
I absolutely love my gtab. I am currently running vegan ginger OC to 1.2ghz. The speed on my gtab is absolutely stunning. There's no jerking at all. My touchscreen is incredibly sensitive. Viewing angle has never bothered me. I love the full size usb where I can just put a memory stick in there just like my laptop. The autocad app is extremely helpful for me. In fact, it's been a whole week since I turned on my laptop.
That said, again, this device is not mainstream. Meaning it's not for most people. I am absolutely convinced that most people would be better off with something like the ipad or transformer.
Based on my experience, there are two types of people in the world of gadgets. (1) Those who sees a problem and see the end of the world and (2) those who sees a problem and try to get around it.
An example of #1 is my friend Sarah. She wanted to use my gtab to get a feel for it. She said the touchscreen bothered her and that she was more comfortable with a laptop touchpad more. And then she said "I don't know, I think I'll be better off with an ipad." LOL. Boy is she going to be so surprised to find out the ipad also uses the touchscreen rather than an touchpad.
Anyway, another example is one of my colleagues. After I told him the autocad app doesn't work with 3-D view yet, he acted like it was the end of the world. Me, I just use the side, top, and front views in my demos. Works just fine for me.
Anyway, I'm rambling now. The point is my experiences tell me most people are better off with something like an ipad or transformer. Since those devices are mainstream, people can't say "of course you can't do this, you can't do that". With the gtab, since it is not mainstream, the smallest inconvenience means the end of the world.
HeadRusch1 said:
I did one flash...to TNT version 4xx, and I loved it...but I'm finding I'm getting lots of Google Framework errors and generally just kind of want to start from scratch, over again.....go back to the latest version of the official viewsonic roms.
Sadly I didn't use clockwork or anything so I think my original files are history
I know there are lots of threads, and I tried to follow one about snagging a rom and moving it to the Root and all it does is re-install TNT I think I am "not getting something".
Can someone walk me through this....
Click to expand...
Click to collapse
Plug the gtablet into the computer.
Mount it for file transfer when prompted.
Check for an "update.zip" file at the root of the SD card (That's the tablet's 16gb internal memory). Delete it using your computer. That was causing TNT to be reloaded.
Here's the link to the original 3588 version they shipped with: http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3588-user.zip Save it to your computer. Rename it "update.zip". Copy it to the root of the gtablet SD. Shut off the tablet. Unplug the USB cord. Restart with power & vol +
It should update.
If anyone notices a mistake, feel free to correct me. I've only flashed from stock 3588 to Vegan Ginger. So a whole 1x.
For what its worth, I tinkered and now I'm good.
Got NVFLASH working, went back to stock. Then went to Clockwork, then went to Vegan 5.1.1, then to CM7, now back to Vegan. I've found some apps that work and I'm liking it more. For the record, I own an Ipad2 as well.
Now, to those who chose to comment: You guys need to understand that many of those links are drowning in "extra information", and that is fine if you don't mind clicking hyperlink to hyperlink to do some trial and error, but now with multiple install path choices and whatnot, it gets confusing and it also means you have some time. I asked for someone, possibly someone in my shoes who has been down the path, to walk me through the steps.
Some of you did, some of you projected some assumptions with the underlying message of "RTFM".
This, too, was my first dip into the Android pool. Thanks for the help.
HeadRusch1 said:
I'm getting lots of Google Framework errors and generally just kind of want to start from scratch, over again.....go back to the latest version of the official viewsonic roms.
Sadly I didn't use clockwork or anything...
Click to expand...
Click to collapse
I had that issue and didn't have clockwork.
Solution:
1: install clockwork
2: boot into clockwork, and select 'fix permissions'.
3: reboot, tablet fixed