Hi all
I recently try to update my Opal with the official version from HTC homepage, but something went wrong I cannot really say what.
Now the Opal is stocked on the splited RGB screen and does not react on any thing I do. I already try soft and hard reset but they did not helped me the Opal always return to the split RGB screen.
Really hope to see some solution soon
Alex
bsash said:
Hi all
I recently try to update my Opal with the official version from HTC homepage, but something went wrong I cannot really say what.
Now the Opal is stocked on the splited RGB screen and does not react on any thing I do. I already try soft and hard reset but they did not helped me the Opal always return to the split RGB screen.
Really hope to see some solution soon
Alex
Click to expand...
Click to collapse
i think u should update a rom cook. I use a rom 6.1 v5 of PhamQuang, it is very good.
This link u can find this forum
bsash said:
Hi all
I recently try to update my Opal with the official version from HTC homepage, but something went wrong I cannot really say what.
Now the Opal is stocked on the splited RGB screen and does not react on any thing I do. I already try soft and hard reset but they did not helped me the Opal always return to the split RGB screen.
Really hope to see some solution soon
Alex
Click to expand...
Click to collapse
i think u should update a rom cook. I use a rom 6.1 v5 of PhamQuang, it is very good.
This link u can find this forum
have download and installed the new Rom which is 1.54, unfortunately that the screen becoming green which looks like with out color and the devise becoming so slow !!
any advice please !
How i can get back to the original ROM !
My phone from Orange which is locked and when i have installed the new ROM the phone was unlocked !! Is this what make it looks like that.
Many thanks
astbok said:
have download and installed the new Rom which is 1.54, unfortunately that the screen becoming green which looks like with out color and the devise becoming so slow !!
any advice please !
How i can get back to the original ROM !
My phone from Orange which is locked and when i have installed the new ROM the phone was unlocked !! Is this what make it looks like that.
Many thanks
Click to expand...
Click to collapse
Reason why your screen is green is most likely down to the fact that you flashed to a 1.54 rom while using HSPL instead of USPL
Try reading these 2 guides:
http://wiki.xda-developers.com/index.php?pagename=HTC_Blackstone_Rom156
http://forum.xda-developers.com/showthread.php?t=505377
many thanks
thatnks alot for this info
Hi.
Since a few hours my HTC is showing the screen in I think 16 colors.
I already tried to flash new ROMs but nothing change.
Someone any idea.
THx
Pimpmastah said:
Hi.
Since a few hours my HTC is showing the screen in I think 16 colors.
I already tried to flash new ROMs but nothing change.
Someone any idea.
THx
Click to expand...
Click to collapse
if my suspicions are correct, you can go here --> HD Dummies Flashing Guide to fix your problem. it pays to read about what you're doing before you do it. .
Did you put HSPL 1.56 on your phone? if not.. you should
Sounds like a HardSPL problem.
I had this problem when I upgraded to HardSPL v1.54, but the ROM was an older ROM. After upgrading to a newer ROM, this problem disappeared. I wasn't alarmed because this problem was expected, as written in HardSPL guide.
Maybe you should try the same...
Sounds like a SPL problem that gets reported every day. Please try searching before creating new thread.
Yesterday I've HSPL'd my leo.
Then I flashed the Dutty0.3v and thought everything was fine. Until this morning the device was unlocked with S2U2 and hung afterwards (not able to show manila page). After a softreset, device hung at white bootscreen (three red version lines bottom). Several softreset later, it actually lost all its settings, windows welcome center was welcoming me. So it did a hardreset.
Then I flashed another rom, the freyberryROM.V5.3. After flashing, I always hardreset the phone of course.
After two hours configuring and installing, all of a sudden some application weren't starting anymore, so I thought let's do a softreset, to see, if it fixes things. The same happened, device hung a bootscreen. After softreset, a hardreset occured again....
First I wanted to put the blame on the HSPL, but I think it was coincidence. But thinking over and over about my procedure and reading the dutty rom's thread, I think this has to do with S2U2. Maybe some of you experienced this as well, and we can put together what might be the culprit.
Details:
Using S2U2 v2.24 (video rawbuffer mode) - imported settings from reg-file.
Using T2Pro-Theme on SD-Card
Manila and every other HTC/WM setting concerning language set to German.
Hooked on Exchange2010 - Pushmail activated.
Somebody in Dutty's thread said, that those hard-resets get quite common with the newer ROMs, and it would help to flash a stock rom before, can somebody comment on this?
Thanks for any input!
ROM
I have had the same too with my former Blackstone, as I flashed it with T2M PDViet, I thought it is a virus, however I solved it by downloading a new version and installed it all over again, good luck
Donald24 said:
Yesterday I've HSPL'd my leo.
Somebody in Dutty's thread said, that those hard-resets get quite common with the newer ROMs, and it would help to flash a stock rom before, can somebody comment on this?
Thanks for any input!
Click to expand...
Click to collapse
We had to do this on all the WM6.5 cooked roms for Kaiser, not heard of it being required for HD2 yet, why not post this in the thread for the ROM you are using?
Before flashing another custom ROM, flash an official stock ROM (1.42/1.48).
I encountered these issues on my TytnII and this weekend, I got the same problem on the HD2. Flahing 1.48 WWE before flashing custom ROM solved the issue for me.
Also: flashing 2.xx ROMs using 1.42xxx SPL may result in unexpected issues.
tomasz said:
Before flashing another custom ROM, flash an official stock ROM (1.42/1.48).
I encountered these issues on my TytnII and this weekend, I got the same problem on the HD2. Flahing 1.48 WWE before flashing custom ROM solved the issue for me.
Also: flashing 2.xx ROMs using 1.42xxx SPL may result in unexpected issues.
Click to expand...
Click to collapse
I've had this on my TytnII as well, but I never heard it for the HD2. So Custom to Custom ROM flashing is a NO GO?
?? Is there any other SPL? SSPL and HSPL are both 1.42 based....
In the diamond and other devices like tynt you could fix this with MTTY but dont know if it will work with the hd2
I thought MTTY was for recovering a device after a bad/interrupted flash??
Can you really use it to fix the non-boot situation and recover your installation?
So, when talking about stock-rom flashing is SoftSPL-flashing enough, or is a full HSPL- or even CID-ID-corresponding flash (incl. radio-rom) necessary?
Can somebody shed some technical background around this issue? I don't understand that there are mysterious areas, which don't get flashed and updated when flashing from custom to custom rom. There is no logic that this works for ONE flash ONLY.
Viewing this post : http://forum.xda-developers.com/showpost.php?p=4798017&postcount=1 , I think a task 32 in MTTY after flash must be a solution (official RUU seem to make it). But never tried.
xvx45 said:
Viewing this post : http://forum.xda-developers.com/showpost.php?p=4798017&postcount=1 , I think a task 32 in MTTY after flash must be a solution (official RUU seem to make it). But never tried.
Click to expand...
Click to collapse
Nope, officially hardresetting a device is recommended after flashing custom rom, I even ran into these issues without hard-resetting after flash (actually forgot it) , so leaving it intentionally out won't fix it.
Are you using CustomRUU to flash your device. I'm sure I read somewhere that flashing from the MicroSD card can cause problems but can't remember what they were now....just a thought
Donald24 said:
Nope, officially hardresetting a device is recommended after flashing custom rom, I even ran into these issues without hard-resetting after flash (actually forgot it) , so leaving it intentionally out won't fix it.
Click to expand...
Click to collapse
Ok, so, we have to found the "Format BINFS" task for HD2 bootloader. It's the command "task 29" on the Diamond (1) and the HD (BlackStone).
So for my experience on the Diamond, we have to do a task 29 before to flash to have a fully cleaned storage before write on this.
So I'ven't found any documentation on this for the HD2, I still investigate with IDA and original RUU, but it's my first attempt to decompile a soft...and it's not really easy to understand.
So we need people with two phone and able to practice JTAG to test a task 29 on Leo bootloader without risk to brick it...and it's not my case.
ps : sorry for my poor English.
crazyman1 said:
Are you using CustomRUU to flash your device. I'm sure I read somewhere that flashing from the MicroSD card can cause problems but can't remember what they were now....just a thought
Click to expand...
Click to collapse
It's not the flashing, me thinks. I experienced the issues only after flashing from custom TO custom rom. So I just think, it's like to old KAISER's times:
Always flash stock rom before!
Has anyone else noticed this?
I've never flashed a stock rom between custom roms and never had any lock up problems. I always use sspl or customRUU. Just thinking it might be the way you're flashing as I'm sure I read somewhere on the forum that there were problems with flashing from the MicroSD card.
xvx45 said:
Ok, so, we have to found the "Format BINFS" task for HD2 bootloader. It's the command "task 29" on the Diamond (1) and the HD (BlackStone).
So for my experience on the Diamond, we have to do a task 29 before to flash to have a fully cleaned storage before write on this.
So I'ven't found any documentation on this for the HD2, I still investigate with IDA and original RUU, but it's my first attempt to decompile a soft...and it's not really easy to understand.
So we need people with two phone and able to practice JTAG to test a task 29 on Leo bootloader without risk to brick it...and it's not my case.
ps : sorry for my poor English.
Click to expand...
Click to collapse
I am absolute unfamiliar with this tasks you do with the RUU....
So task 29 did solve any "leftovers" and freaky behaviour on a diamond?
Donald24 said:
I am absolute unfamiliar with this tasks you do with the RUU....
So task 29 did solve any "leftovers" and freaky behaviour on a diamond?
Click to expand...
Click to collapse
yup, diamond, hd, tynt and i think all htc devices... but nobody have tryed with the hd2... be carefull if you try but i think there shouldnt be any problem.. anyways at your risk
makeveral said:
yup, diamond, hd, tynt and i think all htc devices... but nobody have tryed with the hd2... be carefull if you try but i think there shouldnt be any problem.. anyways at your risk
Click to expand...
Click to collapse
hey - we're getting closer. thinking about a sub-forum about flashing techniques, they will surely get device-dependant at some point.
if a call of task 29 would not make any problems, should it not be made and considered as standard for custom flashing?
did ever anybody brick his device with it? there must be something, causing that fear...
nobody on xda normally shows this respect for trying out undocumented functions
Donald24 said:
hey - we're getting closer.
if a call of task 29 would not make any problems, should it not be made and considered as standard for custom flashing?
did ever anybody brick his device with it? there must be something, causing that respect
nobody on xda normally shows this respect for trying out undocumented functions
Click to expand...
Click to collapse
ya some people have bricked his device because of this... but well it can usually get fixed! problem was that they used mtty without having a hardspl and then they couldnt flash any rom... but if you have hardspl then no problem because you can flash from bootloader!
And if you dont have hardspl then you should also be able to flash HTc official rom(or the official rom that came with your device)
Anyways i wouldnt be first one to try it on my hd2 xD (only if i had problems)
makeveral said:
Anyways i wouldnt be first one to try it on my hd2 xD (only if i had problems)
Click to expand...
Click to collapse
Why hesitating? I'd love to see a "call task 29" as a menu item in your BSB tool I woke up this morning, and I felt for yelling "Task 29" to my girlfriend. No, to be honest, I didn't, I said "69" and enjoyed the morning.
I am going to try this method out and report back, but as it seems, it will be seen as a hack, that doesn't fit for everybody. But I would prefer this against always preloading a stock rom, if it would do the job.
Thanks for putting light on this!
Donald24 said:
Somebody in Dutty's thread said, that those hard-resets get quite common with the newer ROMs, and it would help to flash a stock rom before, can somebody comment on this?
Thanks for any input!
Click to expand...
Click to collapse
Hi,
this is correct, you can stop this happening by flashing a OFFICIAL rom before your cooked rom.
Although i have just posted a thread on MTTY, which is the EXACT answer to all problems in this thread.
THREAD HERE - (It is Under Construction so please dont use until the big red warning has gone, you cant miss it!!)
MG
I was having the same exact problems with softspl and hardspl and with any custom rom. My cousin has the same issues too. I flashed back to stock 1.61 and dont have hardresets anymore.
Please, i bought the hd2 so i can run Android on, I have been looking for a long time searching on XDA, and all over the net for a solution to my problem " when ever i run android it starts, i customize and download stuff, but when ever i just leave it on standby mode for like 2 or 3 mins, it gets stuck when i try opening the buttons just light up and i have a black screen.... please help me
some people get pissed off repeated threads, I'm sorry i've been looking for a really long time never reached a solution
HTC HD2 TMOUSA 1024
WinMob 3.14
Android MDJ 4.3
HellocK said:
Please, i bought the hd2 so i can run Android on, I have been looking for a long time searching on XDA, and all over the net for a solution to my problem " when ever i run android it starts, i customize and download stuff, but when ever i just leave it on standby mode for like 2 or 3 mins, it gets stuck when i try opening the buttons just light up and i have a black screen.... please help me
some people get pissed off repeated threads, I'm sorry i've been looking for a really long time never reached a solution
HTC HD2 TMOUSA 1024
WinMob 3.14
Android MDJ 4.3
Click to expand...
Click to collapse
sounds like a radio issue to me, have you tried other ROMs, what is your radio version?
Try flashing 2.12.50 or 2.15.50 and you should be fine.
tried the Energy Rom, no good use.. flashing the radio now.... thxx for the quick reply
sure thing, let me know how it goes.
Also, when flashing a new winmo ROM, are you doing a task29?
I have had issues when flashing new ROMs over old ones without doing task29 first, it seems to help a lot.
orangekid said:
sure thing, let me know how it goes.
Also, when flashing a new winmo ROM, are you doing a task29?
I have had issues when flashing new ROMs over old ones without doing task29 first, it seems to help a lot.
Click to expand...
Click to collapse
i got the solution .. u disable the autorotation and set the calibration ... as well i did the radio you told me about ... so i guess one of them did it
thanks alot man