[Q] Stuck in bootloop CM9 lost recovery - AT&T Samsung Galaxy Note I717

Resolved - when after many attempts to boot into recovery I gave up and downloaded the Odin version of CWM and was trying to go into boot mode I accidentally managed to go into recovery and was able to recover. I think I will stay away from goo manager or rom manager - neither worked for me. Never had problems just following posted steps on XDA.
I decided to take the plunge and flash my first rom and now my phone is stuck on the CM9 boot loop. I had rooted with CMW through odin followed by superuser. I was on stock ics. I replaced cwm with twrp. No problems up to this point I then downloaded cm9 and the gaaps with goo manager. then tried to flash it after backing up, deleting data, dalvik and cache. It did not work but instead booted back into stock with all my data gone. I added back in my google accounts and wifi password. Then downloaded quick boot. Booted into recovery and installed the CM9 and fgaaps zips.
Now it just cycles in the cynagen bootloop ans will not boot into recovery. In my attempts to get boot recovery started it did once go into download mode. Anyway to recover using odin?

So you are up and running okay ??....g

Related

Flash KA6 unable to CWM

I flashed the following KA6, and I didn't realize it would wipe my apps and contacts. I took a nanroid backup using CWM beforehand, and I'm trying to boot into CWM to restore my backup. However whenever I tell CWM to reboot into recovery or to restore the backup, the phone reboots into the standard Samsung Andriod e3 recovery, which does not allow me to restore my backup.
How can I get CWM to boot up so I can do a restore?
http://forum.xda-developers.com/showthread.php?t=919760
I figured it out.
I'm having the same problem. How did you fix it?
I have flashed, deleted the clockwork recovery files, re-flashed, rebooted, etc, etc.
I can only get the standard blue recovery mode. I run reinstall packages and all it does is quickly shows it's attempting to install the clockwork update.zip file but just boots back into the blue standard recovery mode. Yes I have confirmed the update.zip file is there. I have removed it, reflashed, rebooted, etc. Running reinstall packages takes me into a constant loop.
This really sux.
Anyone got ideas on what my problem might be?
Thanks
Getting the same, and when I go check on my rom backups of my default OS there are no roms to be found after it says it created them successfully.
I erased any existing update.zip, then I told clockworkmod to reinstall, boot into recovery, in the blue menu I selected reinstall package, it rebooted into blue recovery again, and I selected reinstall package for the second time and then it finally rebooted into clockworkmod.
If this doesn't work you can try to follow this guide to get clockworkmod working again.
http://forum.xda-developers.com/showthread.php?t=925400
In the mist of my experimenting trying to get this to work, I did use the app Quickboot which is on the phone already to boot the phone into download mode. Then I did a hard reset (hold power button for 10 seconds), and tried the whole process I described in the previous post. I would guess this is not necessary, but it's just what I did.

[Q] Trouble installing CWM now wont boot

So I got my Gtablet today and after charging I immediately began to flash a new rom. My first step was to install CWM. I downloaded CWM internal and loaded the two files onto the root of the internal sdcard. It initially booted into CWM. I rebooted. It would boot into the stock rom but would not load CWM. I would press the + volume and power. Every time it would hang at the birds. I attempted to delete CWM from the internal card and reinstall. No luck. So I searched around the boards and someone mentioned they had the same problem and fixed it by resetting to factory in the settings menu. I tried that. It immediately rebooted and now it hangs at the birds. It says loading recovery kernel but nothing happens. It won't load into the stock rom. It hangs and says loading recovery kernel image, but doesn't do anything. So as of now my brand new gtablet isn't working.
Any advice?
Sounds like you have a 1.2 bootloader and tried to load CWM for the 1.1 version. You'll probably need to nvflash a good stock recovery image into place to let it finish that data wipe or nvflash back to a factory stock condition.

Stuck on boot animation loop

Attempting to install a new ROM, so wiped all data, did a restore to factory settings and wiped Dalvik Cache. Realised new ROM wasn't on memory card, so tried to boot up, and it just keeps showing the (stock) boot animation.
Can access recovery (CWM 5.0.2.6), so what is the best way to get my phone back up and running?
flash new rom using cwm.
or, if u could enter to download mode. flash stock using odin
Thanks, managed to get a ROM and installed it, and is working!
try to read Q&A thread for future reference.
helps alot. really.. no.. seriously..

[Q] Bootloop help

well I was flashing MIUI V5 UNIVERSAL - v. 3.7.12 for the 3vo and it got stuck in a bootloop. to try and fix it I tried to restore a backup and that rom played a little of the boot animation but then gets stuck in a bootloop. I also tried to wipe/format everything but, that didn't work. If a logcat would help i would appreciate a link on how to do that without being able to boot. I can boot to 4ext recovery. The cause could be that while flashing I selected the file to flash, I selected a file that didn't finish downloading. Thanks in advance for any help
Also if it matters my original rom was negalite blurom.
cdog1213 said:
well I was flashing MIUI V5 UNIVERSAL - v. 3.7.12 for the 3vo and it got stuck in a bootloop. to try and fix it I tried to restore a backup and that rom played a little of the boot animation but then gets stuck in a bootloop. I also tried to wipe/format everything but, that didn't work. If a logcat would help i would appreciate a link on how to do that without being able to boot. I can boot to 4ext recovery. The cause could be that while flashing I selected the file to flash, I selected a file that didn't finish downloading. Thanks in advance for any help
Also if it matters my original rom was negalite blurom.
Click to expand...
Click to collapse
I ran into your same problem today.
At the time my phone was on latest sprint firmware, ICS coolrom (latest rom and kernel) with hboot 1.58 unlocked s-off.
The steps I did preparing to install MIUI was
1) wipe data/factory reset from 4EXT
2) format all (except sdcard)
3) Install MIUI > chose mirage kernal
4) rebooted
after reboot it was stuck at the logo, at least I thought it was, let it sit for about 5 minutes.
Pulled the battery and tried steps 1-4 again.
Kept getting bootloop at that point. Boot splash -> logo -> reboot.
Next I tried flashing the latest mirage kernel from 4ext.
No luck, same issue.
Tried repeating steps 1-4 again.
No luck stuck in bootloop.
At that point I tried to run recovery from a backup I knew was working.
Wiped all data and format all -> selected recovery from 4ext.
Result: still boot loop.
At that point I tried changing bootloader to 1.58.58 jbear. and wiping/formatting all and trying recovery again from known working cool ics backup.
Result: still bootloop.
Switched back to 1.58 bootloader and tried fresh install of CoolICS rom. (I always wipe all data and format all before any rom change.)
Result: still bootloop.
At this point I was getting frustrated but I had an idea that the MIUI install when selecting mirage kernel may have messed up the partition size for the kernel since the mirage kernel states it must be flashed from the flash gui app first to resize the boot partition.
Next I downloaded pacman rom and attempted that install.
result: could not install due to wrong bootloader.
Next I downgraded bootloader to 1.50.50 jbear.
Wiped everything and retried pacman rom.
Install success, before starting the reboot from recovery, I received a message that the boot image has changed and will make a backup/format/flash the new boot image.
upon reboot I was able to successfully boot into pacman rom.
At that point I tried to wipe all again and install CoolICS rom again.
result: bootloop, but probably because of bootloader version. Did not fully test it as at this point I just wanted a working phone again and wanted to try out MIUI.
Rebooted to recovery and wiped everything again.
Installed MIUI using stock kernel option. This time on reboot I let it sit at the rom logo without touching anything. I think it restarted once on its own.
Result: Success. Phone working normally now. such a headache I am just leaving it as is for now.
Jeffjb said:
I ran into your same problem today.
At the time my phone was on latest sprint firmware, ICS coolrom (latest rom and kernel) with hboot 1.58 unlocked s-off.
The steps I did preparing to install MIUI was
1) wipe data/factory reset from 4EXT
2) format all (except sdcard)
3) Install MIUI > chose mirage kernal
4) rebooted
after reboot it was stuck at the logo, at least I thought it was, let it sit for about 5 minutes.
Pulled the battery and tried steps 1-4 again.
Kept getting bootloop at that point. Boot splash -> logo -> reboot.
Next I tried flashing the latest mirage kernel from 4ext.
No luck, same issue.
Tried repeating steps 1-4 again.
No luck stuck in bootloop.
At that point I tried to run recovery from a backup I knew was working.
Wiped all data and format all -> selected recovery from 4ext.
Result: still boot loop.
At that point I tried changing bootloader to 1.58.58 jbear. and wiping/formatting all and trying recovery again from known working cool ics backup.
Result: still bootloop.
Switched back to 1.58 bootloader and tried fresh install of CoolICS rom. (I always wipe all data and format all before any rom change.)
Result: still bootloop.
At this point I was getting frustrated but I had an idea that the MIUI install when selecting mirage kernel may have messed up the partition size for the kernel since the mirage kernel states it must be flashed from the flash gui app first to resize the boot partition.
Next I downloaded pacman rom and attempted that install.
result: could not install due to wrong bootloader.
Next I downgraded bootloader to 1.50.50 jbear.
Wiped everything and retried pacman rom.
Install success, before starting the reboot from recovery, I received a message that the boot image has changed and will make a backup/format/flash the new boot image.
upon reboot I was able to successfully boot into pacman rom.
At that point I tried to wipe all again and install CoolICS rom again.
result: bootloop, but probably because of bootloader version. Did not fully test it as at this point I just wanted a working phone again and wanted to try out MIUI.
Rebooted to recovery and wiped everything again.
Installed MIUI using stock kernel option. This time on reboot I let it sit at the rom logo without touching anything. I think it restarted once on its own.
Result: Success. Phone working normally now. such a headache I am just leaving it as is for now.
Click to expand...
Click to collapse
well I went to go try and boot P.A.C. and my phone just booted normally. So thanks for the help

Galaxy S3 crazy boot loop

hi everybody.
my phone is booting every time. with odin i installed already twrp and cwm. with twrp I can just see the logo and then the phone is booting again. with cwm, i am able to see the menu but when i try to wipe the phone, the phone starts to boot again.
i installed cyanogenmod via adb but the phone is not starting android.
the last chance i have is to hope that someone of you have a solution.
i uploaded a video to show you what i mean.
ht t p : / / s e n dvid.com/u4z3xfu7
thanks
andi
Have you tried flashing a stock ROM?
yes. but it is still in the loop.
Flashing in Odin was successful?
After flashing the stock ROM, did you perform a factory wipe before booting for the first time?
thats not possible. i can boot to the clockworkmod recovery but if i choose the option "wipe data/factory reset" the recovery will be closed and the smartphone boots again and open the recovery.
1, download mode and flash an official stock rom (one package) via odin. Make sure it is for your device specifically.
2, Boot to official stock recovery and wipe data/factory reset. If the phone reboots after this you need to be prepared to key combo to download mode BEFORE it boots android.
3, Flash the official stock rom again.
All remnants of any previous roms will be gone and you should have a booting phone.
Beamed in by telepathy.
It worked with the stock recovery. Now I was able to install cyanogenmod. Thank you very much!!!

Categories

Resources