So... I'm trying to update to the current AOKP release, but seem to have an issue where the phone gets stuck on first boot.
Currently the process I'm using to flash is below:
1) Factory reset+wipe everything from recovery and reboot to bootloader
2) Flash boot.img, go to hwboot and reboot back in to recovery.
3) Push rom to sdcard, install rom/wipe cache and reboot
4) Watch that little X glow for 10-20 minutes.
This isn't the first time I've reinstalled the rom, however (I think) it is the first time I've wiped absolutely everything on the phone first. Is there some extra step I need to go through as a result? Or does first boot really take more than half an hour if I wipe all internal memory prior to reinstalling the OS?
Using TWRP 2.6 and hwboot 1.3(?) I think. Will check next time I'm in fastboot (leaving it on boot screen at the moment to see if it does anything).
Related
Hi guys, I got a SGS2 just over a week ago, on Bell/Virgin network in Canada. Suffered from the battery drain issue due to being stuck with crappy UGKG2 firmware which my provider still hasn't updated.
I decided to update it myself, and did a ton of research. I successfully got Root tonight by flashing CF-Root-SGS2_ZS-OZS_KG2-v4.1-CWM4 kernel with Odin. In case it matters, I did NOT flash back my stock Kernel, so I still had the insecure kernel installed. From there, I backed up my apps with Titanium.
Went into CWM and selected boot into CWM Recovery. I followed the steps on the wiki, including creating a backup file. My only hint of what I might have done wrong was I originally selected to flash update.zip, and that process failed. I then went to the directory in which cyanogenmod is stored on my SD card, and selected that, then it installed ok. I had downloaded update-cm-7.10-GalaxyS2-signed and that's what I put on the phone. I then also installed the Google Apps.
I then hit reboot, and it only goes to the Samsung screen with the yellow triangle and just hangs there for a few minutes. Not knowing what else to do, I popped the battery out. I have since learned that I can turn it on and off, but it never goes past that screen. Wouldn't go into the recovery or download modes, always that screen. Luckily, I saw somewhere to do the 3 button thing WHILE in that screen, and that works. So I can get to recover, and download modes. So, I think I'm ok. I checked, and it does connect to Odin still.
I just want to know EXACTLY what I should do at this point. I don't want to fully brick it. There are actually two recovery files on the phone... not sure why... Or which one to pick. Should I just flash stock firmware back with Odin? One of my main goals is to get off 2.3.3 so I can have more than 8 hours of battery...
Thanks,
Rob
Boot into tecovery, do a full wipe again. (Wipe data/factory reset, wipe cache partition, advanced>wipe dalvik cache).
Now install CM7 zip twice in a row without reboot. It may take a few minutes for reboot since system is rebuilding dalvik cache. Be patient. After you see the home screen, reboot again.
Sometimes, CM won't install properly with CF root recovery. In that case reboot into download mode, flash codeworkx cwm kernel via ODIN.
http://forum.xda-developers.com/showthread.php?t=1118693
Now reboot into recovery and do full wipe and twice-install !
Ok, working now with the flash twice thing. Well that's weird, would be great if it was in the wiki page...
Thanks!
Rob
I just flashed the new CM7 ROM onto my Atrix. I was running the Dark Side ROM before the flash. I tried booting my phone up, it goes to the boot animation which runs for about 5 seconds, then reboots. Its cycled for 10 minutes. I pulled battery, reflashed, but the problem seems pretty persistent. Any Ideas?
it may be obvious but did you do the "3 wipes" before flashing CM7? also try "fastboot -w" if you've done wipes in recovery already before flashing
i am having a similar issue with the MOD 2 version of this rom, i was using my atrix with the hdmimirror.zip that i installed other than that the phone was just stock rooted, with an unlocked bootloader. now that i have flashed this rom ( doing all the necessary wipes and etc.) when i try to reboot i am stuck at the dual core screen. any thoughts?
Format the system partition, factory wipe/reset, wipe dalvik cache. Reboot into CWM and then go ahead and flash the ROM. That should hopefully make sure it's all clean before the install.
Hey,
First off i hope i have put this on the right sub forum.
I've been stupid (I Think) I've olso looked around on the forum and the [READ THIS] Got a Boot Loop? Don't post a New Thread!
topic.
I'm using my SGS2 for a year now and was using the ressurexionRimix rom for a while.
I've been plaing around with my phone so i got lots of folder that were not used etc, so I wanted to get it back to factory settings, here is when all went down.
Via Settings-Backup and recovery i gave my phone a factory reset (while using the latest ressurexionremix rom, i think this is the misstake i made) When my phone went into the reboot is got stuck on the splash screen, it kept reapeeting the boot animation.
The second mistake i mad was not puting back my back-up but thought well i want it back to it's first state so i'll use ODIN to flash the stock ROM onto it. now, 4 hours later and about 10 trys with diferent versions of the stock roms i'm still stuck on the boot screen.
I've also tryd flashing a cwm so i could get in cwm recovery, this also without any luck
Does anyone have a idea what to do!?
go back to recovery - mounts andstorage and format the following :
cache, system, data, sdcards if you have it in recovery. reboot
you have a bkank screen as your phone has been wiped. reboot into download mode.
Connect odin and flash a stock rom. reboot and your phone should work provided that you have not damaged the flash chip on the motherboard.
Is this in CWM? the problem is i dont have that anymore because i've flashed it toc stok. I now get in the Android system recovery
The option i get there ar:
Reboot system now
apply update from external storage
Wype data/factory reset
Wipe cache parition
apply update from cash
test redbend fola[FS]
Will try this, thank..will let you know if it worked
Wiped data/factory reset and cache after this i ebooted my phone and i got the message installing application, now i'm in the setup menu. Looks like it is working.
Did'nt realice there was a recovery besides CWM Thank yoy so much Cosmic Blue!!! You saved my life!!
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
Hi,
First I apologise for not having made a back up of my filesystem, I had grown overconfident from previous successful projects ;-/
I have unlocked the phone and installed TWRP recovery. I then used SUPERSU to root the phone under TWRP. After SUPERSU the phone did not boot, it stayed on the WARNING BOOTLOADER UNLOCKED splash for over an hour and did not boot after a reset.
I read through the forums and looked for a kernel to try as I had read that the OS may be damaged, and I wanted to flash a ROM in any case. I read to clean the boot partition before flashing so I did this. The kernel I tried was Squid. This made the phone display "fall through from normal boot mode". So I tried Cyanogen Mod 14, which put the phone on a very rapid bootloop cycle (about every 15 secs), then tried Squid Kernel R22B which put the phone on a long (about 8 minute) bootloop cycle.
Not sure what else I can do. I don't want to give up on the phone as it still mostly works (it has a bootloader, recovery and a file system). I have tried to find a stock ROM to install but proving difficult to track down - links seem to be down)
I apologise if I have got any technical terms wrong. I hope you can help!
Thanks,
Caroline
Caroline300 said:
Hi,
First I apologise for not having made a back up of my filesystem, I had grown overconfident from previous successful projects ;-/
I have unlocked the phone and installed TWRP recovery. I then used SUPERSU to root the phone under TWRP. After SUPERSU the phone did not boot, it stayed on the WARNING BOOTLOADER UNLOCKED splash for over an hour and did not boot after a reset.
I read through the forums and looked for a kernel to try as I had read that the OS may be damaged, and I wanted to flash a ROM in any case. I read to clean the boot partition before flashing so I did this. The kernel I tried was Squid. This made the phone display "fall through from normal boot mode". So I tried Cyanogen Mod 14, which put the phone on a very rapid bootloop cycle (about every 15 secs), then tried Squid Kernel R22B which put the phone on a long (about 8 minute) bootloop cycle.
Not sure what else I can do. I don't want to give up on the phone as it still mostly works (it has a bootloader, recovery and a file system). I have tried to find a stock ROM to install but proving difficult to track down - links seem to be down)
I apologise if I have got any technical terms wrong. I hope you can help!
Thanks,
Caroline
Click to expand...
Click to collapse
Assuming you've the Lineage 14 zip in your internal storage or micro sd,. Enter TWRP, select wipe, advanced wipe, check system data cache and dalvik, swipe to wipe. Now you've clean wiped your phone.
Then go "install", select the Lineage zip and flash it.
Hi DroidFreak32, thank you for your help. The phone is now booting for the first time since it's "adventure".
Hi,
Unfortunately the phone is still in the boot logo screen. It stayed on the Lineage logo for 2 hours. I have powered off and rebooted once more, and it is still in the boot logo screen now (1 hour later). I'll wipe and install again and post an update.
Hi,
I reflashed Lineage, same problem. I did notice that each time I installed a zip file, SUPERSU asked me to install it prior to reboot to root the phone and I have always hit Yes. On the final flash, I powered off the phone when it prompted me to install SUPERSU, and the phone booted normally. Very nice design on the mod, I like the way the apps are displayed alphabetically. Good work Lineage Team!