It's happening about once every minute or so. Just wondering if it's happening to anyone else?
mrkonyk said:
It's happening about once every minute or so. Just wondering if it's happening to anyone else?
Click to expand...
Click to collapse
Have you tried a reboot or factory reset since upgrading?
Just waiting to see if anyone else is having the same issue before I went through the trouble of a factory reset. No point in doing the reset if it won't fix the problem.
mrkonyk said:
Just waiting to see if anyone else is having the same issue before I went through the trouble of a factory reset. No point in doing the reset if it won't fix the problem.
Click to expand...
Click to collapse
On my Anker Soundbuds Slim as I type this. No issues as far as I can tell.
reverenddak said:
On my Anker Soundbuds Slim as I type this. No issues as far as I can tell.
Click to expand...
Click to collapse
Before you went to beta did you do a factory reset?
mrkonyk said:
Before you went to beta did you do a factory reset?
Click to expand...
Click to collapse
Yes, only when from Nougat. But not between Oreo Betas, and that was a while ago.
reverenddak said:
Yes, only when from Nougat. But not between Oreo Betas, and that was a while ago.
Click to expand...
Click to collapse
Sounds like a factory reset is probably the best option, Thanks!
mrkonyk said:
It's happening about once every minute or so. Just wondering if it's happening to anyone else?
Click to expand...
Click to collapse
Spent the last two hours listening to music over Bluetooth. No issues. Oreo Beta 3.
Hello, how to do a factory Reset without loosing all? I have now Oreo Beta 3 but my Essential crashes every day. it will be black and the boot logo comes and stays. Then i must quit the Phone and restart. In Beta 2 there was this issue too. What can i do?
zzman31 said:
Hello, how to do a factory Reset without loosing all? I have now Oreo Beta 3 but my Essential crashes every day. it will be black and the boot logo comes and stays. Then i must quit the Phone and restart. In Beta 2 there was this issue too. What can i do?
Click to expand...
Click to collapse
Maybe you should reset the phone and see if it still crashes frequently. If so you should send it for warrant.
Been listening to bluetooth for a while this morning and haven't noticed any issues with B3.
zzman31 said:
Hello, how to do a factory Reset without loosing all? I have now Oreo Beta 3 but my Essential crashes every day. it will be black and the boot logo comes and stays. Then i must quit the Phone and restart. In Beta 2 there was this issue too. What can i do?
Click to expand...
Click to collapse
Did you try a standard wipe cache and dalvik after installing B3?
reverenddak said:
Did you try a standard wipe cache and dalvik after installing B3?
Click to expand...
Click to collapse
Hello, no because it was en OTA update. But this issue was in beta 2 too.
zzman31 said:
Hello, no because it was en OTA update. But this issue was in beta 2 too.
Click to expand...
Click to collapse
Boot to Recovery. Once you get to the dead Android with a Red "!", hold Power and then press Vol+. You'll get to a Menu, use the Vol buttons to select Wipe Cache. Press Power. Then Select Reboot.
(though while there, i'd use ADB and re-flash B3, and then clear cache).
reverenddak said:
Boot to Recovery. Once you get to the dead Android with a Red "!", hold Power and then press Vol+. You'll get to a Menu, use the Vol buttons to select Wipe Cache. Press Power. Then Select Reboot.
(though while there, i'd use ADB and re-flash B3, and then clear cache).
Click to expand...
Click to collapse
Okay thank you, I will try it.
I had the same trouble. Anything is working right. I can pair my Bluetooth earbuds. The first minutes are OK, but after the screen goes off there are a couple breaks by the music here and there . Awakening the screen will help.
reverenddak said:
Boot to Recovery. Once you get to the dead Android with a Red "!", hold Power and then press Vol+. You'll get to a Menu, use the Vol buttons to select Wipe Cache. Press Power. Then Select Reboot.
(though while there, i'd use ADB and re-flash B3, and then clear cache).
Click to expand...
Click to collapse
You can't do this on the essential. They took Wipe Cache out of the recovery. I was very angry when I saw that.
JoRocker said:
You can't do this on the essential. They took Wipe Cache out of the recovery. I was very angry when I saw that.
Click to expand...
Click to collapse
Same here. Why on Earth would anyone go out of their way to do this? ?
BTW there are also apps that claim to wipe cache -Lspeed for example, but I have yet to see proof of it actually doing so. Also twrp doesn't register a cache partition either. How weird. It's probably part of the boot partition like everything else seems to be...
Imagine if the only way to clear cache was to flash boot image. What a load of crap that would be, lol
stryver said:
Same here. Why on Earth would anyone go out of their way to do this? ?
BTW there are also apps that claim to wipe cache -Lspeed for example, but I have yet to see proof of it actually doing so. Also twrp doesn't register a cache partition either. How weird. It's probably part of the boot partition like everything else seems to be...
Imagine if the only way to clear cache was to flash boot image. What a load of crap that would be, lol
Click to expand...
Click to collapse
You can do it in ADB, but I don't always have my laptop handy, and besides running ADB every time I have an issue is a huge PITA... I'm starting to lose confidence in this company.
JoRocker said:
You can't do this on the essential. They took Wipe Cache out of the recovery. I was very angry when I saw that.
Click to expand...
Click to collapse
You're right. My bad. I've found that Google backup does a decent job of restoring your phone's settings and apps. I had to wipe my phone the first few times I tried to sideload.
Related
I have EOS4 flashed and my tablet went off yesterday and when I turned it back on it showed a bunch of green lines. Now it just shows the EOS bootimage indefinitely. Does anyone have any info on this?
If you wipe SYSTEM and Cache and Dalvik cache, then flash the ROM again, your apps / user data will not be touched, all that is stored on DATA
*Detection* said:
If you wipe SYSTEM and Cache and Dalvik cache, then flash the ROM again, your apps / user data will not be touched, all that is stored on DATA
Click to expand...
Click to collapse
How do I get into my recovery? Or is it from the cold boot method?
patrickjaden said:
How do I get into my recovery? Or is it from the cold boot method?
Click to expand...
Click to collapse
Yea, just from a powered off state, hold Volume Down and Power until the white text appears at the top of the screen, then release the buttons and hit volume up once to enter recovery
*Detection* said:
If you wipe SYSTEM and Cache and Dalvik cache, then flash the ROM again, your apps / user data will not be touched, all that is stored on DATA
Click to expand...
Click to collapse
*Detection* said:
Yea, just from a powered off state, hold Volume Down and Power until the white text appears at the top of the screen, then release the buttons and hit volume up once to enter recovery
Click to expand...
Click to collapse
So I did that and now I'm stuck at "Starting apps."
patrickjaden said:
So I did that and now I'm stuck at "Starting apps."
Click to expand...
Click to collapse
Hmm, I wonder if something on your DATA partition got corrupted then
Inside of recovery you can navigate through folder levels to reach places like DATA/APPS and disable different apps by renaming from .apk to .apk.old then try booting again
Might take a while to find the offending app though
I would backup your DATA partition, then wipe DATA and see if it boots
If it does then you have the option of the above to disable them one at a time
EDIT - You are running TWRP recovery and not CWM ?
*Detection* said:
Hmm, I wonder if something on your DATA partition got corrupted then
Inside of recovery you can navigate through folder levels to reach places like DATA/APPS and disable different apps by renaming from .apk to .apk.old then try booting again
Might take a while to find the offending app though
I would backup your DATA partition, then wipe DATA and see if it boots
If it does then you have the option of the above to disable them one at a time
EDIT - You are running TWRP recovery and not CWM ?
Click to expand...
Click to collapse
Yes, I'm running TWRP. This started when I was playing Candy Crush. I thought that game was harmless, lol :silly:
patrickjaden said:
Yes, I'm running TWRP. This started when I was playing Candy Crush. I thought that game was harmless, lol :silly:
Click to expand...
Click to collapse
lol, Candy Crush is anything but harmless, especially when the missus kidnaps your TF to play it
I would backup DATA and then wipe Data and see if you get any further, that way you can at least restore Data if its not that
*Detection* said:
lol, Candy Crush is anything but harmless, especially when the missus kidnaps your TF to play it
I would backup DATA and then wipe Data and see if you get any further, that way you can at least restore Data if its not that
Click to expand...
Click to collapse
So I press format data and then it says "Failed" ...
Sorry for the double post, but I just wanted to say I fixed it somehow.
Sorry I meant to reply yesterday but got sidetracked, good news you've fixed it
Do you know what you did to fix it? Just for any one else that comes into the same problem, your fix might help them too
*Detection* said:
Sorry I meant to reply yesterday but got sidetracked, good news you've fixed it
Do you know what you did to fix it? Just for any one else that comes into the same problem, your fix might help them too
Click to expand...
Click to collapse
I factory reset and I think that helped.
Hi, last night my wifi seemed to cut off while using my tablet. I tried to cut it back on and it got stuck in the "trying to connect to wifi" stage. I cant press the button and it wont turn back on. I was running Chromi X 4.6.6 at the time. Today, I flashed 4.6.8, hoping it would reset and fix the problem, but the problem still is there. I am really nervous I broke my wifi chip or something. Here is a screenshot of what is happening. I hope someone can help me.
Thank you.
wl123 said:
Hi, last night my wifi seemed to cut off while using my tablet. I tried to cut it back on and it got stuck in the "trying to connect to wifi" stage. I cant press the button and it wont turn back on. I was running Chromi X 4.6.6 at the time. Today, I flashed 4.6.8, hoping it would reset and fix the problem, but the problem still is there. I am really nervous I broke my wifi chip or something. Here is a screenshot of what is happening. I hope someone can help me.
Thank you.
Click to expand...
Click to collapse
Is the WiFi icon greyed out in the bottom right? If so try removing your Google account from settings and the readd it. I think Google have been having some DNS issues recently.
sbdags said:
Is the WiFi icon greyed out in the bottom right? If so try removing your Google account from settings and the readd it. I think Google have been having some DNS issues recently.
Click to expand...
Click to collapse
I removed my Google account and tried to re add it. I get to the part where I need to be connected to wifi and I get this. Something seems to be horribly wrong.
wl123 said:
I removed my Google account and tried to re add it. I get to the part where I need to be connected to wifi and I get this. Something seems to be horribly wrong.
Click to expand...
Click to collapse
Do you have a back up nandroid to go back to? Try a clean wipe as well to eliminate software issues.
sbdags said:
Do you have a back up nandroid to go back to? Try a clean wipe as well to eliminate software issues.
Click to expand...
Click to collapse
Yes I have a backup from like chromi 4.5. I am trying to restore right now. If I clean wipe it, wont it delete the nandroid backups?
wl123 said:
Yes I have a backup from like chromi 4.5. I am trying to restore right now. If I clean wipe it, wont it delete the nandroid backups?
Click to expand...
Click to collapse
Just do a factory wipe. As long as you don't do a full data wipe you will keep your nandroids if they are on internal.
This :http://www.transformerforums.com/fo...h-will-not-turn-asus-say-start-over-help.html
is exactly the same problem I am having.
sbdags said:
Just do a factory wipe. As long as you don't do a full data wipe you will keep your nandroids if they are on internal.
Click to expand...
Click to collapse
How long does it usually take to Restore Data when restoring a nandroid backup? It seems to be taking a long time
wl123 said:
How long does it usually take to Restore Data when restoring a nandroid backup? It seems to be taking a long time
Click to expand...
Click to collapse
15 mins... ish
BTW you don't need to wipe when restoring as it does that for you automatically.
sbdags said:
15 mins... ish
BTW you don't need to wipe when restoring as it does that for you automatically.
Click to expand...
Click to collapse
**** me. Restored back to 4.6.4. Wifi is still broken. Gets to the the "Turning Wi-Fi- on..." screen and never turns on. I am freaking out.
Do you think doing this will work? And if so, how do I start a terminal session?
I've had the Bluetooth not turning on issue four times on my TF101 - the first two times a hard reset (no data loss) fixed it - have you tried this, as opposed to a restart? - and the next two times I just waited and eventually BT turned on. I've never encountered this with WiFI (yet).
In case anyone else encounters this, on a rooted tablet the following might also help:
Open a terminal session and -
su - <enter>
cd /system/bin <enter>
stop bluetoothd <enter>
start bluetoothd -n <enter>
This will force stop and then restart the Bluetooth daemon. I haven't yet worked out (mainly because I haven't need to) what the equivlent process is for WiFi.
wl123 said:
**** me. Restored back to 4.6.4. Wifi is still broken. Gets to the the "Turning Wi-Fi- on..." screen and never turns on. I am freaking out.
Do you think doing this will work? And if so, how do I start a terminal session?
I've had the Bluetooth not turning on issue four times on my TF101 - the first two times a hard reset (no data loss) fixed it - have you tried this, as opposed to a restart? - and the next two times I just waited and eventually BT turned on. I've never encountered this with WiFI (yet).
In case anyone else encounters this, on a rooted tablet the following might also help:
Open a terminal session and -
su - <enter>
cd /system/bin <enter>
stop bluetoothd <enter>
start bluetoothd -n <enter>
This will force stop and then restart the Bluetooth daemon. I haven't yet worked out (mainly because I haven't need to) what the equivlent process is for WiFi.
Click to expand...
Click to collapse
I got that problem before. I believed that this was what I did if you want to try it out:
1. Wipe both Caches and data
2. Restart your system
3. Shut it off again
4. Go to recovery and select the Android for a cold boot
5. Restart it again and it work for me
I don't know why I had to go through that sequences but I seem to work for me, good luck.
LetMeKnow said:
I got that problem before. I believed that this was what I did if you want to try it out:
1. Wipe both Caches and data
2. Restart your system
3. Shut it off again
4. Go to recovery and select the Android for a cold boot
5. Restart it again and it work for me
I don't know why I had to go through that sequences but I seem to work for me, good luck.
Click to expand...
Click to collapse
Thanks im about to try.
Q1: How do you wipe cache and data without reset?
So, Wipe, Restart, Turn back off. Restart into recovery and select android for a cold boot? What do you mean by that?
wl123 said:
Thanks im about to try.
Q1: How do you wipe cache and data without reset?
So, Wipe, Restart, Turn back off. Restart into recovery and select android for a cold boot? What do you mean by that?
Click to expand...
Click to collapse
1. Restart into your recovery, assuming TWRP, and select Wipe option in your recovery
2. When you boot into recovery, there are 3 icons, the middle icon is the android that I am talking about
Hope that helps
LetMeKnow said:
1. Restart into your recovery, assuming TWRP, and select Wipe option in your recovery
2. When you boot into recovery, there are 3 icons, the middle icon is the android that I am talking about
Hope that helps
Click to expand...
Click to collapse
Everytime I restart to recovery, it loads TWRP. I see a little android icon as it is booting, but its not like I can click on him. When I wiped using TWRP, it did a factory reset. I restarted to system, but the damn wifi is still not working. I am so frustrated.
Thank you for your help. I am going to eat and drink a beer and try again later.
wl123 said:
Everytime I restart to recovery, it loads TWRP. I see a little android icon as it is booting, but its not like I can click on him. When I wiped using TWRP, it did a factory reset. I restarted to system, but the damn wifi is still not working. I am so frustrated.
Thank you for your help. I am going to eat and drink a beer and try again later.
Click to expand...
Click to collapse
Hehe, I have been there so many times before. You can use the volume up to select and volume down to confirm. Any way, did you tweak your device before the problem? Did you use D2SD? Maybe you explain a little more details what you did so that people have better understanding of your problem. The worse case is you have to flash the rom again .
LetMeKnow said:
Hehe, I have been there so many times before. You can use the volume up to select and volume down to confirm. Any way, did you tweak your device before the problem? Did you use D2SD? Maybe you explain a little more details what you did so that people have better understanding of your problem. The worse case is you have to flash the rom again .
Click to expand...
Click to collapse
I was not running Data2SD (at least I dont think). I just figured out how to cold boot android. Do you think this could be a hardware issue with my wireless card? It seems to me like it has to be some sort of software bug
wl123 said:
I was not running Data2SD (at least I dont think). I just figured out how to cold boot android. Do you think this could be a hardware issue with my wireless card? It seems to me like it has to be some sort of software bug
Click to expand...
Click to collapse
I had that problem before. Therefore, I am very sure that it is a program bug. Do you use Micro SD in your tablet? When I tweak my tablet, there are all kinds of problems that I have encountered. If you give me some more details, I might be able to help you out.
LetMeKnow said:
I had that problem before. Therefore, I am very sure that it is a program bug. Do you use Micro SD in your tablet? When I tweak my tablet, there are all kinds of problems that I have encountered. If you give me some more details, I might be able to help you out.
Click to expand...
Click to collapse
OK. I was running Chromi-X 4.6.6 ODEX at the time it happened. I used to use a micro sd card but it was acting weird and I took it out. I have been using only the internal SD for the last ~3 months. I use _that/ stock modded kernel variant based from ASUS Stock that comes with the ChromiX mod. I run Apex launcher. Android version 4.2.1.
Using TWRP 2.5 on 10.6.1.14.4 via goomanager.
So far I have tried:
- Flashing ChromiX 4.6.8
- Recovering an old nandroid backup (4.6.4)
- Clearing cache and data via TWRP and restarting with cold boot
wl123 said:
OK. I was running Chromi-X 4.6.6 ODEX at the time it happened. I used to use a micro sd card but it was acting weird and I took it out. I have been using only the internal SD for the last ~3 months. I use _that/ stock modded kernel variant based from ASUS Stock that comes with the ChromiX mod. I run Apex launcher. Android version 4.2.1.
Using TWRP 2.5 on 10.6.1.14.4 via goomanager.
So far I have tried:
- Flashing ChromiX 4.6.8
- Recovering an old nandroid backup (4.6.4)
- Clearing cache and data via TWRP and restarting with cold boot
Click to expand...
Click to collapse
If you don't mind, you can try a clean install.
1. Boot back into twrp and select wipe, use format option instead of wipe
2. Install cromi x, prefer 3.6.5
3. After the installation is completed, restart your tablet and leave it there for a few minutes
4. Make sure that you must SHUT IT OFF COMPLETELY for a few seconds and turn it back on
Hope it will solve your problem, good luck.
LetMeKnow said:
If you don't mind, you can try a clean install.
1. Boot back into twrp and select wipe, use format option instead of wipe
2. Install cromi x, prefer 3.6.5
3. After the installation is completed, restart your tablet and leave it there for a few minutes
4. Make sure that you must SHUT IT OFF COMPLETELY for a few seconds and turn it back on
Hope it will solve your problem, good luck.
Click to expand...
Click to collapse
Regarding #2. Where would I find a download of chromix 3.6.5?
Holy ****.
I just rebooted into TWRP before formating, and then rebooting back to system to save my pictures, and all of a sudden the WiFi is working again. Going to flash the latest Chromi X and see what happens
I was on Cromi-x 4.7 and everything was smooth.i decided to move on and test the new beta 5.
when i flashed everything was normal and i was on haunds kernel 3.2
it suddenly restartet and got stuck on the asus logo.
i tried everything!changing kernel.changed the rom and even went back to the stock rom and none of them worked for me
and now its stuck on asus logo and its in a restart loop....
i'm really disappointed:/
is it a hardbrick or what??
what should i do???
p.s:i have access to my twrp 2.5 recovery..
Can you hold down power and volume down and get to the bootlloader menu? The one with the RCK menu?
sbdags said:
Can you hold down power and volume down and get to the bootlloader menu? The one with the RCK menu?
Click to expand...
Click to collapse
yes
i have access to bootloader and recovery
original1371 said:
yes
i have access to bootloader and recovery
Click to expand...
Click to collapse
Then you are not hard bricked
Which recovery are you using?
Easiest method is probably go into wipes and do a factory wipe, then reinstall the rom but choose that's or my stock kernel and see if that boots first.
sbdags said:
Then you are not hard bricked
Which recovery are you using?
Easiest method is probably go into wipes and do a factory wipe, then reinstall the rom but choose that's or my stock kernel and see if that boots first.
Click to expand...
Click to collapse
thanks for fast reply!
TWRP 2.5
i did that.wiped everything and reinstalled the rom once with That then with stock and last haunds and none of them worked for me!it just freezes on asus logo and restrat and restarts and restarts.:/ any idea?:s
original1371 said:
thanks for fast reply!
TWRP 2.5
i did that.wiped everything and reinstalled the rom once with That then with stock and last haunds and none of them worked for me!it just freezes on asus logo and restrat and restarts and restarts.:/ any idea?:s
Click to expand...
Click to collapse
Try this:
1. Reboot to recovery
2. Select Mount and uncheck System, Cache and Data
3. Go to Advanced, then Terminal Command, then hit Select Folder to start Terminal
4. type "e2fsck -fvyD /dev/block/mmcblk0p8" and press return. Wait for the process to finish (this is for Data)
5. type "e2fsck -fvyD /dev/block/mmcblk0p2" and press return. Wait for the process to finish (this is for Cache)
6. type "e2fsck -fvyD /dev/block/mmcblk0p1" and press return. Wait for the process to finish (this is for System)
Click to expand...
Click to collapse
Then try wiping and reflashing a ROM.
well i am doing what you said
it is in data part for a long time and i am still waiting
hope it works!:-s
original1371 said:
well i am doing what you said
it is in data part for a long time and i am still waiting
hope it works!:-s
Click to expand...
Click to collapse
If you have a corrupted data partition it may take a long time.
sbdags said:
If you have a corrupted data partition it may take a long time.
Click to expand...
Click to collapse
well...that doesnt work:| still freezes on logo and restarts on and on
does formating internal memory help?
any other idea??
original1371 said:
well...that doesnt work:| still freezes on logo and restarts on and on
does formating internal memory help?
any other idea??
Click to expand...
Click to collapse
If you format your internal SD, it will solve a lot of unknown problems that I don't know how to fix or a root cause of it.. However, you will loose all your personal data and files. By any chance do you use 64G external SD?
LetMeKnow said:
If you format your internal SD, it will solve a lot of unknown problems that I don't know how to fix or a root cause of it.. However, you will loose all your personal data and files. By any chance do you use 64G external SD?
Click to expand...
Click to collapse
well.formating will be my last straw i think
no i dont use sd card at all
original1371 said:
well.formating will be my last straw i think
no i dont use sd card at all
Click to expand...
Click to collapse
Can you check this out for me? Boot back into the TWRP and look under Mount to see if any check boxes are unchecked, especially the System.
LetMeKnow said:
Can you check this out for me? Boot back into the TWRP and look under Mount to see if any check boxes are unchecked, especially the System.
Click to expand...
Click to collapse
now i booted back into the twrp and system was unchecked
data and cache were checked
original1371 said:
now i booted back into the twrp and system was unchecked
data and cache were checked
Click to expand...
Click to collapse
It is why that you can not boot into your system because your system was not mounted.. You can try wipe both caches and power off your device completely for about 15 second. You can power it back on with your power button to see if it works..
sbdags said:
If you have a corrupted data partition it may take a long time.
Click to expand...
Click to collapse
If you have lots of files on the data partition, it may take a long time, even if everything is fine.
original1371 said:
well.formating will be my last straw i think
no i dont use sd card at all
Click to expand...
Click to collapse
*sigh*
Everybody should read this: http://forum.xda-developers.com/showpost.php?p=39476212&postcount=4104
LetMeKnow said:
It is why that you can not boot into your system because your system was not mounted..
Click to expand...
Click to collapse
No. The recovery is independent from Android, and Android mounts the system partition itself.
LetMeKnow said:
You can try wipe both caches and power off your device completely for about 15 second. You can power it back on with your power button to see if it works..
Click to expand...
Click to collapse
*sigh*
http://forum.xda-developers.com/showpost.php?p=39473157&postcount=4099
_that said:
If you have lots of files on the data partition, it may take a long time, even if everything is fine.
*sigh*
Everybody should read this: http://forum.xda-developers.com/showpost.php?p=39476212&postcount=4104
No. The recovery is independent from Android, and Android mounts the system partition itself.
*sigh*
http://forum.xda-developers.com/showpost.php?p=39473157&postcount=4099
Click to expand...
Click to collapse
Thanks again _that. I always learn from your post. However, this is not a Development forum and sometime if you are too technical, it is more confused than helping someone else.. It is my two cents.. :fingers-crossed:
LetMeKnow said:
It is why that you can not boot into your system because your system was not mounted.. You can try wipe both caches and power off your device completely for about 15 second. You can power it back on with your power button to see if it works..
Click to expand...
Click to collapse
no,it didnt help!
_that said:
Everybody should read this: http://forum.xda-developers.com/showpost.php?p=39476212&postcount=4104
Click to expand...
Click to collapse
thank for your help.
well,according to your post, my problem is |boot loop| cause its rebooting and never goes further than the asus logo!
so what should i do now? where should i write |adb shell cat /proc/last_kmsg > last_kmsg.txt|?? in fastmode?? where is adb that you are talkin about?
sorry if i sound noob here,i dont have enough info about this
LetMeKnow said:
However, this is not a Development forum and sometime if you are too technical, it is more confused than helping someone else..
Click to expand...
Click to collapse
This is XDA Developers. "XDA Developers was founded by developers, for developers."
I don't expect everyone to be a developer, but I expect people here to have some knowledge about using computers that exceeds clicking icons in Windows and being able to open a browser.
As super mod zelendel wrote, "XDA is a place to come to learn and share your knowledge. If you are not here for those reasons then you are here for the wrong ones.". I know you are here for the right reasons.
If something in my postings is too technical, just ask - I am happy to explain anything.
original1371 said:
no,it didnt help!
thank for your help.
well,according to your post, my problem is |boot loop| cause its rebooting and never goes further than the asus logo!
so what should i do now? where should i write |adb shell cat /proc/last_kmsg > last_kmsg.txt|?? in fastmode?? where is adb that you are talkin about?
sorry if i sound noob here,i dont have enough info about this
Click to expand...
Click to collapse
Time to take a breather anyway, I think. Take this opportunity to learn the basics about adb. You can start here:
http://forum.xda-developers.com/showthread.php?t=2303834
If you get stuck, just ask.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Usually a data format and reflash of system will fix this type of bootloop. You didn't by any chance flash a new bootloader did you when you were trying to fix it? Have you tried restoring a nandroid at all?
I'm all out of ideas. I've fixed many bootloops now so we should be able to get you up and running but something doesn't quite compute.....
Had the device since release. However when I open the camera setting it won't open .
I tried to clear app cache, restart phone. Wipe device charge and still won't open :/
Anyone faced such thing or have idea how to fix this
duellist said:
Had the device since release. However when I open the camera setting it won't open .
I tried to clear app cache, restart phone. Wipe device charge and still won't open :/
Anyone faced such thing or have idea how to fix this
Click to expand...
Click to collapse
Have you disabled any apps?
airmaxx23 said:
Have you disabled any apps?
Click to expand...
Click to collapse
No, the camera is working fine but I can't seem to open the settings
Likely a settings misconfiguration... look long and hard.
Clear cam data; it may have become corrupted.
You can try taking cam back to factory load if that's an available option.
You cleared the system cache on the boot menu right?
Try a hard reboot as well.
Do not reload unless it's an old load as it will likely only happen again; try to find the cause.
blackhawk said:
Likely a settings misconfiguration... look long and hard.
Clear cam data; it may have become corrupted.
You can try taking cam back to factory load if that's an available option.
You cleared the system cache on the boot menu right?
Try a hard reboot as well.
Do not reload unless it's an old load as it will likely only happen again; try to find the cause.
Click to expand...
Click to collapse
I believe its a miconfiguration as well but can't put my hands on it.
Can you instruct me to troubleshooting steps
I cleared system cache on boot menu. Nothing happened
What do you mean by old load? I am not aware of this.
duellist said:
I believe its a miconfiguration as well but can't put my hands on it.
Can you instruct me to troubleshooting steps
I cleared system cache on boot menu. Nothing happened
What do you mean by old load? I am not aware of this.
Click to expand...
Click to collapse
The OS ie load. Clear the camera app data not just it's cache.
Hopefully that will get it.
Is there no way to clear the cache partition? I wanted to do this because my lockscreen lags when hitting the button and when using my thumbprint after the most recent update. Asus told me to factory reset.
ziptrip said:
Is there no way to clear the cache partition? I wanted to do this because my lockscreen lags when hitting the button and when using my thumbprint after the most recent update. Asus told me to factory reset.
Click to expand...
Click to collapse
I have the issue on my phone, what I did is that I change the phone's Theme to a static(non-animated) theme and restarted the phone. it solved for mine.
It's not on the boot menu, it's in settings under storage.
RogPhone whipe cache
Sorry, how to wipe cache on rog phone? Thanks
forum.xda-developers.com
power off hold volume button up and power chose recovery menu with vol up and down buttons press power to confirm then factory reset i done this after a update to the latest ww firmware.
jutley said:
power off hold volume button up and power chose recovery menu with vol up and down buttons press power to confirm then factory reset i done this after a update to the latest ww firmware.
Click to expand...
Click to collapse
That's the nuke approach... and not desirable.
Find it in Settings under storage.
All Android smartphones have a way to clear the system cache that I'm aware of.
Some like Samsung are on the boot menu, others in the software like this one.
I am not using an animated theme. Rebooting has solved this in the past, but it's not working anymore.
There is no option in settings under storage. Can you elaborate on this maybe?
I'm trying to avoid a factory reset... It would be a pain.
ziptrip said:
I am not using an animated theme. Rebooting has solved this in the past, but it's not working anymore.
There is no option in settings under storage. Can you elaborate on this maybe?
I'm trying to avoid a factory reset... It would be a pain.
Click to expand...
Click to collapse
Try tapping the different buttons on that page for a drop down menu.
Try search function...
Play with it.
Or start searching Google like I did, then Bing, then...
Try a hard reboot too.
There is no way to clear the cache that I can find. I ended up factory resetting, and it fixed it. I just hope it doesn't happen again
ziptrip said:
There is no way to clear the cache that I can find. I ended up factory resetting, and it fixed it. I just hope it doesn't happen again
Click to expand...
Click to collapse
Sorry, wrong device... my bad
It's in Settings under storage somewhere.
On Samsung's it's on the boot menu as well in Device Care.
ziptrip said:
Is there no way to clear the cache partition? I wanted to do this because my lockscreen lags when hitting the button and when using my thumbprint after the most recent update. Asus told me to factory reset.
Click to expand...
Click to collapse
why on earth u dnt flash OMNI?
I don't know what Omni is, but I was able to fix the use by clearing the cache on the Asus Launcher. I was using Nova launcher, but I still had to clear the cache on the Asus Launcher to fix the lock screen lagging issue.