Hello everyone.
I am having a big issue installing custom ROMs nowadays. Previously it was no deal, but now, whatever ROM I get, it is stuck att the Edify crap in the beginning of installation. Tried using the Amend (or whatever) to Edify on the update script in com -> android or something like that. It does everything fine, but rezipped the archive after saving and tried to flash it. This time I got some message from the tool and it ended with an "Update complete" message. Started the phone. NO change.
So I tried opening just the zip of the rom and yet again, seemed to do some stuff. Transfer to my SD card and everything goes well on installation. Getting the regular "Update complete" message. Restart phone, no change.
Thats how far I got, tried flashing the recovery thinking the recovery obviously might be outdated. No luck, at all.
Might add that the reason I want to use a custom ROM is since the one im using now (Mokee Epic) does not support USB. My computer doesn't recognize it. This way I can get it to work in Sony Ericsson PC Companion and reinstall the stock ROM.
So, im sorry for a big read, but I am in a very bad mood now.
EDIT: Might add that I tried out FeraVolt's ROM which installed fine. The problem was that when I started it and entered my PIN, the screen would go black. I guess this is a result of me NOT flashing with their custom FeraKernel. But when I tried to flash the kernel with FeraVolt's GB 5.3 kernel released earlier this month, It gave me the Edify error.
Sincerily,
Related
I've had my Samsung Vibrant rooted for awhile now, and I've been flashing ROMs just as long, but this has got me stumped! I've been running Eugene's Vanilla AOSP ROM for about 2 months, but today I decided I needed a change, so I downloaded the SGSII V2 Final ROM from the Development Section.
So far, so good.
I realised that I hadn't installed Rom Manager on my phone since I flash this Vanilla AOSP ROM, so I went into the market, installed Rom Manager, and flashed the lastest CWM Recovery (2.5.1.2).
Now, here comes the problem.
I rebooted into recovery, and I noticed that the text isn't green anymore, it's red and purple. At the very top it says "EB-ClockworkMod Recovery Ext4 Edition" in red, so I didn't think anything of it. I navigated my way through the install .zip from SD card menus, and then the problems started.
It was try to load the update package, but would stop and give me an error sayings something about Amend scripting no longer being supported. I've tried 2 other ROMs, and I still get the same thing.
I've scoured the internet, but I came up empty handed. Can someone please offer some advice? Thanks in advance!
You've two options; either Odin to stock and that will surely fix your problem. Or try downloading SGS kernel flasher from the market and use it to flash any 2.2 kernel say overstock then manually reboot to recovery using the three buttons combo and flash SGSII clone from there.
One issue with that though, some kernels don't support that one dunno if dead horse is one of those or not. Either way the worst that could happen is the App refusing to run nothing else then you'll have to Odin.
I actually just randomly fixed it.
I went through the install zip from SD card menus, and instead of pointing it to my ROM zip, I pointed it to the update.zip that was sitting in my external_sd folder. Once I did that the menus changed to green, and I was able to install on of my ROMs.
However, the SGSII clone is giving me an error that I've never seen.
It'll start installin the ROM, and right after Copying Files... it says
E: Can't find symlink /system/bin/cat
E: Failure at line 19:
symlink toolbox SYSTEM:bin/cat
Installation aborted.
The other ROM I tried installed works wonderfully, but this one gives me that error.
its always good to odin to stock before every flash but u dont have to. Gets rid of alot of old ghost roms on ur phone before flashing a new one.
Okay, here's the story.
I rooted my phone, turned S-ON, and installed Cyanogen 7 RC-1. So far so good.
Next I threw on ROM Manager, and got the premium version. I updated CWR to 5.0.2.0. And then went to play.
Well, first thing I noticed was ROM Manager kept erroring out when it rebooted into recovery. The error report is something about being "unable to locate dev/tty0". That was when I noticed something.
In ROM Manager, it says Clockwork is updated to 5.0.2.0
But in Recovery Mode it says 2.5.1.2
So far, I've tried "Erase Recovery", flashing to 3.0.0.8 and seeing if that worked (it didnt'). Then i tried going back up to 5.0.2.0. That didn't work either.
I tried a manual instal of 5.0.2.0 and the system didn't even recognize the file, so I probably did something wrong there.
I'm just lost. Can anyone help me figure out what I'm doing wrong? I just want to flash some ROMs with up to date soft-/firm-ware.
new version is buggy
i had an update for my clockwork mod when i tried to download a rom so installed the updated clockwork but in the end i found the new version 5 to be very buggy but if you want to try just try installing another rom (do a nandroid backup first) and it should install the new recovery but in my oppinion i wouldnt bother upgrading why update something that works thats the common saying
Well, in this case, I'm trying to upgrade from Cyanogen (which I've backed up), to Synergy's GingerSense RS1 for the Droid Incredible. However, while it flashes the ROM, it hangs on the boot up screen when rebooting, so I have to go back to Cyanogen. What got this whole thing started was figuring out what I had to do to get that working.
I'm on HBOOT 079, CWR 2.5.1.2, and none of ROM Managers automated features work because of the "Can't located /dev/tty0" function. The only advice I could find online for that was that 2.5.x is too old, and I need at least 3.0.0.8 to load some of these ROMs.
Small error, I didn't run "unrevoked-forever" so I'm not S-OFF yet.
shadowfyre26 said:
Small error, I didn't run "unrevoked-forever" so I'm not S-OFF yet.
Click to expand...
Click to collapse
You did say you "turned S-ON" but really you just, as you said, didn't have S-OFF. So I'm guessing your problem was solved when you got S-OFF and tried again right?
Yup, I just fixed the S-ON issue into S-OFF, and lo and behold it worked.
*looks around sheepishly* Let us never speak of this again.
I had the stock rom installed but I had recovery on it and I decided to just load the new rom on it and I didn't realize I was suppose to root the phone before flashing. So basically everything was a little weird. When it started and was at the unlock screen it said sim card is locked and I don't have a sim card. Then later when looking at the sd card it was saying -- for the available space and space used. I tried to format it and it said please wait while calculating and was showing some odd algebra equation. Then it just did a soft reset and basically showed the IHO boot screen then the loading screen. No LG icon thus being a soft reset. But that is all it would do. And upon trying to shut it off it was showing no option to shut off just a bunch of odd icons and one saying airplane mode or something with a power icon next to it. So I chose it and it was saying something like reset and it had menu for a title. So I chose it and it shut off. So I was just wanting to make sure that if I rooted it before re installing the IHO that this would clear up those issues.
You need a custom recovery to install custom ROMs. Here is a tutorial how to flash one without rooting.
You need custom recovery to install custom roms and to flash custom recovery without rooting Follow http://forum.xda-developers.com/showthread.php?t=1318750
you just need to format your system with any method
and then flash new one
that's what recovery do
may be sometime adb also help
I have this installed on my phone: Xionia_CWMA_12518.6_VM_Recovery-signed and I use it to get the phone formated with a new rom. I know that I can get a custom rom on the phone perfectly fine when it is rooted. I guess since I did it without it being rooted it somehow made things look corrupt after installing the rom without the phone being rooted. I hope that it will work properly when I get the phone re rooted and install the latest version of the rom I use: BACKside-IHO-VM670-11022011 this is the first rom I ever used to get on my phone so I was thinking of sticking with it unless there is a more stable one that performs better and can run most anything thrown at it. As I have run into a few issues with this rom. I can end up having things run off the sd card and they end up crashing the phone and doing a hard reset as well as games or apps not wanting to work at all and give a force close error. I am really wanting to play annoying orange kitchen carnage I have even tried a stock rom at 2.2.1 and it still didn't work. Is there a specific kernel I should be installing or something?
http://forum.xda-developers.com/showthread.php?t=1197991
This should answer all your questions.
Ok thanks. Just wanted to know as I know how to root and get a rom installed on the phone. So thanks for the help.
Hey all,
I'm very new to Cyanogen, so sorry if this is a very n00b question.
The ROM Manager doesn't appear to work. It keeps telling me I'm not running ClockWorkMod recovery, and cannot connect to the web to download. I purchased the premium version thinking it would solve this (as well as to support the dev), but no luck. Is it just an issue with the nightlies not capable of handling ROM manager yet, or is it a setting of some sort that I'm neglecting? It's not a huge deal, but it looks like such a nice, simple way to stay up-to-date with the nightly builds as opposed to updating through CWM, wiping, etc.
I saw a post mentioning to go into developer tools and enable root access. The closest I found was in settings and I allowed apps and ADB root access, but this didn't help.
Any suggestions would be greatly appreciated, thanks!
I'm a bit confused, Why do you require ROM manager? The CWM that is built in with the ICS Kang releases should be doing everything that is required, then again, your reply would matter.
I think I am having the same issue. When I try to Flash ClockworkMod Touch in Rom Manager it keeps telling me I need to first install ClockworkMod Recovery even though I have Recovery 5.5.0.4 currently installed. It did the same thing when I had Recovery 4.0.0.4 installed.
I even tried to "Flash ClockworkMod Recovery" (First option in ROM Manager) and it does nothing.
Any ideas?
BEcause the same menu is in the CWM recovery lol
I'm following one of the threads that updates the kang build every 3 days, and as opposed to having to boot through CWM, wipe, install, then re-install apps and replace widgets, I thought I could update through ROM Manager instead.
It sounds like Sn0warmy and I are having similar issues.
From what I've heard the ROM Manager doesn't really work for the tab yet. If you want to update without replacing all your apps you can just flash the zip file in CWM without doing a wipe. If it causes problems then you could do a wipe & reflash afterwards.
Dolfan058 said:
I'm following one of the threads that updates the kang build every 3 days, and as opposed to having to boot through CWM, wipe, install, then re-install apps and replace widgets, I thought I could update through ROM Manager instead.
It sounds like Sn0warmy and I are having similar issues.
Click to expand...
Click to collapse
ROM manager works but it's wonky on the ICS kangs. It doesn't do anything that you can't already do in recovery, so there's no real advantage anyways. Oh, and don't use ROM manager to install a new recovery, and CWR touch doesn't work for the GT10.
^You saved me the trouble of insisting Why thank you good sir.
Thanks for the replies. I'll keep updating through CWM.
Coffeebeans, obviously I'm following your thread (thanks for the good work!) and I tried flashing over once but I got a ton of process media FCs so I figured wiping was the best way to go and have done so ever since. Probably should invest in titanium backup at this point so I don't have to reinstall from market everytime I wipe.
Thanks again for the help y'all.
It worked once with 4/17 build of CM9. After that, it has never worked again. It boots into recovery and pretends its flashing, but stops half a second later and restarts.
Something odd happened today when I tried to update. It rebooted and phone locked up and screen went black. I took out the battery and put it back in then held up and power to go into CWM. All of a sudden Rom Manager took over and flashed the rom as well as the additional zips successfully and rebooted. Everything works.
CWM tries to flash from /emmc. Rom Manager tries to flash from /sdcard and fails. It may be due to the swapped mount points on CM9. in CWM they are still swapped, even if you check the use internal storage box and everything shows up properly in CM9.
ok so i wouldnt say im a noob but im not as advanced as some of yous. last night i flashed a leaked ics onto my phone and loved it with one exception. i couldnt figure out how to root it. all my apps are backed up on titanium backup and i didnt want to have to get all of them manually. so i flashed back to stock using odin with a file i used back when that crappy update came out. i rooted it with super one click and and then went to put on a prerooted ics... when in recovery mode now i get this message
cant access to '/system/csc/att/system/'
i try putting on cwm and siyah and i keep getting authentication errors and the installation aborts. also recovery mode wont read my external sd card now. when the phone is booted up it works fine except i tried to do the factory ota update and it keeps failing. i tried reflashing back to stock again and did the update unrooted and it still failed.
i know you guys hate hate when people ask without researching so i did SOME forum browsing and found nothing. sorry i dont really have time to look too extensively. i just want to know how to fix it. i appreciate any help i can get
Joeyjr25 said:
ok so i wouldnt say im a noob but im not as advanced as some of yous. last night i flashed a leaked ics onto my phone and loved it with one exception. i couldnt figure out how to root it. all my apps are backed up on titanium backup and i didnt want to have to get all of them manually. so i flashed back to stock using odin with a file i used back when that crappy update came out. i rooted it with super one click and and then went to put on a prerooted ics... when in recovery mode now i get this message
cant access to '/system/csc/att/system/'
i try putting on cwm and siyah and i keep getting authentication errors and the installation aborts. also recovery mode wont read my external sd card now. when the phone is booted up it works fine except i tried to do the factory ota update and it keeps failing. i tried reflashing back to stock again and did the update unrooted and it still failed.
i know you guys hate hate when people ask without researching so i did SOME forum browsing and found nothing. sorry i dont really have time to look too extensively. i just want to know how to fix it. i appreciate any help i can get
Click to expand...
Click to collapse
Start with getting back to stock using this guide. Check for ICS bootloaders too, you probably flashed them and you have to get stock ones back (careful, flashing bootloaders can cause hardbricking). Once you're back to stock and rooted, you shouldn't need to ever use PC Odin again.
Then use this guide for rooting/flashing.
One other note: when you tried to install CWM, it sounds like you loaded an update.zip onto your phone then tried to install it using stock recovery. Stock recovery won't let you install unsigned update.zips, which is why that method for getting CWM on your phone will never work (hence the authentication error and installation abort). For our phone, CWM is only included in custom kernels, that's the only way to get it on there, and don't even think about updating or changing it via other means. Just flash a custom kernel, it'll include CWM, use it until you want to switch kernels.
Hit my thanks button, I was really nice this time. And post in Q/A next time as well.
EDIT: Skip the second guide if all you want is stock. You should be able to update OTA after following the first guide. Though even if stock is what you want, I highly recommend flashing a custom GB kernel because a) they're more stable and faster and b) you'll have CWM in case you need it.
You started off mentioning about "leak ics" which I have absolutely zero experience.
My suggestion:
1. Try to get it back to stock. Make sure it works correctly.
2. If hasn't rooted yet, do so.
3. Getting CMW into the device by flashing custom kernel.
4. From there, install any ICS ROM you want.