hey guys, my problem is that my recovery freezes after 10 or 15 seconds. it was all good until 3 month ago when randomly start to freeze. now it doesn't matter which recovery im using (i tried all of them) it freezes. sometimes i reboot to recovery and it works fine and i can flash a rom or whatever i want to do, but most of the times it freezes.
i tried wiping everything several times, including internal storage and even external storage.
at the moment every time that i want to try a new rom i need to spend about 30 min rebooting over and over again until i can flash the rom. if is an action that last less than 10 or 15 seconds is all good, like flashing another recovery or just wiping cache, but long actions like flashing gaps or rom it doesn't work cause it takes more than that.
im not an expert on android but the only thing that i can think on is that even wiping everything there is still a file or something that is [email protected](#ing with the recovery, but i don't know maybe my phone is f^(#ed.
please help, i don't want to get another phone, i love this one.
by the way, is a note 2 GN7100 international.
thanks
Related
I brought my Nexus Prime from Korea last month.
A few hours ago I was listening to music on my phone when it rebooted. After that it came back on for roughly 10 seconds before rebooting again.
I uninstalled a game from my phone roughly 30 minutes before this error happened.
I cannot use my phone now, I get a few seconds of use out of it before its stuck in a continuous reboot cycle.
I have tried letting it cool down (it was a hot day), removing the simcard and changing batteries. Not sure what else I can do with only a few seconds of use.
Model number - SHW-M420S
Is anyone able to help me get out of this reboot cycle?
Try to back up important things and do factory reset. Is your phone rooted? CWM recovery installed? If so, before doing factory restore you could try wiping cache/dalvik cache first.
Sent from my super Galaxy Nexus plus®
Luckily its still a new phone, so there isn't much on it.
The phone is rooted in that I cannot access it in any way. Even connecting to a computer is useless as its only on for a few seconds before it reboots itself.
CWM recovery isn't installed, will be when the phone is working again though!
Is there a way to wipe the cache/dalvik cache or factory reset while the phone is off?
fastboot will allow you to erase data,userdata, as well as flash a custom recovery like cwm or a full rom.
bk201
edit: boot your device with POWER+VOLUP+VOLDOWN into fastboot. search google and/or xda for some fastboot tutorials.
I had this problem awhile back. It was a bum phone with hardware issue. I had to exchange it. Yours may be in the same boat.
I will try a fastboot later today and let you know the outcome, thank you.
If all else fails I'll send it back to Korea for new hardware I guess.
I ran into this problem a while ago. I had to restore the phone to stock using the image from Google. Haven't had a problem since
I have seen some threads from a month ago but does anyone else still have really long boot times on CM10?
I'm talking like almost 5 minutes probably to boot up the phone.
It happens whether I pull the battery or just do a soft reboot from the menu.
I've always had it but I have upgraded to the newest bootloader that I know about and it is still happening?
Half of the boot is spent at the google bootloader screen and half is on the CM10 boot screen.
Is everyone else getting the same thing or is it just me?
That's definitely abnormal. I've never experienced boot times nearing that long, even after a clean flash, or flashing from a different ROM.
I'd try a completely clean install, including formatting /system.
Edit: a logcat would likely point to the problem if it remains.
CMNein said:
That's definitely abnormal. I've never experienced boot times nearing that long, even after a clean flash, or flashing from a different ROM.
I'd try a completely clean install, including formatting /system.
Edit: a logcat would likely point to the problem if it remains.
Click to expand...
Click to collapse
Definitely abnormal. I would say mine is booted in under 30 seconds. 40 if its a long boot. I agree run a logcat and see what it says
Try logcat or /proc/kmesg indeed. First time boot after wiping Dalvik cache takes more time since Android needs to rebuild it, but after that it should boot normal.
I had Android 4.1.1 installed on a rooted Sprint Galaxy S3 with ClockworkMod. Someone recommended TWRP, so I installed it and used the backup feature, thinking I was completely covered if my foray into ROM flashing on the SGS3 went awry.
So I booted to TWRP, did a "Wipe Data/Factory Reset", and installed the "Blazer" ROM; didn't like it. So I TWRP'ed again, wiped it and flashed CyanogenMod 10.1. Didn't like it either. So I went back into TWRP, did the "Wipe Data/Factory Reset" again, and restored my backup.
When it finished rebooting, it was good for like 20 seconds. I left it on the "lock" screen, and the date reverted back to Dec 24th at some ungodly hour (4 am?). It wouldn't unlock. After less than a minute, it reboots. It kept doing this.
I had a hard time getting back *into* TWRP. I kept getting this weird picture of the battery (?) and the phone kept buzzing every 10 seconds or so. The battery had at least 30% charge. Eventually, by taking the battery out, I was able to get back into TWRP.
Tried it again 2 or 3 more times with the same result. This last time, I immediately got off the lock screen and let it "sit". It has been stable for 10 hours now.
Any idea what's going on?
(If I'm leaving out important information, I apologize. Please let me know and I'll add it.)
Something wrong happened in the restore process. Just make sure that you have at least 80% battery next time.
Sent from my SPH-L710
Thanks.
If I keep restoring it over and over again, is there a chance it will "take" one of these times?
Ok so, check the size of your backups and make sure that they are consistent (for the same ROM types)
I've seen an issue where someones recovery got corrupted, and all restores made with the corrupted recovery were unnaturally small and would bootloop once done restoring
Reflashing your recovery (i recommend through ODIN from a PC) should fix it if this is the issue
Please bare with me, I'm trying to think of every possible detail for anyone to help me with this....
My brother gave me his Note 2 to "fix" because it was stuck in a boot loop and would randomly freeze. It was 100% stock, unrooted and less than a year old. The problem started when the phone auto-updated to 4.4.2. After investigating and tinkering around, I got it out of the boot loop (I just wiped the cache). Upon reboot, the phone would function normally for up to 90 seconds (approx) then freeze. The only way to unfreeze was to battery pull, holding the power button down didn't work. After repeating the reboot process several times I realized that each time it attempted to do a system update. I looked for a way to disable the auto-update feature and was unable to find it.
My next thought went to rooting and flashing a custom ROM. After all, if the problem was with the stock, flashing would fix that. I have rooted, installed philz recovery and flashed the Alliance ROM. I wiped all cache and booted her up. To my dismay, it's still freezing. I've gotten past the boot screen and am now freezing in different places on the "android is upgrading" screen. Each freeze causes me to have to battery pull and start over.
I am out of ideas. I would like to be able to fix this phone and put service on it. Thank you in advance for all help!
-Amy
Nerdmom3 said:
Please bare with me, I'm trying to think of every possible detail for anyone to help me with this....
My brother gave me his Note 2 to "fix" because it was stuck in a boot loop and would randomly freeze. It was 100% stock, unrooted and less than a year old. The problem started when the phone auto-updated to 4.4.2. After investigating and tinkering around, I got it out of the boot loop (I just wiped the cache). Upon reboot, the phone would function normally for up to 90 seconds (approx) then freeze. The only way to unfreeze was to battery pull, holding the power button down didn't work. After repeating the reboot process several times I realized that each time it attempted to do a system update. I looked for a way to disable the auto-update feature and was unable to find it.
My next thought went to rooting and flashing a custom ROM. After all, if the problem was with the stock, flashing would fix that. I have rooted, installed philz recovery and flashed the Alliance ROM. I wiped all cache and booted her up. To my dismay, it's still freezing. I've gotten past the boot screen and am now freezing in different places on the "android is upgrading" screen. Each freeze causes me to have to battery pull and start over.
I am out of ideas. I would like to be able to fix this phone and put service on it. Thank you in advance for all help!
-Amy
Click to expand...
Click to collapse
Make sure you are using philz recovery (6.07.9 recommended). You will need to wipe the internal sdcard. Go under mounts option and select wipe /data /data/media option then go to reboot menu and reboot recovery. Now install rom and see how if that works.
Sent from my SPH-L900 using XDA Premium 4 mobile app
jlmancuso said:
Make sure you are using philz recovery (6.07.9 recommended). You will need to wipe the internal sdcard. Go under mounts option and select wipe /data /data/media option then go to reboot menu and reboot recovery. Now install rom and see how if that works.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you!
I wiped the internal SD. That enabled me to format the phone then install the Liquid Smooth ROM. So far so good. It's been 48 hours with no problems.
Thanks again for your help!
SO, long story short here, new Note 3 less than a week old. rooted just fine, flashed TWRP 2.8.1.0, again no issues. .. here is where things get weird. If I run a factory reset through TWRP or any recovery that I had tried it will hit the cache and take up to a full minute before it finishes with the cache. ROM installs will sometimes take a few mins.. AOSP depending on what builds they are will either fly right through the install or sit for up to a min or 2 before it even starts.
TW ROMs with the exception of Stock, will not have an extended power menu, if I hold the power button as per usual, it will just force a hot reboot. Now, had noticed that if i use MTP and it fails during a transfer, that causes internal storage to lock up. It is then inaccessible to the system . Once this happens, the expanded power menu works. this remains true on all modded TW builds, and on SOME AOSP builds.
If it is flat out stock or stock rooted, this problem does not exist. any suggestions on this?
Also, I understand this is a rambling of crap, but any help is appreciated. I am a 6 year veteran with Android so I am no stranger to flashing, odin, and brick recovery.