Database Develop

[Q] rebooted jellybean now left with screwdriver and spanner icon

hi there
after successfully installing the JB updated on my unlocked phone and all was running fine for a while
that is until I rebooted it this morning, now the stupid thing wont start. I am stuck at the triangle iconwith the screwdirver and spanner, and the 'progress' bar below..
clearly it is not progressing as it been like that for over an hour now
also tried clearing cahce/dalvik to no avail
any options here or do I have to ftf my way back to ICS?
any help very much appreciated
thanks
nat

You just need to format your internal sd card and all should be fine, it's a fairly common issue
Sent from my LT30p using Tapatalk 2

matt4321 said:
You just need to format your internal sd card and all should be fine, it's a fairly common issue
Sent from my LT30p using Tapatalk 2
Click to expand...
Click to collapse
actually I had left it alone for an hour or so and it seems to have come back to life again..
although it has lost my security settings and all the haptic feedback has turned itself back on again
lost my swiftkey settings also it seems
piece of shizzle
EDIT: in fact it refuses to keep any security settings at all, no lock screen nothing.
lost all my texts everything, f*cking cr*p
walkman isnt working either
wondering why i bothered upgrading cant actually see any difference really other than a more colorful boot image. hoping that the battery life will improve as that is rubbish - I know it takes a while to settle.

matt4321 said:
You just need to format your internal sd card and all should be fine, it's a fairly common issue
Sent from my LT30p using Tapatalk 2
Click to expand...
Click to collapse
No No No don't format anything. That would make you loose all data and apps. Let it be. It will fix itself. Could take between 5 minutes and 3 hours. It is not an error or a problem or anything. Its just getting ready.
But if you really really need it to boot, yes you can format internal.
---------- Post added at 11:11 AM ---------- Previous post was at 11:05 AM ----------
xda-nat said:
actually I had left it alone for an hour or so and it seems to have come back to life again..
although it has lost my security settings and all the haptic feedback has turned itself back on again
lost my swiftkey settings also it seems
piece of shizzle
EDIT: in fact it refuses to keep any security settings at all, no lock screen nothing.
lost all my texts everything, f*cking cr*p
walkman isnt working either
wondering why i bothered upgrading cant actually see any difference really other than a more colorful boot image. hoping that the battery life will improve as that is rubbish - I know it takes a while to settle.
Click to expand...
Click to collapse
I don't know why it screwed up your settings buddy maybe due to a small flashing error. Flash again and you will see the difference in the upgrade. Battery life is amazing. I can get two days if i switch off data, and 1.5 days with data always on. Plus multitasking is smoother and the camera has HDR, the Xperia Z's ClearAudio+ engine, notification toggles, a sexy new Album, blah blah. You'll find out.
Oh and you did the right thing by letting it be with the white triangle sign.

I don't know why it screwed up your settings buddy maybe due to a small flashing error. Flash again and you will see the difference in the upgrade. Battery life is amazing. I can get two days if i switch off data, and 1.5 days with data always on. Plus multitasking is smoother and the camera has HDR, the Xperia Z's ClearAudio+ engine, notification toggles, a sexy new Album, blah blah. You'll find out.
Oh and you did the right thing by letting it be with the white triangle sign.
Click to expand...
Click to collapse
its an Xperia T I have in case that wasn't clear...
so I installed it from a zip in the end, rather than an ftf as flashtool was playing sillybuggers.
I should just go in to recovery and do so again? presumably along with the JB GApps
like I say it was working fine after the first time I did that, but when I turned it off this morning it went all manky
I would however like to keep some of my settings for the apps that havent already had their settings raped.. is titanium the best way to do that? or to move things to SD card and reinstall or something
also home button not functioning- at all
the no screen lock is a big issue as I have my work emails on there - if I lost my phone I would really get in trouble

xda-nat said:
its an Xperia T I have in case that wasn't clear...
so I installed it from a zip in the end, rather than an ftf as flashtool was playing sillybuggers.
I should just go in to recovery and do so again? presumably along with the JB GApps
like I say it was working fine after the first time I did that, but when I turned it off this morning it went all manky
I would however like to keep some of my settings for the apps that havent already had their settings raped.. is titanium the best way to do that? or to move things to SD card and reinstall or something
also home button not functioning- at all
the no screen lock is a big issue as I have my work emails on there - if I lost my phone I would really get in trouble
Click to expand...
Click to collapse
OK just installed the ROM zip (timin8r's one) again and its still utterly screwed.
can someone recommend a different one that I might be able to get working.
please....
thanks
nat

thedisturbedone said:
No No No don't format anything. That would make you loose all data and apps. Let it be. It will fix itself. Could take between 5 minutes and 3 hours. It is not an error or a problem or anything. Its just getting ready.
But if you really really need it to boot, yes you can format internal.
Click to expand...
Click to collapse
Most the app stuff is on /data not /sdcard so you'll be fine, some of the data made by apps will be in /sdcard/android but there isn't much there as most is in /data/data so if you backup /sdcard/android you'll be fine, you may as well backup your whole sdcard and format, that's the solution I used and most people have been using. If in doubt use titanium backup to also backup your apps if you're unsure

xda-nat said:
OK just installed the ROM zip (timin8r's one) again and its still utterly screwed.
can someone recommend a different one that I might be able to get working.
please....
thanks
nat
Click to expand...
Click to collapse
I believe the best way is to use a ftf file with flashtool. I have not tried any zipped roms. They might be faulty. And Titanium Backup is the app to use to backup apps. Moving things to SD card is useless as they will be removed when you install a new rom. Always make sure you do a full wipe when you flash a new rom, and flash the kernel before flashing the rom.

xda-nat said:
hi there
after successfully installing the JB updated on my unlocked phone and all was running fine for a while
that is until I rebooted it this morning, now the stupid thing wont start. I am stuck at the triangle iconwith the screwdirver and spanner, and the 'progress' bar below..
clearly it is not progressing as it been like that for over an hour now
also tried clearing cahce/dalvik to no avail
any options here or do I have to ftf my way back to ICS?
any help very much appreciated
thanks
nat
Click to expand...
Click to collapse
I had the screwdriver a few days ago, I freaked out so much because I putted Xperia T ftf and installed app's and then Reboot the device and then boom it showed the screwdriver... I was freaking out, So I went to 3 store's while the device was on.. and then later that day it randomly turned on properly.. Flash att ftf and the put back the jelly bean ftff

[Q] What happened to my HTC One?

Sorry for the vague title, but I couldn't think of a concise way of describing this.
I have a T-Mobile HTC One with the GPe ROM installed on it. I'm on 4.4.2 and using ART. I woke up this morning to find my phone in a boot loop. It would come up with the screen that shows the "Google" logo and the icon showing my phone is unlocked, remain on that screen for longer than normal, then reboot and do it again before getting to the actual ROM boot sequence.
I held down the power button to shut the phone off. When I turned it back on, it made it to the ROM boot, where the four colored circles fly around, but then came up with a screen asking for my disk encryption password. I've never set up encryption on the phone. I didn't want to try passwords I use in case this was some kind of phishing, though I'm not sure how that would be possible. At this point I wasn't really in the mood to do much troubleshooting so I did a factory reset from the bootloader and it seems fine now.
I'm just wondering if anyone knows what happened.

kernco said:
Sorry for the vague title, but I couldn't think of a concise way of describing this.
I have a T-Mobile HTC One with the GPe ROM installed on it. I'm on 4.4.2 and using ART. I woke up this morning to find my phone in a boot loop. It would come up with the screen that shows the "Google" logo and the icon showing my phone is unlocked, remain on that screen for longer than normal, then reboot and do it again before getting to the actual ROM boot sequence.
I held down the power button to shut the phone off. When I turned it back on, it made it to the ROM boot, where the four colored circles fly around, but then came up with a screen asking for my disk encryption password. I've never set up encryption on the phone. I didn't want to try passwords I use in case this was some kind of phishing, though I'm not sure how that would be possible. At this point I wasn't really in the mood to do much troubleshooting so I did a factory reset from the bootloader and it seems fine now.
I'm just wondering if anyone knows what happened.
Click to expand...
Click to collapse
Just don't use ART for now, stay with Dalvik. Much stable atm.

alray said:
Just don't use ART for now, stay with Dalvik. Much stable atm.
Click to expand...
Click to collapse
I wasn't planning on switching back to it. But that's not really answering my question about if anyone knows what happened. Unless you're saying that this is a known problem that happens to people who use ART, but it sounds more like you're just saying since I was using ART and something went wrong, it's a good chance that was why.

kernco said:
I wasn't planning on switching back to it. But that's not really answering my question about if anyone knows what happened. Unless you're saying that this is a known problem that happens to people who use ART, but it sounds more like you're just saying since I was using ART and something went wrong, it's a good chance that was why.
Click to expand...
Click to collapse
What most likely happened is ART corrupted the system and it forced a bootloop. You may have to full wipe and reflash. I would also advice to stay away from ART. It is not made for users.

zelendel said:
What most likely happened is ART corrupted the system and it forced a bootloop. You may have to full wipe and reflash. I would also advice to stay away from ART. It is not made for users.
Click to expand...
Click to collapse
I did a factory reset and so far everything is fine. Are you saying there might still be an issue and I should wipe and reflash to be safe?

kernco said:
I did a factory reset and so far everything is fine. Are you saying there might still be an issue and I should wipe and reflash to be safe?
Click to expand...
Click to collapse
I would just to be safe. Mainly with the pre-Alpha tag of the ART compiler. I mean it may not even make it to be official.

[Q] Question about Build.prop

When I plugged my phone into my computer today, I noticed the autoplay window displayed my phone as being "SM-N900s" or galaxy note 3. I checked my build.prop, and ro.product.model was indeed set to sm-n900s, for some reason. So I checked my original build.prop that I saved over a year ago, and it was set to "HTC One". So I pulled the .prop file from my phone, changed it to HTC One, pushed it, and rebooted. my phone hung on a black screen during boot, no charge light or anything.
I went into recovery, changed the file back to SM-N900s and it booted fine. Can anyone think of a reason my phone wont boot unless it thinks its a note 3?

bbmaster123 said:
When I plugged my phone into my computer today, I noticed the autoplay window displayed my phone as being "SM-N900s" or galaxy note 3. I checked my build.prop, and ro.product.model was indeed set to sm-n900s, for some reason. So I checked my original build.prop that I saved over a year ago, and it was set to "HTC One". So I pulled the .prop file from my phone, changed it to HTC One, pushed it, and rebooted. my phone hung on a black screen during boot, no charge light or anything.
I went into recovery, changed the file back to SM-N900s and it booted fine. Can anyone think of a reason my phone wont boot unless it thinks its a note 3?
Click to expand...
Click to collapse
What rom do you have installed?

I'm using insertcoin 8.1.3 (sense 5.5)

bbmaster123 said:
I'm using insertcoin 8.1.3 (sense 5.5)
Click to expand...
Click to collapse
I would do a full wipe and refresh the rom from scratch cause something is defiantly wrong

Thats a lot of work though. I have a lot of apps, and mods, and other stuff that would take hours to redo. Almost everything else on the phone works fine as far as I can tell. no lag, no FC, no random reboots etc. The only bug I have is the control buttons dont work for the lockscreen music player.
It doesn't really bother me that much, I was just wondering if someone has encountered this before.

bbmaster123 said:
Thats a lot of work though. I have a lot of apps, and mods, and other stuff that would take hours to redo. everything else on the phone works fine as far as I can tell. no lag, no FC, no random reboots etc
It doesn't really bother me that much, I was just wondering if someone has encountered this before.
Click to expand...
Click to collapse
I doubt it because having the build prop stating the wrong device can lead to apps showing incompatible and not updating like a bunch of sense apps and things like that.
The apps are not a big deal if you have TIBU.
I would look at all the mods you have installed. Nothing should touch the build prop other then the rom.

well don't doubt it because im telling you I don't have major issues with my phone. Maybe it CAN but it hasn't so far. BTW, sense apps will never update for me since 5.5 was deprecated a bit over a year ago.

bbmaster123 said:
well don't doubt it because im telling you I don't have major issues with my phone. Maybe it CAN but it hasn't so far. BTW, sense apps will never update for me since 5.5 was deprecated a bit over a year ago.
Click to expand...
Click to collapse
Very true. Well as long as you ok with it then I would sweat it. If you wanted you could pull a logcat when you put the proper build prop in

I've never taken a logcat before, I guess I'll have to research how to properly do that first.

Nexus 6 lock screen pin, 30 second wait for first wrong pin entry

Ive only had my nexus 6 for a couple of days now. I set a lock screen pin like I always do on every phone Ive ever owned. Typically when i need to punch it in on my lock screen I almost always put it in wrong the first time from trying to do it too fast. Well on the nexus 6 u have to wait 30 seconds before u can try again if u input it wrong even once. I dont know if this is how it's supposed to be or if this is possibly a result of something I did. Either way, how can i get rid of that or at least change it to 3 allowed failed attempts before it makes u wait 30 secs? I tried a xposed module called lockscreen tweak box which supposedly lets u change it to unlimited failed attempts but it did not work. Im assuming because im running 6.0. dont think its compatible with mm yet. I love this phone but im not used to this new high level security along with the high level device encryption. Anybody have any ideas as to how I can fix this? Thank u!

bump
can anybody help a ninja out?

NinjaPerv said:
bump
can anybody help a ninja out?
Click to expand...
Click to collapse
you cant get rid of that, and you have to wait 24h before you can bump your thread.

NinjaPerv said:
Well on the nexus 6 u have to wait 30 seconds before u can try again if u input it wrong even once. I dont know if this is how it's supposed to be or if this is possibly a result of something I did.
Click to expand...
Click to collapse
That is not normal. I'm able to retry immediately if my first pin entry is invalid. If you are running a custom ROM, try switching to the stock ROM. If you are on stock ROM, but have made changes to build prop or other system files, try to go back fully stock, and see if problem persists.
Oh, and what @simms22 said - wait 24 hours at least before bumping your thread

jj14 said:
That is not normal. I'm able to retry immediately if my first pin entry is invalid. If you are running a custom ROM, try switching to the stock ROM. If you are on stock ROM, but have made changes to build prop or other system files, try to go back fully stock, and see if problem persists.
Oh, and what @simms22 said - wait 24 hours at least before bumping your thread
Click to expand...
Click to collapse
i dont use a pin mostly, so dont remember. but i just set a pin and tried, and you are right. when i enter wrong, itll remove what i entered within about 3 seconds, then itll let me try again.

Im on the stock rom right now and other than rooting and unlocking the bootloader i have not made any changes to any system files at all. no xposed, no custom kernel, no viper, no build.prop edits, literally nothing. i flashed a different rom last night and it does it on that one as well. is this something that i can change in the build.prop? or does anyone know where the # of pin attempts is set at on the system level? does the same thing with a pattern and password. i don't get it but its incredibly frustrating.
....and in the future ill be a bit more patient before bumping my thread. sorry about that. i can only plead ignorance on that. arnt i original

NinjaPerv said:
Im on the stock rom right now and other than rooting and unlocking the bootloader i have not made any changes to any system files at all. no xposed, no custom kernel, no viper, no build.prop edits, literally nothing. i flashed a different rom last night and it does it on that one as well. is this something that i can change in the build.prop? or does anyone know where the # of pin attempts is set at on the system level? does the same thing with a pattern and password. i don't get it but its incredibly frustrating.
....and in the future ill be a bit more patient before bumping my thread. sorry about that. i can only plead ignorance on that. arnt i original
Click to expand...
Click to collapse
honestly, ive no idea. try a different type of security. i tried pattern, and it was quick as well.

NinjaPerv said:
Im on the stock rom right now and other than rooting and unlocking the bootloader i have not made any changes to any system files at all. no xposed, no custom kernel, no viper, no build.prop edits, literally nothing. i flashed a different rom last night and it does it on that one as well. is this something that i can change in the build.prop? or does anyone know where the # of pin attempts is set at on the system level? does the same thing with a pattern and password. i don't get it but its incredibly frustrating.
....and in the future ill be a bit more patient before bumping my thread. sorry about that. i can only plead ignorance on that. arnt i original
Click to expand...
Click to collapse
Make sure Settings -> Security -> Trust Agents -> Smart Lock (Google) is enabled. Had similar issue with PIN timeout on Chroma ROM when "Quick Unlock" feature was enabled. Never changed my PIN.
Dev stated to delete a specific file via TWRP. Did so and Smart Lock was gone from Settings. Google search to the rescue.
I admit I have no idea if this is root cause for you but worth a look to make certain Trust Agent is enabled for Smart Lock. I had no idea this existed until today. Android user ~15 years, rooting etc. whole time.
Sent from my Nexus 6 using Tapatalk

Random reboots and bootloops

Once and and while my Pixel 5 reboots and gets stuck in a bootloop. It happens while I listen to music with YouTube Music on a bluetooth ear phones or search for updates on the Play Store or nothing at all. I have no idea what is causing this.
I suspect one app called ProCall Mobile but I can't really test for two reasons: 1st it happens to randomly, weeks without one, than two in a row, than nothing for a month, or for few days, 2nd I need the app for my job and can't just remove it for testing.
I'm really annoyed by this, I also can't reset the phone because of reasons. Any ideas how can I narrow it down?

Sounds like something is causing a kernel panic, and it's hard to say what. The best thing I could really recommend is a complete factory reflash, but that requires an unlocked bootloader. I believe there may be a way to use ADB and USB Debugging to get a log dump, but I have no idea how to do that or how to read it.

V0latyle said:
Sounds like something is causing a kernel panic, and it's hard to say what. The best thing I could really recommend is a complete factory reflash, but that requires an unlocked bootloader. I believe there may be a way to use ADB and USB Debugging to get a log dump, but I have no idea how to do that or how to read it.
Click to expand...
Click to collapse
I fear you are right. I think I should set aside a few hours on the weekend to do that.

tehabe said:
need the app for my job and can't just remove it for testing.
Click to expand...
Click to collapse
Nope. If it's your phone, you don't have to keep any app on it. I have never experienced bootlooping or forced reboot on P5. Ask them for a work phone or tablet. It's not like old phones are expensive.
tehabe said:
I'm really annoyed by this, I also can't reset the phone because of reasons. Any ideas how can I narrow it down?
Click to expand...
Click to collapse
Also nope. You can back the entire phone up on google, data reset and reinstall everything.
Try force stop and clear cache in app.
Uninstall reinstall app.
Remove all unused apps.
Check Battery Usage
Go to Dev Options and turn on System Tracing and other debuggin features. I highly doubt you will be able to figure it out from there, but it may help others.