Hi. I was trying to update my player (original froyo)
using the terrasilent kernel
http://forum.xda-developers.com/showthread.php?t=1643384
I flashed with odin and resulted in a soft brick (at first bootloop)
i can only access to the upload mode (phone /!\ pc)
tried to get it working by restoring the original files...
I have the recovery files using this method (adb pull)
http://forum.xda-developers.com/showthread.php?t=1632376
but i cannot flash the PDA using odin (gets stuck in zImage)
then i tried this kernel whitebeam
http://forum.xda-developers.com/showthread.php?t=1807997
now i have the cwm (3.0.0.5) and the upload menu available
If i reboot I get stuck again in a bootloop
then i found i had to use an hex editor to delete the last FF of my originl zImge, which i did but y cannot upload my original kernel back
samsung galaxy s wifi yp-g1 intl (non capacitive home button)
Thanks in advance
YP-G1CW/PEO
One additional question, in the process of updating the kernel, the rom got wiped too?
Do I need also to restore the rom?
the cwm is looking for ext4 partitions, does that mean I have to format/repartition?
please
Well the backup normally is when you're in the ROM itself and not the recovery. If you have made the backups, just flash this
http://forum.xda-developers.com/showthread.php?t=1531850
If not, try to flash the stock kernel from the zkc5 package.
Sent from my Nexus 7 using Tapatalk HD
zaclimon said:
Well the backup normally is when you're in the ROM itself and not the recovery. If you have made the backups, just flash this
http://forum.xda-developers.com/showthread.php?t=1531850
If not, try to flash the stock kernel from the zkc5 package.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
thanks but the zkc5 package is down because of too much traffic
if I trie to flash using Heimdall, I will have to restore and repartition too ._.
axlsmiu said:
thanks but the zkc5 package is down because of too much traffic
if I trie to flash using Heimdall, I will have to restore and repartition too ._.
Click to expand...
Click to collapse
Here's a mirror:
G1ZKC5 mirror
And don't repartition if you haven't done it before.try to flash the zImage alone with heimdall.
zaclimon said:
Here's a mirror:
G1ZKC5 mirror
And don't repartition if you haven't done it before.try to flash the zImage alone with heimdall.
Click to expand...
Click to collapse
thanks for the upload
I extracted the rom and the zimage inside
using the pit file in http://forum.xda-developers.com/showthread.php?t=1531850
but
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Local and device PIT files don't match and repartition wasn't specified!
ERROR: Flash aborted!
Ending session...
Rebooting device...
with the pit file from my recovery there's also a mismatch (the backup files were extracted when the device was fine)
UPDATE
:laugh: my player is working again
to overcome the PIT mismatch I used Heimdall utilities to download a fresh pit from my semi-bricked device
then I flashed the original unmodified (didnt delete the FF's with the hex editor) zImage from my initial backup
and voila! the samsung boot sequence and sound were normal again
but something odd... it appears to be still rooted even when i performed a data wipe / factory reset using the cwm
I still have to recover my apps+data from the titanium backup in the office's pc
the bad
Im stuck again with froyo
firmware ver 2.2.2
kernel
2.6.32.9
compilation froyo.xxke1
Its 2:00 am here an I need some sleep
thanks for your patience and advices:good:
axlsmiu said:
UPDATE
:laugh: my player is working again
to overcome the PIT mismatch I used Heimdall utilities to download a fresh pit from my semi-bricked device
then I flashed the original unmodified (didnt delete the FF's with the hex editor) zImage from my initial backup
and voila! the samsung boot sequence and sound were normal again
but something odd... it appears to be still rooted even when i performed a data wipe / factory reset using the cwm
I still have to recover my apps+data from the titanium backup in the office's pc
the bad
Im stuck again with froyo
firmware ver 2.2.2
kernel
2.6.32.9
compilation froyo.xxke1
Its 2:00 am here an I need some sleep
thanks for your patience and advices:good:
Click to expand...
Click to collapse
Yeah well it's a GB pit so it was normal maybe that it didn't worked. For updating to GB, download the recovery pack for GB and flash the factoryfs.rfs and the image. Also superuser is a system app and it can't be removed with a data wipe.
Sent from my Nexus 7 using Tapatalk HD
zaclimon said:
Yeah well it's a GB pit so it was normal maybe that it didn't worked. For updating to GB, download the recovery pack for GB and flash the factoryfs.rfs and the image. Also superuser is a system app and it can't be removed with a data wipe.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
you mean to use the factoryfs.rfs and the zimage from the YP-G1FullRestoreIntl2.3.6.tar.md5 package?
flashing with Heimdall these two files only?
axlsmiu said:
you mean to use the factoryfs.rfs and the zimage from the YP-G1FullRestoreIntl2.3.6.tar.md5 package?
flashing with Heimdall these two files only?
Click to expand...
Click to collapse
Yeah if you want to update only.
Sent from my Nexus 7 using Tapatalk HD
Related
Heya!
Some know my little kTool already, some love it, some hate it.
Well, let's try to get some more love for it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
>> Now with support for the Galaxy-Nexus and the Galaxy-S3! <<
So, what does this do?
Dump current kernel (and recovery on devices having a seperate one)
Flash kernel from /sdcard/zImage
Flash recovery from /sdcard/recovery.bin
Backup EFS
(as raw .IMG dump and as .TAR archive)
Check/Verify EFS backup (i.e. compare to "live" EFS)
Restore EFS from either .IMG or .TAR
Open stock update .TARs and flash from from it:
- Modem Firmware
- PARAM.LFS
- Kernel
Reboot device
- normally
- to recovery
- to download mode
*) When you check the EFS backup right after you made it, it should show a 100% match to the current phone's EFS.
However, after a reboot, the EFS *does* start to differ a bit - that seems to be normal, during my tests the EFS differed for 80bytes more after each reboot, my original EFS dump even differed by ~150k already
kTool companion tool market link [ Show ]
Hope you like it.
If anyone has more suggestions on what would need to be checked/verified during the check operation, do tell
After doing backup I did efs backup check....
And in that it says nv_data.bin not found..
Whts the reason?
Sent from my GT-I9100 using XDA App
koolshubh said:
After doing backup I did efs backup check....
And in that it says nv_data.bin not found..
Whts the reason?
Click to expand...
Click to collapse
For the .img and the .tar or only for one of them?
What does it say for "mount returned:"?
"nv_data.bin not found" means a bad/corrupted backup.
// EDIT
Just saw the screenshot.
Something went wrong making the raw .img dump (weird....).
But the .tar backup is OK (100% match to the phone's one).
Hmm.... gotta investigate the .img issue some more.
Check this;
Sent from my GT-I9100 using XDA App
OK, that helps a lot already.
The efs.img dump might be all fine and OK, it's actually a problem getting it mounted to "look into it".
Dug around some more and also found this:
Code:
2: system error (out of memory, cannot fork, no more loop devices)
"2" was the returncode you got during the check, fits with the verbose error message you get when trying the mount from a shell.
Cool, at least I know where to look, not exately sure why this happens, but we'll find out.
Maybe a busybox thing, maybe I'll bundle one with the app....
thanks for updating~~~
I have used the old one from here
f.lui.li/get_99_f13d.html
Updated to v1.21
Everything is working from my end. Thanks for the tool!
Sent from my GT-I9100 using XDA App
HellcatDroid said:
Updated to v1.21
Click to expand...
Click to collapse
it just works!
thx!
Thanks and cheers.
Thanks, HellCat. Great little kTool you've made --- love the kernel dump feature, so more love for your app! ; )
Tiny update to v1.22.
"Restore EFS" now lets you chose if you want to restore the raw .IMG dump or from the .tar archive.
Hi. thanks for your work. I kept getting the error shown in the attached pic when on xxki4 so I flashed back to official wxki4 but get the same error.. can u help?
rasinell said:
Hi. thanks for your work. I kept getting the error shown in the attached pic when on xxki4 so I flashed back to official wxki4 but get the same error.. can u help?
Click to expand...
Click to collapse
Are you rooted?
// EDIT
Hmm, and what version of the app are you using?
Tried making the EFS backup again?
I take it the phone does work fine (correct IMEI and all)?
Stock Samsung ROM or a custom ROM?
HellcatDroid said:
Are you rooted?
// EDIT
Hmm, and what version of the app are you using?
Tried making the EFS backup again?
I take it the phone does work fine (correct IMEI and all)?
Stock Samsung ROM or a custom ROM?
Click to expand...
Click to collapse
Hi. Thanks for the response. Yeah I'm rooted running official stock Rom and kernel. Everything seems fine with phone n imei ect. Tried twice on unofficial stock Rom n kernel and twice on this Rom but get the same every time :-\ I'm using v1.22
Sent from my GT-I9100 using xda premium
-scrap initial post-
// EDIT
HAHAA! I think I found something!
Thought some more about this, behaviour/differences of stock kernels and double checked a few things in my code.
I think (i.e. hope) I found the reason for this - and if my theory is correct I will be able to reproduce the app's misbehaviour you are getting and can then fix it.
I'll make a new build tonight.
HellcatDroid said:
What's the version of kTool you are using?
You tried doing the backup as well again, not only the check?
I'll flash a stock kernel and try to reproduce this later tonight.
Click to expand...
Click to collapse
I'm using v1.22. Yeah tried that. I was wondering if it was the kernel that was problem, not had chance to try with another yet. Thanks
Sent from my GT-I9100 using xda premium
HellcatDroid said:
What's the version of kTool you are using?
You tried doing the backup as well again, not only the check?
I'll flash a stock kernel and try to reproduce this later tonight.
// EDIT
HAHAA! I think I found something!
Thought some more about this, behaviour/differences of stock kernels and double checked a few things in my code.
I think (i.e. hope) I found the reason for this - and if my theory is correct I will be able to reproduce the app's misbehaviour you are getting and can then fix it.
I'll make a new build tonight.
Click to expand...
Click to collapse
Cool. Thank you
Sent from my GT-I9100 using xda premium
rasinell said:
I'm using v1.22. Yeah tried that. I was wondering if it was the kernel that was problem
Click to expand...
Click to collapse
Well, in a way.
IIRC the shell command "cp" (to copy files) is not available on stock Samsung kernels, and the app just calls "cp" instead of (like for most of the other shell commands used by the app) using "busybox cp" to call/use the busybox applet of the command.
As said, I'll try, check and hopefully fix this later tonight and if all goes well will have an update ready by tomorrow
Published v1.23 with the above issue fixed
The update should show up on the market soon.
left on old v1.22, right on new v1.23:
.
Hi Guys
I flashed my phone with ICS f/w Lightening ROM but I didn't like it because of FCs and higher batter consumption so I decided to come back to CHeckROM v6 and Phenomenol Kernel.
I did a data wipe, partition wipe, dalvik cache wipe before flashing CheckROM over Lightening ICS ROM and again deleted dalvik cache after installing Phenomenol Kernel.
Now I don't have root. I'm unable to use Applications like Root Call Blocker, Root Explorer and Voltage Control
I tried flashing my phone with different Kernels like N.E.A.K , RedPill etc but didn't get root back. What could be the issue ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flash chainfire kernel in original development thread using odin.
Thanks, that's what I'm trying right now.
I have downloaded concerned firmware from his thread : http://forum.xda-developers.com/showpost.php?p=14733439&postcount=534 and flashing as I write. I'll report back
"I did a data wipe, partition wipe, dalvik cache wipe before flashing CheckROM on Lightening ICS and again deleted dalvik cache after installing Phenomenol Kernel. "
sentance is not clear, are you still on ICS and flashed kenrel on that, or you flashed the Phenomenol, N.E.A.K , RedPill, etc after flashing checkrom ??
EDIT : if you are on Checkrom V6 and you lost root then just unzip this file to get TAR file and flash from ODIN http://download.chainfire.eu/144/CF-Root/SGS2/CF-Root-SGS2_XW_OXA_LA4-v5.0-CWM5.zip you will gain the root
Now on CHeckROM. I was explaining what all I did before returning to GB ROM from ICS ROM
zanderzone said:
Now on CHeckROM. I was explaining what all I did before returning to GB ROM from ICS ROM
Click to expand...
Click to collapse
ok then flash the one on my link after unzipping to TAR put on the PDA of Odin and flash, checkrom v6, is XWLA4, firmware, this one is chanifire's C-F Root for the same firmware....
Thanks my friend. I download the exact same file but getting some error flashing this Kernel from CWM. I also extracted the .tar file and tried via ODIN but ODIN doesn't detect my phone in DOwnload mode
Please note that I'm able to connect my phone to Laptop in normal mode i.e to transfer files.
zanderzone said:
Thanks my friend. I download the exact same file but getting some error flashing this Kernel from CWM. I also extracted the .tar file and tried via ODIN but ODIN doesn't detect my phone in DOwnload mode
Please note that I'm able to connect my phone to Laptop in normal mode i.e to transfer files.
Click to expand...
Click to collapse
have you installed kies first, if not install latest keis
then close the keis and try
Thanks a lot bud. After installing Kies, I was able to use ODIN and flash the tar file. Got root back and not flashed my favorite Kernel over it. Root is retained. Thanks again
zanderzone said:
Thanks a lot bud. After installing Kies, I was able to use ODIN and flash the tar file. Got root back and not flashed my favorite Kernel over it. Root is retained. Thanks again
Click to expand...
Click to collapse
It's my pleasure,
you can use Kitchen from Checkrom to download your favorirte kernels and flash....
if falshing directly not working from Kitchen you can now manually do it from CWM...
get into the checkrom thread and explore....everything is discussed there....
Yeah, I know that but since I lost root, KichenROM was not able to automatically boot in CWM and flash those downloaded file, I had to manually flash them.
I was recently changing custom roms on my i9300 and think i formatted the wrong option. Now when I turn on my phone it gets as far as the start up screen, then goes off and just continues to repeat. I have trawled the web and tried a couple PIT and PDA's but no joy as of yet. I can boot it into download mode. Any help would be highly appreciated! Thank you.
SwirlesY said:
I was recently changing custom roms on my i9300 and think i formatted the wrong option. Now when I turn on my phone it gets as far as the start up screen, then goes off and just continues to repeat. I have trawled the web and tried a couple PIT and PDA's but no joy as of yet. I can boot it into download mode. Any help would be highly appreciated! Thank you.
Click to expand...
Click to collapse
what happens when you try to flash a rom via Odin? any error message? I guess we need a bit more information here
chrismast said:
what happens when you try to flash a rom via Odin? any error message? I guess we need a bit more information here
Click to expand...
Click to collapse
Ahh of course haha. Well the PIT has passed but when i put the PDA on, depending on if i do straight after i have run the PIT, which it stays on "Setup connection..." or if I run the PDA on its own i get "NAND write start!"
Flash a stock rom for your galaxy s3 via Odin it's only recover your phone then you will root again
Sent from my GT-I9100 using xda premium
and just to add to the NAND write start, there is a blue bar on the download screen on my s3
gauravgymnast08 said:
Flash a stock rom for your galaxy s3 via Odin it's only recover your phone then you will root again
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
ok downloading as we speak....
the PDA i downloaded did not come with a PIT in the zip. So i have just used to PDA on its own, and when i opened it come up in the comments "Leave CS...". The start option became available so i hit it and got "NAND write start..."
I then used a PIT i used previously and tried again, then got this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Service centre repair .
jje
SwirlesY said:
the PDA i downloaded did not come with a PIT in the zip. So i have just used to PDA on its own, and when i opened it come up in the comments "Leave CS...". The start option became available so i hit it and got "NAND write start..."
I then used a PIT i used previously and tried again, then got this...
Click to expand...
Click to collapse
Hey untick repartition then flash
Sent from my GT-I9100 using xda premium
Did it help when flashed without re-partition checked?
Why do you need a PIT file? Where did you get it?
Repartitioning could be extremely dangerous.
try odin version 3.04 without the PIT file, if you get NAND write start just wait about 5-6 mins, if it stays where it is come here again.
IF you can, try rooting it with CF AUto root then flash a recovery. THen put a ROM on your external SD card and flash it via recovery and see if it boots.
Very sorry for the delay in reply. Its been bloody hectic!
I tried both of those suggestions Mr Mirage.
The first one i got the NAND write start, and the same on the second. It also got stuck on NAND write start
if you flashed a pit file, send it to service to replace the motherboard
Glebun said:
if you flashed a pit file, send it to service to replace the motherboard
Click to expand...
Click to collapse
Sorry if I sound a bit dim, but is that to samsung, vodafone, or phones 4 u? And do you know how much that will cost about?
Send it to phones 4 u if that's who bills you for your contract
Sent from my GT-I9300 using Tapatalk 4 Beta
It goes to the vendor not the network under SOGA .
Vendor may well send it straight to Samsung .
jje
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
INFO:
Odin is the ROM Flashing Tool for SAMSUNG smartphones. ROM files flashable with Odin come with .tar extension.
Most of the ROMs you are going to flash with Odin are the official stock Samsung ROMs (or leaked stock ROMs). Custom ROMs are rerely flashable by Odin because they come with .zip extension that Odin does not recognize (it recognizes .tar files).
Custom kernels, however, are sometimes provided in .tar format by their developers (e.g. CF-Root kernels), so that they can be flashed by Odin. When your phone is new and running official firmware you most often cannot flash a custom ROM to it because a Samsung phone often requires a custom recovery and root rights that are included in a custom kernel to be able to flash custom ROMs. That's why Odin often comes in handy in rooting and flashing a custom firmware to your phone because you (often) can flash a custom kernel with it that already includes root and custom recovery and enables you to flash custom firmware (custom ROMs). I use the word "often" very frequently in the previous sentence because every Samsung smartphone is different and requires various procedures for rooting it and flashing custom ROMs (see the section about using Odin below).
If it comes to stock ROMs, the best source of stock (official) Samsung ROM files is located at this excellent website: SamMobile.com/firmwares (link). It requires registration (it's free) and I encourage you to set up an account there because you will most likely use this site several times during your stay at XDA. You will most likely come across 1 .tar or 3 .tar file ROMs there, flashable by Odin. Refer to the Odin flashing guide below for more info.
Below in this thread you can download Odin v3.09, v3.07, v3.06, v3.04, v1.85, v1.83 and all important versions of Odin Multi Downloader.
However, bear in mind that not every Samsung smartphone can be flashed using any Odin version. In fact, for every Samsung smartphone there's a specific Odin version compatible with it. Please refer to the tables below to learn which Odin version is compatible with your phone!
To use Odin with ANY Samsung phone you first need to properly install latest Samsung USB Drivers for Mobile Phones. You can download the drivers in this thread (link). They work for all Samsung smartphones. In that thread there is a full guide on installing the drivers on Win 8/7/Vista/XP x86 & x64.
Click to expand...
Click to collapse
Download:
Code:
[COLOR="Red"][B][SIZE="3"]Mod Edit – Some content removed [/SIZE][/B][/COLOR]
Please say thanks.
Is there allowed to change the window size? I always had a problem with the size of the window on my PC
Sent from my GT-N7100 using xda premium
peter-marvel said:
Is there allowed to change the window size? I always had a problem with the size of the window on my PC
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
This latest version had many improvements but i still doubt the resizing.
You can check yourself though.
What exactly is new in this?
iPTPenguin said:
What exactly is new in this?
Click to expand...
Click to collapse
Button AutoStart
Display Binary Size
Branding button Bootloader, PDA, and Phone to BL, AP, and CP
john3166 said:
Button AutoStart
Display Binary Size
Branding button Bootloader, PDA, and Phone to BL, AP, and CP
Click to expand...
Click to collapse
Thanks
Your welcome mate !
&
on my 150th post, i'll be giving unlimited free web hosting account to whoever posts next !
I'll try this version, thank you mate
Can't wait to try it... Just got my new Note II...still stock
I see your post count is 150... do i get hosting account?
Sent from my GT-N7100 using xda app-developers app
Yea but this offer was for the poster above you ^^
Best tool to flash recovery for me.
Thanks
Sent from my GT-I9300 using XDA Premium 4 mobile app
Your welcome guys !
I'll add more mirrors soon.
thankyou for the latest version. i have been looking for this.
I check virus from Dr.web.
So bad !
Checkingdin3_v3.09_2.rar
Engine version:7.0.5.6250
Total virus-finding records:4503189
File size:1.15 MB
File MD5:974b9ac8f1316cfde37b58a376270d2d
Odin3_v3.09_2.rar - archive RAR
>Odin3_v3.09_2.rar/Odin3_v3.09.exe - archive RAR
>>Odin3_v3.09_2.rar/Odin3_v3.09.exe/Odin3v3.09.exe - Ok
>>Odin3_v3.09_2.rar/Odin3_v3.09.exe/rar.exe - archive NSIS
>>>Odin3_v3.09_2.rar/Odin3_v3.09.exe/rar.exe/script.bin - Ok
>>>Odin3_v3.09_2.rar/Odin3_v3.09.exe/rar.exe/Biyulunu.uki packed by XOREXE
>>>>Odin3_v3.09_2.rar/Odin3_v3.09.exe/rar.exe/Biyulunu.uki infected with Trojan.PWS.Multi.1145
>>>Odin3_v3.09_2.rar/Odin3_v3.09.exe/rar.exe/Fimohara.dll packed by FLY-CODE
>>>>Odin3_v3.09_2.rar/Odin3_v3.09.exe/rar.exe/Fimohara.dll - Ok
>>>Odin3_v3.09_2.rar/Odin3_v3.09.exe/rar.exe/Hojifagije.dll packed by FLY-CODE
>>>>Odin3_v3.09_2.rar/Odin3_v3.09.exe/rar.exe/Hojifagije.dll - Ok
>>>Odin3_v3.09_2.rar/Odin3_v3.09.exe/rar.exe/jojihedaca.dll packed by FLY-CODE
>>>>Odin3_v3.09_2.rar/Odin3_v3.09.exe/rar.exe/jojihedaca.dll - Ok
>>>Odin3_v3.09_2.rar/Odin3_v3.09.exe/rar.exe/_=9A=80\System.dll - Ok
>Odin3_v3.09_2.rar/Odin3.ini - Ok
avira virus alerts
Updated the thread.
Mirror Added.
Virus Alert.
Don't download.
Seriously ?
Working fine in Win8 x64
Seriously ?
Working fine in Win8 x64
Reuploaded the files to mediafie.
Hi Hi, First you, you are amazing ... do not understand how you can have so much knowledge about this.
Well I tell you my problem that I have spent one week in and I can not resurrect.
I stayed on the phone with samsung logo and did nothing mas..le install a room and before I came to end in the odin..ahora only fail I get a screen with a water blank and I can not put him any rom always gives me fail've tried everything and no result. Will help me I would appreciate. from already thank you to everyone s.
In product Name GT-I9300 I get as I have seen here the phone is not dead if it goes ... no?
I can also tell you that going into Downloading mode.
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
get Image Capture to see my screen as it has been
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you
first of all
-were you successful flashing the rom via odin and got a pass sign in green color on odin
-which version of rom are you trying to flash.
jasi275 said:
first of all
-were you successful flashing the rom via odin and got a pass sign in green color on odin
-which version of rom are you trying to flash.
Click to expand...
Click to collapse
Hi Thanks for answering.
I have proven with many Roms and always leaves me FAIL in Odin
I have also tried pit.
And whenever I get FAIL in Odin.
I have proven all Odin and I always get the same. FAIL
do you have kies on your pc if not install it, it will install proper drivers for s3 then odin might start working and one more thing odin only works if your phone is on download mode and the added is written
jasi275 said:
do you have kies on your pc if not install it, it will install proper drivers for s3 then odin might start working and one more thing odin only works if your phone is on download mode and the added is written
Click to expand...
Click to collapse
If you have Kies on the PC does not detect the phone.
if you always put the phone in download mode to connect to Odin
Odin if it detects the phone but always comes FAIL
extract the zip file see see if it is corrupted or use different version of odin like latest or old one
jasi275 said:
extract the zip file see see if it is corrupted or use different version of odin like latest or old one
Click to expand...
Click to collapse
The zip file where?
I have proven with all versions of Odin
mensajero2 said:
The zip file where?
I have proven with all versions of Odin
Click to expand...
Click to collapse
you do have a firmware file don't you the stock android .tar file which is used to flash the firmware via odin extract that
jasi275 said:
you do have a firmware file don't you the stock android .tar file which is used to flash the firmware via odin extract that
Click to expand...
Click to collapse
the S3 samsung firmware I have tried them all and does nothing.
Odin goes into FAIL
are you files in zip format or .tar format you do not get added sign in odin when you put your s3 in download mode is that right
jasi275 said:
are you files in zip format or .tar format you do not get added sign in odin when you put your s3 in download mode is that right
Click to expand...
Click to collapse
The Odin works as the problem is not always grabs any ROM out FAIL.
http://forum.xda-developers.com/galaxy-s3/help/samsung-i9300-flash-odin-error-t1842728 see this thread do you have a problem like this
mensajero2 said:
The Odin works as the problem is not always grabs any ROM out FAIL.
Click to expand...
Click to collapse
You cannot fix this with a software fix this is emmc failure you need a service center see this post >> http://forum.xda-developers.com/galaxy-s3/help/problem-white-screen-black-lines-rain-t2467459 << and the many other posts with same problem.