i was following steps to install google now in this thread
http://forum.xda-developers.com/showthread.php?t=1749045
when i came to step of changing value the file wouldnt save my change so i gave extra(besides read and write i also checked execute and special) permission of build.prop file in system folder.
i restarted my phone after that and now phone shuts down after galaxy boot logo.
i tried following this thread
http://forum.xda-developers.com/showthread.php?t=1737855
i can get to download mode, but when i get to step of installing stock rom through odin it isnt working
i get error in odin:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
main line i messed up permission of build.prop how to can i replace it from odin?
thanks
please dont tell me my 500 bucks drain down the toilet. :crying:
Can you enter download mode?
If so, try restoring your phone with the factory Rom using odin
Sent from my SPH-L710 using Tapatalk 2
If you can't get into download mode you are screwed! Sorry
But if you can you should be able to flash stock through Odin.
Sent from my SGH-T999 using xda premium
yes i can get to download mode but i cant install stock rom.
thats what the t-mobile thread was asking to do. i can install stock kernel but not rom.
Why were you trying to install google now, when they said in the thread that it was only for ASOP Roms (CM9 or AOKP) anyway? Maybe try to push via adb if someone has a copy for you model if possible.
crystalstylez said:
Why were you trying to install google now, when they said in the thread that it was only for ASOP Roms (CM9 or AOKP) anyway? Maybe try to push via adb if someone has a copy for you model if possible.
Click to expand...
Click to collapse
can you please tell me how it is done or link me some thread you would recommend?
thanks
Good luck. This is ugly. I still have not rooted my device because besides working great as is, I am not comfortable hacking it. I know if I mess it up it is my fault and the thought of ruining it and cost I paid is making me cautious. I may hack it down the line. But for now, I'm going to enjoy it as is.
Hopefully, you get it restarted somehow.
omar300 said:
i was following steps to install google now in this thread
http://forum.xda-developers.com/showthread.php?t=1749045
when i came to step of changing value the file wouldnt save my change so i gave extra(besides read and write i also checked execute and special) permission of build.prop file in system folder.
i restarted my phone after that and now phone shuts down after galaxy boot logo.
i tried following this thread
http://forum.xda-developers.com/showthread.php?t=1737855
i can get to download mode, but when i get to step of installing stock rom through odin it isnt working
i get error in odin:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
main line i messed up permission of build.prop how to can i replace it from odin?
thanks
please dont tell me my 500 bucks drain down the toilet. :crying:
Click to expand...
Click to collapse
I'm guessing u installed all the right drivers if Odin sees your phone right? Are u using the most updated version of Odin made for our phones? U try download the rom agn? Maybe bad download, if yes try download a different version of rom, maybe the rooted one or if that's the one u used download the factory one, u try different computer? Reboot computer? , pull battery from phone for few min, some of these things sound stupid and pointless but take it from a guy with 7 samsungs its almost impossible to brick a Samsung
yea i got all the drivers and download correctly working. its weird cus it can install kernal and not rom, oh and im trying to install stock rom. only stock rom for t mobile comes in .tar type all other are made for cmw .zip format. im sure it can be unbricked but it will take some developer to get that done. i found this thread where alot of people messed up on same thing so hoping there will be solution soon. http://forum.xda-developers.com/showthread.php?p=28531684#post28531684
omar300 said:
yea i got all the drivers and download correctly working. its weird cus it can install kernal and not rom, oh and im trying to install stock rom. only stock rom for t mobile comes in .tar type all other are made for cmw .zip format. im sure it can be unbricked but it will take some developer to get that done. i found this thread where alot of people messed up on same thing so hoping there will be solution soon. http://forum.xda-developers.com/showthread.php?p=28531684#post28531684
Click to expand...
Click to collapse
What about the tool kit? U can install rooted rom from there while in Odin no? Try the 3.06 version of Odin? I.mean **** what u have to lose at this point . I'd still redownload the file if was me even if waste of time . I have a at&t version and we have 100% stock Odin and a rooted Odin ..
U said u can install the kernel?? Can u get into cwr with correct kernel? Probably dumb question but I asked anyway
Rooting is of no real risk for ATT at least.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
drawde40599 said:
What about the tool kit? U can install rooted rom from there while in Odin no? Try the 3.06 version of Odin? I.mean **** what u have to lose at this point . I'd still redownload the file if was me even if waste of time . I have a at&t version and we have 100% stock Odin and a rooted Odin ..
U said u can install the kernel?? Can u get into cwr with correct kernel? Probably dumb question but I asked anyway
Click to expand...
Click to collapse
I reinstalled the cwr and went in it and advance restored the system and it worked!
Related
Was stuck on dl01 with voodoo, bloatware frozen, rooted, and using launcherpro.
I followed the first link in that sticky: http://forum.xda-developers.com/showthread.php?t=908451
and now my phone wont boot up. when I turn it on I see the samsung logo and then it goes through this:
--Wiping data--
Formatting FOTA...
Formatting DATA...
Data Wipe failed.
Formatting Cache
Formatting DBDATA
Wipe_Data Failed.
Click to expand...
Click to collapse
then it will go back to the samsung logo and go around in circles again.
everything went fine with odin. This is what the little message window said:
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> Enter CS for MD5..
<ID:0/005> Check MD5.. Do not unplug the cable..
<ID:0/005> Please wait..
<ID:0/005> Removed!!
<ID:0/005> Removed!!
<ID:0/005> Removed!!
<ID:0/005> Checking MD5 finished Sucessfully..
<ID:0/005> Leave CS..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> cache.rfs
<ID:0/005> dbdata.rfs
<ID:0/005> factoryfs.rfs
<ID:0/005> modem.bin
<ID:0/005> recovery.bin
<ID:0/005> zImage
<ID:0/005> Removed!!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
I have no idea what went wrong but now i have no phone and this sux big time.
Dont panic this has happened to me.
Try this link:
http://forum.xda-developers.com/showthread.php?t=1026746
And use the method in SECTION 2: HEIMDALL
Rockstar52 said:
Dont panic this has happened to me.
Try this link:
http://forum.xda-developers.com/showthread.php?t=1026746
And use the method in SECTION 2: HEIMDALL
Click to expand...
Click to collapse
will take a look at that in a minute thanx.
but what the hell went wrong? was it something to do with voodoo?? none of the steps said to disable it or anything....
Yes you must disable VooDo before you do anything. Voodo is a real pain if your a new to flashing.
Rockstar52 said:
Yes you must disable VooDo before you do anything. Voodo is a real pain if your a new to flashing.
Click to expand...
Click to collapse
okay this tutorial is not working. I went strait to heimdall step two and I get two problems.
1) in step 3 it says "Now drop the usb drop down box and you will find an option for SAMSUNG android composite ADB device, or Samsung composite usb driver..."
I dont get that, I get "unknown device" My computer is 6 years old and i have always had problems with the usb recognizing my fascinate. It always says some type of problem and when i troubleshoot it says no drivers are installed even though i have installed them.
2)when I select the unknown device and hit install drivers i get installing drivers failed.
If you can get odin to work again use atlas_v2.2.pit to format back to rfs file-system. Use the PIT button in odin.
fupamobile said:
okay this tutorial is not working. I went strait to heimdall step two and I get two problems.
1) in step 3 it says "Now drop the usb drop down box and you will find an option for SAMSUNG android composite ADB device, or Samsung composite usb driver..."
I dont get that, I get "unknown device" My computer is 6 years old and i have always had problems with the usb recognizing my fascinate. It always says some type of problem and when i troubleshoot it says no drivers are installed even though i have installed them.
2)when I select the unknown device and hit install drivers i get installing drivers failed.
Click to expand...
Click to collapse
Definitely try to Odin the Pit 2.2 that DMT suggested.
Here's a link to a giude that should help get you back to stock as it isn't as intimidating for some as the un-bricking one: http://forum.xda-developers.com/showthread.php?t=1124391
And if that fails might I suggest trying it on a more up to date PC, maybe your issues have come from that if your pc never recognized the phone properly.
Nnneeeedd heellp nowwww!!!!!!!!!!
Go to the development stickies and go to the 2 one...how to go from
Cm7 to anything else...that's not the official title but it its something like that. The links for the eb01. tar, the atlas 2.2pit and newer odin versions are all in the first post.
I use odin 1.7..which version are you on? I'm sure if you use odin 1.7 or newer and put the 2.2 atlas pit file in the pit section with repartition checked and put the official vzw eb01 .tar in the pda section and run it..that will get your phone back in stock unrooted bloated form but at least your phone will work and then you can go and flash what you like..but I would try a different odin version and the eb01 with the pit file and you will get your phone back
Sent from my SCH-I500 using XDA App
Are you willing to just go back to stock or start all over again?
Put the phone in Download mode
Remove battery
plug usb into PC
plug usb into phone [battery still out]
push [and hold] volume button down
Should see yellow triangle [once you see this you can let go off the volume]
Use Odin then to flash the Stock image to your phone.
Link to ODIN v1.3 http://www.mediafire.com/download.php?r5izui8a3trpo85
Download the ED01 stock rom
Put it into the PDA section of Odin and flash and Boom Back to stock!
Stock ED01 http://www.multiupload.com/6ET46L1ATD
Nothing will be deleted off of your sd card
xwhofarted said:
Are you willing to just go back to stock or start all over again?
Put the phone in Download mode
Remove battery
plug usb into PC
plug usb into phone [battery still out]
push [and hold] volume button down
Should see yellow triangle [once you see this you can let go off the volume]
Use Odin then to flash the Stock image to your phone.
Link to ODIN v1.3 http://www.mediafire.com/download.php?r5izui8a3trpo85
Download the ED01 stock rom
Put it into the PDA section of Odin and flash and Boom Back to stock!
Stock ED01 http://www.multiupload.com/6ET46L1ATD
Nothing will be deleted off of your sd card
Click to expand...
Click to collapse
Well I got the drivers installed and i was on to step 5 but heimdall.exe wont open.
I think I will just do it this way i guess. this is all because of stupid voodoo
Voodoo used to be a p.i.t.a but it really isn't that hard now with the newer cwm supporting both voodoo and non voodoo, the steps myself and the person who posted above me are describing direction for odin..not heimdall.I don't know much about heimdall or how to use it but you can get your phone back and working using odin
Use the link in junkboy0's reply..follow the directions in the first post.
fupamobile said:
Well I got the drivers installed and i was on to step 5 but heimdall.exe wont open.
I think I will just do it this way i guess. this is all because of stupid voodoo
Click to expand...
Click to collapse
Sent from my SCH-I500 using XDA App
efan450 said:
Go to the development stickies and go to the 2 one...how to go from
Cm7 to anything else...that's not the official title but it its something like that. The links for the eb01. tar, the atlas 2.2pit and newer odin versions are all in the first post.
I use odin 1.7..which version are you on? I'm sure if you use odin 1.7 or newer and put the 2.2 atlas pit file in the pit section with repartition checked and put the official vzw eb01 .tar in the pda section and run it..that will get your phone back in stock unrooted bloated form but at least your phone will work and then you can go and flash what you like..but I would try a different odin version and the eb01 with the pit file and you will get your phone back
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
what should i do about voodoo though?
i am going to do this as two of you have suggested:http://forum.xda-developers.com/showthread.php?t=1124391
but i dunno about voodoo. just ignore it for now? It addresses it in that post but i dont undestand what it is saying
using Odin and the stock image it will over write the voodoo
I have never used the heimdall way. I have been stuck in boot loops many times and ODIN has always saved the day!
As long as you can get to Download mode your phone can be fixed
fupamobile said:
what should i do about voodoo though?
i am going to do this as two of you have suggested:http://forum.xda-developers.com/showthread.php?t=1124391
but i dunno about voodoo. just ignore it for now? It addresses it in that post but i dont undestand what it is saying
Click to expand...
Click to collapse
Yup ignore voodoo for now...when you use the atlas2.2 file in the pit section and the eb01.tar in the pda section...if repartition isn't checked make sure you check it...run it and it will bring you to stock with voodoo removed and then you can flash whatever you wanted from there...if you get stuck,p.m.me and I'll send you files with complete directions but it would have to wait till I get home from work tonight..don't panic we'll get you up and running again!
Get the newest odin, eb01. tar, and atlas 2.2pit file, and I would grab
One of the newer recovery.tar files too so when your back to stock you can flash a working recovery if you want to flash some rom after all is fixed....i recommend the 3-30 fix all recovery, but just make sure you get a tar file so you can odin it after your phone is fixed.
Sent from my SCH-I500 using XDA App
xwhofarted said:
using Odin and the stock image it will over write the voodoo
I have never used the heimdall way. I have been stuck in boot loops many times and ODIN has always saved the day!
As long as you can get to Download mode your phone can be fixed
Click to expand...
Click to collapse
interesting.
in the q/a section there is a sticky on how to go stock. not only does it not tell me how to address voodoo(why i am here) but it tells me to go to DL09 and them OTA to eb01.
the method you guys are posting seems much more logical. it sends me strait to froyo and doesnt brick my phone because it just overwrites voodoo. correct?
once voodoo is "overwritten", is it gone off my phone? if not, should i address it at all after this tutorial? froyo is downloading right now
xwhofarted said:
using Odin and the stock image it will over write the voodoo
I have never used the heimdall way. I have been stuck in boot loops many times and ODIN has always saved the day!
As long as you can get to Download mode your phone can be fixed
Click to expand...
Click to collapse
I concur...soft bricked, boot looped, many many times and never used heimdall either
Sent from my SCH-I500 using XDA App
fupamobile said:
interesting.
in the q/a section there is a sticky on how to go stock. not only does it not tell me how to address voodoo(why i am here) but it tells me to go to DL09 and them OTA to eb01.
the method you guys are posting seems much more logical. it sends me strait to froyo and doesnt brick my phone because it just overwrites voodoo. correct?
once voodoo is "overwritten", is it gone off my phone? if not, should i address it at all after this tutorial? froyo is downloading right now
Click to expand...
Click to collapse
Correct voodoo will be gone but you can just flash another voodoo kernel later and you can flash voodoo over voodoo just not voodoo to non voodoo with out removing it
Sent from my SCH-I500 using XDA App
efan450 said:
Yup ignore voodoo for now...when you use the atlas2.2 file in the pit section and the eb01.tar in the pda section...if repartition isn't checked make sure you check it...run it and it will bring you to stock with voodoo removed and then you can flash whatever you wanted from there...if you get stuck,p.m.me and I'll send you files with complete directions but it would have to wait till I get home from work tonight..don't panic we'll get you up and running again!
Get the newest odin, eb01. tar, and atlas 2.2pit file, and I would grab
One of the newer recovery.tar files too so when your back to stock you can flash a working recovery if you want to flash some rom after all is fixed....i recommend the 3-30 fix all recovery, but just make sure you get a tar file so you can odin it after your phone is fixed.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
okay. I am just following what that tutorial says to do. I dont even know what a working recovery is. I never even had a rom on this thing. I have realized I am in way over my head here and have spent too much time dealing with my phone.
really all i want is to be up to date, have root, debinged/bloat, launcherpro so i dont have to use stupid touchwiz. thats basically all i need. maybe in the future i might get other stuff. but for now i think it will suit me best to just rely on verizon/samsung to keep my phone up to date and then just re root everytime. seems much simpler and safer
fupamobile said:
okay. I am just following what that tutorial says to do. I dont even know what a working recovery is. I never even had a rom on this thing. I have realized I am in way over my head here and have spent too much time dealing with my phone.
really all i want is to be up to date, have root, debinged/bloat, launcherpro so i dont have to use stupid touchwiz. thats basically all i need. maybe in the future i might get other stuff. but for now i think it will suit me best to just rely on verizon/samsung to keep my phone up to date and then just re root everytime. seems much simpler and safer
Click to expand...
Click to collapse
Recovery..clock work mod...or cwm is the recovery program you will use to install custom rom, kernels, or zip files...I will send you a p.m.later with files, info, and instructions and you can read over it and decide if you want to do it now or wait till you're a lil more familiar with the process..but for now odin the pit atlas 2.2 file and eb01 and you will be stock and be able to use launcher pro.
Sent from my SCH-I500 using XDA App
Hi
Yesterday i rooted my Samsung Galaxy S2 i9100m VIA The zergrush exploit.
I Tried to flash CWM Via Odin and it did not work!
My phone will not access recovery and when turned on normally says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I have tried flashing the bootloader, kernel, CSC, modem, and firmware several times but they always fail!
I tried to follow this guide here and it also did not work!
I can not think of what else to do so i have posted this thread here!
Thanks
*EDIT*
This is what originally ****ed me up: http://galaxys2root.com/galaxy-s2-r...ckworkmod-recovery-on-rooted-galaxy-s2-i9100/
if you read the comments everyone is having the same issue
*EDIT*
- What is the error you were getting in Odin=I have successfully flashed a pit file and when trying to flash my firmware it comes up with this
<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> factoryfs.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So it is failing at NAND Write Start!!
- Did you try to flash other recovery's? If yes, then which one= No but i am now
- Do you still have download mode= Yes
- Did you flash .pit files or re-partitoned= Yes i flashed the correct pit file and it succeeded
- What firmware were you on= I9100MKG2
- Did you reinstall the drivers= Several Times
- Tried different usb port / pc= Yes
- Did you try different cables= Yes
So I guess you've flashed a stock I9100M ROM via odin and failed too, right?
Sent from the little guy
gastonw said:
So I guess you've flashed a stock I9100M ROM via odin and failed too, right?
Sent from the little guy
Click to expand...
Click to collapse
Yes i have!
Flash custom kernel so you can get to recovery then.
And if you tried that too keep on flashing.
Hold on a sec, odin passes or fails?
Sent from the little guy
gastonw said:
Flash custom kernel so you can get to recovery then.
And if you tried that too keep on flashing.
Hold on a sec, odin passes or fails?
Sent from the little guy
Click to expand...
Click to collapse
It fails
Jenham said:
It fails
Click to expand...
Click to collapse
it fails
You gotta keep on trying. Trial & error.
Sent from the little guy
gastonw said:
So I guess you've flashed a stock I9100M ROM via odin and failed too, right?
Sent from the little guy
Click to expand...
Click to collapse
Updated
?
Got it working again?
Sent from the little guy
Jenham said:
Updated
Click to expand...
Click to collapse
Huh?
Sent from my digital submersible hovercraft.
You need to start giving more details if you want help...
- What is the error you were getting in Odin?
- Did you try to flash other recovery's? If yes, then which one?
- Do you still have download mode?
- Did you flash .pit files or re-partitoned?
- What firmware were you on?
- Did you reinstall the drivers?
- Tried different usb port / pc?
- Did you try different cables?
If you want help, I suggest you start giving us all the info that you can give us instead of saying "they always fail".
He's mute.
Sent from the little guy
Lennyz1988 said:
You need to start giving more details if you want help...
- What is the error you were getting in Odin?
- Did you try to flash other recovery's? If yes, then which one?
- Do you still have download mode?
- Did you flash .pit files or re-partitoned?
- What firmware were you on?
- Did you reinstall the drivers?
- Tried different usb port / pc?
- Did you try different cables?
If you want help, I suggest you start giving us all the info that you can give us instead of saying "they always fail".
Click to expand...
Click to collapse
Sorry about that and i have updated my thread!
Oh boy, did I just read that you used a .pit file and that the flashing failed? You do know that the flashing needs to succeed when you flash a .pit?
Did you use a .pit the first time when the flashing failed?
http://forum.xda-developers.com/attachment.php?attachmentid=1750999&stc=1&d=1361525591
Really should stay well away from .pit files man.... Reads like jtag or paperweight time.
Amen.
Sent from the little guy
gaosphappy said:
http://forum.xda-developers.com/attachment.php?attachmentid=1750999&stc=1&d=1361525591
Really should stay well away from .pit files man.... Reads like jtag or paperweight time.
Click to expand...
Click to collapse
Lol the pit succeeded
Take a long breath, and when I say long I mean LONG.
Sent from the little guy
Hi I'm in the exact same boat, My sgs2 wont reboot and wont go into recovery. Everytime I flash with odin I get failed. What can I do ? I can't even find the pit file to flash that. I'm getting really worried. Please help
sawdoctor said:
Hi I'm in the exact same boat, My sgs2 wont reboot and wont go into recovery. Everytime I flash with odin I get failed. What can I do ? I can't even find the pit file to flash that. I'm getting really worried. Please help
Click to expand...
Click to collapse
Check the phistachio thread.
Sent from the little guy
After try to recover my S3 ('cause i get a brick the typical problem that Samsung screen and then nothing happend, i put my cell into download mode and then try to flash only with PDA file i got the next error "There is no pit partition" ), following this steps from another post
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
i take the
4.1.2
I9300XXELLA_KOR_MULTI_FACTORY
i got a new message from Odin
see image1 in attachements
Now i don't know what to do... just i know is a little hope 'cause it can start a downloading mode...
So Please HELP!
there is the problem
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What i need to do...!!! PLEASE HELP
Same problem
GaboBigale said:
there is the problem
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What i need to do...!!! PLEASE HELP
Click to expand...
Click to collapse
Got the same problem man, if you resolve it first, let me know.:good:
Same problem
lumogox said:
Got the same problem man, if you resolve it first, let me know.:good:
Click to expand...
Click to collapse
got this same problem also, please, anyone? any help?
pit file missing
you have to download pit file so it can create a partition. download it and flash it together with the tar file of your desired firmware. i had the same problem but it couldn't create a partition as it is full bricked and i sent it for a warranty
re-partition fails
panais86 said:
you have to download pit file so it can create a partition. download it and flash it together with the tar file of your desired firmware. i had the same problem but it couldn't create a partition as it is full bricked and i sent it for a warranty
Click to expand...
Click to collapse
thanks for the replay, unfortunately i have already tried that, it fails every time i am trying to re-partition.
echoen99 said:
thanks for the replay, unfortunately i have already tried that, it fails every time i am trying to re-partition.
Click to expand...
Click to collapse
try to flash only the .PIT file.
you have nothing to loose
nand problem
echoen99 said:
thanks for the replay, unfortunately i have already tried that, it fails every time i am trying to re-partition.
Click to expand...
Click to collapse
try this link
http://www.droidevelopers.com/f363/...-files.html?11722-Download-OPS-amp-PIT-files=
if you have a problem as well then probably you have a problem with nand so you have to send it for warranty as well
Thanks for all the replys, i will check and update
Thanks
Sent from my GT-I9300 using Tapatalk 2
stuck same problem
hi
i have a smasung galaxy s3 international I9300
i think i soft bricked it cause i can go into download mode but when i swithch on the phone it gives me a screen
//i276.photobucket.com/albums/kk29/mlijfu/photo.jpg
how i reached here was i flashed my phone with 3-4 roms got bit stuck and then removed my battery in the middle of a reboot there here i was
so i used ur RESCUE FIRMWARE SGSIII I9300 - I9300XXEMC2_KOR_MULTI_FACTORY
same used in the first thread
but did not help
i got this
//i276.photobucket.com/albums/kk29/mlijfu/Untitled1.png
//i276.photobucket.com/albums/kk29/mlijfu/Untitled.png
pls help
mlijfu said:
hi
i have a smasung galaxy s3 international I9300
i think i soft bricked it cause i can go into download mode but when i swithch on the phone it gives me a screen
//i276.photobucket.com/albums/kk29/mlijfu/photo.jpg
how i reached here was i flashed my phone with 3-4 roms got bit stuck and then removed my battery in the middle of a reboot there here i was
so i used ur RESCUE FIRMWARE SGSIII I9300 - I9300XXEMC2_KOR_MULTI_FACTORY
same used in the first thread
but did not help
i got this
//i276.photobucket.com/albums/kk29/mlijfu/Untitled1.png
//i276.photobucket.com/albums/kk29/mlijfu/Untitled.png
pls help
Click to expand...
Click to collapse
What ROM and what Kernel did you use before it happened (Kernel version is also important)? And what did you mean with you got stuck? Details are important when you are dealing with cases like this.
I saw this kind of screen before, some guy had the same problem. However he couldn`t fix himself. Ever heard of Sudden Death?
Scarface1991 said:
What ROM and what Kernel did you use before it happened (Kernel version is also important)? And what did you mean with you got stuck? Details are important when you are dealing with cases like this.
I saw this kind of screen before, some guy had the same problem. However he couldn`t fix himself. Ever heard of Sudden Death?
Click to expand...
Click to collapse
thanks for the reply
CyanogenMod 9 stable version with its own kernel
i installed it and the gapps with it then when the phone rebooted it got stuck at lock screen then i reebooted it again but it was taking a bit long time at samsung logo so i took off the battery and there the phone became like this
//i276.photobucket.com/albums/kk29/mlijfu/photo.jpg
i can go into download mode
ODIN MODE
Product name:
custom binary download:no
currant binary: samsung official
system status : custom
as u can see product name is blank
with odin i tried ti flash stock Samsung firmware - it wanted some pit
so i used RESCUE FIRMWARE SGSIII I9300 - I9300XXEMC2_KOR_MULTI_FACTORY
same used in the first thread
but did not help
i got this
//i276.photobucket.com/albums/kk29/mlijfu/Untitled1.png
//i276.photobucket.com/albums/kk29/mlijfu/Untitled.png
mlijfu said:
thanks for the reply
CyanogenMod 9 stable version with its own kernel
i installed it and the gapps with it then when the phone rebooted it got stuck at lock screen then i reebooted it again but it was taking a bit long time at samsung logo so i took off the battery and there the phone became like this
//i276.photobucket.com/albums/kk29/mlijfu/photo.jpg
i can go into download mode
ODIN MODE
Product name:
custom binary download:no
currant binary: samsung official
system status : custom
as u can see product name is blank
with odin i tried ti flash stock Samsung firmware - it wanted some pit
so i used RESCUE FIRMWARE SGSIII I9300 - I9300XXEMC2_KOR_MULTI_FACTORY
same used in the first thread
but did not help
i got this
//i276.photobucket.com/albums/kk29/mlijfu/Untitled1.png
//i276.photobucket.com/albums/kk29/mlijfu/Untitled.png
Click to expand...
Click to collapse
This is half sds. Needs to go to a service centre and have the motherboard swapped probably
Sent from my GT-I9300 using Tapatalk 2
rootSU said:
This is half sds. Needs to go to a service centre and have the motherboard swapped probably
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
will a Samsung Galaxy S III JTAG Brick Repair help me ?
mlijfu said:
will a Samsung Galaxy S III JTAG Brick Repair help me ?
Click to expand...
Click to collapse
No one has been successful with that method yet. The issue will be that the wear levelling bug has wiped out your eMMC and it needs replacing.
Have a read in the general forum of the "ultimate SDS thread" or whatever its called. There is also my "important - are you covered" thread stuck at the top of general.
So thats the sudden death ? Were you on 4.1.2 before you bricked?
Sent from my GT-I9300 using xda app-developers app
KayKrate said:
So thats the sudden death ? Were you on 4.1.2 before you bricked?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
before rooting was on what ever the latest firmware was
i did not use triangle away
i was using paranoid android 4.2.2
then went to cmod9
so i think i am screwed
CM9 has no SDS fix.
All you can do is try and get warranty repair if you're still in warranty. Otherwise pay for a Mobo repair / replacement.
Someone posted a how to to fit a new eMMC and the cost of the eMMC was cheap, but the effort was a lot.
People gotta take care what firmware to flash :/ Stock 4.1.2 is safe , I used DFG and didnt get any freeze for like a week so my phone's stable now ... maybe samsung come up with a new firmware which makes your phone explode or ruin our devices ... Who knows >.< ?
rootSU said:
CM9 has no SDS fix.
All you can do is try and get warranty repair if you're still in warranty. Otherwise pay for a Mobo repair / replacement.
Someone posted a how to to fit a new eMMC and the cost of the eMMC was cheap, but the effort was a lot.
Click to expand...
Click to collapse
will this help i know its not for s3 but still as am desperate
1. ://forum.xda-developers.com/showthread.php?t=1670651
2. ://forum.xda-developers.com/showthread.php?p=26428986
3. //forum.xda-developers.com/showpost.php?p=26285877&postcount=12
just wanted to know from an expert will one of then work for me?
I had the latest 4.1.2 stock OTA installed via CWM and I wanted to unroot and go back to stock and that seemed to work fine.... I went to the old version VRALL4 and once rebooted it asked me to update OTA so I did and that was fine........ and it asked me to do it again for some reason and now I'm in a boot loop. The Galaxy note 2 logo flashes on the screen real fast and turns off over and over. I can only get into ODIN and not stock recovery. I've tried re-flashing the original odin package, and the pre-rooted odin packages and nothing is working.... what can I do? am i fux0rd? thx
edit: also USB all drivers are installed .......
Try a factory reset in the stock recovery. Then give it a whirl.
Sent from my SCH-I605 using Tapatalk 2
enkrypt3d said:
I had the latest 4.1.2 stock OTA installed via CWM and I wanted to unroot and go back to stock and that seemed to work fine.... I went to the old version VRALL4 and once rebooted it asked me to update OTA so I did and that was fine........ and it asked me to do it again for some reason and now I'm in a boot loop. The Galaxy note 2 logo flashes on the screen real fast and turns off over and over. I can only get into ODIN and not stock recovery. I've tried re-flashing the original odin package, and the pre-rooted odin packages and nothing is working.... what can I do? am i fux0rd? thx
edit: also USB all drivers are installed .......
Click to expand...
Click to collapse
Checkout this thread by Adam Outler called "DON'T ACCEPT OTA UPDATES" in the Verizon Galaxy Note II General section. I'm aware that you aren't experiencing this specific problem, but it should fix your boot loop problem. You'll need the two files that he makes available just below the picture. I've had others tell me that they used those files to successfully fix boot loops.
RomsWell said:
Try a factory reset in the stock recovery. Then give it a whirl.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I can only get into odin... not even stock recovery. the odin app doesn't even work most of the time....
If i hold vol up + power + home it just continues to boot loop flashing the note 2 logo....... downloading one more odin file to see if this can fix it..... :crying:
I knew I should have used triangle away before doing this as if I take it to the VZ store they're going to be able to tell that it'd been modified before....
The lesson you should learn from this is DO NOT ACCEPT OTAS! Not sure how you haven't understood that since it has been stated more than enough times in almost every thread.
BoostedB18C said:
The lesson you should learn from this is DO NOT ACCEPT OTAS! Not sure how you haven't understood that since it has been stated more than enough times in almost every thread.
Click to expand...
Click to collapse
First of all, I'm not a noob and I did get the system back up.... as I said above i was trying to UNROOT not ROOT my device using Odin which I have done many times. This is the first time I've ran into the boot loop issue.... so I flashed a stock unrooted odin tar.md5 and this is the issue that I had.... now when I did that, I thought I was unrooted but obviously the bootloader did not get flashed back to stock... anyways thanks for your oh so useful post in lumping me in with the n00bz... :laugh:
anyways
now im facing another issue where its still has the rooted bootloader installed but an "official" stock rom on it.....
I'm not saying you're a noob. All I'm trying to get you to understand is to read before doing. As with your unlocked bootloader issue, you probably overlooked that there are 2 ways to restore to stock. One re locks the bootloader and the other doesn't. Read more and don't skim the guide, that's all I'm saying my dude.
BoostedB18C said:
I'm not saying you're a noob. All I'm trying to get you to understand is to read before doing. As with your unlocked bootloader issue, you probably overlooked that there are 2 ways to restore to stock. One re locks the bootloader and the other doesn't. Read more and don't skim the guide, that's all I'm saying my dude.
Click to expand...
Click to collapse
thats what Ive been trying to find for ages and I've downloaded 4 or 5 different "stock" odin packages which puts me back to the original 4.1.1 I506VRALJB version....
So I'm trying to find the ODIN package that wipes everything (bootloader esp)....... thanks..... and with goo.im having so many issues its really tough finding all the files I need.
....hmmmmmmm so I updated superSU and unchecked a box that "hides" root - but if I accept another OTA i'm sure I'll be stuck with another boot loop until I really flash the unlocked bootloader with the OEM one right?
DO NOT ACCEPT OTAS! Lol. I forgot which thread had the right file. I'll look around and try to find it. Which files from which threads have you tried?
This is where I pointed the last person I helped and it worked for them
http://forum.xda-developers.com/showthread.php?p=41584579
BoostedB18C said:
DO NOT ACCEPT OTAS! Lol. I forgot which thread had the right file. I'll look around and try to find it. Which files from which threads have you tried?
Click to expand...
Click to collapse
lol yea my goal is to be on the latest and greatest OTA but of course im not going to accept an OTA until I'm 100% locked first....
http://forum.xda-developers.com/showthread.php?t=2040264
Tried this one which puts me on the original oem rom that came with the phone w/ no updates....
The only way I was able to get out of the boot loop is use the PIT file and this file root66_VZW_stock_system.tar.md5
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
Here is where I Found the "pre-rooted" file... I put that in the bootloader section of ODIN along with the PIT file and this fixed my boot loop problem.
so even tho ODIN mode says "official" and not custom - this is bc I disabled root thru superSU even though its still rooted..
http://d-h.st/Qd4
I think this is the baseline unrooted baseband......trying it out.
enkrypt3d said:
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
Here is where I Found the "pre-rooted" file... I put that in the bootloader section of ODIN along with the PIT file and this fixed my boot loop problem.
so even tho ODIN mode says "official" and not custom - this is bc I disabled root thru superSU even though its still rooted..
Click to expand...
Click to collapse
I would advise you to stay away from guides that are not on xda. Just because there is more knowledge here.
BoostedB18C said:
I would advise you to stay away from guides that are not on xda. Just because there is more knowledge here.
Click to expand...
Click to collapse
Just showing where I Got the file to recover from boot loop.... that guide isnt even for the right phone model...... read back as I added a bunch to my last post.
Trying to flash with the below file in the "phone" section so that it wipes the entire phone but it fails.... I've also removed superSU by using the option to "unroot" inside SuperSU..... whats going on? I have the PIT File in place, "phone bootloader update" checked or unchecked doesn't seem to matter..... and same for Phone EFS Clear......
<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/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<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> 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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> cache.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> hidden.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> param.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> recovery.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> sboot.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
http://forum.xda-developers.com/showthread.php?t=2120726
This is the exact problem I have.....
From what I am understanding you can't write boot on Vrall4. So you would need to be on vraljb before being able to re lock the bootloader. I'm my head it makes sense but not sure how you need to go about it. I only looked at it real quick and I can't look into it right now. I'll check with you later and see what you have figured out. So post anything that you come across.
finally resolved it by erasing nand and flashing root66, then factory reset, then flashing one without the sboot.bin......
it took so many times - i dont think ive ever flashed this phone this many times before....... ugh what a pIta.... never rooting this phone again as its so freakin tempermental.
Or just don't unroot it. Problem solved??
Sent from my SCH-I605 using Tapatalk 2
enkrypt3d said:
finally resolved it by erasing nand and flashing root66, then factory reset, then flashing one without the sboot.bin......
it took so many times - i dont think ive ever flashed this phone this many times before....... ugh what a pIta.... never rooting this phone again as its so freakin tempermental.
Click to expand...
Click to collapse
please instruct me on all steps u took... where did u put the files and what u checked and what not.. i have the same exact problem except it gets stuck at Logo... i cannot go into recovery as well.
i have tried all the same files as u and all fail except root66 but it stays stuck on logo
as far as I can remember, take odin, put the pit file in the pit location in odin:
http://d-h.st/mKu
Then flash with root66...
http://androidfilehost.com/?fid=9390210501348163619
then see if u can get into stock recovery and do a factory reset and then go back into odin mode.... then tick nand erase and then use the alternate restore and put it in the phone section of the ODIN app and flash it....... of course this doesnt have the sboot but this was the only way i was able to get it back up....
if u are able to get the phone back up with root66, then stop there..... erasing the nand and not doing it right can brick it. i spent 2 days fixing mine and I must have tried flashing the phone at least 25 times... when I got root66 up and running I went into SuperSU app and went into settings and theres an option to remove or hide root. this may have helped. right now im finally on the latest OTA and it says official (not custom rom) in odin mode and in the about phone section. Hope this helps.
keep the back cover off the phone bc you'll be pulling the battery out if it gets stuck... good luck. FYI I always use the PIT file and that always seemed to have helped.
enkrypt3d said:
as far as I can remember, take odin, put the pit file in the pit location in odin:
http://d-h.st/mKu
Then flash with root66...
http://androidfilehost.com/?fid=9390210501348163619
then see if u can get into stock recovery and do a factory reset and then go back into odin mode.... then tick nand erase and then use the alternate restore and put it in the phone section of the ODIN app and flash it....... of course this doesnt have the sboot but this was the only way i was able to get it back up....
if u are able to get the phone back up with root66, then stop there..... erasing the nand and not doing it right can brick it. i spent 2 days fixing mine and I must have tried flashing the phone at least 25 times... when I got root66 up and running I went into SuperSU app and went into settings and theres an option to remove or hide root. this may have helped. right now im finally on the latest OTA and it says official (not custom rom) in odin mode and in the about phone section. Hope this helps.
keep the back cover off the phone bc you'll be pulling the battery out if it gets stuck... good luck. FYI I always use the PIT file and that always seemed to have helped.
Click to expand...
Click to collapse
ah man... i can get PASS! on root66 but it still gets stuck at logo.. anything else i flash will just fail at boot.img nand write... think im just f*ck'ed dude..
my thread is here if anything... thank you !
http://forum.xda-developers.com/showthread.php?t=2296441
Best bet is to erase nand and try flashing with the alternative rom and pit file at the same time...tomorrow I'll post the files I used as most mirrors are slow as balls..
Sent from my SCH-I605 using xda app-developers app
hi my name is david i have a galaxy s4 sgh-i337 model i had it root on 4.2 i used a vroot method 2 month ago the i updated to 4.3 and i still had rood then i was wodering if there was any new updates in ota soo i updated to 4.4.2 and i dnt notice that i had lost root and i tried to use the freedom app i it messed up my host file preventing me from using the play store or any google service and cuz i lost root i couldnt edit the host file to fix soo i flash some ((stock rom)) and now im back to 4.3 i have no wifi or mobile data and for some reason i cant flash a stock rom cuz of some auth error odin keeps giving me so plizz help me out
dvd2474 said:
hi my name is david i have a galaxy s4 sgh-i337 model i had it root on 4.2 i used a vroot method 2 month ago the i updated to 4.3 and i still had rood then i was wodering if there was any new updates in ota soo i updated to 4.4.2 and i dnt notice that i had lost root and i tried to use the freedom app i it messed up my host file preventing me from using the play store or any google service and cuz i lost root i couldnt edit the host file to fix soo i flash some ((stock rom)) and now im back to 4.3 i have no wifi or mobile data and for some reason i cant flash a stock rom cuz of some auth error odin keeps giving me so plizz help me out
Click to expand...
Click to collapse
Hmm.. first let's see what errors Odin is giving..post the log that Odin spits out here..
If you took an OTA to 4.4.2 is sounds like you might be locked..I'm not positive bc I don't have tie device but I'm pretty sure 4.4.2 for t mobile gs4 was just released, therefore, flashing OTA locks your bootloader and no more flashing customs roms for you. That is unless someone (dev) finds a way to unlock the bootloader..
The only thing I don't understand is you say your back on 4.3.. how did you go about flashing this..
Provide a little more info on the above and I'll see if I can give you a little more
lacoursiere18 said:
Hmm.. first let's see what errors Odin is giving..post the log that Odin spits out here..
If you took an OTA to 4.4.2 is sounds like you might be locked..I'm not positive bc I don't have tie device but I'm pretty sure 4.4.2 for t mobile gs4 was just released, therefore, flashing OTA locks your bootloader and no more flashing customs roms for you. That is unless someone (dev) finds a way to unlock the bootloader..
The only thing I don't understand is you say your back on 4.3.. how did you go about flashing this..
Provide a little more info on the above and I'll see if I can give you a little more
Click to expand...
Click to collapse
the way i got back to 4.3 whas that i was looking online for a solution and nothing came up soo i decided to downgrade my phone thinking that with that i would get the play store and google service back but like always there was a problem and now i dont have wifi :/ so i cant ota again to return to stock and no mater what stock rom i odin gives me the fail (auth) error. and the odin log is
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
dvd2474 said:
the way i got back to 4.3 whas that i was looking online for a solution and nothing came up soo i decided to downgrade my phone thinking that with that i would get the play store and google service back but like always there was a problem and now i dont have wifi :/ so i cant ota again to return to stock and no mater what stock rom i odin gives me the fail (auth) error. and im not at home right now soo i cant provide the odin log
Click to expand...
Click to collapse
You need to go here and get your correct firmware..
When you flash it add this pit file to Odin to ensure it flashes to the proper place..
Let me know if have any success:good:
lacoursiere18 said:
You need to go here and get your correct firmware..
When you flash it add this pit file to Odin to ensure it flashes to the proper place..
Let me know if have any success:good:
Click to expand...
Click to collapse
o.k i will let u know how it came up
both the links dont work the pit file is a txt file that cant be changed and the other page dont got the tar for my phone
dvd2474 said:
both the links dont work the pit file is a txt file that cant be changed and the other page dont got the tar for my phone
Click to expand...
Click to collapse
Ok HMM.. not sure where to look man you need to search in your devices section..
I have a question for you though? Why are you selecting NAND.. here:
Code:
<ID:0/006> NAND Write Start!!
You should not select this..
Try it again with out selecting that and see what happens..
lacoursiere18 said:
Ok HMM.. not sure where to look man you need to search in your devices section..
I have a question for you though? Why are you selecting NAND.. here:
Code:
<ID:0/006> NAND Write Start!!
You should not select this..
Try it again with out selecting that and see what happens..
Click to expand...
Click to collapse
how do i unselect it cuz i just load the tar file. and auto reboot and f.flash what ever are all ready selected soo how i do it??
lacoursiere18 said:
Ok HMM.. not sure where to look man you need to search in your devices section..
I have a question for you though? Why are you selecting NAND.. here:
Code:
<ID:0/006> NAND Write Start!!
You should not select this..
Try it again with out selecting that and see what happens..
Click to expand...
Click to collapse
u still there i really need your help
dvd2474 said:
hi my name is david i have a galaxy s4 sgh-i337 model i had it root on 4.2 i used a vroot method 2 month ago the i updated to 4.3 and i still had rood then i was wodering if there was any new updates in ota soo i updated to 4.4.2 and i dnt notice that i had lost root and i tried to use the freedom app i it messed up my host file preventing me from using the play store or any google service and cuz i lost root i couldnt edit the host file to fix soo i flash some ((stock rom)) and now im back to 4.3 i have no wifi or mobile data and for some reason i cant flash a stock rom cuz of some auth error odin keeps giving me so plizz help me out
Click to expand...
Click to collapse
m.ibtimes.co.uk/i9500xxufnb4-android-4-4-2-stock-firmware-arrives-galaxy-s4-how-install-1439951
dvd2474 said:
how do i unselect it cuz i just load the tar file. and auto reboot and f.flash what ever are all ready selected soo how i do it??
Click to expand...
Click to collapse
Sent from my SCH-I605 using xda app-developers app
lacoursiere18 said:
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
i never selec it but it always comes up on the odin log
dvd2474 said:
i never selec it but it always comes up on the odin log
Click to expand...
Click to collapse
Try Odin 1.85..here is a link..
https://www.dropbox.com/s/nbnzikksjrnuucy/Odin3-v1.85.zip
Sent from my SCH-I605 using xda app-developers app
lacoursiere18 said:
Try Odin 1.85..here is a link..
https://www.dropbox.com/s/nbnzikksjrnuucy/Odin3-v1.85.zip
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
i have tried that odin but i get the same results
U have any other ideas??
Sent from my SAMSUNG-SGH-I337 using xda app-developers app