Hey all.
I've been trying to flash ShadowROM onto my eris (got the eris dl off their site), but everytime I try to flash it on it gives me "E:missing file: recovery/recovery-from-boot.p" and "E:Verification failed" and then aborts the installation.
So I then tried re-downloading the rom, but the same thing happened again.
Any ideas on what might be going on? I did all my wipes and everything so I'm not really sure what could be going on. Also I have been using Evil Eris for a while, if that makes any difference.
Thanks in advance for any advice.
EDIT: Also I'm currently on 2.1 so I'm not sure if theres anything I need to do to be able to put a 2.2 rom on my eris.
greekstallion said:
Hey all.
I've been trying to flash ShadowROM onto my eris (got the eris dl off their site), but everytime I try to flash it on it gives me "E:missing file: recovery/recovery-from-boot.p" and "E:Verification failed" and then aborts the installation.
So I then tried re-downloading the rom, but the same thing happened again.
Any ideas on what might be going on? I did all my wipes and everything so I'm not really sure what could be going on. Also I have been using Evil Eris for a while, if that makes any difference.
Thanks in advance for any advice.
Click to expand...
Click to collapse
At this time it doesn't work with Amon's recovery. It only will work if you use clockwork, which isn't recommended. I got it to work but I use a rom kitchen and replaced the boot-img.
Busphan said:
At this time it doesn't work with Amon's recovery. It only will work if you use clockwork, which isn't recommended. I got it to work but I use a rom kitchen and replaced the boot-img.
Click to expand...
Click to collapse
Ah I see, hrm I really wanted to give it a try too.
Out of curiosity, why isn't clockwork recommended?
greekstallion said:
Ah I see, hrm I really wanted to give it a try too.
Out of curiosity, why isn't clockwork recommended?
Click to expand...
Click to collapse
There have been a few reports of bricks from just flashing roms.
Busphan said:
At this time it doesn't work with Amon's recovery. It only will work if you use clockwork, which isn't recommended. I got it to work but I use a rom kitchen and replaced the boot-img.
Click to expand...
Click to collapse
You don't need to replace the boot.img....the rom just needs to be signed and it will flash fine amon's. Clockwork can load an unsigned rom but amons can't....
Conap said:
You don't need to replace the boot.img....the rom just needs to be signed and it will flash fine amon's. Clockwork can load an unsigned rom but amons can't....
Click to expand...
Click to collapse
Thanks for the info that would have been easier. I just replace it because of the error message.
**please ignore, sorry!**
Clockwork wont hurt your phone. Also when you go into to clockwork and flash clockwork recovery it will only temp use clockwork as a recovery just to install the rom. After that it will boot into amon.
"Clockwork won't hurt your phone" Boyyyyyyyyy I bet a lot of people with broken eris's would be glad to hear that!
Hungry Man said:
"Clockwork won't hurt your phone" Boyyyyyyyyy I bet a lot of people with broken eris's would be glad to hear that!
Click to expand...
Click to collapse
You running clockwork Hungry Man? I wasn't ever trying to stop anyone, I just wanted them to look into it themselves.
Conap said:
You don't need to replace the boot.img....the rom just needs to be signed and it will flash fine amon's. Clockwork can load an unsigned rom but amons can't....
Click to expand...
Click to collapse
Im not knew to the rooting and flashing thing when it comes to my eris, but i do have to ask for my knowledge: what do you mean by the rom needs to be signed?? thanks!!
duccicucci said:
Im not knew to the rooting and flashing thing when it comes to my eris, but i do have to ask for my knowledge: what do you mean by the rom needs to be signed?? thanks!!
Click to expand...
Click to collapse
He means that this rom will not work with amons recovery because it isn't signed. You can create a zip that isn't sign, meaning you never used a program that signs zips, but you can't flash a zip in amons unless it is signed. So if you just create a zip it probably won't work, but if you use an autosigner then you will be in buisness. I hope this helps, probably not because I have been drinking.
Just so there's full information in case someone finds this thread in the future.
There was a bug with using Clockwork Mod Recovery with the Eris. They squashed it, at least 2-3 months ago.
Besides, you don't have to get rid of amon in order to use clockwork. Just download ROM Manager from the Market and it will make it so that you can load clockwork from amon. Then you get all the advantages of ROM Manager and clockwork without any hassles.
Sent from my xtrSENSE Eris using XDA App
I'm having issues loading the rom, it keeps staying on the 3 skateboarding droids then it reboots back to the skateboarding droids whats going on?
johnny quest said:
I'm having issues loading the rom, it keeps staying on the 3 skateboarding droids then it reboots back to the skateboarding droids whats going on?
Click to expand...
Click to collapse
This seems to be a hit or miss build for the Eris. About 50% (guestimated) of Eris users are unable to boot with v0.2.x and there is no known reason why, even after viewing logcats.
I have dropped the entire desirec device configuration (a mix of kaos & conap) and have forked over a pure conap device config for v0.3.x to attempt to fix this issue. We won't know for sure until v0.3.0 finally releases to the masses. All my testers (even myself) are able to run v0.2.x just fine.
There is no ETA for v0.3.0 at this time.
I'm sorry if this is off topic but I need to ask. Were can you get themes for ShadowRom? Do you just use anything that is for cynogen? Is it best to use metamorph or and update.zip?
I flashed shadowrom using clockmod just fine.
Sent from Eris with Froyo
xtreme3737 said:
I'm sorry if this is off topic but I need to ask. Were can you get themes for ShadowRom? Do you just use anything that is for cynogen? Is it best to use metamorph or and update.zip?
Click to expand...
Click to collapse
We currently have zero themes for the eris. We rely on themers to provide ports, which none have done yet.
Guess I'm one of the lucky ones
billygalbreath said:
This seems to be a hit or miss build for the Eris. About 50% (guestimated) of Eris users are unable to boot with v0.2.x and there is no known reason why, even after viewing logcats.
I have dropped the entire desirec device configuration (a mix of kaos & conap) and have forked over a pure conap device config for v0.3.x to attempt to fix this issue. We won't know for sure until v0.3.0 finally releases to the masses. All my testers (even myself) are able to run v0.2.x just fine.
There is no ETA for v0.3.0 at this time.
Click to expand...
Click to collapse
I flashed this rom and it was slow and jittery and all around not good.
Sent from my ERIS using XDA App
Related
Ok I'm worried because I read some forums today saying that clockworkmod recovery will give more chances to brick your phone so I want to know which recovery is best to use
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Droid Eris
Plainjane1 with ota 2.1
and evil Eris 2.0.1
I'm using amonra and have read some of the same things. I'd love for someone to let me know what the difference is. I'm also curious why ROM Manager makes you use Clockwork.
Rooted Eris running Eris Lightning (CyanogenMOD build)
RA is the only recovery to use CLOCKWORK has given people bricks....me included. It didn't happen right away I had been using CLOCK for about a month and a half before i had problems with it.
Amon RA no question
Sent from my Eris using XDA App
saintdice said:
I'm using amonra and have read some of the same things. I'd love for someone to let me know what the difference is. I'm also curious why ROM Manager makes you use Clockwork.
Rooted Eris running Eris Lightning (CyanogenMOD build)
Click to expand...
Click to collapse
you can use amon_ra with rom manager ..... it gives you the option of installing amon_ra
ROM manager has always said "Needs Clockwork mod" for me...
I used clockwork recovery image with the rom manager for a little while, mainly just because it was easier then flashing an image manually.
after a couple times of nandroid backups not working, and the talks of how it bricks the eris, I sucked it up and installed Amon_Ra's. never had a problem with it.
I get the same. Maybe the option shows up with the paid version'
Hungry Man said:
ROM manager has always said "Needs Clockwork mod" for me...
Click to expand...
Click to collapse
Eris running Eris Lightning (CyanogenMOD build)
I had the paid version.
Hungry Man said:
I had the paid version.
Click to expand...
Click to collapse
and you could flash roms using armons recovery via the interface in rom manager? i think thats what they were getting at. not just flashing the recovery.
Hey there.
My Droid Eris was rooted about a month ago with the Universal Root Method for the 1.49 bootloader. I am unable to flash certain ROMs on my phone such as Kaos Froyo and Plain Jane. I get a "Verification Failed, Installation Aborted" error every single time I try it. I have tried flashing the ROMs using both Clockwork and Armon RA. Clockwork just returns to the main menu, and Armon gives the verification error. I tried searching the forum and found very little people with the problem. In case it matters, I also tried formatting my memory card, wiping Dalvik and memory, and un-rooting my Eris by loading a PB00IMG.zip onto it.
Could anyone help me out here, as I am fairly new to this?
Thank you guys.
jonathan.moran said:
Hey there.
My Droid Eris was rooted about a month ago with the Universal Root Method for the 1.49 bootloader. I am unable to flash certain ROMs on my phone such as Kaos Froyo and Plain Jane. I get a "Verification Failed, Installation Aborted" error every single time I try it. I have tried flashing the ROMs using both Clockwork and Armon RA. Clockwork just returns to the main menu, and Armon gives the verification error. I tried searching the forum and found very little people with the problem. In case it matters, I also tried formatting my memory card, wiping Dalvik and memory, and un-rooting my Eris by loading a PB1000.img onto it.
Could anyone help me out here, as I am fairly new to this?
Thank you guys.
Click to expand...
Click to collapse
Did you format your sd card to fat32 no partitions?
Yes, I formatted it with the recovery.
jonathan.moran said:
Yes, I formatted it with the recovery.
Click to expand...
Click to collapse
So you set both sides to zero right?
Busphan said:
So you set both sides to zero right?
Click to expand...
Click to collapse
Yeah.
But just my luck, it doesn't help anything.
jonathan.moran said:
Yeah.
But just my luck, it doesn't help anything.
Click to expand...
Click to collapse
Ok, have you loaded the engineering bootloader (s-off)?
Busphan said:
Ok, have you loaded the engineering bootloader (s-off)?
Click to expand...
Click to collapse
Uhm, no.
I am rooted with the S-ON 1.49.0000 bootloader. It also says (PB0010000) next to the bootloader number.
jonathan.moran said:
Uhm, no.
I am rooted with the S-ON 1.49.0000 bootloader. It also says (PB0010000) next to the bootloader number.
Click to expand...
Click to collapse
Jcase has a thread on how to change to the s-off bootloader. I think that might be part of the problem. I'm pretty sure I saw someone having similar troubles until he changed his bootloader. I would try that. Just read the thread thoroughly to ensure that you don't brick it. This bootloader is safer when rooted so it is best to run the s-off one.
Busphan said:
Jcase has a thread on how to change to the s-off bootloader. I think that might be part of the problem. I'm pretty sure I saw someone having similar troubles until he changed his bootloader. I would try that. Just read the thread thoroughly to ensure that you don't brick it. This bootloader is safer when rooted so it is best to run the s-off one.
Click to expand...
Click to collapse
Alright.
Thank you for the help!
I hadn't even considered the bootloader.
I will try Jcase's thread when I return home, I have to do a few errands.
Thank you again!
jonathan.moran said:
Alright.
Thank you for the help!
I hadn't even considered the bootloader.
I will try Jcase's thread when I return home, I have to do a few errands.
Thank you again!
Click to expand...
Click to collapse
Anytime
10 chara
I have the same issue. I am rooted and have boot loader s-off engineering boot loader.
What happens Isherwood rom will flash but won't make it past thru boot up. Freezes or boot loops. Only certain roms seem to ever make it to the final stages.
Had a lot of issues with nonsensical v4.6. Been round and round the barn on this one.
Jp50 said:
I have the same issue. I am rooted and have boot loader s-off engineering boot loader.
What happens Isherwood rom will flash but won't make it past thru boot up. Freezes or boot loops. Only certain roms seem to ever make it to the final stages.
Had a lot of issues with nonsensical v4.6. Been round and round the barn on this one.
Click to expand...
Click to collapse
So you haven't found a fix yet?
Hopefully changing his bootloader will work. If not at least he will be on a safer bootloader.
Busphan said:
So you haven't found a fix yet?
Click to expand...
Click to collapse
Not yet. Although I was able to flash Tazz froyo. 2.0 over 1.0 last night with no isssues. That rom has been good to me.
Sent from my Tazz Froyo 2.0 using Tapatalk
Jp50 said:
Not yet. Although I was able to flash Tazz froyo. 2.0 over 1.0 last night with no isssues. That rom has been good to me.
Sent from my Tazz Froyo 2.0 using Tapatalk
Click to expand...
Click to collapse
Yeah, Tazz's rom is my fav.
Jp50 said:
I have the same issue. I am rooted and have boot loader s-off engineering boot loader.
What happens Isherwood rom will flash but won't make it past thru boot up. Freezes or boot loops. Only certain roms seem to ever make it to the final stages.
Had a lot of issues with nonsensical v4.6. Been round and round the barn on this one.
Click to expand...
Click to collapse
My phone won't even get that far into the flashing process.
It just stops the whole thing before it even starts.
But I'm back home now, hopefully when I change my bootloader that it will help.
jonathan.moran said:
My phone won't even get that far into the flashing process.
It just stops the whole thing before it even starts.
But I'm back home now, hopefully when I change my bootloader that it will help.
Click to expand...
Click to collapse
Just let us know, if it doesn't we will go from there.
jonathan.moran said:
My phone won't even get that far into the flashing process.
It just stops the whole thing before it even starts.
But I'm back home now, hopefully when I change my bootloader that it will help.
Click to expand...
Click to collapse
that sounds like a corrupted download. Which browser are you using? Chrome has been known to corrupt downloads.
The other thing to try is, back up all the contents of your sd card. Reformat the card in the phone, boot into amons ra and select partition. set all the values to zero, this will create a FAT32. copy back just the stuff you need back to the sd card, reload the rom to the sd card.
do both wipes, flash and try again.
If its not getting past the installation/flashing stage that has to be an issue with the file itself.
I never solved my issues and resolved that I can only work with certain roms. Tazz's is a great rom and I love it. well, not love but really enjoy it.
which roms are you successful in loading? There may be a connection to the type of riom and what it was based off of. i.e. sprint hero based, or cyanogen or froyo based etc.
Have you tried xtrrom or xtr sense? those loaded with no issues for me.
Aloysius V11 and V12 are both good for me
Roms that don't work for me:
Kaos Froyo (tried so many times, really want to try this one)
any CELB based roms
Nonsensikal v 4.4 and above (3.4 worked great for some reason, just any updates afterwards didn't work.
Jp50 said:
which roms are you successful in loading? There may be a connection to the type of riom and what it was based off of. i.e. sprint hero based, or cyanogen or froyo based etc.
Have you tried xtrrom or xtr sense? those loaded with no issues for me.
Aloysius V11 and V12 are both good for me
Roms that don't work for me:
Kaos Froyo (tried so many times, really want to try this one)
any CELB based roms
Nonsensikal v 4.4 and above (3.4 worked great for some reason, just any updates afterwards didn't work.
Click to expand...
Click to collapse
It really just varies for me.
I can successfully load Evil Eris 4.0 after trying for hours at a time, but if I try to re-flash it again, I get the error.
I can't flash the Froyo ROMs that I have tried either.
The only one that I had absolutely no problem flashing was Evil Eris 3.0
And that's it.
It's quite strange..
I was trying to install axura custom ROM. So I copied it to the sdcard and then I rebooted to recovery. Everytime I choose "reisntall package" this what shows up :
i51.tinypic.com/212fpfa.jpg
you need to download rom manager and flash clockwork recovery first. You do not install rom's from the stock recovery. Read the noob guide if you have not already.
if you do have CWR, go to install from zip from sdcard and choose zip.
yes, I installed that already and chose Samsung vibrant after that i rebooted to recovery and that's what happened.
anyone who knows what the problem is?? been fixing it for a day.. but still can't make it work.
chase15 said:
anyone who knows what the problem is?? been fixing it for a day.. but still can't make it work.
Click to expand...
Click to collapse
Are you coming from stock 2.2?
not sure..i got this phone with 2.2 already installed.. im pretty sure its the stock..
chase15 said:
not sure..i got this phone with 2.2 already installed.. im pretty sure its the stock..
Click to expand...
Click to collapse
Ran into some crazy issues when rooting/custom flashing a friend's vibrant from stock 2.2. I ended up using ODIN back to 2.1 and then rooting and flashing a custom rom. The file system on 2.2 is different and CWM doesn't like it right away.
Also, that 3e recovery is a ****.
Read some of this...
http://forum.xda-developers.com/showthread.php?t=833423
http://forum.xda-developers.com/showthread.php?t=945294
and watch this
http://www.youtube.com/watch?v=AnY7P14JSWQ
Lots of work, but worth it. Please read up on other options too.
Good luck
ok.. so all this means... flashing ack to 2.1.. using odin.. then install custom ROM?
Essentially, yeah. Here's an OP that I just stumbled across. It should step you through it. I wish I had seen this when I was fumbling with errors messages like that on my friend's phone.
EDIT: This is a non-ODIN solution:
http://forum.xda-developers.com/showthread.php?t=925400
Good luck
chase15 said:
ok.. so all this means... flashing ack to 2.1.. using odin.. then install custom ROM?
Click to expand...
Click to collapse
Yeah, I had the same problem with my friend's phone. After you go back to stock, you can use z4root to apply a temporary root and then install CWR. Kind of a pain, but it gets the job done.
Sent from my SGH-T959 using XDA App
alright.. flashing 2.1 now.. ill come bck later.. if everything will work.
problem solved! Successfully flashed axura.. Thanks!
Rock on.
Congrats!
Vibrant on T-Mobile.
Powered by Whiskey and Voodoo magic while riding a Dead Horse.
chef_w said:
Rock on.
Congrats!
Vibrant on T-Mobile.
Powered by Whiskey and Voodoo magic while riding a Dead Horse.
Click to expand...
Click to collapse
thank you.. now waiting for my ffc.. gonna install it when it arrives.
I'm trying to flash to stock 2.3.4 from Cyanogen 7 and so far I've had no luck. I've tried flashing from both internal and external memory and this is what I get:
Installing: /emmc/234-sb-release.zip
Finding update package...
Opening update package...
E:Can't open /emmc/234-sb-release.zip
(bad)
Installation aborted.
I'm opening to flashing to stock by some other method, but I have no idea why this won't work for me. Any help is appreciated! Thanks!
Try to download the ROM, although it seems you've tried that. If that doesn't work, maybe you are using the wrong recovery? Try romracers recovery, it's the best right now for the Atrix.
Sent from my MB860 using XDA App
what about loading a rom like alien? where as its like stock, based off stock but has some tweaks and upgrades?
c_86 said:
what about loading a rom like alien? where as its like stock, based off stock but has some tweaks and upgrades?
Click to expand...
Click to collapse
Yeah. Alien didn't work either. I'll probably try a different recovery if I have to. It sucks that I'm going to have to put a lot of work into this seeing as I'm not even keeping the phone (passing it along to my dad).
Are u using an old recovery? Use rom managers recovery. (Cwm) if that doesn't work its possible there was data corruption with the rom downloads.
Sent from my MB860 using Tapatalk
It's really not a lot of work at all, just a few fastboot commands. Probably an issue with the dl though but try romracers in conjunction with a fresh download, most people only recommend the CWM recovery if you're flashing CM7.
jtc276 said:
Yeah. Alien didn't work either. I'll probably try a different recovery if I have to. It sucks that I'm going to have to put a lot of work into this seeing as I'm not even keeping the phone (passing it along to my dad).
Click to expand...
Click to collapse
live4nyy said:
It's really not a lot of work at all, just a few fastboot commands. Probably an issue with the dl though but try romracers in conjunction with a fresh download, most people only recommend the CWM recovery if you're flashing CM7.
Click to expand...
Click to collapse
Just tried flashing with fastboot also. This is what I get:
EOCD not found, not Zip
error: failed to access zipdata in (then it's just a huge list of random characters that I'd rather not type out).
I've tried this with 3 different roms: 234-w-release.zip, 234-sb-release.zip, and Alien-4.zip. They all had the same result of not working.
But that's not all. I also flashed Rom Racer's recovering (successfully) and tried to flash the same files that way. Still nothing worked.
I find it extremely unlikely that 3 ROMs that were all downloaded on different days will not work at all.
If anyone has anymore ideas, I'll be up for a while.
Also, is it possible for me to flash 2.3.4 using RSD? If so, I can just do that. I want to make sure because I know flashing back prior to 2.3.4 can cause a hard brick.
Are you using the Rom Manager recovery or the custom recovery?
For Fruitcake roms (Stock based roms) needs the custom cwm recovery. Thats here: http://forum.xda-developers.com/showthread.php?t=1204500
edit: do not SBF!! that results in a hard brick
also, download the files with the built in browser's downloader, dont use a download manager, sometimes they can corrupt the zip
I think I've got it to work! I reflashed the recovery you directed me to, download a new file, and it actually flashed this time. I should be good to pass this phone along now.
Thanks to everyone who helped me out with this one! I really do appreciate it!
While I can agree that flashing an sbf through rsd poses a risk of hard bricking your device, I do have to add that it is not definitive. I have sbf'ed twice now, once from pi-crust and once from cm7, so it can be done, but I would also suggest just using fruit cakes.
princeandy63 said:
edit: do not SBF!! that results in a hard brick
Click to expand...
Click to collapse
That's weird because the link he gave you was the romracer recovery. What were you using before that you thought was romracer?
jtc276 said:
I think I've got it to work! I reflashed the recovery you directed me to, download a new file, and it actually flashed this time. I should be good to pass this phone along now.
Thanks to everyone who helped me out with this one! I really do appreciate it!
Click to expand...
Click to collapse
That's true. I hate when people spread misinformation. 2.3.4 stock .sbf will not cause a brick. Only earlier .sbfs will.
Sent from my MB860 using Tapatalk
Just like the title says why should we not use rom-manager on this phone?
from what i can remember it installs a ****ty version of CWM that doesn't cooperate well with our phones.
Boobie Watcher said:
from what i can remember it installs a ****ty version of CWM that doesn't cooperate well with our phones.
Click to expand...
Click to collapse
gotcha. i wish koush would do something about rom manager because the atrix also had a wipping issues on roms and he never fixed it
From my recent experience with the SGSII, the recovery is integrated into the kernel (unlike HTC devices which have a dedicated partition for it). My guess is ROM Manager can't flash it, since it doesn't have the kernel image.
Phoenix84118 said:
From my recent experience with the SGSII, the recovery is integrated into the kernel (unlike HTC devices which have a dedicated partition for it). My guess is ROM Manager can't flash it, since it doesn't have the kernel image.
Click to expand...
Click to collapse
gotcha thats intresting
You shouldn't use it on any phone anyway, your best bet is going into recovery
Sent from my Inspire 4G using XDA App
Haha too funny I was literally wondering this last night. Glad you asked kuz I couldn't find an answer when I did a quick search.
Edit: so I've been running miui this week and see the app rom manager. I'm fine as long as i don't actually do anything through it correct?
Sent from my SGH-I777 using Tapatalk
It breaks and does weird crap - I've heard it works OK if (and only if) you are currently on CM7.
But since you're most likely using it to move to/from another ROM... Just three-finger into recovery or if the ROM has an extended power menu use that for recovery.
Its best to just use three-finger or the extend menu power menu like Entropy said. I've seen Rom manager mess up leading to a semi-brick phone.
Hey all,
First time poster and new to rooting.
I ended up attempting to use rom manager to load CWM right after root, but I think that borked my wifi.
What can I do if I've already used it? I did it because I hadn't yet seen all the xda threads on NOT using it, and the place I was was not as well informed as you folks.
Also, how do I get CWM if not via ROM Manager?
My brothers EVO was royally effed up from using ROM Manager. Became a paperweight until Sprint authorized a replacement.
karankshah said:
Hey all,
First time poster and new to rooting.
I ended up attempting to use rom manager to load CWM right after root, but I think that borked my wifi.
What can I do if I've already used it? I did it because I hadn't yet seen all the xda threads on NOT using it, and the place I was was not as well informed as you folks.
Also, how do I get CWM if not via ROM Manager?
Click to expand...
Click to collapse
Read through the FAQs and this thread - CWM is included in kernels that support it.
karankshah said:
Hey all,
First time poster and new to rooting.
I ended up attempting to use rom manager to load CWM right after root, but I think that borked my wifi.
What can I do if I've already used it? I did it because I hadn't yet seen all the xda threads on NOT using it, and the place I was was not as well informed as you folks.
Also, how do I get CWM if not via ROM Manager?
Click to expand...
Click to collapse
I ended up figuring most of this out so I wanted to close this out (for anyone that stumbles past my original post).
Here's what I did:
I uninstalled ROM Manager - but this didn't get the wifi going.
I reflashed with the stock ROM and unrooted kernel - this still didn't help.
I did a factory reset - this did manage to get it going.
I was able to track down a CWM standalone that I flashed it with (using Odin).
I followed that up with a root, a wipe, and then a fresh flash of UnNamed.
Phone seems to be working fine.
Andrew149 said:
Just like the title says why should we not use rom-manager on this phone?
Click to expand...
Click to collapse
When I first rooted my phone I installed rom manager because it looked easier to just pick the file that u wanted flashed and it would do it for u, so u wouldn't have to play with the volume keys. But every time I tried to do anything with it, it just said certificate not found. Aborting. So u shouldn't use rom manager. I think it works with the roms that u download of the app but not ones from XDA.
Sent from my SGH-I777 using XDA App
I loaded a kernal with cwm. I use rom manager to install Google apps. After new rom loads up.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Flash entropys kernel. Daily driver
Sent from my Samsung Galaxy S II
If you're on CM7, ROM Manager can be used to install gapps - that's about the only thing it doesn't seem to choke on.
karankshah said:
Hey all,
First time poster and new to rooting.
I ended up attempting to use rom manager to load CWM right after root, but I think that borked my wifi.
What can I do if I've already used it? I did it because I hadn't yet seen all the xda threads on NOT using it, and the place I was was not as well informed as you folks.
Also, how do I get CWM if not via ROM Manager?
Click to expand...
Click to collapse
You cannot get CWM via ROM Manager - that is the point. It comes with certain custom kernels such as Entropy's DD kernel. If you do not have a CWM kernel - you will more than likly need to use Odin to get a kernel with CWM.
If you have totally screwed things up - look in the dev thread for "the return to stock" section and start over doing it the right way
karankshah said:
I ended up figuring most of this out so I wanted to close this out (for anyone that stumbles past my original post).
Here's what I did:
I uninstalled ROM Manager - but this didn't get the wifi going.
I reflashed with the stock ROM and unrooted kernel - this still didn't help.
I did a factory reset - this did manage to get it going.
I was able to track down a CWM standalone that I flashed it with (using Odin).
I followed that up with a root, a wipe, and then a fresh flash of UnNamed.
Phone seems to be working fine.
Click to expand...
Click to collapse
Hi first post as well XDA forums so in depth and helpful decided I wanted to be apart of it. Still a noob though ill work my way up.
I am trying acheive the same goal he is, that is to say Instal the UnNamed (it is exactly what I want) Rom on my Samsung Galaxy S2 Skyrocket.
Keep it brief: Rooted my phone using root exploit:
it will not let me post link. the zergrush one
and bellow flashed clockwork mode using stand alone not ROM because of this forum. Model 5.0.2.6
I wipe catch, battery, then format everything. Then I start to flash the ROM. The installation begins. It cleans and formats everything again, then sais that there was an error in the file and it fails. After this if I dont restore my phone will not start. Ive tried it several times being even more thorough on procedure and its the exact same error every time.
Im just wondering if its the way I rooted it is incorrect, The CWM Im using is not the correct one, or if Im doing something wrong entirely. I think it might be CWM but I have not been able to locate one like he did that worked.
Any help, suggestions, criticism or advice would be very helpful. I just thought Id ask. thanks in advance ^^
Elemblue said:
Hi first post as well XDA forums so in depth and helpful decided I wanted to be apart of it. Still a noob though ill work my way up.
I am trying acheive the same goal he is, that is to say Instal the UnNamed (it is exactly what I want) Rom on my Samsung Galaxy S2 Skyrocket.
Keep it brief: Rooted my phone using root exploit:
it will not let me post link. the zergrush one
and bellow flashed clockwork mode using stand alone not ROM because of this forum. Model 5.0.2.6
I wipe catch, battery, then format everything. Then I start to flash the ROM. The installation begins. It cleans and formats everything again, then sais that there was an error in the file and it fails. After this if I dont restore my phone will not start. Ive tried it several times being even more thorough on procedure and its the exact same error every time.
Im just wondering if its the way I rooted it is incorrect, The CWM Im using is not the correct one, or if Im doing something wrong entirely. I think it might be CWM but I have not been able to locate one like he did that worked.
Any help, suggestions, criticism or advice would be very helpful. I just thought Id ask. thanks in advance ^^
Click to expand...
Click to collapse
UnNamed is not a Skyrocket ROM nor are any other ROMs in this subforum. You want to go here: http://forum.xda-developers.com/forumdisplay.php?f=1399