Hello all, introduced myself the other day, I'm new to the Galaxy SII and have had it only a few short days. And already I've managed to screw it up! LoL. No really what I made this thread for is to let people who may have done the same thing I've done that there is a solution. Here's what I did. Download the VillainRom and the Hellraise MOD from the development section. I put them both on internal SD card, rebooted into clockwork mod recovery, and flashed Villlain ROM. After that, I was SUPPOSED to flash Hellraiser so it would be compatible with the I777 since it's an international version ROM. But I was talking to my son at the same time and FORGOT and let it reboot and boot up into VillainROM. I was at this point very worried, as I thought a bunch of errors would occur. But not a bunch did. However I knew this wasn't good and tried immediately to reboot into recovery, wipe, and redo the process PROPERLY. Except when I rebooted, it rebooted me into clockwork mod recovery 4.0 version. Now, at this point, none of the capacitive buttons or the power button would select anything. It just showed the Clockwork Mod logo when I clicked on anything to wipe, reboot, anything. SO, here's what I did to fix this mistake. I download the clockwork mod recovery .tar that is flashable with Odin (the one for I777), rebooted back into VillainRom, put the phone into Download mode, and flashed it. Then I let the phone reboot, and then rebooted a second time into what I HOPED would be the correct version of CWM. And thank God, it was. However, the capacitive buttons were STILL not working correctly. The answer? They DO work, however, they are out of order. Different buttons do different things but if you figure the order out you can wipe and flash back to a ROM for our device. I just wanted to post this, in case anyone else messed up like I did.
edit: It did not, however, change the Boot Logo from thinking I'm running the international version. That still says i9100
Phalanx7621 said:
Hello all, introduced myself the other day, I'm new to the Galaxy SII and have had it only a few short days. And already I've managed to screw it up! LoL. No really what I made this thread for is to let people who may have done the same thing I've done that there is a solution. Here's what I did. Download the VillainRom and the Hellraise MOD from the development section. I put them both on internal SD card, rebooted into clockwork mod recovery, and flashed Villlain ROM. After that, I was SUPPOSED to flash Hellraiser so it would be compatible with the I777 since it's an international version ROM. But I was talking to my son at the same time and FORGOT and let it reboot and boot up into VillainROM. I was at this point very worried, as I thought a bunch of errors would occur. But not a bunch did. However I knew this wasn't good and tried immediately to reboot into recovery, wipe, and redo the process PROPERLY. Except when I rebooted, it rebooted me into clockwork mod recovery 4.0 version. Now, at this point, none of the capacitive buttons or the power button would select anything. It just showed the Clockwork Mod logo when I clicked on anything to wipe, reboot, anything. SO, here's what I did to fix this mistake. I download the clockwork mod recovery .tar that is flashable with Odin (the one for I777), rebooted back into VillainRom, put the phone into Download mode, and flashed it. Then I let the phone reboot, and then rebooted a second time into what I HOPED would be the correct version of CWM. And thank God, it was. However, the capacitive buttons were STILL not working correctly. The answer? They DO work, however, they are out of order. Different buttons do different things but if you figure the order out you can wipe and flash back to a ROM for our device. I just wanted to post this, in case anyone else messed up like I did.
edit: It did not, however, change the Boot Logo from thinking I'm running the international version. That still says i9100
Click to expand...
Click to collapse
You could have just flashed the stock ROM though Odin. That would have fixed everything and given you a fresh start but that's up to others to decide.
Sent from my SGH-I777 using XDA App
You DID read the first post for codeworkx's CWM kernel for the button mappings, right?
IF you had CWM 5.x after flashing his tar, it did correctly flash.
Also, all you have to do now is just flash hellraiser - should be OK even after booting VR normally, although NFC might flake out... I haven't tested what happens if you flash hellraiser after /data is created
Entropy512 said:
You DID read the first post for codeworkx's CWM kernel for the button mappings, right?
IF you had CWM 5.x after flashing his tar, it did correctly flash.
Also, all you have to do now is just flash hellraiser - should be OK even after booting VR normally, although NFC might flake out... I haven't tested what happens if you flash hellraiser after /data is created
Click to expand...
Click to collapse
You DID receive my pm right? Yea I thought so...
Sent from my SGH-I777 using Tapatalk
No I didn't receive any pms ..
Have to check and see if somethings wrong on my end with tapatalk. Thanks for the tips if I ever do it again ill know what to do
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Related
Hey guys. I've been an Android & XDA user for a while now, so this question shouldn't be about a nooby-sitiuation.
My friend bought an AT&T Samsung Galaxy SII (SGH-i777) this week. I've been trying to flash CM7 ever since. I got the rooting done, the properly recovery (with no signature / "abort" problems)
The rom seems to keep bricking the phone. Its simply unflashable. I seen tons of people on XDA who got it to work, with barely any serious problems. I troubleshooted the problem myself, and its simply just the CM7 roms. I would do a full wipe, and then install the rom like I would on my other Android phones, and the installation is successful. When it boots, it gets stuck on the Galaxy SII boot screen (not the splash/boot animation screen) and it would stay on it with a yellow warning triangle on the bottom.
I tried flashing other roms, like Cognition X2, and they worked. Its just CM7 on this phone... which is odd because CM7 is usually stable (nightlies aside.) Especially since the 7.1 stable version was recently released. Anyone can help me get the rom up and going? Would be highly appreciated.
did you try to wipe dalvick cashe as well when you wiped data?
I just flashed it tonight myself and all I did was reboot into CWM and did a Wipe data/factory reset and then Wipe cache partition. After doing that, I simply flashed the cm7 zip file that was loaded on my internal sd. Rebooted and no problems.
I didn't have ANH ISSUES installing it but I know I read that some.people bad to flash it twice initially. So flash it, then when it goes back to the recovery screen flash it a second time. I also remember users on the international SGS2 bad to do the same thing. Most have no issues but I think they found that it depends on what you used to root your phone (on the SGS2 internationals) and I THINK some had to do the same here. Try it and if it works just hit the thanks button.
Sent from My KickAss CM7 Galaxy S2
if you flash it and get stuck in a bootloop, just pull the battery, and 3-finger back into recovery to flash the rom again.
keep doing this until you get it up and running - took me a few times, including a couple of battery pulls.
How do you boot into recovery? I know On the SGH-i777 you have to hold the Vol down+back+power to get to the Download mode, but I tried everything to get to the recovery itself.
Boobie Watcher said:
did you try to wipe dalvick cashe as well when you wiped data?
Click to expand...
Click to collapse
Yes. I've flashed many roms before, this seems to be the only one I had ever seen a problem with.
mfpearson said:
if you flash it and get stuck in a bootloop, just pull the battery, and 3-finger back into recovery to flash the rom again.
keep doing this until you get it up and running - took me a few times, including a couple of battery pulls.
Click to expand...
Click to collapse
Word.
Edit: To boot into recovery vol up+vol down+power
Had the same problem. Read somewhere to install the ROM twice in a row in CWM without rebooting inbetween. Worked like a charm.
Thanks for the feedback guys. I'll try this in the morning once I get my hands on the phone again.
Saw this type of behaviour on occasion with cm7 on my aria. Sometimes caused by a bad download of the rom. Did you verify md5s ?
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Don't forget to do a master data clear /reset before trying to boot the new CM7 rom for the first time - clear out the old stuff. Works perfectly here.
Sent from my SGH-I777 using xda premium
I'm having the same issue. I'm getting signature errors when trying to flashCM7.1 stable. I've downloaded it two times now with the same problem. My question is, I'm trying to flash from on the phone itself, storing the zip in the download dir on the phone as I don't have an sd card. Will this even work? I've tried looking around and all I can find is flashing from an sd card. I can get one, I just haven't yet.
squigge said:
I'm having the same issue. I'm getting signature errors when trying to flashCM7.1 stable. I've downloaded it two times now with the same problem. My question is, I'm trying to flash from on the phone itself, storing the zip in the download dir on the phone as I don't have an sd card. Will this even work? I've tried looking around and all I can find is flashing from an sd card. I can get one, I just haven't yet.
Click to expand...
Click to collapse
That's the way I did it. Put the update in the same folder on the internal SD card. I can't even access my external SD card from CWM.
Sent from my SGH-I777 using xda premium
Hmm, I'm not sure what I'm doing wrong then. I did a factory reset, and wiped the cache and get the same thing. I know it wiped because now I have nothing setup on the phone when I boot normally. Suggestions?
Quit downloading the CM7 builds for the International Galaxy S II. They will NOT work. That is why it fails. Look for the Galaxys2ATT build.
Sent from my SGH-I777 using xda premium
I got the build by going to the cm7 website, looking by device, finding the galaxy s 2 and grabbing the stable one. So perhaps that is the incorrect one and I'll look closer for one that has att in it, whenever the site isn't going up and down. They seem to be having issues today.
Make sure you're installing the version located in this thread...
http://forum.xda-developers.com/showthread.php?t=1297568
Specifically this link
Double flash made it work. Thanks guys. + thanks for telling me how to boot into recovery lol. Great rom.
Sorry for the newb issues, it was the wrong version. I got the att version from the thread previously mentioned and that worked perfectly. Thanks!
Hey guys.
Using Samsung Galaxy S Froyo 2.2.1 I9000
Was installing CM7 today through CWM in Recovery Mode, at first it wouldn't work, threw me an error about signature verification, found it was because of 3e verification on zip files, so flashed the kernel with Odin to 2e.
After installing the kernel, ran the CM7 again and it ran fine, followed the instructions, wiped before installing CM7. The install looked like it ran fine, phone rebooted no problem, but it came back to a wiped Froyo still, didn't load CyanogenMod at all.
Anyway, there's no GMail app, and only Market, and Market wont let me add a Google account even if I say yes to the prompt. Looked round the SGS forums, didn't see anything like this.
I'm guessing I did something wrong, help someone?
Belahzur said:
it came back to a wiped Froyo still, didn't load CyanogenMod at all.
Click to expand...
Click to collapse
What do you mean by this?
Theonew said:
What do you mean by this?
Click to expand...
Click to collapse
I can only describe it as once I got to the step of rebooting the phone, it didn't load CyanogenMod, I was expecting the CM animation but I got my normal Froyo screen, does that make sense?
Probably a bad download. Delete the download and do it again. But just a word of advice...ROM's come with kernels, so if you flash a kernel first and then a ROM, you are going to lose the first one you flashed.
Thanks lowandbehold, one problem though.
I wiped the phone following the instructions, so I don't have ROM Manager anymore and can't open the Market, it asks me if I want to sign in with a Google account, I hit yes and nothing happens.
Ideas?
Sorry for double post, looks like I made some progress possibly.
Got the CM7 animation on boot, but doesn't go any further.
Got Clockworkmod recovery up though, flashed speedmod kernel, and CM7 initial kernel through ODIN.
Now in recovery mode when I go to install "update-cm-7.1.0-GalaxyS-signed.zip" I get an error about assert failed, error in the zip, status 7 and aborts.
Did you make a nandroid backup of the stock ROM before you flashed? If so, try to revert back to that. If you didnt make a backup, do a full wipe...wipe data/factory reset, wipe cache, and go into advanced and wipe the davlik cache. Then go to install zip from SD Card and select the CM7 zip. You should also check the md5 sum of the zip file to see if it matches up to make sure the download was good. You will be able to figure something out, as long as you can get into recovery and not getting crazy cache errors your phone should be 100% recoverable. Maybe even try something that is not CM7...just keep at it.
---------- Post added at 12:13 PM ---------- Previous post was at 12:11 PM ----------
Also, standby on the kernel for now. Get CM7 up and running on the kernel it provides you with and then make a backup in CWM. Then you can try to change the kernel...if you have issues then you can just go to your CM7 backup.
Would the backup be a recovery-update.zip file in the \clockwordmod folder?
Belahzur said:
Would the backup be a recovery-update.zip file in the \clockwordmod folder?
Click to expand...
Click to collapse
No, it's in recovery/backup on the clockword recovery screen.. personally, I like Amon Recovery a lot better than CM. Clockwork doesn't wipe the cache as well good luck! Hope you get it working
Sent from my Evo 4G using Tapatalk.
kendallc123 said:
Clockwork doesn't wipe the cache as well
Click to expand...
Click to collapse
Fixed your spelling (bold). Anyways, do you have proof of this?
Theonew said:
Fixed your spelling (bold). Anyways, do you have proof of this?
Click to expand...
Click to collapse
Thanks haha, went back and fixed it too. I don't have solid facts about it, but I have read in multiple threads that
1) People love Clockwork
2) People say Clockwork doesn't wipe the Dalvik cache thoroughly and sometimes causes boot loops (I've never had one)
I have had some problems with Clockwork personally. But, this is just my opinion. Also, Clockwork doesn't recognize some zips that I try to flash while Amon does. Anyway, it's all your opinion, whatever feels better to you.
gtab wifi, stock tw3.2., cwm 5.8.3.1
i've tried flashing several roms using cwm and through rom manager. every time i get stuck on the the samsung screen after reboot, which takes about 30 seconds after initiating flash. i've never had a problem installing anything on my phones or my nook color. it's been nothing but a paper weight for the last year and it's going to the landfill if i can't figure it out soon.
Did you try to wipe data/factory reset/ wip cachd and wipe dalvik?
all of it. follow directions for each rom exactly. i always end up in the same spot
burnitdown said:
all of it. follow directions for each rom exactly. i always end up in the same spot
Click to expand...
Click to collapse
How much you wait? After I flashed the Galaxy Task 14 room earlier this day it took several minutes to load.
Certain ROMS require an older version of CWM, such as CM9. If that is the latest version you have installed it may not work. Maybe try using ODIN to flash the recommended version (you can easily find that in the CM9 Nightly threads or simply by searching around)?
bar_rodoy
Click to expand...
Click to collapse
i let it sit long enough.
this_is_nick6
Click to expand...
Click to collapse
i'm using the most up to date cwm. right now i'm trying to flash aokp m4
burnitdown said:
gtab wifi, stock tw3.2., cwm 5.8.3.1
i've tried flashing several roms using cwm and through rom manager. every time i get stuck on the the samsung screen after reboot, which takes about 30 seconds after initiating flash. i've never had a problem installing anything on my phones or my nook color. it's been nothing but a paper weight for the last year and it's going to the landfill if i can't figure it out soon.
Click to expand...
Click to collapse
Can you link us to the CWM 5.8.3.1 recovery your using???
As far as I know this is the latest version of CWM http://droidbasement.com/db-blog/?p=2655 as of 6/30 and it's only 5.5.0.4.
As far as Googling is telling me...
1. It may be a touch recovery?
2. I couldn't find a many search returns that mentioned it being for Tab10.1s
3. The search returns I did find that mentioned Galaxy Tabs were in languages I don't read.
Just curious don't ya know...
Sent From My Galaxy10.1 Class Starship....
Questions go in the Q&A section
my recovery is listed on the cwm site under rom manager. it's not touch
now i'm curious as to what version everyone else is using
okay. so i flashed 5.5.0.4 through odin then flashed aokp m4 plus gapps. all seemed to go well until boot time. i've been sitting at the samsung screen for a full 20 minutes now. i suppose my next course of action would be to revert to stock via odin and start the process over? i'd really like to use this thing but absolutely can't stand tw
you may have gotten a corrupt partition somewhere. I'd odin back to stock and start fresh. fwiw, I wouldn't trust ROM Manager for the latest recovery, it doesn't always have the correct file for your device. For example, for may particular phone Rom Manager had never worked properly and soft-bricks the phone every time.
Always check here on XDA for the proper recovery files for this device first.
that's all i needed to hear. now, can anyone point me in the direction of the file i need? my searches all point to S0ckM0nk3y's link which results in a 404 error
disregard my last post. i flashed sam's ics via odin. i'll play with it and try to like it. thank you sir
huh. still can't flash a custom rom...
Well, I don't know what I did but i was able to get MapleSyrup's CM10 preview to run. I'm happy for now
Are you doing a factory reset and wiping the cache in CWM before you flash? I always do that and then use titanium backup to restore my apps.
Also, what version of recovery are you using? I'm on CWM 5.5.0.4 which I've used to flash a couple of different roms, including the latest stock ICS from Toldo I think.
you can get it here and use ODIN to flash. Just make sure you download the correct version for your device:
http://droidbasement.com/db-blog/?p=2668
i had the same problem. i flash stock ics rom for my 7510. at first it looks fine until i try to reboot my tab. it starts to hang at the bootscreen. i try to reflash the rom via recovery but fail. try to install nandroid backup and also fail. the last resort is to do clean flash from odin. this thing happened 5 times in 3 days. one time after i install all the apps and try to restart my tab then it happened again, stuck at bootcscreen.
Hello all, I want to install Clockworkmod on my Samsung Vibrant T959 so I can install a custom ICS ROM. I ran into some problems along the way. I can not seem to install CWM correctly. I had the phone under Froyo 2.2, kernel version 2.6.32.9, and build number froyo.uvkb5. After flashing the recovery by ROM Manager, I would still be stuck at the stock recovery. I have the correct files to download:update.zip. After clicking on "reinstall packages", the recovery said "replacing stock recovery with Clockworkmod recovery". The problem is that after that message, the phone restarts into the stock recovery. I tried it 4 times in a row, but I'm still stuck at the stock recovery. The system keeps saying that it will replace the stock recovery with the CWM recovery, but that did not happen with me. I would keep getting the same message when I click on "re install package". What am I missing that does not allow me to do this? Thanks all.
Are you on 2.1 eclair or 2.2 froyo?
I'm pretty sure you need to be on 2.1 but don't quote me.
Also, I believe there is an issue with the newer versions of ROM manager, recovery mismatch. (Again don't quote)
I haven't had to mess with that stuff in a long time. Either way I'm posting a link that will help you along. If you have any more questions just shoot.
http://forum.xda-developers.com/showthread.php?p=9375927
Paranoid, sitting in a deep sweat...
Thanks for the reply. Like I said in my last post, I am running at Froyo 2.2. I already bricked my phone for failing to downgrade to 2.1. I already rooted my phone, my problem is that I could not install CWM correctly by the stock rom. After the message states that it is replacing the stock rom, my phone goes back to stock with no changes.
woodrube has some great guides, I use the update.zip method, rom manager didnt like my phone, post if you still have problems and Ill give you more accurate directions on guides.This is probably heresy, but i never could get rom manager, even pro to do what I wanted,and Im sure it was me.
Your positive you dont have a 4g?
Sugartibbs said:
woodrube has some great guides, I use the update.zip method, rom manager didnt like my phone, post if you still have problems and Ill give you more accurate directions on guides.This is probably heresy, but i never could get rom manager, even pro to do what I wanted,and Im sure it was me.
Click to expand...
Click to collapse
You do not understand, I am having the problem that CWM could not install properly. When I chose "install packages" the steps went by and ended with "Replacing stock recovery with CWM recovery". Usually, that would jump straight into CWM recovery after it's installed. That did not happen to me, After installation, my phone restarted and booted back into stock recovery. I tried installing again but I always go back to stock recovery and not Clockworkmod recovery as I planned.
Ive never seen that error message, I know its frustrating, but the t959v 4g comes loaded with Froyo 2.2,the a 2.1 eclair odin will brick it.Just trying to help.
Go back to 2.1, uninstall ROM manager, use the update zip in the guide link I posted.
Paranoid, sitting in a deep sweat...
---------- Post added at 11:06 PM ---------- Previous post was at 10:44 PM ----------
In the link I sent is the AIO toolbox download. There is a guide how to use it in this link. The DL links are dead in this one so get from previous.
Paranoid, sitting in a deep sweat...
IIRC the update.zip method does not work in Stock 2.2 because of the 2e and 3e recovery mismatch. If you to go to 2.1 Eclair, then you can use the update.zip method and then flash your ROM of choice after that. If you decide to stay on 2.2, you'll have to get the 3e method. It is in the Development section, so you'll just have to search 3e and it should come right up.
All this is provided you have a T959 (3g) and not a T959v (4g). Sorry but lately there have been many 4g users flashing our ROMs and then freaking out.
You can also find a bunch of files in my Repo thread stickied in the Dev section.
samsgun357 said:
Go back to 2.1, uninstall ROM manager, use the update zip in the guide link I posted.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Maybe you'll get it now.
Good luck.
@Woody, thanks buddy.
I linked your repo thread in my previous post.
Edit: well the link isn't in my posts, must not have sent??? But here it is
http://forum.xda-developers.com/showthread.php?p=31279153
Paranoid, sitting in a deep sweat...
Click to expand...
Click to collapse
The first thing you need to do after obtaining root is flash a kernel. You can't install a rom from re-install packages. That has to be done in a custom recovery, which is built into the kernel. Easiest way to do that is download a kernel and flash it with sgs kernel flasher. I would suggest immortality kernel. After that you can go into the custom recovery and flash your rom of choice.
nfkod said:
The first thing you need to do after obtaining root is flash a kernel. You can't install a rom from re-install packages. That has to be done in a custom recovery, which is built into the kernel. Easiest way to do that is download a kernel and flash it with sgs kernel flasher. I would suggest immortality kernel. After that you can go into the custom recovery and flash your rom of choice.
Click to expand...
Click to collapse
^^ this is not true.
I had a issues with my apps doing the same thing. I had to get busy box and install a older ver 19.2. It corrected the issue. Updating superuser caused my headache
Sent from my SGH-T959 using xda premium
naturallight said:
I had a issues with my apps doing the same thing. I had to get busy box and install a older ver 19.2. It corrected the issue. Updating superuser caused my headache
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
I have no idea what you are talking about?????
Paranoid, sitting in a deep sweat...
If you have the proper xda version of update zip on your sd...,, theres no need for a kernel flash.
I have the same exact issue as the original poster. 2.2 froyo and all. I even replaced my stock 3e recovery with the modded one, but I get the same issue. Says its flashing CW recovery but it always reboots and comes back with the stock recovery. What exactly are we doing wrong?
Follow steps in this guide, update.zip b is probably best but you need to Odin back to stock first.
http://forum.xda-developers.com/showthread.php?p=9375927
Alright so I managed to get CWM on my 2.2 Stock Vibrant and even got it permanently. What I did was download SGS Kernel Flasher and install it. Then I went the Samsung Vibrant Kernel Bible and found the stock kernel with Voodoo lagfix included that matched my phone (because the kernel has CWM built in) downloaded it, and placed it on the root of my card. Launched the app, backed up my current kernel and then flashed the new one. Everything went smooth and then my phone rebooted and was stuck on the Vibrant screen for 20 minutes. I was pretty sure I messed my phone up. Also it was talking to me which I didn't realize at first, because I was expecting my phone to be talking to me! Finally made out what it said and it said something along the lines of not enough space on the partition, closing... It was hard to understand because it was in a robotic voice. It eventually rebooted and loaded up like normal. Checked the about phone but saw nothing different. So I decided to reboot to recovery just to check and sure enough, CWM 2.5.1.3 comes up, and comes up every time Finally, now to figure out what to do to get on a jellybean ROM
When I say Odin to stock that's 2.1 eclair. Voodoo lagfix will cause issues going to a JB ROM.
You don't need to try and re-invent the wheel.
Odin to stock 2.1 eclair JFD.
Put ROM on sdcard
Go to recovery, install update.zip from guide I linked.
Wipe and flash ROM.
It can't get much easier. I am not trying to come off as a ****, only to help you, and avoid future issues.
BTW, I saw your pm, I can't reply because it keeps crashing the app. If you go in and disable voodoo lagfix you should be able to flash PA without issue. It will take 3 flashes. You only need to wipe before the first flash. Wipe cache, dalvik cache, factory/data and format system in mounts and storage. If you get in a boot loop, pull battery then use button combo back to recovery. GB boots are not required.
samsgun357 said:
When I say Odin to stock that's 2.1 eclair. Voodoo lagfix will cause issues going to a JB ROM.
You don't need to try and re-invent the wheel.
Odin to stock 2.1 eclair JFD.
Put ROM on sdcard
Go to recovery, install update.zip from guide I linked.
Wipe and flash ROM.
It can't get much easier. I am not trying to come off as a ****, only to help you, and avoid future issues.
BTW, I saw your pm, I can't reply because it keeps crashing the app. If you go in and disable voodoo lagfix you should be able to flash PA without issue. It will take 3 flashes. You only need to wipe before the first flash. Wipe cache, dalvik cache, factory/data and format system in mounts and storage. If you get in a boot loop, pull battery then use button combo back to recovery. GB boots are not required.
Click to expand...
Click to collapse
QFT. Just yesterday I ran into the same problem as reported by the OP and a few others. I HAD to downgrade to 2.1 via JFD Odin. Then flash the update.zip. I then just downloaded ROM Manager to get CWM working. However, I did see in some instructions that sometimes even though you know you have CWM installed, it will still default to stock recover. I simply applied the update.zip again and it eventually fixed itself. Not sure what that was about, but I did see it in some instructions, and I experienced it as well.
nfkod said:
the first thing you need to do after obtaining root is flash a kernel. You can't install a rom from re-install packages. That has to be done in a custom recovery, which is built into the kernel. Easiest way to do that is download a kernel and flash it with sgs kernel flasher. I would suggest immortality kernel. After that you can go into the custom recovery and flash your rom of choice.
Click to expand...
Click to collapse
great help dude.i fixed finaly."""""thanks"""""
Hi there,
I tried to flash a new rom and it some how is stuck on the reboot screen.
Any help in what to do, would be great!
Thanks!
Pull the battery, put it back. Hold button combo to boot to recovery. Flash the ROM again but do not wipe. Reboot and you should be good.
FFR please list which ROM you are coming from and the ROM you are flashing.
Sent from my SCH-I535 using xda premium
Thanks, for your help!
I ended up taking out the battery, and then rebooting it, and it went to the Recovery mode.
I actually did wiped everything all over again, like you were doing it from the start originally, and it seemed to work fine.
I cant even remember what I was coming from, I had it on my Phone for almost two years, and it was old and the battery life was terrible.
I tried RemlCS-JB its not bad, but I think I am going to try another one. Any suggestions? I have been away from this forum for over a year, so anything recent with good battery life and good GPS is ideal.
The rom did not seem to come with an app downloader such as google play, or Clockwork manager.
Anyone know how to get into reboot recovery mode without clockworkmanager?
When I try to download clockworkmanager online it does not let me really download it.
When I try to install a new Auxura rom it states the following:
It says Installation aborted
Above that, it states please switch Edify scripting
Anyone know, if I have to do something else? I am just doing a normal Clockwork Flash.
I wiped the data/factory set, then tried to install the rom
molson24 said:
When I try to install a new Auxura rom it states the following:
It says Installation aborted
Above that, it states please switch Edify scripting
Anyone know, if I have to do something else? I am just doing a normal Clockwork Flash.
I wiped the data/factory set, then tried to install the rom
Click to expand...
Click to collapse
Did you Odin back to stock before trying to flash a ROM that is a previous version of android? It could cause a lot of problems if you don't Odin back to stock first!
Did you flash gapps on the ROM that you said was missing apps etc?
Gapps is a package of Google apps that devas can't include in the ROM.
I wouldn't use ROM manager, in most ROMs, there is an option to reboot to recovery in power menu. You can also power down and use button combo to boot to recovery.
I highly suggest reading through some of the dev threads for any ROMs you are interested in. It will answer most of your questions and prevent future issues.
Sent from my GT-P5113 using xda premium
Oh yeah, it said to flash GAPPS after, but I never did. Where do you get GAAPS?
No, I dont even have ODIN installed on my computer and all of those drivers, so It is something I do not want to do.
It has been 2 years since, I switched, so I randomly flashed to this new one, but I want to try a different one, but seems to get an error.
Ill try a few other roms to see if they work though.
molson24 said:
Oh yeah, it said to flash GAPPS after, but I never did. Where do you get GAAPS?
No, I dont even have ODIN installed on my computer and all of those drivers, so It is something I do not want to do.
It has been 2 years since, I switched, so I randomly flashed to this new one, but I want to try a different one, but seems to get an error.
Ill try a few other roms to see if they work though.
Click to expand...
Click to collapse
You can get the gapps from the op of the ROM thread or go to www.goo.im/gapps
As far as Odin etc
If you are on an ICS or JB ROM and want to go back to a froyo or GB ROM, you need to odin to stock first.
General rule of thumb, you can flash up but to flash down, Odin to stock first.
Sent from my SCH-I535 using xda premium