Related
Hi guys,
So I tried to root my phone today - I dont know what happened or what I did wrong, but my phone now is locked constantly into a boot cycle. It'll turn on, boot into the lockscreen for maybe 20 seconds, then reboot itself. Nothing i do seems to help. I tried flashing back to the stock rom, flashing back to stock rom + root, but to no avail. Ive been desperately trying to find a solution that will at least allow me to get to the data on the phone (i have some pictures that i haven't backed up that are absolutely essential) and then i have no problem doing a complete data wipe or whatever is necessary.
Someone PLEASE help! phone is completely unusable at this point!
Yes, I can enter download mode
re: Boot Looping
victor3063 said:
Hi guys,
So I tried to root my phone today - I dont know what happened or what I did wrong, but my phone now is locked constantly into a boot cycle. It'll turn on, boot into the lockscreen for maybe 20 seconds, then reboot itself. Nothing i do seems to help. I tried flashing back to the stock rom, flashing back to stock rom + root, but to no avail. Ive been desperately trying to find a solution that will at least allow me to get to the data on the phone (i have some pictures that i haven't backed up that are absolutely essential) and then i have no problem doing a complete data wipe or whatever is necessary.
Someone PLEASE help! phone is completely unusable at this point!
Yes, I can enter download mode
Click to expand...
Click to collapse
When you flashed the STOCK rom was it a ZIP or a TAR file?
Before I can help I need to know.
Zipfiles require CWM Recovery for flashing and TAR files require ODIN for flashing.
I flashed the TAR file in ODIN 1.85, PDA.tar from the unzipped file UCKH7_stock_odin.7z
So I just tried it again, for something like the 4th or 5th time. I checked only "AUTO REBOOT" and "RESET TIME" in Odin, selected PDA as PDA.tar from UCKH7_stock_odin, got the following sequence from Odin
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> factoryfs.img
<ID:0/006> NAND Write Start!!
<ID:0/006> zImage
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
where I'm locked into the bootcycle again. It does boot up into my lock screen, I can interact with the screen for maybe 10 seconds, and then it just reboots. I've let it run for a little while to see if it can figure itself out, but after the third or fourth time i get nervous and pull the battery.
victor3063 said:
I flashed the TAR file in ODIN 1.85, PDA.tar from the unzipped file UCKH7_stock_odin.7z
Click to expand...
Click to collapse
ok, here is what to do.
Download this stock rooted rom: http://www.multiupload.com/PNQC9KOD4D
and download the MODEM file for the rom: http://www.multiupload.com/VWTSCXE5L0
After you extract both TAR files flash both of them at the same time by
putting the PDA tar file into the PDA slot in ODIN and the MODEM tar file
in the PHONE slot in ODIN then start flashing.
Don't check or uncheck any checkboxes in ODIN.
When its done flashing, it should boot into the STOCK ROOTED rom.
Before, or after doing the above boot into recovery and do a data wipe/factory reset
Sent from my SAMSUNG-SGH-I777 using XDA App
Didn't work. Still stuck in the same boot pattern. Redownloaded ODIN, redownloaded all the links again just to guard against any kind of corrupted files, but same end result, constant reboot cycle.
Samsung galaxy s2 --> at&t rethink possible --> preparing usb storage/lock screen --> reboot
You probably need to do a wipe data/factory reset.
Since you apparently have files that you want - enter CWM recovery and adb pull them.
re: try this
victor3063 said:
So I just tried it again, for something like the 4th or 5th time. I checked only "AUTO REBOOT" and "RESET TIME" in Odin, selected PDA as PDA.tar from UCKH7_stock_odin, got the following sequence from Odin
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> factoryfs.img
<ID:0/006> NAND Write Start!!
<ID:0/006> zImage
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
where I'm locked into the bootcycle again. It does boot up into my lock screen, I can interact with the screen for maybe 10 seconds, and then it just reboots. I've let it run for a little while to see if it can figure itself out, but after the third or fourth time i get nervous and pull the battery.
Click to expand...
Click to collapse
Try this first if you have not tryed it yet, it looks like odin flashed the PDA
file sucessfully, but did not flash the modem.
So put the modem into the PDA slot in ODIN and flash it.
If that don't work then do it vica versa and only flash the
PDA file in the PDA slot in ODIN.
This way you will know for sure which TAR file is not flashing.
(if you only have one TAR file to flash at a time with ODIN always put it in PDA slot)
If that don't work then try the method below.
Try this, turn off the phone or pull the battery, turn the phone back on or
replace the battery and go into CWM recovery and select
"Wipe Data/Factory Reset" Don't worry, it will NOT delete any pictures
or videos, or anything which you personcally have saved into a folder
you have created and it will not even touch the external sdcard if you have one.
It will however delete all the apps which you have installed in the phone prior
to having the problems you have now..
Is the data wipe / factory reset going to delete pictures off my phone? thats really my last resort.. I have a couple dozen pictures that I took on my phone since i purchased that I haven't had a chance to backup.
Does anybody have any ideas?
victor3063 said:
Is the data wipe / factory reset going to delete pictures off my phone? thats really my last resort.. I have a couple dozen pictures that I took on my phone since i purchased that I haven't had a chance to backup.
Does anybody have any ideas?
Click to expand...
Click to collapse
Its not going to delete any pictures, videos or even music you have
on the phone.
Anything which YOU have SAVED to the phone will not be touched
except usernames or passwords, credit card #'s might be deleted.
But actual files or folders you created will stay intact as well as
the external sdcard if you have one will not even be touched.
I think the reboot is occurring due to corrupted settings of network or files ystem. You can try this. pull out the battery, remove sim and sd card if you have any, then try booting..
Factory reset or data wipe should not theoretically wipe your pictures.. It basically wipes only /data partition. I have done factory reset which retained my pictures..
But to be on safer side, try the above step to see, if you can get the phone running..
Had same issue trying to factory restore with Odin. Wipe from e3 did the trick.
Sent from my SAMSUNG-SGH-I777 using XDA App
victor3063 said:
Is the data wipe / factory reset going to delete pictures off my phone? thats really my last resort.. I have a couple dozen pictures that I took on my phone since i purchased that I haven't had a chance to backup.
Does anybody have any ideas?
Click to expand...
Click to collapse
Those SHOULD be on /sdcard, but I can't guarantee it. Also, if you use 3e recovery, there's a chance that might hit /sdcard.
MJ, you should never guarantee something like that to someone.
Make sure you have ADB set up - I suggest Googling Droid Explorer if you're on Windows
Flash a CWM-enabled kernel
Enter CWM using the three-finger trick (this should work fine)
In CWM, go to Mounts and Storage and mount /sdcard and /data if they are not mounted
Connect to your phone using ADB and start looking for your files - I think Droid Explorer makes this MUCH easier by providing a nice graphical frontend to ADB push/pull
so this is what i'm doing right now.
Obviously my problem is constant rebooting.
1. Flash UCKH7 stock odin PDA.tar and UCKH7 modem via odin onto phone via odin
2. flash CWM recovery ClockworkMod Recovery 5.0.2.3 via odin as PDA
3. both these step pass OK, now Samsung Galaxy S2 I9100 bootscreen with yellow triangle shows up + at&t logo, however constant reboot problem is still present
4. pull battery unplug usb replugin battery and attempt to enter cwm recovery via holding down volume up+volume down+power button
5. CWM based recovery 5.0.2.3 flashes up for a brief second after bootscreen, then immediately reboots and reenters boot cycle
REALLY stuck here. i spent the whole day looking through the forum and i'm really not sure where i went wrong. the only thing that doesnt have the reboot cycle is download mode.
im basically trying to reach the step where i can enter cwm recovery and attempt to do a factory wipe, but it still reboots the enter i enter cwm recovery and enters the normal reboot cycle. i have NO IDEA how i couldve corrupted the file system this badly, perhaps the usb cable got bumped during the initial root? who knows. all i know is i cant even bring the phone to any form of usable status right now. any ideas?
re: boot looping
victor3063 said:
im basically trying to reach the step where i can enter cwm recovery and attempt to do a factory wipe, but it still reboots the enter i enter cwm recovery and enters the normal reboot cycle. i have NO IDEA how i couldve corrupted the file system this badly, perhaps the usb cable got bumped during the initial root? who knows. all i know is i cant even bring the phone to any form of usable status right now. any ideas?
Click to expand...
Click to collapse
You really do have a problem.......
I remember before getting this new SGS2 when I had the Samsung Infuse.
There was a thread in the Infuse forum called "The Ultimate Unbrick", I know
that there is a simular thread here for our SGS2 however the unbrick here is
lacking the PIT file.
I am 100% sure that if you could get a hold of something like the
Ultimate Unbrick which included the *.PIT file that it would solve the
problem you have.
The Ultimate Unbrick for the Samsung Infuse consisted of a
PDA*.TAR, PHONE*.TAR and the *.PIT file and it came with ODIN too.
The PIT file repartitions the sdcard to stock which fixes any partition
errors the phone may have due to flashing a non-compatible rom or
due to the flashing process being interupted while odin was flashing.
You might want to ask around the forum here if anyone has a stock
ODIN rom which includes PDA, MODEM and the PIT file for SGS2 i777.
I know for a fact that for the Infuse phone a complete stock package like
that always worked for fixing and solving problems like yours.
The only problem a package like this could not fix was if the phone
was hard-bricked meaning that it would not turn on at all no matter what.
Good luck with it..........
wow, the thought that i might be completely bricked is genuinely terrifying. really frustrating too, as i definitely consider myself fairly tech savvy.
Are you getting any indication that any of your capacitive buttons are acting like they are continually being pressed?
Did your phone at any time get wet?
The reason I ask is it almost seems like a hardware problem at this point. I would pull your battery and check the water indicators and see if there are any signs of moisture.
If there are no signs of moisture and you are pretty positive the phone is dry I would put the battery back in, don't turn it on, plug it into a wall charger and let it charge for a few hours. Then try to get into recovery again.
If after that you are still getting boot loop even in recovery we will link you to a .pit file and have you try a re flash to stock with a re partition.
Sent from my SAMSUNG-SGH-I777 using XDA App
thanks for the advice dayv.
I'm 100% sure theres been no water damage. I've barely had the phone for a week, and everything was working fine up until now. Other than that, I guess i'm going to have to go for the pit method - going to charge the phone overnight, see if it boots into cwm one last time, and then i'm going to use the following pit file from paulyhoffman
http://forum.xda-developers.com/showthread.php?t=1286218
so just to go over the procedure one last time - download mode on phone (only thing that seems to be working correctly so far)
flash PIT (I777UCKH7.pit), PDA (PDA.tar) and PHONE(UCKH7_modem.tar) at the same time, with REPARTITION, AUTO REBOOT, and RESET TIME checked in Odin?
Big problem...
After flashing 9.3 on SGS2 without wiping i rebooted in cwm and flashed siyah 2.6.2.
After that the phone stuck on the omega logo and did not boot.
I rebooted into CWM wiped cache/davlic etc and i tryed to reflash the 9.3 and the siyah.
After that i tryed to flash the kernel but the phone restarted itself and since then it doesnt boot at all neither in CWM or into android.
Only in download mode and it's not recognized by ODIN or kies.
ODIN:
ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>Firmware update start..
<ID:0/003> zImage
<ID:0/003> NAND Write Start!
Kies: The device is not responding.
BUT windows is recognizing the phone in devices.
What should i do?
IF i try to turn it on it appears a phone-triangle-pc logo and nothing happens after that.
angelossssss said:
Big problem...
After flashing 9.3 on SGS2 without wiping i rebooted in cwm and flashed siyah 2.6.2.
After that the phone stuck on the omega logo and did not boot.
I rebooted into CWM wiped cache/davlic etc and i tryed to reflash the 9.3 and the siyah.
After that i tryed to flash the kernel but the phone restarted itself and since then it doesnt boot at all neither in CWM or into android.
Only in download mode and it's not recognized by ODIN or kies.
ODIN:
ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>Firmware update start..
<ID:0/003> zImage
<ID:0/003> NAND Write Start!
Kies: The device is not responding.
BUT windows is recognizing the phone in devices.
What should i do?
IF i try to turn it on it appears a phone-triangle-pc logo and nothing happens after that.
Click to expand...
Click to collapse
1) Get the right CF Kernel from the Chainfire kernel thread in the Android Original Development Thread. Extract the zip to get a TAR and extract the TAR to get a z-image file. Also download the corresponding original stock kernel from the Intratech thread in the same section.
2) Flash the TAR in PDA using Odin. Do not click repartition. This lets you boot with with functional Root and CWM.
3) If you want to get rid of the yellow triangle, then load the z-image file into /sdcard. Reboot into download mode and use Odin to flash the stock kernel (again in the PDA without repartition). After that, go to the CWM app, choose flash kernel and locate the zimage and proceed.
NB: You can read Chainfire and Intratechs threads in case I was vague somewhere.
Thanks mate but i already know and did all these.
The thing is what i do in order to bring my phone back to life.
What is 9.3 you flashed ???
Kies: The device is not responding.
Why are you using KIES to flash a rom is it open and preventing Odin from working .
jje
Are you saying Odin does it doesn't recognise your phone?
In the past Odin flashing has gone wrong and can usually be fixed by a PC reboot or rebooting into download mode again.
Sent from my GT-I9100
9.3 = Omega 9.3 rom.
No i'm not.
I installed kies to see if the phone is recognized. After i realized that it's not i uninstalled the kies.
The thing is that odin sees my phone but stacks at <ID:0/003> NAND Write Start!
With 115 posts no reason for you not to ask in the rom thread as its possible its rom specific .
Dont think it is but worth a try .
Choices try Odin on another PC .
Take phone to service centre and hope it is not an expensive repair .
Buy a JTag machine .
jje
Just tryed odin on another pc and i got the same result...
i had the same problem and tried flashing the PIT thinking it might do something, but ended up fully bricked. couldnt power on anymore. only way is to JTAG it now, if odin cant flash it.
read this thread maybe it can help
http://forum.xda-developers.com/showthread.php?t=1382838&highlight=unbrick
angelossssss said:
9.3 = Omega 9.3 rom.
No i'm not.
I installed kies to see if the phone is recognized. After i realized that it's not i uninstalled the kies.
The thing is that odin sees my phone but stacks at <ID:0/003> NAND Write Start!
Click to expand...
Click to collapse
Were you flashing using Odin without Kies installed? As far as i'm aware Kies must be installed but not running to flash with Odin.
Nothing worked
The phone is off to Samsung service.
Thanks for your help people.
Hi,
I've think i've caused a problem on my Phone, I tried flashing a number of roms but now after flashing DlevRom 3.1_KI4. And trying to restore it back to Stock.
Its hanging on when using odin.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
I can use Heimdall to flash my kernel back to stock without any issue. But using Odin it keeps doing the above.
I've tried CF-Root-SGS2_XX_XEO_KI4-v4.4-CWM4 kernel which i'm able to flash and access clockworkmod but i'm unable to flash CyanogenMod rom which is still stored on the phones memory it shows a number of errors.
The default rom/kernel i'm trying to restore to are
ROM - GT-I9100_XEU_I9100XWKI4_I9100XEUKH2_I9100XXKI1
Kernel - Kernel_I9100XWKI4
I've flashed back to these before when it had CyanogenMod on. So i'm not sure what the problem is now.
Anybody got any ideas to help me.
Also when flashing with ClockworkMod, all roms flash very quickly like its not changing anything.
Have you put asn ICS rom on your phone and changed the bootloaders is my first question??
jje
No keeping away from ICS roms at present. I Flashed my phone with DlevRom 3.1_KI4 rom which booted up ok but decided to go have a go again with CyanogenMod. So went into Clockmod selected the ZIP it went thought the process but display error see attached image.
http://img585.imageshack.us/img585/2970/dsc00010ob.jpg
I didn't change the kernel before trying to change to cyanogenmod so it had the kernel from DlevRom.
Then i starting having these problems.
But at present the only way i can change the kernel is using Heimdal. If i try using Odin it freezes.
Hope that makes sense.
That error is telling you it thinks your device isn't an I9100, or the check to determine if it is isn't working correctly. If you're sure you do have an I9100, follow the instructions to install CM7 to the letter, which involve flashing a different kernel first (you said you can do this with Heimdall), and then flashing the CM7 zip twice in succession.
Yes i have a Samsung Galaxy I9100 (UK). Yeah i was able to flash without a problem but then i think i forget to reflash the kernel with the CM7 one. But using Heimdall i'm able to reflash to any kernel without any problems. Its only when i try to flash a rom that it doesn't work.
So now sure how ive done that to make it think i have a differnet type of phone.
I've had CM7 running on the device before and stock but wanted to try a couple more roms. So maybe i've skipped a step somewhere but not sure.
Hey all,
I am in the US I bought this I9300 that won't boot thinking I could simply reflash it and use it/resell it.
It won't boot into custom recovery or the OS. Last night it was stuck on the Samsung screen but I did some reading and found this guide: widefide (dot) com/mobile/galaxy-s3-boot-problem-solution (spam filter)
I was able to use Odin to reflash the PIT that was linked there so now the phone gets to the Firmware/Kies screen.
I have tried flashing any stock ROM (I'm not even sure which 1 I should be flashing) and/or installing CMW and Odin either gets stuck on SetupConnection.. or <ID:0/003> NAND Write Start!!
Is there anything I can do to recover this phone? I'm pretty savvy so as long as the tools exist I anticipate that I can fix this.
Can you please post in the correct sections?.
Thread closed.
Hello,
i tryied to flash CM11 to my i9300 using one of the manual here but i ended up with phone going on boot loop when started(Shows only Samsung i9300 black/white logo in 3seconds loop). I only have an access to download mode
It says:
Product name: GT-i9300
Custom Binary download: Yes
Current Binary: Samsung Official
System Status: Custom
When i try to get the recovery mode installed again the Odin say
<ID:0/028> File analysis..
<ID:0/028> SetupConnection..
<ID:0/028> Initialzation..
<ID:0/028> Get PIT for mapping..
<ID:0/028> Firmware update start..
<ID:0/028> SingleDownload.
<ID:0/028> boot.img
<ID:0/028> NAND Write Start!!
And thats all. I supose i can connect through the USB while the odin shows the USB COM port and blue color.
Is my phone bricked or is there any way how to save it? Thank you for your advice
honzicek69 said:
Hello,
i tryied to flash CM11 to my i9300 using one of the manual here but i ended up with phone going on boot loop when started(Shows only Samsung i9300 black/white logo in 3seconds loop). I only have an access to download mode
It says:
Product name: GT-i9300
Custom Binary download: Yes
Current Binary: Samsung Official
System Status: Custom
When i try to get the recovery mode installed again the Odin say
<ID:0/028> File analysis..
<ID:0/028> SetupConnection..
<ID:0/028> Initialzation..
<ID:0/028> Get PIT for mapping..
<ID:0/028> Firmware update start..
<ID:0/028> SingleDownload.
<ID:0/028> boot.img
<ID:0/028> NAND Write Start!!
And thats all. I supose i can connect through the USB while the odin shows the USB COM port and blue color.
Is my phone bricked or is there any way how to save it? Thank you for your advice
Click to expand...
Click to collapse
If I'm not mistaken boot.img is the bootloader, not the recovery. Are you sure you can't get into recovery using the 3-button-combo? If not I would try flashing this recovery via ODIN. And then try to reboot into it using the combo. Then flash CM zip from there again.
Hi, im sure i cant get to recovery using 3 button combo. That gives me only the loop of "Samsung SIII" logo. The 3buttons combo work only for download mode.
Thats what i wrote, when im trying to flash the recovery via ODIN it gets stucked on the on the message <ID:0/028> NAND Write Start!! and nothing else happens. I tryed the 3.07 and 3.09 version of ODIN.
honzicek69 said:
Hi, im sure i cant get to recovery using 3 button combo. That gives me only the loop of "Samsung SIII" logo. The 3buttons combo work only for download mode.
Thats what i wrote, when im trying to flash the recovery via ODIN it gets stucked on the on the message <ID:0/028> NAND Write Start!! and nothing else happens. I tryed the 3.07 and 3.09 version of ODIN.
Click to expand...
Click to collapse
Ah, I'm sorry I misunderstood. I thought that was just a snippet of the log... Try flashing the recovery I provided and see if it flashes. If not, maybe you can flash stock firmware with pit file (new partition table). If nothing flashes, I have no further ideas.
Thanks, but ive already tryed to flash several recovery with the same results (got stucked on NAND write in ODIN), I downloaded stock rom but the package was without pit and other kinds of files (got stucked too on NAND write in ODIN). Its a ROM for TMZ (T-mobile Czech). Do you know where i can get the "full" package. Do i need to flash the pit and other files together with ROM?
You're seriously pottering a brick. The 'full package' contents 3 files, which you've to place in the right Odin-windows +repartition-check. These files are unofficial. Google for files and instruction.
rp158 said:
You're seriously pottering a brick. The 'full package' contents 3 files, which you've to place in the right Odin-windows +repartition-check. These files are unofficial. Google for files and instruction.
Click to expand...
Click to collapse
I could be mistaken but I believe the 3-part-roms (csc / pda / phone) is the "old style" how roms where put out by sammy. You would have to search but I would think you can also use the version you get from sammobile nowadays (one zip) and additionally just use the gt-i9300 pit file found somewhere here in the forums.
@Hawaiihemd: be shure, you're wrong.
honzicek69 said:
Thanks, but ive already tryed to flash several recovery with the same results (got stucked on NAND write in ODIN), I downloaded stock rom but the package was without pit and other kinds of files (got stucked too on NAND write in ODIN). Its a ROM for TMZ (T-mobile Czech). Do you know where i can get the "full" package. Do i need to flash the pit and other files together with ROM?
Click to expand...
Click to collapse
Try this >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << the pit file is in the 4.1.2 download and can be used on both versions.(Also try the 1.85 version of Odin) >> http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539 <<
rp158 said:
@Hawaiihemd: be shure, you're wrong.
Click to expand...
Click to collapse
@rp158 Well, I think I only made a small error in my assumption.
Here are the details on the sammobile download. It seems to hold everything a "3-part-version" holds. I downloaded the file and a look at the .tar file inside the single .zip seems to confirm that.
This post suggests that flashing the .tar with the pit file should work.
I don't know because I haven't tried myself, maybe you have. Or I'm missing a piece of the puzzle. If so, maybe you could point me to it!?
@Hawaiihemd: If I look into the unzipped tar.md5-firmware, there are image-files. One for each partition. If I look into a 3part-zip-file, there are 3 tar.md5-files for each Odin-input-window. I tried only this soft method. The way, described in your cited post, I would only try as a last exit. The whole Odin-firmware-flashing is a black-box: noone knows, why&when during a normal flash a factory-reset is triggered or during repartition efs-data are restored. So, where the software finds the necessary repartition-data in the usual 1part-zip, is also unknown. Sorry, if I hurt you.
rp158 said:
@Hawaiihemd: If I look into the unzipped tar.md5-firmware, there are image-files. One for each partition. If I look into a 3part-zip-file, there are 3 tar.md5-files for each Odin-input-window. I tried only this soft method. The way, described in your cited post, I would only try as a last exit. The whole Odin-firmware-flashing is a black-box: noone knows, why&when during a normal flash a factory-reset is triggered or during repartition efs-data are restored. So, where the software finds the necessary repartition-data in the usual 1part-zip, is also unknown. Sorry, if I hurt you.
Click to expand...
Click to collapse
You didn't, don't worry. I was a little stumped maybe, but only because your answer was so terminal. Actually I only wanted to start a discussion about this, because you seemed to know more about said process than me and I always try to gain knowledge here to better help solving problems. I haven't been in this forum for long or into android for that matter...
That said, I have done the "3-files" version of this process with a .pit file thrice already on different gt-i9000s. Always worked flawlessly.
Looking at the ones in the post @tallman43 suggested, I found the contents of those 3 .tar.md5 files in summary(!) similar to the ones in the 1 .zip from sammobile. That's why I thought it could work in the first place.
One thing I'm sure of is that in both cases the repartition info is in the .pit file. If you choose none, the MMC should not be repartioned. If partitions are reformatted... that's another deal.
Concerning the efs partition, to/from where that info is stored/restored during repartitioning of the MMC... that's a very interesting question!
tallman43 said:
Try this >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << the pit file is in the 4.1.2 download and can be used on both versions.(Also try the 1.85 version of Odin) >> http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539 <<
Click to expand...
Click to collapse
Thank you very much for this hint. It worked well. I used the all files from KOR zip and 1.85 ODIN. Now i have the Korean version but at least i have something to start with and phone which works now.