Develop Bugs

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!

[Q] What should I do in case of semi-brick?

I rooted my HTC One X and unlocked the bootloader with HTCDev earlier this year. Recently I have had this problem with the phone where it bugs out. Sometimes in the middle of using the phone the screen will turn off and on showing the unlock screen while the Home buttons pulsate white.
So I did a factory reset and the phone seemed to work quite well not as buggy. After I had to revive it by leaving it on the charger for a couple hours.
I also have clockwork recovery still installed and I made a back up image that you guys talk about. The boot.img which I made after I rooted and facotry reset it. I don't think you can even get the boot img without it have that recovery program.
My question is should I try and mess with it some more? Should I re root it? I just want it function with out breaking now is my goal.
And is there any way to hide that whole "This is HTC software... do not distribute " message that comes up when I boot the phone? Because I know this voided my warranty but if I could get rid of that message my warranty is through a third party so I might be able to get a replacement if I can get that boot message off.

After re rooting it it seemed to calm down and the frequency of restarting was down significantly.

Now after a week, it is starting to restart again. Should I of flashed the kernel? I see that throw around a lot here in these forums but I don't know if it pertains to my situation. Anything help would be appreciated.

TheZander said:
I rooted my HTC One X and unlocked the bootloader with HTCDev earlier this year. Recently I have had this problem with the phone where it bugs out. Sometimes in the middle of using the phone the screen will turn off and on showing the unlock screen while the Home buttons pulsate white.
So I did a factory reset and the phone seemed to work quite well not as buggy. After I had to revive it by leaving it on the charger for a couple hours.
I also have clockwork recovery still installed and I made a back up image that you guys talk about. The boot.img which I made after I rooted and facotry reset it. I don't think you can even get the boot img without it have that recovery program.
My question is should I try and mess with it some more? Should I re root it? I just want it function with out breaking now is my goal.
And is there any way to hide that whole "This is HTC software... do not distribute " message that comes up when I boot the phone? Because I know this voided my warranty but if I could get rid of that message my warranty is through a third party so I might be able to get a replacement if I can get that boot message off.
Click to expand...
Click to collapse
delete

matt95 said:
delete
Click to expand...
Click to collapse
delete what? am I posting wrong? is there some kind of forum rule or format for asking questions or something?

Phone Dead After Recent OTA Update

Hi All,
First of all I'm not a native english speaker and I'm a noob in this stuff o rom's .
I recently bought a phone and on update it to JB 4.1.1 with Sense 4+ . Everything went ok and the phone apparently was working ok.
The next day I just noticed that the bluetooth was not 100% because I had some cuts in the sound when connected to a bluetooth headset. Because of this I looked for another OTA update and it found one that said somethink like "General System Improvement" or something like that.
I've installed it but this update didn't went till the end since I get stucked on the "red sign" indicating some fail. I try to reboot the phone but apparently he was dead.
After a lots of tries and key combinations I was able to enter the boot mode and choose to restore to factory mode, but apparently it was not successful. Then I tried and option to check for CRC of img files I think (not sure because don't remeber). It check for 3 images files showing the CRC code, then I think the phone get stucked on one because I still have the waiting message but nothing else happens.
I pressed power button again trying to reboot the phone but since then then phone died completly. The only sign of life is when I connect to the PC windows emits the sound of detecting something but gives an error related to the drives.
Sometimes I get a message saying that a ARX device was found but not anymore.
Tried almost everything that I could read on this forum but nothing seems to work...I think the phone is looping on the boot or doesn't have any battery...not sure.
I've tried some RRU but they fail to find the phone saying not connected or not detected.
Any help will be greatly appreciated, Thanks
Johny

Sent it back for warranty repair as soon as you can this is a known fault as it happened to me recently.
Similar problems: http://forum.xda-developers.com/showthread.php?t=2075862
Getting out of APX mode

Your bootloader isn't locked right? Or were you ever rooted? If the answer is no, just send it to HTC and your warranty will do the rest.
Sent from my HTC One X using xda app-developers app

[Q] Screen flickering / Bootloop -> Is my Nexus dead? Data recovery possible?

Hello,
just some hours ago my Galaxy Nexus (SC-04D) rebooted while lying on the table next to me. After several sings of vibration I noticed that the phone doesn't boot completely.
When switching on the phone I get the turn-on-vibration, then the google letters are displayed. Most times the word "google" flickers from left to right over the screen (only the line where the word is supposed to be). Sometimes it boots further and I get the colored "X" displayed. This symbol starts flickering, too and if it went so far it reboots.
Here are two pictures I took from the phone failing to boot:
picpaste.com/img_0001_01-Rmm7kDYb.jpg
picpaste.com/img_0001-eoLqVoiM.jpg
The phone is running stock Android from Docomo. The phone is about 14 months old and has never been unlocked, rooted, modded, taken a bath, ... 'til now.
I tried starting with and without SIM-card, with and without charger attached and let it lie around for several minutes without battery between my tries.
Is there any chance to get my data from the phone or even get it fixed? Please give me a hint what I can do.

Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix. This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery

Thanks GPFboy for your fast response,
GPFboyJS said:
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix.
Click to expand...
Click to collapse
As far as I understand a factory reset results in a complete loss of data on the phone, right? So without root/unlock there's no chance to get my data from the phone? That would be really bad.
GPFboyJS said:
This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
Click to expand...
Click to collapse
What is "too many"? I think there are about 35 apps installed atm. By the moment the problem arose wifi and 3g-data,BT,GPS were disabled and just a minute before I took a look how late it was. So nothing special.
GPFboyJS said:
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Click to expand...
Click to collapse
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?

BrainSD said:
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
Click to expand...
Click to collapse
thats stock recovery.
is your bootloader already unlocked or no?

Zepius said:
is your bootloader already unlocked or no?
Click to expand...
Click to collapse
It's still locked.

you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.

Zepius said:
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Click to expand...
Click to collapse
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?

BrainSD said:
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
Click to expand...
Click to collapse
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.

beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Well if I was him I would be more worried about my expensive phone instead of data. Maybe a lesson for later to have a backup
Sent from my Galaxy Nexus using XDA Premium HD app

beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Yes exactly this is the point. Since I don't have a current data backup the first thing to try is getting my data from the phone. I already tried temporary loading the clockwork recovery through fastboot - with the galaxy nexus toolkit and by hand(sdk) - but it failed ("Bootloader locked").
What I'm wondering about is the fact that the phone seems to behave normally in odin and fastbood mode but going nuts the moment it's expected to boot. Besides the flickering google logo and the "matrix-modded" dead android it even ended up in a totally green screen one time.
At the moment I don't dare trying to unlock/flash the phone because of being afraid getting stuck and ending up with the phone being in some kind of undefined / totally broken state. Initially I was in hope of being able to rescue my data but now i will try my luck with docomo support first.
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
I will try to get through 1 to 4 of the guide first and see how far I get.
If this won't work I might try to unlock, recover and try to "undelete" what's possible. (http://forum.xda-developers.com/showthread.php?t=1994705)
Does this order make sense?
Btw, having a dead phone is bad, of course, even when I got it new for 2300Yen but loosing some pictures i really liked and having no phone atm currently hurts more. Especially when knowing that I was thinking of copying all photos to my computer only one day before when I pulled only some minor important ones from the phone I needed for work and planned to do a full backup and unlock this weekend when I get back my 'Milestone' currently lent to someone else.
Once again something I learned. Backup! Even you phone.

BrainSD said:
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
Click to expand...
Click to collapse
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.
It will unlock your bootloader, bypassing fastboot. Still, it's not for the faint hearted. I refered to omapflash because its a low level tool, it doesn't require the bootloader to be unlocked, and is able to restore the bootloader to working state, and I got there because you mentioned you see graphical glitches/flickering which may indicate bootloader partition failure and/or consequent corruption.
I think that's your best shot at trying to get your data back. After unlock, boot to fastboot and 'fastboot boot custom_recovery.img', and grab your stuff (if you can) from /data/.

beekay201 said:
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.....
Click to expand...
Click to collapse
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems

BrainSD said:
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
Click to expand...
Click to collapse
Great, so far so good.
Yeah, they're ext4 images, but sparse images i believe - link

[Q] Red triangle after factory reset

Hey guys, new member to this forum here. So, recently i just factory resetted my converted GPE HTC one m8 with supercid. After that, something might have went wrong somewhere because my phone booted into the stock recovery with the red triangle. I tried factory resetting through this recovery as well and rebooted it but to no avail since my phone just keeps rebooting into the screen over and over again. I'm getting kinda worried now since this has never happened to me before. I just want to start my phone again. Help...

Pete7856 said:
Hey guys, new member to this forum here. So, recently i just factory resetted my converted GPE HTC one m8 with supercid. After that, something might have went wrong somewhere because my phone booted into the stock recovery with the red triangle. I tried factory resetting through this recovery as well and rebooted it but to no avail since my phone just keeps rebooting into the screen over and over again. I'm getting kinda worried now since this has never happened to me before. I just want to start my phone again. Help...
Click to expand...
Click to collapse
Hi Pete,
Did you ever find a solution to this issue, I have colleague with the same issue as you.
He did a factory reset and efter that the phone just goes to boot loop, as you we have access to recovery.

Leo_83 said:
Did you ever find a solution to this issue, I have colleague with the same issue as you.
Click to expand...
Click to collapse
The thread is from Jan 2015. Whatever applied to the OP almost a year and a half ago, may not apply to you. Lots of things change in Android month by month, and what worked for an old build might not for you.
Also, he converted to GPE and SuperCID. Is it really the exact same problem? In any case, you should give details about your device if you want any meaningful help (most easily and comprehensively by doing fastboot getvar all, and post the output - delete IMEI and serial number before posting).
RUU is one solution that comes to mind.