I had dual booting working fine with dual boot patcher. Offical Samsung rom as my primary and CM 12.1 as my secondary. Yesterday I decided to update my secondary Rom using cyandelta. The update was successful and CM12,1 booted up fine. What i didn't test was to see if my primary rom was fine. Anyway today I tried booting into my primary rom and it would not go. It only boots into Cyangenmod. The only way for me to go back into my primary is go to and start "UDC download". pull the battery out. This will boot the phone back into the primary rom. However the minute i restart the phone it will go straight back into CM12. Looks like the boot.image isn't right or being loaded correctly for the primary rom. How do I fix this problem?
Related
I recently decided that I wanted to do a fresh install of CM7 using the latest nightly. I wiped everything, including boot (which I think is the problem). I made a bootable CWR SD card and installed the latest nightly and gapps. Everything booted up fine and ran great, until I tried to use ROM Manager. Every time I try to boot into recovery, the Nook hangs at the "ReadForever" screen. It was hanging at the new Cyanogen boot logo, but in an attempt to correct the issue, I flashed the stock 1.2 uboot. I have also noticed that several apps are now showing up at phone size when they were fine before running the same setup. I am running n87, 5/23/11 OC, and the stock 1.2 uboot. Does anyone have any idea what the problem might be?
You can try to disable the "compatibility mode" in order to try and get the apps to use the full screen. Regarding the Clockwork recovery issue, I have no idea - sorry!
Trying to install the Cynogen ICS ROM, and when installing the .zip, it loads the Samsung flash screen with Cynogen, then get the green guy and loads of text for about half a second, then it just reboots. Over and over for about 10 mins. WHat went wrong? What should I do?
It happend the same to me.
I just removed the battery and put it back, entered in CWM and reinstalled the ROM.
Good luck!
I somehow got into a recovery mode, but with the assumption it would all go wrong again, tried to install the .zip Darky rom instead, went through the process and said it worked but then it just went back to the Cynogen loop problem!? I just tried a Restore instead, but I haven't rebooted yet, should I wipe everything again, and try the ICM .zip again?
Yep, just go with the whipe. I hope you did a backup.
OK turns out the Restore failed, so now trying to reinstall ICS .zip again. fingers crossed!
yep backed it up, not that its seems to have helped.
Well now it's stuck in the Galaxy S bootscreen...
that really sucks....did you deactivated the lagfix before running the rom?
If the problem persists you have to run a basic ROM using ODIN.
Yes deactivated the lagfixI can't get into recovery or anything now, except download mode.
Download mode is all you need to run a ROM with Odin.
I recommend Amestris, it is a good ROM, good battery life but the thread in not complete, there are some files missing...for now.
I've put some older ROM on I had, then tried to install ICS again but now when I use Clockwork, and select the file it goes to recovery but I can't select any zip files, just reboot back to this awful old ROM!
I had same issue when I installed ics, what I did that worked was pull battery and go back into cwm, reflashed ics zip and it fully installed that time. Had same experience when flashing cm7 before.
Not getting anywhere with this. I get an option to install zip from sdcard which is where the update is (an where the darky update also is which worked), but there is an option to update from internal SD, which is not where the file is. Is it in the wrong place?
I think you would be best to use Odin 1.3 to flash DarkyROM Ficeto JVT base rom.
are you sure those files are still on your sd card?
The reason you need to pull the battery and reflash the ICS rom a few times is because Samsung ROM (most) have a different partition layout to CM7 based roms (which the ICS port is one).
GL.
I had installed cyanogen mod 10.1 on my bionic and i wanted to try other roms since i was getting very weak signal on this one. So i tried several times using safestrap on rom - slot 2 since on the stock rom i have the stock rom and on rom slot 1 i have 10.1. I found a rom that states that it gets good signal once you apply a gsm patch and some other stuff but i didn't ge to do that. It said to install bootstrap. so i did. But what i shouldn't have done is mess around with that now my phone won\t boot to fsafestrap so i can restore and when it boots i get Unsuccessful Encryption and a reset button but it stays on that loop.
is there any way i can recover my safestrap installation or how can i go about reseting or installing everything to stock to start over.
I can't access my phone only the sd card. When i try to boot to recovery i get the dead android.
I have the backups folder i made with safestrap. Anyway can apply them manually? Or how can i install safestrap manually?
Please help
cm 10.2.1 works great in rom slot 2 on my droid4, but not in the stock slot. Is there something different I have to do?
I activated the stock slot, did a Factory Reset, installed cm and gapps. It boots, shows the safestrap splash screen, then goes to a black screen with the backlight on. Nothing after that.
I can connect with adb and see the logs, there are repeated heap dumps from something crashing, but I don't see a line saying what. It appears to be trying to start AndroidRuntime and dalvik (same thing?) over and over. Does this give anyone a clue?
I also tried wiping /system after a factory reset, but it just hangs on the black screen, no change.
Before this, I had the latest OTA in the stock slot, and I was running eclipse rom 1.0.8 (or something) in slot 1. I am able to restore my safestrap backup of the stock slot and the stock rom still works.
You can only safely install Cyanogen in ROM-Slot 1. Never try to install to the stock ROM slot. Slots 2 and 3 are touch and go. It's best to just stick with ROM-Slot 1.
If you've already installed it in the stock ROM slot, then you'll likely have to restore your phone using SBF/fastboot files and start the whole process over from a stock system. :\
NeoPhoenixTE said:
You can only safely install Cyanogen in ROM-Slot 1. Never try to install to the stock ROM slot. Slots 2 and 3 are touch and go. It's best to just stick with ROM-Slot 1.
If you've already installed it in the stock ROM slot, then you'll likely have to restore your phone using SBF/fastboot files and start the whole process over from a stock system. :\
Click to expand...
Click to collapse
The note on the cyanogen site says "Builds older than 09/01/2013 must be installed on rom-slot1." I've read threads where people are using cm and aokp in the stock slot, so I thought it would work.
Any idea why it can't work in the stock slot? Safestrap seems to create image files for virtual filesystems of system, cache, and userdata which are obviously just imitating the stock partitions. I guess you need to bypass that logic, so can I just tweak the fstab or something? I'm curious what other magic safestrap is doing (or the cm/aokp roms) that needs to be adjusted for stock.
Nevermind, I figured out my mistake. I was on an old version of safestrap. Upgraded to safestrap-maserati-3.65, flashed latest nightly cm11 to stock slot, and it works. Great job cyanogenmod!
The other day i took my HD+. I havent used it for two years, and had been running the hybrid boot from the sd card, which was awesome! Well, I wiped the SD card and wiped the tablet. So essentially it was stock.
I formatted a new microSD card with verygreens recovery, booted it, flashed the rom and google apps, and thought everything was fine. Well, I kept getting a google services stopped working error so I decided to just experiment with Marshmallow. I went into the recovery, wiped everything, and flashed amaces ASOP rom. Then tried flashing gapps, and got an error that said that I didnt have android 6.0.x
Must have failed. And when I booted from the SD, sure enough it booted to KitKat, the one I had flashed previously. Well, eventually I took out the SD and to my surprise, cyanoboot was installed to the tablet and not booting from the SD card. And the marshmallow rom launched (without gapps). I tried booting into the internal cyanoboot, but it was the old one. I held the power button and the home button, but to no avail.
This is probably where I messed stuff up. It started booting and started booting stock, which I didnt want. Where it has the little white loading bar. I force shut it down. Well then it started acting weird and not even booting with the internal cyanoboot. It now just flashes the nook logo.
Luckily, I can boot to the external cyanoboot, but it has an error mounting the emmc. Should I reflash the stock rom and recovery?
Thanks!
SouthernGeorge said:
The other day i took my HD+. I havent used it for two years, and had been running the hybrid boot from the sd card, which was awesome! Well, I wiped the SD card and wiped the tablet. So essentially it was stock.
I formatted a new microSD card with verygreens recovery, booted it, flashed the rom and google apps, and thought everything was fine. Well, I kept getting a google services stopped working error so I decided to just experiment with Marshmallow. I went into the recovery, wiped everything, and flashed amaces ASOP rom. Then tried flashing gapps, and got an error that said that I didnt have android 6.0.x
Must have failed. And when I booted from the SD, sure enough it booted to KitKat, the one I had flashed previously. Well, eventually I took out the SD and to my surprise, cyanoboot was installed to the tablet and not booting from the SD card. And the marshmallow rom launched (without gapps). I tried booting into the internal cyanoboot, but it was the old one. I held the power button and the home button, but to no avail.
Click to expand...
Click to collapse
Running CM internally on EMMC and on SDcard use different CM ROM image versions that are not interchangeable. Currently there is no SDcard build for CM12.x or CM13, so your only choice is to flash and run them on EMMC.
This is probably where I messed stuff up. It started booting and started booting stock, which I didnt want. Where it has the little white loading bar. I force shut it down. Well then it started acting weird and not even booting with the internal cyanoboot. It now just flashes the nook logo.
Luckily, I can boot to the external cyanoboot, but it has an error mounting the emmc. Should I reflash the stock rom and recovery?
Click to expand...
Click to collapse
If you plan to go back to stock ROM and recovery, see item #6 of http://forum.xda-developers.com/showthread.php?t=2062613.
I don't really care about going back to stock, but I can't mount the emmc, will flashing the original recovery fix that do you think?
SouthernGeorge said:
I don't really care about going back to stock, but I can't mount the emmc, will flashing the original recovery fix that do you think?
Click to expand...
Click to collapse
I don't think the cause of your "can't mount emmc" problem is due to not having the original recovery. And there is no point in restoring stock recovery unless you want to re-install stock ROM.
So what do you suggest? Try to flash to CWM recovery and hope it fixes the mounting emmc problem?
Great news! Luckily the rom was still intact. I was able to run a "factory reset" and that fixed the emmc mount problem. The CWM recovery was still installed too and it booted into Marshmallow like I had before!
At this point, can I install a different resident recovery utility? I dont see why not.
Thanks for your help