Hey, complete noob but will try to give a concise post of what I've done and where I'm at now. I received an I727R second hand and I am trying to put seanzscreams Sky ICS rom on it but am constantly running in to problems. Here are some important details:
Phone: SGH-I727R
Android Version: 2.3.5 GB (stock rogers firmware)
Baseband: I727RUXKJ7
Kernel: 2.6.35.11
Unrooted
O/S: Windows 7 Ultimate x64
Phone was in USB debugging mode before I bricked it
Did *#7284# and switched from Modem to PDA
Plugged in phone first time ever to PC, drivers installed OK. Installed Kies from Canadian Samsung website, did not recognize phone. Uninstalled/Reinstalled Kies after using registry cleaner; no difference, still connection error (wouldn't troubleshoot too). Uninstalled Kies. Uninstalled samsung drivers, installed standalone samsung drivers (Samsung_USB_Driver_for_Mobile_Phones_v1_3_2200_0.exe). Reinstalled Kies still no difference. Uninstalled Kies and standalone drivers, used registry cleaner, plugged in phone and let drivers install from Windows update.
Next I figured I wanted to root my phone so I could install CWM, and custom ROMs.
Installed android sdk for windows; made sure I had adb drivers for my phone. Tried to use adb for zergRush exploit; exploit worked but when running the command "adb remount" adb wouldn't recognize device (does the phone need to be in download mode when doing this whole process? Never was it mentioned that it needed to be). Then tried to use Skyrocket Easy Root method from this thread (http://forum.xda-developers.com/showthread.php?t=1340710), plenty of errors but it resulted in my phone apparently being rooted. Tried installing ROM manager from market to then install CWM, said I had no permissions (phone isn't rooted).
Then after getting frustrated...
Tried grabbing Odin 1.8.5 and this recovery file for CWM (http://www.mediafire.com/?5xc7gjkrbwihajp) and tried to flash to phone. First attempt it got stuck at <ID:0/004> recovery.img, let it stay for about +15min, nothing. Phone bricked (Firmware upgrade encountered etc.; not able to get in to download mode). Next tried to reinstall stock rogers 2.3.5. Still nothing, hangs at <ID:0/004> SetupConnection... Tried multiple times to reboot phone and then load firmwares again, nothing. Latest error is this after trying the recovery image again <OSM> All threads completed. (succeed 0 / failed 1). Moving the phone to different USB ports on my laptop makes Odin not recognize the phone at all
I beg someone to help me unbrick this phone and to help me get the custom ICS debloated version running on it. I'm short of pulling all of my hair out from frustration
Thanks for taking the time to read this
Look at the Odin tar thread. Its a sticky in the development section. Flash the tar file to completely restore your device. And read read read
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
cdshepherd said:
Look at the Odin tar thread. Its a sticky in the development section. Flash the tar file to completely restore your device. And read read read
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
+1
how did you ever find that old thread, read the last part of my sig and go to the second link in my sig
EDIT: Nvm, I just saw vincom's post which directs me to the thread you were talking about. I've read that thread, and still can't flash to stock firmware.
Here:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I727RUXKJ7_I727RRWCKJ7_I727RUXKJ7_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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
flum said:
If by Odin tar thread you mean this, http://forum.xda-developers.com/showthread.php?t=1566613, it's not a stickied thread. I tried flashing it anyways and it fails everytime I try. Thanks for the input though.
Click to expand...
Click to collapse
you must be blind, look at my sig
flum said:
If by Odin tar thread you mean this, http://forum.xda-developers.com/showthread.php?t=1566613, it's not a stickied thread. I tried flashing it anyways and it fails everytime I try. Thanks for the input though.
Click to expand...
Click to collapse
My goodness lol. Look in vincoms sig. Its obvious you jumped into this without doing your homework. Now your paying for it. Not trying to be rude but your not paying attention. Good luck and we are here if you still can't figure it out...luckily:thumbup:
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
vincom said:
you must be blind, look at my sig
Click to expand...
Click to collapse
Nah, read his post before I refreshed and saw yours directing me to the thread
Well?
stoopendis said:
Well?
Click to expand...
Click to collapse
He's not good at reading, it seems. Oh well that's what happens when you just start flashing away without research.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
stoopendis said:
Well?
Click to expand...
Click to collapse
I've followed vincom's directions exactly for reflashing the phone with a stock firmware and this is what I get:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I727RUXKJ7_I727RRWCKJ7_I727RUXKJ7_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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Then I tried his directions for reflashing the phone with a CWM recovery file to no avail:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
Odin is still running so I'm not sure what to do now
Sorry guys, I've just been frustrated with hitting so many problems right from the beginning after reading through numerous guides. I guess I did rush too fast in trying to upgrade it/fix it but now I face the result of it. Hopefully I can unbrick it and learn why it wouldn't flash. As for now though I feel like I'm at a dead end because Odin is still running and it seems that it won't write for whatever reason.
flum said:
Sorry guys, I've just been frustrated with hitting so many problems right from the beginning after reading through numerous guides. I guess I did rush too fast in trying to upgrade it/fix it but now I face the result of it. Hopefully I can unbrick it and learn why it wouldn't flash. As for now though I feel like I'm at a dead end because Odin is still running and it seems that it won't write for whatever reason.
Click to expand...
Click to collapse
did you read the whole sticky, theres a troubleshooting section for odin, basically
you have a problem with
1. drivers
2. usb cable
3. usb port
go through the troubleshooting section for odin, thats why i wrote it, but if newbs arent going to read it then why the frack did i write it.
Throwing this out there.
Set time out to 10 minutes
Enable usb debugging in settings
Enable download from unknown sources
Sent from my SAMSUNG-SGH-I727 using xda premium
When I've have Odin trouble sometimes this helped.
1. Uninstall kies if you have it installed, it will leave the drivers.
2. Try a different version of Odin and /or a different USB port
3. Try a different PC
If all else fails pm me
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
stoopendis said:
Throwing this out there.
Set time out to 10 minutes
Enable usb debugging in settings
Enable download from unknown sources
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I made sure all of that was checked before I bricked the phone. Phone is completely bricked, I cannot get in to download mode or even recovery mode. It goes straight to the screen with an image of the phone yellow warning triangle and computer with the text reading "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
cdshepherd said:
When I've have Odin trouble sometimes this helped.
1. Uninstall kies if you have it installed, it will leave the drivers.
2. Try a different version of Odin and /or a different USB port
3. Try a different PC
If all else fails pm me
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I've already had Kies uninstalled before I started to actually try flashing things to the phone. I've downloaded Odin 1.8.3 and it won't recognize the phone at all. I've tried different USB ports but I get an error from Windows saying that the USB device has malfunctioned and both Windows and Odin cannot see the phone; the only way I can get my system to see the phone again is if I reboot the phone and plug it in before the error screen shows. I'm going to be doing a little more troubleshooting before I try it out with another computer which will likely be tomorrow. Thanks for all the replies so far guys I'm gonna try tinkering with the drivers but I'm worried about my system not being able to see the phone if I do. I have no access to another cable and the cable I am using is not the OEM cable that came with the phone so the problem might be that right there.
flum said:
I made sure all of that was checked before I bricked the phone. Phone is completely bricked, I cannot get in to download mode or even recovery mode. It goes straight to the screen with an image of the phone yellow warning triangle and computer with the text reading "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I've already had Kies uninstalled before I started to actually try flashing things to the phone. I've downloaded Odin 1.8.3 and it won't recognize the phone at all. I've tried different USB ports but I get an error from Windows saying that the USB device has malfunctioned and both Windows and Odin cannot see the phone; the only way I can get my system to see the phone again is if I reboot the phone and plug it in before the error screen shows. I'm going to be doing a little more troubleshooting before I try it out with another computer which will likely be tomorrow. Thanks for all the replies so far guys I'm gonna try tinkering with the drivers but I'm worried about my system not being able to see the phone if I do. I have no access to another cable and the cable I am using is not the OEM cable that came with the phone so the problem might be that right there.
Click to expand...
Click to collapse
That screen with the triangle means it's still in download mode, man
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
That screen with the triangle means it's still in download mode, man
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
:thumbup:
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
your not bricked if u see the dl screen, your on the right track for troubleshooting, just take it slow as your phone is not dead, but go through my odin troubleshooting section in the 2nd link in my sig.
kies and adb should not be running in the background, and yes get a samsung usb cable to rule out cable issues
I think your whole problem was when you did this
"Did *#7284# and switched from Modem to pda"
Ive never had to do that with mine. Just put phone in download mode. Use odin and flash. Runnin windows 7 x64 found drivers by it self.
Sent from my SGH-I727R using xda app-developers app
enegizer07 said:
I think your whole problem was when you did this
"Did *#7284# and switched from Modem to pda"
Ive never had to do that with mine. Just put phone in download mode. Use odin and flash. Runnin windows 7 x64 found drivers by it self.
Sent from my SGH-I727R using xda app-developers app
Click to expand...
Click to collapse
he did get into dl mode, the problem is the computer wont see the phone
Related
Alright, going to post here because I have been searching for hours and still no solution that I can come up with. Hoping the experts here can help me with some information on how I can fix my phone (if possible at this point).
Verizon Galaxy Siii (originally with the Hyperdrive Rom) Tried to go to 10.2 CM:
4.1.2 (I believe)
Current status:
Soft Brick (? -i'm guessing it's a soft brick because I can still access download mode).
When I try to access recovery mode it states: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Download Mode Notifications:
Product Name: SCH-i535
Custom Binary Download : Yes (4 counts)
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secureboot: Enabled.
Originally tried to flash 10.2 CM but got stock on the boot up screen so tried to go back to stock.
Phone had some possible hardware/software issues with the phone's screen constantly turning on and off (also the shut down pop-up menu would pop-up); ended up mid=process having my phone shutdown while installing a rom ( i think it was late at night and i was tired )
Tried a few variations to get back to an official release for the Verizon Galaxy SIII. This is what I've been I've trying to flash via odinVRBLK3_Image_WIPE\COMBINATION_I535VRBLK3_I535VZWBLK3_381038_REV09_user_low_ship.tar.md5)
/ --Auto Reboot & F. Reset Time are both checked--/
When I would flash the VRBLK3....tar.md5 file via Odin, it would fail, often at different times during the installation; some within a minute, some near the end of the installation.).
Odin Results:
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __Xmit Write fail
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've been reading that I need to reset the custom binary download back to : No or 0 in order for me to go back to stock? Is this true? My phone is unable to full turn on so the possibility of me using Triangle Away is not possible. Is there any other way I can get my phone back to stock--going delusional and tired from searching all day--need your help. thanks in advance!
jayun28 said:
Alright, going to post here because I have been searching for hours and still no solution that I can come up with. Hoping the experts here can help me with some information on how I can fix my phone (if possible at this point).
Verizon Galaxy Siii (originally with the Hyperdrive Rom) Tried to go to 10.2 CM:
4.1.2 (I believe)
Current status:
Soft Brick (? -i'm guessing it's a soft brick because I can still access download mode).
When I try to access recovery mode it states: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Download Mode Notifications:
Product Name: SCH-i535
Custom Binary Download : Yes (4 counts)
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secureboot: Enabled.
Originally tried to flash 10.2 CM but got stock on the boot up screen so tried to go back to stock.
Phone had some possible hardware/software issues with the phone's screen constantly turning on and off (also the shut down pop-up menu would pop-up); ended up mid=process having my phone shutdown while installing a rom ( i think it was late at night and i was tired )
Tried a few variations to get back to an official release for the Verizon Galaxy SIII. This is what I've been I've trying to flash via odinVRBLK3_Image_WIPE\COMBINATION_I535VRBLK3_I535VZWBLK3_381038_REV09_user_low_ship.tar.md5)
/ --Auto Reboot & F. Reset Time are both checked--/
When I would flash the VRBLK3....tar.md5 file via Odin, it would fail, often at different times during the installation; some within a minute, some near the end of the installation.).
Odin Results:
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __Xmit Write fail
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've been reading that I need to reset the custom binary download back to : No or 0 in order for me to go back to stock? Is this true? My phone is unable to full turn on so the possibility of me using Triangle Away is not possible. Is there any other way I can get my phone back to stock--going delusional and tired from searching all day--need your help. thanks in advance!
Click to expand...
Click to collapse
Also experiencing the same exact thing right now. Already tried Odin on 3 computers. Right now I'm reading up on heimdall and looking for files I can use with it.
I've had success with the images in this thread:
http://forum.xda-developers.com/showthread.php?t=1984436
BattsNotIncld said:
I've had success with the images in this thread:
http://forum.xda-developers.com/showthread.php?t=1984436
Click to expand...
Click to collapse
failed
"<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_VZW_I535VRBMA2_nowipe.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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> cache.img.ext4
<ID:0/003> __Xmit Write fail
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
""
A few things:
1) Are you using a good quality USB cable? Certain cheap aftermarket ones will cause ODIN fail issues. The one from Samsung that came with the phone is good.
2) Try a different USB port, specifically one connected directly to the motherboard (if you're using a tower pc hook it up to the back, on a laptop hook it up to the usb ports next to the video/audio inputs)
3) Make sure all the correct Samsung drivers are installed on to your PC, and reboot the PC after they are installed.
4) What version of ODIN are you using? v3.07 is what I use and I've never had issues
BattsNotIncld said:
A few things:
1) Are you using a good quality USB cable? Certain cheap aftermarket ones will cause ODIN fail issues. The one from Samsung that came with the phone is good.
2) Try a different USB port, specifically one connected directly to the motherboard (if you're using a tower pc hook it up to the back, on a laptop hook it up to the usb ports next to the video/audio inputs)
3) Make sure all the correct Samsung drivers are installed on to your PC, and reboot the PC after they are installed.
4) What version of ODIN are you using? v3.07 is what I use and I've never had issues
Click to expand...
Click to collapse
Just to add to this, if you are using a laptop it should be plugged in while doing this. Odd thing I've seen over the years is a lot of failures with ODIN on a laptop if it is not plugged in.
BattsNotIncld said:
A few things:
1) Are you using a good quality USB cable? Certain cheap aftermarket ones will cause ODIN fail issues. The one from Samsung that came with the phone is good.
2) Try a different USB port, specifically one connected directly to the motherboard (if you're using a tower pc hook it up to the back, on a laptop hook it up to the usb ports next to the video/audio inputs)
3) Make sure all the correct Samsung drivers are installed on to your PC, and reboot the PC after they are installed.
4) What version of ODIN are you using? v3.07 is what I use and I've never had issues
Click to expand...
Click to collapse
Got the process to pass but now I'm stuck at the Verizon 4G LTE rainbow screen for approximately 30+ minutes :\
jayun28 said:
Got the process to pass but now I'm stuck at the Verizon 4G LTE rainbow screen for approximately 30+ minutes :\
Click to expand...
Click to collapse
Factory reset?
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
Factory reset?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Yes, a factory reset will work for sure.
Sent from my SCH-I535 using Tapatalk 2
Locklis Health
Back to stock! Appreciate all the help!
Accidentally bricked my phone. Changed file called secsettings.apk to secsettings.apk.bak and completely ****ed it up. I can't mount it using my recovery, and when I can somehow manage to get it to connect to my PC, it cant install drivers for some reason. Only way I can really get files onto my phone is via Odin3 and Download Mode. I've tried Converting the rom i was running on into a .tar file and had no luck. Also tried .gz, no luck. I have no idea what to do. I'm kinda screwed for now. Whenever I try sending the rom file across on Odin, I get
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<OSM> All threads completed. (succeed 0 / failed 1)
Should I test my luck and take it back to Best Buy? I doubt its under warranty after I rooted and everything.
Also, It has something to do with MTP being corrupted I think. I have tried my phone across multiple computers, running linux, windows, etc. and all have had issues with MTP connection. Not sure if that does anything.
ToeJullar said:
Accidentally bricked my phone. Changed file called secsettings.apk to secsettings.apk.bak and completely ****ed it up. I can't mount it using my recovery, and when I can somehow manage to get it to connect to my PC, it cant install drivers for some reason. Only way I can really get files onto my phone is via Odin3 and Download Mode. I've tried Converting the rom i was running on into a .tar file and had no luck. Also tried .gz, no luck. I have no idea what to do. I'm kinda screwed for now. Whenever I try sending the rom file across on Odin, I get
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<OSM> All threads completed. (succeed 0 / failed 1)
Should I test my luck and take it back to Best Buy? I doubt its under warranty after I rooted and everything.
Also, It has something to do with MTP being corrupted I think. I have tried my phone across multiple computers, running linux, windows, etc. and all have had issues with MTP connection. Not sure if that does anything.
Click to expand...
Click to collapse
Did you try using this to Odin http://forum.xda-developers.com/showthread.php?t=2737112 ?
miked63017 said:
Did you try using this to Odin http://forum.xda-developers.com/showthread.php?t=2737112 ?
Click to expand...
Click to collapse
I'll download this now, let you know if I get a successful flash.
miked63017 said:
Did you try using this to Odin http://forum.xda-developers.com/showthread.php?t=2737112 ?
Click to expand...
Click to collapse
THANK YOU SO MUCH! This worked perfectly!
To anyone else who bricks their phone, put your phone into download mode, flash this file using Odin. Works like a charm.
I'm trying to follow this guide: http://forum.xda-developers.com/showthread.php?t=1705260
But the instructions don't work for me. The only way I can make Odin detect my phone is if I start the phone normally (no usb debug, no download mode), connect the usb cable, and when prompted on my phone, select 'firmware update (kies)'.
Then the box on Odin goes yellow as OP says, and it's writen 0:[COM3]
Is that correct? Can I go ahead with rooting like this? I'm going to be installing Beansprout.
Edit:
I tried it anyway, and it failed (0 success 1 fail)
How can I get it to be detected in download mode then?
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_UCLB3.tar.md5 is valid.
<OSM> PHONE_UCLB3.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..
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_UCLB3.tar.md5 is valid.
<OSM> PHONE_UCLB3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Removed!!
Y.June said:
I'm trying to follow this guide: http://forum.xda-developers.com/showthread.php?t=1705260
But the instructions don't work for me. The only way I can make Odin detect my phone is if I start the phone normally (no usb debug, no download mode), connect the usb cable, and when prompted on my phone, select 'firmware update (kies)'.
Then the box on Odin goes yellow as OP says, and it's writen 0:[COM3]
Is that correct? Can I go ahead with rooting like this? I'm going to be installing Beansprout.
Edit:
I tried it anyway, and it failed (0 success 1 fail)
How can I get it to be detected in download mode then?
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_UCLB3.tar.md5 is valid.
<OSM> PHONE_UCLB3.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..
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_UCLB3.tar.md5 is valid.
<OSM> PHONE_UCLB3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
Hey there,
I am assuming you have no trouble getting into download mode, and Kies is not running at the time?
Kies didn't work for me when it came to appropriate drivers. I ended up using generic Android drivers for stuff like ADB and download mode. The drivers in this package may work for you:
http://forum.xda-developers.com/showthread.php?t=2588979
Hope this helps.
joel.maxuel said:
Hey there,
I am assuming you have no trouble getting into download mode, and Kies is not running at the time?
Kies didn't work for me when it came to appropriate drivers. I ended up using generic Android drivers for stuff like ADB and download mode. The drivers in this package may work for you:
http://forum.xda-developers.com/showthread.php?t=2588979
Hope this helps.
Click to expand...
Click to collapse
Unfortunately the new drivers didn't help, it's still not detected while in download mode, only when the phone is booted.
Yes, I can enter download mode (robot with a shovel).
When I first tried, Kies was running (didn't know it wasn't supposed to). I uninstalled to be sure it wouldn't run. When that didn't work I installed it again but made sure to close it before trying Odin.
Does it matter if usb debug is on or off? The OP doesn't say either way.
The phone is only detected in Kries firmware update mode (shows up as COM3) or Usb debug mode (shows up as COM4)
State of debug mode shouldn't matter, only matters for ADB (I think). But I would leave it on just in case.
I don't think the availability of COM ports makes any difference either.
Sorry, I am out of ideas for now.
Sent from my MyTouch 4G Slide using XDA Free mobile app
Code:
Beanstalk install instructions:
http://forum.xda-developers.com/showthread.php?t=2091900
Coming from Froyo(2.2) Gingerbread(2.3) or ICS(4.0)
Obtain CWM, this can be done using Jscotts Odin back to stock (Follow instructions and use SGS kernal flasher to obtain CWM)
Run Qksters IMEI backup script here
Make certain you are on ICS, this can be done by flashing Entropy's CM9
It is recommended now that you remove your SD Card
CWM: Wipe Cache / Factory Reset
Install ROM
... The package will start to install..
... Phone will reboot into the install screen again...
... Continue to install [Automatically] If not manually flash again
... Phone will reboot again and be at the recovery screen...
Install Gapps
CWM: Wipe Cache Partition
CWM: Advanced/Wipe Dalvik Cache
Reboot
So the idea is to get gingerbread on my phone (with Odin) and then use SGS kernel flasher to install CWM.
If I understood that right, I wonder if I can just use SuperOneClick to install gingerbread, then use the kernel flasher to install CWM.
I do have the kernel flasher on my froyo, but I guess it needs to be gingerbread.
Edit: well, scratch that, 2.3.3 superoneclick download not available :/
Edit: firmware 2.2 is froyo, right? I mean, it says that, and build number froyo, but my kernel version is 2.6.32.9
Alas, another edit! I could try installing jellybean (guide page 1, page 2) but again, that needs superoneclick for which there is no download available unless I'm mistaken.
Y.June said:
Code:
Beanstalk install instructions:
http://forum.xda-developers.com/showthread.php?t=2091900
Coming from Froyo(2.2) Gingerbread(2.3) or ICS(4.0)
Obtain CWM, this can be done using Jscotts Odin back to stock (Follow instructions and use SGS kernal flasher to obtain CWM)
Run Qksters IMEI backup script here
Make certain you are on ICS, this can be done by flashing Entropy's CM9
It is recommended now that you remove your SD Card
CWM: Wipe Cache / Factory Reset
Install ROM
... The package will start to install..
... Phone will reboot into the install screen again...
... Continue to install [Automatically] If not manually flash again
... Phone will reboot again and be at the recovery screen...
Install Gapps
CWM: Wipe Cache Partition
CWM: Advanced/Wipe Dalvik Cache
Reboot
So the idea is to get gingerbread on my phone (with Odin) and then use SGS kernel flasher to install CWM.
If I understood that right, I wonder if I can just use SuperOneClick to install gingerbread, then use the kernel flasher to install CWM.
I do have the kernel flasher on my froyo, but I guess it needs to be gingerbread.
Edit: well, scratch that, 2.3.3 superoneclick download not available :/
Edit: firmware 2.2 is froyo, right? I mean, it says that, and build number froyo, but my kernel version is 2.6.32.9
Alas, another edit! I could try installing jellybean (guide page 1, page 2) but again, that needs superoneclick for which there is no download available unless I'm mistaken.
Click to expand...
Click to collapse
2.2 is Froyo. Kernel Version 2.6.x has to do with the Linux counterpart, not much to be concerned about at this point.
My concern with SuperOneClick is that if something goes wrong, you will be unable to flash back to Froyo. Best to get Odin working in Download Mode first.
A quick search ("no odin in download mode") found this thread (on a different Samsung device):
http://forum.xda-developers.com/showthread.php?t=2561137
So your fix may involve a different version of Odin, a different USB cable (and as a note from some place else) you may want to make sure you are not using a USB 3.0 port (2.0 preferred), and connected straight from the motherboard (no hubs). This may not be a requirement for Odin, but I've seen the recommendation (and it's a requirement for certain HTC tasks).
Edit: ... argh... I did the install recommended to fix the rainbow screen and now the phone is bricked. No signs of life.
I guess it was too good to be true.
Don't do the bootloader he tells you to install to fix rainbow screen.
No download mode, no recovery mode. If I go into recovery mode it just gives me some red letters about RST_stat, IRQ, and some hexcodes (those 0x000 numbers)
Click to expand...
Click to collapse
Edit again! I fixed it! I was all ready to get a usb jig. When I tried to go to download mode nothing happened at all. But instead of plugging in the cable to the phone and then to the computer, I plugged it to the computer first and then the phone. It gave me download mode! I thought this was bricked for sure!
So I can't do emergency recovery mode from kries mini, it only gives the option from the 'firmware update' option you get when connecting the phone while it's booted in.
That means I need to do Odin again... I hope it works! This time I won't do the rainbox fix. I'll just deal with it. Rainbows are pretty anyway.
Click to expand...
Click to collapse
I got Odin to work and install! After uninstalling drivers and rebooting over and over, and installing the samsung driver that was in that link you posted.
Thanks!
This is what I was typing before I got it to work so I'll post it anyway. It might be helpful for someone:
I found a samsung.com link for installing gingerbread. I can't link on forums yet so just google this:
AT&T Cell Phones: How Do I Update My Infuse 4G (SGH-i997) Mobile Device to Android 2.3 (Gingerbread) Operating System?
Click to expand...
Click to collapse
I did try it,it was detected fine, and started installing after Kris Mini put the phone in download mode. But a bit after installing it failed. However, the website does have some more troubleshooting info that could help someone. The website does say kries 3 is not compatible with this model, you have to download kries mini.
Here's the troubleshooting info:
Basic Troubleshooting
General
If you are unable to download an install the Kies mini application you may need to disable all Firewall & Anti-Virus Programs.
Kies Mini Does Not Detect The Phone
Remove previously installed Samsung software and drivers. PC Studio, New PC Studio, or Kies can cause driver conflicts. Uninstall these applications/drivers and reinstall Kies mini.
Enable USB debugging mode before connect your device to the PC.
Close the Kies mini application.
On you device press Menu Menu >Settings > Applications > Development > USB debugging to place a checkmark.
Reopen the Kies mini application.
Reconnect your device to the PC.
You may have changed your default USB settings. To check your USB settings follow the instructions below.
Close the Kies mini application.
On you device press Menu Menu > Settings > Applications > USB settings.
Touch Kies (Firmware update).
Reopen the Kies mini application.
Reconnect your device to the PC.
Download or update Windows Media Player to the latest version. Click here for the Windows Media player update website.
Remove previously installed service provider applications (ACM, VMM, etc…). These applications may cause driver conflicts. Uninstall these applications and reinstall Kies mini.
Depending on the amount of data stored in the phone memory, this could impair Kies Mini's ability to detect the device. It may be necessary to remove the microSD card (Requirements). Should problems persist, the internal memory may need to be purged. Backup all desired data (using instructions provided above) and then go to Menu > Settings > Privacy > Factory Data Reset. Follow the onscreen instructions and after reboot, attempt to connect to Kies Mini.
The Media Scan process could produce a loop if connected while in progress. If this occurs, disconnect and power cycle the device. Wait until the device fully boots and the process is finished before connecting again.
When the handset goes into download mode instructed by Kies Mini, additional drivers need to be installed. A timeout may occur from the time the drivers install until Kies Mini can detect. Should this occur, close Kies Mini and remove the cable. Next, remove the battery cover and battery. Afterwards, insert the battery, place the cover back on, and power on the device. When the device reboots, connect the data cable and open Kies Mini.
Click to expand...
Click to collapse
Y.June said:
I got Odin to work and install! After uninstalling drivers and rebooting over and over, and installing the samsung driver that was in that link you posted.
Thanks!
Click to expand...
Click to collapse
Glad I could be of help. If the ADB/Driver package post was helpful, feel free to thank it.
Y.June said:
That means I need to do Odin again... I hope it works! This time I won't do the rainbox fix. I'll just deal with it. Rainbows are pretty anyway.
Click to expand...
Click to collapse
With regard to the rainbow bug, if I recall correctly the ROM's don't have that issue, so you may want to explore Cyanogenmod or Beanstalk (et cetera). I found CM 10.1 useful* (albeit with a few minor bugs), although it seems everyone has moved on to KitKat.
Just a thought. Gingerbread is a bit long in the tooth these days, but you may be set on sticking with stock for a while. (For the record, there is nothing wrong with the OS itself, it's that the app selection is starting to narrow.)
Good luck!
* I tried CM 10.2. I'm not sure if it was my phone (Rogers), or a bad download, but I could not finish the install and CWM was so borked I had to Odin back to stock and start over. I thus gave up on trying anything newer.
go up too CarbonRom latest nightly 4.4.2 KitKat https://carbonrom.org/downloads/?device=infuse4g&type=nightly its almost perfect
My phone appears to be in a bootloop as it is stuck on the Samsung Galaxy Note GT-N7000 Screen. I cannot access recovery mode, I can only access Downloading Mode. It started when I used Rom Manager to flash CWM to my device and do a backup. I have tried flashing a stock ROM to my device but ODIN (v3.9) gives me the following error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLT9_N7000XXLT3_N7000ORALT3_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
And shows a FAIL at the top in red.
Does anyone have any suggestions? Any help would be much appreciated.
Thank you.
Update:
After searching around it appears I may need to use PIT file, is this the case and does anyone know where I would get one for my device?
ivel97 said:
My phone appears to be in a bootloop as it is stuck on the Samsung Galaxy Note GT-N7000 Screen. I cannot access recovery mode, I can only access Downloading Mode. It started when I used Rom Manager to flash CWM to my device and do a backup. I have tried flashing a stock ROM to my device but ODIN (v3.9) gives me the following error:
And shows a FAIL at the top in red.
Does anyone have any suggestions? Any help would be much appreciated.
Thank you.
Update:
After searching around it appears I may need to use PIT file, is this the case and does anyone know where I would get one for my device?
Click to expand...
Click to collapse
Sure HERE you can download ODIN 1.85 + PIT file. Make sure to choose the correct PIT size 16/32GB
ivel97 said:
My phone appears to be in a bootloop as it is stuck on the Samsung Galaxy Note GT-N7000 Screen. I cannot access recovery mode, I can only access Downloading Mode. It started when I used Rom Manager to flash CWM to my device and do a backup. I have tried flashing a stock ROM to my device but ODIN (v3.9) gives me the following error:
And shows a FAIL at the top in red.
Does anyone have any suggestions? Any help would be much appreciated.
Thank you.
Update:
After searching around it appears I may need to use PIT file, is this the case and does anyone know where I would get one for my device?
Click to expand...
Click to collapse
I don't think so that the problem is the PIT file. Because it fails after SetupConnection. Are you sure you are you using the original usb cable. You can try with other usb cables to confirm it.
root-expert said:
I don't think so that the problem is the PIT file. Because it fails after SetupConnection. Are you sure you are you using the original usb cable. You can try with other usb cables to confirm it.
Click to expand...
Click to collapse
Suggested ODIN version for GT-N7000 is 1.85 (as I linked it). Could also be related to a wrong version of ODIN.
Thanks for the suggestions. I have tried different versions of ODIN. I'll have a go with different USB cables.
root-expert said:
I don't think so that the problem is the PIT file. Because it fails after SetupConnection. Are you sure you are you using the original usb cable. You can try with other usb cables to confirm it.
Click to expand...
Click to collapse
I don't have the original Samsung charging cable that came with my device. I looked online for some and found one that claims to work for all Note models, does that sound right?
root-expert said:
I don't think so that the problem is the PIT file. Because it fails after SetupConnection. Are you sure you are you using the original usb cable. You can try with other usb cables to confirm it.
Click to expand...
Click to collapse
I bought a new cable for the Note, still getting the same error. Any suggestions?
ivel97 said:
I bought a new cable for the Note, still getting the same error. Any suggestions?
Click to expand...
Click to collapse
Kill all kies proccess and try again. Also enable usb debugging.
root-expert said:
Kill all kies proccess and try again. Also enable usb debugging.
Click to expand...
Click to collapse
I uninstalled keis (not the USB driver) and I can't enable USB debugging because the phone is in a boot loop.
Then make sure that you have installed the correct drivers. Also try to download odin from other sites.
root-expert said:
Then make sure that you have installed the correct drivers. Also try to download odin from other sites.
Click to expand...
Click to collapse
Tried both. Sorry.
I think I'll just give up and take it to a phone repair shop, see what they can do. :crying:
ivel97 said:
Tried both. Sorry.
I think I'll just give up and take it to a phone repair shop, see what they can do. :crying:
Click to expand...
Click to collapse
Remove your bettery and leave it for 5 minutes. Then go again to download mode and flash with odin. Also you can try defferent usb ports and ensure that you don't use a usb hub! Finally nesure that you are running odin as admin.
root-expert said:
Remove your bettery and leave it for 5 minutes. Then go again to download mode and flash with odin. Also you can try defferent usb ports and ensure that you don't use a usb hub! Finally nesure that you are running odin as admin.
Click to expand...
Click to collapse
ODIN got a little further this time. Still stuck on cache.img, though.
<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> cache.img
Click to expand...
Click to collapse
ivel97 said:
ODIN got a little further this time. Still stuck on cache.img, though.
Click to expand...
Click to collapse
Now you have to check that the file you have downloaded is correct. Maybe you can check the md5 checksum or something. Or simply redownload it. Which step fixed your issue?
root-expert said:
Now you have to check that the file you have downloaded is correct. Maybe you can check the md5 checksum or something. Or simply redownload it. Which step fixed your issue?
Click to expand...
Click to collapse
Changing USB port I think, maybe in conjunction with new cable because I've tried changing ports before. Also made sure I started in admin. Odin checks the md5 checksum automatically but I'm downloading it again. Got the stock firmware off sammobile.com . Using the UK Orange version - XXLT9. I think that is the right one from memory. Can't check build setting because I'm stuck in bootloop. Pain.
EDIT:
Damn. Just tried again with ODIN 1.85 and it gets stuck on setup connection again. Same with v3.09.
ivel97 said:
Changing USB port I think, maybe in conjunction with new cable because I've tried changing ports before. Also made sure I started in admin. Odin checks the md5 checksum automatically but I'm downloading it again. Got the stock firmware off sammobile.com . Using the UK Orange version - XXLT9. I think that is the right one from memory. Can't check build setting because I'm stuck in bootloop. Pain.
EDIT:
Damn. Just tried again with ODIN 1.85 and it gets stuck on setup connection again. Same with v3.09.
Click to expand...
Click to collapse
Do the same with the battery
root-expert said:
Do the same with the battery
Click to expand...
Click to collapse
Taking out the battery fixed the setup connection error. Thanks!!! Still failing on cache.img, though. Waiting for the stock Rom from sammobile.com to finish downloading and I'll try again.
root-expert said:
Do the same with the battery
Click to expand...
Click to collapse
Redownloaded the stock firmware from sammobile and tried again. Failing after cache.img.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLT9_N7000XXLT3_N7000ORALT3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> cache.img
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
ivel97 said:
Redownloaded the stock firmware from sammobile and tried again. Failing after cache.img.
Click to expand...
Click to collapse
Have you already try to flash .pit file. I recomend you don't because if odin fail to flash it your phone will f*** up. So this is your last resort. You can try different roms. You can try to use heimdall for windows to flash your firmware. Heimdall is more reliable
root-expert said:
Have you already try to flash .pit file. I recomend you don't because if odin fail to flash it your phone will f*** up. So this is your last resort. You can try different roms. You can try to use heimdall for windows to flash your firmware. Heimdall is more reliable
Click to expand...
Click to collapse
Not tried to flash .pit file. I'll try heimdall, thanks.
so i have Kies not running in the background and have downloaded the appropriate Firmware from SAM Mobile but odin is still giving me issues saying...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cm.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Odin has been Admined, and i followed a couple of youtube videos but still once again i keep failing. HELP PLEASE.
[email protected] said:
so i have Kies not running in the background and have downloaded the appropriate Firmware from SAM Mobile but odin is still giving me issues saying...
Odin has been Admined, and i followed a couple of youtube videos but still once again i keep failing. HELP PLEASE.
Click to expand...
Click to collapse
Need some more info on your setup.
Laptop or desktop, location of USB ports (hubs and front USB can be problematic), OS, ODIN version.
NotATreoFan said:
Need some more info on your setup.
Laptop or desktop, location of USB ports (hubs and front USB can be problematic), OS, ODIN version.
Click to expand...
Click to collapse
Im currently using my Samsung R580 Laptop with 2 USB 2.0 and 1 3.0 USB. Odin Version 3.10.7
and my Model number for the Phone is N920TZWATMB Currently with Noble Kernel V0.1
Knox Counter: 1
If you need any more information please ask.
re: odin flash firmware
[email protected] said:
so i have Kies not running in the background and have downloaded the appropriate Firmware from SAM Mobile but odin is still giving me issues saying...
Odin has been Admined, and i followed a couple of youtube videos but still once again i keep failing. HELP PLEASE.
Click to expand...
Click to collapse
Did you make sure to enable the "OEM Unlock" in settings>developers options before odin flashing?
If it's not enabled enable it and do the odin flash again.
By the way, you did not need to odin flash stock firmware to unroot.
All you needed to do is to go into your app drawer and open supersu
then in it's settings you simply disable it.
If you wanted to leave the phone unrooted then after disabling supersu
you can simply uninstall it.
Good luck,
Have a great day!
My OEM Unlock switch has been on since a while ago. The thing is when ever i try to update my phone to the latest firmware it stays at 0 on my computer. Ive tried that method before but i still have problems with the random reboot.
[email protected] said:
My OEM Unlock switch has been on since a while ago. The thing is when ever i try to update my phone to the latest firmware it stays at 0 on my computer. Ive tried that method before but i still have problems with the random reboot.
Click to expand...
Click to collapse
Have you tried all the USB ports? USB 3.0 ports can be picky and sometimes ODIN and ADB commands don't work properly. Also make sure to either use the official Samsung cable or at least one that can Fast Charge when plugged into the phone. The cheaper cables will sometimes cause communication issues.
Also, what version of Windows? I'm currently on Windows 10 x64, but also used ODIN on my Galaxy S5 when I was on Windows 8.1 x64.
I have tried all my cables and the original samsung died on me cuz of the nephews
Can i get an mod to lock this post? I found what i was doing wrong. Thanks to all those who tried helping!
[email protected] said:
Can i get an mod to lock this post? I found what i was doing wrong. Thanks to all those who tried helping!
Click to expand...
Click to collapse
can you share what you were doing wrong? i am having the same issue and might be doing the same.
Thanks
ogsmokey said:
can you share what you were doing wrong? i am having the same issue and might be doing the same.
Thanks
Click to expand...
Click to collapse
I downloaded the latesr smart switch and looked at the latest update. Then look for the same update on Sammobile. So from COJ5 to COI5.
The latest version is coj5 in order to go back to stock you have to flash it via odin and make sure you factory reset after that if it bootloop after flashing
Sent From My SM-N920T Using Tapatalk
TEKHD ROM[Advanced Hybrid Edition ll][UrV4.1]