Today Cyanogen updater notified me that the 10.2M build was available. I usually only flash stable builds, but I decided to check it out.
I was updating from 10.1.3- did everything as I always did, flashing seemed to go fine, but then I got stuck on the Cyanogen splash screen. So I went back to safestrap recovery, flashed back to 10.1.3- wiped cache etc... same thing. Just stuck on the Cyanogen splash. Tried installing 10.1.2, which was the first version I ever flashed. Same problem.
I was able to successfully boot back into stock using Safestrap (v3.11), but now I can't seem to get any version of Cyanogen to successfully boot.
Any suggestions?
Reboot into cm 10.2 before flashing gapps?
Sent from my XT894 using Tapatalk
Related
I flashed cyanogenmod 6 RC2 over RC1without a wipe, then i flased clockworkmod. after doing this, the g1 boots into android just fine, and works pretty well, but i wanted to flash another froyo rom, and when i tried i found out i couldnt boot into recovery. help please
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!
Ok, I upgraded my Milestone to official APAC 2.2.1 ROM. Was using it for a while, got bored and decided to go a custom ROM. I had previously successfully flashed MIUI and CM7 ROMS back on Eclair. Did a nandroid with Androdiani OR 3.3 and flashed CM7. Bootloop at CM logo. Pulled battery, reboot back to OR and tried flashing MIUI (stable version). Boot loop again at MIUI logo. Turned off using power button. Tried HO!NO!. Bootloop at M logo. Reboot, wipe, flashed FroyoMod. Bootloop again at M logo. Reboot, full wipe, tried iceandfire 2.9. Bootloop again at M. Gave up. Reboot, restored nandroid and everything is fine again. No idea what I've screwed up. Any advice?
Thanks.
Try wiping caches (both) and data in open recovery, then restart custom rom. Most custom roms require data/cache wipes.
Tried that. Wiped dalvik, and factory-reset before rebooting after flashing the custom ROMs. None of it worked. Cracking my head on this one.
Try flashing the 2.2 VR from http://android.doshaska.net/rootable, re-rooting the phone and starting the custom ROM process over again.
skadude66 said:
Try flashing the 2.2 VR from http://android.doshaska.net/rootable, re-rooting the phone and starting the custom ROM process over again.
Click to expand...
Click to collapse
Thanks. Will give a shot when get home from work and see if this fixes things.
Ok, tried flashing the 2.2 SBF with RSDLite. Checked version, exactly the same as what's already on the device. Flashed anyway. Restart, bla... bla... boot into Androdiani OR. Flash CM7, bootloop... damn... Nandroid restore.
Oh no! I can't get into bootloader mode now. I tried the D-Pad Up + Power button and it just boots up. No bootloader. Help.
afadzil21 said:
Oh no! I can't get into bootloader mode now. I tried the D-Pad Up + Power button and it just boots up. No bootloader. Help.
Click to expand...
Click to collapse
That doesn't make any sense.. did you do power+dpad-up and not the reverse?
Sent from my Milestone using XDA Premium App
I think I did Dpad UP+ Power. Got it to bootloader mode this time. Updated RSDLite to 4.9 and it recognised the phone when I plugged it in. Reflashed CM7 RC13 and gapps. Rebooted and... CM7 booted and started up. Crashing randomly though. Trying MIUI next.
afadzil21 said:
I think I did Dpad UP+ Power. Got it to bootloader mode this time. Updated RSDLite to 4.9 and it recognised the phone when I plugged it in. Reflashed CM7 RC13 and gapps. Rebooted and... CM7 booted and started up. Crashing randomly though. Trying MIUI next.
Click to expand...
Click to collapse
Yes! After reflashing bootloader everything seems to work. MIUI crashed. FroyoMod running ok. Trying HO!NO! next.
CM7 based ROMs don't seem to work well except for iceandfire. HO!NO! and CM7 crash frequently. But at least I can flash now..
Sent from my GT-I9100 using Tapatalk
I have a problem I haven't heard of yet.
I have a Vivid, S-OFF, Boot and SIM unlocked running CM 10 Official Nightly with TWRP 2.4.3 on T-Mobile.
Every other day the phone won't boot, just stays on HTC screen. I pull the battery and boot into recovery but nothing in recovery works. I can't restore backups or wipe anything and it says it appears no OS is installed.
In order to get it running I have to install CWM recovery and restore a backup I made with CWM.
Then a day later it starts all over again.
No idea what is going on but it's extremely frustrating.
Any suggestions would be greatly appreciated.
A lot of us are having problems with twrp 2.4.3.0. You could try the older 2.4.2.0 or flash WCX recovery. Last resort might even be reinstalling and starting fresh after you flash the different recovery
Sent from my HTC PH39100 using Tapatalk 2
I've been trying to flash a custom rom to my verizon HTC one, and have been getting stuck in a boot loop on every attempt.
ROMs I've tried:
CyanogenMod (m7 nightly 3/19)
ViperOne (5.8.0 and 5.7.0)
Currently running (and stable):
S-Off and Booloader Unlocked
stock radio
stock firmware
stock ROM (w/ root)
TWRP 2.7.0.0
CyanogenMod would boot, but then randomly reboot shortly afterward and was unable to recognize my SIM. Viper goes into a true boot loop, rebooting at the HTC splash screen (w/ red warning text). I have tried flashing each several times, wiping before each installation. Luckily, I have a backup of the current stable ROM, so I'll always be able to get out of a loop. I'm not new to unlocking and flashing ROMs but I've been using an HTC Thunderbolt until now (not losing my unlimited data, finally gave in and bought a used phone). I never had a problem on my old phone, but I feel like I might be missing something.
Any suggestions on what I might be doing wrong?
EDIT: Tried Android Revolution HD 53.0, same result as Viper
The_Wing_Man27 said:
I've been trying to flash a custom rom to my verizon HTC one, and have been getting stuck in a boot loop on every attempt.
ROMs I've tried:
CyanogenMod (m7 nightly 3/19)
ViperOne (5.8.0 and 5.7.0)
Currently running (and stable):
S-Off and Booloader Unlocked
stock radio
stock firmware
stock ROM (w/ root)
TWRP 2.7.0.0
CyanogenMod would boot, but then randomly reboot shortly afterward and was unable to recognize my SIM. Viper goes into a true boot loop, rebooting at the HTC splash screen (w/ red warning text). I have tried flashing each several times, wiping before each installation. Luckily, I have a backup of the current stable ROM, so I'll always be able to get out of a loop. I'm not new to unlocking and flashing ROMs but I've been using an HTC Thunderbolt until now (not losing my unlimited data, finally gave in and bought a used phone). I never had a problem on my old phone, but I feel like I might be missing something.
Any suggestions on what I might be doing wrong?
EDIT: Tried Android Revolution HD 53.0, same result as Viper
Click to expand...
Click to collapse
You need to flash a verizon compatible rom.
alray said:
You need to flash a verizon compatible rom.
Click to expand...
Click to collapse
I came across this in some of the research I was doing, and I realize that was a problem for Revolution, but Viper is listed as compatible. I would have originally asked on their thread, but I'm not allowed to post in that section yet and I wasn't able to find a similar post because the search isn't functioning right now.
The CM page said that build was compatible for multiple carriers, but I did try the m7vzw build and got an error during the installation that said I was using an m7 device.
EDIT: Problem solved, switched from TWRP to PhilZ CWM recovery, Viper booted successfully.