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!
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, i flashed my s3 to Omega rom then after trying to restore my EFS using Hc-ktool, now my phone is stuck at boot logo and failed to load, i tried to restore my phone to stock firmware using ODIN but still the same. still stuck at samsung galaxy logo. any ideas?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMA2_I9300XEFELL1_I9300XXELKB_HOME.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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> tz.img
<ID:0/003> NAND Write Start!!
<ID:0/003> sboot.bin
<ID:0/003> system.img
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Boot into recovery and factory reset.
boomboomer said:
Boot into recovery and factory reset.
Click to expand...
Click to collapse
i tried it still no luck :crying:
try flashing a custom recovery(CWM touch or PHILZ) and then making a full wipe from recovery.
sriram231092 said:
try flashing a custom recovery(CWM touch or PHILZ) and then making a full wipe from recovery.
Click to expand...
Click to collapse
i made a full wipe/factory reset, dalvik cache, wipe cache partition still not working. could this be a hardware issue?
d_tan10 said:
i made a full wipe/factory reset, dalvik cache, wipe cache partition still not working. could this be a hardware issue?
Click to expand...
Click to collapse
Download the firmware agin .
Flash stock rom to test hardware after a full wipe
JJEgan said:
Download the firmware agin .
Flash stock rom to test hardware after a full wipe
Click to expand...
Click to collapse
i downloaded a new stock firmware again from sammobile.com now im having boot loops. putting it back to stock firmware should fix the problem but mine doesnt.
d_tan10 said:
i downloaded a new stock firmware again from sammobile.com now im having boot loops. putting it back to stock firmware should fix the problem but mine doesnt.
Click to expand...
Click to collapse
which f/w did you flash? did you factory reset immediately after flashing the f/w?
sriram231092 said:
which f/w did you flash? did you factory reset immediately after flashing the f/w?
Click to expand...
Click to collapse
I9300XXEMG4_I9300XEFEMG2_I9300XXEMG4_HOME.tar.md5
Yes i did a factory reset/data wipe using stock recovery
d_tan10 said:
I9300XXEMG4_I9300XEFEMG2_I9300XXEMG4_HOME.tar.md5
Yes i did a factory reset/data wipe using stock recovery
Click to expand...
Click to collapse
now that is odd! restoring EFS should have bricked the phone! but that's not a hard brick. as you have flashed XXEMG4, now you have a chance of flashing a f/w newer than that(like XXEMG5 or XXMEG6)! try flashing either of these. if the problem still persists, send it to service center.
:good:
have you tried removing the battery for a few minutes ?
sriram231092 said:
now that is odd! restoring EFS should have bricked the phone! but that's not a hard brick. as you have flashed XXEMG4, now you have a chance of flashing a f/w newer than that(like XXEMG5 or XXMEG6)! try flashing either of these. if the problem still persists, send it to service center.
:good:
Click to expand...
Click to collapse
Yes i can flash stock firmware using Odin also able to install Custom rom using CWM. the problem is just the booting up, im downloading I9300XXEMG6_I9300PHNEMG2_PHN.zip now. Do you think the service center will repair my phone even if they see i have flash counts?
ashraf sharif said:
have you tried removing the battery for a few minutes ?
Click to expand...
Click to collapse
Yes, i took the battery,SIM,memory card out and put it back
have you tried kies? if not do this, BEFORE CONNECTING PHONE TO PC start kies go to upgrade and initialisation. enter your phone model number and serial number. put phone in download mode, vol down +home+power NOW CONNECT PHONE TO PC. this should force kies to upgrade your firmware
d_tan10 said:
Yes i can flash stock firmware using Odin also able to install Custom rom using CWM. the problem is just the booting up, im downloading I9300XXEMG6_I9300PHNEMG2_PHN.zip now. Do you think the service center will repair my phone even if they see i have flash counts?
Click to expand...
Click to collapse
they will repair what ever may happen to your phone but will charge you. did you try flashing CM10.2 roms or aosp custom roms?
since odin is not solving your issue than perhaps kies may fix it. i would try kies before service center as it probably will work .even if it does not solve the looping it would leave your phone with official status and may even allow you to get your phone fixed under warranty. after all kies and ota updates are the only official ways to upgrade your firmware under warranty.
Ok thanks, ill keep you guys posted on the status of my phone
XXEMG6 didnt work for me still stuck on the boot loop and also samsung kies, is there any other way i can fix my phone before going to the service center?
maybe flash an emergency firmwareRescue http://forum.xda-developers.com/showthread.php?t=1825272 these firmwares have pit partitions if you flash pit better make sure its the right one
d_tan10 said:
XXEMG6 didnt work for me still stuck on the boot loop and also samsung kies, is there any other way i can fix my phone before going to the service center?
Click to expand...
Click to collapse
send it to SC before something very bad happens to your phone. you should've been careful while flashing. hope you get your phone in a good working condition.
:good:
I will not go into detail but suffice to say I was running my Samsung Galaxy S3 GT-I9300 on a stock Samsung Android 4.1.2 ROM and it was rooted and had a custom CWM Recovery.
I then flashed to CM 10.0.0 but encountered problems and tried to revert to my original ROM. This resulted in my phone displaying the initial black background boot screen with the words "Samsung Galaxy SIII GT-I9300". It stuck there and I could not switch it off nor could I get into Recovery Mode.
I was able to get into Download mode and connect to Odin to reflash my original ROM but Odin continually got stuck in the process at "Setup Communication" and on the odd occasion it got past that it then stuck on "Get Pit Mapping".
After much research of this and other forums found one lone article about Samsung introducing new ROMS from July 2013 onwards which had efs2 and that once upgrading to an efs2 ROM you could not go back to a previous efs1 ROM which I think I tried to do.
I eventually decided therefore to bite the bullet and I downloaded GT-I9300.pit and flashed it using Odin with Re-Partition selected. I was then able to flash Samsungs latest Android 4.3 (I9300XXUGMK6) ROM for the I9300.
The result is that whilst the phone is again fully functional I am unable to install a custom recovery nor can I root my phone.
I thought that if I used the GT-I9300.pit file it would re-partition the phone as a I9300 should be partitioned but it seems I was wrong.
I am happy with my phone now that I have recovered it but would like to be able to backup my rom but I need root to do that. Does anyone know what I have done with my phone and are you able to advise as to how I might now root it again?
Thanks
matrixmainframe said:
I am happy with my phone now that I have recovered it but would like to be able to backup my rom but I need root to do that. Does anyone know what I have done with my phone and are you able to advise as to how I might now root it again?
Thanks
Click to expand...
Click to collapse
After flashing the stock rom when coming from a custom rom is always best to do a factory reset to clear the phone.
You can root with CF auto root from my signature it works perfectly well on stock 4.3 MK6, then use TWRP or Philz recovery both are in the Dev section
ag4751 said:
After flashing the stock rom when coming from a custom rom is always best to do a factory reset to clear the phone.
You can root with CF auto root from my signature it works perfectly well on stock 4.3 MK6, then use TWRP or Philz recovery both are in the Dev section
Click to expand...
Click to collapse
When I try to flash a recovery or try to root I get the following.
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-m0-m0xx-gti9300.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> Get PIT for mapping..
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
As you can see from the above it looks as though the process falters at "<ID:0/003> Get PIT for mapping.." which would appear to have something to do with the fact that I had to re-partition using GT-I9300.pit and that is what prompted my question in the first place.
It appears to me that the GT-I9300.pit file has altered my partitions in a non I9300 way despite having I9300 in the filename and that is why I posted the question in the hope someone would know what I had done and hopefully know a way I could either reverse what I had done or suggest a way to root despite my apparently new partition format?
matrixmainframe said:
When I try to flash a recovery or try to root I get the following.
It appears to me that the GT-I9300.pit file has altered my partitions in a non I9300 way despite having I9300 in the filename and that is why I posted the question in the hope someone would know what I had done and hopefully know a way I could either reverse what I had done or suggest a way to root despite my apparently new partition format?
Click to expand...
Click to collapse
Have a look here then you my be able to recover your device, it is Korean based so will default to KOR not BTU but it could repair the PIT problem if that is what you have.
ag4751 said:
Have a look here then you my be able to recover your device, it is Korean based so will default to KOR not BTU but it could repair the PIT problem if that is what you have.
Click to expand...
Click to collapse
Please read my initial post(#1).
I have already recovered my phone and it is working correctly on Samsung Official Stock 4.3 ROM (Android 4.3 - I9300XXUGMK6) EXCEPT that I cannot flash a custom Recovery nor can I root the phone. I have several apps that only operate on a rooted phone so just rooting it without a custom recovery would suffice.
If someone tells me that it is no longer possible to root my phone then I will be disappointed but I can live with it. I just thought someone might know the answer.
That problem in Odin might be related to incorrect drivers for your phone.
Remove any kies or Samsung softwares and reboot pc. Reinstall kies and connect phone 2 pc for drivers install. Then try a different usb port to flash smth on the phone.
Trimis de pe al meu GT-I9300 folosind Tapatalk
matrixmainframe said:
Please read my initial post(#1).
I have already recovered my phone and it is working correctly on Samsung Official Stock 4.3 ROM (Android 4.3 - I9300XXUGMK6) EXCEPT that I cannot flash a custom Recovery nor can I root the phone. I have several apps that only operate on a rooted phone so just rooting it without a custom recovery would suffice.
If someone tells me that it is no longer possible to root my phone then I will be disappointed but I can live with it. I just thought someone might know the answer.
Click to expand...
Click to collapse
I think i had the same problem with rooting and done reinstalling drivers and change the port so it is now rooted.
Also try unticking autoreboot then after the instalation is done disconnect the phone and remove/reinsert battery and boot to recovery so the auto root files start to install...
Of course everything you do is at your own risk...
BR
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. :/
How can I fix this? I want to go back to stock. No root. Please see below.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> param.bin
<ID:0/003> recovery.img
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!
I need help with this ASAP.
If you haven't found it already, go to Droidstyle's Restore Guide here: ( http://forum.xda-developers.com/showthread.php?p=34891181 ). Section 1b has step by step instructions on how to restore the phone. Make sure you use the pit file with the correct firmware version when doing the restore.
Unless you have a Note 2 that never had a firmware update since the phone's release in 2012, then you can't use the VRALJB stock restore image. Droidstyle warned that it would fail at sboot.bin if you try it. Also, if you ever upgraded to 4.4.2, then you can't downgrade back to 4.3 or 4.1.2 because of bootloader issues.
If your phone is currently on 4.1.2 bootloader, then you can restore back to that firmware version. If it's on 4.3 bootloader, then restore back to that... and if it's on 4.4.2, then restore back to that. After returning the phone to Stock, boot into recovery and wipe cache & do a factory reset... as Odin doesn't seem to fully wipe everything.
Droidstyle's link for 4.1.2 looks to be down.... but recognized XDA Developer imnuts has the 4.1.2 VRAMC3 Odin file on his Android File Host site here: https://www.androidfilehost.com/?fid=23159073880932932
Also...if needed, here's a link to the Verizon stock 4.4.2 firmware: ( http://www.sammobile.com/firmwares/download/30950/I605VRUFND7_I605VZWFND7_VZW.zip/ ).
Good luck!!
I can't get in bootloader. I press up vol + home button + power. No good.
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
GiantsFan91 said:
I can't get in bootloader. I press up vol + home button + power. No good.
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Click to expand...
Click to collapse
Volume up+home+power button would put phone in Recovery mode if it was functioning properly.
You need to use Volume Down+Home+Power button to put the phone back into Odin mode (aka Download mode). From there, you can Odin flash the appropriate firmware to restore the phone. If you're not sure what version of Android you had on the phone before you tried to restore it... then I'm not sure which version you should use.
I used 4.1.1 Jelly bean.
GiantsFan91 said:
I used 4.1.1 Jelly bean.
Click to expand...
Click to collapse
But that attempt to flash 4.1.1 failed at sboot.bin... so you'll need to restore to whatever version you were on before to tried that.
I downloaded CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar and fail! I put sch-i605-16gb.pit and CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar. No good.
mattnmag said:
But that attempt to flash 4.1.1 failed at sboot.bin... so you'll need to restore to whatever version you were on before to tried that.
Click to expand...
Click to collapse
How? I have no recovery. I can't get in recovery.
You need to put phone into download mode to restore with ODIN... not into recovery.
I did..i restore with ODIN. No good.
You tried to restore back to 4.1.1. It will fail at sboot.bin every time and won't work. You need to restore back to a different firmware version.... whatever version you were on before you tried to Odin flash the 4.1.1 firmware. If your phone was updated to the newest 4.4.2 firmware them you will only be able to restore back to that firmware version because the bootloader is locked.
Bricked Galaxy Note 2 while updating to 4.3
Hello I am a new member i recently tried to update the Galaxy Note 2 to Android 4.3 through Odin using stock firmware i downloaded from Sammobile.com and it went through successfully but the phone is now stuck on the Samsung logo and will not go any further, I need some help with this ASAP as the phone does not belong to me, I was trying to update it for a friend like i updated mine but i have not run into an issue like this before. Any help would be greatly appreciated.
christherock said:
Hello I am a new member i recently tried to update the Galaxy Note 2 to Android 4.3 through Odin using stock firmware i downloaded from Sammobile.com and it went through successfully but the phone is now stuck on the Samsung logo and will not go any further, I need some help with this ASAP as the phone does not belong to me, I was trying to update it for a friend like i updated mine but i have not run into an issue like this before. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Try to boot the phone into Stock recovery by holding volume up+home button +power buttons all together until it boots into the stock recovery. Then wipe cache and do a factory reset. Hopefully that will fix things.
tried that
mattnmag said:
Try to boot the phone into Stock recovery by holding volume up+home button +power buttons all together until it boots into the stock recovery. Then wipe cache and do a factory reset. Hopefully that will fix things.
Click to expand...
Click to collapse
i tried to do that but the phone will not allow me to enter recovery mode, only 2 screens i seem to be able to access is the Odin download screen and the perpetual Samsung Galaxy NoteII screen, i did the update through Odin 3.9.0 and it took the update on Odin just fine but the phone wont boot up all the way, this is the script from Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUEMJ9_I605VZWEMJ9_I605VRUEMJ9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
i used file name I605VRUEMJ9_I605VZWEMJ9_I605VRUEMJ9_HOME.tar.md5
and i used pit file sch-i605-16gb.pit
as stated before im still kind of new at this so any information you could provide me would help a ton.
christherock said:
i tried to do that but the phone will not allow me to enter recovery mode, only 2 screens i seem to be able to access is the Odin download screen and the perpetual Samsung Galaxy NoteII screen, i did the update through Odin 3.9.0 and it took the update on Odin just fine but the phone wont boot up all the way, this is the script from Odin
Click to expand...
Click to collapse
If the phone was on 4.4.2 before you tried to Odin flash 4.3, then you will need to reflash 4.4.2 back onto the phone. You can not downgrade the phone to any previous Android versions because of the locked bootloader on the SCH-I605.
The log from Odin looks ok to me, so it sounds like something must be corrupted on the phone. Since you can't get into Stock recovery to wipe things.... then you might try 4.4.2 since 4.3 won't seem to work.
4.4.2 is not as easy to root as 4.3, but there is a root method called GhettoRoot that works on 4.4.2.
the phone was on 4.1.2 before i attempted the update
mattnmag said:
If the phone was on 4.4.2 before you tried to Odin flash 4.3, then you will need to reflash 4.4.2 back onto the phone. You can not downgrade the phone to any previous Android versions because of the locked bootloader on the SCH-I605.
The log from Odin looks ok to me, so it sounds like something must be corrupted on the phone. Since you can't get into Stock recovery to wipe things.... then you might try 4.4.2 since 4.3 won't seem to work.
4.4.2 is not as easy to root as 4.3, but there is a root method called GhettoRoot that works on 4.4.2.
Click to expand...
Click to collapse
i am not interested in rooting it im more concerned on getting it to boot up all the way, i get all of my firmware from sammobile but i cant seem to find the firmware for 4.4.2 on there, if you have a link of where i could find it that would be very helpful as well. please im kinda desperate here lol
christherock said:
i am not interested in rooting it im more concerned on getting it to boot up all the way, i get all of my firmware from sammobile but i cant seem to find the firmware for 4.4.2 on there, if you have a link of where i could find it that would be very helpful as well. please im kinda desperate here lol
Click to expand...
Click to collapse
On the sammobile website, you should be able to click Firmware, then enter GALAXY Note II and pick (SCH-I605).
Here's a direct link that should work: http://www.sammobile.com/firmwares/download/30950/I605VRUFND7_I605VZWFND7_VZW/
found it
mattnmag said:
On the sammobile website, you should be able to click Firmware, then enter GALAXY Note II and pick (SCH-I605).
Here's a direct link that should work:
ok just found it its downloading ill keep you posted if it works or not, i doubled checked and it is a 16gb, do i need to use the .pit file or no?
Click to expand...
Click to collapse
christherock said:
ok just found it its downloading ill keep you posted if it works or not, i doubled checked and it is a 16gb, do i need to use the .pit file or no?
Click to expand...
Click to collapse
I would still use the pit file. If you follow Droidstyle's Restore guide, (but just use the ODIN 3.10 version and the 4.4.2 firmware from Sammobile)... that will hopefully help you to get it restored.
The Sammobile site says not to have the repartition box checked.... but if you use the pit file, it automatically ticks the repartition box (which is what it's supposed to do.... so leave it ticked when using the pit file).
PS: Also make sure you're right clicking on ODIN and running it as Administrator....and disable all antivirus programs and close other running programs in the background when running Odin.
If your friend doesn't want the phone on 4.4.2 and it was never on 4.4.2 previously, then you could try reflashing 4.3 onto the phone using Odin 3.10 just to see if it would work with the newer Odin version. If it doesn't work, you could try 4.4.2.