Related
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?
hey guys, im trying to flash the miui 1.6.24 rom onto my 2.2 fascinate. ive tried twice now and everytime i i try and flash, it starts the download for about 5 seconds, then just keeps rebooting the phone and says cant mount and does a countdown from 20 then reboots and repeats. i have had to odin back to stock 3 times already from this. any ideas why this is not working? and how can i get it to work? Thanks in advance
Have you read how to flsh to the cm7 & miui thread. Make sure you have the correct kernal, gapps and recovery. I think that is why you maybe getting stuck. Be sure to read how to get back to other roms if you choose to go back.
gotsflat4love said:
Have you read how to flsh to the cm7 & miui thread. Make sure you have the correct kernal, gapps and recovery. I think that is why you maybe getting stuck. Be sure to read how to get back to other roms if you choose to go back.
Click to expand...
Click to collapse
no i cant find that thread. the only one i can find is the how to go from cm7 or miui to another rom. but im trying to do the opposite
it just keeps saying "waiting for SD Card to mount" and counts down. then just keeps repeating
Can anybody help me?
I came from Nameless v4.1 and have a thread in Q and A that answers this but I'll tell ya how, it's basically the same steps since I odined back to stock.
Make sure that you have Andmer's latest miui build on the root of your SD card. Then assuming you already use the latest recovery (I had time's blue recovery) , wipe the big 3 (data, cache, delvik) > install from SD card > choose the miui rom > have a little patience > profit.
For me it did the count down 4 times before it actually mounted and finished the install. I don't know if the size of the SD card effects it in any way, concidering I'm only using a 4g, but it may take awhile. Again these are the steps I took and I haven't had any problems other than the one's already stated.
Sent from my miui fascinate using XDA Premium App
Yeah when it was doing the countdown I let it go before for about a half hour and it still list kept doing it and I had to Odin back to stock again. I didn't have the rom on the root of the SD card, I had it in a folder entitled root that I put all my roms on. I don't know if that would really make a difference
To be honest I'm not entirely sure. I've always put it on the root of the sd card. I guess at this point it wouldn't hurt to try. And again I'm not sure if the size of the card comes into play considering I'm using just a 4g card and not my stock 16g. Maybe someone else with more experience and overall know how can chime in to help. Sorry if I couldn't be of any help.
Sent from my miui fascinate using XDA Premium App
Maybe a bad d/l ?
I just switched to cm7 from miui then back and had no issues
Try redownloading
Sent from my MIUI Fascinate XDA App
Yeah I'm not using the stock card either. I'm using a 2gb Samsung and a 8gb sandisk. And I don't think its a bad download cuz I've tried doing it with all 3 versions of miui and it did it to all of them and the new cm7 and the cm7/miui kernel. I could get the old cm7 but when trying to flash the new one I get the countdown
I just tried again and let it do the countdown for a half hour so it tried about 40 times to mount the card. Any other suggestions?
I'm also needing a bit of advice on how to install MIUI on my Fascinate...
http://forum.xda-developers.com/showthread.php?t=1139400&highlight=AOSP+Gingerbread
Trying to install that. Downloaded the packages, but not sure what to do from there. I was going to load them into ODIN, but realized they aren't regular tar.gz packages...can I just load it with ROM Manager or what? I'm currently on 2.2.1, "Super Clean version 2.9 - EB01/EC16 Froyo leak root+Froyo Clockworkmodwith MALWARE protection".
Not to hijack, but seems we have similar questions.
You need to load in CWM, ROM manager is not compatible with the newer roms
MIUI 1.7.1 error 7
GuitarrassDeAmor said:
I'm also needing a bit of advice on how to install MIUI on my Fascinate...
http://forum.xda-developers.com/showthread.php?t=1139400&highlight=AOSP+Gingerbread
Trying to install that. Downloaded the packages, but not sure what to do from there. I was going to load them into ODIN, but realized they aren't regular tar.gz packages...can I just load it with ROM Manager or what? I'm currently on 2.2.1, "Super Clean version 2.9 - EB01/EC16 Froyo leak root+Froyo Clockworkmodwith MALWARE protection".
Not to hijack, but seems we have similar questions.
Click to expand...
Click to collapse
Yeah trying to load MIUI 1.7.1 also and keep getting the error 7. Do we have to do it through odin?! cleared data, cache and dalvik, still no go. Did putting it in root make a difference? why cant it just work like the other roms lol! Sorry for taking your Thread away kendall316!
Thanks in advance if anyone figures it out! if i do, will post it.
Hey, everyone. I've been having this problem a lot... when I was on CM7, about once a month everything would force close. First an app (xScope, Twicca, anything), then GApps, then my keyboard... the phone starts FCing everything within about an hour of being turned on. In the past, I've just fully wiped the phone... I'm on Pool Party now (the version before the newest one right now), and everything is FCing again. Is there a solution that isn't just "wipe everything?"
Did you make any drastic changes before it started force closing everything or has it been that way since you flashed the new ROM? Or was your ROM working fine in the past and it mystically started happening
Sent from my SCH-I500 using XDA App
This just mystically started today. It's been about a month and a half since the last time this happened, on CM7.
My phone got all screwed up one time when I installed either a bad gapps zip or the wrong one and I ended up having to wipe everything and start over to get out of that mess, although it's weird it randomly is happening to you.
I highly recommend the new ics roms
Sent from my SCH-I500 using XDA App
kadin.zimmerman said:
My phone got all screwed up one time when I installed either a bad gapps zip or the wrong one and I ended up having to wipe everything and start over to get out of that mess, although it's weird it randomly is happening to you.
I highly recommend the new ics roms
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
@OP... I installed TSM Pool Party, flashed gapps for CM7, [big mistake???] and then today everything FC. Couldn't load my browser, only ADWlauncher and perhaps a few other apps I tried worked.
I tried flashing the correct gapps, not sure if it fixed it, rebooting now. if not I will have to reflash tsm pool party.
@above poster, where is this new ICS fascinate rom? Is it stable?
GApps is GApps, man. Wondering if it's a sync issue...
mvmacd said:
@OP... I installed TSM Pool Party, flashed gapps for CM7, [big mistake???] and then today everything FC. Couldn't load my browser, only ADWlauncher and perhaps a few other apps I tried worked.
I tried flashing the correct gapps, not sure if it fixed it, rebooting now. if not I will have to reflash tsm pool party.
@above poster, where is this new ICS fascinate rom? Is it stable?
Click to expand...
Click to collapse
Yeah the ics ROM is very stable, I love it. Go to Google and type in "rootzwiki fascinate ics build 6" and you should find it on the rootzwiki website. Let me know if you end up using it and if you like it or even if you need help...I have encountered most problems people have had so I experienced them first hand lol
Sent from my SCH-I500 using XDA App
Gonna boot my phone up for the first time in 24 hours, maybe it's calmed down. I'd love to switch to ICS, but this isn't solving my "I don't want to wipe everything AGAIN" ordeal.
obsidianchao said:
Gonna boot my phone up for the first time in 24 hours, maybe it's calmed down. I'd love to switch to ICS, but this isn't solving my "I don't want to wipe everything AGAIN" ordeal.
Click to expand...
Click to collapse
Yeah I understand you on that...makes you sick to your stomach when you lose everything. Did you not have any backups of when your phone was in its working state? Backups are one of the most important things in my opinion. I learned the hard way
Sent from my SCH-I500 using XDA App
I haven't done a proper backup in a while. I should really start doing that, sigh.
obsidianchao said:
I haven't done a proper backup in a while. I should really start doing that, sigh.
Click to expand...
Click to collapse
boot into cwm and wipe cacnhe and dalvik. I normally do this once a week. Also if you have alot of apps downloaded to the internal memory this can happen. Check rootzwiki out for a thread about fixing the datadata force close issues.
http://rootzwiki.com/topic/5635-problems-with-datadata-causing-force-closes-for-google-apps/
Ahhh, thank you so much, this is perfect!
kadin.zimmerman said:
Yeah the ics ROM is very stable, I love it. Go to Google and type in "rootzwiki fascinate ics build 6" and you should find it on the rootzwiki website. Let me know if you end up using it and if you like it or even if you need help...I have encountered most problems people have had so I experienced them first hand lol
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Ah nice. I was hoping to see a stable ICS. So, it says there's no video hardware acceleration.. does that mean future updates will bring hardware acceleration for the fasciante? like h264 mkv's, or h264 mp4's, or even mpeg4 avi's? tsm/jt's rom doesn't have good video hardware support, MX video has to use SW almost all the time.
So I think I would like to check it out, but I wish I knew about it before I went through all the trouble last night to reflash and reinstall all my apps.. [was up till 3am working on it] lol
any major troubles with it? Also what CWM do I use? Perhaps the one on the CM7 fascinate wiki? [cwm4-bml-i500.tar] or the cwm 5.0.2.7 in vanilla gb?
Also do I need to odin it to anything? or can I go from what I've got now [tsm pool party]?
I've had no major troubles with the past 2 builds and definitely build 6 is the best. Not exactly sure what is meant by the hardware acceleration but everything about this ROM runs smooth. As for cwm version, just install any cwm and the ics ROM has its own that it will install. Once it installs it's own, it is recommended to not flash a new kernel once it does it's own because the one it puts on has stuff built in to make all the features work.
As for Odin, hmm....too be safe I would go back to stock and then throw a cwm kernel on. Then do a wipe data + cache and install build 5. Make sure it is running good then just clear cache and install build 6
Do a backup before you start all this just to be safe!!
Sent from my SCH-I500 using XDA App
kadin.zimmerman said:
As for Odin, hmm....too be safe I would go back to stock and then throw a cwm kernel on. Then do a wipe data + cache and install build 5. Make sure it is running good then just clear cache and install build 6
Do a backup before you start all this just to be safe!!
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Ok so how come I should install build 5 first?
mvmacd said:
Ok so how come I should install build 5 first?
Click to expand...
Click to collapse
I'm not sure if you have to or not, probably don't actually I'm not sure why I said that lol...I guess in my situation I had troubles along the way so I started at build 3 and worked my way up.
just go straight to build 6 and in that case wipe data and cache. And I still would go to stock first because I read somewhere that it best to go from the bml based versions to mtd.
I would then update your radio to EH03 if it isn't already
Sent from my SCH-I500 using XDA App
kadin.zimmerman said:
I'm not sure if you have to or not, probably don't actually I'm not sure why I said that lol...I guess in my situation I had troubles along the way so I started at build 3 and worked my way up.
just go straight to build 6 and in that case wipe data and cache. And I still would go to stock first because I read somewhere that it best to go from the bml based versions to mtd.
I would then update your radio to EH03 if it isn't already
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
awesome... yes I was planning on Odin'ing again, because I've found it gives the rom you flash after it better chance of survival.
It is a inconvenience though because I have to boot up W7 [Dual boot Linux] every time I wanna Odin.. haha, same thing back when I used my ipod touch for iTunes.
So what radio does the ics build 6 have? can they not use the eh03 radio [I'm assuming is superior to whatever it has]? And I assume heimdall can flash the "modem.bin" radio that I untar from the "CI500_VZW_EH03_GB_CM.tar.md5" like so:
heimdall flash --modem modem.bin
right?
The ics builds don't have a specific radio, it doesnt mess with the radio you currently have, so whatever radio you have now is what you will have after the rom. I just didn't know what radio you had now, and the reason i recommend the EH03 is because it is the newest stock radio from verizon - meaning it is definitely reliable.
I'm not sure what you mean by untaring the .tar file. Odin uses the .tar file, so do not untar the file, just leave it the way it is. Unless you mean you can specifically take the radio.tar file out from the other tar file. I have the EH03_radio.tar file so if you wanted it i could upload it somewhere and give you the link. Odin back to any stock firmware, then load a cwm recovery as well as the EH03 radio.
EDIT: Here you go http://dl.dropbox.com/u/32493357/eh03_radio.tar.md5
kadin.zimmerman said:
The ics builds don't have a specific radio, it doesnt mess with the radio you currently have, so whatever radio you have now is what you will have after the rom. I just didn't know what radio you had now, and the reason i recommend the EH03 is because it is the newest stock radio from verizon - meaning it is definitely reliable.
I'm not sure what you mean by untaring the .tar file. Odin uses the .tar file, so do not untar the file, just leave it the way it is. Unless you mean you can specifically take the radio.tar file out from the other tar file. I have the EH03_radio.tar file so if you wanted it i could upload it somewhere and give you the link. Odin back to any stock firmware, then load a cwm recovery as well as the EH03 radio.
EDIT: Here you go http://dl.dropbox.com/u/32493357/eh03_radio.tar.md5
Click to expand...
Click to collapse
sorry... what I meant is, I know how to extract the EH03 modem.bin file out of the ".tar.md5" file for the stock Verizon eh03 firmware.
I know how to flash CWM with heimdall, but I guess I do not need to flash the radio [ right? ] because I just came from a fresh eh03, completely wiped, cache, dalvik, and..... urmm, it is showing the same animation I had back on "Eclipse ROM" for Droid X2... ew... For some reason I do not like that particular animation. I guess you can change the boot animation though?
mvmacd said:
sorry... what I meant is, I know how to extract the EH03 modem.bin file out of the ".tar.md5" file for the stock Verizon eh03 firmware.
I know how to flash CWM with heimdall, but I guess I do not need to flash the radio [ right? ] because I just came from a fresh eh03, completely wiped, cache, dalvik, and..... urmm, it is showing the same animation I had back on "Eclipse ROM" for Droid X2... ew... For some reason I do not like that particular animation. I guess you can change the boot animation though?
Click to expand...
Click to collapse
Use the program "odin" to flash all your .tar.md5 files. You don't extract those files, you leave them in the .tar format. I gave you the link to download specifically the eh03 radio, but if you have it already on your phone you dont need to worry about it. As for the boot animation, the ics rom will install its own boot animation so no worries there.
You know about odin right? It is definitely the easiest way to flash kernels, radios, and stock firmware.
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