[Q] installing a new rom - Vega General

Hello, i own two vega. I bought one of the with cm7 installed, i exchanged several roms [corvus, cm7, different nightly] always with rom manager or from clockwork recovery. Never had a problem.
Bought a second vega with modaco r8 installed. Installed last rom manager, installed throught it the last recovery, downloaded the corvus image [checked hash, correct] and finally choose to flash with a full wipe, erased cache ect ect. Device rebooted, screen black. After 5 mins i pushed the power button, device turned on [screen backlight was on] but nothing else. Everything black.
Downloaded the official firmware 1.10, connected the vega to the pc and restored stock 1.10. Got root access with z4root, installed the market, downloaded rom manager, installed tfhe last recovery image. Rebooted in recovery and manually wiped and erased the caches. Installed tghe corvus. All processes went ok. Rebooted and once again black screen, not able to boot in recovery and not able to boot in corvus. Had to go back once again to stock 1.10
Whats wrong? Do i miss something?

Related

Issues getting in to recovery...

So i did a soft brick yesterday..
Applied voodoo, then tried to restore a non voodoo backup.. My bad
Since then i have used ODIN and flashed the justinthecroud "stock"
After that i re-flashed some rom's but once i get in to the OS and Download rom manager i have nothing but issues.
Rebooting via ROM manager in order to flash a new rom, or even "reboot recovery" via the terminal i just get the "vibrant" screen and then nothing..
This has happened a few times.
Since then i flashed the leaked 2.2 posted by Eugean (via ODIN).
Then macnut12
Again, as soon as i use ROM Manager and try to get in to recovery directly from the OS i get soft bricked...
Anyone have any clue?

no boot, no recovery mod after kernel upgrade via Rom Manager

Hello,
my phone was working like a charm with cm 7.1 , Siyah Kernel, clockworkmod recovery mod 5.0.2.
I decided to upgrade my Siyah Kernel from 2.0 beta 8 to v2.
I used the QR code from Xda forum. Phone downloaded kernel, then once download finished, opened Rom Manager app, then invite me to install the new .zip file.
I usually do it manually, in rebooting in recovery and installing the .zip file in recovery mod, but I wanted to try this way.
Now my phone doesn't boot, hanf on on Samsung logo. No recovery mod available, only download mod.
Tried to reinstall ClockworkMode recovery 5 with Odin, but nothing happens. The yelow box stays yellow, and message hans on at Setup connection.
I alos tried to flash P-SBL.tar with odin, but it failed.
So, what can I do??
EDIT : Issue solved. Retried with Odin and ClockworkMod. This time I booted in recovery, phone booted in it and installed new kernel, and the booted in cm 7.1. I do think this issue came from Rom Manager.
So far as i know, using rom manager with the S2 is a mistake.
The S2 dosnt like rom manager much, and it can end up in a lot of problems up to a semi bricked phone.
Glad you solved it , but i recommend to avoid rom manager for now

Cannot install gapps on CM7.1

I have a Samsung Fascinate, it was just updated to Gingerbread.
I followed the instructions here:
h t t p:// wiki.cyanogenmod.com/wiki/Samsung_Fascinate:_Full_Update_Guide
I downloaded heimdall, downloaded the clockworkmod tar, I untar, then I flashed the recovery.bin to it in Download Mode with heimdall.
Then I boot up into cwm, select my fascinate cm7.1 zip file. It reboots after about 3 seconds, and it boots up, looks like it's in cwm, and takes about 30-45 seconds, then it reboots on its own. Then it shows the cyanogenmod animation, and then it boots up.
It was my first time booting cyanogenmod. Then I remembered I hadn't installed the gapps. So I reboot into cwm, and then I install from zip, and choose 'gapps-gb-20110828-signed.zip' so there's no errors whatsoever, and I reboot.. and I look for the Market.. and it is not there. And neither is Gmail, or anything else. It looks as if I didn't do anything after installing cm7.
I tried this twice already.. I tried downloading it in the Rom Manager, but rom manager doesn't work.
I really want to have the market and stuff..what should I do?
[edit]ok, I tried some stuff, like factory reset, and then flashing gapps, and I also installed a different version of cwm, and then it started working![/edit]

Recovery not "sticking" ?

Hey guys, I have a weird issue. I recently (re)aquired a MyTouch 3G Slide after selling my old one. The other I rooted back when rooting was still super-hard. I bought it the day it came out, and had CyanogenMod7 running beautifully and everything.
The "new" mytouch 3g slide I aquired was factory reset (s-on) on 2.1. I tried to update to 2.2, but HTCs website doesnt seem to have the files anymore. So I rooted it using UniversalAndroot. I tried to run RomManager to flash recovery, but as you know, it no longer supports 2.1 and below, so that sucked.
I found an old version on here, flashed it as update.zip, and everything was good.
Now that I'm rooted I flash CyanogenMod7 and GAPPS. Everything installs fine, except GAPPS didn't. So I reboot into recovery, and I see it's stock again. Hmmm, strange. I install update.zip again, recovery comes back, I flash GAPPS again, this time only the market installs. Fine with me.
I reboot into recovery to make a back-up after installing everything. Strange...stock recovery AGAIN. Install update.zip, everything is fine, create my backup, reboot and I update CWM through RomManager, everything's good. Reboot into recovery. STOCK RECOVERY AGAIN.
It seems the only way to get into CWM is to flash update.zip (luckily only takes a few seconds), but is there anyway to make it stick? I had to force update SuperUser as well, and a few other things.
So my question is, if I downgrade to stock 2.2 from HTC, root, then reupgrade to Cyanogenmod 7, would all my issues be fixed?
Update.zip will NOT change the recovery; it will only allow you to use the custom recovery for that certain time. You must obtain the recovery image(recovery.img) and then boot into fastboot(press vol-down+power, then press power) and, on your computer, move the recovery.img to the same directory as fastboot and then, still on your computer, type fastboot flash recovery recovery.img, and there you go

Trying to install cyanogenmod to nexus 4, I cannot flash it through TWRP recovery

I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
I've the same problems with my nexus 4
gerardgerard said:
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
Click to expand...
Click to collapse
Hi gerardgerard,
I also wanted to flash my Nexus 4 with Cyanogenmod 12.1. So I installed TWRP into recovery and wiped everything, like it's explained in the wiki. I can also see the error "unable to mount /usb-otg". When I want to reboot the system I always get back to TWRP. Cyanogenmod doesn't boot correctly. Did you find a solution for the problem?
same problem
Hi
I'm having the same problem. As follows:
Cause (my mistake): I have been using Cyanogen-mod nightlies for a couple of months on my Nexus 4, and made the grave mistake of leaving the phone to upgrade one night but without it being plugged in properly - and it ran out of power part way through! (At least, that's what I think happened).
Fortunately, it would boot into bootloader and I could use adb/fastboot. I (re)installed TWRP 2.8.7.0 (from my Mac, using fastboot). And that works fine - I can boot into twrp ok.
Next I loaded the latest nightly from cm (using fastboot - is this what people call sideloading?) and used twrp to install it. It goes through the installation fine (the only error message is that it can't mount /usb-otg). But when I reboot it just goes back to twrp.
I then tried installing the earlier cm nightly that I know worked, but with the same result.
Finally, before I first installed cm I did a backup (using twrp), and I have tried recovering that. It seems to do all the right things, but again when I reboot it just goes back to twrp.
Any suggestions would be welcome.
Thanks
J
Flash back to a completely stock ROM and run through the set up to make sure everything works. Then copy CM to the phone, reboot to fastboot, flash twrp, immediately boot into recovery using the volume and power button without leaving fastboot, wipe data, cache, system, flash CM, reboot.
If the phone will not boot after flashing a stock ROM, boot to fastboot, flash the userdata.img file, and immediately go to stock recovery without leaving fastboot, wipe data/cache, reboot.
It works now!
I managed to fix the problem ... I found this guide for the Nexus 5:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
and I applied those instructions. It didn't work first time, so I just repeated them and now it's working. I used the 5.1.1 stock downloaded from https://developers.google.com/android/nexus/images#occam.
I guess this is what audit13 means in their post - so thanks are due there.
I will next reinstall twrp and cm and I don't expect any problems with that (having done it successfully before).
Smaje

Categories

Resources