I installed BAMF 1.6.3 remix and I noticed that I don't have some of the features that were listed in his OP.
For ex. I still have my location icon in my status bar, when I press on the themed rosie button on the right it still opens up the personalize settings no matter what icon I chose to put there. I don't have the 6 bar signal strength. I don't have the power control settings in my pull down menu, but I do have the power control settings apk in my drawer. Don't have widget picker, Don't have the extra power options when the power button is pressed, reboot, hibernate, etc.... Also when a call is missed it doesn't show the number in my pulldown menu only that I had 3 missed calles from*86 and something about CDMA on the missed call icon.
These are the few that I noticed in the couple hours of it being on my phone. I am just wondering if this is normal or what I may have did wrong and how to get these working as I thought they were part of the ROM itself.
Thanks
Did you flash the rom in rom manager??? If so, thats most likely what created the missing issues.
You have to flash the rom thru CWR for you to get everything up and running fully.
Yeah I downloaded from the forum then installed using ROM manager. I will re-install using CWR. I will post my results. Thanks for the quick response. Oh yeah I noticed my post was at like 1:34 am? It's only 8:47 where im at?
So I re-flashed the ROm and everything seems to be like it should. I wonder why the differnece from Rom Mgr? It's not like I downloaded the file through RM, And It flashed using CWM? Oh well, I will know from now on to flash manually. I don't have the paid version, but if you can't fully flash a rom then what's the point of having/paying for Rom Mgr?
MomentFreak said:
Yeah I downloaded from the forum then installed using ROM manager. I will re-install using CWR. I will post my results. Thanks for the quick response. Oh yeah I noticed my post was at like 1:34 am? It's only 8:47 where im at?
So I re-flashed the ROm and everything seems to be like it should. I wonder why the differnece from Rom Mgr? It's not like I downloaded the file through RM, And It flashed using CWM? Oh well, I will know from now on to flash manually. I don't have the paid version, but if you can't fully flash a rom then what's the point of having/paying for Rom Mgr?
Click to expand...
Click to collapse
Sometimes it works, sometimes it doesn't. Full blown roms I will always try to do in CWR from now on. If its something small like a theme or extra or add on, Rom Manager usually works well.
Glad the reflash worked well thru CWR.
New here , just wanted to ask under this post.
Kind of the same topic.
I came from the dx used droidx bootstrap and dx2 bootstrap.
New the the TB I seen some post saying Rom manager.
So I installed Bamf 1.6 and 1.6.3 remix from Rom manager.
But I hit the flash Rom manager button, success.
Then hit boot into recovery.
Is that what you guys mean when you type. CWR.
Checking to make sure I am doing it correct.
Thank you
tanium said:
New here , just wanted to ask under this post.
Kind of the same topic.
I came from the dx used droidx bootstrap and dx2 bootstrap.
New the the TB I seen some post saying Rom manager.
So I installed Bamf 1.6 and 1.6.3 remix from Rom manager.
But I hit the flash Rom manager button, success.
Then hit boot into recovery.
Is that what you guys mean when you type. CWR.
Checking to make sure I am doing it correct.
Thank you
Click to expand...
Click to collapse
Well you need Rom Manager to Install CWR which stands for ClockworkMod Recovery, Which is where you can make what they call Nandroid backups, which is a backup of your current system and setup including apps and data. So it's always good do backup before making any changes ex, flashing rom's. But there are many things you can do with it and to me is one of the most important parts of having a rooted phone is having recovery. Hope this clears some stuff up.
Yes thank you.
But this is all done from inside Rom manager correct.
I mean I open Rom manager and clicked boot into recovery.
This is how I flashed Bamf 1.6 remix.
I installed no other program or app to get recovery.
Yes I see now , went and looked.
I was following instructions before.
I had to hit flash clockworkrecovery.
That is what installed that I guess.
See learning all the time.
I used droidx bootstrap before never new Rom manager was so cool.
That guy rocks.
I also had this problem. Installing from Rom manager doesn't seem to be enough. You seem to need to boot into recovery and install it manually from cwr.
Sent from my Verizon Wireless 4G LTE Thunderbolt
Definitely noticed that things can come up missing unless you wipe all three Data/Davlik/Cache and use clockwork to do it all. For some reason just flashing and wiping using ROM manager doesnt cut it.
Related
Hi everyone.
I'm pretty new to android, but I'm quite good at following instructions. Basically I've tried doing a nandroid backup with ROM Manager and everytime it reboots to make a backup it goes to a black screen with a phone in the middle of the screen with a red warning sign next to it. I've always tried booting into recovery and I get the same result. I first found this out while trying to follow the instructions for replacing the status and battery icons. Has anyone else had this issue?
I'm using ROM Manager v3.0.0.1 on a stock HTC MySense ROM from TMO running Android v2.2.1.
Thanks in advance for anyone that knows what I'm apparently doing wrong.
when you opened ROM Manager did you select "Flash ClockworkMod Recovery"? if not try that, it's the only time mine has what your's is doing. I got a little excited to flash Iced-Glacier when I first got the phone and accidentally skipped that step and had same issue
Yeah I first clicked on Flash ClockworkMod Recovery and it currently says Current Recovery: ClockworkMod 2.5.1.2. I just redid the flash and tried to boot into recovery mode and I'm still getting that error picture upon reboot.
Is there a setting on the phone somewhere that would cause this?
I am not positive 100% but I think I know what you mean; and I had it once due to very low battery charge. See if it is the problem or not.
infraled said:
Yeah I first clicked on Flash ClockworkMod Recovery and it currently says Current Recovery: ClockworkMod 2.5.1.2. I just redid the flash and tried to boot into recovery mode and I'm still getting that error picture upon reboot.
Is there a setting on the phone somewhere that would cause this?
Click to expand...
Click to collapse
The phone with the triangle is the stock recovery image. Others have had to try flash the ClockworkMod Recovery several times. You may need to as well.
this is what i did, not sure if your doing the same thing or not. i clicked on Flash ClockworkMod Recovery, MY4G came up and i clicked that and then clicked on backup current rom.
Alright so I've tried it with a full battery and I had the same result. I also tried reflashing several times with the current version and rebooting. I even tried to load some of the older versions of clockwork through ROM Manager and everytime I tried it spits out an error. I don't understand how I could be having such a hard time with something everyone seems to be able to do effortlessly.
Sent from my HTC Glacier using XDA App
R u sure u r rooted with S-off? If u r then u may have to flash recovery from ADB. Some people have not been able to get recovery to stick through ROM manager. There is a thread in the development section that explains how to do this.
Sent from my HTC Glacier using XDA App
Really? I have not heard that...I'll have to check up on that. It seems that this problem would be more common, but I guess not as I have had little luck in finding information on my own about this problem.
Just in case anyone is following this thread with the same problem as me, this is the post that the previous poster was referring to:
http://forum.xda-developers.com/showthread.php?t=852905&highlight=recovery
UPDATE:
Ok I figured out what was wrong. Apparently although I had root access on my phone and able to run things like Titanium Pro and Adfree and others with root privileges it wasn't good enough.
I followed the instructions here on how to permaroot your phone by pushing gfree to it. Once I did that I attempted to manually flash clockworkmod, which I ended up running into other issues. On a lark I tried installing clockworkmod through ROM Manager after permarooting and it finally installed it properly!
I love doing stuff like this, thanks to everyone for their input as it guided me to finally solving this. I'm off to do a nandroid backup now.
krypto16 said:
R u sure u r rooted with S-off? If u r then u may have to flash recovery from ADB. Some people have not been able to get recovery to stick through ROM manager. There is a thread in the development section that explains how to do this.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I have NEVER been able to flash Recovery with ROM manager. It says it does it but corrupts if everytime! Note: There has been some recent updates to ROM Manager and I haven't tried lately.
krypto16 said:
R u sure u r rooted with S-off? If u r then u may have to flash recovery from ADB. Some people have not been able to get recovery to stick through ROM manager. There is a thread in the development section that explains how to do this.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
IIRC the security protocol doesn't have to be off to flash clockwork ROM you do have to be rooted, VISONary.apk of course. I've turned my S=on just to make sure and it [clockworkROM] works pretty flawlessly.
Hey hey, it's great to see infraled out here! I am rooted/S=Off via the first VISIONary thread that was posted...
http://forum.xda-developers.com/showthread.php?t=834225
I installed Clockwork, flashed Clockwork Recovery and was expecting to have to do it twice, as outlined in this thread...
http://forum.xda-developers.com/showthread.php?t=858021
It only took one shot for me and it worked perfectly. The very first try, I powered off, powered on w/ vol down, went into Recovery and wham, there was Clockwork in its green glory. I figured I was just lucky and that once I rebooted, it would be lost and I'd have to flash again. Not so. Did a backup right away, worked flawlessly.
Looking forward to Iced Glacier, eVil and Cyanogen over the holiday break...
shlongwoodian said:
Looking forward to Iced Glacier, eVil and Cyanogen over the holiday break...
Click to expand...
Click to collapse
Cyanogen Gets my vote... But i've always loved T/DB's ROMS.
Recently rooted My new MyTouch 4G, downloaded the paid version of rom manager. I didn't understand why there are none of the current roms like the iced glacier, roms made by evil and several others listed as possible roms for flashing. The only roms are the cyanogenmod nightly builds. The cyanogenmod 6.1.2 RC2 isn't listed either. Do I need to do anything to get those listed or is that just the way it is???
Thank you,
Vinny
Birgertime has done a great job getting EDT ROMs available via Rom Manager (I may have bugged him a couple of times). I was a bit shocked when I was reading the thread and saw people were having issues when they updated using Rom Manager. I think the consensus was that Rom Manager was not properly wiping.
This is what I did:
I was on Trigger 2.9.3 *I try every ROM and I just felt like being old school.
I opened Rom Manager and downloaded the latest Trigger 3.2,
I used the KB1 Modem, KB5 kernel, I selected a few of the apps I wanted (bloater, titanium, maybe a couple others)
I told Rom Manger to wipe and do a backup by clicking the two boxes.
Once the download was completed I proceeded.
It went into CWR and it did a backup... immediately it did a wipe (it showed the steps in CWR like normal)... and then it flashed the ROM and it rebooted perfectly. I have had NO issues with the ROM. It's perfect in my opinion.
What I want to know, for those who had issues... what was different?
Did you get rebooted into the red voodoo recovery (I was at the normal CWR)? I don't understand how it can work perfectly for me, and not others. I would like to know exactly what went wrong so we can go to @koush and try and get both Rom Manager and Clockwork Recovery working better for us.
Between this, Fix Permissions, Partitions F'ing people, stats not working (for the dev's) I think our phone needs this amazing app to be better, and I know koush can do it.
** If there are other things wrong with Rom Manager/CWR, please post... it would be nice to have a list of things to work on.
I can put up a test version on rom manager. The current Trigger 3.2 up there will wipe regardless of what you tell ROM manager.
PS: who rated it 1 star?
birgertime said:
PS: who rated it 1 star?
Click to expand...
Click to collapse
Team Whiskey
EDIT, were you going to fix the prop so it showed 3.2, not 3.1? =)
Im confused. You said you used CWR to wipe and flash the ROM. What exactly did you use ROM Manager for?
s15274n said:
Team Whiskey
EDIT, were you going to fix the prop so it showed 3.2, not 3.1? =)
Click to expand...
Click to collapse
I think I did when I uploaded the vvm fixed version
androidmonkey said:
Im confused. You said you used CWR to wipe and flash the ROM. What exactly did you use ROM Manager for?
Click to expand...
Click to collapse
To download it
Sent from my SGH-T959 using XDA App
duboi97 said:
To download it
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Ah, ok. I dont see why downloading it with RomManager would make a difference, unless its not completely downloading. The safest is like birgertime says in the Trigger thread, download on PC and check Hash.
androidmonkey said:
Ah, ok. I dont see why downloading it with RomManager would make a difference, unless its not completely downloading. The safest is like birgertime says in the Trigger thread, download on PC and check Hash.
Click to expand...
Click to collapse
Rom Manager is the most convenient way to do this. it also checks the MD5 before it flashes the ROM. Trust me when I say I know the process...
I just want to know from those who had issues with using Rom Manager to download/wipe/flash, what went wrong?
I flashed it using Rom manager.
I chose KB5 modem and KB5 Kernel.
along with things like Bloater and swype.
it rebooted into red recovery and seemed to go fine from there.
when it first booted up it seemed ok at first, I let it sit for a while like usual.
and then rom manager force closed.
from there it was just force close after force close.
So I rebooted back into recovery and wiped data and dalvik.
then I rebooted.
and everything works just fine, with the exception of it never installed any of the extras I chose (swype,Bloater, etc...)
but I had those in titanium backup just in case anyways so it wasn't a big deal.
Its been running beautifully ever since.
Pretty much same thing happened to me, it went to red recovery and seemed to flash just fine. then when it rebooted i kept getting force closes everywhere. rebooted to clear cahce, dalvik, and fix permissions and has been fine ever since. it didnt wipe my apps which i found a bit odd
Alright, so as I expected... it sounds like it was
THE RED VOODOO RECOVERY AS THE PROBLEM.
Anyone able to prove that wrong?
I mean, it makes sense, it's not the recovery Rom Manager expects to see.
So, how do we fix it? This would not be koush now, I do not think.
Where did the red voodoo recovery initiate? I remember it just showed up one day. was it supercurio?
I don't know if you guys are aware of this but evertime I flash something its been with Rom manager. I got very sick of killing WiFi so I started all over again with BAMF beta 5 and flashed the few fixes and a new kernel. Same as I always did but this time I only used recovery and it worked. Haven't killed WiFi at all. Tried a bunch of times and still good to go. Also this only applies to GINGERBREAD ROMS!
Sent from a cellular telephone
You mean flash in recovery?
I had a similar experience but I think it was a coincidence.
Sent from my ADR6400L using XDA App
You should always flash through recovery... ROM manager likes to break things. Glad you got it working though.
yeah. Flash in recovery.. and I don't think its a coincidence. But who knows. Been working great this way
Sent from a cellular telephone
bking_soda said:
You should always flash through recovery... ROM manager likes to break things. Glad you got it working though.
Click to expand...
Click to collapse
Yeah. Ha. I guess so. I'm never using Rom manager again. Lol
Sent from a cellular telephone
I usually flash in recovery because my old OG Droid didn't like rebooting into recovery from ROM Manager. My T-bolt doesn't seem to have that issue and any time I have used Rom Manager to flash several zips at once, usually multiple patches or whatnot, I haven't had any issues. I have yet to flash an entire ROM in ROM Manager though.
So are you saying that ROM Manager is good for nothing but flashing the recovery image and getting CM7 Nightlies when they come out?
I knew I shouldn't have paid for it!
I flashed the bamf2 beta 5 update with ROM manager and my WiFi got messed up. I read this thread, rebooted into recovery, wiped cache and reflashed bamf2 beta 5. Wifi now works
Sent from my ADR6400L using XDA App
Uh ok lol
Sent from my ADR6400L using XDA Premium App
So has anyone let Koush know so he could look into this issue?
rom manager = junk for gingerbread roms i guess. it was amazing on froyo though, maybe they will update
RM updated to 4.2.2.0
CWR updated to 3.1.0.1
Had the same problem with flashing from rom manager. I do not use it anymore
ROM Manager
I was addicted to ROM Manager on my D1, even with Gingerbread ROMS (CM7). I haven't really used it for ROM installation on the Thunderbolt though. I paid for it on the Android Market and have absolutely no regrets, and as the ROMS mature for the Thunderbolt, so will the means for installing them.
Flash away I say.
Used it to flash BAMF 1.6.3 Remix, worked great.
i used it for das bamf 1.6.3 remix and had issues through rom manager. When i flashed through recovery everything went smoothe as butter. This time things were debloated.
tegan_ca said:
Used it to flash BAMF 1.6.3 Remix, worked great.
Click to expand...
Click to collapse
I had problems using it to flash remix, had to use recovery to get it to work correctly. It seemed like it wasn't fully wiping the cache/data before the flash, whereas recovery did.
Newb here, is it possible to download through RM but not trigger the auto-flash-sequence? Every time I d/l something through RM it tries to flash immediately after downloading.
tegan_ca said:
Used it to flash BAMF 1.6.3 Remix, worked great.
Click to expand...
Click to collapse
I had problems using it to flash remix, had to use recovery to get it to work correctly. It seemed like it wasn't fully wiping the cache/data before the flash, whereas recovery did.
My D1 never did like RM or CWM. And its nands were huge. I haven't rooted my Bolt yet... need to get around to that, I desperately miss Titanium and Root Explorer.
I'm running UnNamed 1.3.0 right now with no themes applied but I have everything setup the way I like it. I'd like to do a full 1.3.1 flash and try the Blue Monkey theme.
Is the best way to do this
A) backup apps with Titanium, backup with CWM, full wipe, flash 1.3.1 full, then flash blue monkey, restore apps with Titanium
B) backup with CWM, flash 1.3.1 over 1.3, then flash blue monkey theme
C) other
I'm unclear on whether I need to do a wipe going from 1.3 to 1.3.1 if it's a full flash and not the 1.3to1.3.1 update.
Thanks in advance for any help.
dont need to wipe. just flash it.
You can wipe cache and dalvik to clean up, but you don't need to wipe.
Alright, I did a backup then installed 1.3.1 and rebooted. Everything works fine and the phone looks exactly how I left it except in the about phone area it says I'm running 1.3.1 now.
Rebooted and backed up again.
Installed from zip the Blue Monkey theme and rebooted. I'm running Go Launcher Ex so I went in and cleared it as the default. Pressed the home button and chose TwLauncher. Everything looks fine but I'm not seeing the theme applied. I still have the same background live wallpaper and icons. The lock screen is still WidgetLocker.
Thoughts?
EDIT:
Apparently installing the theme a second time did the trick. I now see the new icons.
Knips178 said:
EDIT:
Apparently installing the theme a second time did the trick. I now see the new icons.
Click to expand...
Click to collapse
Right on. That's good advice for everyone. Sometimes things need more than one flash.
Sent from my páhhōniē
I had the same thing happen with that theme on 1.3.1. I knew something was up when it flashed really fast. A second flash took longer and worked properly.
Sent from my SAMSUNG-SGH-I777 using xda premium
Can anyone give a quick reply as to why that happens with flashing? Is it a problem with CWM, the zip files, or the process?
Knips178 said:
Can anyone give a quick reply as to why that happens with flashing? Is it a problem with CWM, the zip files, or the process?
Click to expand...
Click to collapse
Lol, I think alot of us wish we knew why. I don't think anyone has figured it out. It's not limited to our phone.
Sent from my páhhōniē
gr8hairy1 said:
Lol, I think alot of us wish we knew why. I don't think anyone has figured it out. It's not limited to our phone.
Sent from my páhhōniē
Click to expand...
Click to collapse
I think I have posted this twice today and the third time might...be the charm. You guys have to remember to check and mount your system and data in recovery before flashing ROM's or Themes. It should alleviate any re-flashing or multi-flash scenarios for you guys.
Additional: Also if some of you guys are having a bad or fast install you might want to re-download the Theme. I know in talking with Jivy26 (Blue Monkey Themer) the initial release of the update of 1.3 (For you quick and early adopters) had an issue and was pulled, repacked and posted again. Try a fresh copy.
hkeyman said:
I think I have posted this twice today and the third time might...be the charm. You guys have to remember to check and mount your system and data in recovery before flashing ROM's or Themes. It should alleviate any re-flashing or multi-flash scenarios for you guys.
Click to expand...
Click to collapse
Very true. But it's still only a 'should' not have to flash twice, not a certainty that it won't need the flash again.
It doesn't explain the times we do that and it still needs a reflash (usually cm7).
Sent from my páhhōniē
gr8hairy1 said:
Very true. But it's still only a 'should' not have to flash twice, not a certainty that it won't need the flash again.
It doesn't explain the times we do that and it still needs a reflash (usually cm7).
Sent from my páhhōniē
Click to expand...
Click to collapse
I used to see the same thing with flashing multiple times, thought it might have been a bad root install or something wrong with the ROM itself. Ever since implementing the mentioned procedure into my regimen of updates. I only flash once (Unless of course there is in fact something wrong with the package).
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