having a wierd problem, as the title says i am unalbe to change roms and have it boot.ever since i flashed the ROGERS 2.3.3 (containing i896 ROGERS bootloaders)
no big surprise i didnt like it.
while reading this keep in mind i have alot of experience flashing, and yes lagfix was disabled!
odin flashed a CWM kernel (one was using before rogers)
restored Nandroid. (of before ROGERS)
stuck at kernel screen
Flashed different kernel compatible with rom.
stuck at kernel screen
Loaded CWM to flash a custom rom.zip
flashed OK
reboot stuck at kernel screen
Odin flashed i9000 gingerbread (with i9000 GB bootloaders) from few months ago
stuck at kernel
Odin flashed ROGERS 2.1 eclair stock.
stuck at kernel
Odin flashed ATT one click
SUCCESS!!
Odin flahsed Rogers 2.1 eclair
SUCCESS!!
ODIN flashed i897 ATT GB bootloaders
ODIN flashed CWM kernel CWM flash ROM
Restore NANDROID
SUCCESS!!
finally back to normal...**never flashing rogers 2,3,3 again!
or so i thought.
got bored and went to flash a different ROM
STUCK AT KERNEL
had to repeat all above steps!! ALL before it was back to *normal* again
any thoughts to what got permanently messed up????
Did you try reformatting system and cache before flashing a new ROM in cwm? (i'm just guessing here)
yes and the Odin one click re-partitions - wiping everything known.but still the problem exists after flashing my 1st custom rom i am unable to boot into a second ANY rom (stock or custom)
and this is VERY frustrating as i just finnished my own custom ROM and am unable to quickly flash test versions.!!
I don't know. Odin one click should have fixed everything. Did you master clear/reformat the internal Sd?
no not the internal sd.
also i remembered at one point right after being on ROGERS stock 2.3.3
the first rom i tried flashing was a custom build I made with a kitchen tool using cygwin.
anyways after flashing and failing, i noticed the update script i created flashed the zimage to 2 different dev/bml blocks!! one i never seen before.
i stopped using that kitchen tool but is it possible it flashed something to a dev block that odin one click isnt clearing? but it repartitions. that should clear EVERYTHING!
still my problem presists...
flashing issues. cracked screen. might be time to buy a new phone.....
You could use Heimdall to dump your partitions and find out.
Heimdall print-pit...in case u didn't know
Sent from my SGH-I897 using xda premium
Related
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!
How did I permabrick my cappy?
Flashing with Odin, I restored to the Rogers stock 2.1 firmware, however the phone refused to boot past the rogers loading screen. I re flashed the phone a few more times playing with the flashing options of Odin, using alternate stock .tar files with no luck. My final flash caused the phone to get into such a state that going into download mode no longer worked, as well as it failing to boot. Luckily Rogers warranty has replaced the phone for me
Any ideas on what caused the phone from booting into the OS, so I don't do it again?
Additional Questions
1. The new cappy given to me through the Roger's warranty has stock 2.2 loaded on it. Is there anyway to back up this firmware to a tar file for later use? If so, how can I use it in conjunction with Odin to restore to stock 2.2?
2. Do I HAVE to restore the phone to 2.1 eclaire firmware before loading a custom ROM on it? Or is it possible to root / reboot into clockwork recovery and successfully flash from stock 2.2 froyo?
3. In my past experiences, after restoring to Rogers 2.1 stock firmware through Odin, kies no longer recognizes the firmware currently loaded on my device... Is this normal? Any fixes? Is there anyway to get kies to recognize the firmware such that it would be able to upgrade or even wipe the phone with the standard stock firmware? I ask this because on the new kies I see the function "emergency firmware recovery".
did you brick flashing the NEW stock 2.1 thats in my sig? or the old one that messed alot of people up in a few ways?
#1 yes but unsure how to make, it would be used like any other tar and odin.
#2 from what ive seen sofar, 2.1 wont boot on phones that came with 2.2, but it was a noob i was talking to that had the issue. the only thing you run into is having 3e recovery and needing the fix before you can load clockwork on 2.2. all is good from there.
#3 normal. no fix. keis sucks
Trusselo said:
did you brick flashing the NEW stock 2.1 thats in my sig? or the old one that messed alot of people up in a few ways?
Click to expand...
Click to collapse
Yeah it was from the one in your sig (linked in the stickies I believe).
#2 from what ive seen sofar, 2.1 wont boot on phones that came with 2.2, but it was a noob i was talking to that had the issue. the only thing you run into is having 3e recovery and needing the fix before you can load clockwork on 2.2. all is good from there.
Click to expand...
Click to collapse
Thanks for the link! and the prompt response
Are there any .tar files floating around for the Rogers froyo 2.2 that address the warranty / logo issues? (search function seems to be broken).
Any stock 2.2 rogers .tar files for use with Odin floating around the board?
What is your recommendation with regards to proceeding with flashing? Should I try to flash 2.1 on the phone with 2.2 preloaded, or just go the 3e clockwork recovery fix route?
Any other pieces of reading you might be able to point me towards in this regard?
I would suggest adding your locale to your profile for future reference, as restoring an I896 is different than an I897.
There is also another way to get clockwork on your phone.
Use Odin and just flash the speedmod kernel .tar from here: http://forum.xda-developers.com/showthread.php?t=893880
I have done it this way since I got my phone and have yet to run into a problem. This works with 2.2 only.
2.2 odin flashable (NO ATT boot fix) and cwm upgrade from 2.1 zip. are here
http://forum.xda-developers.com/showthread.php?t=905042
the person i mentioned before that couldnt get my 2.1 stock to boot on his 2.2 ... he did fix the att boot by un-successfully flashing my 2.1 then the 2.2 overtop, then it booted correctly WITH the i896 bootscreen, basically double flash.
i will contact the creator of the updated 2.1 and see if he can do it to 2.2 as well.
feel free to attempt to flash 2.1 to confirm weather or not it does work on a phone that comes with 2.2. as this isnt confirmed. also note any new notes on the 2.1 stock rom page.
oh and speaking of the updates on that page...
theres the fix for the getting stuck at rogers bootscreen on first boot after flash... (the problem you had)
reboot into recovery and clear data and cache, reboot. done.
sorry its late...
Trusselo said:
oh and speaking of the updates on that page...
theres the fix for the getting stuck at rogers bootscreen on first boot after flash... (the problem you had)
reboot into recovery and clear data and cache, reboot. done.
sorry its late...
Click to expand...
Click to collapse
That's common. Everytime I flash the gf's Galaxy Spica, that's the first thing you have to do with it is clear the data and cache. I just do it instinctively now.
Hi,
This is my first time experimenting with flashing custom roms. I was trying to flash a custom rom onto my perfectly working newly rooted sgs (using odin), but the first rom i tried has gotten my phone to boot loop and now I don't know what to do with it. I can get to the download screen just fine and recovery mode but don't knwo what to do. Please help, I really can't afford a new phone/ don't know if samsung will let me replace it now.
Oh, the rom was the XXJVK Gingerbread which is near the top of the forums right now, if that helps at all.
I really just need my phone to be usable, I didn't expect to mess it up. Thanks again to anyone with information.
I assume you were running jl2. The problem might be because of bootloader issue.
When you were flashing gingerbread did you use pit file and repartition?
I am not a pro but If you download JL2 and flash it, should be good to go. Try not to repartition and flash without using pit file.
I did use the .pit and repartition. I'm guessing this was a no no? I'll look for jl2 and try flashing that. Might you direct me to the right download?
http://www.multiupload.com/6GRS1OWRJW
I have no idea if it will work or not. Same thing happened to me also when I was trying to flash darkys rom and I was able to open the phone after I flashed with bells original rom. Give it a try. If its a boot loop I assume its a firmware problem. You should be able to fix it. The problem might be the repartirion and pit file. I am not sure about it. Hope this helps.
Just try flashing again with boot loader update ticked in odin. I'm pretty sure that repartition and pit do nothing to the bootloader. If that doesn't work I'll add more after I shower, I stink!
Sent from my GT - I9000 running Darky's 9.5 w/ DamianGTO's Ultimate Kernel using XDA Premium App.
A bootloop = ****ed framework and/or /system/ (rom)
Flashing bootloaders will not fix the problem, they are not related at all. And if a bootloader flash fails your phone will actually be bricked.
Just flash a stock rom with odin. I recommend jl2 if you want to go official stock, js8 for fastest froyo stock or jvk for the latest leaked beta. Tick update bootloaders for jvk or jl2 flash because jvk requires jvk bootloaders and jl2 because it supposedly fixes corruption problems. Remember bootloaders are overwritten every time you flash them and us risky.
Sent from my GT-I9000 using XDA Premium App
Thanks a million guys, I did flash the stock jl2 (no .pit or partition, nor bootloader update) and the phone booted. It fed me a gajillion force closes, but i managed to connect to kies and updated it that way, so now I have a perfetly working phone again. I'll probably experiment with a few more things now that I know how to fix this.
Again, Thanks guys!
Hey all, just revived my old captivate, was going to put ICS on it, was attempting to root, but the one click root program wasn't working, was hanging while rooting.
I tried factory wipe, and now I get stuck in a boot loop, it will boot the i896 bootscreen, the the Rogers screen, then reboot.
I've tried from there connecting to Kies, but it won't recognize it. I tried flashing stock Eclair to it using Odin, still bootloops, tried one click odin, still boot loops.
Any thoughts? Am I missing some obvious noob step? I don't have CWM or anything on it, just a stock 2.1 that won't boot.
Just tried flashing the AT&T firmware, same deal. Get past the ATT bootscreen, then the Galaxy S screen then it reboots.
Flashed Froyo, and it boots! But I can't root If I flash back to 2.1, back to bootloop.
Try to search around the forum for the stock recovery without signature checks. Once you have that, you can flash a rom. And most custom roms comes pre-rooted. You can also flash a kernel with Clockworkmod recovery built in, and flash the rom via CWM. Just read the Rom thread about installing.
Sent from my Serendipity VII flashed Captivate using xda premium
Limitz Cash said:
Try to search around the forum for the stock recovery without signature checks. Once you have that, you can flash a rom. And most custom roms comes pre-rooted. You can also flash a kernel with Clockworkmod recovery built in, and flash the rom via CWM. Just read the Rom thread about installing.
Sent from my Serendipity VII flashed Captivate using xda premium
Click to expand...
Click to collapse
Thanks, looking for that now, any idea where it might be to narrow my search? Hopefully this helps.
I think it should be in android development forum, in this captivate section. If your on a computer, you can search for it using the search box at the top.
Sent from my Serendipity VII flashed Captivate using xda premium
If you're on Froyo, look for the speedmod kernel. If you can flash that via Odin/Heimdall, you should have root and CWM on your Froyo build.
The other option would be to flash a stock Gingerbread rom with CWM baked in - I believe that 4-2ndtwin has a KK4-based one-click with CWM and Gingerbread bootloaders in the Stock Roms Collection thread.
jmtheiss said:
If you're on Froyo, look for the speedmod kernel. If you can flash that via Odin/Heimdall, you should have root and CWM on your Froyo build.
The other option would be to flash a stock Gingerbread rom with CWM baked in - I believe that 4-2ndtwin has a KK4-based one-click with CWM and Gingerbread bootloaders in the Stock Roms Collection thread.
Click to expand...
Click to collapse
Flashed the Kernel through Odin, but on reboot there was no sound and the touchscreen didn't work. Managed to get into CWM, so I'll see how things go.
The kernel worked, got to CWM and flashed CM9, thanks for the help!
Hi everyone,
First time posting, I was on Simplicity rom 2.2.1, playing tiny tower while my alarms were going off. Next thing I know, the whole phone (GT-i9000) crashes and its stuck in an infinite bootloop. I can get into download mode easy enough and I tried flashing to a heap of stock roms: JVT, JVU, JVH and JVN. Nothing worked. I couldn't get into recovery mode, but after flashing the original CWM7 kernel I could.
Tried wiping everything in recovery, including dalvik cache, then flashing back to Simplicity in CWM. Again, nothing working, in fact nothing at all. Tried stock again, not working. Tried flashing some other kernels, didn't work either. Curiously I tried flashing darkys rom RE 10.5 in ODIN and it failed at repartitioning. Not sure if there's anything behind that. Anyway, I don't really know what to do next, so I'm here.
i tried without repartition with repartition etc and it would always fail.. but then i tried again put repartition set pit file and now..its flashing it! so trying more might help you. btw im using darky resurrection
That didn't work, it only lets me attempt one ODIN flash per entry into download, then I have to reset the phone to try again.
Make sure flashing a rom with bootloader.
Sent from my I9000 running JW5 with Dmore3.3 and Semaphore 2.7.4
I've always been cautious about bootloaders, I read somewhere that if you do it wrong it will completely brick your phone. Can you tell me how to do this safely?
you need to flash stock rom 2.1 with three parts and pit 512 and repartition checked, if didnt work try with out repatition
Can you provide a link for stock 2.1? I can't find one.
Found one with a bootloader, used ODIN, and it worked! Then went to stock JVU, updated to speedmod kernel (still working) but then I tried to update to SURFACE rom and I'm back to square one. Bootloops.
Tried more stocks roms with bootloaders, none of them working. I can get to recovery again if I flash CWM7 kernel like before.
lankks said:
I've always been cautious about bootloaders, I read somewhere that if you do it wrong it will completely brick your phone. Can you tell me how to do this safely?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=14273101
Sorry when I say bootloaders I mean they are built into the rom. I never flash them separately. The above link is a great resource to firmware with bootloaders. The newest gingerbread firmware is JW6... Try that or one of the others. I'm currently on JW5, with semaphore 2.7.4 kernel and DMore 3.3 Rom, it's rock solid. Hope you get it sorted.
Sent from my I9000 running JW5 with Dmore3.3 and Semaphore 2.7.4
vanisleryan said:
http://forum.xda-developers.com/showthread.php?p=14273101
Sorry when I say bootloaders I mean they are built into the rom. I never flash them separately. The above link is a great resource to firmware with bootloaders. The newest gingerbread firmware is JW6... Try that or one of the others. I'm currently on JW5, with semaphore 2.7.4 kernel and DMore 3.3 Rom, it's rock solid. Hope you get it sorted.
Sent from my I9000 running JW5 with Dmore3.3 and Semaphore 2.7.4
Click to expand...
Click to collapse
Yeah I found this thread earlier, I did flash with JW6, doesn't work.
So instead I just accidentally flashed a ROM for the Galaxy Tab, now my phone won't turn on at all, I'm afraid I just bricked it for reals. Can't enter download mode, completely dead boot.
http://www.teamovercome.net/p1000/?page_id=17