Hi all,
Need some help with a boot freeze.
I flashed my N7000 to Slimbean 4.3 last year and put in CWM 6 (can't remember version).
Earlier today, I powered up the phone (after a complete battery drain followed by a full charge). The boot got stuck at the Slimbean glowing logo. Then I went into recovery to clear dalvik cache, reboot. The phone is still stuck at the glowing logo.
What is my next best way to get out of the boot freeze without losing my SMS, photos and documents on my phone? I do not use an external micro SD card for my photos. The 16GB on my phone is still left with 8GB.
TIA to all.
Doing a factory reset in cwm shouldn't delete your photos or documents. But it will wipe your MMS/SMS. Just don't format emmc/sd
Sent from my Nexus 5 using Tapatalk
Related
Before I startת I tried to find this problem also search on Google and here but could not find any information about this problem.
This night I did not put the device to a charger because he had already 90% battery, so I left it disconnected,in the morning I got up I saw the phone is turn off, I tried to turn the phone light up and the ATT screen turn on,
I went and when I came back after 10 minutes I saw that the phone is still stuck on the "Galaxy S" screen.
I removed battery, changed, and it's still stuck.
I'm running version CM7.1,
The phone can get into the recovery menu.
Can anyone help me?
I do not understand in the android system and I don't have any backups of my pictuers...
Any chance to save the phone?
update: I search for a solution, and found on the CWM the option of "Mount USB storage" and I copied my pictures to my computer...
so now my new question is how can I get the phone to turn on again? only format and install new rom?
I can use CM7.2 zip file and install via the recovery menu?
you can go to cwmr and can do a data wipe which will uninstall all your apps and data but will not touch your sdcards
You won't lose your pictures on the sd card. If you are still stuck, try wiping dalvik cache from recovery
Sent from my ICS Samsung Captivate
I have a similar problem. Like eidoll32, I did not plug in my cappy and when I went to turn it on the next day, I was only able to get a boot loop at the AT&T screen. Currently, I cannot get into recovery, but only download mode.
I originally rooted the phone with the Galaxy_One_Click_Root tool, and installed CyanogenMod 7.1 for the captivate, when CM7.2 went to RC1, I flashed that from CWM, doing a full wipe. Later I wanted to try ICS, so I flashed AOKP - captivatemtd - M5 b30, doing a full wipe (twice).
That's where I was when this happened, and where I am now.
I would have never thought that I could brick my device without... doing something wrong. Here I come, completely helpless at this point.
Earlied today the phone had worked just fine until I turned 3G on, it wouldn't actually turn it on. I tried Aeroplane mode which didn't help, so I held power button and chose to reboot. This is when the problem starts. The phone booted itself successfully through its logo, then Devilkernel logo, and lastly showed the GamerzROM logo (which is actually the Nexus logo) and kept showing this flashing logo forever. Even after 30 minutes.
CWM works just fine.
I noticed that while booting it makes a single loop (Samsung logo -> Devil logo -> Samsung logo -> Devil logo -> Nexus logo).
I've wiped partition cache and dalvik, put the ROM and Gapps on external sd and flashed again. Nothing changed.
I am also worried about the battery - when I plug the charger the device turn on (the way mentioned above) and I have no idea whether it's charging or not, at the moment I am at 24% of battery so it's risky to flash without a charge.
Please, I need some advice to fix this, without loosing my data on the phone. I could flash another ROM, but that obviously means data/factory reset.
Thank you in advance!
EDIT: I've just checked in CMW and the phone is actually charging. Battery percentage rose up.
Have you tried to return to stock ROM ?
Sent from my GT-I9000 using xda app-developers app
I've made a nandroid backup to a external SD and wiped data. The phone "amazingly" works, although I've lost all my configuration and data (maybe I'll retrieve it somehow from the backup files).
Must have been corrupted files or something.
Hmmm im running gamerzrom too since first day and i didnt have anything like this.
Did you change/update kernel?
Sent from my GT-I9000 using xda app-developers app
Nope, I didn't touch anything. Just changed the DPI once I flashed the ROM.
Well I couldn't have said a bad word about GamerzROM until yesterday's incident.
Hope it never happens again.
Hi,
Device: I9000 International
Samsung firmware 2.3.6
Tried to flash a different ROM.
Made full WIPE, factory reset, etc.
After the first flash the device loads OK, but once I reboot it, the Samsung Logo starts to re-appear as a boot loop (sometimes 1-2 times till it goes up and sometimes more (even 10-20 boot loop) till I give up )
The internal SD card was formatted, PIT was done as well, and I have no idea why this is happening even if I switch to different ROMs.
Any help / advice would be highly appreciated.
Tnx,
wipe system?
Sent from my GT-I9000 using Tapatalk
Hi.
Since yesterday my galaxy s3 lte i9305 does not boot anymore, the blue cyanogenmod logo keeps turning for hours. I can however still go to the recovery (which was a few month old cwm). I completely wiped the phone (both caches, data, internal sd, boot, firmware etc ... all but the modem) and reinstalled the newest cwm and the newest nightly build three times now using heimdall and the external sd (connected my external micro sd to my computer sd card reader via adapter and put the zip on it). Just now I installed twrp-2.8.5.0-i9305 as a new recovery and installed everything again, but everytime - and also now - despite the seemingly successful installation, the phone is stuck at the cyanogen bootlogo.
Any ideas on how to get my phone running again?
Cheers
ScPo said:
Hi.
Since yesterday my galaxy s3 lte i9305 does not boot anymore, the blue cyanogenmod logo keeps turning for hours. I can however still go to the recovery (which was a few month old cwm). I completely wiped the phone (both caches, data, internal sd, boot, firmware etc ... all but the modem) and reinstalled the newest cwm and the newest nightly build three times now using heimdall and the external sd (connected my external micro sd to my computer sd card reader via adapter and put the zip on it). Just now I installed twrp-2.8.5.0-i9305 as a new recovery and installed everything again, but everytime - and also now - despite the seemingly successful installation, the phone is stuck at the cyanogen bootlogo.
Any ideas on how to get my phone running again?
Cheers
Click to expand...
Click to collapse
I would try a factory reset from recovery and see if that helps. You did check the md5 for your downloads right?
Otherwise I would install the stock rom, then try again, this time(making sure you have a compatible recovery) just wipe caches, data, and format system, and then install CM
noppy22 said:
I would try a factory reset from recovery and see if that helps. You did check the md5 for your downloads right?
Otherwise I would install the stock rom, then try again, this time(making sure you have a compatible recovery) just wipe caches, data, and format system, and then install CM
Click to expand...
Click to collapse
I did do the factory reset. I just wiped the areas separately as well. Anyway, I took your advice and installed the latest stock rom. Now I got the Samsung logo slightly flashing blue for hours instead of the cyanogenmod logo. Did not do anything else.
I suspect that its a battery issue in some way. The last weeks the phone lost its charge very quickly very often (not constantly though). Yesterday, the phone was in my pocket and then went off. It went into the constantly trying to restart despite the lack of batteries state until I removed the battery. Maybe that gives any clue?
ScPo said:
I did do the factory reset. I just wiped the areas separately as well. Anyway, I took your advice and installed the latest stock rom. Now I got the Samsung logo slightly flashing blue for hours instead of the cyanogenmod logo. Did not do anything else.
I suspect that its a battery issue in some way. The last weeks the phone lost its charge very quickly very often (not constantly though). Yesterday, the phone was in my pocket and then went off. It went into the constantly trying to restart despite the lack of batteries state until I removed the battery. Maybe that gives any clue?
Click to expand...
Click to collapse
Try booting into stock recovery, then factory reset from there. Last time I went back to stock I had a bootloop until I did this, then it booted properly. If that doesn't work, maybe try new battery.
Have you tried booting up whilst plugged in to a usb charger?
noppy22 said:
Try booting into stock recovery, then factory reset from there. Last time I went back to stock I had a bootloop until I did this, then it booted properly. If that doesn't work, maybe try new battery.
Have you tried booting up whilst plugged in to a usb charger?
Click to expand...
Click to collapse
Thanks for your helpful input.
I did what you said, even tried it twice now. Phone is still booting after 20 minutes now. I also tried booting up while charging the phone, yes. That was my standard procedure actually, but nothing changes when I unplug it. I don't have a different battery and I am wary of buying one just for the sake of trying. Tried that when my galaxy s 1 broke down and that didn't save the phone. At this point I am contemplating if the phone (s3) is broken now or not. It still reliably boots to the recovery, but it doesn't do much else. How are the chances?
Or has anyone any idea on how to proceed?
ScPo said:
Thanks for your helpful input.
I did what you said, even tried it twice now. Phone is still booting after 20 minutes now. I also tried booting up while charging the phone, yes. That was my standard procedure actually, but nothing changes when I unplug it. I don't have a different battery and I am wary of buying one just for the sake of trying. Tried that when my galaxy s 1 broke down and that didn't save the phone. At this point I am contemplating if the phone (s3) is broken now or not. It still reliably boots to the recovery, but it doesn't do much else. How are the chances?
Or has anyone any idea on how to proceed?
Click to expand...
Click to collapse
Try to boot into recovery. Do a factory reset then boot straight into download mode and flash stock rom. You might have to redownload the firmware it could be corrupted.. If that doesn't work then you might have to send it in. It might cost about to fix. Or go to your local phone repair shop and see if they could fix it for cheaper
Sent from my GT-I9305 using XDA Forums
my galaxy note 4 (sm-n910t) caught in bootloop . i dont know what caused it. the phone simply restarts upto first bootscreen, ie upto 'samsung galaxy note 4' and then vibrates and then restarts.this process continues upto battery is down or i pull out battery.the phone is not entering to recovery mode but enters to download mode.
i have tried installing stock rom from sammobiles but it won't help.i have also installed custom recovery twrp but that also won't help to enter to recovery mode,
i am trapped pls help..
You didn't mention how you tried to install the stock ROM . Did you use Odin?
I just fixed mine with the same issue. I was able to boot into recovery and download mode but mostly download mode without bootloop when I had the usb cable plugged in. I used ADB when I could to boot into download mode, but the buttons worked too. Trying to restart the phone only lopped after the Google screen.
I followed several guides here to flash stock with Odin and wipe cache etc but none solved my boot loop issue. almost gave up but there is a video on You Tube that said the battery warping in the cause of the boot loop. The battery, after/during quick charge, may heat up and change shape causing the issue. Today I installed my new battery purchased on amazon and no more issues.
Now I am on stock and have to find a good rom.
If you do decide to flash back to stock there are a lot of good guides. You may find yourself stuck on the T-mobile screen for 15 minutes when booting for the first time but that is ok. If you still boot loop after installing stock and wiping cache I would try the battery.
Nabeel mhd said:
my galaxy note 4 (sm-n910t) caught in bootloop . i dont know what caused it. the phone simply restarts upto first bootscreen, ie upto 'samsung galaxy note 4' and then vibrates and then restarts.this process continues upto battery is down or i pull out battery.the phone is not entering to recovery mode but enters to download mode.
i have tried installing stock rom from sammobiles but it won't help.i have also installed custom recovery twrp but that also won't help to enter to recovery mode,
i am trapped pls help..
Click to expand...
Click to collapse
hi OP,
did you find any solution to your problem?
Hello all. I'm also pasting this in the T-mobile thread in case it can be of benefit to someone. This is advice to use as a very last resort if you are experiencing the recovery bootloop issue AND you don't have the emmc failure bug. I had the recovery reboot, sudden shutdown with no warning, etc. issue for the past two weeks. I tried everything on Google and Youtube to fix my problem with no success. I flashed multiple stock ROMS and recovery tars (stock and TWRP) via ODIN, but nothing worked. Oddly enough, I never received the emmc error that I have read about. Also, in the few times that my phone booted normally, I even loaded the Wakelock Power Manager app, set it to partial wakelock and my phone STILL continued to bootloop. As a last resort, I bought a new battery, but the reboot problems continued in Android 4.4.4 Kitkat, 6.0 Marshmallow, 7.1 Nougat and 8.1 Oreo ROMS. Well, here is what finally helped me to get my phone back operational. I had a backup ROM from a previous install and a TWRP flashable version of the same ROM on my SD card (in case the phone did not stay on for the full restore). I put the phone into a ziplock bag into a freezer for about 20 min. (thankfully this time TWRP stayed on long enough for me to do the following):
1) copy all the files I wanted to save from internal storage to a computer.
2) performed a full wipe (Dalvic, Cache, System, etc. Like when flashing a ROM, but this time also internal storage. Note: Please do not wipe both internal and SD card, as you may have a difficult time trying to load the ROM file back on the sd card (assuming you don't have a card reader).
3) After wiping, I was able to restore my stock ROM backup (or you can just flash the stock ROM).
I can't be 100% sure, but I think my wiping internal and then flashing the stock ROM finally did the trick. Since this morning, the phone has been pretty much back to as it was before. In either case, I'm sharing this with the hope that it helps someone else.
Sent from my SM-N910T using Tapatalk
chrismcnally123 said:
I just fixed mine with the same issue. I was able to boot into recovery and download mode but mostly download mode without bootloop when I had the usb cable plugged in. I used ADB when I could to boot into download mode, but the buttons worked too. Trying to restart the phone only lopped after the Google screen.
I followed several guides here to flash stock with Odin and wipe cache etc but none solved my boot loop issue. almost gave up but there is a video on You Tube that said the battery warping in the cause of the boot loop. The battery, after/during quick charge, may heat up and change shape causing the issue. Today I installed my new battery purchased on amazon and no more issues.
Now I am on stock and have to find a good rom.
If you do decide to flash back to stock there are a lot of good guides. You may find yourself stuck on the T-mobile screen for 15 minutes when booting for the first time but that is ok. If you still boot loop after installing stock and wiping cache I would try the battery.
Click to expand...
Click to collapse
Thanks sir! I have the same issue! it's working now after replace the battery