There's a lot of beautiful ROMS for our device but most of the new ones face one problem SOD (Sleep of Death) when the device goes to sleep you can't wake it up.
What "causes" SOD?:
* Bad Flashes
* Residual code for flashing you device a lot
* Newer SYS cooked in ROM
I've been searching for a solution and this is what I've found.
qbus00 said:
That's something which I have to do...
I'll downgrade SYS to 21896 soon which does not face SOD problem.
Click to expand...
Click to collapse
wuub said:
MTTY is a software that allows you to format internal storage before you flash a new rom.
By doing this you will make sure that no residual files or past informations are kept in the system. This usually fixes random crashes and weird behaviours on PDAs.
This is the DIAM100 thread but i've been using on D2 without trouble : http://forum.xda-developers.com/showthread.php?t=540290
Click to expand...
Click to collapse
From HD2 ROM Thread
rjd1 said:
I started having issues similar to this and a few other non-normal issues with NRG ROM. I ended up loading carrier ROM again, re-flashing 2.08 radio and then 23544 COokie ROM and all cleared up. It appears alot of risidual code happens with the HD2 ROMS regardless of AS or SD card ROM loading. I added to my flashing every 2 weeks or so - I am a flashaholic...
Click to expand...
Click to collapse
doloop said:
Hi,
(To make it short, follow the red sentence to format your phone to avoid roms problem.)
I hex-edited RomUpdateUtility.exe so it runs task 29 right after flashing ruu_signed.nbh
Task 29 formats your phone memory (=binfs). It prevents weird error appearance when you flash new Roms.
you stile need something to flash, it may be a radio, a splashscreen nbh or a blank nbh file (shadrack repack provide a tiny blank nbh).
Usually you don't need anything more than the file provided in the packs. so:
Just unzip and run task29.exe .
Eventually, you may replace ruu_signed.nbh with the radio/splashscreen of your choice.
When update status reach 99%, press vol down button, and keep it pressed until the phone reboot to the three color bootloader.
After the phone reset itself, your old rom will be gone, so it can't boot to winmo: binfs has been formated, your phone memory is clean.
if you fail to press vol down key and your phone get stuck on the white screen, just remove your battery, then try again: press power, and keep vol down pressed immediatly next, until the phone get to RVB bootloader.
When your phone is back to RVB bootloader screen, use the leocustomruu.exe provided with your favorite rom package to flash a new rom, or flash it from memory card using standard procedure.
Repack by ShaDrac (Recommended):
http://forum.xda-developers.com/showpost.php?p=5848003&postcount=19
No radio needed, smaller, faster.
Video tutorial by [★]
http://forum.xda-developers.com/showthread.php?t=621930 (Video 9: How To Perform A Task 29 Without MTTY)
direct link: http://www.youtube.com/watch?v=DtTDuc4V4cU
To do:
remove the "reset" command from task29.exe, to stay into boot loader screen. Then, one should flash the new rom immediatly using their cook's flash utility.
Original files
http://www.megaupload.com/?d=J3OELQ8I
RS mirror, by Sardelisp
http://www.rapidshare.com/files/361617741/Radio_2.08.50.05___task29.zip
Edit, distribute, repack, comment and spread these files as much as you want.
Click to expand...
Click to collapse
I've tried some of these suggestions, but none work. I tried Task29 flashing a boot screen and everything was erased. I flashed a new ROM and guess what? SOD even with task29
If you want to try any of these procedures do it "At your own risk" task29 for Topaz will flash a custom boot screen and erase your WinMo.
Use it at your own risk
And you, got any solutions that want to share?
PS. I'm sorry for my english, remember I'm El Toro not "The Bull"
I have an ATT Pure and have flashed every ROM on here that is in English and not once has one failed to boot or contiunue running till I get tired of it. You do have to use HARDSPL with all of them. My only ROM issue are the ROMS that have everything in the Start menu instead of separate folders. It seems so disorganized but that is a different topic.
I just wanted to point out it must be your phone or you have not used hardSPL or maybe your phone vendor bugged it so you can't flash a new ROM.
Oh I also noticed you say it's and ATT thats unlocked. That could be the issue. Mine is not unlocked. BTW being unlocked would mean it is not an ATT unit any more right?
Solarenemy68 said:
I have an ATT Pure and have flashed every ROM on here that is in English and not once has one failed to boot or contiunue running till I get tired of it. You do have to use HARDSPL with all of them. My only ROM issue are the ROMS that have everything in the Start menu instead of separate folders. It seems so disorganized but that is a different topic.
I just wanted to point out it must be your phone or you have not used hardSPL or maybe your phone vendor bugged it so you can't flash a new ROM.
Oh I also noticed you say it's and ATT thats unlocked. That could be the issue. Mine is not unlocked. BTW being unlocked would mean it is not an ATT unit any more right?
Click to expand...
Click to collapse
Thanks for replying, my pure is Hardspl'd with the latest 2.51 Olinex. It's unlocked meaning Sim Unlocked that I could use it with any Operator that uses a Sim Card, and yes I could flash every single ROM that it's posted in this Topaz ROM Development thread. I've been using Dutty WWE Official Test ROM since he posted it and no problems have come up at all. The "new ROMS" are the ones that caused the SOD even our chefs have suffered from this bug. So it's not the device.
I never had the SOD happen to me. And i have htc pure too.
Apparently, the great majority of us do not have this problem, and have never heard of it. As long as MTTY is run, I've never heard of anyone having a sleep of death issue.
eltoro said:
There's a lot of beautiful ROMS for our device but most of the new ones face one problem SOD (Standby of Death) when the device goes to sleep you can't wake it up.
What "causes" SOD?:
* Bad Flashes
* Residual code for flashing you device a lot
* Newer SYS cooked in ROM
I've been searching for a solution and this is what I've found.
From HD2 ROM Thread
I've tried some of these suggestions, but none work. I tried Task29 flashing a boot screen and everything was erase. I flashed a new ROM and guess what? SOD even with task29
Qbus13 Com2 ROM with SYS downgraded doesn't face SOD.
If you want to try any of these procedures do it "At your own risk" Keep in mind that HD2 task29 files are intended for that specific device not for the Topaz I put them here just for reference, If you want to try the task29 for Topaz I could post it here, It will flash a custom boot screen and erase your WinMo.
And you, got any solutions that want to share?
PS. I'm sorry for my english, remember I'm El Toro not "The Bull"
Click to expand...
Click to collapse
Standby?
I've ran a few Rom's here from energy 6.5.5 to Dutty R6 - R10
with the latest 6.5.x builds, every once in a while after coming back from standby the device will be unresponsive. The touch screen seems to not do anything, but the hardware keys work fine, typically placing it back to sleep and waking it up again seemed to fix it... I have had to pull the battery once.
This didn't happen on the 6.5 builds, only 6.5.5.
Mostly running Energy Aprl and May releases.
I had SOD. I've solved it by changing my SIM card since previous one was more than 10 years old. With new one I never had this problem.
I'm using NhatHoa TopazRom 23563 WWE so far no SOD after 2 days of using it.
I flashed the Dutty's Topaz Sense 2.5 Holy Grail R10 |WWE| rom last night and get my phone goes into the SOD pretty much every time I leave it alone for more than 10 minutes. I have an HTC Pure as well. From the searches I've done it seems solving this problem is pretty much a turkey shoot. I just wish there was a concrete solution, as I kind of like being able to use my phone.
reptiletim said:
I flashed the Dutty's Topaz Sense 2.5 Holy Grail R10 |WWE| rom last night and get my phone goes into the SOD pretty much every time I leave it alone for more than 10 minutes. I have an HTC Pure as well. From the searches I've done it seems solving this problem is pretty much a turkey shoot. I just wish there was a concrete solution, as I kind of like being able to use my phone.
Click to expand...
Click to collapse
The same thing happened to me with that ROM but if you flash Dutty's Topaz Holy Grail R11 WWE it's fine no SOD
On the Touch Pro 2, Tilt 2 section they have a lot of theories about what causes SOD http://forum.xda-developers.com/showthread.php?t=648134
but still no solutions.......
They said that Task29 is the solution but is not I'm posting the Task29 files if you want to try it yourself
INSTRUCTIONS:
Originally Posted by SacTilt
Some of you are making this too difficult. I've posted this before, as this is all that needs to be done. Task29 does not remove your radio or your splash screen. It only clears the ROM, therefore, all you need to do is run Task29 and then flash your ROM. This is how I do it from the PC.
Connect to PC via Active Sync/WMDC.
Execute Task 29.
When phone boots to "Touch Pro 2" screen (or whatever your splash screen happens to be), I hold down the volume down button while hitting the reset button.
Once I'm on the Bootloader screen, and it shows "USB", I flash the new ROM from the PC as I normally would.
When the phone vibrates, indicating the ROM upgrade is complete, I disconnect the phone from the computer.
Click to expand...
Click to collapse
Of course in this case will be your Topaz, Pure, Touch Diamond 2 boot screen
CREDIT:
all credit goes to doloop
Originally Posted by doloop
Hi,
I hex edited RomUpdateUtility.exe so it runs task 29 right after flashing ruu_signed.nbh
As every one understand this command format the rom,
Just unzip and run task29.exe . You may replace ruu_signed.nbh with the radio of your choice.
After the phone reset itself, your old rom will be gone, so it won't boot: binfs has been formated, your phone memory is clean.
You'll need to power up in bootloader mode (press vol down right after power key), then use the leocustomruu.exe provided with your favorite rom package, or flash it from memory card using standard procedure.
Click to expand...
Click to collapse
This files are for Topaz only it will replace your Boot screen or if you want to replace it with another boot screen or radio is up to you. I like the boot screen because the process is faster. **Use it at your own risk**
Related
Hi,
I have just tryed to flash both newest laurentius rom and newes kwbr rom
Flashing goes ok, but when all files are loaded, phone just resets and starts all over again.
im on spl-1.56 Olinex
Help needed
Whenever you flash a new rom your phone will automatically reboot and start up again. The phone will need to be setup again with date/time etc but connections etc should automatically setup itself.
This is similar to a hard reset as everything has been wiped from phone apart from OS and whatever you had stored on SD Card
Once setup go to Settings > System and it should state which rom you have installed
Yes but it starts up again with setting time date and so on.
When finished loading files, it starts over as you says, but then rom starts loading again. its like it hard resets all the time instead of just resetting..
I flash. allign screen - set time date and so on - files load - phone restarts
And then i shall allign screen - set time and date - load files - phone restarts
and on and on and on
Megawhopp said:
I flash. allign screen - set time date and so on - files load - phone restarts
And then i shall allign screen - set time and date - load files - phone restarts
and on and on and on
Click to expand...
Click to collapse
Ah, right. Apologies. Now I understand your problem better.
Had you ever successfully flashed a rom? Or has thius always happened with a cooked rom?
Megawhopp said:
Hi,
I have just tryed to flash both newest laurentius rom and newes kwbr rom
Flashing goes ok, but when all files are loaded, phone just resets and starts all over again.
im on spl-1.56 Olinex
Help needed
Click to expand...
Click to collapse
You can better ask it in L26 ROM topic, but I know that Laurentius ROM (2.3 or 2.4) KEEPS hardresseting automatically due to bugs in his cooked rom. After 2 or 3 times automatic HR it stops....
Yes i have successfully flashed roms, i came from kwbr 2.1
i have tryed with more roms than laurentis´ also with kwbr 2.3 and 2,3,1
Megawhopp said:
Yes i have successfully flashed roms, i came from kwbr 2.1
i have tryed with more roms than laurentis´ also with kwbr 2.3 and 2,3,1
Click to expand...
Click to collapse
Ok, sounds like a hardware problem to me. I've had only automatic Hard Resets with L26's Rom. No problems with Kwbr or Dutty's roms.
Try flashing via USPL and tell us how it goes.
had same problem with l26 rom will never use laurentius rom's again, dutty's and miri's roms are the best
I have tryed with USPL and its the same
Now i cant do anything from my computer. How is it that i flash from sd card?
Credits to JohnQ
"take a look at your SD card. direct folder storage card/sdconfig.txt. delete the inside code. im sure there is a code which means hardreset after flash/hardreset. i dont know what it means but i just delete it. but it still hardreset again. so let it hardreset again. then it will be ok until you hardreset your self. lol."
I did it and it worked as a charm. Have you flashed you device with the memory card inserte into it?
no i didnt flash with memory card in it, and memorycard is not in it now
i just managed to flash danish ship rom, but cant seem to flash stock uspl
i will see if phone starts up wit danish ship rom
It worked.. My phone is now alive with danish ship rom..
I will now try to flash newest from Miri..
Megawhopp said:
no i didnt flash with memory card in it, and memorycard is not in it now
i just managed to flash danish ship rom, but cant seem to flash stock uspl
i will see if phone starts up wit danish ship rom
Click to expand...
Click to collapse
Anyway, take a look into you SD Card through you PC...is there a folder named "sdconfig.txt"?...if so, take a look into this "sdconfig.txt" and, please, tell what is written into it...
nope, is no such file
Cant flash miris. Just stays at 0 %
managed to get phone back to hard spl thanks to crackwhores fantastic guide.
And at the moment im flashing miris newest rom..
Hope it works
Megawhopp said:
nope, is no such file
Click to expand...
Click to collapse
But what matters is that you have your baby back
Greetings.
Nope, its not..
Miris didnt work either, and despite the fact that im on hard spl phone is now with the blurry green screen.
Im beginning to get lost now..
What to do..
Please help
Hello,
Today I reflash my HTC Touch HD (the first official ROM from December 2008). First I made HardSPL unlock and then changed the ROM (http://forum.xda-developers.com/showthread.php?t=555137).
Since then, the words smart mobility on the first screen changes color after 10 seconds (maybe one color from RGB disappears). But if I press the buttom on the top twice, the color is ok. In this state the text and images are absolutely unreadable. In fact, I would not mind this flaw, but it makes another mistake. When I tap on something, so very often happens that stops working touch layer. I recognised that, because hardware buttom volume up/down works, display indicate loudness, but taping on screen doesn't work. Sometimes after a few tens of seconds it makes better, sometimes helps only software restart.
Before I recognised, that the problem is probably permanent, so I reflash ROM http://forum.xda-developers.com/showthread.php?t=542104 and then http://forum.xda-developers.com/showthread.php?t=547278
Then I tried to save my device by official ROM (_HTC Touch HD_MR_2009_RUU_BlackStone_HTC_Europe_1.56.401.0_Radio_52.62.25.34_1.13.25.24_Ship.exe), from this site: http://www.htc.com/europe/SupportDownload.aspx?p_id=179&cat=2&dl_id=533 and using this code HT849KD07000
Finally, I did SPL Stock.
But the problem is worse and dosn't work gsm module.
Once it shows this message: A problem has occurred with gwes.exe. and if I want to send to microsoft ...
Please hepl me. :-(
Thanks a lot.
I had the same problem
First flash HSPL 1.56 and your colours will still look funny
then flash a new ROM and your colours and everything else will be fine
welcome to the club
USPL the Best flashing tool
Si1m said:
Hello,
Today I reflash my HTC Touch HD (the first official ROM from December 2008). First I made HardSPL unlock and then changed the ROM (http://forum.xda-developers.com/showthread.php?t=555137).
Since then, the words smart mobility on the first screen changes color after 10 seconds (maybe one color from RGB disappears). But if I press the buttom on the top twice, the color is ok. In this state the text and images are absolutely unreadable. In fact, I would not mind this flaw, but it makes another mistake. When I tap on something, so very often happens that stops working touch layer. I recognised that, because hardware buttom volume up/down works, display indicate loudness, but taping on screen doesn't work. Sometimes after a few tens of seconds it makes better, sometimes helps only software restart.
Before I recognised, that the problem is probably permanent, so I reflash ROM http://forum.xda-developers.com/showthread.php?t=542104 and then http://forum.xda-developers.com/showthread.php?t=547278
Then I tried to save my device by official ROM (_HTC Touch HD_MR_2009_RUU_BlackStone_HTC_Europe_1.56.401.0_Radio_52.62.25.34_1.13.25.24_Ship.exe), from this site: http://www.htc.com/europe/SupportDownload.aspx?p_id=179&cat=2&dl_id=533 and using this code HT849KD07000
Finally, I did SPL Stock.
But the problem is worse and dosn't work gsm module.
Once it shows this message: A problem has occurred with gwes.exe. and if I want to send to microsoft ...
Please hepl me. :-(
Thanks a lot.
Click to expand...
Click to collapse
Lyptherion said:
First flash HSPL 1.56 and your colours will still look funny
then flash a new ROM and your colours and everything else will be fine
welcome to the club
Click to expand...
Click to collapse
i highly recommend you use USPL : I still yet have to see someone who had a problem after using USPL. This is even endorsed by Dutty Throy - Moderator ROM Cooker par excellence!
look here
http://forum.xda-developers.com/showthread.php?t=505377
and here
http://forum.xda-developers.com/showthread.php?t=462347
format your sd card using fat32 (full format) (if you are a frequent flasher I suggest you get a small capacity sd card – 1Gb - and devote this only for flashing)
rename the RUU_signed.nbh to BLACIMG.nbh and pair this with ROMUpdateUtility -(application file). copy this two files in you formatted sd card.
then using Digital Outcast's USPL GUI: look here
http://forum.xda-developers.com/showthread.php?t=508361
flash the ROM.
please let me know once you've done this succesfully, i wish you the best of luck!
Lyptherion said:
First flash HSPL 1.56 and your colours will still look funny
then flash a new ROM and your colours and everything else will be fine
welcome to the club
Click to expand...
Click to collapse
Thanks a lot, it works and finaly I din't have to reflash a ROM.
jigners said:
i highly recommend you use USPL : I still yet have to see someone who had a problem after using USPL. This is even endorsed by Dutty Throy - Moderator ROM Cooker par excellence!
look here
http://forum.xda-developers.com/showthread.php?t=505377
and here
http://forum.xda-developers.com/showthread.php?t=462347
format your sd card using fat32 (full format) (if you are a frequent flasher I suggest you get a small capacity sd card – 1Gb - and devote this only for flashing)
rename the RUU_signed.nbh to BLACIMG.nbh and pair this with ROMUpdateUtility -(application file). copy this two files in you formatted sd card.
then using Digital Outcast's USPL GUI: look here
http://forum.xda-developers.com/showthread.php?t=508361
flash the ROM.
please let me know once you've done this succesfully, i wish you the best of luck!
Click to expand...
Click to collapse
Sorry, but I am not sure if I twigged your post. (I dont speak english well) But never mind, the solution of Lyptherion works.
I believe what jigners was suggesting was for you to use USPL instead of HSPL. Both work just as good as each other, though USPL is temporary and would not void warranty should something happen to your device. HSPL is referred to as permanent as it stays on device unless you remove it so would void warranty if something happened to device while it was still on.
But I'm glad you have solved your issue.
Thread closed
Hi All,
I have used the search function - but ended up getting confused.
I have a Touch HD that I bought in January of this year (2009) from Mobiles.co.uk (Carphone Warehouse) and is on the O2 network (UK).
I have been using Dutty's ROMs (both 6.1 and 6.5) for months now - and have always used USPL when flashing, using the SD card method.
Over the past 3 days, my HD has been playing up.
When it started, I was using Dutty's R7. The radio was 1.14.something.something. The device was working perfectly, and I was really happy with the ROM and the way the phone was working. I had installed NO other applications with the exception of a different taskbar and obviously SDKCerts.cab
First of all, HTC Sense stopped working - it would cycle between "Loading HTC Sense" and "Tap here to launch HTC Sense"
Then, when rebooting the device, it just hung on the "Smart Mobility" screen. I left it in case it just needed a while to boot, but nothing.
I had no other option than to hard reset.
It worked OK for a few hours, but then HTC Sense started to crash again. So I flashed a new ROM - Lost in Asia or whatever it is called.
Same symptoms.
I flashed Dutty's R7 back and also the new 1.17 radio.
No joy.
The phone also hangs for ages on the Smart Mobility screen - perhaps a full minute where as before, it used to be no more than 15 seconds or so.
The following is displayed on the "Smart Mobility Screen"
1.17.25.09
52.69.25.37H
1.59.Dutty
The bootloader screen (before running USPL) shows the following:
BLAC100 32M
SPL-1.54.0000
MicroP-BlackStone (LED) V6
So the question I'm asking - is... Is my phone suffering some kind of hardware malfunction, or is this a known and fixable fault that I somehow have caused?
If the phone looks like it is malfunctioning, how would I go about returning it to stock so that the CPWH repair centre do not know it's had an unofficial ROM installed?
I'd like to add that whilst I'm very PC literate, I'm no programmer and a lot of the stuff here is alien to me hence my confusion - I just know how to flash a new ROM etc.
Thanks to anyone that takes the time to help me - I'd be really thankful to anyone that helps me sort this - be it tell me how to fix the device, or tells me to take it back!
Thanks in advance & Regards,
Chris.
Will D/L and flash Dutty's R0 Holy Grail ROM and see if that makes a difference...
If you've been using uspl than it will still be the stock spl and thus you could try to load the stock rom from htc.com specially designed for the touch hd(blackstone). I've read and heard from a lot of people that after flashing several roms and even hard resetting afterwards, some bits and pieces stay behind and flashing an original stock rom will undo this. I don't think it's a radio issue. And another big thing if you use dutty R7 that's a 1.56+ rom so you should have the right uspl olinex software to load these roms, if you used older software then problems with colouring and other things will appear.
a1gp said:
If you've been using uspl than it will still be the stock spl and thus you could try to load the stock rom from htc.com specially designed for the touch hd(blackstone). I've read and heard from a lot of people that after flashing several roms and even hard resetting afterwards, some bits and pieces stay behind and flashing an original stock rom will undo this. I don't think it's a radio issue. And another big thing if you use dutty R7 that's a 1.56+ rom so you should have the right uspl olinex software to load these roms, if you used older software then problems with colouring and other things will appear.
Click to expand...
Click to collapse
Thanks for the quick reply.
So is it perhaps better to revert to the original ROM before flashing a cooked ROM? I always Hard Reset twice after flashing as understand this helps.
OK - so the 1.56+ situation - I was under the impression that using the latest USPL (2.5) when flashing was OK? I have never had the colour problem... but perhaps if I'm flashing wrong then these problems could be to do with this?
Thanks again...
Chris
The Sense Manila has known bug that you need to press home to load it (sometimes).
For you case, I would suggest you to clean up your SD Card.
there may be several file that cause your system to freeze.
So, format your SD, hard reset.. and cross fingers.
Yes, It is better to revert to the original rom once in a while before flashing a new rom, if u used the latest uspl and the colours are ok, then you've done that right and it will probably be bits and pieces of old flashed roms floating around on the device.
Best to revert to stock rom and hard reset twice.
Afterwards flash the rom u want. If everything works again. U could hspl instead of uspl, hspl is more stable if u ask me. And you can go back to stock spl if you have waranty issues. there's a tut on that to in the rom section.
mcdull said:
The Sense Manila has known bug that you need to press home to load it (sometimes).
For you case, I would suggest you to clean up your SD Card.
there may be several file that cause your system to freeze.
So, format your SD, hard reset.. and cross fingers.
Click to expand...
Click to collapse
I forgot to mention - that was one of the things I did. Previously, I had loads of email folders from all the ROM installs.
Now I have a folder containing the useful CAB files that I need, and the ROM image file. Thats it.
It's only a 1gb card as my 8gb card gave up the ghost.
Thanks for the suggestion though and my apologies for not mentioning this in the initial post.
From reading the Dummies guide, am I right in thinking that in order to use a 1.55+ ROM (such as Dutty's Holy Grail R0) I only need to run USPL and then flash (as opposed to flash a newer SPL) as my stock SPL is already 1.54?
a1gp said:
Yes, It is better to revert to the original rom once in a while before flashing a new rom, if u used the latest uspl and the colours are ok, then you've done that right and it will probably be bits and pieces of old flashed roms floating around on the device.
Best to revert to stock rom and hard reset twice.
Afterwards flash the rom u want. If everything works again. U could hspl instead of uspl, hspl is more stable if u ask me. And you can go back to stock spl if you have waranty issues. there's a tut on that to in the rom section.
Click to expand...
Click to collapse
Thanks for this - I didnt realise the device would retain bits and bobs, and you may well be right in that things are getting corrupted in there!
Which is the best stock ROM to flash - is there a link to one? I looked on the Wiki and there seem to be loads... which will work on a UK T8282?!
Thanks again!
Chris
constablechris said:
I forgot to mention - that was one of the things I did. Previously, I had loads of email folders from all the ROM installs.
Now I have a folder containing the useful CAB files that I need, and the ROM image file. Thats it.
It's only a 1gb card as my 8gb card gave up the ghost.
Thanks for the suggestion though and my apologies for not mentioning this in the initial post.
From reading the Dummies guide, am I right in thinking that in order to use a 1.55+ ROM (such as Dutty's Holy Grail R0) I only need to run USPL and then flash (as opposed to flash a newer SPL) as my stock SPL is already 1.54?
Click to expand...
Click to collapse
what do you mean hang for age?
1 minute is nothing if it turns out boot up.
There are chances that the nand flash needs to refresh and wasted some times. But it won't be forever.
constablechris said:
Thanks for this - I didnt realise the device would retain bits and bobs, and you may well be right in that things are getting corrupted in there!
Which is the best stock ROM to flash - is there a link to one? I looked on the Wiki and there seem to be loads... which will work on a UK T8282?!
Thanks again!
Chris
Click to expand...
Click to collapse
there's an original rom on htc.com for blackstone just use that one.
hope it will turn out right for you
I thought I'm the only one who had this problem. Last Sunday my blackstone started to freeze on the smart mobility screen too. I flash 3 different roms because I thought its an rom issue with no luck. On Monday it even managed to hardreset itself after I waited for about 15 min in the smart mobility screen.
After that I flashed a stock rom and it seem to be fine by now.
But now I will flash a custom again, the stock one is so 6.1
Ok these two are related and are not...
I hadn't seen this elsewhere even with a search but to flash without having to use activesync simply power down your phone (completely off) either by holding the power button for about 3 seconds or by a program or remove your battery and count to 10...
Then hold volume down and power on the device then wait until the device gives you the bootloader screen (or the 3 colored bars)...
At this point the bootloader will say serial in the white portion... hook up a USB and connect it to the computer... windows 7 beeps at you when it accepts it... and it should now read "usb"... flash away!
1. power down
2. wait for shutdown
3. hold volume down
4. power on
5. wait for 3 color screen and serial
6. release
7. connect usb to both computer and phone.
8. wait for serial to change to usb
9. flash away!
With that said I like clearing my memory with Task29 which gave me this idea... as I hate doing activesync flashing... repeat... however I found that activesync does not resolve driver issues...
This is why it is advised to do task29 and your stock rom... then flashing your cooked rom... some things that task29 could not clear up for me that stock could....
I had a new voicemail message on every reset hard or soft... on 3 roms... this was a problem as there was no voicemail... but there was the icon?
Answer: flashed stock rom... this removed it where several task29's could not
Internet could not connect... Answer: flashed stock rom again... task29 and hard reset could not...
I know this takes a long time... flashing stock, task 29, then your Rom, and no the 2.07's do not count as Stock... and they do not seem to clear up anything... as the voicemail glitch was on WWE 2.07 EU and the internet was on a WWE 2.07 ASIA... I flashed, reflashed, task29'd, and hard reset, nothin'!
My thought is that first you restore the drivers/hardware let the phone reboot clear any problems... clear the rom with task29 then have a fairly good place to set your new Rom with good drivers/hardware and blank slate!
Hope this is useful for a lot of problems.
Going into bootloader mode is covered in the sticky thread about flashing ROMs. You can also flash from memory card too.
task29 completely wipes out the ROM area. I'm struggling to understand how flashing a stock ROM after a task29, and then your cooked ROM, is better. In fact it seems worse to me, i.e. you may have some stuff from the stock ROM left around when you flash the cooked ROM.
You didn't say that you need Hard SPL on your Rhodium to do this... I reckon a lot of noobs reading this would brick their devices after reading this...
ultramag69 said:
You didn't say that you need Hard SPL on your Rhodium to do this... I reckon a lot of noobs reading this would brick their devices after reading this...
Click to expand...
Click to collapse
I don't think they'd be at risk of bricking. Task29 needs HardSPL and will refuse to work otherwise. And a ROM flash will just hang without HardSPL.
I don't see a reason to flash a stock rom, at all. Although, I do appreciate your input about task29 to stock rom then to cooked rom. It just doesn't make sense to me, because I have never had issue using task29 and then just flashing to the next cooked rom.
Like I said above guys... I have ISSUES TASK29 COULD NOT RESOLVE ALONE... thus flashing the STOCK then Task29... NOT Task29 then Stock that would seem to be pointless -eh? So I am sorry if I were not clear enough in the post.
As far as the sticky, I had read through it... must of missed it but then again I was skimming for stuff I did not already know from my days of owning a T-Mo Dash (2G)... sorry but I did not remember seeing these instructions on how to get around activesync all the time... I mean let's face it, it is time consuming.
Also I let the stock run for a little too... just a few minutes and a reset or two...
ive done a lot of research and still cant find a solution. im sort of a newb, heres the problem my wifes TP2 when she turns it off and turns it back on the phone gets stuck on bootloadr screen, tried to hard reset but wont do anything. but when i plug it with usb to my laptop if i soft reset it will boot up.I read that alot of people had the same problem and just had to install a coocked rom, well i did i installed energys rom but it still had the same issue. Now its back to stock rom. any info on how to fix this is appreciated and thnx in advance.
Get it replaced under warranty
if you were able to flash a cooked rom, you must have installed hard-spl.
when did you do this, after the problem appeared to be able to flash the energy rom, or before? maybe this could be the problem...
http://forum.xda-developers.com/showthread.php?t=606078
here is a thread on the subject already.
Huthus said:
if you were able to flash a cooked rom, you must have installed hard-spl.
when did you do this, after the problem appeared to be able to flash the energy rom, or before? maybe this could be the problem...
Click to expand...
Click to collapse
well the first time her phone did it i googled the problem and it brought me here, a thread that said stuck at bootloader screen and their solution was flashin a cooked rom. well it got the phone to boot after i did that but every time if she turns it off and back on it gets sutck at the tri color screen. i installed hard spl when i was flashin rom.
here is a thread on the subject already.[/QUOTE]yea been at that thread also,but my problem is that when i turn the phone off and when i turn it back on it wont boot up it just gets stuck there, like i stated above i already flashed hard spl and flashed a energy rom but it still does the same thing. i flashed the phone back to the original rom but is still gets stuck, the phone works as long as she dont turn it off but after awhile her ram goes up to like 80 so i have to turn it off, and to turn it back on i have to use my laptop. and thanx for the help guys i really appreciate it. and phone dont have warranty i bought it on craigslist.
Since it's going to the tri-color bootloader screen, seeing as normally to get to that screen you would hold volume down on boot, have you checked inside the back of the case to make sure there isn't dirt/debris jamming the volume down button? If the volume adjusts normally once you do get it booted, that may not be it, or maybe it's just a short in the key.
Also, both the stock ROM and energy ROMs are bad about eating ram, and need to be rebooted regularly. Maybe try one of the ROMs that doesn't, like a Jackos rom, which you can leave running for days without a reset. Might not solve your problem, but might at least take some of the bother out of it.
FL5 said:
Since it's going to the tri-color bootloader screen, seeing as normally to get to that screen you would hold volume down on boot, have you checked inside the back of the case to make sure there isn't dirt/debris jamming the volume down button? If the volume adjusts normally once you do get it booted, that may not be it, or maybe it's just a short in the key.
Also, both the stock ROM and energy ROMs are bad about eating ram, and need to be rebooted regularly. Maybe try one of the ROMs that doesn't, like a Jackos rom, which you can leave running for days without a reset. Might not solve your problem, but might at least take some of the bother out of it.
Click to expand...
Click to collapse
I take it you haven't used the latest NRG ROM. Mine runs for several days.
stevedebi said:
I take it you haven't used the latest NRG ROM. Mine runs for several days.
Click to expand...
Click to collapse
You've got me, there. The last energy rom I tried was a little bit ago, and was a Maxsense version at that. Even still, it soundly failed my Opera Mobile 10 test on a clean flash off of a fresh boot (it would autokill OM 10 to free up ram without any other apps open). Any rom that does that goes straight into the bin as far as I'm concerned.
I have been meaning to drop one of the more recent builds on to see if that was just a bad experience. Maybe try one of the titanium versions, just to make sure I'm giving it a fair shake. Either way, this has now gotten at least a bit off topic. =P
stevedebi said:
I take it you haven't used the latest NRG ROM. Mine runs for several days.
Click to expand...
Click to collapse
yea i have the sep 18 nrg rom on mine wich now runs very good. well after a couple reboots with the phone plugged to my laptop, i unplluged it and tried a soft reset and thank god it booted normal, i then powered the phone off and turnd it back on and it worked. dont know what the problem was but i appreciate everyones help.
There is different things that you can do to try and resolve your problem. Start by finding a rom that you would like to install on your phone and save the file to your SD Card. FL5 Mentioned Jacko's rom and I swear by it as well. I run the showlite version modified to my liking and still have on average about 80 mbs of ram open.
2nd thing to do would be a Task 29 which will pretty much formats your phone. This is important to do because if there is any "debris' left over from any of the roms you have installed, this will take care of that. "Debris" at times cause issues that you cannot pinpoint and interfere with the rom that is currently installed. It is also important that you do this step second because once you do a Task 29 you will not be able to flash through USB. At least, I have not been able to do so. I flash from my SD Card. You can get Task 29 here-->http://forum.xda-developers.com/showthread.php?t=649191
Once you do that, flash your rom from your SD Card by following the directions here-->http://forum.xda-developers.com/showthread.php?t=550540
Hopefully this fixes your problem. If it doesn't, you don't have to soft reset to free up ram. I use software called "cleanram" and usually run it on level 3 which means that it thoroughly finds processes taking up ram and reclaims it. You can also schedule a daily, weekly, hourly clean under the settings menu. You can find that here-->http://forum.xda-developers.com/showthread.php?t=514333
Best of luck.
Oooooooooooo yeah! Task 29 is absolute magic. Completely wipes your NAND before a flash to remove the chance of old ghost files from past ROMs jacking up your system. If you've followed any of the flashing tutorials on the board then you've definitely been doing this step, and thus this shouldn't have been your problem. Not everyone has problems if they skip it, but all sorts of seeminly otherwise random problems can pop up otherwise.
marduk79 said:
2nd thing to do would be a Task 29 which will pretty much formats your phone. This is important to do because if there is any "debris' left over from any of the roms you have installed, this will take care of that. "Debris" at times cause issues that you cannot pinpoint and interfere with the rom that is currently installed. It is also important that you do this step second because once you do a Task 29 you will not be able to flash through USB. At least, I have not been able to do so.
Click to expand...
Click to collapse
Eh ? I don't know what's going wrong for you, but that's completely untrue. After running task29, you need to unplug the phone from the PC, put the phone into the bootloader (e.g. press reset while holding down the Volume Down button), wait for it to come up and say "Serial" at the bottom, then plug it back in and it should say "USB". Then you can flash via USB (which is safer than flashing from SD card, since it does more checking).
FL5 said:
You've got me, there. The last energy rom I tried was a little bit ago, and was a Maxsense version at that. Even still, it soundly failed my Opera Mobile 10 test on a clean flash off of a fresh boot (it would autokill OM 10 to free up ram without any other apps open). Any rom that does that goes straight into the bin as far as I'm concerned.
I have been meaning to drop one of the more recent builds on to see if that was just a bad experience. Maybe try one of the titanium versions, just to make sure I'm giving it a fair shake. Either way, this has now gotten at least a bit off topic. =P
Click to expand...
Click to collapse
The 20 Sep ROMs have the option of using quick menu. With that option, even with Sense 2.5 and CHT (a RAM hog), I have 88 Mb available on a normal basis. I don't use Opera 10 (also a RAM hog), but I think it would work with the new ROM.
You have to manually select the Quickmenu option.
well the problem with her phone is fixed. but now my hardware keys stay on dim but they stay on, im gonna try doin task 29 and reflashing a rom see if that takes care of my issue.
Well just for future references, I had all of the above problems and tried all of them. Issue did not go away until I did the following steps..:
Run Task 29
Flash new ROM (Issue still exist)
Flash New Radio (Issue still exist)
Reflashed Hard-SPL (This somehow fixed the issue....)
starmena said:
Well just for future references, I had all of the above problems and tried all of them. Issue did not go away until I did the following steps..:
Run Task 29
Flash new ROM (Issue still exist)
Flash New Radio (Issue still exist)
Reflashed Hard-SPL (This somehow fixed the issue....)
Click to expand...
Click to collapse
well i just did all of it and the freakin keys wont go off, n e one have any other suggestions? and thanks to every one for their help.