On the first boot after unlock I couldn't expand my notification bar. It only showed the clock and was unresponsive. A reboot fixed it. Anyone else see this?
I used the UnLock_Device_App_V7.apk and had no other issues. Worked fine on an updated 4.1.1. Just installed, opened and agreed to the terms. Boot up shows unlocked in the UL corner. One step closer to root. Perhaps after a nap.
You can't know your limits until you exceed them.
I had this bug as well at a random boot.
I'm not unlocked though.
It happened to me twice... I cannot tell why.
I was already unlocked but I'm not sure it has anything to do with it.
duckredbeard said:
On the first boot after unlock I couldn't expand my notification bar. It only showed the clock and was unresponsive. A reboot fixed it. Anyone else see this?
I used the UnLock_Device_App_V7.apk and had no other issues. Worked fine on an updated 4.1.1. Just installed, opened and agreed to the terms. Boot up shows unlocked in the UL corner. One step closer to root. Perhaps after a nap.
You can't know your limits until you exceed them.
Click to expand...
Click to collapse
Have you considered a reboot, if not working a cold boot, if stills not working a factory reset!!
Related
My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
bsander said:
My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
Click to expand...
Click to collapse
Are you doing Apps to SD? It could be your card.
Did you move any caches?
Do you have any nandroid backups? (just fastboot flash if so)
Did you recently try to update to anything and fail?
Try to use the update.zip again. If that doesn't work then start over from scrap.
bsander said:
My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
Click to expand...
Click to collapse
Wipe worked for me. It was sticking on the Android flash screen, but worked after the wipe.
Yeah, a wipe fixes it. Later today I stumbled upon a thread which suggested the problem is the "Contact Owner" app that doesn't play nice. Can anyone confirm that?
In answer to binary: yeah I do apps on SD but I've been doing that since ADP1.1, so I doubt the card is the problem. Didn't move any caches. Yeah I have a nandroid backup, and all the updates I did went smoothly. I had the whole system working for about 2 days until this happened (probably, because this was the first time I rebooted since installing Contact Owner, though I can't really remember that 100%)
bsander said:
Yeah, a wipe fixes it. Later today I stumbled upon a thread which suggested the problem is the "Contact Owner" app that doesn't play nice. Can anyone confirm that?
Click to expand...
Click to collapse
Contact Owner caused my phone to go into a reboot loop, but that was on the 5.02H build. I haven't had the guts to try it on JF1.5 or 1.5Hr3. If you look through the market comments for Contact Owner you'll see quite a few complaints of the same issue.
Hi there,
And sorry for reviving this old thread. I am the developer of Contact Owner an I kinda need your help in debugging this issue. I got a small number of messages from users of custom builds a while ago (about a month or two) but thought it was an issue with those builds.
Now it came back to bite me in the ass, as it seems the HTC builds in various countries (Canada, Sweden, South Africa) have the same issue: the phone goes into a reboot loop. I've tried (and failed) to install a custom build on my dev phone (almost bricked it) so I'm going to ask nicely if someone is willing to debug the issue for me. Please, please, please!
All that's needed is to install and run Contact Owner and if the device goes into a reboot loop, simply attach it to USB, run 'adb logcat' and then post the output. To recover from the reboot loop, simply start in 'safe mode' (hold Menu down while booting) and then uninstall Contact Owner.
I suspect the problem lies in SQLite, because I've seen similar complaints from Klaxon users and that app also sets the alarm message (which then ends up in a SQLite db, I guess). The Alarm Clock app that comes with Android also does that but I imagine it's because the message set by Alarm Clock is always short and has no newlines. I also don't think the issue is in Dalvik code, because the device should not crash if managed code causes an error.
TIA,
Paranoid Android.
Hello...
I'm a newbie to modding phones (obvious from the question/problem I've about to ask). I have an HTC Inspire and I followed the one click rooting guide and installed Coredroid7 with the 3rd set of radio/RIL listed in that thread. With a bit of a struggle I got it working - worked great and I loved it. Unfortunately I found on the market place an app (Overclock Widget by Billy Cui ) - clicked on "load on boot" and a few bad settings and the entire phone froze. Since then whenever I boot my phone is stuck on the white screen with green HTC logo. The config on my phone is:
s-off
hboot 0.85.0019
micop-0438
radio 26.09.04.11_m2
emmc boot
I've googled all of the internet and followed advice such as reflashing the radio/RIL. went into recover and typed the "adb shell, etc... to remove files indicated (but they were not there)". tried to do recover but the recovery files werent there. At this state, there is only so many combinations you can do and I feel I have done it all.
there are a lot of advice on set cpu problem with other HTC devices but none of them work/can be applied to the Inspire.
Can someone please help me? In your answer please answer me in a dumb down way - keeping in mind I am new and have a hard time understanding acroynms and how to perform complex operations with the hint of a word phrase (ie - please be explicit for me on how to flash radio, instead of saying flash radio XYZ)
Thanks in advance
PS: I am already nervous/scared of what has happened, I am hoping I don't have to do a eng s-off as part of the solution please
based on my description (white screen with HTC logo) have i bricked my phone or is it in a boot loop?
i tried the following
http://forum.xda-developers.com/showthread.php?t=1033353
and when i say install PD98IMG.zip it just says installation aborted. This is the image I got from Coredroid7 that was working before the problem started.
also tried this:
http://forum.androidcentral.com/lg-...cks/50301-setcpu-forgot-uncheck-set-boot.html
but my phone does not have the file they wanted me to delete
If you see the white HTC logo your always okay. The problem comes when there is nothing showing, you must have changed some settings that won't let the phone complete some core processes.
This can easily be fixed by pulling battery hold volume down button and power and booting into Hboot. Then go into recovery factory reset and wipe dalvik_cache(under advanced) and flash the desired ROM or do a restore from a point your phone worked perfectly.
Sent from my Inspire 4G using XDA Premium App
ThEiiNoCeNT said:
If you see the white HTC logo your always okay. The problem comes when there is nothing showing, you must have changed some settings that won't let the phone complete some core processes.
This can easily be fixed by pulling battery hold volume down button and power and booting into Hboot. Then go into recovery factory reset and wipe dalvik_cache(under advanced) and flash the desired ROM or do a restore from a point your phone worked perfectly.
Sent from my Inspire 4G using XDA Premium App
Click to expand...
Click to collapse
First... THANK YOU very very much for telling me it is not as bad as it seems.
I have done the following:
go into hboot
recovery option
wipe dalvik
flash coredroid7 again by having it be embedded in PD98IMG.zip however like mentioned above this fails.
Right now I am redoing the process again by formatting my sdcard, creating /download to put the PD98IMG.zip in follow the procedures again above. In case this fails, what are my options?
thanks for the guidance. i flashed it again with:
CoreDroid_Desire_HD_GB_2.3.3_V7.0_RV
and I am out of the white screen mode.
Just remember if your phone boots up but not all the way its still ok you can save it. The easiest although most annoying solution is reflash the rom. Also i know you hear about people bricking there phone. I truly think its harder than anyone thinks. Good luck with the inspire. Also if you want overclocking/underclocking stick with setcpu(you can get it free for being an xda member just search xda). Let it auto detect speeds. Give it root permission (itll pop up asking make sure you check remember above the allow button). If your overclocking I recommend staying undler 1.6 ghz (1600 on setcpu) and go to profile select enable. Then set up a profile for screen off and set it for around 300 mhz to help with battery life.
Carlrobling said:
Just remember if your phone boots up but not all the way its still ok you can save it. The easiest although most annoying solution is reflash the rom. Also i know you hear about people bricking there phone. I truly think its harder than anyone thinks. Good luck with the inspire. Also if you want overclocking/underclocking stick with setcpu(you can get it free for being an xda member just search xda). Let it auto detect speeds. Give it root permission (itll pop up asking make sure you check remember above the allow button). If your overclocking I recommend staying undler 1.6 ghz (1600 on setcpu) and go to profile select enable. Then set up a profile for screen off and set it for around 300 mhz to help with battery life.
Click to expand...
Click to collapse
I think I've had about every kind of soft boot thre is on the sticky guide, and one that isn't, and I have always been able to recover (knock on wood). Even black screens...
I was stuck in a similar situation once:I forgot to take off "load on boot" and increased the max speed all the way to like 1.9. And phone froze.
SetCPU gets permissions in the process of phone boot up, after the whole OS is loaded. There is a tiny time gap between home screen coming up, and SetCPU being granted SU permissions. So this is what I did:
I did a reboot. And after the phone starts, without giving any time opened the app drawer for "SuperUser" app, and took off SetCPU permissions from there. This denied SetCPU of it permissions and it was loaded at default speeds. Then I went into Settings-->Applications, and erased all SetCPU data.
Well, it took me like 3-4 reboots before I could master the timing to get to SuperUser and take off SetCPU from there. But it atleast saved me the hazzle of reflashing everything again. And yes sir, I forgot to take a nandroid backup
thanks
Thanks All
Problem fixed
same issue only worse
I have the same situation. I flashed absolution 2.0 last night. Everything went good. Turned it on this morning seemed to work fine also then I turned it off for work and tried turning it back on at the end of the day and it just runs a loop. I can get to the HBOOT menu but I only have 5 options; fastboot, recovery, factory reset, sim lock, and image crc. There is no advance settings and when I choose any of the available options nothing happens except the phone reboots (crc does run a check but then nothing). Hooked to my pc and it says found android 1.0 but I can't do anything with it. I have also pulled the battery and sims card.
freedompc said:
I have the same situation. I flashed absolution 2.0 last night. Everything went good. Turned it on this morning seemed to work fine also then I turned it off for work and tried turning it back on at the end of the day and it just runs a loop. I can get to the HBOOT menu but I only have 5 options; fastboot, recovery, factory reset, sim lock, and image crc. There is no advance settings and when I choose any of the available options nothing happens except the phone reboots (crc does run a check but then nothing). Hooked to my pc and it says found android 1.0 but I can't do anything with it. I have also pulled the battery and sims card.
Click to expand...
Click to collapse
What happens when you select recovery and press power?
It just turns off and starts back up and runs its loop. Same for fastboot and factory reboot.
Go here, I've already informed attn1 and his group that you'd be coming.
Going to the link.
They'll get ya fixed up.
Thanks TX. Those guys on that site were awesome. Attn1 worked with me for over an hour. Unfortunately, my phone itself has a hardware failure. Never the less, GREAT support. I wish there was a thank you button for them. This was my first android phone (lasted 3 months) and b/c of the DEV's and other members it won't be my last. Just hope the next one lasts longer.
freedompc said:
Thanks TX. Those guys on that site were awesome. Attn1 worked with me for over an hour. Unfortunately, my phone itself has a hardware failure. Never the less, GREAT support. I wish there was a thank you button for them. This was my first android phone (lasted 3 months) and b/c of the DEV's and other members it won't be my last. Just hope the next one lasts longer.
Click to expand...
Click to collapse
Dang man, that sucks. I can honestly say I've never had a device fail like that.
Good luck on your next device, whatever it may be.
Tx
Disregard... posted in error
sent from my secret agent phone in my shoe
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.
Sometimes I unlock my phone and the screen remains black, then the phone reboots but weirdly it doesn't ask for the SIM pin number. Other times I notice the phone reboots by itself and I notice it because obviously the screen lights up during the boot animation. This happens very rarely, so far it has happened about 3 to 5 times in a couple of months but it's still mega annoying when it happens.
Does it happen only to me? Is there any way to troubleshoot this issue?
MarkMRL said:
Sometimes I unlock my phone and the screen remains black, then the phone reboots but weirdly it doesn't ask for the SIM pin number. Other times I notice the phone reboots by itself and I notice it because obviously the screen lights up during the boot animation. This happens very rarely, so far it has happened about 3 to 5 times in a couple of months but it's still mega annoying when it happens.
Does it happen only to me? Is there any way to troubleshoot this issue?
Click to expand...
Click to collapse
If you provide some logs then maybe someone can see what is happening....
Or even basic information, like the configuration and setup of your device.
Right, forgot my configuration. I have an unbranded Z3 on latest Lollipop (but I recall I had a reboot also on Kitkat), no root, no weird apps like task killers or antivirus or anything like that. Sometimes it just does a reboot by itself, but doesn't ask for pin number so it's not a full reboot.
How do I provide logs again?
Info
MarkMRL said:
Right, forgot my configuration. I have an unbranded Z3 on latest Lollipop (but I recall I had a reboot also on Kitkat), no root, no weird apps like task killers or antivirus or anything like that. Sometimes it just does a reboot by itself, but doesn't ask for pin number so it's not a full reboot.
How do I provide logs again?
Click to expand...
Click to collapse
Factory Reset can solve ur problem /based on personal experience
I did that already less than two months ago and I refuse to believe I have to factory reset this thing every month to get stable operation. Also I'm not even rooted and I haven't messed with the system itself so why would I need to factory reset? Factory reset implies that there is something that has changed and needs to be re-set, and I haven't changed anything special that would require such a drastic solution. Not having done anything special, the issue would come back sooner or later if I don't spot the real cause.
Anyway, in diagnostics I have 21 application incidents for systemUI... Could it be caused by a bugged theme? Does this happen to anyone else?
Today I had two and I had another one last week. A off these were weird half reboots like I described above. I only noticed one because I was at my desk and the phone lighted up for the boot animation.
These reboots show up in diagnostics (phone info menu) as system events. Can you please check out if you have any system events and post here? I want to know if this is a widespread problem. Post here if you have any and also if you have a solution or way to troubleshoot.
Nobody at all? Really?
Just flashed latest (230405.003.E1)
and noticed I have to unlock my screen manually even when I'm at home.
So I checked my smart lock settings, and it was blank!
I factory reset, and it was fine last night, woke up today and it was blank again.
Anyone else on the latest build experience this?
I did an OTA update to the exact same Android version on my AT&T Pixel 7 Pro. My Smart Lock settings are still there. No issues here.
I updated as well and mine isn't blank but I saw somewhere someone said if you bring up the power menu and hit lockdown then unlock with your pin/pattern it'll fix it.
mackdacre said:
I updated as well and mine isn't blank but I saw somewhere someone said if you bring up the power menu and hit lockdown then unlock with your pin/pattern it'll fix it.
Click to expand...
Click to collapse
Mine was blank and I just tried this. That fixed it.
bradhoschar said:
Just flashed latest (230405.003.E1)
and noticed I have to unlock my screen manually even when I'm at home.
So I checked my smart lock settings, and it was blank!
I factory reset, and it was fine last night, woke up today and it was blank again.
Anyone else on the latest build experience this?
Click to expand...
Click to collapse
Mine started doing that randomly on the March update. A reboot temp fixes it.