Related
Use At Your Own Risk!!!
Hey all. I hope my experience trying to get ROM Manager and CWM working under AT&T's official FROYO 2.2 update will keep someone from throwing their Captivate against the wall.
Here is the sequence I used. I admit it is kinda convoluted, but it did finally work and I can get to the CWM boot menu. This assumes you follow the instructions associated with each individual step.
1. Blast the phone back to 2.1 with [STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY
2. Run the Kies Mini update from Samsung/AT&T to get the Official FROYO build.
3. Only run Shell Root with [APP]SuperOneClick v1.7 (Root, Unroot, Enable Non-Market App)
4. Run the recovery 3e modified to work like recovery 2e - Updated 01/23/2011
(You know this worked if when you boot to Recovery mode you see a line that says, checksum confirmation need_checksum[0], shows up.)
5. Reboot!!!
6. Run the SuperOneClick v1.7 and choose Root then Enable Non-Market Apps. Use the psneuter radio button.
7. Reboot!!!
8. Delete any update.zip on the internal SD.
9. Go to the Market and install ROM Manager.
10. Run ROM Manager, let it d/l and install CWM. It should ask for SU permissions. If it doesn't you probably forgot to reboot.
11. Use ROM Manager to Reboot into Recovery.
12. Choose reinstall packages from the BLUE recovery menu. You will have to do this TWICE and then the GREEN CWM Recovery menu should appear.
Now you can use ROM Manager/CWM to do full backups which was the reason why I wanted to get it to work as I'm still leary about how well Titanium Backup works and coming from the IT world I love imaging.
UPDATE
OK I just installed [KERNEL] stock+Voodoo stable 5.x for Captivate and it worked fine. Bobapunk's steps should work fine but I haven't followed his steps.
UPDATE 2
Well it seemed to work fine, but it gave errors reading cache files and I could no longer install apps off the Market. Doing a Master Clear atm and will try Boba's order.
UPDATE 3
Seems to have been an error with partitioning. Back to 2.1, Kies to 2.2, Odin3 1.81 to PDA the Kernel, then repartition and format ALL partitions (had to do this to format BOOT). Then back to 2.1, Kies to 2.2, OneClick to root, Odin3 1.81 to PDA kernel. Now I can have fun getting rid of the bloatware and I might install plumbBob's GPS fix.
UPDATE 4
Everything is working fine now. Did [FIX] PlumbBob GPS Fix 1.0 [UPDATE 3/10/2011] and the GPS locks on in about 5 seconds in LBSTestMode, but Google Maps/Navigation still seems to lose lock often. Using Captivate SGS Tools and recommend it highly.
UPDATE 5
Works beautifully except for Messaging does an FC on boot. Doesn't seem to matter and I'm not a big texter and it does work afterward. One of the system apps I uninstalled with TB must be tied in to it. Not sure which one and my week at home is up. Disable media scanning in SGS Tools doesn't work, but Rescan Media ROOT (search the Market) does.
As Always Use At Your Own Risk!!!
I am glad that you got this figured out. I accomplished this a little differently.
I had AT&T 2.1 rooted
I upgraded to 2.2 via Kies
I rooted with Super One Click
I flashed Supercurio's Kb1+ Voodoo Kernel
I flashed CWM Recovery with ROM Manager
This worked fine on my 1009 build captivare. It seems simpler than your process and you get Voodoo along with CWM Recovery.
Well I'm trying to keep it as stock as possible. Next step will be to use TB to get rid of the AT&T bloatware. I haven't decided if I will use the Voodoo lagfix or not as it makes a radical filesystem change and some posts have warned about flashing new ROMS to it's FS and ending up with expensive paperweights.
BTW didn't you have to go back to the stock (i.e. unrooted) ROM to get Kies to perform the update?
bobapunk said:
I am glad that you got this figured out. I accomplished this a little differently.
I had AT&T 2.1 rooted
I upgraded to 2.2 via Kies
I rooted with Super One Click
I flashed Supercurio's Kb1+ Voodoo Kernel
I flashed CWM Recovery with ROM Manager
This worked fine on my 1009 build captivare. It seems simpler than your process and you get Voodoo along with CWM Recovery.
Click to expand...
Click to collapse
I used Kies mini to upgrade to 2.2, then rooted, installed Rom Manager, and Titanium Backup, TB works well, but Rom Manager wont reboot in recovery and go to green...always stays in blue...error messages when I reinstall pkgs..so...reading your fix, if I was to be able to flash Supercurio Kb1+ Voodoo Kernel, should I be able to get to the green in Rom Manager?...what is CWM Recovery?...and what about that update file in my sd...delete?..or keep it?
Thanks in advance for any help....been 6 weeks now and cant get the green to happen in Rom Manager...so other than Tit. Bac. nothing else works...where to get the Supercurio Kb1?....and how to flash CWM?...thanks...any steps to install supercurio would be appreciated...thanks..
Studio52
Does this will work on my samsung mini gt s5570,i have root and custom rom
Thanks in advance
Hi there,
Since gingerbread with most probably be the last update for SGS i would like to install a custom mod.
Now i have been trying to do this (darky 10 RC4) for the past 2 days.
I followed Darky's instructions then i had a problem with the CWM only accepting "edified" script.
So i downloaded rom manger and tried to downgrade ta 2.5 but as soon as i tap on the 2.5 it immediately comes up with an error, "an error occured while flashing your recovery."
this is done on a 2.3.3 JVB SGS with CWM 3 installed (orange text).
Are there alternate routes? maybe downgrading to android 2.2 installing an older version of darky and than upgrading the darky rom?
any help is much appreciated.
thanks
Download the rom CWM-zip and put it in your internal sdcard.
Download some froyo-kernel (yes, froyo) with CWM 2.5. Speedmod for example. Then flash it with Odin repartition and auto-reboot unticked. When the flashing process is completed, pull the battery and then boot to recovery (3 button combo). Now you have CWM 2.5 and you can flash the CWM-zip from there.
thanks, i wil try that.
Now you have CWM 2.5 and you can flash the CWM-zip from there.
Click to expand...
Click to collapse
just 1 question, why do i need t flash CWM-zip if i am already on CMW 2.5?
jan-sgs said:
thanks, i wil try that.
just 1 question, why do i need t flash CWM-zip if i am already on CMW 2.5?
Click to expand...
Click to collapse
Sorry. With CWM-zip I meant the Darky's Rom.zip, which can be flashed through CWM.
it didnt work, u just gave up.
hopefully some new rom update that is edified will show up in a couple of months
Install supercurio hacked kernel, it has recovery 2.5 instead of 3.0.0.5. From there you should be able to install darky's rom. If the new version of his kernel is recovery 3, tell me i'll send the old one just for the purpose.
Hi,
ok last attempt
i flashed ( odin PDA, no pit and no repartition) with this link:
Kernel Download:
Gingerbread-GT-I9000-stock-kernel+hacks.tar
http://forum.xda-developers.com/showthread.php?t=975349
while i was on
PDA_I9000XWJVB - PHONE_I9000XXJVK - CSC_I9000XEEJV3
rooted with root CF-Root-XX_OXA_JVK-v3.1-CWM3RFS
and lag fixed with CF-Root-ext4-v1.2
and it forking worked red text 2.5 THANKS A BUNCH!
edit just a problema. it is only booting in CWM.
reattempting this without the lag fix.
2nd attempt with PDA_I9000XWJVB - PHONE_I9000XXJVK - CSC_I9000XEEJV3
and without lag fix not rooting.
phone stuck looping at booting with strange sound on each boot loop
3rd attempt with rooting, but no lagfix
If you are only rebooting in recovery, did you flash the new kernel, then reboot recovery ? if yes, the easy way to get out, is to reboot in download then reflash the wanted kernel (Since your rom is installed, you can install any kernel (GB of course)) then, it will reboot in recovery again and just reboot system now. This should fix your problem.
edit : Dont forget to get CF-root 3.1 for JVB and not JVK.
chadouming said:
If you are only rebooting in recovery, did you flash the new kernel, then reboot recovery ? if yes, the easy way to get out, is to reboot in download then reflash the wanted kernel (Since your rom is installed, you can install any kernel (GB of course)) then, it will reboot in recovery again and just reboot system now. This should fix your problem.
edit : Dont forget to get CF-root 3.1 for JVB and not JVK.
Click to expand...
Click to collapse
ok, i couldnt do that before because i had deleted the rom form the internal SD.
and also thanks for pointing out that i had the wrong root (i worked by you never know if it could case problems)
ok so
PDA_I9000XWJVB - PHONE_I9000XXJVK - CSC_I9000XEEJV3
root CF-Root-XW_XEE_JVB-v3.1-CWM3RFS
lagfix CF-Root-ext4-v1.2-Addon
and
Gingerbread-GT-I9000-stock-kernel+hacks
and the zip is in progress.
ps it wasnt stuck the previous time, i was pressing the middle key as the selection while i should have been pressing the power button.
thanks for your help very much appreciated.
if i get some free time i will write at tutorial since i could not the solution.
This isn't development, moved to Q&A
I have an i9000M running UGKG3, rooted. I still have the stock kernel and have no modifications. I'm trying to get a CWM or 2e recovery that will let me install update.zip files that aren't signed.
I have tried kernel after kernel, getting bootloops with every one.
I tried signing the CWM update.zip myself but it only managed to remove one of the two errors I get about it not being signed in 3e Recovery. I tried signing it multiple ways, nothing.
I tried replacing some of the recovery files with Root Explorer, to no avail.
I also tried flashing JVQ and JVR so I could use CF-ROOT, but they didn't even get to the "Galaxy S" boot logo before it looped.
Does anyone have a solution?
Anything that works, really. A signed update.zip, a i9000m compatible kernel, a successful replacement method, anything that will install a usable recovery.
Thanks in advance,
Getinaf
I'm in the same situation as you. I have UGKG3 installed, with the rooted stock kernel via Odin. I have tried almost every custom kernel I can think of, and they all boot loop. I've tried Rom Manager to install CWM, and it doesn't work either. I haven't tried any JVR roms yet, but from what I read they should work, so I'm surprised you're getting bootloops there too.
I guess there is something different with gingerbread compared to froyo that makes the kernel more picky. On froyo I had the stock JL2 rom, and was able to install the speedmod k13e kernel to get CWM without any problems at all.
I guess we'll have to beg and plea for a dev to make a modified KG3 kernel with root and CWM recovery. I would be happy with that. I don't care about lagfixes or any other mods to the kernel. I just want root and CWM
I totally agree, that or I'll try and cook us one. I hear there are tutorials for things like root and cwm. I'm really actually trying to install juwe's smart rom, and for the life of me nothing is working. I'm sure there are more people like us out there too, it will be worth it to find a solution.
Sent from my GT-I9000M using XDA App
Getinaf said:
I totally agree, that or I'll try and cook us one. I hear there are tutorials for things like root and cwm.
Click to expand...
Click to collapse
I am very tempted to make own kernel. Nice and simple: root, and cwm. That's it. Now to find a tutorial
has anyone figured this out yet?i'm in the same situation...
Just flash this kernel on top of whatever you have, it'll work... trust me!
http://forum.xda-developers.com/showthread.php?t=1112908
I've been running that kernel for months back then when I was still running official Gingerbread KG3 from Bell and it's the best one there is.
Installation steps :
- Download kernel
- Start Odin, make sure Kies' services are all shut down
- Select Kernel as PDA in Odin
- Put phone in download mode
- Connect through USB ... Odin should detect phone
- Hit start, reboot phone
- Enjoy, you're done!
If you have problems like FC after that:
- reboot to recovery
- "wipe cache"
- Advanced menu --> Wipe Dalvik cache
- reboot (be patient, it'll take a few minutes to reconstruct dalvik cache)
- you're done!
Did all this and nOw in a boot loop. Can't reflash as debugging is off. I flashed first tIme frOm mObile Odin ?
What ROM did you have installed when you flashed Semaphore kernel?
Please help
HiKsFiles said:
Just flash this kernel on top of whatever you have, it'll work... trust me!
http://forum.xda-developers.com/showthread.php?t=1112908
I've been running that kernel for months back then when I was still running official Gingerbread KG3 from Bell and it's the best one there is.
Installation steps :
- Download kernel
- Start Odin, make sure Kies' services are all shut down
- Select Kernel as PDA in Odin
- Put phone in download mode
- Connect through USB ... Odin should detect phone
- Hit start, reboot phone
- Enjoy, you're done!
If you have problems like FC after that:
- reboot to recovery
- "wipe cache"
- Advanced menu --> Wipe Dalvik cache
- reboot (be patient, it'll take a few minutes to reconstruct dalvik cache)
- you're done!
Click to expand...
Click to collapse
Hi,
Please help... i have samsung i9000 and had stock rooted the phone. Tried to install the above kernel and now the phone is stuck on the bootloop, not booting up... Please help
So I updated the MIUI on my Cappy from whatever I had before to 2.3.30 that is GB 2.3.7 from this location:
http://miuiandroid.com/community/threads/archived-miui-versions-captivate-gb.16558/
I didnt care for it so I downloaded SlimICS. I downloaded the base and the cappy essentials. Put them both on my internal sd. I factory reset, wiped data, cache and system and dalvic, just as i do for every phone i work on. I ran the SlimICS base and now it keeps rebooting and going back into recovery and doing this:
Finding update package...
Opening update package...
Installing update...
Slim ICS
Once Slim ICS pops up, it reboots and does it all over. I can yank the battery and manually go into recovery, but if i try to boot it up normal, it goes back into the loop. I am on CWM 5.0.2.7 also.
So what did i miss?
GB bootloaders most likely missing - flash 'em using Heimdall. And SlimICS doesn't have modem. So. Flash my ROM for a change may be.
Sounds like you just need to flash again. You have to do that when you are going from GB to ICS, and vice versa I believe.
And you flashed the base and the cappy essentials right? Not just the base
Sent from my SGH-I897 using xda premium
korockinout13 said:
Sounds like you just need to flash again. You have to do that when you are going from GB to ICS, and vice versa I believe.
Click to expand...
Click to collapse
trying to flash again just put it back in the loop. And I read that that does happen alot going from GB to ICS on the Cappy. But for Slim it didnt work.
Wdustin1 said:
And you flashed the base and the cappy essentials right? Not just the base
Click to expand...
Click to collapse
I never could get that far because it was the base that I started to install and it got bootlooped on, everytime it restarted, it went back into recovery and started to run the base again, and repeated boot loop. I read somewhere that teamhacksung's rom would get me over the GB to ICS bridge. This one here:
http://forum.xda-developers.com/showthread.php?t=1363760
It did the bootloop to, but when i yanked the battery and went back in and installed it a 2nd time, it didnt restart and installed correctly. After that I installed SlimICS. But I dont like it as much as i thought i would and now when i try to reinstall teamhacksung ROM, it errors out during the beggining of the installation. The MD5 is still fine. I dont think it likes the version of CWM recovery that SlimICS installed. I know CWMR went to an older version when i went from teamhacksung to SlimICS.
Flash glitch kernel first. Also, don't use the builds from that thread, it is old. Just flash the latest CM9 nightly
Swyped from my ICS Samsung Captivate
Stuck in A boot loop after flashing paranoid rom to cappy i897
I downloaded all needed files to internal SD just as the (how to upgrade the captivate i897 to Paranoid ROM said to do )
wipe data factory reset,wipe cache,selected install zip zip>package (pa_captivatemtd-1.99-13AUGUST2012.zip, md5sum: cc03bacf0f07a94bf25b482d64b94e63) then it started boot looping / att screen twice then android guy ,, then falling over with exclamation point in the middle of him , let it go considering options of 3 button combo weren't working ,, beside guide said 5-10 min to install then it made it to devil kernel installed gapps >> (gapps-jb-20120726-signed.zip, md5sum: f62cfe4a827202899919fd932d5246d7) now back in the boot loop again>>
i did make a nandroid backup but cant seem to get into cwm recovery or download mode . I did follow that guide to a tee.
any help or suggestions on this i would greatly appreciated if this post in wrong spot sry im new.
Also stuck in bootloop reverting to Gingerbread
I am also stuck in boot loop after attempting to restore back into Gingerbread.
Here's how I got in this mess: I had been running Gingerbread on my Captivate for several months (rooted). I decided it was time to try upgrading to Jelly Bean (cm9 version). I installed ClockworkMod Recovery and that appeared to be working, so I made a NANDroid and proceeded to install CyanogenMod on my phone.
It booted OK, but I didn't like it and figured I'd just revert by restoring my NANDroid. Only thing is, it didn't restore correctly and my phone was stuck at the initial AT&T "bars" screen.
So I attempted to reboot in recovery and restore my latest update.zip. This did not seem to help at all. My phone would just boot to the AT&T screen and be stuck there. I checked to see adb was reachable behind the scenes but it wasn't.
After that I loaded Odin 1.85, downloaded a copy of the stock Captivate ROM, unzipped it and loaded it to my ROM (using the method described in this link I'm not allowed to show you because I'm a new user), more or less.
Odin said it was successful, but the phone is now still stuck in a boot loop. The ClockworkMod Recovery options are gone from the recovery menu. Now it looks like my stock recovery menu. There are some diagnostics on the recovery screen:
-- Copying media files --
E: failed to mount /dbdata (Invalid argument)
E: copy_dbdata_media: Can't mont /dbdata
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Applied CSC-code 'ATT'
Successfully copied multi-CSC.
-----
the bold text indicating errors appears in orange.
I tried "wipe data/factory reset" and "wipe cache partition" and rebooting. This had no apparent effect. The Captivate still continues to loop on reboot.
What next? It seems like it's missing something it needs to boot that's not in the standard Gingerbread Captivate image I downloaded with Odin. What else do I need to do? Keep in mind that right now the only way I can get files onto the phone is Odin (or similar) via the USB port. The phone never gets booted enough to get to it with adb, let alone mounting as a drive on my computer.
Thanks
Reply Back.
HG_User said:
I am also stuck in boot loop after attempting to restore back into Gingerbread.
Here's how I got in this mess: I had been running Gingerbread on my Captivate for several months (rooted). I decided it was time to try upgrading to Jelly Bean (cm9 version). I installed ClockworkMod Recovery and that appeared to be working, so I made a NANDroid and proceeded to install CyanogenMod on my phone.
It booted OK, but I didn't like it and figured I'd just revert by restoring my NANDroid. Only thing is, it didn't restore correctly and my phone was stuck at the initial AT&T "bars" screen.
So I attempted to reboot in recovery and restore my latest update.zip. This did not seem to help at all. My phone would just boot to the AT&T screen and be stuck there. I checked to see adb was reachable behind the scenes but it wasn't.
After that I loaded Odin 1.85, downloaded a copy of the stock Captivate ROM, unzipped it and loaded it to my ROM (using the method described in this link I'm not allowed to show you because I'm a new user), more or less.
Odin said it was successful, but the phone is now still stuck in a boot loop. The ClockworkMod Recovery options are gone from the recovery menu. Now it looks like my stock recovery menu. There are some diagnostics on the recovery screen:
-- Copying media files --
E: failed to mount /dbdata (Invalid argument)
E: copy_dbdata_media: Can't mont /dbdata
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Applied CSC-code 'ATT'
Successfully copied multi-CSC.
-----
the bold text indicating errors appears in orange.
I tried "wipe data/factory reset" and "wipe cache partition" and rebooting. This had no apparent effect. The Captivate still continues to loop on reboot.
What next? It seems like it's missing something it needs to boot that's not in the standard Gingerbread Captivate image I downloaded with Odin. What else do I need to do? Keep in mind that right now the only way I can get files onto the phone is Odin (or similar) via the USB port. The phone never gets booted enough to get to it with adb, let alone mounting as a drive on my computer.
Thanks
Click to expand...
Click to collapse
While searching threw all this mess on this site and various other :
I did stumble on something that might help u get your cwm
mode Look up Captivate Q&A the scroll to T, Russel thread has file needed to get your cwm mode working using rageagaistcage method.
Odin has multi file upload for stock alone check to make sure you selected right one . then just reflash should be good
mine i examine really thoroughly and figure out i try to jump to high .
i had stock then firefly then darkfire which is based off i900 <> Cappy rom bad <>idea on my part i try to jump to paranoid rom from darkfire '
don't think files were save to SD internal card - download section instead so firmware lost track of it self .
reviewing errors made on my part order 2 jig for my 2 cappys
my plan use jig get into download flash back to stock using odin one click using kies flash to froyo and stick with it for another six months
while reading everything i need to know about flashing that high up , besides that rom will become more stable less bugs and it will give me
time to see what errors occurs with this phone model on that rom last time i check there was only 7 posted user using it
again i was trying to flash paranoid rom for Samsung captivate SGH_I897'' I hope you get your issue resolved.
If u try one click unbrick and on win xp uninstall kies the drivers will not work together log in to administrator account <> just Google it if not on welcome screen there a few ways to get into that account,, but that did work for me on my cappy . let me know how u make out. ??
---------- Post added at 06:38 PM ---------- Previous post was at 06:27 PM ----------
321321wrick said:
While searching threw all this mess on this site and various other :
I did stumble on something that might help u get your cwm
mode Look up Captivate Q&A the scroll to T, Russel thread has file needed to get your cwm mode working using rageagaistcage method.
Odin has multi file upload for stock alone check to make sure you selected right one . then just reflash should be good
mine i examine really thoroughly and figure out i try to jump to high .
i had stock then firefly then darkfire which is based off i900 <> Cappy rom bad <>idea on my part i try to jump to paranoid rom from darkfire '
don't think files were save to SD internal card - download section instead so firmware lost track of it self .
reviewing errors made on my part order 2 jig for my 2 cappys
my plan use jig get into download flash back to stock using odin one click using kies flash to froyo and stick with it for another six months
while reading everything i need to know about flashing that high up , besides that rom will become more stable less bugs and it will give me
time to see what errors occurs with this phone model on that rom last time i check there was only 7 posted user using it
again i was trying to flash paranoid rom for Samsung captivate SGH_I897'' I hope you get your issue resolved.
If u try one click unbrick and on win xp uninstall kies the drivers will not work together log in to administrator account <> just Google it if not on welcome screen there a few ways to get into that account,, but that did work for me on my cappy . let me know how u make out.
There also Ginger Bread Boot loaders Needed for it to start up Correctly - i personally don't know that much bout gingerbread rom i didn't like it as much as froyo WiFi issues'' the the stock odin should erase all info on your part thou 'e use Is OCD 1 i897UCJF6>lowercase work every time for me.
cept now because my usb is not able to charge phone or enter download mode or recovery which leaves jig option .
Click to expand...
Click to collapse
HG_User,
U can't go back to GB (or froyo/eclair) from CM, MIUI, ICS, JB, AOSP etc., etc. without using Odin or Heimdall---because of the different partitions used---Stock firmware is bml/rfs and all the AOSP etc etc are mtd/yaffs(2).
And u can only restore a backup when u r back running the base rom where u made the back up.
Use this...Stock i897ucKK4 GB 2.3.5 with or without bootloaders... http://forum.xda-developers.com/showthread.php?p=18370912
This kk4 should get u going. Then u can use Odin to flash Corn Kernel to get a cwm back...:thumbup:
Sent from my SGH-I897 using xda premium
... one step on the way: Back to Eclair
thanks for the advice. Ultimately, I decided I should use Odin 3 1-click to revert back to original (2.1 Eclair) firmware that I found on the first post of thread titled
[STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY
This is a huge step forward because it makes my phone work, but it's also a step back in time to the early Eclair days.
Now my next step is to upgrade back to Gingerbread...
Edit: Thanks to all who pointed me in the right direction. I took the phone back to Eclair then used Samsung KiesMini (twice) to get it back to Gingerbread. After re-rooting and removing the AT&T Bloatware, it works fine again. I might try upgrading again to ICS or JB, but I didn't like Cyanogen 9 at all. Maybe I'm just used to the way AT&T polishes the UI, but Cyanogen didn't appeal at all. Now looking for a relatively polished but lightweight ICS or JB version... Also, it would be nice if when I upgrade it preserves the installed apps and what's on my home screens, but that seems unlikely going from AT&T-branded Gingerbread to an independent ICS or JB.
Dear friends,
Little background. I was on CM10 stable, but decided to I update to CM10.1 M1, After the update, had no market, however, so I tried to downgrade to CM10 stable and it bricked. So .. back to stock it is! Now I am having trouble getting out of stock. I am not new to flashing, but I never had this kind of a persistent problem.
The short summary of what I get no matter what I try is: Every kernel that is not the stock Eclair kernel has boot-animation messed up (random lines of color on screen), and I cannot enter recovery - I sometimes can boot sometimes cannot.
Steps I have taken
I went back to stock Eclair rom + non-root kernel (LINK).
I rooted (LINK)
But when I tried to update kernel to allow CWM, it bricked my phone. So back to stock, again!
I tried this a few times. Now, the latest attempt, I tried the stock 2.3.5 rom + rooted, CWM kernel (LINK... I get the phone running, but I cannot get into recovery, and no utility that has "reboot to recovery" has managed to get me into recovery.
The plea
All I want is CWM, so I can install what I want. Without it, I am stuck with Odin one-click and Odin flashable packages (Heimdall does not want to work right for me - the drivers are messed up - and trying to fix those brkeas my Odin drivers).
I have no data on the phone at the moment, I can reinstall everything if need be .. but I am out of ideas besides keep trying different roms and kernels until something gives me CWM and I am free again.
I have AT&T GB bootloaders.
thanks for any help, I will try to provide any additional info I can.
dozyaustin said:
Dear friends,
Little background. I was on CM10 stable, but decided to I update to CM10.1 M1, After the update, had no market, however, so I tried to downgrade to CM10 stable and it bricked. So .. back to stock it is! Now I am having trouble getting out of stock. I am not new to flashing, but I never had this kind of a persistent problem.
The short summary of what I get no matter what I try is: Every kernel that is not the stock Eclair kernel has boot-animation messed up (random lines of color on screen), and I cannot enter recovery - I sometimes can boot sometimes cannot.
Steps I have taken
I went back to stock Eclair rom + non-root kernel (LINK).
I rooted (LINK)
But when I tried to update kernel to allow CWM, it bricked my phone. So back to stock, again!
I tried this a few times. Now, the latest attempt, I tried the stock 2.3.5 rom + rooted, CWM kernel (LINK... I get the phone running, but I cannot get into recovery, and no utility that has "reboot to recovery" has managed to get me into recovery.
The plea
All I want is CWM, so I can install what I want. Without it, I am stuck with Odin one-click and Odin flashable packages (Heimdall does not want to work right for me - the drivers are messed up - and trying to fix those brkeas my Odin drivers).
I have no data on the phone at the moment, I can reinstall everything if need be .. but I am out of ideas besides keep trying different roms and kernels until something gives me CWM and I am free again.
I have AT&T GB bootloaders.
thanks for any help, I will try to provide any additional info I can.
Click to expand...
Click to collapse
Messed up screen = wrong bootloaders. Flash Odin KK4 with bootloaders
From there, follow this link.
Finally, you can get back up on CM10.1 - Btw, you had no market cause you didn't flash their Gapps.
UPDATE .. ugh that took a while:
1) From the master list LINK, wet back to 2.1, I897UCJF6
2) From the same thread installed I897UCKF1 with bootloaders
3) rooted: LINK (I know -not XDA)
4) removed the 3e recovery lock (LINK) - this did not seem to work, but I did do it.
5) installed Speedmod kernel from here LINK - this did not boot, but it did install CWM
6) installed CM10.0 Stable from SD cadr - twice
7) installed gapps
8) just did my first boot to CM10.
This is both a record for myself for later, and for anyone else that may find this useful.
BWolf56 said:
Messed up screen = wrong bootloaders. Flash Odin KK4 with bootloaders
From there, follow this link.
Finally, you can get back up on CM10.1 - Btw, you had no market cause you didn't flash their Gapps.
Click to expand...
Click to collapse
Ooooh. I learn something new every day! Thanks.
Sent from my SGH-I897 using xda app-developers app