Hi guys-
Just tried to flash the latest stable cm7 & now I'm stuck on touch the future of reading. Prior to this I upgraded rom manager to the latest (3.0.2.8 as i recall). I've tried power+n on boot to force it into cwm but no dice.
Before i try the 'file of last resort' (which I believe will repartition me at the cost of losing my previous setup) are there any other suggestions?
Thanks,
Mark
Related
I was wondering if anyone else is experiencing the same problem as myself. I am running rodriguezstyle 2.2 r16, and I was able to download flash 10.1 immediately after the ROM install, but when I try to update, it either gives me a "Installation failed" notification, or resets the phone, not from the boot image with the static nexus one logo, but from the actual boot animation, and it reboots very quickly, but doesn't show a successful update. I have flash moved to the SD card, and have set all apps to install to the SD card. Any ideas?
same thing with me...its only the adobe flash that wont install, everything else works just fine
I guess the good news is (at least for me) that the install attempt doesn't uninstall the previous version. Flash sites still work as the did before.
Hi
I had upgraded to CM6 RC1 a while back, did the whole dangerspl stuff, and radio updates with no problem, from then on, I kept upgrading manually till I got to the stable release and thought I'd try to do it with the mod manager that's included in cm6.
It required me to install clockwork recovery manager and so I did, replacing the amon-ra recovery I had installed before.
I downloaded the rom with the google apps and tried to upgrade.
It is not stuck in the screen showing "T mobile G1" with no indication of progress or anything, it didn't load the recovery image.
I can still boot into the phone by removing the battery and placing it back, but I can't go into recovery.
What can I do now?
eladkatz said:
Hi
I had upgraded to CM6 RC1 a while back, did the whole dangerspl stuff, and radio updates with no problem, from then on, I kept upgrading manually till I got to the stable release and thought I'd try to do it with the mod manager that's included in cm6.
It required me to install clockwork recovery manager and so I did, replacing the amon-ra recovery I had installed before.
I downloaded the rom with the google apps and tried to upgrade.
It is not stuck in the screen showing "T mobile G1" with no indication of progress or anything, it didn't load the recovery image.
I can still boot into the phone by removing the battery and placing it back, but I can't go into recovery.
What can I do now?
Click to expand...
Click to collapse
If you flashed recovery from within CM6 it's known to failure. You should use fastboot to flash your recovery when using CM5/CM6. There are several threats dealing with this topic.
AndDiSa said:
There are several threats dealing with this topic.
Click to expand...
Click to collapse
Can you please point me (and anyone else who will read this thread in the future) to any of them?
I just fixed this by reinstalling the amon-ra recovery image
For example here
or use
http://www.google.com/cse?q=cm5+rec...ub-2900107662879704:fs7umqefhnf&ie=ISO-8859-1
Hey all.
I was using an old version of MIUI (RCxx, I don't remember anymore). And I decided to update to the latest. I copied the zip which is required to update but my recovery seemed to be broken. When I select anything from it, nothing happened. So I decided to flash kernel with another recovery. But something didn't go well and I got a picture with mobile phone, exclamation mark and PC on the display.
So I flashed Darky's reserruction ROM (which helped me many times) but it didn't boot. It stacked on Darky's boot animation. I wiped cache, system and data but it's now stacked on Galaxy S logo.
I'm still able to go in download mode. What should I do?
Thanks in advance.
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!
Hi...
I have no idea how exatly how, but I might have bricked my galaxy. I installed LineageOS 19 and got the recent update and ofc. it didn't boot after (bootloop). I wiped it using twrp and installed the "first" version I tried again. Will boot untill I try installing gapps.
I have looked around and tried restoring using odin. The Download Mode screen says "unsupported version" in the cornor.
Soo now I'm looking for someone with a backup with a stock firmware so I can use that to get everything working again
______________________________________________________________________________________________________________________________________
Many thanks, a lost s10 user (Simon)