Develop Bugs

[Q] Red exclamation mark after bungled update

I'm an idiot, I had a rooted HTC Sense (2.2) Rom installed and tried to do the over the air update last night, now I can get into recovery but I get the red triangle with an exclamation mark in it. I have, no really, searched and tried a few fixes but I'm not getting anywhere.
HTC Desire
BRAVO PVT1 SHIP S-ON
HBOOT-0.93.0001
I tried the modaco solution but skipped the first two steps and started at 3;
Any help would be greatly appreciated.

Yes you have indeed acted stupid...
But don't worry. The red triangle with the exclamation is just the standard HTC recovery screen. This is because the OTA update updates bootloader and recovery to the non modified ones, so you are basically back to stock.
If you can boot the system all you need to do is to use unrevoked again. If you cannot boot into system, you need to use a ruu first.

Thanks very much for your reply, I did backup first within recovery so I guess once I'm rooted again I can restore?

Any pointers? I can't boot and when I rooted last time I used unrevoked3, could you point me to a thread which could help please?

you just have to look for an ruu.exe wich fits to your phone....

Okay, I'm being less of a 'tard I think and I'm trying to make a gold card, but ADB lists my phone as offline (when on the red triangle screen) and wont let me invoke the shell. Am I still missing the obvious?

There's many threads on here.
Search for '2.29.405.5'.
I'm assuming that's the rom you're on.
Sent from my HTC Desire using Tapatalk

That hasn't helped me, I've just got a list of nice custom roms which I can't have until my phone boots

http://forum.xda-developers.com/showthread.php?t=869048
There you go. Download the file, plug in your phone while booted in fastboot and run the .exe file.

3 minutes is not long enough to justify a thorough search!!!

Totally agreed but bear with him. When people believe their device is "bricked" or f***** they tend to panic

Thank you very much

Sorry, you're right I should have tried harder but am getting in the neck for not having a working phone - thanks so much for your help, I really do appreciate it.

Sorry but I'm still stuck, the RUU won't work in Windows 7 which my PC runs and when I use Parallels on my Mac (the only XP machine I have) it won't detect the phone - is there a way I can do this under OSX?

you need to put your phone into fastboot - power and back button, then connect it to your PC.
turn off any antivirus/firewalls as these can interfere with the RUU.
also, install HTC sync if it isnt already
HTH

also, can you confirm which ROM you were on before the OTA?
and which RUU you are using?

Thanks, forgot about HTC Sync so installing it now - I was on this ROM;
http://forum.xda-developers.com/showthread.php?t=789058
and using the RUU mortenmhp linked to.

I was missing HTCSync, updating now in Parallels, thanks again for the help - feel like a retard this evening.

ok, do you know what the original rom was that was on your phone when new?
sorry for so many questions, but it should help sort it out.

ignore my last post then
glad its getting sorted....

[Q] OMG! Accidentally Formatted system data!

Alright. For starters, xda has been VERY VERY helpful to me over the past few months and I thank everyone who has ever contributed to a question or a discussion I have read. That being said, this is my first post. I watched the newb video, read many forums (both xda and others), google searched, read some more threads, kept reading threads, tried some methods described in some threads, bookmarked some interesting threads for if my phone ever works again, and read some more threads.
I am not saying the answer is not already out there, I am saying I have reached my resourcefulness cap.
Anyway, to the root of the problem: I'm not entirely new to rooting, and am comfortable using recovery and hboot to flash roms. I also had a nandroid backup! for SOME SILLY reason, while in my clockworkmod recovery this morning (maybe slightly due to being half asleep which is why I now recommend being fully awake before entering hboot or recovery or rom manager....etc) I formatted the system on my phone. I THINK.
My phone will now load up to display the bootloader, and go into recovery mode, and flash roms, but when I flash a rom, nothing changes. If I boot my phone up, it will show a notification bar at the top like usual, a stock wallpaper, and that is IT! it will show a message notification and missed call icon since I have them, but the touch screen will not work. The rosie buttons at the bottom do not show up (i.e. phone button or all aps button) no apps appear, no clocks except for in the notification bar... hardkeys have no effect (home button search button menu or back) and volume keys will not work. The lock button will only lock and unlock the screen, not power off or reboot or anything. If plugged in at this point, it is charger only.
So, I can take the micro sd card out and put files on it from my PC via a microsd-usb converter thing...
I have tried putting new roms on the sd and flashing them from recovery, no effect. Tried the RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe program, it always says that my phone has below 30% battery and will not continue (this is not the case as I have two batteries both have been fully charged because the phone will still charge them...)
And I have tried putting PC36IMG.zip files on my sd card to no avail.
I am thinking that the system was wiped because it seems like there is no boot image on the phones internal memory itself. I am currently looking for a way to place a boot image on the sd card to possibly flash it or some sort of update.zip so that my bootloader will ask me to update upon reading it.
Sorry for the long post, and ask any questions I will answer as best I can.
I am posting preemptively to the boot image adventure so that if it does not work, maybe I can have some help finding a solution by then.
I was going to take my evo to the sprint store since it is under warranty but if they go into recovery they will see clockworkmod recovery.
Thanks to all for any form of guidance!
I did just notice in my Bootloader menu (HBOOT-2.10.0001) that it says Supersonice evt2-3 **** S-ON
I don't know how because I thought it was a requirement that it says S-OFF to be rooted and flash roms, but I have definitely flashed roms before and gained su access to applications and such. BUT since it says S-ON would it then be covered by the warranty if it is not rooted?
Thanks again.

I you want to flash a boot image, you can take the boot.img from an RUU for the firmware you are, place it in your adb tools folder, then flash it using the commands:
fastboot flash boot boot.img
fastboot reboot

I'm not sure how to identify what firmware I am. Unless your talking about the Hboot version? and also, I can't place anything in any folder except onto my sd card. I have no access other than that to the phone. On the sd card there are no files except for what I put on there.
...aaand not to mention I don't know what adb is exactly...

Does your phone still go to clockwork when you go to recovery?

Am going to try it right now, but will that work if I cannot tell my phone to allow usb debugging? i remember something about unrevoked needing that to root the phone in the first place. will update as soon as I try it. May not have time right now as I have to leave in about 15 mins. If no reply by 9:45, then I will be back online tomorrow morning. and thanks!

Timeconsumer10 said:
Am going to try it right now, but will that work if I cannot tell my phone to allow usb debugging? i remember something about unrevoked needing that to root the phone in the first place. will update as soon as I try it. May not have time right now as I have to leave in about 15 mins. If no reply by 9:45, then I will be back online tomorrow morning. and thanks!
Click to expand...
Click to collapse
Welcome, but yes, you do need to have had usb debugging enabled, so we'll see how that goes.

SUPER THANKS! S-OFF tool worked perfectly just flashed a rom and now so far so good. Will post tomorrow to let you know if everything works well. So much appreciated =) I would thanks a million times if i could don't know what to do without my evo.

Timeconsumer10 said:
SUPER THANKS! S-OFF tool worked perfectly just flashed a rom and now so far so good. Will post tomorrow to let you know if everything works well. So much appreciated =) I would thanks a million times if i could don't know what to do without my evo.
Click to expand...
Click to collapse
Lol, it'd take you 200,000 days since you can only thank 5 times a day Though glad you're rooted now.

shortydoggg said:
Does your phone still go to clockwork when you go to recovery?
Click to expand...
Click to collapse
Yes it still goes to clockwork because its rooted.. now my screen legitimately does not work in certain areas of the screen (not responding to touch) so I'm going to try and get it stock stock stock unrooted and go for warranty replacement. Any ideas please let me know. Currently trying RUU Supersonic...

So, I got an ERROR [110] message from the RUU package its a file open error... :/ now i dont know what is up. Says I need a complete RUU package. Looking for another one or another option now.
If i boot phone normally now it just goes to a black screen with "htc" in the middle and "!" in a triangle in all four corners. Can't do anything from that screen.
If I boot into bootloader once where it says SHIP S-OFF at the top and instead of recovery and all those options it just says RUU but you cant do anything there... :/ I now, however cannot even get to the bootloader screen.
Could they tell it is rooted?
Maybe I could say I finally decided to do sprints OTA update that I've been denying for a while and this is the result.
Anyone agree disagree?

COCLUSION!
So. Since it has just the HTC logo and four error icons one in each corner... I took it into a sprint repair store. It would not boot into bootloader as a hard reset, so the guys at the store were stumped. They had actually never seen this before =). They asked me if I rooted it and all so I just played dumb. I told em I didn't know what that really was. They kinna explained it and I told em I didn't even have a computer (not a lie actually I sold mine and now use my dads or gfs lol). The logo on the screen was an oooold htc logo from like hero or so. So they just put it in the system as a wont even turn on type of thing and gave me a new phone since I was under warranty =) gonna see if I can live without root juuust for a little bit because work and school are gonna keep me busy for a while. I am certain to return though!
Can't wait to see what the devs can do by then!
Thanks to all for the help!

[Q] **BRICKED**

HI. Okay, so a couple weeks ago, I received a notification from HTC that said there was a new update available. Since I had S-Off and an unlocked bootloader (don't ask why, I just ****ing do.) I could not update, as it would give me errors, and cancel the update. So, earlier today I was fed-up with how slow my phone was being, and I wanted to fix it by updating. So I scoured XDA and found a thread about how to update by updating the HBoot or whatever. I followed those instructions and everything was fine, until I got to the initial part of installing the new **** through RUU. It was running fine, and then all of a sudden, the phone disconnected and ****ed the installation up. My battery was fully charged, and still has a charge as I am writing this. I digress. Whenever I would try to power my phone on, I would feel THREE (3) vibrations, and nothing would happen after. I tried booting into the stock recovery (fastboot, recovery, etc) and would still get THREE (3) vibrations. Bricked. So, I looked through a few threads on XDA, and found a few ways to fix it. Something about a Blind HBoot, or a Qualcomm Diagnostic Mode being stuck or something. Figured it was my best shot to try these. I tried them all. I put the PG76IMG.zip into my SD card, and booted up when holding Volume down, and only got THREE (3) vibrations. The tutorial said I was supposed to get FIVE (5) vibrations. So, I thought maybe it was something strange, and kept going through the tutorial. After five minutes, I'm supposed to press VOL UP, and should feel THREE (3) vibrations. Nothing happened. I waited and waited and tried again, and still, nothing. My phone is still lying here as a paperweight, and I want to get this working, so I can sell it because this phone is too much of a ****ing hassle for me. NOTHING HAS WORKED. ROMS, KERNELS, NOTHING. HAS. WORKED. I'M TIRED OF IT. I'm not a noob, I've been working with Android phones for a long time, and have never quite used an HTC device before. I had a Samsung Galaxy S Fascinate (CDMA) and it lost it's flash after I had moved to a different state. (The state I'm in does not have any towers for that carrier here.) SO. Can ANYONE give me a HIGHLY DETAILED tutorial, STEP BY STEP, to fix my phone?
HTC Wildfire S *Relocked* bootloader S-OFF CDMA METRO PCS.
I have tried everything I can find, and I have reached my wits end, man. Please, for the love of GOD, help me. I would really appreciate it.

I had 1000 rom flashes
3 Updates through RUU
Never had a brick
I hope someone can help you.
This is same as this thread http://forum.xda-developers.com/showthread.php?t=1522235

m1ndh4x8r said:
I had 1000 rom flashes
3 Updates through RUU
Never had a brick
I hope someone can help you.
This is same as this thread http://forum.xda-developers.com/showthread.php?t=1522235
Click to expand...
Click to collapse
I don't see how this helps me.

Help in the sense u have sent it to HTC for repair

Try this http://forum.xda-developers.com/showthread.php?t=1432425
Sent from my HTC_A510c using Tapatalk

kyleisah said:
HI. Okay, so a couple weeks ago, I received a notification from HTC that said there was a new update available. Since I had S-Off and an unlocked bootloader (don't ask why, I just ****ing do.) I could not update, as it would give me errors, and cancel the update. So, earlier today I was fed-up with how slow my phone was being, and I wanted to fix it by updating. So I scoured XDA and found a thread about how to update by updating the HBoot or whatever. I followed those instructions and everything was fine, until I got to the initial part of installing the new **** through RUU. It was running fine, and then all of a sudden, the phone disconnected and ****ed the installation up. My battery was fully charged, and still has a charge as I am writing this. I digress. Whenever I would try to power my phone on, I would feel THREE (3) vibrations, and nothing would happen after. I tried booting into the stock recovery (fastboot, recovery, etc) and would still get THREE (3) vibrations. Bricked. So, I looked through a few threads on XDA, and found a few ways to fix it. Something about a Blind HBoot, or a Qualcomm Diagnostic Mode being stuck or something. Figured it was my best shot to try these. I tried them all. I put the PG76IMG.zip into my SD card, and booted up when holding Volume down, and only got THREE (3) vibrations. The tutorial said I was supposed to get FIVE (5) vibrations. So, I thought maybe it was something strange, and kept going through the tutorial. After five minutes, I'm supposed to press VOL UP, and should feel THREE (3) vibrations. Nothing happened. I waited and waited and tried again, and still, nothing. My phone is still lying here as a paperweight, and I want to get this working, so I can sell it because this phone is too much of a ****ing hassle for me. NOTHING HAS WORKED. ROMS, KERNELS, NOTHING. HAS. WORKED. I'M TIRED OF IT. I'm not a noob, I've been working with Android phones for a long time, and have never quite used an HTC device before. I had a Samsung Galaxy S Fascinate (CDMA) and it lost it's flash after I had moved to a different state. (The state I'm in does not have any towers for that carrier here.) SO. Can ANYONE give me a HIGHLY DETAILED tutorial, STEP BY STEP, to fix my phone?
HTC Wildfire S *Relocked* bootloader S-OFF CDMA METRO PCS.
I have tried everything I can find, and I have reached my wits end, man. Please, for the love of GOD, help me. I would really appreciate it.
Click to expand...
Click to collapse
ok, im not saying i can get it going again but i`ll do my best to help. lets start from the beginning, what actually works atm? you say when you try boot up the phone in any way it just vibrates 3 times.
does it do anything else, does the screen light up?
does it even stay on?
when you connect it to the charger does the led still light up?
have you tried to connect it to the pc? have you tried to connect it too the pc with volume down first?
all seem very basic stuff obviously but if the pc can register it in hboot we might be able to get a ruu running on it.

Found this on a different thread...
Nevermind. Just realized you were still getting three vibrates. Sorry man. I'll keep an eye out if I see anything else that might help.

what is your hboot version? i was see 1.09.099 like in forum maybe you can start with update hboot.
you can use adb for all of this works. download a ruu and run it. after some steps you can find rom.zip in windows/temp extract it to a folder like c:\android\rom and use adb for install all *.img files. maybe it can fix that problem

hypercode said:
what is your hboot version? i was see 1.09.099 like in forum maybe you can start with update hboot.
you can use adb for all of this works. download a ruu and run it. after some steps you can find rom.zip in windows/temp extract it to a folder like c:\android\rom and use adb for install all *.img files. maybe it can fix that problem
Click to expand...
Click to collapse
seriously , adb can install img files ?!

Alright, well, I called htc and told them about my problem, and I might have to just send it in. BUT. I had my phone rooted, and had CM Recovery on it. So, since nothing is booting up at all, only the three vibrates when trying to enter either boot mode, will they be able to see that I had it rooted or anything? They said they'll charge 35$ just to ship it back in the same condition if it is. Can't really afford anything like that right now.
tl;dr I had my phone rooted, but nothing on my phone comes up, will they see my root or anything?

if you are rooted you are probably s-off or at least have unlocked bootloader. and both they will find out very easily.

Sorry for my bad it was fastboot.exe you can install .img files with fastboot.exe i was installed stock recovery with that
Sent from my HTC Wildfire S A510e using XDA App

[Q] Unsuccessful Root of Desire HD. Please Help, Newbie Here.

Hello everyone, first of all I am a total newbie not just to rooting but also today was my first time ever using linux so please bear with me. Having said that, I have done my best to learn and understand the linux commands in the effin manual and followed all instructions as best as I could though I couldn't understand them well enough which is why I am here.
I am using Ubuntu 11.04 64 bit live cd but managed to install the i32-libs as stated in the effin manual. This is the only version of Ubuntu I could get from my friends as I have very slow internet connection and cannot download the new version or just the 32 bit one.
Anyway, on to the problem at hand.
I first ran the aahk, going through all the steps in the effin manual. My phone was originally on 2.3.5 and Sense 3 so I had to downgrade and the aahk downloaded the necessary rom(?) or RUU (?) to do this.
Once that was done, aahk carried on until the step where my phone rebooted.
This was where things started going wrong for me.
When the phone rebooted into 2.3.3 and started the wizard to set up my phone, I went through all that.
If I recall, at this point the aahk screen was up to “Once the downgrade is successful, press a key to return to the menu.... Otherwise, cut and paste the output to the screen into a text file for evaluation... then press a key. Press any key to continue...”
However, the step before that, “The phone will now reboot into HBOOT. If everything is okay, the phone will prompt you to continue by pressing VOLUME UP. It will reboot, flashing twice.”
PUSH POWER WHEN THIS STEP COMPLETES
I don't recall this happening for me or maybe it did but I did not notice. I did not press VOLUME UP nor see the flashing twice but surely it happened? Otherwise I would have been able to reboot into the phone environment correct? My head is spinning now...
Okay, this is where I may have gotten ahead of myself when reading the effin manual. You have to understand, I was just brimming with joy “thinking” I had successfully rooted my first ever and one and only smartphone.
I started looking for BusyBox or Superuser but couldn't find anything.
Not knowing what else to do, I rebooted the phone MANUALLY (hold power button and reset).
Then everything started going wrong.
Please don't get mad. I did not realise the aahk had to reboot several times. I thought once and that was it. I just found that out now.
However, between that time and when I found this out I believe I caused all sorts of damage.
When the phone rebooted, it got stuck on the white screen with HTC logo and aahk was no longer working.
The wrong things I did were to to go into HBOOT and RECOVERY and WIPE EVERYTHING (DATA, CACHE, DAVLIK, EVERYTHING) *SORRY!*
And so here I am, hoping someone can help me.
After searching around the forums some similarities I had with other users in the past was that the phone is still showing S-ON and because of what I had done, aahk did not get to work properly so my phone has no ROM and no RECOVERY.
And I also JUST realised I made things worse by deleting USB debugging when I WIPED everything!.
Please help.... (_ _”)

I can help you out. Can you still go in Hboot?
Sent from my Desire HD using XDA

dnplee said:
Hello everyone, first of all I am a total newbie not just to rooting but also today was my first time ever using linux so please bear with me. Having said that, I have done my best to learn and understand the linux commands in the effin manual and followed all instructions as best as I could though I couldn't understand them well enough which is why I am here.
I am using Ubuntu 11.04 64 bit live cd but managed to install the i32-libs as stated in the effin manual. This is the only version of Ubuntu I could get from my friends as I have very slow internet connection and cannot download the new version or just the 32 bit one.
Anyway, on to the problem at hand.
I first ran the aahk, going through all the steps in the effin manual. My phone was originally on 2.3.5 and Sense 3 so I had to downgrade and the aahk downloaded the necessary rom(?) or RUU (?) to do this.
Once that was done, aahk carried on until the step where my phone rebooted.
This was where things started going wrong for me.
When the phone rebooted into 2.3.3 and started the wizard to set up my phone, I went through all that.
If I recall, at this point the aahk screen was up to “Once the downgrade is successful, press a key to return to the menu.... Otherwise, cut and paste the output to the screen into a text file for evaluation... then press a key. Press any key to continue...”
However, the step before that, “The phone will now reboot into HBOOT. If everything is okay, the phone will prompt you to continue by pressing VOLUME UP. It will reboot, flashing twice.”
PUSH POWER WHEN THIS STEP COMPLETES
I don't recall this happening for me or maybe it did but I did not notice. I did not press VOLUME UP nor see the flashing twice but surely it happened? Otherwise I would have been able to reboot into the phone environment correct? My head is spinning now...
Okay, this is where I may have gotten ahead of myself when reading the effin manual. You have to understand, I was just brimming with joy “thinking” I had successfully rooted my first ever and one and only smartphone.
I started looking for BusyBox or Superuser but couldn't find anything.
Not knowing what else to do, I rebooted the phone MANUALLY (hold power button and reset).
Then everything started going wrong.
Please don't get mad. I did not realise the aahk had to reboot several times. I thought once and that was it. I just found that out now.
However, between that time and when I found this out I believe I caused all sorts of damage.
When the phone rebooted, it got stuck on the white screen with HTC logo and aahk was no longer working.
The wrong things I did were to to go into HBOOT and RECOVERY and WIPE EVERYTHING (DATA, CACHE, DAVLIK, EVERYTHING) *SORRY!*
And so here I am, hoping someone can help me.
After searching around the forums some similarities I had with other users in the past was that the phone is still showing S-ON and because of what I had done, aahk did not get to work properly so my phone has no ROM and no RECOVERY.
And I also JUST realised I made things worse by deleting USB debugging when I WIPED everything!.
Please help.... (_ _”)
Click to expand...
Click to collapse
Do not panic...although you did a factory reset and disabled usb debugging, you can solve your situation. Just flash the RUU (PD98IMG-GBx.zip) file you used to downgrade the phone. It has to be in the PD98IMG folder of the Hack Kit. Make sure that it is that file and no other. Rename it PD98IMG.zip and then put it in the root of the sdcard. Then boot in hboot and update pressing volume up. Let it finish....then you will have a working phone. Then re run the hack kit to Gain S-OFF and Root....if you can´t do it just hit the IRC Channel that is stated in the OP of the Hack Kit thread.

benydc, glevitan, thank you both for the offers of help and advice.
I eventually found my way to the IRC aahk support channel and was blessed to get the help of attn1, one of the ops there.
He helped me through my problem and now everything is as is should be. Thankfully I have a working rooted phone.
Everyone there was very friendly and helpful, not just attn1. He must have spent the last two hours or so juggling with helping out three users (probably more). We even got to make some friendly banter amongst ourselves.
Though I was freaked out initially, I am glad everything works now and from the support I got there, I am somehow not going to shy away from trying to learn about rooting.
I managed to save all the text during our conversation so when I get the time, I will try and build a simple but detailed walkthrough of how attn1 got my phone working again. I will post it here so that it may help others who find themselves in a similar position one day.
Many thanks you guys. This is a great community.

same problem,s-on,no recovery
hey there...ive got similar problem with u and i try putting the PG98IMG on the root of the SD card which i get from the folder from AAHK...but when i go to HBOOT and try to install the PG98IMG, it failed and it says MAIN VERSION IS OLDER ! what should i do?

hi
i have same phone whith you
2.3.5 sens 3.0
i used AAHK but the file name downloaded is "PD98IMG-GB2"
you can rename "PD98IMG" on "PD98IMG-GB2"

new problem?

okay guys ill make this quick.
my one x had no problems at all since I got it, few days ago htc launcher starts to crash and i realize a bit of battery drain and some lag, so I pressed the power botton for 10 sec for a full restart. after boot(ONEX logo) comes a black screen and i cant do anything, i press power button nothing happens just the buttons at the bottom will light up.
i posted my problem here at XDA and i was told to do a factory rest which i did and it erased all my pics and data .
anyway, today i pressed the power botton and same problem happend so can anyone tell me whats rong with the phone?
things you may need to know.
fast boot mode is on
android version 4.0.3
htc sense 4.0
software 1.26.401.2 (I didnt update software because im hoping to get S-off.)
PLEASE GUYS HELP
i really dont want to factory rest my phone every day.

mr.dj26 said:
okay guys ill make this quick.
my one x had no problems at all since I got it, few days ago htc launcher starts to crash and i realize a bit of battery drain and some lag, so I pressed the power botton for 10 sec for a full restart. after boot(ONEX logo) comes a black screen and i cant do anything, i press power button nothing happens just the buttons at the bottom will light up.
i posted my problem here at XDA and i was told to do a factory rest which i did and it erased all my pics and data .
anyway, today i pressed the power botton and same problem happend so can anyone tell me whats rong with the phone?
things you may need to know.
fast boot mode is on
android version 4.0.3
htc sense 4.0
software 1.26.401.2 (I didnt update software because im hoping to get S-off.)
PLEASE GUYS HELP
i really dont want to factory rest my phone every day.
Click to expand...
Click to collapse
Why do you have fastboot on?
And why you didn't update? Where did you find out that you will get S-OFF on that firmware?

PAGOT said:
Why do you have fastboot on?
And why you didn't update? Where did you find out that you will get S-OFF on that firmware?
Click to expand...
Click to collapse
software update will update hboot, and fast boot is on because when i shut off the off and turn it on it starts up in seconds.
anyway, any idea about the problem?

mr.dj26 said:
software update will update hboot, and fast boot is on because when i shut off the off and turn it on it starts up in seconds.
anyway, any idea about the problem?
Click to expand...
Click to collapse
Well try to use your phone without the fast boot on?
And okay I still do not get the point? Have you asked in the S-OFF thread and they said, that S-OFF will come only for the old hboot and everyone who updated wont get S-OFF?
If that would be the case, there would be many many unhappy ppl.
So you rather will be on a half year old bug filled fw as to update and use your phone properly?

Turn off fast-boot. And then do a reboot. Elimination my friend.

PAGOT said:
Well try to use your phone without the fast boot on?
And okay I still do not get the point? Have you asked in the S-OFF thread and they said, that S-OFF will come only for the old hboot and everyone who updated wont get S-OFF?
If that would be the case, there would be many many unhappy ppl.
So you rather will be on a half year old bug filled fw as to update and use your phone properly?
Click to expand...
Click to collapse
i tried hard reset with both fast boot on and off both work; i just dono why im having this problem.
and about the update, i didnt have any issues with my phone so I didnt update and I have read somewhere that after update it would be difficult to s-off i dont remember.
thank for your help

oliseo said:
Turn off fast-boot. And then do a reboot. Elimination my friend.
Click to expand...
Click to collapse
so you think this is the reason of the problem?
thanks

mr.dj26 said:
i tried hard reset with both fast boot on and off both work; i just dono why im having this problem.
and about the update, i didnt have any issues with my phone so I didnt update and I have read somewhere that after update it would be difficult to s-off i dont remember.
thank for your help
Click to expand...
Click to collapse
To be rude, you think you have no issues with 1.26 doesn't means that the firmware is stable. And yes, everyone here knew 1.29 is the ways much better than 1.26 with a bunches of fixes and tweaks.
For the s-off progress, as far as I know those developers who are working on it do not stayed tight on 1.26 hboot (correct me if I'm wrong), though some of them has s-off devices. The main barriers on s-off path was not a newer hboot patching holes (there is no big hole found yet) but was the HTC hardworks to barricaded us to have a talk with tegra. On my guess, even there is a solution reveal it will be less likely to be achieve through an old hboot only.
To be honest, you are the only here i had seen that are stayed on 1.26 for s-off..

mr.dj26 said:
so you think this is the reason of the problem?
thanks
Click to expand...
Click to collapse
With bugs like this, it's a process of elimination. Unless it's specifically ruled out (ie, you still suffer the same bug regardless of fast-boot being on or off), then you can only assume that may be.
See what happens if you turn it off. If it works, you know that was causing the issue. If it doesn't, then repeat the process until you eliminate all possibilities. (ie, does it crash after you've transferred files via USB, switched WiFi on/off).
Once all possibilities (within your remit of course) have been exhausted then it's time to send it off, as it's nothing you can solve and it could be a hardware issues (bad memory perhaps??)
Anyway, let's go for the easy fix first, and I keep my fingers crossed that turning off fast-boot helps.

HebeGuess said:
To be rude, you think you have no issues with 1.26 doesn't means that the firmware is stable. And yes, everyone here knew 1.29 is the ways much better than 1.26 with a bunches of fixes and tweaks.
For the s-off progress, as far as I know those developers who are working on it do not stayed tight on 1.26 hboot (correct me if I'm wrong), though some of them has s-off devices. The main barriers on s-off path was not a newer hboot patching holes (there is no big hole found yet) but was the HTC hardworks to barricaded us to have a talk with tegra. On my guess, even there is a solution reveal it will be less likely to be achieve through an old hboot only.
To be honest, you are the only here i had seen that are stayed on 1.26 for s-off..
Click to expand...
Click to collapse
lol
thanks for your help

oliseo said:
With bugs like this, it's a process of elimination. Unless it's specifically ruled out (ie, you still suffer the same bug regardless of fast-boot being on or off), then you can only assume that may be.
See what happens if you turn it off. If it works, you know that was causing the issue. If it doesn't, then repeat the process until you eliminate all possibilities. (ie, does it crash after you've transferred files via USB, switched WiFi on/off).
Once all possibilities (within your remit of course) have been exhausted then it's time to send it off, as it's nothing you can solve and it could be a hardware issues (bad memory perhaps??)
Anyway, let's go for the easy fix first, and I keep my fingers crossed that turning off fast-boot helps.
Click to expand...
Click to collapse
i really appreciate ur help guys
i just had the problem again, fast boot was off.. just did a factory reset
theres no crashs when transferring file or turning wifi on or off.
this is really weird.
do you think flashing RUU may help or its the ame as factory reset?
thanks..

Worth trying.

BenPope said:
Worth trying.
Click to expand...
Click to collapse
I have never flashed an ruu before.
can you tell me how that work and from where I can get it? my cid is J_15
and im useing mac, will it work?
thanks m8

There is a sticky Endeavor shipped ROM collection thread in dev section.
You can't easily do it from Mac, if at all.

BenPope said:
There is a sticky Endeavor shipped ROM collection thread in dev section.
You can't easily do it from Mac, if at all.
Click to expand...
Click to collapse
theres no guide on how this works..
my cid is J_15, which file should i download ?:S
i really hope this would do it, htc support at my place isn't that good and i really dont want to send it back and wait for ages

,,
i rebooted the phone now more than 10 times with now problems,
the phone now has no apps or anything brand new.
could it be a cause of apps or something?

Just look at your software version, then find the RUU in the link from the first page in the sticky thread.
Then borrow a Windows machine and run the RUU with your phone connected.

BenPope said:
Just look at your software version, then find the RUU in the link from the first page in the sticky thread.
Then borrow a Windows machine and run the RUU with your phone connected.
Click to expand...
Click to collapse
okay here it is 1.26.401.2
now when i want to download it it requires premium account WT* ?!

.
dose flashing the RUU require adb or only htc driver?

I'm in the same position. Woke up yesterday, booted phone, black screen after "HTC One" screen. Oddly I could change the volume and the volume changer would display on a black screen. Restarted, same thing. Factory reset, no problems. All the while fast-boot is off.
Same thing happened this morning, cold boot, "HTC One" screen then black screen. Factory reset and immediately rebooted - same thing again! is this a hardware issue or a corrupt software issue?
Will go and join the incredibly long and slow moving at the HTC service centre after work.
---------- Post added at 12:34 PM ---------- Previous post was at 11:50 AM ----------
I've spoken with HTC customer services and they recommend taking the phone in to get it flashed - basically they think that there is a problem with the software. They claim it is a quick job.
They offered to come out to my office and collect my phone and return it tomorrow - I'm impressed with that level of service... pending they can fix it with a simple flash of the firmware!