Help.
I have been running Frost just fine for about 24 hours now. Have rebooted a few times for media scanning reasons without incident. Just now I rebooted and am stuck in a boot loop. So I long held the power key and boot loop again. Then pulled the battery and tried again and I get the same thing. Google logo and then the frosty Team Whiskey a few times and then it vibrates and starts all over. What should I do from here. Its the first time Ive had a problem flashing and Im thinking I have to use Odin now....or can I get into recovery somehow and boot from there? ( sorry if I posted this in the wrong section. In my nervousness I posted here instead of Q&A)
edit: Read, read, and read some more. Odin-ed to stock successfully....and then did it again to be safe. Now to start the root/ flash process all over. It's almost like an addiction. This time I think I'll stick with one rom for a while.
just ODIN back to something. Learn it. Love it. It's simple.
Ok. Any way I can use my nandroid backups? If no.....would I be best to go back to stock and then to my rom of choice? or just odin to my rom of choice
GoodVibrant-ions said:
Ok. Any way I can use my nandroid backups? If no.....would I be best to go back to stock and then to my rom of choice? or just odin to my rom of choice
Click to expand...
Click to collapse
Since frost uses ext 4 for partitions, I recommend odin to jfd stock with repartition checked. it has all the fs files you would need. Then flash back to whichever rom you want. there are tutorials on how to use odin, or you can use heimdall, same thing but open source and you need to unzip the tar that the rom comes in to get the individual files inside.
wildklymr said:
Since frost uses ext 4 for partitions, I recommend odin to jfd stock with repartition checked. it has all the fs files you would need. Then flash back to whichever rom you want. there are tutorials on how to use odin, or you can use heimdall, same thing but open source and you need to unzip the tar that the rom comes in to get the individual files inside.
Click to expand...
Click to collapse
Ok...looks like I have some reading to do. I knew I was gonna have to do this sooner or later so I guess it's good I learn it now.
When you say I have to unzip the tar that the rom comes in.....does that just apply to heimdall....or heimdall and odin both?
GoodVibrant-ions said:
Ok...looks like I have some reading to do. I knew I was gonna have to do this sooner or later so I guess it's good I learn it now.
When you say I have to unzip the tar that the rom comes in.....does that just apply to heimdall....or heimdall and odin both?
Click to expand...
Click to collapse
Just heimdall. If you use odin, just load the whole tar the rom is in into the pda field.
I just odin back to Eugenes Froyo that doesn't brick w partitions set, I wonder if im doing it right, or if my phone would work better if I odin'd back to JFD stock, never had any problems though, and ive been in some bad soft bricks (e: cant mount, bootloop, etc..)
Sent from my SGH-T959 using XDA Premium App
gfropr said:
I just odin back to Eugenes Froyo that doesn't brick w partitions set, I wonder if im doing it right, or if my phone would work better if I odin'd back to JFD stock, never had any problems though, and ive been in some bad soft bricks (e: cant mount, bootloop, etc..)
Click to expand...
Click to collapse
I've heard of this also but I don't want to mess anything up worse than it already is. Would Eugenes froyo no brick be ok since I'm coming from frost?
My best advice would be odin back to stock, it's a fresh clean start, don't be intimidated, odin is very ready to use, go to the Bible and get the 512 file, JFD stock file, and Odin program. If I could do it without a hitch, you can too, it takes about 2 minutes to odin, go for it! lol
Sent from my Vibrant w/ Bionix V 1.3 and Launcher Pro Plus
negerhab said:
My best advice would be odin back to stock, it's a fresh clean start, don't be intimidated, odin is very ready to use, go to the Bible and get the 512 file, JFD stock file, and Odin program. If I could do it without a hitch, you can too, it takes about 2 minutes to odin, go for it!
Click to expand...
Click to collapse
Thanks man. I appreciate the reply.....wish I would have saw it earlier. It might have saved me a little bit of time. I am writing this from my phone after odin-ing to stock and then odin-ing to eugenes jk2 froyo. After that it was cake to flash back to bionix 1.3. You're right though....its intimidating to use odin when you have never done it but now that I have I will use it anytime I switch between roms. Plus I feel like I now have a clean install of bionix. But mainly I'm glad the panic is over and my phone is back to lightning speed operation.
Sent from my SGH-T959 using XDA App
Related
My Captivate is only about a week old. After getting it, I immediately rooted it and installed stock Froyo, but wasn't satisfied with the battery life or performance. So I installed Darky's 7.5 ROM (nowipe version using the 'wipe data + cache' option in CWM) along with the glitterball kernel and JL3 modem. Performance and stability were excellent, but battery life was abysmal, even with no apps running and the CPU capped between 100MHz and 800MHz using SetCPU (which is plenty fast on this ROM). I'm talking about 10-15% drain per hour while on standby, packet data, wifi, bluetooth, GPS, and sync all off.
I attempted to flash back to stock to try other ROM's, but Odin one-click simply bricked my phone to the point where I needed a hardware jig. After much work, I was able to flash Cognition using the regular Odin and then use CWM to restore my phone back to the Darky's ROM state with all my data and apps intact. Battery life is still terrible though. I've tried several methods to revert my phone to a stock kernel, including Odin one-click, Odin with 3-button fix, and regular Odin loading various stock ROM PDA and PIT files.
The furthest I was able to get was a phone with a working recovery menu that gave me 'Kernel Panic' right after the AT&T logo. Otherwise, the phone would be completely bricked (no button combinations) and I'd have to reset it using the jig. However, flashing a custom ROM that *doesn't* require reverting to stock first (Odin-flashable), or restoring a backup from CWM works just fine every time, no matter how badly I brick the phone. It's just stock ROM's and kernels that I can't get to boot or install properly.
I'm running out of ideas, because this battery drain is unacceptable and my ROM choices are severely limited. I did try flashing some ROM's over Darky's (JPY) without the revert-to-stock step, but I always get weird problems like missing phone, message and contacts apps.
I would really appreciate it if someone could help me out.
You need to get your odin issues worked out. They are abnormal. One I would try to delete the prism then re download. Two please list steps your are following to flag with odin, hopefully it is an ready oversight someone xan point out to you.
Sent from my SGH-I897 using XDA App
mcord11758 said:
You need to get your odin issues worked out. They are abnormal. One I would try to delete the prism then re download. Two please list steps your are following to flag with odin, hopefully it is an ready oversight someone xan point out to you.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
I have re-downloaded both Odin and the files to flash multiple times, confirmed by the '(1)' tacked onto the filenames in my download folders. My procedure:
1. Extract Odin and PIT file (if flashing with a PIT).
2. Run Odin as Administrator, select PDA tar/md5 file (and PIT file if applicable). Untick 'Auto Reboot'.
3. Put phone into download mode using volume button combo (or hardware jig if Odin already bricked my phone).
4. Plug phone in. Phone recognized immediately by Windows and Odin.
5. Click start in Odin. Procedure always completes successfully.
6. Battery pull and unplug phone. Put battery back in and turn phone on. If flashing a stock ROM, phone either gets kernel panic, or is bricked and all button combos are disabled.
The files I used for stock flashing were found in the Odin one-click + master clear thread and the Odin one-click button combo fix thread (which uses a PIT and PDA file). I used Odin 3 v1.0 when flashing PDA files (had no problems flashing cognition ROM or non-stock kernels).
For the one-click versions, I followed the above procedure (minus the selection of PDA/PIT files). One-click always bricks, regular Odin will either brick or cause kernel panic when flashing a stock ROM or kernel, depending on PDA/PIT files and the previous state of the phone.
When you run odin one click, were do things appear to go wrong
Sent from my SGH-I897 using XDA App
mcord11758 said:
When you run odin one click, were do things appear to go wrong
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
There's no sign of anything going wrong until the phone auto-reboots (since you can't disable that in one-click). Upon rebooting, the phone just loops the AT&T logo, requiring a battery pull. Button combinations do not work and the battery charge icon (when the phone is off) freezes when the phone is plugged in.
GGXtreme said:
There's no sign of anything going wrong until the phone auto-reboots (since you can't disable that in one-click). Upon rebooting, the phone just loops the AT&T logo, requiring a battery pull. Button combinations do not work and the battery charge icon (when the phone is off) freezes when the phone is plugged in.
Click to expand...
Click to collapse
are you at&t our rogers? What us the name if the odin file you are using/
Sent from my SGH-I897 using XDA App
mcord11758 said:
are you at&t our rogers? What us the name if the odin file you are using/
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
I'm on AT&T. Odin files I've tried include:
Odin3 v1.3.exe (bundled with Odin3.ini and s1_odin_20100803.pit)
Odin3_v1.0.exe (bundled with PIT.pit and used with PDA.tar)
Odin.exe (bundled with PIT.pit and PDA.tar for Cognition)
I897UCJF6-final-OCD-REV0.exe
All of the Odin executables (with the exception of the one-click) work fine flashing Cognition and I9000_reoriented_v2.3.0.tar (xcalib kernel), but not with the included PDA.tar files. When I say 'work fine', I mean flash the phone into a workable, non-bricked state, since Odin never throws me any errors or failures.
*bump*
Is this hopeless? I've asked about this elsewhere, and no one seems to have any suggestions. My phone has been up and running fine on multiple different custom ROM's and kernels, but it still bugs me that I can't flash back to stock if needed. Also, any suggestions on improving battery life are very welcome.
After searching around for a bit, it seems that Captivates from batches 1008 to 1010 cannot be flashed back to JF6 using any version of Odin. The closest that can be achieved is JH3 using Odin 1.7. This is pretty disappointing.
Oh well, I guess I have no luck with technology. Unless anyone feels like throwing battery life suggestions at me, this thread can be closed/deleted I guess.
The battery probably just needs calibrating.
There are.multiple threads in the forum on this and I would be happy to point.you to them, bit.I am on the phone app and its a little more.difficult to do so.
Sent from my GT-I9000 using XDA App
Search development thread for I897UCJH7 - OTA by designgears. Close enough to JF6.
Sent from a phone somewhere in the universe
http://forum.xda-developers.com/showthread.php?t=731989 <-- this is what I use to go back to stock before every re-flash. Never had an issue.
Build 1008 phone - hobbling along with random reboots etc.. and no buttons working.
I wouldn't suggest using anything else to flash back to stock. Then flash your new ROM as usual. You do NOT need to do a "stock" 2.2 froyo ROM first before installing any custom ROM.
The simple way to flash correctly to a new ROM
Use Odin 1 Click I897UCJF6 back to Stock.
Root your Phone (Or if you kept the Update.zip from CWM you can fore go all of this )
Download ROM Manager - update Busybox
Put the ROM you wish to use on your SDCard
Go into CWM and flash as normal following the dev/cooks instructions.
cappysw10 said:
Search development thread for I897UCJH7 - OTA by designgears. Close enough to JF6.
Sent from a phone somewhere in the universe
Click to expand...
Click to collapse
Thanks. I eventually figured out the JH2 to JH7 trick. It seems I can't properly flash any ROM below JH3 using any version of Odin.
avgjoegeek said:
http://forum.xda-developers.com/showthread.php?t=731989 <-- this is what I use to go back to stock before every re-flash. Never had an issue.
Build 1008 phone - hobbling along with random reboots etc.. and no buttons working.
I wouldn't suggest using anything else to flash back to stock. Then flash your new ROM as usual. You do NOT need to do a "stock" 2.2 froyo ROM first before installing any custom ROM.
The simple way to flash correctly to a new ROM
Use Odin 1 Click I897UCJF6 back to Stock.
Root your Phone (Or if you kept the Update.zip from CWM you can fore go all of this )
Download ROM Manager - update Busybox
Put the ROM you wish to use on your SDCard
Go into CWM and flash as normal following the dev/cooks instructions.
Click to expand...
Click to collapse
That is what I've always been trying. Attempting to flash anything below JH3 with any version of Odin (one-click or regular with PDA/PIT files) ALWAYS bricks my phone and requires a jig, 100% of the time, using any computer. Flashing a newer/custom ROM works fine.
GGXtreme said:
Thanks. I eventually figured out the JH2 to JH7 trick. It seems I can't properly flash any ROM below JH3 using any version of Odin.
That is what I've always been trying. Attempting to flash anything below JH3 with any version of Odin (one-click or regular with PDA/PIT files) ALWAYS bricks my phone and requires a jig, 100% of the time, using any computer. Flashing a newer/custom ROM works fine.
Click to expand...
Click to collapse
intriguing the somewhat random button combo issues on some newer builds of phone
newter55 said:
intriguing the somewhat random button combo issues on some newer builds of phone
Click to expand...
Click to collapse
I can't remember if it did, but I think the actual issue is that my phone came with JH7 (not JF6) and is actually incapable of running older firmware due to some difference in the hardware/build. That's why flashing stock JH7 seems to work fine.
I messed up my Bell SGS playing with odin.
Lost the 3 button options and ended up hacking a jig to get it into DL mode. done
Goal - a Functioning phone. Now what?
Thinking I should odin the I9000M_JL2_JL2_JL2_JL2_UG_BMC.tar.
But with or without repartition?
Can I use any 512pit?
I think repartitioning is where i messed it up.
Now all of this happened because I wanted seeARMS.JL2.v0.4 but couldn't update with the <3e> recovery mode.
Knowing that seeArms is my second (first?) goal, is there a different firmware I should flash something other than BMC to give me back update functions, but stable to resuscitate my phone?
There's ages of material here and I don't want brick my phone or waste time, I've done enough of that by myself.. now I'm looking for some expert opinion.
thanks
Best option for bell users is darkys rom. For further info check darky's rom info
Lyon huntington said:
I messed up my Bell SGS playing with odin.
Lost the 3 button options and ended up hacking a jig to get it into DL mode. done
Goal - a Functioning phone. Now what?
Thinking I should odin the I9000M_JL2_JL2_JL2_JL2_UG_BMC.tar.
But with or without repartition?
Can I use any 512pit?
I think repartitioning is where i messed it up.
Now all of this happened because I wanted seeARMS.JL2.v0.4 but couldn't update with the <3e> recovery mode.
Knowing that seeArms is my second (first?) goal, is there a different firmware I should flash something other than BMC to give me back update functions, but stable to resuscitate my phone?
There's ages of material here and I don't want brick my phone or waste time, I've done enough of that by myself.. now I'm looking for some expert opinion.
thanks
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA App
Lyon huntington said:
I messed up my Bell SGS playing with odin.
Lost the 3 button options and ended up hacking a jig to get it into DL mode. done
Goal - a Functioning phone. Now what?
Thinking I should odin the I9000M_JL2_JL2_JL2_JL2_UG_BMC.tar.
But with or without repartition?
Can I use any 512pit?
I think repartitioning is where i messed it up.
Now all of this happened because I wanted seeARMS.JL2.v0.4 but couldn't update with the recovery mode.
Knowing that seeArms is my second (first?) goal, is there a different firmware I should flash something other than BMC to give me back update functions, but stable to resuscitate my phone?
There's ages of material here and I don't want brick my phone or waste time, I've done enough of that by myself.. now I'm looking for some expert opinion.
thanks
Click to expand...
Click to collapse
Flash the stock JL2 firmware with Odin the use super one click to root your phone then flash a new kernel with SGS Kernal flasher from the market... then u will have clockwork recovery then wipe and flash seeArms! Its a great rom but not as fast as darkys
Get the stock firmware from samfirmware.com u can get the .pit file from there to
Sent from my bell GT-I9000m using XDA App
repartition yes? .pit universal?
Jason123420 said:
Flash the stock JL2 firmware with Odin the use super one click to root your phone then flash a new kernel with SGS Kernal flasher from the market... then u will have clockwork recovery then wipe and flash seeArms! Its a great rom but not as fast as darkys
Get the stock firmware from samfirmware.com u can get the .pit file from there to
Sent from my bell GT-I9000m using XDA App
Click to expand...
Click to collapse
So the stock JL2 that I have is a .tar and .dll
I have a 512.pit from a beta 2.2 , are they different?
Did I mention boot problems too? Hanging @ Samsung, no splash ani.
I guess the .pit means yes on repartition?
Thanks
Just use the stock firmware and .pit from samfirmware.com and when Odin is open do not tick off repartirion... just put the .pit in it's spot and the tar in th's PDA part and flash
Sent from my GT-I9000 using XDA App
Now I'm no pro... I just flashed a rom once and got stuck in a boot loop and this is what worked for me
Sent from my GT-I9000 using XDA App
Recovery back but can't mount /dev/block/stl10
Decided to try Darkys v9.2 Resurrection.. no go.
Flashed JL2 and got recovery back but crash after animation.
3e recovery shows me Can't mount /dev/block/stl10.
some threads say dead, others make ref. to old builds.
any current ideas?
thanks
Sorry man like I said I'm no pro... ide flash stock jl2 back and send it back to Samsung for repair maybe they will do something for your warranty
Sent from my GT-I9000 using XDA App
Lyon huntington said:
Decided to try Darkys v9.2 Resurrection.. no go.
Flashed JL2 and got recovery back but crash after animation.
3e recovery shows me Can't mount /dev/block/stl10.
some threads say dead, others make ref. to old builds.
any current ideas?
thanks
Click to expand...
Click to collapse
Download a full firmware for your model and locale (with dbdata in it) and flash it with repartition with the pit proposed (samfirmware.com) then, I believe, you will have a full functioning phone. If everything is ok, then flash ... whatever.
It's Alive! - Can't mount /dev/block/stl10 fixed.
Hey All,
Got it all working again.
Repaired: Can't mount /dev/block/stl10
the fix: A full firmware (pda/csc/phone/pit) flash w/repartition.
Flashed w/repartition - I9000XXJP2.7p. (the only FULL firmware I had on-hand)
on reboot the system does a media check and was successful in reformatting and mounting the internal SD.
Phone didn't like the ROM and still logo of death, but..
A quick Jig into Download Mode..
Flashed I9000UGJL2_homebinary_add_param.tar with no repartition
(can't remember if I used .pit).
And Success!! my phone is alive and running 2.2
Thanks for the help, and hopefully this thread can help others.
Everyone should build/get a jig
There is nothing more awesome than being able to force download your non-booting phone.
I could not have done this repair without one.
http://forum.xda-developers.com/showthread.php?t=819551.
The only problem now is it's back to stock...
oh phone, how can I crash you next?
thanks again everybody!
tsinc said:
Download a full firmware for your model and locale (with dbdata in it) and flash it with repartition with the pit proposed (samfirmware.com) then, I believe, you will have a full functioning phone. If everything is ok, then flash ... whatever.
Click to expand...
Click to collapse
Yes, do this. For repartition to work the .tar has to have dbdata.rfs, otherwise it won't work.
Then flash a speedmod kernel with odin for root/cwm and flash you're favourite custom rom
unlock&root owngrade or speedmod kernel? suggestions?
Forgot to mention that all this started after I got the phone back from Bell service after SD card failure.
I know mod methods changed with the latest firmware, as I had used the update.zip method that is now unavailable.
My phone went in unlocked and rooted
the phone came back re-locked (old code doesn't work? wtf?),
and it was unrooted w/3e recovery
Can the phone unlock code change?
Will downgrading to 2.1 make unlocking easier?
or is unlocking just as simple after a speedmod kernel with odin for root/cwm
Which is better?
downgrade the firmware to 2.1 and root using the old update.zip method or speedmod kernel?
Which kernel? (link please )
cheers
Lyon huntington said:
Hey All,
Got it all working again.
Repaired: Can't mount /dev/block/stl10
the fix: A full firmware (pda/csc/phone/pit) flash w/repartition.
Flashed w/repartition - I9000XXJP2.7p. (the only FULL firmware I had on-hand)
on reboot the system does a media check and was successful in reformatting and mounting the internal SD.
Phone didn't like the ROM and still logo of death, but..
A quick Jig into Download Mode..
Flashed I9000UGJL2_homebinary_add_param.tar with no repartition
(can't remember if I used .pit).
And Success!! my phone is alive and running 2.2
Thanks for the help, and hopefully this thread can help others.
Everyone should build/get a jig
There is nothing more awesome than being able to force download your non-booting phone.
I could not have done this repair without one.
http://forum.xda-developers.com/showthread.php?t=819551.
The only problem now is it's back to stock...
oh phone, how can I crash you next?
thanks again everybody!
Click to expand...
Click to collapse
All you did was flash UGJL2 with no repartition and it brought your phone back?
Kops said:
All you did was flash UGJL2 with no repartition and it brought your phone back?
Click to expand...
Click to collapse
You know what....I've been trying various combinations of CSC/MODEM/PIT and everything to get this phone running again.
All I did was select a FULL UGJL2, and thats IT. NO pit, NO repartition, and it worked
The best way to revive your I9000m is to first flash JPC (a three file ROM) with 512 PIT and repartition ticked. The phone will still be in a boot loop. Then flash the JL2 PDA without repartition or PIT. The best way to go back to stock! Has always worked for me. I9000m's are not the same as other I9000's and do not flash repartition and the PDA in the same flash! Good luck!
So, just switched out my captivate because my warranty was still in effect. Rooted etc etc. But I remember installing CWM with rom manager to begin flashing my first rom back in the day.
But anywho, I have installed ROM Manager, clicked to flash CWM but when I go into recovery (vol + - & Power) All I get is the samsung one. (Blue text) and I only have the options to reboot, install packages, clear cache or wipe sd card.
Can anyone offer any advice?
^ Try reinstall packages. U may have to do it twice.
Gotta install the update.zip with install packages but you have signed bootloaders if you're on stock froyo. Odin to 2.1 and install cwm from there. You can find the update.zip for cwm on the cappy forums and just put that on the root of your internal memory to avoid using rom manager. Don't even have to root to flash.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Hmmmm do you have the stock odin pit file/pda or is the old school odin where you couldnt even do that shoot you right back to 2.1?
^ If u want to go back to Stock Eclair...use the first link in my signature below.
I typically use Odin jf6 one click rev0 from designgears. Its still on the forums I believe but might be dead link. Just make sure it has the pbl and sbl. If you are worried I can upload the one I have used for the past 9 months without fail( but ffailure is always possible, just be sure to follow directions and you should be alright. ) alternatively there is a guide to get to stock jh7 on the forums using the Odin that you have to manually select files for. Should be an easy search. I believe people consider this safer for the newer builds but I used oneclick on my 1010 tons of times and have used it once on my 1012 no problems.
Sorry for the long post hope I helped
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
You all have helped. Thank you so much. Running MiUi again and still loving it.
so my dilemma is as follows.. i was running continuum 4.1 on my captivate. i decided i wanted to try one of the new gingerbread roms, so my first step was to use odinoneclick 1.0 to get to complete stock and go from there. my luck, odin froze on me at sbl.bin... so i am soft bricked but i can use the vol up/down plug usb method to get to download mode. because i have only used one click before, and not a full odin like 1.7, i am having trouble figuring out exactly what i need, and what steps are necessary to safely get me back to stock using odin 1.7 so i can then load GB bootloaders and stop messing with BL's from now on.. so i suppose my main question is should i first flash eclair before trying to flash GB bootloaders/rom? my other question being, if so, what files do i need, and do i need to place a pit file and repartition? sorry if this is a noob question, i just dont want to screw it up any further and wasnt sure if specific steps must be taken when you are soft bricked.. thanks very much in advance!
No need to flash Eclair. Just flash the KF1 file in this post and then XCal's reorient for GB and you'll be good to go. Just don't boot into the OS after flashing XCal's kernel else you'll get bootloops since it was designed for I9000 based ROMs rather then I897. Just reboot back into recovery after flashign XCal's Kernel and then flash whatever GB ROM you want.
http://forum.xda-developers.com/showthread.php?t=1126704
I personally prefer to flash my phone using Heimdall on my laptop running Kubuntu as it's generally more stable/successful, and it's easier to choose which files you want to flash if you only want to flash specific files (Like the bootloaders).
Also KH3 is out and it looks like it might have updated bootloaders, but it's not a full ROM from what I was able to grab. It's missing the param.lfs, dbdata.rfs, and the pit file. Also has an added SS_DL.dll which I'm not sure what the purpose of that file is since it's a Windows file...
http://forum.xda-developers.com/showthread.php?t=1232703
Moved to Q&A.....
NO QUESTIONS IN DEVELOPMENT PLEASE!!!!!
conantroutman said:
Moved to Q&A.....
NO QUESTIONS IN DEVELOPMENT PLEASE!!!!!
Click to expand...
Click to collapse
my apologies! my intention was to post in q&a but i was at work sneaking on the pc i must have been clicking too fast..
and kyuta... thank you for the suggestion! so is it safe to just use the whole odin package in the link you provided just to get a clean install, and then move on to a rom/kernel of choice at a later time?
im getting a big red FAIL on every attempt at flashing KF1 file with odin 1.3 and 1.7 im not sure which route to take at this point. do i need to flash the pit file with the bootloaders?
dartdc97 said:
im getting a big red FAIL on every attempt at flashing KF1 file with odin 1.3 and 1.7 im not sure which route to take at this point. do i need to flash the pit file with the bootloaders?
Click to expand...
Click to collapse
just make sure u hav right file downloaded...and right click on odin and click run as administrator...try changing the usb ports....and try changing the usb cable...and see if u hav proper driver installed ....
check all these which i hav mentioned...
then u shd be able to go back to either eclair(jf6) or gingerbread(kf1) stock
killer_raj said:
just make sure u hav right file downloaded...and right click on odin and click run as administrator...try changing the usb ports....and try changing the usb cable...and see if u hav proper driver installed ....
check all these which i hav mentioned...
then u shd be able to go back to either eclair(jf6) or gingerbread(kf1) stock
Click to expand...
Click to collapse
Just to add this this: Try using XP service pack 2 mode if you are using Windows 7 x 64.
I was on Slim ICS and downloaded an update (2.8) which was to include a wifi toggle fix. After downloading directly to my phone, I tried to install it and it started looping (kernel then into recovery). I could not stop it in recovery. It would loop through the boot up and then I could see the recovery and but it said something about not being able to read zip file (corrupted download?). It just kept looping.
I was able to get Odin to work once (that is why I get the AT&T screen). Now, I can get Odin to recognize my phone but I cannot get beyond that. I have tried to reflash kernels that have worked before (assuming that I needed to start over). But Odin just sits there with the tar file in the pda section (for well over five minutes). Working on a Windows 7 machine (64-bit).
My phone's current status is that it is frozen at the AT&T screen (from the boog kernel without bootloaders - since I was on gingerbread before). I can get into download (volume buttons, plug in USB).
FYI, in the past I had flashed Continuum, Andromeda3, Mosaic IX, Fusion ICS, and Slim ICS, without a problem other than a soft brick or two that I was able to fix using Heimdall. (I am realizing I know/knew enough to be dangerous)
Am I "bricked" or can it be repaired.
Any direction as to what to do right now would be greatly appreciated.
Since I have yet to start playing with ICS this is just a guess on my part.
Since you are experiencing looping issues maybe you should go back to stock (without bootloaders). Flash one of the Odin/Heimdall one clicks so that your phone will get repartitioned back to RFS.
If that gets you working again you can reinstall SlimICS from that point.
Red_81 said:
Since I have yet to start playing with ICS this is just a guess on my part.
Since you are experiencing looping issues maybe you should go back to stock (without bootloaders). Flash one of the Odin/Heimdall one clicks so that your phone will get repartitioned back to RFS.
If that gets you working again you can reinstall SlimICS from that point.
Click to expand...
Click to collapse
I will try it again but I did try once with Odin and after about ten minutes, I cancelled the process (hopefully that did not add to my problems). It seemed to be hung up on the message, "Do Not Turn Target Off," but there was no process started.
Try a heimdall one click then. It might solve the issue.
Red_81 said:
Try a heimdall one click then. It might solve the issue.
Click to expand...
Click to collapse
Red_81,
Thank you!
Heimdall worked (http://forum.xda-developers.com/showthread.php?t=1300843)! Although I loaded the version that contains bootloaders, it actually flashes the kernel first and then give you the opportunity to flash again installing the bootloaders. Since the phone worked after the first flash, I did not bother doing a second flash. Now, back to Slim ICS!
Glad I could help. I had to sit down and read some info on SlimICS. I found through a couple of threads that one of the developer's post mentions a bootloop and going back to stock.
Heimdall packages tend to include the bootloaders, but only if you flash the second time and enable that option. According to the creator, it is much safer to flash them after flashing the ROM rather than flashing them first like Odin does.
Red_81 said:
Glad I could help. I had to sit down and read some info on SlimICS. I found through a couple of threads that one of the developer's post mentions a bootloop and going back to stock.
Heimdall packages tend to include the bootloaders, but only if you flash the second time and enable that option. According to the creator, it is much safer to flash them after flashing the ROM rather than flashing them first like Odin does.
Click to expand...
Click to collapse
Heimdall worked but I was left with two problems. One was that the Kernel installed by Heimdall did not have CWM in it, which I need to flash Slim ICS.
The second problem is that my computer will not recognize my device when I try to use Odin since Heimdall installs different drivers (I have read about how to covert to Odin and/or uninstall/replace the drivers, but it is hard to find that time given family and job obligations).
Since Heimdall did work to fix my original problem work, I found a package to install Apex 12.4 (http://apex.merseine.us/installation/) on my phone. I did this so I can have a working copy of CWM in order to re-flash Slim ICS.
Given the travails of the last two days, I may wait a battery charge or two on Apex (lots of customization but higher battery drain, which is why I went from Fusion ICS to Slim in the first place).
Anyway, thanks again for your help.
I know the feeling with family and job. You could try a different usb port and it may recognize. Using odin to add another cwm injected kernel is by far the easiest way. Of course, if you could find a ROM in the One Clicks master collection that was a heimdall with CWM already in it then you wouldn't have to worry about getting odin working again right away.
Red_81 said:
I know the feeling with family and job. You could try a different usb port and it may recognize. Using odin to add another cwm injected kernel is by far the easiest way. Of course, if you could find a ROM in the One Clicks master collection that was a heimdall with CWM already in it then you wouldn't have to worry about getting odin working again right away.
Click to expand...
Click to collapse
Believe me, I tried seven ports on three different computers with two different cords (my Kindle cord is actually the most dependable ).
I then searched for a Heimdall package that had CWM. It has a Talon kernel with CWM 3.0.x and I can get into recovery with the option of installing from my internal sd card.
I just have to wait for my nerves to settle (and this is a very fash gb rom and I have had no issues yet).