When my G2 reboots in the middle of the night for no good reason the start up jingle wakes me up as it's really loud. Also a problem if I need to turn my phone on in the cinema/theatre etc. Anybody know how to turn this down or even better stop it altogether! The phone is standard T-mobile rom equipped.
Pete
Code:
adb pull /system/media/bootscreen/boot_animation.xml .
then alter the file that the line reads:
Code:
useAudio="0"
and push it back to your phone:
Code:
adb remount
adb push boot_animation.xml /system/media/bootscreen/
this will silence your bootsound completely. to revert just change the value back to "1".
kendong2 said:
Code:
adb pull /system/media/bootscreen/boot_animation.xml .
then alter the file that the line reads:
Code:
useAudio="0"
and push it back to your phone:
Code:
adb remount
adb push boot_animation.xml /system/media/bootscreen/
this will silence your bootsound completely. to revert just change the value back to "1".
Click to expand...
Click to collapse
You've lost me, where do I put in this code? You did read that my phone is standard T-mobile build?
Pete
You have to execute those commands in shell.
I guess You may need to read about using ADB first
good luck!
top_banana123 said:
You did read that my phone is standard T-mobile build?
Pete
Click to expand...
Click to collapse
You're going to need to root your phone too.
Regards,
Dave
Hi, hope this will help, although it will only work if mean to restart phone.. Put it into vibrate mode, then when it starts up, it vibrates instead of that loudness that they have...
barny_stumble said:
Hi, hope this will help, although it will only work if mean to restart phone.. Put it into vibrate mode, then when it starts up, it vibrates instead of that loudness that they have...
Click to expand...
Click to collapse
won't help if the phone restarts itself.
sorry i guess i overread you having the original rom, you need it to be rooted to silence the bootsound... or at least have a custom recovery image. you can start that once without the need to flash it, if your fastboot isn't too new.
When I have my phone in silence mode it doesn't make a peep if I reboot it.
A better question is, why does your phone reboot on it's own?
Mine has never done that to me.
rdgut said:
When I have my phone in silence mode it doesn't make a peep if I reboot it.
A better question is, why does your phone reboot on it's own?
Mine has never done that to me.
Click to expand...
Click to collapse
I wish I new. Rebooted again last night at 4am!
Related
hi, my phone has stuck on the "google" icon when i start it. I have tried the "bootmode" you know when you hold volume and on/off button. There i tried to push on "reboot", "recovery", nothing is happening same thing. The only thing i have managed so far is installing driver usb for android phone in my computer, but i cant find the phonefolder in "My computer" to put reboot/update files to make the phone work.
How can i make the phone work? please help me im not so good at this.
please someone???
distortedloop said:
Everything you need should be in these two threads:
http://forum.xda-developers.com/showthread.php?t=878786
http://forum.xda-developers.com/showthread.php?t=895545
The second one has pictures and is very easy to follow.
Click to expand...
Click to collapse
Try this, thanks go to DistortedLoop
Check the links kenvan posted above.
You don't want to see the phone mounted as USB, you need to see it with the fastboot command from your DOS or unix terminal.
Then push ClockWork recovery to the phone.
From CW recovery you should be able to use it's tools to get you running again, or at least adb should work so you can mount storage and push files to it via adb.
I'd love to help you but I need a little more background... did you just buy the phone and this is happening? Or did you try rooting it and this is happening? Or did you just flash a different rom and this is happening?
somii87 said:
hi, my phone has stuck on the "google" icon when i start it. I have tried the "bootmode" you know when you hold volume and on/off button. There i tried to push on "reboot", "recovery", nothing is happening same thing. The only thing i have managed so far is installing driver usb for android phone in my computer, but i cant find the phonefolder in "My computer" to put reboot/update files to make the phone work.
How can i make the phone work? please help me im not so good at this.
Click to expand...
Click to collapse
i have tryed this one : http://forum.xda-developers.com/showthread.php?t=895545
once i get to the phase where i select recovery in bootloader it just goes to the screen with the google logo and the unlocked padlock icon and it sticks there, any suggestions? i have tried to entering the recovery command again in the command prompt, still same problem =(
dinan said:
I'd love to help you but I need a little more background... did you just buy the phone and this is happening? Or did you try rooting it and this is happening? Or did you just flash a different rom and this is happening?
Click to expand...
Click to collapse
nothing the phone started to hang/freeze and then vibrating for about 40 seconds, i took out the battery the it was stucked in on the google icon.
dinan said:
I'd love to help you but I need a little more background... did you just buy the phone and this is happening? Or did you try rooting it and this is happening? Or did you just flash a different rom and this is happening?
Click to expand...
Click to collapse
kenvan19 said:
Try this, thanks go to DistortedLoop
Click to expand...
Click to collapse
i have tryed this one : http://forum.xda-developers.com/showthread.php?t=895545
once i get to the phase where i select recovery in bootloader it just goes to the screen with the google logo and the unlocked padlock icon and it sticks there, any suggestions? i have tried to entering the recovery command again in the command prompt, still same problem =(
Ok since you say you have a padlock on the boot screen, I assume you know how you unlocked the bootloader.
Turn the phone on into fastboot (hold power and volume up), then connect the phone to the computer via USB. Flash clockwork recovery (3.0.0.5 preferred) and then you should be able to enter clockwork recovery assuming you did it correctly. Push this rom (http://forum.xda-developers.com/showthread.php?t=884093) to your card and flash it in recovery.
dinan said:
Ok since you say you have a padlock on the boot screen, I assume you know how you unlocked the bootloader.
Turn the phone on into fastboot (hold power and volume up), then connect the phone to the computer via USB. Flash clockwork recovery (3.0.0.5 preferred) and then you should be able to enter clockwork recovery assuming you did it correctly. Push this rom (http://forum.xda-developers.com/showthread.php?t=884093) to your card and flash it in recovery.
Click to expand...
Click to collapse
Yes i know, can you be more specific`? step by step? im noob sorry for bothering you., how do i push to my card?
I have fixed my phone, my phone was liquid damaged. So i putted the hole mainboard in 100% alcohol and after 20 min i took it out and let it dry. And then it worked fine!
It just happened to me an hour ago. I tried for a few time to remove the battery and start it up (even with a new one). I also thought it might happen since the battery was drained so i let it recharge for a while with no success.
Eventually i attached the device to the computer's usb, waited and started it. and it worked.
Don't know if that was what solving it - but it back working.
Hello forum so here is another request for help.
Last night I charged my Xoom. This morning I shut it down and took it with me to class as I knew I wasn't going to use it until that afternoon. When I powered up this afternoon I get the Moto logo then the pulsing tiles. Then the screen will eventually time out and "go to sleep". When I push the power button the screen comes on and the pulsing tiles are still being displayed. The system will still play the notification sound when emails are received so I think that it is somewhat alive.
Tried to talk to Moto tech support but was disconnected when being transfered from a lvl 1 tech to a lvl 2 tech. Unfortunately I didn't have time to sit on hold again so I will have to try them again tomorrow.
Adb works.
Vol up + power reboots
Vol down just brings me to a screen that says "Starting Fastboot protocol support." and sits there.
adb reboot recovery brings me to and android with a yellow caution sign in him.
The only "unusual programs/activity" I have loaded is this launcher which was set as default. http://forum.xda-developers.com/showthread.php?t=1017451
Any Ideas?
PS NOTE: This is a Xoom Wifi.
Thanks,
ChanceM
Just an update in case anyone else has this just talked with Moto and they are sending me a new Xoom.
ChanceM
Same thing happened to me
Hey dude, same thing happened to me, although I had not enabled usb debugging before hand. I still had access to fastboot so doing a 'fastboot oem unlock' formatted the device and returned it to stock.
VTL-launcher will not work for the xoom, as you and I both painfully found out.
Since you have adb still working during the animation, couldnt you just:
'adb reboot recovery'
and recover stock?
I'm by no means an expert, just trying to help out... if anyone else has anything to add on this, this dude will surely appreciate it.
If you can get adb access its easier to just remove the offending application
Code:
adb shell rm /data/app/packagenamehere.apk
Where packagenamehere.apk is the name of the APK you installed.
Reboot and you're good to go.
Sent from my GT-P1000
alias_neo said:
If you can get adb access its easier to just remove the offending application
Code:
adb shell rm /data/app/packagenamehere.apk
Where packagenamehere.apk is the name of the APK you installed.
Reboot and you're good to go.
Sent from my GT-P1000
Click to expand...
Click to collapse
Excellent! That's even better. Still trying to learn all this stuff.... Thanks dude.
I had the same problem with ADW Launcher but, oddly, not with ADW Launcher EX. Removing the package was the only way I could solve it, too. besides removing, you can adb uninstall packagename.
EDIT: BTW, you can comment directly to the author of VTL-Launcher in his thread here on XDA: http://forum.xda-developers.com/showthread.php?t=1017451. Gojimi's a great guy and anxious to get to the bottom of any problem.
Okay I tried removing it but I get permission denied.
Edit: Thanks guys I was able to do a factory reset.
ChanceM
put it in fastboot mode by holding down the volume down key during power up
do:
fastboot erase cache
fastboot erase userdata
be aware that if you do this, everything that you have in your xoom will be erased, but it will boot up fine, will ask you to go through the activation again and you are ready to put your stuff back in.
Times like these is when I wished the sdcard was working, so my content wouldn't be wiped out
HazeT said:
put it in fastboot mode by holding down the volume down key during power up
do:
fastboot erase cache
fastboot erase userdata
be aware that if you do this, everything that you have in your xoom will be erased, but it will boot up fine, will ask you to go through the activation again and you are ready to put your stuff back in.
Times like these is when I wished the sdcard was working, so my content wouldn't be wiped out
Click to expand...
Click to collapse
We should add to this that he must be have an unlocked boot loader to issue these commands, I tried just that when I had this problem.
However, unlocking forced a system format anyways.
Hi All, as the title states, I'm currently stuck in a CWM bootloop after trying to applying the new OTA update on my rooted transformer.
I know it was kinda stupid of it.
I tried following the steps posted here, but i can't seem to get adb to push the file through.
I must admit that I'm not very good with using command prompts and i have no idea if I'm doing it right.
Steps I'm sure i'm doing right so far.
I opened up my cmd and cd C:\android-sdk\platform-tools
When typing adb devices, my transformer is successfully recognized as 0123456789ABCDEF OFFLINE
However, the next part got me slightly confused.
I had typed in C:\android-sdk\platform-tools>adb push C:\cwm_recovery-5027_rogue_rburrow-tf101-r1.zip /sdcard/download.
However, i kept encountering the error that the device is offline.
I had also set up a marco to press the up arrow+enter key with a 10ms pause in between followed by a 1 second pause before repeating.
However, the file was still unable to be pushed to the device despite countless tries.
I'm not sure if it's because the line i had entered was wrong or was it due to some other factor.
Would someone be kind enough to help me take a look and see if i had done something wrong?
Thank you very much for your help!
lunzi88 said:
Hi All, as the title states, I'm currently stuck in a CWM bootloop after trying to applying the new OTA update on my rooted transformer.
I know it was kinda stupid of it.
I tried following the steps posted here, but i can't seem to get adb to push the file through.
I must admit that I'm not very good with using command prompts and i have no idea if I'm doing it right.
Steps I'm sure i'm doing right so far.
I opened up my cmd and cd C:\android-sdk\platform-tools
When typing adb devices, my transformer is successfully recognized as 0123456789ABCDEF OFFLINE
However, the next part got me slightly confused.
I had typed in C:\android-sdk\platform-tools>adb push C:\cwm_recovery-5027_rogue_rburrow-tf101-r1.zip /sdcard/download.
However, i kept encountering the error that the device is offline.
I had also set up a marco to press the up arrow+enter key with a 10ms pause in between followed by a 1 second pause before repeating.
However, the file was still unable to be pushed to the device despite countless tries.
I'm not sure if it's because the line i had entered was wrong or was it due to some other factor.
Would someone be kind enough to help me take a look and see if i had done something wrong?
Thank you very much for your help!
Click to expand...
Click to collapse
Damn man sorry to hear that. Def should have flashed stock recovery before applying the OTA. Im sure one of these guys can help you out though good luck!
Sent from my Transformer TF101 using xda premium
pierrekid said:
Damn man sorry to hear that. Def should have flashed stock recovery before applying the OTA. Im sure one of these guys can help you out though good luck!
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
yeah dude, i realised that after i googled for a fix.
prior to this my experience with OTA updates on rooted+CWM phones had never encounter such problem.
The most that had happened previously was that the update failed to be installed.
I had no idea it could get stuck in a loop i couldnt get out of.
when you're doing adb devices, is your tablet in recovery or off?
try this,
push and hold vol down plus power button
when you see words at top left corner, wait a while till you see options to wipe data or cold boot.
Select cold boot to see ifnyou can boot into OS
baseballfanz said:
when you're doing adb devices, is your tablet in recovery or off?
try this,
push and hold vol down plus power button
when you see words at top left corner, wait a while till you see options to wipe data or cold boot.
Select cold boot to see ifnyou can boot into OS
Click to expand...
Click to collapse
thanks for the tip.
I can't try it right now as I left the tablet at home when I left for work today.
I'll update once I get back home to try it.
baseballfanz said:
when you're doing adb devices, is your tablet in recovery or off?
try this,
push and hold vol down plus power button
when you see words at top left corner, wait a while till you see options to wipe data or cold boot.
Select cold boot to see ifnyou can boot into OS
Click to expand...
Click to collapse
The words are not even popping up for me, it just shows the asus logo and then goes straight into recovery. I go into adb devices and it shows OFFLINE aswell.
:S
baseballfanz said:
when you're doing adb devices, is your tablet in recovery or off?
try this,
push and hold vol down plus power button
when you see words at top left corner, wait a while till you see options to wipe data or cold boot.
Select cold boot to see ifnyou can boot into OS
Click to expand...
Click to collapse
That's what I did when it happened to me. Worked like a charm.
I did the same thing and I'm stuck too.
Sent from my Kindle Fire using xda premium
Same problem here for the same reason...flash ota update on my root tablet....I'm always on cwm recovery when reboot. I'm able to cold boot it when holding.vol down and power but I do I get around this cwm ecovwry bootloop? Thanks
Envoyé depuis mon HTC Glacier avec Tapatalk
lamaqc said:
Same problem here for the same reason...flash ota update on my root tablet....I'm always on cwm recovery when reboot. I'm able to cold boot it when holding.vol down and power but I do I get around this cwm ecovwry bootloop? Thanks
Envoyé depuis mon HTC Glacier avec Tapatalk
Click to expand...
Click to collapse
Same here. The only way I can boot now is VolDown + Power. Another thread recommended flashing some stock-like ROM, but I'd rather not.
Has someone found out how to boot normally?
I have to cold boot everytime my device reboots or it shuts off, which is quite often.
The cold boot method is becoming really annoying.
Thanks!
Found a way!
Hi guys! This is my first post helping somebody
So I found a way to make it boot normally...
What you need to do is to cold boot your device.
Then download from the store Android Terminal Emulator.
Open it up and type in:
Code:
su
Allow SuperUser if prompted.
If you get # then you are good to go!
Now you need to type in:
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Once it's done, reboot your tablet and you should see a progress bar.
Let it load and once it's done, you have your tablet back!
Hope it works!
Hi guys I'm in trouble!! I have continuos bootloops in recovery. I tryed to flash a rom as usual but always bootlooping adn when I tryed to make a cold boot it remain in the same " colod booting linux ".. I can't restore my backup cause I move it on my memory card and cant restore it! Can I do something? I can't boot anymore... Any suggestions? I can only install the rom I have put in the internal memory..
So heres my issue, ATT G2. Installed clean rom xe 1.1 then was dumb and used titanium to restore my app data, not system, just app. but someone that caused a system ui to keep crashing, so I got into recovery mode by holding down and power button (white screen that asks to reset to factory). Did that and it booted to TWRP ran a script and then went back to LG screen and then blank screen with flashing led and that's where it stayed, won't go any further.
I've put it in download mode now and am using LG flash tool but when I plug the phone in the box for COM41 in the flash tool just says waiting for connection and thats it. then when I unplug it it says failed, obviously. Is my phone a brick or can it be saved?
I think it's getting a model information check fail in lg flashtool, ugh this sucks.
bova80 said:
So heres my issue, ATT G2. Installed clean rom xe 1.1 then was dumb and used titanium to restore my app data, not system, just app. but someone that caused a system ui to keep crashing, so I got into recovery mode by holding down and power button (white screen that asks to reset to factory). Did that and it booted to TWRP ran a script and then went back to LG screen and then blank screen with flashing led and that's where it stayed, won't go any further.
I've put it in download mode now and am using LG flash tool but when I plug the phone in the box for COM41 in the flash tool just says waiting for connection and thats it. then when I unplug it it says failed, obviously. Is my phone a brick or can it be saved?
Click to expand...
Click to collapse
LOL, i just went through the same thing. I'll be posting a fix tonight I worked out with Scott.
"There is a "back door" method. This is why they updated TWRP by the way...
Download this: https://dl.dropboxusercontent.com/u/...with cmd.zip
Extract it to desktop. open the command.bat file.
Type "adb reboot recovery" then press enter. You need to keep doing this during the factory reset.
This assumes you have drivers installed. If you have no drivers installed for recovery mode then just select generic Google Nexus ADB drivers.
You kinda have to hammer the reboot recovery command. Its all timing... To hammer it... press the up arrow in the dos prompt and that will repeat the line. then press enter.
Keep doing it until you see it reboot to twrp and you should be able to sideload or load from storage.
It may take 10 or 15 minutes to get the exact right timing so dont give up.
And of course, this is all dependent upon you having the drivers already installed."
- Scott
For timing, you'll need to wait right when TWRP starts writing the script and start hammering it out. Timing is everything so when you see the TWRP screen starting hitting the up cursor and enter. It should load recovery. Don't bother using the tool, it won't work as it thinks your device is a D802 and won't be compatible with the dll. This will get you back to normal and from here you can just wipe and reinstall the rom again fresh with out losing media/data on the your drive.
I tried to download the file since I am in the same boat, but the dropbox is giving errors... Could you please repost the link to get the file? It would be greatly appreciated
MkV05 said:
I tried to download the file since I am in the same boat, but the dropbox is giving errors... Could you please repost the link to get the file? It would be greatly appreciated
Click to expand...
Click to collapse
When I get home to my personal desktop I'll be able to upload the link again. It's not my drop box but I have the files to upload to drop box and repost.
SamsungGalaxyStig said:
When I get home to my personal desktop I'll be able to upload the link again. It's not my drop box but I have the files to upload to drop box and repost.
Click to expand...
Click to collapse
Awesome, been waiting for this! Just to confirm, will the same file work for someone with a Verizon G2 who's having the same problem?
ccmbr002 said:
Awesome, been waiting for this! Just to confirm, will the same file work for someone with a Verizon G2 who's having the same problem?
Click to expand...
Click to collapse
I haven't tested it on VZW unfortunately. Check with scrosler. However, I assume it should be similar if not the same, but don't quote me on that.
Updated Link guys: https://www.dropbox.com/s/qsjwguwtlyczwdh/adb with cmd.zip
so I got it right when it said teamwin to reboot but everytime it reboot it tried to run the script and would never actually go into twrp. att is sending me a new phone but I'm worried when I send this one back they'll get me for being rooted.
SamsungGalaxyStig said:
I haven't tested it on VZW unfortunately. Check with scrosler. However, I assume it should be similar if not the same, but don't quote me on that.
Updated Link guys: https://www.dropbox.com/s/qsjwguwtlyczwdh/adb with cmd.zip
Click to expand...
Click to collapse
I just messaged him to double check - I don't have access to my phone for a few days (out of town) but if he hasn't responded by the time I get home I'll just go ahead and try it and post here if it works or not. Thanks again for sharing this file!
Got the file... and MANY THANKS!!! It allowed me to un-softbrick my G2 finally
this just isn't working for me, so hard to get it to get that command and when I do it still just reboots to the wiping partition script and reboots again. Think I'm screwed. Anything I can do in download mode or any other commands I can send? @SamsungGalaxyStig
video clip of what is happening
http://youtu.be/8U_mgYYxIpQ
here is what the script says
updating partition details
Running boot script....
Finished running bootscript,
Processing AOSP recovery commands....
----Wiping Data Partition----
Wiping data without data/media...
Done.
Removing all files under '/cache'
---- data partition wipe complete!
Done processing script file
Click to expand...
Click to collapse
bova80 said:
this just isn't working for me, so hard to get it to get that command and when I do it still just reboots to the wiping partition script and reboots again. Think I'm screwed. Anything I can do in download mode or any other commands I can send? @SamsungGalaxyStig
video clip of what is happening
http://youtu.be/8U_mgYYxIpQ
here is what the script says
Click to expand...
Click to collapse
The minute you see the twrp screen pop up start hammering away at the adb command listed before. after you type it once, you can keep pressing the up cursor and it will just replicate the previous command. You are opening up the cmd in the adb folder right?
SamsungGalaxyStig said:
The minute you see the twrp screen pop up start hammering away at the adb command listed before. after you type it once, you can keep pressing the up cursor and it will just replicate the previous command. You are opening up the cmd in the adb folder right?
Click to expand...
Click to collapse
yeah just tried it again and as soon as I hit it it starts rebooting again goes to TeamWin screen and then runs the same script I posted before and when it is done it reboots and then goes to blank screen. I had just put the latest twrp on the day before too so I don't understand why it isn't booting to it.
My biggest thing is will ATT freak and send the phone back once they get it and go to download mode and see it says rooted or if they try the hard reset and see it goes to a TeamWin screen.
side note, if I can type adb shell and get it to prompt me there, is there anything I can try and type quickly to have it do anything else?
bova80 said:
yeah just tried it again and as soon as I hit it it starts rebooting again goes to TeamWin screen and then runs the same script I posted before and when it is done it reboots and then goes to blank screen. I had just put the latest twrp on the day before too so I don't understand why it isn't booting to it.
My biggest thing is will ATT freak and send the phone back once they get it and go to download mode and see it says rooted or if they try the hard reset and see it goes to a TeamWin screen.
side note, if I can type adb shell and get it to prompt me there, is there anything I can try and type quickly to have it do anything else?
Click to expand...
Click to collapse
Are you constantly doing the adb recovery reboot? or once or twice?
SamsungGalaxyStig said:
Are you constantly doing the adb recovery reboot? or once or twice?
Click to expand...
Click to collapse
I did it a bunch of times continuously and it would just keep rebooting. Am I supposed to just keep doing that for 10-15min straight? How will I know if it gets into recovery if it just keeps rebooting when ever I keep doing that?
bova80 said:
I did it a bunch of times continuously and it would just keep rebooting. Am I supposed to just keep doing that for 10-15min straight? How will I know if it gets into recovery if it just keeps rebooting when ever I keep doing that?
Click to expand...
Click to collapse
Keep doing it, watch your phone as it will eventually boot into recovery itself without running script.
SamsungGalaxyStig said:
Keep doing it, watch your phone as it will eventually boot into recovery itself without running script.
Click to expand...
Click to collapse
when I'm sending that command though it never actually runs the script, it just reboots.
I'll try this out when I get home, hopefully my fingers don't get tired, lol. How long did it take you?
bova80 said:
when I'm sending that command though it never actually runs the script, it just reboots.
I'll try this out when I get home, hopefully my fingers don't get tired, lol. How long did it take you?
Click to expand...
Click to collapse
like 5-10 min at most. it's literally timing. and based on what i saw on the youtube video you were having the exact same problem. btw, you have your drivers installed correctly right? you can check that under device manager. BTW, are you using a PC or mac?
SamsungGalaxyStig said:
like 5-10 min at most. it's literally timing. and based on what i saw on the youtube video you were having the exact same problem. btw, you have your drivers installed correctly right? you can check that under device manager. BTW, are you using a PC or mac?
Click to expand...
Click to collapse
on a pc. when i go under device manager I think it says something like lg modem, I'll know for sure when I get home.
omg it finally worked! thanks, I eventually just gave up with the command prompt and it went in.
Hey guys.
I have nexus 4 4.4.2stock+root.
I have problem that sometimes the phone not wake up(I push the keys(home keys and volume keys and the phone just not turn on the screen)...
(Its can to hapeen after some minutes I use the phone)
Then I must to do hard restart to the phone...
How I can slove this problem...
Thanks very much..
( I have closed with gravitybox and greentify)
Oz4225 said:
Hey guys.
I have nexus 4 4.4.2stock+root.
I have problem that sometimes the phone not wake up(I push the keys(home keys and volume keys and the phone just not turn on the screen)...
(Its can to hapeen after some minutes I use the phone)
Then I must to do hard restart to the phone...
How I can slove this problem...
Thanks very much..
( I have closed with gravitybox and greentify)
Click to expand...
Click to collapse
I also had this problem for 3 weeks. I believe I got this fixed now and the problem hasn't come back for a week.
What I did was to boot into recovery and wipe cache.
The second thing that I did was to use ADB (I am not sure if it's necessary):
adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity‘
This will initialize the setup wizard again and freshen things up, according to this article:
http://www.androidauthority.com/nexus-4-issues-kitkat-319948/
Maybe it's a mental thing, but I find the N4 works more smoothly now and has better battery life.
dookie23 said:
I also had this problem for 3 weeks. I believe I got this fixed now and the problem hasn't come back for a week.
What I did was to boot into recovery and wipe cache.
The second thing that I did was to use ADB (I am not sure if it's necessary):
adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity‘
This will initialize the setup wizard again and freshen things up, according to this article:
http://www.androidauthority.com/nexus-4-issues-kitkat-319948/
Maybe it's a mental thing, but I find the N4 works more smoothly now and has better battery life.
Click to expand...
Click to collapse
Thanks!!
I will try to Wipe cache frist.
The ADB command(-n com.google.android.setupwizard/.SetupWizardTestActivity) delete somthing in the device?
This is a common N4 problem.
Oz4225 said:
Thanks!!
I will try to Wipe cache frist.
The ADB command(-n com.google.android.setupwizard/.SetupWizardTestActivity) delete somthing in the device?
Click to expand...
Click to collapse
no, the ADB command doesn't delete anything. The SetupWizard will bring up the screen where you have to type in the owner's information (first and last name) then to accept the terms and conditions, etc.
Hope this will solve the issue for you... it solved mine