Related
Hi I updated my SGS from Eclair to what I thought was the latest Froyo firmware. It turned that I had updated it to JP2. Now really nothing works anymore. Not even 3G.
My phone is not branded it any way but since Samsung turned off the update to JP6 I can't update using Kies. So I need to make the update using Odin or being able to get it to accept 2e files so I can install Clockwork Mod. Thing is I have no clue how to make it run 2e files. I did root it but that didn't work so obvious there is something else I need to do.
I guess my JP2 version is the stock JP2, and I would like to update it to stock JP6 or Tayutama's custom mod.
Is there something I need to do before I try updating my phone to JP6, or would it work to simply load the .tar file in Odin using the 803.pit file and re-partion and click "Start"?
PDA: I90000XXJP2
PHONE: I90000XXJP2
CSC: I90000XXJP2
Build Info: 2010.07
TIA
Daniel
Eh. Best way is downgrade to jm8 using the 512 pit file and set it to re partition. Once that's done install jp6 with 803 pit but do not use re partition. It will take too long to explain why you need to downgrade. But if you want to save time then try this method. Install jp6 as normal with 803 pit and don't re partition but this method isn't safe
Sent from my GT-I9000
I hope you made a backup first.
The way i do flash jpm or jp6 is safe and simple.
First you need a clean system.
I do this with jpk. Using pit 512 and with re-partition.
Then flash with odin.
Then i let the phone boot up.
I then format the internal sdcard.
Then i reboot in recovery mood.
There do i wipe the catch and do a factory reset.
Now is the phone almost clean.
Next i flash jpm or jp6. Use no pit file and do NOT re-partition.
People that tell you to use pit file here don't know what they are talking about.
Flash now with odin.
Start the phone and let it boot up.
Format the internal sdcard again and restart the phone in recovery again. Wipe the catch and do a factory reset. Restart the phone.
Now you got a working phone with latest froyo.
Sent from GT-I9000 jpm My own kernel for z4mod and with 341MB Ram
OK and by backup you mean backup of contacts, photos, sms's and so on? And a clean system is a system that has just been factory resetted, right?
Svantesson666 said:
OK and by backup you mean backup of contacts, photos, sms's and so on? And a clean system is a system that has just been factory resetted, right?
Click to expand...
Click to collapse
No. I mean a real backup. The efs folder is very important. There you have you personal code for the phone.
The rest of the backup is just good to have.
A clean system need more than a factory reset. If you do the steep i wrote it will be clean.
Sent from GT-I9000 jpm My own kernel for z4mod and with 341MB Ram
I didn't do a real backup before I used Odin to update to JP2. By doing so have I now lost something I can't retreive?
How do you do a real backup? Is that done in Odin too?
I am not sure if posting external links are allowed. My apologies if not allowed.
http://www.androidpolice.com/2010/0...nandroid-backup-and-clockworkmod-rom-manager/
Cheers mate, I'll go ahead and make a complete backup using the tutorial above once I'm back from work.
No worries man as long as it helps
Sent from my GT-I9000 using XDA App
Hmmm it didn't work as my phone is 3e and doesn't run update.zip. I know you have to reflash your Kernel to make it support update.zip files I just don't know how to do it. Man I'm rubbish when it comes to Android phones! haha
Hmmm you don't need to patch any kernel man.. Hope your phone is rooted the backup thing works with most of my friends' phones.. What is a 3e..? Just curious .
Sent from my GT-I9000 using XDA App
No I can't run update.zip as my phone doesn't support unsigned files in recovery mode. In recovery mode it says 3e at the post instead of 2e as it said when there was Eclair 2.1 on it.
My phone is rooted but even so I can't get it to actually create the backup. All things before that went smooth though. Superuser gave Nandroid root access and everything.
Go to the z4mod tread and download jp6 kernel and flash it with odin.
Then you got a recovery that works with update script.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 341MB Ram
Is it this kernel, by RyanZA, I should flash onto my SGS? - http://forum.xda-developers.com/showpost.php?p=8645069&postcount=162
If so should I simply apply this in Odin as PDA leaving everything else as default, put my phone in download mode and press start even though I don't run JP6 but JP2?
And after the update is done, then flash PHONE and CSC from JP6 using 803.pit leaving Re-Partion unchecked and click start?
Or should I apply the z4mod.ext2.update.zip from here - http://forum.xda-developers.com/showthread.php?t=797672 - first in recovery mode and then flash PHONE and CSC?
Or should I actually flash ALL three files, PDA, PHONE and CSC?
I must say I really appreciate all the help guys and I'm sorry if I'm abit slow, but smartphones are really a new area for me and I know nothing about Linux for that matter.
2.2 finally out for galaxy s!!
Sent from my GT-I9000 using Tapatalk
I bump this thread to get an answers to my "hopefully" final questions.
You should update the phone to the latest froyo. Don't se any reasons not to.
Then flash a kernel. After that use a filesystem, lagfix you want.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 341MB Ram
DamianGto said:
You should update the phone to the latest froyo. Don't se any reasons not to.
Then flash a kernel. After that use a filesystem, lagfix you want.
Click to expand...
Click to collapse
So I should just flash the PHONE and CSC before I flash the kernel (PDA) you say?
And are those files I posted in a few posts above the correct ones?
No.
You should use kies to upgrade if you can. ;-)
Then you can do other stuff.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 341MB Ram
I tried Kies yesterday. Sadly after putting in JP2 that ruined Kies, It says, this device can't be updated. I even tried to fool Kies by registry hack, but Samsung has obviously done something to provoke that as it didn't work.
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!
I've been asking for help after screwing up my Tab while trying to restore my Roto Backup with Odin, and the thread has been completely quiet.
I just wanted to ask an easier question, and see if that might tell me everything I need to know: Has anyone other than rotohammer ever actually successfully restored their Roto Backup? Second question, has anyone, including rotohammer, ever restored their Roto Backup with Odin?
The reason you screwed with your roto backup is the base in which you flashed the backup over and how you flashed the backup.
Here are the Reasons for Rotobackup failures:
1- Flashing a FROYO backup over a GINGERBREAD system (Both systems have DIFFERENT BOOTLOADERS) this causes lines and corrupted system image etc.
2. Not Flashing the correct PIT file or flashing one at all over a custom ROM you are using e.g Flashing your ROTO without PIT over overcome ROM formatted in EXT4 can result in a non boot as the kernel doesn't support EXT4.
3. Flashing bootloaders (boot.bin and SBL.bin) from the Roto backup. My advice: DO NOT DO THAT IF YOU DON'T WANT TO END WITH A HARD brick. For some reasons bootloaders from rotobackup arent really Safe.
My advice is to flash a Standard stock firmware (Froyo if you backup is froyo and GB if your backup is GB) then flash your Roto backup over it WITHOUT pit and WITHOUT bootloaders.
DarkPal said:
The reason you screwed with your roto backup is the base in which you flashed the backup over and how you flashed the backup.
Here are the Reasons for Rotobackup failures:
1- Flashing a FROYO backup over a GINGERBREAD system (Both systems have DIFFERENT BOOTLOADERS) this causes lines and corrupted system image etc.
2. Not Flashing the correct PIT file or flashing one at all over a custom ROM you are using e.g Flashing your ROTO without PIT over overcome ROM formatted in EXT4 can result in a non boot as the kernel doesn't support EXT4.
3. Flashing bootloaders (boot.bin and SBL.bin) from the Roto backup. My advice: DO NOT DO THAT IF YOU DON'T WANT TO END WITH A HARD brick. For some reasons bootloaders from rotobackup arent really Safe.
My advice is to flash a Standard stock firmware (Froyo if you backup is froyo and GB if your backup is GB) then flash your Roto backup over it WITHOUT pit and WITHOUT bootloaders.
Click to expand...
Click to collapse
Thanks for the help. So you've managed to get your Roto Backup to work before?
So if I can't flash a bootloader from Roto backup, how do you recommend I flash back to the Froyo bootloader?
Also, any recommendations on a Froyo standard stock firmware image I can flash safely on an AT&T tab?
Well any stock package (froyo or GB) will have its bootloaders included so don't worry about them. As for a recommendation for a stock package yes actually I have 2 for froyo. JK5 and JJ4 packages should be good to go if you want to downgrade your tab to froyo (if you for some reason wanted to do that).
DarkPal said:
The reason you screwed with your roto backup is the base in which you flashed the backup over and how you flashed the backup.
Here are the Reasons for Rotobackup failures:
1- Flashing a FROYO backup over a GINGERBREAD system (Both systems have DIFFERENT BOOTLOADERS) this causes lines and corrupted system image etc.
2. Not Flashing the correct PIT file or flashing one at all over a custom ROM you are using e.g Flashing your ROTO without PIT over overcome ROM formatted in EXT4 can result in a non boot as the kernel doesn't support EXT4.
3. Flashing bootloaders (boot.bin and SBL.bin) from the Roto backup. My advice: DO NOT DO THAT IF YOU DON'T WANT TO END WITH A HARD brick. For some reasons bootloaders from rotobackup arent really Safe.
My advice is to flash a Standard stock firmware (Froyo if you backup is froyo and GB if your backup is GB) then flash your Roto backup over it WITHOUT pit and WITHOUT bootloaders.
Click to expand...
Click to collapse
and
I'll explain
=-=-=-=-=-=
I got 2 Tab's same STOCK ROM's...
on one of them installed overcome...
then i took roto backup the other and restored with odin on the overcome..
wait wait... i restored a stock GB from samfirm first and then used my Froyo backup...
kinda the same like you explained not to do... and guess what?!
tab died needed jtag... after jtag they gave me back the tab with stock froyo from samfirm...
now i'll explain
=-=-=-=-=-=-==
i restored again my backup with odin and original rom is now installed perfectly.. i did had an error when it reached boot.bin though..
but i restarted the tab and it's up and running...
too bad i didn't saw your message before...
i just have a question..
so lets say i'm now in overcome.. want to install 2.2
you say that i'll should use lets say stock rom from samfirm
with odin... with p1 pit file
check repartition, areboot, freset and start...
when done restore using my backup created using RB
with odin... areboot, freset and start (pda with the tar file and no pit)
but in the 'tar' file not to include boot.bin and SBL.bin files? just those files?
sorry for bad english...
I would think that Roto Backup is only good for restoring within the same base rom. For example, if the backup is done under rom DXJDE, i would flash stock DXJPE rom with pit file and all, then follow by the backup without the pit file.
Secondly, if you want to revert to stock status, i think Roto Backup is only suitable for Froyo base. This is because in order to create a backup, your tab have to be rooted and with busy box. Froyo can easily go back to unroot status by using SuperOneClick.
Not so for Gingerbread. The only way to get unroot status is to flash stock.
Once you restore from your backup, your tab is rooted.
nevermind it's working...
cymagnus said:
I would think that Roto Backup is only good for restoring within the same base rom. For example, if the backup is done under rom DXJDE, i would flash stock DXJPE rom with pit file and all, then follow by the backup without the pit file.
Secondly, if you want to revert to stock status, i think Roto Backup is only suitable for Froyo base. This is because in order to create a backup, your tab have to be rooted and with busy box. Froyo can easily go back to unroot status by using SuperOneClick.
Not so for Gingerbread. The only way to get unroot status is to flash stock.
Once you restore from your backup, your tab is rooted.
Click to expand...
Click to collapse
So there's probably no way to go back to AT&T stock then once you flash a custom ROM right? Because there is no AT&T base ROM for the ROM that was originally flashed on my Tab floating around to use as a base for my Roto Backup.
manekineko said:
So there's probably no way to go back to AT&T stock then once you flash a custom ROM right? Because there is no AT&T base ROM for the ROM that was originally flashed on my Tab floating around to use as a base for my Roto Backup.
Click to expand...
Click to collapse
i had the same problem u have... u must find someone with same rom u had and rotobackup it then flash stock rom from samfirn and then restore ur backup. dont forget to remove the boot and sbl files do not flash them. i did so and it hard bricked my tab needed jtag.
hope i helped...
avishai0528 said:
i had the same problem u have... u must find someone with same rom u had and rotobackup it then flash stock rom from samfirn and then restore ur backup. dont forget to remove the boot and sbl files do not flash them. i did so and it hard bricked my tab needed jtag.
hope i helped...
Click to expand...
Click to collapse
I have a Roto Backup, made from my own tab right after I got it, just no stock AT&T ROM to use as a base.
manekineko said:
So there's probably no way to go back to AT&T stock then once you flash a custom ROM right? Because there is no AT&T base ROM for the ROM that was originally flashed on my Tab floating around to use as a base for my Roto Backup.
Click to expand...
Click to collapse
That is correct. The backup made does not contain all the files.
DarkPal said:
Well any stock package (froyo or GB) will have its bootloaders included so don't worry about them. As for a recommendation for a stock package yes actually I have 2 for froyo. JK5 and JJ4 packages should be good to go if you want to downgrade your tab to froyo (if you for some reason wanted to do that).
Click to expand...
Click to collapse
I've done some research based on your recommendations. JK5 is actually no good I think, since it isn't a full ROM, and can't be used to re-partition.
JJ4, however, worked a charm. I downloaded it from samfirmware.com, and it came with all files necessary in the rar. Re-flashed pit, pda, modem and csc. Everything booted up as expected in Russian.
Then I used my Rotobackup, and re-flashed my pit and pda.
For the most part, everything is working, and restored, but for whatever reason, the boot animation is missing, and after the Galaxy Tab screen, it just turns black, and then after a while if I turn the screen off and on, I find it's already booted up (but booted with screen off). Any thoughts on why this occurs or how I can fix it?
My situation is that I'm increasingly beginning to suspect that my data connection is fritzy because of a hardware defect. I was on Overcome, and the data would just not be working when I turned on the Tab. The symptoms are one of the following: (1) data shows as connected and you can see the Tab sending but not receiving on the status bar, or (2) data shows as disconnected and then will show as connected for a moment and then show as disconnected again, or (3) data shows as disconnected, period. To fix any of these, I would have to either cycle the data or sometimes re-select the APN and reboot and then it would work. I then flashed to and used JPE for a few days, and observed today that my data showed as connected but would only send and not receive until I cycled the packet data setting.
Flashing back to stock, which I've now (mostly) done, is pretty much a last resort. I want to confirm whether this problem still exists on stock firmware, and if it does, I want to be in a condition to send in my Tab for repairs.
Just an update, I found this thread, which sounded a lot like my problem:
http://forum.xda-developers.com/showthread.php?t=899196
However, flashing jj4_bootloaders hasn't helped my missing logo problem. There is sound now, but still a black screen on bootup.
and none from samfirm are working? couldnt be.
Have you try booting up in recovery (power on, volume up combination) and do factory reset, clear cache?
cymagnus said:
Have you try booting up in recovery (power on, volume up combination) and do factory reset, clear cache?
Click to expand...
Click to collapse
As with the people that had the white line problem, with the corrupted graphics on the bootloader, I can't see recovery, just a black screen.
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.
First i had a JB Rom on my GT-I9000 it got too hot using a app so i decided to flash CM9 on it after 2sec the installtion was aborted and i was thinking that it was trying to install CWM-Recovery but it didnt after 10min of waiting, i decided to pull the battery out. I tryed to start recovery mode but there was none. I used Odin and a pit file (Re-partion was checked) than i put a Devil 3 kernel on it. Recovery Mode was working but after i wiped everything and flashed Dark Knight 5.5 on it and clicked on reboot system now, i was sent back into recovery!!!!
Please help me to solve this problem.I am not a expert in android programm so please dont let it sound complicated
Thanks for your help.
I had this two before. Nothing would work to fix it. This is what I did
1. Flash back to stock 2.3.x with 512 pit
2. Boot into stock recovery and wipe data / factory reset
3. Pull battery and reboot into bootloader/download mode
4. Flash Devil kernel or semaphore tar with Odin.
5. Reboot into recovery and flash ROM of choice
6. Restore nandroid data through advanced restore or just start fresh.
7. Profiiit
Sent from my GT-I9000 using xda premium
One more question
AlwaysDroid said:
I had this two before. Nothing would work to fix it. This is what I did
1. Flash back to stock 2.3.x with 512 pit
2. Boot into stock recovery and wipe data / factory reset
3. Pull battery and reboot into bootloader/download mode
4. Flash Devil kernel or semaphore tar with Odin.
5. Reboot into recovery and flash ROM of choice
6. Restore nandroid data through advanced restore or just start fresh.
7. Profiiit
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
So do i need just the 512. tar file (i dont know where to download this! ) or stock rom too (I had 2.3.3 Gingerbread when i bought this phone)
Thanks for your help
Hey
theres a guide below..
Sent from my GT-I9000
Omg i worked
tchindalia said:
hey
theres a guide below..
Sent from my gt-i9000
Click to expand...
Click to collapse
thank u thank u thank u :d
Tibiak19 said:
So do i need just the 512. tar file (i dont know where to download this! ) or stock rom too (I had 2.3.3 Gingerbread when i bought this phone)
Thanks for your help
Click to expand...
Click to collapse
Samfirmware.com to download the stock ROM.
Pit files just tell Odin how to repartition the device when flashing. Should come with Odin when you download it. There should be an 80x as well, just use 512.
Then select to use xxxx512.pit
Flash ROM in PDA.
Sent from my GT-I9000 using xda premium
Try this!
Try this:
All you have to do is revert to an older version of clockworkmod, I used version 6.0.12 I believe.
the file name is: CWM6012-CM9-recovery so it might be that. Yep that's it, now i can finally rest
Thanks Byrkoet
http://forum.xda-developers.com/show...2#post39067132