[Q] Phone boots after ROM install, but has no launcher, etc - HTC Butterfly

Hello, all. I've been playing around with my X920D and I've tried installing InsertCoin 3.0.6, but after the installation completes and the phone boots, I get stuck on a screen with what appears to be a default wallpaper and nothing else. If I slide down from the top of the screen, I can make the notification bar appear temporarily, but it goes away again after about a few seconds. There is no launcher, there are no icons, and it the phone's language seems that it is set to Japanese (or possibly Chinese, I'm not really sure). If I press the lock button, I can get to the lock screen and it displays a clock, some more text in I guess what is Japanese, and I can swipe to unlock and go back to the empty desktop. I can also change the volume, take screenshots, and connect the device to my computer (which recognizes it as an HTC Butterfly) and look around through the internal storage, but I'm kind of stuck if I want to do anything beyond that.
I've installed TWRP 2.7.0 with SELinux support, the bootloader is unlocked, and the phone does not have S-OFF. I'm really puzzled, because I'm able to flash a boot image with fastboot, I can install a ROM and the installation completes and the phone boots, but it doesn't seem that the OS has any functionality at all. I've also tried this with the NOS ROM, and I ended up with a black screen and a notification bar, pretty much exactly the same situation as what is happening with the InsertCoin ROM. I've looked through several threads here, I've seen a few instances of people having this issue, but I've not seen a solution for it. I've wondered if I might need to flash a new kernel, but I'm not entirely sure if that would solve the problem. Anyhow, if someone is able to provide assistance or knows anything about this issue, I'd be very appreciative.
EDIT: I've been doing some more digging, it seems that I don't actually have an X920d despite the back of my phone having "X920d" under the volume speaker (my phone has red capacative buttons and there was a European charger in the box when I went looking back through it for other clues). The ROMs I've tried were for the X920d, so I suppose that is the reason that they aren't working on my phone and why I'm encountering these weird problems. I'll see if I can locate a ROM for the X920e and try that out, but it doesn't seem like there is a version of InsertCoin for the X920e If everything goes well, I'll update here in case anyone else has this same problem.
EDIT 2: I was able to download a what looks like a stock Chinese ROM for the X920e and install it, everything went fine and my phone seems to be working now. I've still been unsuccessful in finding any other more custom ROM, but I guess this will do for now. If anyone happens to be reading and could point me in the direction of a cool ROM for the X920e, I'd be grateful

Related

Display / menus freezing and / or disappearing, system apps force closing

I've been searching this form for an hour or two now and still haven't found my issue, so here goes.
Just got an HTC Inspire 4G off of ebay and it arrived today.
The seller had mentioned that the phone was freezing / rebooting, but I figured.. that's because he's not running cm7, right?
Charged and booted up the phone and it turns out that the problem was a little worse than I first expected. I only experienced occasional freezing, and it only rebooted once, but there is a worse problem.
The phone loaded up fine, looked good, but tapping around on the home screen I got messages alerting me that system apps (htc sense, launcher, and even com.android.phone) had stopped responding or had shut down.
I hit the menu and go to settings. I scroll down the list and the entire list goes black. I hit home and it goes to a home screen, but with no launcher or icons. Basically, every few taps, the interface goes out. If you are on a menu it blacks out, if you are at home or press home after the menu blacks out you will get anywhere from pieces of icons / widgets to just a blank desktop. The live wallpaper even keeps going, but all of the interactive stuff quits. The disappearing menus didn't usually give app closed messages, they just went black. The home screen only gave app closed messages sometimes.
I thought this was a software problem, so I managed to root the phone and flash cm7. Everything booted good, but it still had the same problem of weird disappearing menus and home interfaces. I went ahead and flashed gapps and got the little intro thing about setting up my Inspire 4g that starts when you first boot your phone. I clicked through that but when it gets to connect wifi, the phone entirely freezes and I have to pull the battery.
I flashed inspiremod and nothing changed, tho that's for something else, so I'm not sure that's entirely relevant, but I was trying everything I could think of.
I'm definitely no expert on hardware, but it almost sounds like a ram problem, like it doesn't have enough to keep all of the interface going all the time and shuts it down or shuts parts of it down to work.. but I don't want to believe that. I'm really hoping that it's a software problem.
I got the phone at a good price and it came with an otterbox, so I won't be too disappointed if I can't get it fully functional, but it would still be a bummer.
Any help / advice / suggestions appreciated. Thanks, guys!
EDIT: I cleared the cache / dalvik cache before flashing / reflashing cm7, which I did once or twice
EDIT 2: Now if I leave it on the intro screen where it freezes it reboots after a minute or so. Gonna try flashing a different mod.. see if that helps.
That was a long post. But it was good, you gave a lot of info.
The cm7 zip that you downloaded, check the md5 checksum, make sureit matches whatever is in the op (first page) or wherever the md5 is, maybe where you downloaded it from. If it doesn't, download again.
Then,
from recovery,
Wipe data/factory reset.
Wipe dalvik
Format all partitions(except sd card)
Flash zip/rom.
Check if it works. If not, try using it without the sd card. If not, come back and report.
Sent from a dream.
Thanks for the reply and suggestions.
I check the md5, and it's good. I just did a factory reset and wiped cache and dalvik.. I'm unsure what you mean by format all partitions except sd card. I don't think I know how to do this with clockworkmod.
Started up without sd card and it still has the same problem. Looks great until I touch the screen, then everything disappears except the wallpaper.
Reboot in recovery and do it from there. You'll find format all partitions at the bottom... well, maybe. Cwm has an option to reboot in recovery, and I think if you press and hold the power button, select reboot and it will also ask you if you wantto boot into recovery. Cant remember if cm7 has it, it should.
After you wiped those, flash the rom. Stay in recovery and search for fix.permissions. Reboot.
Sent from a dream.
Just did that and re-flashed cm7, but the phone was still having the same problems.
I then repeated the process with a MIUI ICS rom and it seemingly worked for a little bit. I got a "Maps has stopped working" message, but I was able to slide back and forth through the home screens, and the menu came up. After I tapped though the menu a bit it started being weird again, but with MIUI the weirdness is different. It looked like the screen was divided up into 20 something smaller screens tiled across the display with messed up looking bits of screen in them.. weird..
If you are wiping correctly then I am out of ideas. I would say try a GB rom, however that is a strange issue and just might be a hardware problem. Tough, Im not sure.
Sent from a dream.
I've tried cm7, which is 2.3, and I've tried a 4.0.4 MIUI build and one other sense rom that didn't work well at all.
I'm wiping and flashing the same as I did on my LG p509, which works beautifully with cm7.
If it is hardware, hopefully it's something simple like the battery, and not bad RAM or anything serious..
Maybe if I keep at it I'll get it.
Thanks for all the suggestions!
Np. Keep us updated.
Sent from a dream.
I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!
awkwardcheesecake said:
I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!
Click to expand...
Click to collapse
Have you tried changing out the sd card? Having a bad sd card can cause all inds of odd issues
I booted it without an sd card before and couldn't tell the difference, but it had a lot more issues than just freezing then.
I haven't tried it since those other issues have stopped. I'll try that when I get home from work.

Reoccurring Dead Spots on Screen?

Hello community of XDA, I was hoping you could help me with an issue I'm experiencing with my HTC One S. Sometimes when I unlock the phone to respond to a text message or do anything really (it's just most noticeable on the keyboard) there will be a dead spot on the screen. The pixels work but none of my touches register. The spots where this happens are not always the same but the same spots will pop back up from time to time. An example of what happens is I unlock the phone, pull up the keyboard, and try to type out a message but some of the keys won't respond to a touch or will just register the key next to it. The odd thing about this is, I'll relock the phone, unlock it again, and that dead spot will be fully functional again. It's never the same spot twice and I know it's not the keyboard because this occurs if I am on the home screen trying to swipe pages or scrolling through the browser. I have not attempted fully wiping and restoring the device because I do not have a sufficient internet connection to re-setup (if you will) all my settings, and I do not want to use Titanium Backup or another backup app because the problem may be something hidden in all those files. Has this happened to anyone else/does anyone know what I can do to solve my problem? Feedback and help is greatly appreciated because the warranty was void after the phone had been unlocked through HTCDev.com. I am currently running xkonni's latest CM9 build (from the 31st if I remember correctly). Thank you very much I appreciate it.
mdskrzypczyk said:
Hello community of XDA, I was hoping you could help me with an issue I'm experiencing with my HTC One S. Sometimes when I unlock the phone to respond to a text message or do anything really (it's just most noticeable on the keyboard) there will be a dead spot on the screen. The pixels work but none of my touches register. The spots where this happens are not always the same but the same spots will pop back up from time to time. An example of what happens is I unlock the phone, pull up the keyboard, and try to type out a message but some of the keys won't respond to a touch or will just register the key next to it. The odd thing about this is, I'll relock the phone, unlock it again, and that dead spot will be fully functional again. It's never the same spot twice and I know it's not the keyboard because this occurs if I am on the home screen trying to swipe pages or scrolling through the browser. I have not attempted fully wiping and restoring the device because I do not have a sufficient internet connection to re-setup (if you will) all my settings, and I do not want to use Titanium Backup or another backup app because the problem may be something hidden in all those files. Has this happened to anyone else/does anyone know what I can do to solve my problem? Feedback and help is greatly appreciated because the warranty was void after the phone had been unlocked through HTCDev.com. I am currently running xkonni's latest CM9 build (from the 31st if I remember correctly). Thank you very much I appreciate it.
Click to expand...
Click to collapse
I have never heard of something like this happening, seems like youve got a unique problem my good friend
The best thing to do would be to restore to your stock RUU and relock the bootloader and send it back to HTC. Many peope report that they have relocked their bootloader and HTC has still replaced or repaired their phone
Now I understand your hesitation doing this, so in my opinion the only other thing you could do is a stock wipe. Unfortunately i cant help you with your internet speed, but really its all you can do. The easiest way to get completely back to stock is to follow this guide:
http://www.htconeforum.com/forum/htc-one-s-hacks/389-how-unbrick-restore-your-htc-one-s-back-100-stock-relocked.html
If you have already tried flashing new roms and the issue persists, then it is most defiantly a problem that only HTC can fix, sorry to say
happy troubleshooting!
:EDIT:
I FORGOT SOMETHING
The easiest way to find out if this is in your system or your apps is to do a factory reset
Go into recovery, make a backup, wipe DATA and CACHE and reboot. Your phone should be stock cm9 now, check if the issue exists
If it doesnt, its your apps
If it does, you still need to try flashing a new rom or going back to stock with the RUU

deleted lockscreen, oops!

being a noob to Android after years of BlackBerry, but LOVING the Android freedom, I rooted my HTC Sensation 4G (not all that easily, I might add). In trying to remove bloatware, I deleted the stock Android default lockscreen, thinking that it was superfluous since T-Mobile/HTC had included the HTC lockscreen. What I failed to realize was that apparently the HTC one works on top of the default one (I even "quarantined" the deleted one before fully removing, and it still functioned fine, but must have been from cache or something because it no longer did after reboot). So, now no lockscreen comes up at all, no ring tab to pull, just a blank screen of wallpaper, effectively meaning I've bricked my phone. I'm hoping that I can do some kind of restore, perhaps an apk I could load from my PC onto my phone's SD card, or alternatively have some kind of recovery whereby I don't lose everything, programs and data such as contacts. I do have a Clockwork backup on the SD from a month or so ago, and can get my HBOOT menu offering me both factory reset and Recovery options, but not sure what I might lose doing either of those. Still learning Android, not even sure of terms like SuperCID and ICS, though reading much as I can to learn. I am looking for suggestions as to how I might recover just my lockscreen, or failing that, the best path to recovery after some sort of restoration. Have never yet flashed a ROM or done anything with firmware, but maybe this is the time since I may have nothing to lose, in a sense, don't know about either of those processes but want to learn and do.
reply to myself
OK, seeing as nobody came to my info rescue, I'll post to myself in case it helps somebody in the future. Finally just got brave enough to push some buttons, and came out smelling like a rose. Did the HBoot via power button together with down volume after battery pull, chose Recovery, then Advanced, and then chose to just recover the System only from the one available recovery. Worked like a charm. Phone no longer rooted, but I'm going to try the OTA of ICS anyway and eventually re-root after that. Know I will have to flash stock recovery to replace the CWM (Clockwork) one that allowed me this recovery, as OTA ICS requires stock recovery, but that doesn't sound like a problem.

[Q] Can't unlock phone touch screen not responding

My phone is rooted and I have Jelly 'beans' ROM installed. Everything was going well (been running for a week) until I installed ActiveNotifications (https://play.google.com/store/apps/details?id=com.greatbytes.activenotifications). I'm not stuck on my lock screen and the touch screen does not respond to unlock it. There is also a hand icon in the status bar that I've never seen before. I can't (as far as I know) use adb to uninstall because the phone is not in USB debugging.
Any thoughts short of wiping and re-installing the ROM?
TIA
ffeingol said:
My phone is rooted and I have Jelly 'beans' ROM installed. Everything was going well (been running for a week) until I installed ActiveNotifications (https://play.google.com/store/apps/details?id=com.greatbytes.activenotifications). I'm not stuck on my lock screen and the touch screen does not respond to unlock it. There is also a hand icon in the status bar that I've never seen before. I can't (as far as I know) use adb to uninstall because the phone is not in USB debugging.
Any thoughts short of wiping and re-installing the ROM?
TIA
Click to expand...
Click to collapse
Yeah, neat app huh? I did the same thing myself. I think to use it you have to have a PIN unlock. Anyway, if you can pull down your notification shade, go into settings and uninstall it. Also if you have no security set for your lock screen, try to call your phone or send a text, something that will immediately get you into the main UI, then uninstall it.
Power it off the press at the same time power>home>vol up and boot into recovery and reflash the rom..
Sent from the future via Tapatalk 4
ffeingol said:
My phone is rooted and I have Jelly 'beans' ROM installed. Everything was going well (been running for a week) until I installed ActiveNotifications (https://play.google.com/store/apps/details?id=com.greatbytes.activenotifications). I'm not stuck on my lock screen and the touch screen does not respond to unlock it. There is also a hand icon in the status bar that I've never seen before. I can't (as far as I know) use adb to uninstall because the phone is not in USB debugging.
Any thoughts short of wiping and re-installing the ROM?
TIA
Click to expand...
Click to collapse
Maybe consider restoring from your most recent nandroid? I know that it's losing some progress, but you might be able to save yourself some time. Short of that, I think you'll need to re-flash your ROM, unfortunately.
I've been in situations like this one before, and that's the big reason why I've made it my standard operating procedure to maintain two backups: one for pre-flash and on stable post-flash for every new ROM. It's been helpful so far (in the extremely limited experience I have with custom software on my phone).
I'm going to wait just a bit to see if anyone else has some great suggestion, but I think I'll have to re-flash (after I finally got my home screen the way I want it). I do have PIN lock on. Can't pull the notifications down. With the ROM I'm using the AOSP lockscreen and I when you touch the circle to unlock none of the icons show.
Not a happy camper
ffeingol said:
I'm going to wait just a bit to see if anyone else has some great suggestion, but I think I'll have to re-flash (after I finally got my home screen the way I want it). I do have PIN lock on. Can't pull the notifications down. With the ROM I'm using the AOSP lockscreen and I when you touch the circle to unlock none of the icons show.
Not a happy camper
Click to expand...
Click to collapse
Try to hit the menu button while you're on the lockscreen, sometimes that'll bypass the lock screen.
Sent from my SCH-I535 using Tapatalk 2
After wiping and re-installing the ROM (several times) I think I may have found the culprit. My phone suddenly thinks that my 32 GB external SD card is bad and is stuck in a fsck. If I put the card out everything is happy. Time to backup the sdcard and reformat.

Display stops working, mostly, on second boot after installing non-stock.

I've got an odd problem with my p900. If I install any lollipop ASOP ROMs, the first time I reboot after initial install, the display mostly stops working. The first boot works fine, I go through the setup wizard, set everything up, and the tablet works and displays fine as long as I don't reboot.
Specifically, what will happen if I reboot is that the tablet will go through the normal boot, and get to the point when the wallpaper and status bar will come up, but no homescreen icons or anything. Then after a while, about 2-5 minutes, the display will go black except for the status bar. I can pull down the notifications drawer from the status bar, and it will display, as will the quick settings, but anything I tap to try to interact with will seemingly just do nothing. If I have 'show touches' on, then touches will display properly, anywhere on the screen, but they seem to do nothing. I've tried trebuchet, google now, and adwex, the home app doesn't seem to make a difference.
The problem first began in I want to say october, when I flashed a CM12 nightly update. I unfortunately no longer remember which nightly I was on nor which I flashed to. I of course immedately tried to flash back to the previous nightly when I discovered the problem, but it did no good. It took me a while to figure out the pattern to the problem after it first occurred, as I often don't reboot the device for a long while after a first install. I don't have a lot of spare time to devote to sitting down and just focusing on trying different things, so it wasn't until president's day weekend that I tried what I *thought* would fix it, ODINing back to stock and installing the latest CM12.1. Clearly that didn't work, or I wouldn't be posting.
I've tried the 20151104, 1029, 1006, and 0910 CM12.1s from http://forum.xda-developers.com/gal...nt/rom-cyanogenmod-12-lollipop-5-0-1-t2971945. I've also tried Civz lollipop, pacman, and resurection remix. Anything not stock based has the problem. I tried running stock, but I've been running CM since G1 days, and I just can't stand stock, even the stripped down and modded versions. It just doesn't work right, and I can't get used to it, even after forcing myself to use it for several days.
I've never encountered such a weird problem, and I can't seem to find anyone else having a similar problem. I have no idea how to troubleshoot this beyond what I've done already. I'm currently running thompatry's Cm12.1 20160212, having not rebooted after the initial install, and it's running mostly ok, but I live in dread of my battery dying, and of course I can't install any xposed modules like xprivacy or multiwindow, which is bothersome. I have the wifi only US model, v1awifi, and I'm currently running TWRP 3, tho I was on TWRP 2.8.something when the issues first started happening.
what's the last 3 characters of your bootloader version?
heldc said:
I've got an odd problem with my p900. If I install any lollipop ASOP ROMs, the first time I reboot after initial install, the display mostly stops working. The first boot works fine, I go through the setup wizard, set everything up, and the tablet works and displays fine as long as I don't reboot.
Specifically, what will happen if I reboot is that the tablet will go through the normal boot, and get to the point when the wallpaper and status bar will come up, but no homescreen icons or anything. Then after a while, about 2-5 minutes, the display will go black except for the status bar. I can pull down the notifications drawer from the status bar, and it will display, as will the quick settings, but anything I tap to try to interact with will seemingly just do nothing. If I have 'show touches' on, then touches will display properly, anywhere on the screen, but they seem to do nothing. I've tried trebuchet, google now, and adwex, the home app doesn't seem to make a difference.
The problem first began in I want to say october, when I flashed a CM12 nightly update. I unfortunately no longer remember which nightly I was on nor which I flashed to. I of course immedately tried to flash back to the previous nightly when I discovered the problem, but it did no good. It took me a while to figure out the pattern to the problem after it first occurred, as I often don't reboot the device for a long while after a first install. I don't have a lot of spare time to devote to sitting down and just focusing on trying different things, so it wasn't until president's day weekend that I tried what I *thought* would fix it, ODINing back to stock and installing the latest CM12.1. Clearly that didn't work, or I wouldn't be posting.
I've tried the 20151104, 1029, 1006, and 0910 CM12.1s from http://forum.xda-developers.com/gal...nt/rom-cyanogenmod-12-lollipop-5-0-1-t2971945. I've also tried Civz lollipop, pacman, and resurection remix. Anything not stock based has the problem. I tried running stock, but I've been running CM since G1 days, and I just can't stand stock, even the stripped down and modded versions. It just doesn't work right, and I can't get used to it, even after forcing myself to use it for several days.
I've never encountered such a weird problem, and I can't seem to find anyone else having a similar problem. I have no idea how to troubleshoot this beyond what I've done already. I'm currently running thompatry's Cm12.1 20160212, having not rebooted after the initial install, and it's running mostly ok, but I live in dread of my battery dying, and of course I can't install any xposed modules like xprivacy or multiwindow, which is bothersome. I have the wifi only US model, v1awifi, and I'm currently running TWRP 3, tho I was on TWRP 2.8.something when the issues first started happening.
Click to expand...
Click to collapse
Have you tried changing kernel? I mean in the case of civz lollipop rom you do get an option of 2 different kernels try choosing the opposite to the one you had chosen before. Thank you, hope it helps.
I won a year ago 2 Note Pro, one works flawlessly while the other is slow af and it has the same issue that you speak about. If I stay on stock everything is good more or less (sometime little slow), but if I install Lineage or any other Custom Rom is too slow and has the same issue you speak.
I changed both batteries, but nothing to do. If anyone knows, text please.
Thank you!

Categories

Resources