Develop Bugs

[Q] Buggy screen on any DK28 rom

any time i try to flash to anything dk28 based, i get the same result. the touch screen (almost) randomly stops responding to input. seems to be related to keyboard opening, but not always. example: from sleep, wake > slide unlock > slide notification bar > tap... "damn it..." can't open the notification unless i sleep it and start over. this is not a hardware problem so far as i can tell as it works fine when flashed to stock. it's less than 2 weeks old and no, i did not spill anything on it. am i alone here?
not new to android, nor am i new to flashing roms, hacking portable devices / electronics in general or using forums. i did search and nothing matched my issue. please don't treat me like a noob just bc my account is new.

As of this morning my phone seems to have developed this kind of behavior, out of the blue. I have no idea what caused it, just that it is exceptionally frustrating.

further info:
...this was all using cwm3 one click with conversion to ext4. just installed cwm 2.5 and flashed the zip version of dk28 (from here) and got the same result again... damn it... back to the beginning again...

Flashed Nebula (seven sisters) and got the same... I mean, if it did this on stock fw I would obviously exchange it... but its only when I flash. So either I'm doing something wrong, there is something wrong with my handset or there's something with cwm or dk28 causing this. Not outside the thought of me doing something wrong, but I've tried so many different things at this point... the only thing I have left I think is flashing dk28 as an update. Is there one around?
Sent from my SPH-D700 using XDA App

my epic was doing the same thing after i flashed midnight but then just a soon as it started it stopped and hasnt happened since. ive tried to recreate to solve it but to no avail if you figure anything out please let me know

Odin back to stock = fine.
flash update.zip for here = intermittently unresponsive again.
seriously... no one else is getting this continuously? i mean it's pretty unusable...

I'm still getting it pretty consistently, I haven't flashed back to DI18 to see if that fixes it. (Odin and I have a bitter history) I suppose if I'm going to take it back I need to flash it back though.

yeah, i did something wrong the first time with Odin but i'm pretty comfortable now. don't know what i did before, but it failed and nearly bricked. as i understand it now:
1. remove sd card (i just go ahead and pop out the battery while i'm at it)
2. boot into download mode (boot while holding "1")
3. select victory PIT and DI18 in PDA
4. uncheck everything but restart
5. connect handset and verify that it is seen
6. go.
have done this about 10 times now and haven't had a problem... until i try to do go to DK28...
I think i'm going to have to wait for official FROYO... it's killing me but i don't want to try to walk into sprint like "hey, my rooted phone doesn't work right...". if it still happens on official 2.2, i will swap.

Mine does the exact same thing. I asked about it yesterday because I couldn't find anyone with a similar issue but the only answer I received was to go back to stock and try it again. I did that and I got the same result.

I ended up just taking the phone into a Sprint repair center, they replaced the screen and didn't even mention the DK28 Bonsai 2.0.1. For free, in less than three hours.

I'm a little confused, are u flashing DK28 with Odin?

It doesn't seem to matter how I flash:
tried flashing just DK28 in Odin
tried flashing modem/pit in Odin and ROM in CWM3
tried the same with CWM2.?
tried update.zip from stock recovery
all get the same result. Behavior seems to actually be time based - like when wake from sleep, it responds for a few seconds and then stops. it doesn't come back until i sleep/wake again, then it's fine.

UPDATE
EB13 is out, installed and still causing an issue. I will be going to the Sprint store later. Still don't know why this didn't happen on DI18, but whatever - happens on official release now so a replacement is justified.

Phone reboots and gets stuck on "HTC Inc" bootscreen

I've owned my DInc for around 8 months now and a week after I got the phone I had rooted it... The only thing I truly did was install a few custom ROM's on it to try out what I liked, when Froyo was in it's prime I used CM6 nearly every day, and now Gingerbread is around I've been running steady on OMGB6/7 for the past few months...
My problem is that last week my phone randomly rebooted and decided to get stuck on the white "HTC" boot logo... It stayed there for around 10 minutes before I finally decided to pull the battery, restart it, and the same thing occured.
Of course I have CWR installed with Nandroid backups, but when I used the backup for the current ROM I was on, it happened again getting stuck at the white screen. So I fired up CWR again and restored to a previous version of OMGB6 and that ran steady until today (in the middle of calculus of course) it rebooted after sending a text and got stuck at the white screen once more...
Now I CWR restored to my Stock HTC Sense ROM and I'm running that as we speak (and god, is it god-awful).
WTF is wrong with my Incredible? I'm guessing something got corrupted maybe in the /boot partition or something of the likes? Could someone please help me? I've never had this problem before... and never did any "customization" other than wiping my cache/data/dalvik/battery stats and installing different ROMs.
Thank you!

al2x said:
I've owned my DInc for around 8 months now and a week after I got the phone I had rooted it... The only thing I truly did was install a few custom ROM's on it to try out what I liked, when Froyo was in it's prime I used CM6 nearly every day, and now Gingerbread is around I've been running steady on OMGB6/7 for the past few months...
My problem is that last week my phone randomly rebooted and decided to get stuck on the white "HTC" boot logo... It stayed there for around 10 minutes before I finally decided to pull the battery, restart it, and the same thing occured.
Of course I have CWR installed with Nandroid backups, but when I used the backup for the current ROM I was on, it happened again getting stuck at the white screen. So I fired up CWR again and restored to a previous version of OMGB6 and that ran steady until today (in the middle of calculus of course) it rebooted after sending a text and got stuck at the white screen once more...
Now I CWR restored to my Stock HTC Sense ROM and I'm running that as we speak (and god, is it god-awful).
WTF is wrong with my Incredible? I'm guessing something got corrupted maybe in the /boot partition or something of the likes? Could someone please help me? I've never had this problem before... and never did any "customization" other than wiping my cache/data/dalvik/battery stats and installing different ROMs.
Thank you!
Click to expand...
Click to collapse
This used to happen with me on OMGB, its one of the reasons I switched to CM7. When I rebooted it used to get stuck on the splash screen. Mine, however, would work after a battery pull. I'm not sure, I'd try a fresh install, if that doesnt help, try out CM7, its a pretty stable.

Oh ok... so you're saying its probably just a ROM issue with OMGB? I'd switch to CM7 but the only thing I want is stock Gingerbread, I really hate the little customizations they put into CM7. Do they still have that CM7 Source project going on where it was pretty much stock gingerbread? Thanks again!

al2x said:
Oh ok... so you're saying its probably just a ROM issue with OMGB? I'd switch to CM7 but the only thing I want is stock Gingerbread, I really hate the little customizations they put into CM7. Do they still have that CM7 Source project going on where it was pretty much stock gingerbread? Thanks again!
Click to expand...
Click to collapse
I'm not saying thats 100% the case. I'm just saying that used to happen to me when I ran OMGB. I couldn't find a fix, so I just switched ROMs. I don't think CM7 has a just stock gingerbread look. But how can you not like all the features they packed into it?

AOSP + SD
Perhaps try flashing a Sense ROM and see if the issue persists.
Why?
AOSP ROMs interact quite a bit w/ the SD card. So, if there are issues w/ the SD card, the Sense ROM may not present as many funky issues.
After that test, I'd try another SD card and see if the issue persists.
If a different SD yields no wonky stuff, the answer was faulty SD card.

continual spontaneous reboots
I have the same issue. I was using CM6.1 I think and it's been fine for awhile and then it just started spontaneously rebooting. I can no longer get into Clockwork, all I can do is hold volume down and power to start it and from there, nothing will start the phone. I get the HTC spash and after about 3 seconds, it reboots and gets stuck in that cycle. Nothing has really changed and it rebooted on it's own to start the problem.
So, it's not like I installed something and rebooted. I'm interested in hearing if others are having the issues and what exactly their thoughts are.

[Q] Help with unresponsive rooted phone

Hi guys,
I need your expertise and ultimately your help!
So i was running Lee droid for months, it was all good, did loads of flashing of roms without never any (massive) issues.
Last week, i decided i wanted to try gingerbread, so I flashed gingervilain and the kernel that went this it. I din't really like it, i missed sense too much so i decided to go back to Lee Droid.
I did a clean install after wiping everything as i've done dozens of times in the past. But ever since a problem has arisen.
Whenever I'm on call, when i move the phone away from my face, the screen doesn't turn on and I can't turn it on at all, even when i press on the power button. Which means i can't hang up. So if i call someone and end up on voicemail, I need to remove the battery to finish the call, and whenever I am on the phone with someone I have to ask the person to hang up as I have no control over the phone.
The phone is to be totally irresponsive.
I tried to re-install gingervillain and had the same problem. So I reverted again back to Lee's rom, from a clean install and the problem persists!!
Last night I tried to format the card and I installed snq's new kernel, but it still doesn't work.
I have no clue what's going on. Could it be a voltage issue???
I'm s-on by the way.
I'm seriously confused at what the fark could be going on!?
Anyone has any idea?
On Lee's rom forum, a poster told me to flash a RUU or WWE rom. But I don't really wanna do that for two reasons :
1. I'm not sure it will work since installing Lee's rom on a clean install didn't solve anything
2. I don't really wanna go through the hassle of rooting my phone again
Thanks!

Using an RUU is your best bet since no one knows wtf is going on. I would say to do that as well and I'm sure maybe a few others would. Yes, you would have to root again (not like it takes forever and not like you have to do anything other than plug your phone into your PC and run the unrevoked utility, seriously). That would be your best chance for fixing it. BTW, using an RUU would wipe everything out and start fresh so it probably would fix the issue.
If it doesn't... well, that's for another time.

u can try go into settings turn off senser
exit settings
then go back in settings again set the senser on again

I see more and more people having the deep sleep bug, rooted or not.
Wish I knew how to fix the damn thing! The only sure thing is that if the phone is at stock condition (rooted or not does not matter), it doesn't have the problem.
When I install some apps, it would start doing this!

Alright, I guess I don't have much choice then! I'll flash a ruu.
Thanks a lot fo your help guys

[Q] Constant Reboots...

Hello everyone. I have not been too particularly active here mainly because I have had no real reason to post. I give thanks when needed, but don't really post. Well, now I am having an issue that I genuinely cannot figure out. I recently dropped my phone and the digitizer cracked big-time. When I went to replace it, the connector for the ribbon cable broke. So instead of buying a new logic board, I just decided to buy a new Evo. However, I couldn't afford the approx. $600 for the "without a contract" price. So I went to a local Sprint dealer in my town and bought a factory refurbished Evo. Here is where the problems start.
I have been having reboots constant with this phone. I knew that there were some issues with the Evo randomly rebooting, but I have never seen something like this. It happens about every minute or so. Sometimes sooner. Sometimes I luck out and it doesn't reboot for a few hours. I notice that it does not reboot at all while it is in recovery, which is a great thing. I have tried multiple different ROMs and each one does it. I am completely out of ideas. I don't necessarily want to take it back, mainly because returning it to stock would be a pain. However, it is looking like I have to. Does anyone have any idea? It is obvious that it is not a bootloop, because I am able to actually get into the launcher. However, within a minute, it reboots. Can old radios cause it to reboot like this? It did this even with stock unrooted.
If any information is needed, please let me know. I really want to get this working without returning.
Thanks
StompySan
EDIT: It would seem that flashing my Nandroid backup of stock rooted seems to stop the rebooting issues. Could the ROMs I am installing be conflicting with the radios, causing it to reboot?

If I were you, without unrooting, I would flash the RUU for your phone. Then flash the pc36img for Amon Ra.
Before all that, I'd also back up your SD Card, then reformat it, so you are basically starting from scratch. A good idea, before you restore everything to your SD Card, but after you flash Amon Ra, is to partition it for EXT3. ( http://themikmik.com/showthread.php?5669-GUIDE-TUTORIAL-Apps2SD-Guide&highlight=partition+sdcard )
A lot of the ROMS now will take advantage of that. Once that's done, you can restore your SD Card backup to your phone.
Then I'd make a nandroid of that stock/rooted ROM, so you can always go back to it if you need to. When I nandroid, I backup everything except cache.
Figure out which ROM you want, put it on your card along with DT A2SD and the kernel you want to use. Make sure it's a kernel for the type of ROM you want, either AOSP or Sense. Personally, I keep the best rated kernel for each on mine.
Go to Wipe in Recovery and wipe everything, EVERYTHING, except the SD Card, then flash your ROM, and in the same recovery session, flash DT A2SD.
Let it boot up and let it settle in before you do anything. For me, that means once the screen shuts itself off.
Back to recovery, wipe Cache and Dalvik-Cache, then flash your kernel, reboot and let it settle in again.
THEN setup your Google accounts and preferences.
For me, I'd go back to recovery and nandroid that setup, before you've restored your apps, and make another nandroid, so you have one of your ROM's Base.
Then, reboot and see if the problem is fixed. If it is, restore your apps and see how it goes. If it starts rebooting, you know it's in your apps, so you can go back to the nandroid you made and start form there, installing a few apps at a time

Thanks for your reply HipKat.
I followed your tutorial step-by-step. However, after flashing A2SD and rebooting, it bootlooped (not like what I was getting, but an actual no boot logo bootloop). I am assuming that the ROM that I flashed didn't like the A2SD. So I restarted the tutorial, skipping the part where you flash the A2SD script. It seems like it is doing great now! I have no clue what I was doing wrong. I was using CWM. Maybe that was the problem. Could it have not been wiping it properly?
Thanks again for the quick response!

1.There are some roms that provides a CPU speed of 1.2G. With those roms and setcpu installed manually by myself, my evo rebooted just like yours. I don't know why, too.
But after I wipe everything(as HipKat said) and flash other rom, my evo 4g works just fine.
2. Before flashing new roms, wipe everything is absolutely required, otherwise strange problems will keep coming out.
What I comprehend is that flash roms on phone is like upgrading OS on your computer, you can't run windows7 with XP's configuration, right?

Hey HipKat, I've noticed that you advise people to wipe everything but the SD card in Amon Ra. You may want to note that wiping battery stats is only good if you have a full battery and plan on calibrating properly. If you wipe battery stats at 70%, your phone won't charge past 70% (thinking that it's full) unless you use an sbc kernel. Just something to keep in mind.
I'm not knocking your directions, you help a lot of people out. It's just something to think about.
Sent from my PC36100 using Tapatalk

plainjane said:
Hey HipKat, I've noticed that you advise people to wipe everything but the SD card in Amon Ra. You may want to note that wiping battery stats is only good if you have a full battery and plan on calibrating properly. If you wipe battery stats at 70%, your phone won't charge past 70% (thinking that it's full) unless you use an sbc kernel. Just something to keep in mind.
I'm not knocking your directions, you help a lot of people out. It's just something to think about.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
You're right! I keep overlooking that because I never flash unless I'm fully charged.
My mistake on those posts. Thanks!

I was still getting reboots after doing all of that. I thought it went away, but it didnt.
79x1 said:
1.There are some roms that provides a CPU speed of 1.2G. With those roms and setcpu installed manually by myself, my evo rebooted just like yours. I don't know why, too.
But after I wipe everything(as HipKat said) and flash other rom, my evo 4g works just fine.
Click to expand...
Click to collapse
This has to be it. I changed the speed to 1.15GHz in SetCPU and it has not done it since. Thanks!
EDIT: Well, it was OK, but it has started again. I have no clue why it is doing it again...

Maybe you should try some classic roms that don't require app2sd, like kings' kinged kingdom.
Before I partition my sd card, with shooter E3D and synerge, my evo also sometimes reboot, but not so frequently as yours.

And the CPU speed should be below 998MHz on my device (HW version:004)! Set your cpu frequency lower first, then try some other roms.

79x1 said:
And the CPU speed should be below 998MHz on my device (HW version:004)! Set your cpu frequency lower first, then try some other roms.
Click to expand...
Click to collapse
It doesn't matter what speed I set it to. I had it at 998 before and it still rebooted.
79x1 said:
Maybe you should try some classic roms that don't require app2sd, like kings' kinged kingdom.
Before I partition my sd card, with shooter E3D and synerge, my evo also sometimes reboot, but not so frequently as yours
Click to expand...
Click to collapse
I am going to flash Synergy real quick. I have already tried the following:
EVOlvedROM r3chargeD
Cyanogenmod
Are there any other ROMs I should try?
EDIT: I recorded a video of exactly what it is doing. I am currently encoding it. I will throw a YouTube link up soon.

Kings' Alliance is the steadiest rom i've ever used, without sense 3.0 though. If you don't mind you could try this:
http://forum.xda-developers.com/showthread.php?t=1180048

Here is the video of the rebooting problem. Sorry it is so long. It seems like the one time I want it to reboot it took forever for it to. lol.
79x1 said:
Kings' Alliance is the steadiest rom i've ever used, without sense 3.0 though. If you don't mind you could try this:
http://forum.xda-developers.com/show....php?t=1180048
Click to expand...
Click to collapse
I will try this ROM later tonight. I probably won't be able to reply tomorrow, because I have to work from 10AM to 10PM (I hate long days, lol), but will reply as soon as possible.

MIUI, for the win, man!

OK, I can pretty much confirm that it is a hardware problem. I have tried every ROM I can think of. It always seem to restart when it tries to turn on the Mobile access. If it is connected to WiFi, it will not reboot. The moment it is disconnected, it starts. However, I know it is not because of a bad radio flash. I have tried re-flashing the radios and it still doesn't work. I have restored it completely back to stock (while keeping S-Off, naturally) and it still does it. So, I am going to be returning it tomorrow. However, I have one real quick question. I know how to unroot, but I am not sure on how to achieve S-On with the Revolutionary root. Can you just flash the Unrevoked S-On zip with this root, or is there a different method? I wasn't able to find anything out on this.
Thanks again for all of your help. I really can't believe how quick people on here replied.

It isn't your hardware, I had a similar issue on my phone, it wouldn't go past the evo screen (for hours), I updated my firmware and it worked.
Clear caches, flash this rom (supersonic_4.24.651.1_odexed-signed2 google it), it will update your firmware, then flash the rom you want on top of it

stompysan said:
OK, I can pretty much confirm that it is a hardware problem. I have tried every ROM I can think of. It always seem to restart when it tries to turn on the Mobile access. If it is connected to WiFi, it will not reboot. The moment it is disconnected, it starts. However, I know it is not because of a bad radio flash. I have tried re-flashing the radios and it still doesn't work. I have restored it completely back to stock (while keeping S-Off, naturally) and it still does it. So, I am going to be returning it tomorrow. However, I have one real quick question. I know how to unroot, but I am not sure on how to achieve S-On with the Revolutionary root. Can you just flash the Unrevoked S-On zip with this root, or is there a different method? I wasn't able to find anything out on this.
Thanks again for all of your help. I really can't believe how quick people on here replied.
Click to expand...
Click to collapse
You can flash S-On.zip directly from the recovery, I suggest you try out the method I mentioned in the previous post, before you go doing something drastic.

prometh1us said:
It isn't your hardware, I had a similar issue on my phone, it wouldn't go past the evo screen (for hours), I updated my firmware and it worked.
Clear caches, flash this rom (supersonic_4.24.651.1_odexed-signed2 google it), it will update your firmware, then flash the rom you want on top of it
Click to expand...
Click to collapse
Nonono, it goes past the Evo screen. It goes past the standard boot logo. However, once you are in the lockscreen, and it tries to connect to 3G, it reboots. It is not a standard no boot logo bootloop.

stompysan said:
Nonono, it goes past the Evo screen. It goes past the standard boot logo. However, once you are in the lockscreen, and it tries to connect to 3G, it reboots. It is not a standard no boot logo bootloop.
Click to expand...
Click to collapse
If you're gonna trade it in, you don't need to unroot. Chances are no one will ever know, as long as you have a stock ROM on there.

HipKat said:
If you're gonna trade it in, you don't need to unroot. Chances are no one will ever know, as long as you have a stock ROM on there.
Click to expand...
Click to collapse
Yeah. That's what I was reading. Plus, I rooted with Revolutionary, which doesn't have a method to enable S-On.
Last night I flashed the latest stock ROM. As soon as it booted up and got to the lockscreen, it restarted. I can't see it not being a hardware problem. I am going to return it today. Hopefully they don't notice that it is S-Off. Any suggestions on what to say if they do?

same issue
i have an old evo that is doing the same thing, i flashed the original ruu and it still does it. i just reported it lost.

Stuck on lockscreen after reboot

On both Blazer (w/ rogue and Lost Kernel) and Calks 2.0 (only tried rogue) whenever I reboot my phone nine times out of ten, it hangs on the lockscreen with a random date and random time flashing back and forth between no signal and the regular status bar symbols. It is unresponsive to touch and repeats the process of the keys lighting up, screen comes on for about 4 seconds, keys turn off, screen turns off. Repeat... If I hit the power button, the pop up shows up but I can't touch anything so I end up having to do a battery pull and reflash the rom. I've re-downloaded both roms to rule out a bad copy. I over-wipe every time I flash a new rom formatting system, wiping data, cache, and dalvik, and then flashing Calk's format all.
I messed with it last night and it seems pretty random but more often than not, it happens. If I try to restore a nandroid I had made recently, it does the same thing. In other words, there were multiple instances where I flashed the rom, got it set up, booted to recovery to make a back up, and then it wouldn't boot back up NOR could I get my back up to boot up.
What in the hell could be causing this??? Please and 1000 thank you's!!!!

First of all, sorry to tell you I don't have the answer.
I have this exact same issue and have tried almost everything you have tried, (I didnt have a back up since I just got this phone not too long ago).
My issue started at work when my battery died really fast in the middle of the day after being fully charged. The phone got hot and I just pulled the battery to stop it. Then I came home and am having this exact same issues.
I've spent the last few hours working on resolving this without success. Hopefully someone out there knows how to resolve this issue.
Edit: I am on Rogue recovery 1.10 (cmw v 5.6.2.7) and on Blazer ROM [11/26/11] [v1.2]
Might be the rom since we are both on Blazer...Im gonna try another. Hmm we are on the same recovery too!
Thanks!

Why not flash back to stock and start over?
Sent from the future.

FIXED!!
I've got it working finally. For me, I just had to check Go Launcher as my default launcher. Now when I reboot, it loads up just fine. I guess it was hanging when it tried to open up the pop-up where you select your launcher if you have more than one and don't have one set as default. So, to the few people affected by this, set your favorite launcher as default and give it a try. Thank you to everyone for all of the suggestions.

VegasEvo4G said:
I've got it working finally. For me, I just had to check Go Launcher as my default launcher. Now when I reboot, it loads up just fine. I guess it was hanging when it tried to open up the pop-up where you select your launcher if you have more than one and don't have one set as default. So, to the few people affected by this, set your favorite launcher as default and give it a try. Thank you to everyone for all of the suggestions.
Click to expand...
Click to collapse
Yes this has been an ongoing issue and posted in a few places. Also remember that when Go Launcher updates this may happen to you again. You can always use adb and push a launcher over to your phone incase you find yourself stuck like this again. Or delete launchers so there is only 1 choice

I finally got rid of this loop. I was able to flash a rom via the recovery menu in clockworkmod, since for some strange reason it won't recognize my sd card now.
Playya, so if I wanted to push a recovery on my phone (I have clockworkmod v. 4.015 installed but it won't recognize the sd card no matter what I do to it), can I do this from Root Explorer? ADB? What commands would I use? I am on Linux and am looking for a guide. Thanks.