Related
all right I have been running ICS roms since passion v6ish. Tried Miui, cm7 and eugenes gingermod with no problems. The other day I decided I wanted to try Slim-ICS. It looks nifty. I flash the base.zip then vibrant essentials and get a boot loop. ok no big deal I go back to clockworkrecovery and it is now wome sort of touch based recovery. I attempt to restore my nandroid of the most recently working CM9 build I was running. Hangs at boot animation.. I tried flashing other ICS roms that I had used previously to no avail. I have tried every which way I can read to wipe data/factory reset, wip dalvik, cache partition boot and data. I gots nothin can not get anything to work. Now I try using vibrant toolbox to odin back to stock. no problemo. Rooted using update.zip and installed cm7. No problemo. Tried to install an ICS rom again and still nothing. I have odines at least 12 times and tried different ways to root, install recovery and flash an ICS rom and am not having any luck. I tried flashing the GB bootloaders through odin a few times with no success. I have been glancing over at kangs pink unicorn for sometime now.
Was I wrong in believing that flashing CM7 means I now have GB bootloaders?
Now that I have flashed aokp again when I boot I still see the cyanogen mod splash screen before I see the team kang boot animation....this strikes me as odd.
No, flashing CM doesn't mean you have Gingerbread bootloaders. I don't understand were you able to install AOKP after all? Regarding CM kernel boot screen before aokp boot animation, it is because Aokp uses CM9 kernel.
I had tried passion, euphoria and CM9 before I decided to try slimics and everything got borked from there. Currently running CM7.
So odin the GB bootloaders like in this thread no more failing at life right?
Here goes...
Thanks for the emotional support. Currently running Slim ICS.
It sure was strange using GB for a day...
Double noob I guess posting a q here.
hi guys
I recently bought a 2nd hand Vibrant for a really good price.
As far as i see the Vibrant is already rooted with 2.2.1 Lidroid, and CWM installed.
The battery usage is amazing with this rom, but I still fancy to install some custom GB roms.
I have some questions:
1. I would like to check if I am already on GB bootloader, please guide me to check?
2. If I am not on GB bootloader, I know I must first install it.
I wonder if Vibrant has some stock GB firmwares like captivate does? The stock camera is a must for my case ><
Am i correct if I follow this method from here
http://forum.xda-developers.com/showthread.php?t=1156832
3.Or actually I can simply flash any custom GB roms directly from where I am (Lidorid 2)
THX
Okay you know if you're not gb bootloaders when you turn on ur phone there's weird rainbow lines
If not then you are
And if you are then yea you can flash any rom
Sent from my GT-I9000 using xda premium
Let me confirm if you suggesting me to flash the GB roms?
If there's rainbows > froyo bootloader
if nothing > GB bootloader
So can i say actually Gb roms doesnt really need GB bootloader
as long as I am fine with the rainbows?
THX
j4371 said:
Let me confirm if you suggesting me to flash the GB roms?
If there's rainbows > froyo bootloader
if nothing > GB bootloader
So can i say actually Gb roms doesnt really need GB bootloader
as long as I am fine with the rainbows?
THX
Click to expand...
Click to collapse
I've run CM7, and CM9 (ICS) on Froyo boot loaders. For me it just makes the kernel screen flash and show again, then goes on to ROM booting. I'm running a Froyo boot loader right now.
Is lidroid a t959 rom or a t959v?
You need to have a t959 to be in the vibrant 3g section, otherwise you'll probably want the galaxy s 4g section.
Sent from my Sensation using Tapatalk 2
there is a Lidroid version for T959 - I have a Odin flash with it. I use it instead of JFD.
Want to know if you have the GB boot loaders? Easy -
Hold the Volume up button and the power button at the same time. If it goes to download mode....you got the GB bootloaders.
T959 Vibrant does not have Samsung 2.3 support. Samsung forgot about us after Froyo. There Froyo OTA upgrade bricked so many phones that they wont chance it again.
For 2.3 Gingerbread you will have to download a I9000 port found in our Development section. That said the ICS packages are very nice for Vibs too.
need help guys
A few hours ago, I was at work and bored.
I started to flash some GB roms without coming back to check this post.
The rom i used was phiremod-fusion-2.1.1.
As usual I nandroid my lidroid before doing anything.
Then I 3 wipes and flash the phiremod rom.
first time the flash was really quick and also rebooted itself.
But only this time I realise I have a newer CWM 5.xx version instead of my 2.xx version (Lidroid)
Ok, i wasn't panic, because i read some where before. It's prefectly fine for a cm7 if the first time it bootloop.
Then I pull battery, and boot into recovery again, to flash the 2nd time.
this time BAAM, prefect. I found myself with a 2.3.x cm7 mod rom.
but as soon as I found the camera apk is actually the MIUI one. I decided to nandroid back to Lidorid.
things turns ugly at this point, when i back to CWM i restored.
But only found some errors CWM said , but I remember CWM did say something like erasing boot.img before restoring.
After the resotre failed, I accidentally reboot my phone.
And now my vibrant only stuck at the typical black boot screen "Vibrant in the middle with samsung at the bottom.
I tried to boot back to recovery, but no luck.
right now I am telling myself i probably need to restore to stock.
Can my fellow xda members guide me the proper way to
1. boot CWM
2. download mode
Given the fact that I am not too sure about which bootloader I am on.
THX people!!
Yup, you'll need to go back to stock. There are plenty of write-ups on how to do it.
Also, NEVER restore a 2.2 backup after you install 2.3 or higher. The file systems and partitions are different. Odin back to stock, install lidroid again, and then try to restore your backup.
j4371 said:
need help guys
A few hours ago, I was at work and bored.
I started to flash some GB roms without coming back to check this post.
The rom i used was phiremod-fusion-2.1.1.
As usual I nandroid my lidroid before doing anything.
Then I 3 wipes and flash the phiremod rom.
first time the flash was really quick and also rebooted itself.
But only this time I realise I have a newer CWM 5.xx version instead of my 2.xx version (Lidroid)
Ok, i wasn't panic, because i read some where before. It's prefectly fine for a cm7 if the first time it bootloop.
Then I pull battery, and boot into recovery again, to flash the 2nd time.
this time BAAM, prefect. I found myself with a 2.3.x cm7 mod rom.
but as soon as I found the camera apk is actually the MIUI one. I decided to nandroid back to Lidorid.
things turns ugly at this point, when i back to CWM i restored.
But only found some errors CWM said , but I remember CWM did say something like erasing boot.img before restoring.
After the resotre failed, I accidentally reboot my phone.
And now my vibrant only stuck at the typical black boot screen "Vibrant in the middle with samsung at the bottom.
I tried to boot back to recovery, but no luck.
right now I am telling myself i probably need to restore to stock.
Can my fellow xda members guide me the proper way to
1. boot CWM
2. download mode
Given the fact that I am not too sure about which bootloader I am on.
THX people!!
Click to expand...
Click to collapse
Get into download mode by while it's off, holding VOL-UP + Vol-DOWN and plugging in USB.
y vibrant revived!!
Thx everyone
After this, I am thinking to ask my colleagueto make one JIG for me.
I'd like to confirm it's same as SGS, i.e. 3 X 10kohm in series
hi,
I am sorry if this is a dumb question. But i have failed several attempts while shifting to ICS (RC 5 by team-nyx). Every time when i install ROM & kernel via CWM and boot the device (vibrant t959) it freezes on the screen with VIBRANT and SAMSUNG displaying WHITE on BLACK back ground.
i have gone back to JFD and tried several times BUT same result.
I was on froyo 2.2 (build UVKB5) updated via kies and did it but no luck. I followed wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide and did starting from No. 03 --
downloaded Cmenard's Kernel with the ClockworkMod Recovery 2.5
Heimdall Suite 1.3.2 for windows
AND upto No. 9 under Windows ONLY: section
the CWM installs as it says (A blue transfer bar will appear on the phone showing the kernel being transferred. The device will reboot automatically. )
after that i cleared factory, cache and dalvik cache.
then I select install Zip from SD card and chose the ROM (which is from team-nyx.com/index.php/releases).
after 3% it says rebooting and vibrant shuts down and reboots.. when after I clicked the combo (vol+vol-power) to enter the CWM its not there.. so I reinstall using [heimdall flash --kernel zImage] command in PC's cmd. then after i redid the same to select from SD and then ROM installed ok.
then I selected the kerenel which was taken by same source and installation went normal..
after I select reboot from CWM it reboots and hangs on vibrant screen.
I cannot figure OUT WHAT IM doing WRONG..
Please HELP ME..!!!
thank you for your time
I am moving to 2.2 via kies after going back to stock JFD. then i will root my vibrant. after that i will install ROM manager from market. THEN i will try to FLASH to ICS RC 5 + kernel from nyx TEAM.
I dont know what is wrong.. please HELP
From what you told us it sounds right. Have you tried a different ICS rom? Give ICS slim a try. When you Odin back did you checked re-partition?
Sent from my SGH-T959 using Tapatalk 2
You should try flashing the Gingerbread bootloaders using Odin after you flash back to stock. Those bootloaders can run a Froyo ROM as well as ICS so it wouldn't hurt to do either way. After you flash the bootloader then try flashing the ROM.
And try a different ROM like iwillkillyou suggested. Slim is good, but ICZen is very solid if you're tipping your toes into ICS.
iwillkillyou said:
From what you told us it sounds right. Have you tried a different ICS rom? Give ICS slim a try. When you Odin back did you checked re-partition?
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
hi,
thank you for the reply. No i havent tried a different ROM. yes I checked repartiton when ODin Y this is happening.. I have Flashed this ROM once.. but then when someone calls me they cudnt hear me clearly.. when i initiate the call its ok.. so I moved back to JFD..:/
kaiser_bun said:
You should try flashing the Gingerbread bootloaders using Odin after you flash back to stock. Those bootloaders can run a Froyo ROM as well as ICS so it wouldn't hurt to do either way. After you flash the bootloader then try flashing the ROM.
And try a different ROM like iwillkillyou suggested. Slim is good, but ICZen is very solid if you're tipping your toes into ICS.
Click to expand...
Click to collapse
thank you for the reply.. I jz finished Updating to 2.2 via kies..ok I will flash Gingerbread bootloaders using Odin. I will try I think it wont be necessary to ROOT the vibrant..to Flash Bootloaders.. I am going to Flash the ICS ROM via ROM manager (after rooting via SuperOneclick root2.3.3)..
haarsh said:
thank you for the reply.. I jz finished Updating to 2.2 via kies..ok I will flash Gingerbread bootloaders using Odin. I will try I think it wont be necessary to ROOT the vibrant..to Flash Bootloaders.. I am going to Flash the ICS ROM via ROM manager (after rooting via SuperOneclick root2.3.3)..
Click to expand...
Click to collapse
Just so that you know, everytime you are using Kies, you are running the risk of hardbricking your device. It is notorius for that and in fact someone last week got HBricked with it.
I don't use ROM Manager and probably won't as long as I have a Vibrant. All you need to do is go back to JFD and pull the CWR from my signature and put it on your internal_sd and label it as Update.zip. Then boot into recovery and hit Reinstall PAckages (might have to do this twice) and your stock recovery (blue) will go to CWR (green) and you can flash away.
Also for more detailed instructions, se my ICS install giude also in my signature.
Woodrube said:
Just so that you know, everytime you are using Kies, you are running the risk of hardbricking your device. It is notorius for that and in fact someone last week got HBricked with it.
I don't use ROM Manager and probably won't as long as I have a Vibrant. All you need to do is go back to JFD and pull the CWR from my signature and put it on your internal_sd and label it as Update.zip. Then boot into recovery and hit Reinstall PAckages (might have to do this twice) and your stock recovery (blue) will go to CWR (green) and you can flash away.
Also for more detailed instructions, se my ICS install giude also in my signature.
Click to expand...
Click to collapse
Thank you for the links.. I downloaded and place CWR inside SD. Without kies can we install official releases via Odin.. is there any way.. im sorry if that is a stupid question
No stupid questions. That is why we are here. I am pretty sure there is a flashable 2.2 stock floating aroung here. I personally don't have it though. Custom 2.2's are at this point tweaked so completely out, that they will blow the doors off any 2.2 stock ROM out there. I usggest Moped_Ryder's ROMs and Fishman's Bionix-redux ROMs. Quality, fast and stable. Not ICS, but everything works and no fear of the dreaded Encryption Bug.
PM incoming btw.
Woodrube said:
No stupid questions. That is why we are here. I am pretty sure there is a flashable 2.2 stock floating aroung here. I personally don't have it though. Custom 2.2's are at this point tweaked so completely out, that they will blow the doors off any 2.2 stock ROM out there. I usggest Moped_Ryder's ROMs and Fishman's Bionix-redux ROMs. Quality, fast and stable. Not ICS, but everything works and no fear of the dreaded Encryption Bug.
PM incoming btw.
Click to expand...
Click to collapse
thank you. btw can we Flash to 2.2 via CWM .. directly selecting the ROM from SD .. without Odin
If you can find it, you should be able to. Just put on your card and flash away, taking care to wipe accordingly.
A note on flow though:
2.1, 2.2 -can go into and out of any 2.2 there is laterally.
2.3-4.0 -will need to Odin to stock before going back to a 2.2 ROM. Can move laterally from 4.0 to 4.0 though.
(i.e DO NOT try to restore a 2.2 nandroid or flash a 2.2 ROM when you are on an ICS variant. the /system is completely changed and reformatted. You need to Odin to get it back.)
Moped Ryder uploaded a semi tweaked version of the stock 2.2 build. It's a zip that you can just flash using CWR:
http://forum.xda-developers.com/showthread.php?t=1674519
It comes rooted with busybox and some other goodies, but it's the stock kernel and whatnot. I'd highly recommend Fishman's Bionix-V Mod or Moped Ryder's Slim_Ryder ROMs if you're going to be on Froyo though. They're both great, but I went with Fishman's latest Bionix Mod since I couldn't get bluetooth to work on Moped Ryder's ROM. Which is really unfortunate because I loved Moped Ryder's otherwise.
And you don't have to Odin back to stock if you're just bouncing around Froyo or Eclair builds; only if you're coming from Gingerbread or ICS (2.3 or 4.0).
Keep us updated. I'm curious to see what worked. It's probably the gingerbread loaders. But, who knows.
Sent from my SGH-T959 using Tapatalk 2
Is your Samsung Vibrant (T959) Rooted.?
iwillkillyou said:
Keep us updated. I'm curious to see what worked. It's probably the gingerbread loaders. But, who knows.
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
hi.. I tried again with flashing semaphore kernel through Odin installed CWM version higher than 2.5 to install ICS RC5 by nyx --sorry i need that soo badly so didnt checked anything else ..
@that time I was on vibrant 2.2 UVKB5 (stock)
NOT rooted
I didnt had so called
bootloaders
Click to expand...
Click to collapse
(i dunno what it means though--have to search )
BUT it didnt worked for me instead freezes at Vibrant start-up screen. So i Couldnt switch back to CWM. I Odin back to JFD with repartition clicked and my vibrant was locked (network lock). Finally, I got it cleared by application named Galaxy_S Unlock by Helroz from the market.
Now I am at the very beginning again. I am now on 2.1 JFD. I dont know WHY this happening to me .. :crying:
gonna try again with GB bootloaders.. BUT Im sick of failing and going back to 2.1 (my friends who are having captivate had no problem)
Speedy5150 said:
Is your Samsung Vibrant (T959) Rooted.?
Click to expand...
Click to collapse
At the time i was trying it was NOT rooted.. But now i have it rooted because i needed to unlock the network . which happened me for the very first time after flashing back to JFD using Odin..
Thank you guys for the links and thoughts on 2.2 ROMs.. I am not that expert . Thats why i was updating to 2.2 via KIES -- which is not a good idea as it seems with the ability 2 brick the device. I am going to get Bionix-V FishmanMod V4 FULL and install as http://forum.xda-developers.com/showthread.php?t=1441976 says..
It says Boot into clockwork recovery and i think i found something to do that in this thread http://forum.xda-developers.com/showthread.php?t=734164
I have to get ROM manager from market and go through it..
BUT Im damn upset with the RC5 ICS update by nyx being unable to installed into my device.. I will try with GB bootloaders flashed ..
If you are going to go with Fish's ROM, then all you need to do is Odin back to JFD and pull the CWR from my signature and put it on your internal_sd and label it as Update.zip. Then boot into recovery and hit Reinstall Packages (might have to do this twice) and your stock recovery (blue) will go to CWR (green) and you can flash away.
Fish also has a Odin package that you can flash his ROM through Odin and not have to deal with CWR.
ROM Manager is no longer supporting 2.1, so if you do go back to JFD, then it will be hard to get RM. It is out there somewhere but really all you need is the Update.zip from above to do it. I suggest that you stay on Fish's ROM for awhile and read about ICS installs and all the little things that are involved. If you do flash Fish's ROM, you don't need to mess with the bootloaders.
Btw, aside from Kies, messing with Bootloaders is one of the sure fire ways to hardbrick your device. It only takes seconds to flash them, but do it wrong and, well you know.
Good luck and ask if you have any.
Woodrube said:
If you are going to go with Fish's ROM, then all you need to do is Odin back to JFD and pull the CWR from my signature and put it on your internal_sd and label it as Update.zip. Then boot into recovery and hit Reinstall Packages (might have to do this twice) and your stock recovery (blue) will go to CWR (green) and you can flash away.
Fish also has a Odin package that you can flash his ROM through Odin and not have to deal with CWR.
ROM Manager is no longer supporting 2.1, so if you do go back to JFD, then it will be hard to get RM. It is out there somewhere but really all you need is the Update.zip from above to do it. I suggest that you stay on Fish's ROM for awhile and read about ICS installs and all the little things that are involved. If you do flash Fish's ROM, you don't need to mess with the bootloaders.
Btw, aside from Kies, messing with Bootloaders is one of the sure fire ways to hardbrick your device. It only takes seconds to flash them, but do it wrong and, well you know.
Good luck and ask if you have any.
Click to expand...
Click to collapse
thanks alot for the info brother.. some guys told me STUPID.. but YOU guys are awesome.. I am a newbie to this flashing and stuff.. but learned a lot from XDA . Thanks again for the reply. now I have stock 2.1 with ROOT . (rooted cuz i had to unlock the vibrant). I will flash to Fish's 2.2 ROM soon. BTW may i ask you after moving to Fish's ROM and later if i need to move to ICS still can I do it without messing with Bootloaders..
Thank you
That is what we are here for in the Q&A/General sections.
Regaring your question about Gingerbread bootloaders being needed:::Yes and No.
Gingerbread bootloaders were required in the infancy of ICS ROMs bc they prevented what is called "Rainbows" in your clockwork where you couldn't see anything. The options were there but you just couldn't see them. Then as ICS evolved, the need for GB bl's lessened and now you don't need them at all.
But...There's always a but...Gingerbread bl's are recommended by most of the devs for ICS builds because they seem to work better with the custom recoveries that come with some of the kernels. There is more to it but in short, GB bl's are not required but recommended.
If you go to my ICS install guide, in the middle pages and more again at the end, Yosup (highly respected user) and I have a detailed conversation about bootloaders and their installation. Once he got over the fear and did it, he was hooked and flashing ICS ROMs weekly if not more. It is a very informative section of that thread.
Okay in the last three days I have softbricked my vibrant several times. Each time after tyring to update to a newer ROM. Now however I can not even return to what I had, only the Eclair ROM. I was running Tigers Breath Kernel with Bionix ROM
I should point out that my efs has hone corrupt mysteriously on this phone twice before in the past , and luckily I made a back up that was easily restored.
I now have a vibrant that was restored to a stock image however I believe the stock image is incomplete. It lacks the ability to reset.Says Something like reset service unavailable. I would be happy for now at the stock eclair image however I run into the same issue I had on Eclair before. Android Market will not download any apk, it starts pauses and fails.. When I look at the corresponding device in google play on the web I see it says PHONE and there is another SAMSUNG GALAXY VIBRANT T 969 . However the corresponding device is PHONE . So Google has no idea what my phone is. This could be the market issue however I want to point out that when I first set up the google account I can go to the market and download but once the market app is updated, it no longer works!
So a few days ago my goal was to attempt to install Gingerbread or higher to take a look at xbmc for android betas. The result has literally given me a 3 day headache.
before three days ago I was running Bionix and Tigers breath kernel. I tried to follow instructions to downgrade to stock and then to Gingerbread or higher. I have now made more the several attempts. All I can do is O|DIN to the stock image I have which complains that oit lacks the reset service.
Even trying to restore either of My CWM back ujps of Bionix fails.
I also have another interesting thing that when I attempt to install CWM from an update.zip I get screen goes black for a second then i see CWM running . It is as if it is running it instead of installing it.
The one image that I have that I can restore does have ROM manager that55 always reports a download error with installing CWM from there
Is there an image that I can install from ODIN that will get me Gingerbread or higher? ODIN seems to be my only hope.
And what of the market errors , do ya think my EFS is hammered again? before the issue was the electronic serial number (dont remember what its called) but the carrier stopped honoring the generic number it was producing. I do however recall last year that I could not get the market working and now I seem to have returned to that. I think it has much to do with the market version on Eclair.
would the vibrant be adequate to run XBMC beta at lest to test it?
Should I repartition from ODIN?
Is there a stock froyo image around at least that I can install from ODIN?
Thanks,
Mark
Yes you should check repartition when you use Odin to flash ROMs. There are froyo Odin images out there but I don't think there is a "true" stock 2.2 froyo image, only custom ones. I know there is a ROM uploaded by moped ryder that is as close as you will get to stock 2.2, fishman made an odin image of it. You can check it out here http://forum.xda-developers.com/showthread.php?t=1674519. I know for sure fishman uploads odin images with his 2.2 ROMS, they are far from stock but I love them. I've been running Axura resurrected 2.2 for months, its solid. You can check it out with this link http://forum.xda-developers.com/showthread.php?t=1787267, it has odin images. Just be sure to read first and follow directions.
Sent from my SGH-T959 using Tapatalk
If it was me, I would Odin back to stock JFD. There is a guide on YouTube by Eddie1west that I recommend.
Then just I would follow the guide to install Gingerbread boot loaders.
Then I would download and wipe/wipe cache/dalvik and flash a fresh Froyo ROM download. I use Bionix V fishmans with the Bali kernel. Then if your satisfied then stop. If not, download latest CM9 Nightly (ICS). Wipe/wipe cache/dalvik and flash the ROM and common files.
Since you've gone this far download latest Helly Bean all in one, wipe/wipe cache/dalvik and flash HB and the add on file.
Might as well right? I had lots of trouble flashing up to HB yesterday, and I had never had any issues before.. but if your looking to get to GB or beyond... I would follow the steps above. Could be overkill. But I tried about every other combination of flashes I could think of before Odining back and doing it that way.
I have had a Bad ESN Fascinate for a while that I was playing around with, trying to get it to work on Sprint... No go. Anyway, it was rooted with a stock GB ROM and I decided I wanted to try out some of the ICS or Jellybean offerings that XDA has in its forums.
To be honest, I am no noob, but I didn't do enough research to begin with. First I installed GeeWiz 2.9 Kernel, System, and 2.8 Recovery. I didn't like the 2.8 Recovery, so I tried to flash something else, but nothing would replace it. Then I tried to install Baked CM10 from the GeeWiz recovery, and it went downhill from there.
Long story short, I have ODIN'd back to stock EH03 and tried to update to a couple of CM10 ROMs using the guides I have found here and on a few other forums. I have a working install of Hacksungs CM9 build 5 as of right now, but I can't get any further.
After using ODIN to get to Stock EH03, I ODIN the CWM4 for CM7. 3-fingering brings me to CWM4 where I begin the install of CM9. When it examines the partition BML/MTD it reboots the recovery (took me a while to figure that out) in to CWM 5.5.0.4 where it finishes the CM9 install. When I soft reboot into recovery, I get CWM 5.5.0.4. According to the guides, this is where I would flash CM10. It runs the update, but when I go to reboot the system, it reboots into a recovery of CWM 6.0.1.4. Also, if I reboot the system from CWM5 without installing anything, it boots back into CM9 just fine.
I am pretty sure I installed CWM 6.0.1.4 sometime in the past, but to be honest I have no recollection of when.
My question is multi-part: How do I get rid of CWM6; why is it still there after all the repartitioning with ODIN (with and without PIT file), MTD partition formatting, etc; why can't I get CM10 to install?
While this is a fairly wordy post, I have to say, I do have a working Fascinate with CM9 that I am enjoying playing with. I just thought if nothing else, people might get a laugh out of my struggles with this phone, that is basically a web browser and toy.
FWIW I have seriously ODIN'd back to stock about 5 or 6 times today alone.
Thanks for any help or suggestions in advance.
Unlike Gingerbread and earlier, with ICS and JB kernels they include whatever version of recovery the developer wants to include.
Is there a reason you don't want the latest CWM?
Sent from my SCH-I500 using xda app-developers app
Its been awhile for me since I had to go back to stock, but unless something has changed the three finger reboot into cwm caused some problems when flashing. Try rebooting to recovery through power menu.
Some ROMs are requiring to be installed a second time to "stick" due to partition layout changes.
Sent from my SCH-I500 using xda app-developers app
Thanks for the info on the ICS and JB attached recoveries. I was unaware of that. Maybe that's where the CWM6 came from.
And it isn't that I don't want to most current, it just didn't seem to want to play nice with the ICS and JB Roms I was trying to installed.
Now my problem is that the phone won't boot when powered down from ICS. Glad this isn't my main phone.
Sent from my EVO using xda app-developers app
That's what I had read everywhere... NEVER 3-Finger into Recovery from ICS or JB. I still managed to do it a few l times when I wasn't thinking.
It definitely screws up the install. I can attest to that.
I just don't get why there are all three CWM versions present during the install, and if I am installing CWM4 fixed for CM7, and one of the other two is included with the ICS Rom, where did the 3rd one come from? Just a big, confusing mess
Sent from my EVO using xda app-developers app
From my limited knowledge,,,
I know the fixed cwm is what you need to get out of a 3 finger boot loop,,, I've had to do that...
Cwm 6 is what runs and works with cm10/jb roms,,,
Causes no errors that I'm aware of...
No more 3 finger,, always use power button/reboot
Once you have started an install of say cm10 ... Let it run its course , so to speak,,, if it comes up with cwm5 or cwm6 then that is the one the developer designed it to work with,,,
Let it come all the way up,, and then reboot through the power button method always,,,, you'll get used to that quick enough , as i remember the old gb froyo stuff didn't offer this method
I keep a copy of the fixed cwm just in case i happen to accidentally 3 finger ever again...
Sent from my swagger
spikeekips said:
That's what I had read everywhere... NEVER 3-Finger into Recovery from ICS or JB. I still managed to do it a few l times when I wasn't thinking.
It definitely screws up the install. I can attest to that.
I just don't get why there are all three CWM versions present during the install, and if I am installing CWM4 fixed for CM7, and one of the other two is included with the ICS Rom, where did the 3rd one come from? Just a big, confusing mess
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Not sure if you are still looking for advice but here is a little guide that has not failed me at all. If you follow this then you should come to the latest JB rom that you want.
Click here