Hi,
I updated my P7510 to the official ICS rom the other day, and since then I have been having a problem.
If I leave the tab alone for a bit (on the charger or not), it powers off completely. And I don't just mean that you have to just press the button shortly to restart it, no I have to keep the power button pressed for ~10 seconds for it to boot to the loader (battery icon appears) and then press it again for a few seconds to actually boot ICS.
I have CWM 5.8.3.1 and I did a dalvik clean and a cache partition format, but it made no difference. I am a bit hesitant to do the full factory reset as that will clear all the storage and it will take some time to restore more then 20GB of data.
I have the official ICS and don't have that problem. I'm not rooted at this time and not using CWM so I assume it has something to do with that.
I have the same problem and mine is running stock, un-rooted.
kungfoofool said:
I have the same problem and mine is running stock, un-rooted.
Click to expand...
Click to collapse
did you do a factory reset as part of your upgrade?
I will probably do it a bit later, to see if it fixes this very annoying problem.
I bit the bullet and installed ICS on mine the other day. Mine is currently rooted with CWM and I am not experiencing that problem.
It did boot up after the install and I still had all my data and apps but chose to do a full wipe anyway just to be safe and start fresh. All I really lost was the music I had loaded and, other than the time it will take, that can be reinstalled w/o any problems.
robert__ said:
Hi,
I updated my P7510 to the official ICS rom the other day, and since then I have been having a problem.
If I leave the tab alone for a bit (on the charger or not), it powers off completely. And I don't just mean that you have to just press the button shortly to restart it, no I have to keep the power button pressed for ~10 seconds for it to boot to the loader (battery icon appears) and then press it again for a few seconds to actually boot ICS.
I have CWM 5.8.3.1 and I did a dalvik clean and a cache partition format, but it made no difference. I am a bit hesitant to do the full factory reset as that will clear all the storage and it will take some time to restore more then 20GB of data.
Click to expand...
Click to collapse
If you wipe data through cwm, only apps will be deleted. /sdcard will remain untouched.
Sent from my amazing 10.1 galaxy tab
Panos_dm said:
If you wipe data through cwm, only apps will be deleted. /sdcard will remain untouched.
Sent from my amazing 10.1 galaxy tab
Click to expand...
Click to collapse
Yeah I noticed. I ended up doing a 'factory reset' and the /sdcard contents was untouched. And it seems to work better afterwords, although I did still encounter once that it had shut itself down.
robert__ said:
Hi,
I updated my P7510 to the official ICS rom the other day, and since then I have been having a problem.
If I leave the tab alone for a bit (on the charger or not), it powers off completely. And I don't just mean that you have to just press the button shortly to restart it, no I have to keep the power button pressed for ~10 seconds for it to boot to the loader (battery icon appears) and then press it again for a few seconds to actually boot ICS.
I have CWM 5.8.3.1 and I did a dalvik clean and a cache partition format, but it made no difference. I am a bit hesitant to do the full factory reset as that will clear all the storage and it will take some time to restore more then 20GB of data.
Click to expand...
Click to collapse
kungfoofool said:
I have the same problem and mine is running stock, un-rooted.
Click to expand...
Click to collapse
I have the same issue...
It seems there is no fix for it..
-TB-
Related
Hello i have a serious problem
I have infinite bootloop in every ROM, every baseband/radio, and in stock. I tested the (4.2, 4.4, 5.0) and any of this works. I wiped the system/data/cache/dalvik a lot of times and installed the CM11 in 4.4 baseband but still not working.
The bootloader is unlocked and fastboot working well. I spent all the day testing solutions of my knowledge but dont work.
Any idea?
ChameleonGeek said:
Hello i have a serious problem
I have infinite bootloop in every ROM, every baseband/radio, and in stock. I tested the (4.2, 4.4, 5.0) and any of this works. I wiped the system/data/cache/dalvik a lot of times and installed the CM11 in 4.4 baseband but still not working.
The bootloader is unlocked and fastboot working well. I spent all the day testing solutions of my knowledge but dont work.
Any idea?
Click to expand...
Click to collapse
Have you tried just flashing the full factory images? Or booting TWRP via fastboot and looking at the results of a manual wipe to ensure all partitions are "good"? Often when I hear about an "infinite bootloop" on every rom, it means the internal storage is bad, sometimes flashing the factory images helps, and sometimes it's just time to put the poor thing to rest... :/
acejavelin said:
Have you tried just flashing the full factory images? Or booting TWRP via fastboot and looking at the results of a manual wipe to ensure all partitions are "good"? Often when I hear about an "infinite bootloop" on every rom, it means the internal storage is bad, sometimes flashing the factory images helps, and sometimes it's just time to put the poor thing to rest... :/
Click to expand...
Click to collapse
I solved it with a rare solution, i install the stock Android L wait for the bootloop and i press the power button until the phone power off later i restart and works and it works in every stock ROM. Sounds weird but works.
ChameleonGeek said:
I solved it with a rare solution, i install the stock Android L wait for the bootloop and i press the power button until the phone power off later i restart and works and it works in every stock ROM. Sounds weird but works.
Click to expand...
Click to collapse
Definitely weird... How long are you waiting for this "bootloop"? The reason I ask is because the first boot on lollipop takes an extremely long time since it is ART, 10-15 minutes for first clean boot, or over 30 minutes with a dirty flash isn't unheard of, and the first boot doesn't give the "Android is updating", just the swirling circles, if you interrupted it you could have other issues later on.
acejavelin said:
Definitely weird... How long are you waiting for this "bootloop"? The reason I ask is because the first boot on lollipop takes an extremely long time since it is ART, 10-15 minutes for first clean boot, or over 30 minutes with a dirty flash isn't unheard of, and the first boot doesn't give the "Android is updating", just the swirling circles, if you interrupted it you could have other issues later on.
Click to expand...
Click to collapse
I wait several times more than 10 minutes. I wipe data/cache after restart the phone. I found the solution in Google Forum: https://productforums.google.com/forum/#!topic/nexus/D2vKK9rLgh8[1-25-false]
You should only have to wipe /cache from recovery to get out of it. I believe wiping /data is unnecessary (so you can avoid losing your data if you are concerned.
Hello everyone,
So here's my story: I got a 6P short after release and it's been amazing. After switching from a S6 I couldn't be happier until 3 days ago.
I was playing around with my phone (checking for updates on the play store if I recall correctly) and I was going to switch from 4g to wifi. I went ahead and pulled down my notification shade and went to press WiFi but misclicked and hit Hotspot which was below it. My phone suddenly froze big time and this is for the first time ever since purchase.
At first I thought I'd wait it out since the device was completely unresponsive, home button didn't work and neither did anything on screen. Buttons didn't make a difference either. 10 minutes went by and I ended up force restarting by holding down power + volume up. First part of my bootup went fine but when it got to the android boot animation after I put in my pin to allow the device to start it dropped from the smooth usual framerate down to 1 frame every 10-15 seconds and it slowed down further until it came to a complete halt around the time the android letters appear.
My first thought was corrupt rom so I went ahead and wiped data from the stock recovery. I was running completely stock with no modifications whatsoever. That didn't do anything. Phone still froze in the same boot phase. Desperate I unlocked bootloader to flash a clean fresh image to try to fix it and to my surprise that didn't change a thing.
As I was getting pretty desperate already I had one more idea and that was to flash up to the Dev preview. To my huge surprise it booted and I jumped from excitement. So I started setting up my phone again. I got past the prompt to insert sim card and I was now at the screen to choose a wifi network. As soon as I clicked into that the phone froze up again and at that point I lost all hope.
I wiped data in stock recovery and shut the phone down for the night. On day 3, today I woke up and tried starting the phone and it worked as if nothing had happened. I went through the setup and set up my phone on the N preview. At a certain point I was planning to go back to the latest official build but for now I was happy my phone was back from the dead. Later today I tried to restart my phone to clear all running apps etc and it froze up on boot.
I'm losing all hope that I'll be resolving this myself so I'm reaching out to the community to see if anyone's had this happen to them before and hopefuly for a solution. It's still under warranty so I can eventually send it back to the retailer but I'd rather not have a phone for 3 weeks.
Any and all help is appreciated.
Thank you for reading through my long and probably pretty boring story!
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
To the OP, is there any reason you did not flash to release version 6 instead of Dev preview ?
Also, any reason you can not simply do the "unenroll" from https://www.google.com/android/beta ?
It will require you to setup certain settings again as you will be back to a "factory reset".
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
DJBhardwaj, i haven't specifically erased those partitions. I was under the impression wipe userdata along with reflashing did that. I will try that tonight when I get home!
Xdafly, I only updated up to N as a last resort because at first I had a locked BL. I was planning to unenrol but that would've been too late as it self bricked after a restart.
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
Well I just did the erase thingy and my phone booted but wifi won't turn on. Enabling hotspot doesn't brick anymore but I now suspect WiFi might've been the issue. Any tips on how to find out what it could be and possibly fix it?
Edit: 2 restarts and a factory reset later I'm back to bricked same way as before.
try safe mode
mr.dj26 said:
try safe mode
Click to expand...
Click to collapse
That was my first thought, that was the restart that bricked it again. Safe mode shouldn't have made a difference since I hadn't even logged into Google account for apps.
After reading the very first post; sounds like bad WiFi hardware.
All the hanging has been related to WiFi or Hotspot.
I think you should get a replacement
Sent from my Purified NexusixP
If Someone Helped You Then Dont Just say Thanks...Hit The Thanks Button!
Is your phone rooted and did you install Xposed?
Over the weekend I shutdown my 6p (stock rooted with April security patch, Xposed v80) and charged it. When it turned it back up I kept getting "Unfortunately, nfc service has stopped". Long story short: I ended up factory reset my phone and reinstalled EVERYTHING and I still got into bootloop. Then I came across
https://github.com/rovo89/Xposed/issues/113
https://github.com/rovo89/android_art/issues/28
At the end of the second post rovo89 (developer of Xposed) fixed the bug in V83. I wiped my 6p once more and installed everything with v83. Problem solved.
Good luck!
I just received the OTA upgrade to 7.0 and installed it. Now every time I want to use the phone I need to wait 5-10 seconds for the screen to turn on. This happens both after I press the power button or if I use the fingerprint reader. I've tried clearing the cache partition but that did not help. I've found a couple reddit threads from earlier this month but nobody seems to have a solution.
I had this same problem. I tried a bunch of things but ended up doing a clean wipe. It's working great now. Sorry I don't have better news.
gthing said:
I had this same problem. I tried a bunch of things but ended up doing a clean wipe. It's working great now. Sorry I don't have better news.
Click to expand...
Click to collapse
That's unfortunate. Is a 'clean wipe' the same thing as choosing a 'factory data reset' from the backup & reset menu?
Well just to follow up, here are the things I tried:
- Factory wipe while on Nougat. Didn't help. When I booted the phone and pressed the power button during the signup process, it still took 5-10 seconds for the screen to turn back on.
- Unlock the phone and re-install the NRD90U OTA via ADB. Didn't help, same as above.
- Reinstall the factory image for NRD90U. Didn't help.
- Reinstall the factory image for MTC20L. Phone was back to normal operation. Screen turned on immediately after pressing power button. Camera functional. Auto-rotate functional.
Don't know what's wrong with my phone and nougat, but I guess I'll wait for some kind of future release.
I have that too, but it only happens when phone has been sleeping for a while. Doze on the go may be causing it?
The problem was happening for me right from the initial set up your phone screen after a fresh install as well as after the phone had been on for some time, so I don't think it was doze.
Hi guys
i have a custom rom, nougat 7.1 installed and its been working fine. last night i installed an aftermarket battery replacement as the other wasnt holding a charge. after turning on by simply pressing the power switch it went straight to twrp recovery and kept doing so. this morning i cleared the cache and data to start again which was a bit of hassle and it then booted fine. however, i just restarted again and its in the same loop.
i have checked for any obvious obstruction under the rear case that could be pressing against the volume keys but there isnt anything.
any ideas?
cheers
Did you try to reflash everything, e.g. also the ROM?
AndDiSa said:
Did you try to reflash everything, e.g. also the ROM?
Click to expand...
Click to collapse
i didnt really want to do that unless i really had to. as i say, before the battery swap it was fine
But if you cleared already cache *and* data all your data is already lost, e.g. it's like a factory reset. So flashing a new ROM will not worse the situation ...
AndDiSa said:
But if you cleared already cache *and* data all your data is already lost, e.g. it's like a factory reset. So flashing a new ROM will not worse the situation ...
Click to expand...
Click to collapse
well, i just went to restart and was going to reinstall but it booted properly. i then did a restart and again it booted fine. i dont get it.
Classic "my phone keeps freezing and rebooting". I am quite in the know about flashing roms and such.
It started on the stock firmware 6.1.1 (i think it was). I dd factory resets, cache wipes the lot. It would still randomly reboot.
So i flashed Telstra version of 7.0. Still froze every now and then. Did the same things as above.
Flashed TWRP and wiped everything, flashed Renovate Rom and the bootloader for it, Still did it. Numerus factory resets and wipes of everything. It would freeze at any point from startup, to having setup the phone and making phone calls or on facebook or whatever. It would even freeze in twrp, or loading twrp.
I found that the data partition was corrupt so i re partitioned to ext4. Still nothing. I reformatted every partition so the phone was a complete brick with nothing on it and after flashing clean again it would still do it.
Whats the issue that I'm missing, or is there a way to log so i can find where it keeps getting stuck? It gets hot and blue light flashes and i have to hard reset it or sometimes i have to let the battery drain so i can turn it back on again.
pls help?
Hmm i will give you an advice so you dont have to wait for your battery to drain...just press volume down and power button for like 5 secs and phone will force boot. Anyway back to your problem...did you tried flashing latest stock samsung firmware?
raz_il_dio said:
Hmm i will give you an advice so you dont have to wait for your battery to drain...just press volume down and power button for like 5 secs and phone will force boot. Anyway back to your problem...did you tried flashing latest stock samsung firmware?
Click to expand...
Click to collapse
This advice doesn't work with my phone even with holding the buttons for 30 secs and more. For rebooting I can only wait until the battery is completely drained. With little hope for another way shortening time to the next reboot any help is appreciated.
Same here...experiencing the same prob...
Same problem.
Sent from my Redmi Note 4 using Tapatalk
smallcapsicum said:
Classic "my phone keeps freezing and rebooting". I am quite in the know about flashing roms and such.
It started on the stock firmware 6.1.1 (i think it was). I dd factory resets, cache wipes the lot. It would still randomly reboot.
So i flashed Telstra version of 7.0. Still froze every now and then. Did the same things as above.
Flashed TWRP and wiped everything, flashed Renovate Rom and the bootloader for it, Still did it. Numerus factory resets and wipes of everything. It would freeze at any point from startup, to having setup the phone and making phone calls or on facebook or whatever. It would even freeze in twrp, or loading twrp.
I found that the data partition was corrupt so i re partitioned to ext4. Still nothing. I reformatted every partition so the phone was a complete brick with nothing on it and after flashing clean again it would still do it.
Whats the issue that I'm missing, or is there a way to log so i can find where it keeps getting stuck? It gets hot and blue light flashes and i have to hard reset it or sometimes i have to let the battery drain so i can turn it back on again.
pls help?
Click to expand...
Click to collapse
Sounds like you need your motherboard replaced i had the same issues on marshmallow thought the nougat update would fix it but realized it was a hardware fault not software..left it in store to get fixed and on repair sheet it said faulty motherboard..
Sent from my SM-G935F using XDA-Developers Legacy app
As i know some S7 have motherboard hardware problem, mine has too, what help? warranty and they replaced motherboard. But if you root, you can say good bye to warranty, they look at knox first with this problem.