Related
hello guys im fernando im new to the forum, i would like to get some help with my little problem with my s3... im very sorry about my english spelling...
the problem is that i flashed a custom rom into my phone.. it worked great for the last 5 months or so.... in the past month i installed cyanogenmod 10.1... it was great.. but i have a little situation and i have to sell my s3 (no worries, im getting a new one hehe) but the buyer wants to get the phone with stock samung official rom... i downloaded the lastest official rom but i dont know how to install it and leave the phone like out of the box like new.... can someone help me with the steps on how to get to sotck premium suite samsung official rom from cyanogenmod 10.1??? thank you in advance guys
Hi Fernando.
You should read the basics, how to flash stock ROMs via Odin, there's loads of useful information on here if you look for it. And don't forget to do a factory reset
Glebun said:
Hi Fernando.
You should read the basics, how to flash stock ROMs via Odin, there's loads of useful information on here if you look for it. And don't forget to do a factory reset
Click to expand...
Click to collapse
thanks a lot glebun for your asnwer, but the question is.. i can flash the stock rom with odin normally?.. doesnt matter if i had a previous custom rom and cm10.1?'
No, it doesn't matter, as long as you do a factory reset from recovery right afterwards. Also, they may want to have the flash counter at zero, it can be easily reset, all the info is there for you to read
Glebun said:
No, it doesn't matter, as long as you do a factory reset from recovery right afterwards. Also, they may want to have the flash counter at zero, it can be easily reset, all the info is there for you to read
Click to expand...
Click to collapse
sorry bro me again.. i tried to flash my phone with odin used the .md5 of stock rom plugged the phone everything nice... after a min or so it says fail!... heres the log:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELLC_I9300PHEELL3_I9300XXELLA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> system.img
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
make sure Kies is not running
it worked but....
ty for your ansers and patience... i load the stock rom with odin all went fine but now went it turned on just stays in th samsung logo and keeps repeating the boot samsun image over and over... now i realy dont know what to do help please
flashing rom 101: just flash it like every other rom. put the stock rom on your phone. reboot to cwm recovery. do wipe cache/ wipe davilk cache/ wipe user data-factory reset then flash zip from sd card. look for the rom .zip and flash it.
edit: take the battery out of the phone. put it back in. shoot i just read its stuck on boot loop. yea i dont know. im a noob at that part. well search around the forums or use google.
also maybe look here: http://forum.xda-developers.com/showthread.php?t=2111641
Go into recovery, wipe data and cache.
ty guys but the problem is that when i flashed the custom it doesnt come with CMW so i cant get into recovery to flash a custom or something
just do a factory reset from recovery
Hello,
My Galaxy s2 is stuck in boot loop, I can see only the GS2 logo.
It went into this situation after holding down power button trying to turn it off.
Tried to remove battery and nothing changed.
Entered recovery mode and did wipe cache and then reboot.
It went past the initial logo, showed samsung animation and then it went back to samsung logo boot loop. It never went to samsung animation again.
From that point on it does not boot to recovery mode, it shows the android robot with the spinning cog for a while and then it goes back to the samsung logo boot loop.
The phone can go to download mode without problem. I have not tried to install a stock firmware through odin, since I would like to get a backup of the sms messages from the phone first. I already have backup of pics, contacts, etc so I dont care about anything else besides the sms.
The phone was running the latest spanish stock JB version
GT-I9100 Galaxy S II
PDA: I9100XWLSD
CSC: I9100FOPLS4
MODEM: I9100XXLS8
Added: 2013-02-03
The only modifications to stock were
. Root when it was running ICS
. CSC change from EUR to FOP (so that it auto upgraded to JB from ICS)
The phone retained root after the auto JB upgrade
Do you know if there a solution to this situation? I am still under warranty so I can take it back to samsung so I would like to avoid installing CWM recovery kernel that would make them immediately reject service due to warranty void.
thank you in advance!
Yes, you can keep trying to flash a stock firmware in Odin. Click the link in my signature if you're having troubles with the flash failing. Flash the JB version you were on before, that's got the most chance of working with out having to wipe.
Personally, I think you're going to have to get a working recovery and factory reset to be honest.
Sent from a galaxy far, far away
Hopper8 said:
Yes, you can keep trying to flash a stock firmware in Odin. Click the link in my signature if you're having troubles with the flash failing. Flash the JB version you were on before, that's got the most chance of working with out having to wipe.
Personally, I think you're going to have to get a working recovery and factory reset to be honest.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
thank you for answering, so if I install the same version through Odin, it will not wipe out the current phone contents by default?
Toliver said:
thank you for answering, so if I install the same version through Odin, it will not wipe out the current phone contents by default?
Click to expand...
Click to collapse
Correct. A 1-part firmware will not wipe by default. If you flash a 3-part firmware (JB leak, LSJ for instance) that WILL wipe by default.
If you flash something other than the firmware you were on directly before the bootloop, you've got pretty much no chance of getting out of the bootloop without a factory reset. If you flash the same firmware you were on before the bootloop, then there's a chance of getting it to boot up with all your data.
If that (flashing with the same stock ROM) doesn't work, then I'm afraid its down to a factory reset, sorry.
Hopper8 said:
Correct. A 1-part firmware will not wipe by default. If you flash a 3-part firmware (JB leak, LSJ for instance) that WILL wipe by default.
If you flash something other than the firmware you were on directly before the bootloop, you've got pretty much no chance of getting out of the bootloop without a factory reset. If you flash the same firmware you were on before the bootloop, then there's a chance of getting it to boot up with all your data.
If that (flashing with the same stock ROM) doesn't work, then I'm afraid its down to a factory reset, sorry.
Click to expand...
Click to collapse
Ok then, I will give it a try and see how it goes. Another solution that I was thinking about is to try to install CWM through odin (i'm not sure if it's possible though) then boot into CWM and get backup through it. Then if I apply a stock firmware through odin, this would remove CWM and install the stock recovery kernel back, correct?
Yes, that's possible. You can flash Philz kernel via Odin, it's stock kernel only with root CWM. Other than that its the same. You could do that procedure using his kernel. When you flash stock rom via Odin then yes, you'd get rid of the custom recovery.
Depending on what you want to do (warranty etc) read up about the flash counter and then triangle away.
Sent from a galaxy far, far away
regarding the 1-part firmware, I downloaded from sammobile the I9100XWLSD_I9100FOPLS4_FOP.zip.
The zip archive contains a tar.md5 file I9100XWLSD_I9100FOPLS4_I9100XXLS8_HOME.tar.md5 and a dll file SS_DL.dll.
So I should use only the tar.md5 in the PDA section of odin, right? should I keep this dll in the same folder as the tar.md5 in case odin needs it?
Also does it make any difference which odin version should I use?
thaks again
Well I suppose it can't hurt to put it in the same directory, but I don't know if it really does anything. Yes, flash it in the pda section.. Which version? Take your pick. I usually use 3.0.4 but have also used others. Click my signature if you want a zip file with a few versions.
Sent from a galaxy far, far away
I tried flashing the same rom as it was installed but nothing changed, after the first boot I see the robot with the cog, a thin progress bar filling below it and then it goes to boot loop. No luck getting into recovery, still the same symptom... Besides the sms backup I am thinking about how to recover it, should I try installing 4.0.3 that was the factory default? Any more ideas??
thanks again
The odin log seems clean though, no error or anything else
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100FOPLS4_I9100XXLS8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> cache.img
<ID:0/007> NAND Write Start!!
<ID:0/007> factoryfs.img
<ID:0/007> hidden.img
<ID:0/007> modem.bin
<ID:0/007> boot.bin
<ID:0/007> param.lfs
<ID:0/007> Sbl.bin
<ID:0/007> zImage
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/007> Removed!!
And can you try a factory reset from the stock recovery? You're not on 4.0.4 so it'll be safe.
@gastonw, can you have a look here? I know that I've seen Odin passing but still no boot... I just can't remember how on earth it was fixed. It seems I didn't bookmark it either.
Sent from a galaxy far, far away
Hopper8 said:
And can you try a factory reset from the stock recovery? You're not on 4.0.4 so it'll be safe.
@gastonw, can you have a look here? I know that I've seen Odin passing but still no boot... I just can't remember how on earth it was fixed. It seems I didn't bookmark it either.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Could you provide more details on how to do a factory reset from stock recovery? Do you mean to flash 4.0.3 via odin? Or is it some options in odin that would enforce factory reset?
More details are to search for it mate. It's covered so many times that it's just plain spoonfeeding if I'm to post it.
Sent from a galaxy far, far away
Eventually I made it work by installing the 4.0.3 EUR via odin. I did not allow it to boot into the OS, as soon as it finished flashing via odin, I rebooted into recovery mode. This time it went in successfully. Then I used the CWM recovery kernel that just runs from the sd (it does not install) and got the full backup. Later on by using nandroid manager I recovered the sms messages + more (apps, etc). Thanks for all the help!
Hey Guys,
I'm sure all of you get lots of these questions, however I have been trying for a couple of days to get this S3 going so I can just asking for help.
My main issue is I cannot flash any ROM's via Odin.
Here is some background infomation:
I started with a stock Galaxy S3 GT-i9300 International 16GB model.
Flashed the correct version of Cyanogen Mod for my Model/Sub Model.
I install this rom by flashing CWM (Clock Work Recovery Mod) and installing the update.zip from my external SD card.
I have done this before with other Samsung devices, No big deal, just factory rest and wipe the davik cache and flash the new ROM.
Well I decided to backup the original ROM via CWM's backup option. The backup completed fine but I backed it up to the phones internal storage instead of my External SD card. The new ROM worked fine till it ran out of space. So I selected the Delete option back in CWM to remove the backup file, rebooted the phone only to find I was still using 8 or so GB of storage.
So my phone was not happy. No room to download updates or save new pictures, etc.
This week I decided to flash the stock ROM back over the phone. For some reason the firmware was incorrect for that model or something was wrong with the phone.
After looking around I decided to flash a .pit file for the Galaxy S3, One problem, I did not know that different storage sizes of S3's have different .PIT files. However it flash and I still could not restore my phones ROM.
So after a few days of looking around I downloaded the stock ROM from Sam-Mobile.com for my phone and country and download GT-I9300_mx_20120220 PIT for for what I read and understood was for a 16GB GT-I9300.
So the new PIT file flashes fine, however I still cannot flash any new ROMS. I have tired the stock rom from Sam-Mobile or trying to flash Recovery-cwmtouch-6.0.3.2-GTI9300.tar (clock work recovery mod).
None of these flash. Odin3.04 just sits on "NAND Write Start!!" and there is a blue "downloading" bar that is across the screen and that's it.
Nothing else happens. I have also attached a screen shot of this.
I have a water damaged 16GB GT-i9300T that I have used to create a .PIT file from Heimdall, But that sits there for about 10 Min before Odin says "Unable to get pit map"
I have also tried this: http://forum.xda-developers.com/showthread.php?t=1916796
I get all the way to shorting out the resistor (R313) on the PCB but the phone does not turn on and fails to display "SD Card Mode"
So, can anyone help me?
I know it might be a long shot but at this point I'm willing to try anything. Any ideas would be much appreciated.
Cheers
Mitchell
Flashing just a pit file usually results in a hard brick.
You can try a rescue firmware:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6&nocache=1&z=2665989794768393
But you probably need a new motherboard.
Thanks for that!, The recovery firmware failed to flash but the pit file flashed allowing me to install Cyanogen Mod.
Thanks for your help on this one :good:
boomboomer said:
Flashing just a pit file usually results in a hard brick.
You can try a rescue firmware:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6&nocache=1&z=2665989794768393
But you probably need a new motherboard.
Click to expand...
Click to collapse
I. Need help to...my s3 its stuck at samsung logo. I dont have recovery. Just download Mode..i try to flash pit and no flash. Roms nand write fail. Some pits just say get pit mapping but nothing happens. Kies dont flash just 0%...how can i unbrick the iPhone please need help
Did u fix !!!
leo_hacker82 said:
I. Need help to...my s3 its stuck at samsung logo. I dont have recovery. Just download Mode..i try to flash pit and no flash. Roms nand write fail. Some pits just say get pit mapping but nothing happens. Kies dont flash just 0%...how can i unbrick the iPhone please need help
Click to expand...
Click to collapse
Did u fix ur phone??? same problem happend me
You're using the original Samsung USB cable?
audit13 said:
You're using the original Samsung USB cable?
Click to expand...
Click to collapse
yes.
What file is failing in Odin?
jtk585 said:
Did u fix ur phone??? same problem happend me
Click to expand...
Click to collapse
For getting error when flash in Odin no matter what kind of error. Just need to flash out and repartition it for pit file and you get back yours phone back. The problem is the pit file must be suit to flash your phone. If not no matter how you flash it still the same.
Yumiko87 said:
For getting error when flash in Odin no matter what kind of error. Just need to flash out and re-partition it for pit file and you get back yours phone back. The problem is the pit file must be suit to flash your phone. If not no matter how you flash it still the same.
Click to expand...
Click to collapse
thanks.
i tried many time. i try to do partition also. that time partition error is occur.
i connect with kies, i tried recovery , firmware not downloadind to my device it's stuck on 0 % , then i use that download original firmware that file in odin v3.9 , to v 11 :laugh: tried all odin. i think emmc is corrupted..!!
anyway my phone is bricked so i used every button on odin ...:laugh::laugh:
i tick T.Flash ,that time no error occur, downloaded , but nothing happened.
thanks. any chance to enable debugging mode in recovery mode.
jtk585 said:
thanks.
i tried many time. i try to do partition also. that time partition error is occur.
i connect with kies, i tried recovery , firmware not downloadind to my device it's stuck on 0 % , then i use that download original firmware that file in odin v3.9 , to v 11 [emoji23] tried all odin. i think emmc is corrupted..!!
anyway my phone is bricked so i used every button on odin ...[emoji23][emoji23]
i tick T.Flash ,that time no error occur, downloaded , but nothing happened.
thanks. any chance to enable debugging mode in recovery mode.
Click to expand...
Click to collapse
So now you still able to go download mode without error? I mean when you connect to odin it's work for You?
Yumiko87 said:
So now you still able to go download mode without error? I mean when you connect to odin it's work for You?
Click to expand...
Click to collapse
thanks
download mode working perfectly . all time.
odin only install my device when i tick T.flash. i cant install normal way
after installation nothing change. that is it.
actually i don't know what is the use of T.Flash :laugh:
thanks
jtk585 said:
thanks
download mode working perfectly . all time.
odin only install my device when i tick T.flash. i cant install normal way
after installation nothing change. that is it.
actually i don't know what is the use of T.Flash [emoji23]
thanks
Click to expand...
Click to collapse
So the installation successful until come out with pass in Odin? But it's doesnt change is revert to download mode?
Yumiko87 said:
So the installation successful until come out with pass in Odin? But it's doesnt change is revert to download mode?
Click to expand...
Click to collapse
yes PASS..! but nothing change on device
if i going to change motherboard, is my device work?
can i install any country firmware ?
bcoz motherboard get under 30 dollar. i know how to fix
so total cost is 30 cowboy:
i forget say one thing, when i choose boot loader file BL sboot.bin file is stuck... freeze.....
jtk585 said:
yes PASS..! but nothing change on device
if i going to change motherboard, is my device work?
can i install any country firmware ?
bcoz motherboard get under 30 dollar. i know how to fix
so total cost is 30 cowboy:
Pls refer to this before you go for hardware issues.
http://forum.xda-developers.com/showthread.php?t=2120726
Click to expand...
Click to collapse
Pls refer to this before you go for hardware issues.
http://forum.xda-developers.com/showthread.php?t=2120726[/QUOTE]
thanks..
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin engine v(ID:3.1203)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> sboot.bin
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
this is happening my device.
i think emmc is corrupted or my bootloader is locked.. nothing write on
jtk585 said:
Pls refer to this before you go for hardware issues.
http://forum.xda-developers.com/showthread.php?t=2120726
Click to expand...
Click to collapse
thanks..
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin engine v(ID:3.1203)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> sboot.bin
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
this is happening my device.
i think emmc is corrupted or my bootloader is locked.. nothing write on [/QUOTE]
Try both:http://cloud.tapatalk.com/s/580ff78a7f0a7/N9005XXUENB4_N9005DBTENB1_DBT_PIT.zip
http://cloud.tapatalk.com/s/580ff790b5dbe/SM-N9005 OXX pit.zip
If still failed sry to tell you need to change motherboard aredy. As I faced such issues on my n3 and I able to recovery well using my pit files via Odin without fail. So might be your hardware problem aredy.
The sboot.bin file is not flashing because the rom is either not for the phone or the phone bootloader is too new.
Are you a using the original USB cable?
audit13 said:
The sboot.bin file is not flashing because the rom is either not for the phone or the phone bootloader is too new.
Are you a using the original USB cable?
Click to expand...
Click to collapse
Thanks..
yes dude
Original USB Cable
S3 GT-I9305 LTE
Kit kat 4.4.4. EVR EE Europe international Firmware
i did root this phone
i think bootloader not allowed to write anything on it or corrupted
what you think ??
---------- Post added at 09:59 AM ---------- Previous post was at 09:56 AM ----------
Try both:http://cloud.tapatalk.com/s/580ff78a7f0a7/N9005XXUENB4_N9005DBTENB1_DBT_PIT.zip
http://cloud.tapatalk.com/s/580ff790b5dbe/SM-N9005 OXX pit.zip
If still failed sry to tell you need to change motherboard aredy. As I faced such issues on my n3 and I able to recovery well using my pit files via Odin without fail. So might be your hardware problem aredy.[/QUOTE]
can i use this pit or firmware on my GT-I9305 device
is it work?
thanks
jtk585 said:
Thanks..
yes dude
Original USB Cable
S3 GT-I9305 LTE
Kit kat 4.4.4. EVR EE Europe international Firmware
i did root this phone
i think bootloader not allowed to write anything on it or corrupted
what you think ??
---------- Post added at 09:59 AM ---------- Previous post was at 09:56 AM ----------
Try both:http://cloud.tapatalk.com/s/580ff78a7f0a7/N9005XXUENB4_N9005DBTENB1_DBT_PIT.zip
http://cloud.tapatalk.com/s/580ff790b5dbe/SM-N9005 OXX pit.zip
If still failed sry to tell you need to change motherboard aredy. As I faced such issues on my n3 and I able to recovery well using my pit files via Odin without fail. So might be your hardware problem aredy.
Click to expand...
Click to collapse
can i use this pit or firmware on my GT-I9305 device
is it work?
thanks[/QUOTE]
This will only for n9005. Not 9305.
Hi, im a noob user about roms and root, and 1 week ago i had a problem flashing roms, i flashed shostock3 with rom manager (i didnt know that i could be dangerous in my phone) after flashing shostock i decided to flash a kernel, but when i tried to reboot recovery mode in rom manager the phone turned off, and when i try to turn it on stops in "samsung galaxy s2" logo, the good news is i can acess download mode.
Does anyone know how to solve this problem?
Thanks.
gecafe said:
Hi, im a noob user about roms and root, and 1 week ago i had a problem flashing roms, i flashed shostock3 with rom manager (i didnt know that i could be dangerous in my phone) after flashing shostock i decided to flash a kernel, but when i tried to reboot recovery mode in rom manager the phone turned off, and when i try to turn it on stops in "samsung galaxy s2" logo, the good news is i can acess download mode.
Does anyone know how to solve this problem?
Thanks.
Click to expand...
Click to collapse
In download mode you can install the last stock 4.1.2 Jelly Bean UCMD8 firmware using the program Odin follow this complete tutorial :
http://www.android.gs/flash-android...d8-update-for-the-att-samsung-galaxy-s2-i777/
After installing the stock ROM root your phone in this way:
1-Download Framaroot apk file into your device.
2-Go to Menu—>Download, locate the Frameroot apk file.
3-Press on Frameroot apk file in the Download folder. A pop-out windows ask for confirmation, press confirm/yes to proceed with Framaroot installation.
4-Once Framaroot successfully installed on your device, you shall find Framaroot icon in the Menu.
5-Press on Framaroot icon in Menu to launch the app.
6-In Framaroot user interface, choose Aragorn exploits within the list of exploits.
7-You shall now receive a exploit results: “Success… Superuser and su binary installed. You have to reboot your device”
Sent from my SGH-I777 using xda app-developers app
Flashing with odin this happened
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> boot.bin
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
gecafe said:
Flashing with odin this happened
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> boot.bin
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try again use Odin3 v.1.85
Sent from my SGH-I777 using xda app-developers app
pepe100 said:
Try again use Odin3 v.1.85
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
That's what i used, but im gonna install it again
Still failing, downloaded another odin3 1.85, run it as administrator but didnt work.
what else should i try?
gecafe said:
Still failing, downloaded another odin3 1.85, run it as administrator but didnt work.
what else should i try?
Click to expand...
Click to collapse
I'm not sure what rom manager does to the memory, but I think the phone can be recovered.
Please delete rom manager from your I777 and never use it on this phone, as it is not compatible.
Try the following sequence to see if this will clear the problem:
Odin3 v1.85 is recommended.
Steps 1 & 2 in sequence without rebooting if possible.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning.
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
You may need to enter recovery and perform a wipe data/factory reset, either before, during or after these two steps.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
creepyncrawly said:
I'm not sure what rom manager does to the memory, but I think the phone can be recovered.
Please delete rom manager from your I777 and never use it on this phone, as it is not compatible.
Try the following sequence to see if this will clear the problem:
Odin3 v1.85 is recommended.
Steps 1 & 2 in sequence without rebooting if possible.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning.
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
You may need to enter recovery and perform a wipe data/factory reset, either before, during or after these two steps.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
Click to expand...
Click to collapse
Thanks mate im gonna try it, but how do i get recovery mode, i tried to do it but it didn't work, i tried this:
Press volume+ and volume- at the same time 5 seconds and later press power button, i always get to the download mode.
OK guys, i have not solved my problem but i could investigate something thanks to my friend's i777 phone, and this is:
I noticed he had Rom manager, and he said he uses it lot of times and his phone have not gotten a problem, so i tried the rom magager recovery mode (what i tried and f***** my phone), the phone worked great and did not have any problem, after trying lot of things i decided to use the NQ antivirus, and it detected the rom manager as a virus and dangerous app i had to uninstall, actually just tried it in a i777 phone, tomorow i'll try on a different phone to see if this is normal.
Im gonna keep investigating about what rom manager does after solving my problem.
creepyncrawly said:
I'm not sure what rom manager does to the memory, but I think the phone can be recovered.
Please delete rom manager from your I777 and never use it on this phone, as it is not compatible.
Try the following sequence to see if this will clear the problem:
Odin3 v1.85 is recommended.
Steps 1 & 2 in sequence without rebooting if possible.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning.
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
You may need to enter recovery and perform a wipe data/factory reset, either before, during or after these two steps.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
Click to expand...
Click to collapse
No matter what i do, Odin is still failing, so i havent been able to do anything, well the stock GB from the download repository got stuck in setupconnection, i dont know what to do, i don want to pay for fixing my phone.
Practically every post in this thread from people trying to help you are the answers you need. Your instance on continuing to use Rom Manager on this phone, even after you've been warned about it, AND there's been a sticky regarding the dangers for nearly 2 years, are simply incredible!
If you can't get Odin to work (something as simple as trying the USB port in the back of the computer may work), your only option is to pay someone to fix it for you.
And by the way, entering recovery for the i777 is all three buttons at the same time, then releasing them once the boot logo appears.
gecafe said:
No matter what i do, Odin is still failing, so i havent been able to do anything, well the stock GB from the download repository got stuck in setupconnection, i dont know what to do, i don want to pay for fixing my phone.
Click to expand...
Click to collapse
You need to try a different known good usb cable, or different ports on the computer, or even a different computer to see if you can get Odin to complete. If you are absolutely sure that the reason Odin does not complete is not due to the above, then you may have a firmware problem that is beyond my ability to help you, or you may have some kind of hardware issue.
If it were my phone, I would probably send it to Mobile Tech Videos, since they are reliable and very good, but if you are not willing to spend money, then I don't have anything else to suggest.
Edit: It occurred to me that you may not have followed the full sequence. Did you get to step 4, and if not you need to try to flash the sbl.tar by itself in the pda slot and then go back to step 1.
I have been there...
This has happened to me a couple of times. You can either do a complete flash of a stock rom and go from there, OR, you can flash a recovery kernel. There is an old Sylah image floating around. You can flash this with the Odin tool. I believe Odin 3.07 worked best for me.
SteveMurphy said:
Practically every post in this thread from people trying to help you are the answers you need. Your instance on continuing to use Rom Manager on this phone, even after you've been warned about it, AND there's been a sticky regarding the dangers for nearly 2 years, are simply incredible!
If you can't get Odin to work (something as simple as trying the USB port in the back of the computer may work), your only option is to pay someone to fix it for you.
And by the way, entering recovery for the i777 is all three buttons at the same time, then releasing them once the boot logo appears.
Click to expand...
Click to collapse
First of all is im a newbie in XDA i saw the warning when i joined, it seems u got mad, if u cant be patient with a noob, dude just let others help me.
Thanks im gonna try another pc and cable.
I have the i9300 but when I boot up into download mode it says PRODUCT NAME: SGH-T999 (not my model, though). I think this is because I accidently installed the SGH-T999 version of cyangomenod.
So to try to fix it, I used odin 3.07 and the
"I9300ZSEMC1"
stock rom file to try to put it back onto stock. Odin "stopped working" and crashed and I soft-bricked my phone (Firmware upgrade encountered an issue message at boot).
I tried again using I9300XXEMC3 stock rom, but odin 3.04 says
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> tz.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
And fails. My phone says "unsupported dev_type" in red.
Can I please get some guidance? I don't know what I did wrong. What rom should I flash with odin? Should I try to flash the SGH-T999 stock rom with odin?
zhinkk said:
I have the i9300 but when I boot up into download mode it says PRODUCT NAME: SGH-T999 (not my model, though). I think this is because I accidently installed the SGH-T999 version of cyangomenod.
So to try to fix it, I used odin 3.07 and the
"I9300ZSEMC1"
stock rom file to try to put it back onto stock. Odin "stopped working" and crashed and I soft-bricked my phone (Firmware upgrade encountered an issue message at boot).
Can I please get some guidance? I don't know what I did wrong. What rom should I flash with odin? Should I try to flash the SGH-T999 stock rom with odin?
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showthread.php?t=2535367
Hope it help.
TheoDores said:
Try this: http://forum.xda-developers.com/showthread.php?t=2535367
Hope it help.
Click to expand...
Click to collapse
I tried following those instructions. I managed to flash the .PIT file. Now I don't see the error message at boot, my screen is just black. BUT I can "sorta" boot into recovery mode (starting recovery message shows for one second, then black screen again). So I'm still stuck.
I can STILL boot into download mode though. And if I try to use CF-Root Odin fails again (same error) and my phone says "unsupported_devtype".
Flash stock rom via Odin .
But flashing a wrong firmware for a different phone may well be a lot more than a soft brick
Did you also flash wrong recovery ???
JJEgan said:
Flash stock rom via Odin .
But flashing a wrong firmware for a different phone may well be a lot more than a soft brick
Did you also flash wrong recovery ???
Click to expand...
Click to collapse
Everytime I flash the stock rom odin fails and phone says "unsupported dev_type". In Download mode it says my phone model is T999, but it's actual GT-I9300.
And I don't think I did. I think I had clockwork mod recovery, I'm not too sure though.
You have flashed at least the T999 bootloader, which is why it says that in download mode. If flashing a full i9300 stock rom doesn't help then you'll need a new motherboard.
boomboomer said:
You have flashed at least the T999 bootloader, which is why it says that in download mode. If flashing a full i9300 stock rom doesn't help then you'll need a new motherboard.
Click to expand...
Click to collapse
That really depresses me. Are you sure this is the only solution? Because I remember when my phone WAS working I booted into download mode once and it said the same "T999 Model" and I could still use it. This only happened after I tried flashing the stock i9300 stock rom.
I think it's the cyanogenmod installer that flashed this T999 bootloader for me. When I used the cyanogenmod installer it detected my phone as a AT&T phone and I was dumb enough to click "install" thinking it would work for all galaxy S3's.
I think this guide is exactly what I need (since it restores bootloader), but I can't seem to complete all the steps: http://forum.xda-developers.com/showthread.php?t=2535367
I get to #5 but once I try to install CF-ROOT through odin it says the same unsupported dev type error on my phone.
This is the error I get when trying to use CF-ROOT through Odin3 v1.85:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
(along with the red "Unsupported dev_type" on my phone in download mode).
I think it was already rooted though, maybe someone could help me reinstall the recovery (cwm) so I can install the bootloader from that guide I just linked?
Best option is to try a rescue firmware, which might help:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6&nocache=1&z=8215224728919566
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Best option is to try a rescue firmware, which might help:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6&nocache=1&z=8215224728919566
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Will this delete my EFS? I remember I backed up efs with this guide: http://forum.xda-developers.com/showthread.php?t=1852255
I did: "adb reboot nvbackup"
By restoring to "complete" factory settings, won't this efs be deleted? Can I still backup my efs in my 'soft brick' mode I'm in?
Alright, I've tried using the rescure firmware and all the files, but every time I try I get it a FAIL on odin:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_I9300OXAEMG4_KOR_FACTORY_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And my phone says in red "SECURE CHECK FAIL : PIT".
I've spent 12 hours on this now...
Did you try Kies yet?
Do you still have a custom recovery?
I'm not sure about that adb nvbackup you have done. As far as i know it's only for Qualcomm chipsets not Exynos. Maybe you have severely damaged the device. But try Kies first or if you still have root access with recovery try to flash the bootloader manually.
If everything fails contact the low level guys like @AdamOutler or @Entropy512. They might be your last hope.
DualJoe said:
Did you try Kies yet?
Do you still have a custom recovery?
I'm not sure about that adb nvbackup you have done. As far as i know it's only for Qualcomm chipsets not Exynos. Maybe you have severely damaged the device. But try Kies first or if you still have root access with recovery try to flash the bootloader manually.
If everything fails contact the low level guys like @AdamOutler or @Entropy512. They might be your last hope.
Click to expand...
Click to collapse
I tried Kies on two different computers, but whenever I connect my S3 it just says "connecting" forever and never connects to my phone. Tried solutions online, couldn't get it to work.
And I have root access, but can't boot into recovery (says "recovery booting" for a few seconds then goes black screen). So I don't know if I can flash the bootloader manually, unless I did it with odin.
And those seem like busy developers, would they really have time for me? I don't even know what I would ask. :S
Sorry I seem so clueless, I'm just upset/sad/confused/everything right now. Saved up for this phone for a while.
Try to flash the bootloader only. There are different ones. Maybe you need one that is not blacklisted if that's even possible.
Last option that comes to my mind is an external jtag flasher. Maybe you have a local service shop or similar in your area that could help with that.
DualJoe said:
Try to flash the bootloader only. There are different ones. Maybe you need one that is not blacklisted if that's even possible.
Last option that comes to my mind is an external jtag flasher. Maybe you have a local service shop or similar in your area that could help with that.
Click to expand...
Click to collapse
Hmm when I had a functional phone it said I had the ZSEMC1 stock rom, so the "bootLoader_ZSEMC1.tar.md5" flashed from odin should work? I got it off this thread: http://forum.xda-developers.com/showthread.php?t=2189063
But I don't know if I'm still on ZSEMC1 since I flashed XXEMC3 with odin (but I think it failed) and I got soft bricked.
What could go wrong? Could I hard brick it by installing that bootloader?
I have no clue but i think all I9300 bootloaders would be ok. Your problem probably is rather to find one that gets accepted. Try the latest one for I9300. There is a thread with different bootloaders somewhere here i guess.
Also try to flash a custom recovery like twrp or cwm. I'm not sure if official tools like odin have a separate bootloader check that prevents cross model flashing. No one really knows how you did that. Maybe it's necessary to be done with dd.
DualJoe said:
I have no clue but i think all I9300 bootloaders would be ok. Your problem probably is rather to find one that gets accepted. Try the latest one for I9300. There is a thread with different bootloaders somewhere here i guess.
Also try to flash a custom recovery like twrp or cwm. I'm not sure if official tools like odin have a separate bootloader check that prevents cross model flashing. No one really knows how you did that. Maybe it's necessary to be done with dd.
Click to expand...
Click to collapse
I tried the ZSEMC1 and XXEMC3 and XXEMG5 bootloaders from this thread and they didn't work: http://forum.xda-developers.com/showthread.php?t=2189063
(shows unsupported dev type)
How do I get the 'latest' boot loader? That thread is the only one I could really find.
And also I did try installing cwm through odin. It didn't "fail" but it doesn't work when I try to boot into recovery. I'm guessing this has to do with my locked bootloader?
Really don't know what to do at this point. :/
New motherboard if you have tried the fixes .
Check if 'adb shell' is working in recovery nevertheless. Maybe it's just a display issue in cwm. Also try twrp.
If all that fails go to a mobile shop near you asking for a jtag flash. It shouldn't be too expensive or something. Hardest part is probably to find one locally...
DualJoe said:
Check if 'adb shell' is working in recovery nevertheless. Maybe it's just a display issue in cwm. Also try twrp.
If all that fails go to a mobile shop near you asking for a jtag flash. It shouldn't be too expensive or something. Hardest part is probably to find one locally...
Click to expand...
Click to collapse
I tried cwm and twrp. They both install successfully on odin but have the same "recovery starting...." message and they don't work. I've tried connecting the USB when it's in this "recovery" mode but my computer doesn't detect it so I can't start up adb and interface with it.
And also, I doubt I'm going to be able to find any in northwest ohio.I wonder if this service is any good?
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
Looks promising for $50.
Sorry I've been on this problem for so long guys, I'm just stubborn and can't get over the fact that it's a software brick and I need to replace hardware. :/