My coworker gave me his Verizon S3 on 4.3 I was going to try to unlock it for TMobile by following this thread and not realizing that I wouldn't be able to flash the custom JB image because I was on 4.3. Needless to say, it didn't work. Odin failed repeatedly. Well one time it hung but I thought it was just orphaned so I unplugged my phone. Bam, soft brick.
I got the stock Verizon image here and tried to ODIN it back to stock. I fail at aboot. I tried the stock PIT along with the stock image. Failed.
I tried SUA and its stuck at 83% and has been for over an hour.
I tried Kies and it does not even recognize the device but does know when I unplug it.
I just want to get it to stock so I can root. Any help is appreciated.
I should add I am on a Macbook Pro using VM Fusion. I don't have another Win 7 machine. I do have an Ubuntu box and my wife's Win 8 laptop.
HotShotAzn said:
My coworker gave me his Verizon S3 on 4.3 I was going to try to unlock it for TMobile by following this thread and not realizing that I wouldn't be able to flash the custom JB image because I was on 4.3. Needless to say, it didn't work. Odin failed repeatedly. Well one time it hung but I thought it was just orphaned so I unplugged my phone. Bam, soft brick.
I got the stock Verizon image here and tried to ODIN it back to stock. I fail at aboot. I tried the stock PIT along with the stock image. Failed.
I tried SUA and its stuck at 83% and has been for over an hour.
I tried Kies and it does not even recognize the device but does know when I unplug it.
I just want to get it to stock so I can root. Any help is appreciated.
I should add I am on a Macbook Pro using VM Fusion. I don't have another Win 7 machine. I do have an Ubuntu box and my wife's Win 8 laptop.
Click to expand...
Click to collapse
Use this guide, and specifically use jodin and follow the directions:
http://forum.xda-developers.com/showthread.php?t=2586319
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Use this guide, and specifically use jodin and follow the directions:
http://forum.xda-developers.com/showthread.php?t=2586319
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the tip. I tried JODIN but it sits in a "RUNNING" status for a long time. Like I left it for over an hour and it still just said "running".
HotShotAzn said:
Thanks for the tip. I tried JODIN but it sits in a "RUNNING" status for a long time. Like I left it for over an hour and it still just said "running".
Click to expand...
Click to collapse
Somethings wrong then, did you use the pit file?
I say unplug it and give it a shot again. Try a better cable if you have one.
Somebody else reported the same thing and I couldn't figure it out.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Somethings wrong then, did you use the pit file?
I say unplug it and give it a shot again. Try a better cable if you have one.
Somebody else reported the same thing and I couldn't figure it out.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Correct, I used the PIT file for the 16GB S3.
I switched to the Windows version and let it run. It finished and said no changes were made. Rerunning it now.
I have a couple more cables at home (stock factory) so we'll give that a whirl.
Well its off and running. Task manager has it using about half a gig of memory and CPU bounces so it looks like its doing something. I guess I'll just keep my fingers crossed.
Well nada. It ran for over two hours and nothing. Not sure where the disconnect is.
I'm at home now and am going to try with a different cord.
Is there even a good indicator of JODIN running besides watching CPU/Memory?
A handful of people seem to get stuck at 83%. I'll try to look into the problem when I get the time. In odin how far did it get before it failed? Just so I know I'm explaining properly what part is odin flashing.
ThePagel said:
A handful of people seem to get stuck at 83%. I'll try to look into the problem when I get the time. In odin how far did it get before it failed? Just so I know I'm explaining properly what part is odin flashing.
Click to expand...
Click to collapse
Thanks! I appreciate the offer for help!
This is the furthest that Odin has gone. I had just removed all Samsung drivers and rebooted.
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> sbl1.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl2.mbn
<ID:0/008> sbl3.mbn
<ID:0/008> aboot.mbn
<ID:0/008> rpm.mbn
<ID:0/008> tz.mbn
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
HotShotAzn said:
Thanks! I appreciate the offer for help!
This is the furthest that Odin has gone. I had just removed all Samsung drivers and rebooted.
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> sbl1.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl2.mbn
<ID:0/008> sbl3.mbn
<ID:0/008> aboot.mbn
<ID:0/008> rpm.mbn
<ID:0/008> tz.mbn
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
A few things to try before I start looking into more drastic options. I did a quick google search and it seems the gs4 people have a similar problem but at 66%. One person said that by using the usb on the actual motherboard not the front or pci/pcie slot it worked. I would add a recommendation of uninstalling the drivers restart the pc then reinstall the drivers without the phone plugged in restart again and make sure you use a built in usb 2.0 (make sure its not 3.0 or 1.1). also if you have the samsung usb cable use that if you don't and fail try a different one. if you tried everything and you do have a usb 3.0 it couldn't hurt to try it (the first time I used the verizon utility was on 3.0 and it worked fine for me). I will hopefully have time tomorrow to explore this a little but my schedule is packed. I can look at the forums on my phone every hour or so but no access to a computer because I am running around.
Ideas that came right before I hit submit but I don't feel like changing my post:
Make sure your pc is updated 100% (especially drivers, you may need to go to the manufacturers website to get motherboard drivers. widows update is ok but not 100% recent)
Make sure you install the phone drivers with kies (check the install unified drivers option at the end of install. or if its already installed click trouble shoot connection in kies)
Make sure kies is completely closed before you open odin or verizon utility (Reboot should take care of that)
Before you open odin or verizon utility make sure no unneeded programs are running (once again that last restart should take care of that unless you have programs auto launch on start up)
Open odin or Verizon utility as administrator
Lastly if you go to try a different usb cable or port you should click that trouble shoot connection button then make sure you completely close kies before you plug the phone in. I know that sounds like a pain but its the only way to make sure every base has been covered. sometimes the biggest problems are from the smallest detail. Also it looks like it is running fine until you get to the big file which is the system file. I am wondering if perhaps you are on a usb 1.1 and that is why the over one gigabyte file fails to transfer.
ThePagel said:
A few things to try before I start looking into more drastic options. I did a quick google search and it seems the gs4 people have a similar problem but at 66%. One person said that by using the usb on the actual motherboard not the front or pci/pcie slot it worked. I would add a recommendation of uninstalling the drivers restart the pc then reinstall the drivers without the phone plugged in restart again and make sure you use a built in usb 2.0 (make sure its not 3.0 or 1.1). also if you have the samsung usb cable use that if you don't and fail try a different one. if you tried everything and you do have a usb 3.0 it couldn't hurt to try it (the first time I used the verizon utility was on 3.0 and it worked fine for me). I will hopefully have time tomorrow to explore this a little but my schedule is packed. I can look at the forums on my phone every hour or so but no access to a computer because I am running around.
Ideas that came right before I hit submit but I don't feel like changing my post:
Make sure your pc is updated 100% (especially drivers, you may need to go to the manufacturers website to get motherboard drivers. widows update is ok but not 100% recent)
Make sure you install the phone drivers with kies (check the install unified drivers option at the end of install. or if its already installed click trouble shoot connection in kies)
Make sure kies is completely closed before you open odin or verizon utility (Reboot should take care of that)
Before you open odin or verizon utility make sure no unneeded programs are running (once again that last restart should take care of that unless you have programs auto launch on start up)
Open odin or Verizon utility as administrator
Lastly if you go to try a different usb cable or port you should click that trouble shoot connection button then make sure you completely close kies before you plug the phone in. I know that sounds like a pain but its the only way to make sure every base has been covered. sometimes the biggest problems are from the smallest detail. Also it looks like it is running fine until you get to the big file which is the system file. I am wondering if perhaps you are on a usb 1.1 and that is why the over one gigabyte file fails to transfer.
Click to expand...
Click to collapse
I'm on a Macbook Pro that is a late 2011. According to Google, I should have USB 2.0.
I am updating the Windows VM as we speak. After that, here's my plan:
1) Install updates
2) Reboot
3) Verify no Samsung drivers are installed
4) Install KIES with Unified Drivers
5) Reboot
6) Open ODIN as Admin
7) Attempt flash
My biggest concern is the fact that I am using the VM. I believe the way VMware sees the USB ports is as a hub, not native USB ports. (I hate Macs ) My only other machines are my wife's Win8 and my Ubuntu box....although I could probably go steal my folk's Win7 machine. I tried JODIN for the Mac but it really doesn't seem to be doing a whole lot.
HotShotAzn said:
I'm on a Macbook Pro that is a late 2011. According to Google, I should have USB 2.0.
I am updating the Windows VM as we speak. After that, here's my plan:
1) Install updates
2) Reboot
3) Verify no Samsung drivers are installed
4) Install KIES with Unified Drivers
5) Reboot
6) Open ODIN as Admin
7) Attempt flash
My biggest concern is the fact that I am using the VM. I believe the way VMware sees the USB ports is as a hub, not native USB ports. (I hate Macs ) My only other machines are my wife's Win8 and my Ubuntu box....although I could probably go steal my folk's Win7 machine. I tried JODIN for the Mac but it really doesn't seem to be doing a whole lot.
Click to expand...
Click to collapse
When you ran the PIT file for your phone in Odin, did you flash that PIT file by itself? Reason I ask is because I remember "Odin getting stuck at 83%" being an issue in one of the 4.3 debrick method threads. I did a few searches and found post #86 where the user fixed it by flashing both the PIT AND VRUMCL1 tar. @ThePagel will probably remember reading this as well since its kinda obscure.
Edit: I'm gonna also suggest to try either Windows laptop as well if the Windows VM isn't working for you.
SlimSnoopOS said:
When you ran the PIT file for your phone in Odin, did you flash that PIT file by itself? Reason I ask is because I remember "Odin getting stuck at 83%" being an issue in one of the 4.3 debrick method threads. I did a few searches and found post #86 where the user fixed it by flashing both the PIT AND VRUMCL1 tar. @ThePagel will probably remember reading this as well since its kinda obscure.
Edit: I'm gonna also suggest to try either Windows laptop as well if the Windows VM isn't working for you.
Click to expand...
Click to collapse
PIT and tar file both.
So with KIES unified drivers, I fail at aboot.mbn. With "native" drivers that are installed without any additional installs, I get to the recovery.img.
I'm going to try the wife's Win 8 laptop.
Any ideas why even JODIN isn't working?
HotShotAzn said:
PIT and tar file both.
So with KIES unified drivers, I fail at aboot.mbn. With "native" drivers that are installed without any additional installs, I get to the recovery.img.
I'm going to try the wife's Win 8 laptop.
Any ideas why even JODIN isn't working?
Click to expand...
Click to collapse
I haven't a clue, I'm unfamiliar with JODIN. Haven't seen it mentioned too often so I haven't attempted to learn what its about. I might change that this weekend after work though.
Well @ThePagell, @SlimSnoopOS, @BadUsername looks like this is resolved.
Macs do not play well with Androids...at least in my case and with the S3. I had no problem using ADB with my S2. My wife's Win 8 laptop installed native drivers and is flashing using Odin 3.09 as we speak. No updating this or installing that. "It just works" (haha, ok, i'm done now).
Thanks for your time and your suggestions. I personally disliked my MBP but its what my work gave me and I'm too cheap to go buy a laptop although this experience has reiterated the need for a dedicated Win 7 machine at my house.
HotShotAzn said:
Well @ThePagell, @SlimSnoopOS, @BadUsername looks like this is resolved.
Macs do not play well with Androids...at least in my case and with the S3. I had no problem using ADB with my S2. My wife's Win 8 laptop installed native drivers and is flashing using Odin 3.09 as we speak. No updating this or installing that. "It just works" (haha, ok, i'm done now).
Thanks for your time and your suggestions. I personally disliked my MBP but its what my work gave me and I'm too cheap to go buy a laptop although this experience has reiterated the need for a dedicated Win 7 machine at my house.
Click to expand...
Click to collapse
I'll take that progress! haha great job on getting this resolved!
If using the MBP I would suggest setting up a Bootcamp partition instead of a VM. Odin in VMs used to work, but not anymore. Bootcamp works well though because its native.
I had similar issues but unfortunately the only fix for me was buying a jtag service off eBay and sending them the phone. Works great afterwards.
Sent from my Amazon Kindle Fire using Tapatalk
Related
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
I have a Galaxy Tab 2 10.1 w/ JB 4.1.1 through AT&T that got screw up while rooting
I was following the guide here:
androidrooting.com/how-to-root-galaxy-tab-2-10-1-p5100/
I deviated from the guide in 1 way. When it says to select the '.zip' file, I assumed they meant the .md5, as .zip is not an option
When I hit start on Odin, Odin crashed. I loaded it up and tried it again. This time it 'failed'. My tablet rebooted to the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." So, I installed Kies on my computer and tried to do what it says. When the device is plugged in Kies tries to connect but comes back with the error "Device not responding. To fix the issue, reboot the device". I also tried using Odin again to continue where I left off, but it simply fails.
Any advice would be great. Please help, thanks!
tholt2121 said:
I have a Galaxy Tab 2 10.1 w/ JB 4.1.1 through AT&T that got screw up while rooting
I was following the guide here:
androidrooting.com/how-to-root-galaxy-tab-2-10-1-p5100/
I deviated from the guide in 1 way. When it says to select the '.zip' file, I assumed they meant the .md5, as .zip is not an option
When I hit start on Odin, Odin crashed. I loaded it up and tried it again. This time it 'failed'. My tablet rebooted to the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." So, I installed Kies on my computer and tried to do what it says. When the device is plugged in Kies tries to connect but comes back with the error "Device not responding. To fix the issue, reboot the device". I also tried using Odin again to continue where I left off, but it simply fails.
Any advice would be great. Please help, thanks!
Click to expand...
Click to collapse
I should also note that the upper right corner of the tablet says:
"ODIN MODE
PRODUCT NAME: ESPRESSO10
CUSTOM BINARY DOWNLOAD: YES (3 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
Unsupport devtype"
tholt2121 said:
I have a Galaxy Tab 2 10.1 w/ JB 4.1.1 through AT&T that got screw up while rooting
I was following the guide here:
androidrooting.com/how-to-root-galaxy-tab-2-10-1-p5100/
I deviated from the guide in 1 way. When it says to select the '.zip' file, I assumed they meant the .md5, as .zip is not an option
When I hit start on Odin, Odin crashed. I loaded it up and tried it again. This time it 'failed'. My tablet rebooted to the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." So, I installed Kies on my computer and tried to do what it says. When the device is plugged in Kies tries to connect but comes back with the error "Device not responding. To fix the issue, reboot the device". I also tried using Odin again to continue where I left off, but it simply fails.
Any advice would be great. Please help, thanks!
Click to expand...
Click to collapse
Strange, because it should work. You didn't need to select the .zip file indeed, choosing the .md5 file was the right choice. Have you tried running Odin as an administrator?
Endiej said:
Strange, because it should work. You didn't need to select the .zip file indeed, choosing the .md5 file was the right choice. Have you tried running Odin as an administrator?
Click to expand...
Click to collapse
I have not - how would I go about doing that?
tholt2121 said:
I have not - how would I go about doing that?
Click to expand...
Click to collapse
Just right click on the Odin setup file (the .exe file) and select 'Run as an administrator'. Always run as an administrator when doing something in Odin.
Try running as admin for sure. Even though my windows account is admin, odin will not flash properly. I have to run as admin for it to flash.
Sent from a rooted candy bar
Zagnutty said:
Try running as admin for sure. Even though my windows account is admin, odin will not flash properly. I have to run as admin for it to flash.
Sent from a rooted candy bar
Click to expand...
Click to collapse
I tried it running as administrator. It still didn't work. Here is the log from Odin:
<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> system.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)
Sooo.. any other thoughts on this?
I also tried using the .md5 file from this guide:
http://forum.xda-developers.com/showthread.php?t=2158914
Does the fact this is the AT&T version of the tablet make any difference
Yes the reason it isn't working may be that it was not written for the ATT Tab 2. Never try to install anything like this not written for your tablet or phone. Close does not count.
Try this proven method instead:
http://forum.xda-developers.com/showthread.php?t=2342501
Agoattamer said:
Yes the reason it isn't working may be that it was not written for the ATT Tab 2. Never try to install anything like this not written for your tablet or phone. Close does not count.
Try this proven method instead:
http://forum.xda-developers.com/showthread.php?t=2342501
Click to expand...
Click to collapse
Yes!! Thank you so much! That fixed my tablet [and rooted it]. You are amazing. It didn't strike me that my tablet had any different version.. thanks!! Now to figure out what to do with this root access...
Pay close attention. There are no ROMs on XDA for the ATT I497 Tab2. Do not attempt to install a ROM for another version of our Tab.
I am new to android.. Long time Apple user, My parents each gave me their old android phones when they upgraded; Motorolla Droid 4 and Samsung GSII Skyrocket. Anyway, I messed up the skyrocket using odin, now I cannot turn the phone on, I cant go into recovery mode or download mode. I have the proper drivers, when I plug it into the computer, and go to devices, it shows it as an unspecifed device called "Qualcomm HS-USB QDLoader 9008 (COM3)" Prior to that, it was referred to as "QHSUSB DLOAD" in device manager, but I go those drivers. Now Odin will see it, the left box goes yellow and its called "0:[COM3]" and the log says "added" I make the proper settings and set pda to a recovery ROM, hit start and it gets stuck:
"<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection.."
And then wont do anything more. Ive tried everything I have read in these forums, with no luck. I know it is bricked, but ANY advice on maybe an alternative way to get into the download or recovery mode would be appreciated. Ive had much better success with the droid 4, it's running a couple of ROMs. And I will be getting an S5 next week for my birthday... so I need to make sure I am on the up and up with Odin flashing.
seach the forum: QHSUSB DLOAD
...Never Mind...
What did you do with Odin specifically? It's very easy to do the wrong thing, either mess up the partitions or flash a ROM not meant for the phone. If you did that, the only fix is JTAG, search the forums here for how to go about that.
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.
Hi
I downloaded the UK (live in Denmark) H3G version (same firmware number as my old one), added it in Odin (newest version) and flashed.
Just before finishing up, it failed. Waited 10-20 minutes and nothing happened (cause it told me to not turn off the device or unplug).
But well nothing happened, so I unplugged and restarted phone.
Now it's at a blue screen saying: "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
I then tried that, but it says my device is unsupported.
Do anyone have any idea what to do?
Thanks in advance
EDIT THE ERROR:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU1AOCV_G920FH3G1AOC1_G920FXXU1AOCW_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1005)..
<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> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> modem.bin
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Faspaiso said:
Hi
I downloaded the UK (live in Denmark) H3G version (same firmware number as my old one), added it in Odin (newest version) and flashed.
Just before finishing up, it failed. Waited 10-20 minutes and nothing happened (cause it told me to not turn off the device or unplug).
But well nothing happened, so I unplugged and restarted phone.
Now it's at a blue screen saying: "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
I then tried that, but it says my device is unsupported.
Do anyone have any idea what to do?
Thanks in advance
EDIT THE ERROR:
Click to expand...
Click to collapse
Can you boot into download mode? press power on, volume down and home button. Then you download Samsung Kies 3 and go to "firmware upgrade and initialization", type model name "SM-G920F", then write your serial number which you can find on a sticker on back of your phone. If you can't boot into download mode its impossible to recover your phone.
Aircondition said:
Can you boot into download mode? press power on, volume down and home button. Then you download Samsung Kies 3 and go to "firmware upgrade and initialization", type model name "SM-G920F", then write your serial number which you can find on a sticker on back of your phone. If you can't boot into download mode its impossible to recover your phone.
Click to expand...
Click to collapse
Tried with Kies. It said my device is not supported and I should use Smart Switch. But was still able to continue with Kies. An error occured and Kies closed.
I then continued with Smart Switch and tried to do the same and this occured. Image not working when putting it in, so here the link is. http://prntscr.com/6vy161
I'm able to enter download mode, yes.
Faspaiso said:
Tried with Kies. It said my device is not supported and I should use Smart Switch. But was still able to continue with Kies. An error occured and Kies closed.
I then continued with Smart Switch and tried to do the same and this occured. Image not working when putting it in, so here the link is. http://prntscr.com/6vy161
I'm able to enter download mode, yes.
Click to expand...
Click to collapse
So you got to this screen and then when you plugged USB cable in it says "device is not supported"?
Also make sure you have Kies 3.0 and not earlier versions. My phone also got softbricked but you may have messed it up way more than me. Then your only option left is to flash stock rom with Odin 3.10.6, you will have to find right CSC version for your country from sammobile.com (15 kb/s download speed) or download faster with Kies client (it will save it to C:\Users\AppData\Local\Temp)
Aircondition said:
So you got to this screen and then when you plugged USB cable in it says "device is not supported"?
Also make sure you have Kies 3.0 and not earlier versions. My phone also got softbricked but you may have messed it up way more than me. Then your only option left is to flash stock rom with Odin 3.10.6, you will have to find right CSC version for your country from sammobile.com (15 kb/s download speed) or download faster with Kies client (it will save it to C:\Users\AppData\Local\Temp)
Click to expand...
Click to collapse
Thank you. It worked now.
I already got Kies 3.0 and I already tried to flash with Odin before. But well, I restarted my PC and suddenly, it worked just fine.
So thank you mate.
hello excuse English but I find myself in your same conditions and with no win 8.1 Riec it to start it in emergencies with kies it with smart switches, nor with odin pui tell me step how to solve I would be grateful
pippo74 said:
hello excuse English but I find myself in your same conditions and with no win 8.1 Riec it to start it in emergencies with kies it with smart switches, nor with odin pui tell me step how to solve I would be grateful
Click to expand...
Click to collapse
Just do what is wrote in the thread.
It worked just fine for me, after the restart on my PC, but I think it was because my network connection was going on and off, so it couldn't download the file.
I used Kies, but I think Smart Switch works just fine too.
Remember to use Kies 3.0 and put your phone into download mode.
a quick way to fix this is to flash twrp with odin...
enij said:
a quick way to fix this is to flash twrp with odin...
Click to expand...
Click to collapse
THANK YOU!!!
I know it's an old post but it saved me from going even more insane.
Flash this via odin.
http://www.sammobile.com/firmwares/download/49782/G920FXXU2BOFJ_G920FH3G2BOF1_H3G/
roydok said:
Flash this via odin.
http://www.sammobile.com/firmwares/download/49782/G920FXXU2BOFJ_G920FH3G2BOF1_H3G/
Click to expand...
Click to collapse
3 months too late, but you still get my thanks just for trying.
Help i cannot get smart switch or kies 3.0 to reconize device SM-g920f
My girlfriend S6 suffered a softbriked after a OTA update. I was about to return the phone and I was going to be a lot of problems. Thank you for saving me!!!!
Aircondition said:
So you got to this screen and then when you plugged USB cable in it says "device is not supported"?
Also make sure you have Kies 3.0 and not earlier versions. My phone also got softbricked but you may have messed it up way more than me. Then your only option left is to flash stock rom with Odin 3.10.6, you will have to find right CSC version for your country from sammobile.com (15 kb/s download speed) or download faster with Kies client (it will save it to C:\Users\AppData\Local\Temp)
Click to expand...
Click to collapse
Hi sorry to bother you but I have the same problem only mine happened when i tried to root my phone and failed, so I am now on the same blue screen as the other guy. I went onto Kies and did everything and it was working fine until it told me to put my phone into recovery mode, which I assume is download mode, and then it says start upgrade, but the box where it says this is gray and I cannot click on it. Any idea on what I can do?
ALL,
i have the same issue., i had a stock firmware and wanted another sotck firmware on the phone
the original firmware from sammobile failed via odin
i went through the smart switch pc software and it also failed near the end.
what can i do to fix the issue please.? need urgent help.
Somoeone earlier mentioned to install TWRP via odin to fix the issue, is this correct? will this trip knox when installed TWRP?
PLEASE ADVISE.
Yes it will... download the newest firmware in sammobile of your model (doesnt metter the country) and flash. Or post here the logs of odin of failing flash
lummujaj said:
Yes it will... download the newest firmware in sammobile of your model (doesnt metter the country) and flash. Or post here the logs of odin of failing flash
Click to expand...
Click to collapse
Im trying to download this version of the firmware G920FXXU1AOCV_G920FTEF1AO.zip but the download fails before it can download onto my computer for use in odin, how do i make the download work?
i have a solution my friend . just extract your firmware with win rar and copy recovery.img to your desktop
there is a tool for making .tar file from .img called tar-Tool .
with tar tool you can make .tar from .img files
convert recovery.img to recovery.tar with this tool
flash it in pda (AP) in odin . now you can go to recovery mode
then wipe data/factory reset and wipe cache
rebooot
have a lot of fun with your phone !
Faspaiso said:
Hi
I downloaded the UK (live in Denmark) H3G version (same firmware number as my old one), added it in Odin (newest version) and flashed.
Just before finishing up, it failed. Waited 10-20 minutes and nothing happened (cause it told me to not turn off the device or unplug).
But well nothing happened, so I unplugged and restarted phone.
Now it's at a blue screen saying: "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
I then tried that, but it says my device is unsupported.
Do anyone have any idea what to do?
Thanks in advance
EDIT THE ERROR:
Click to expand...
Click to collapse
I know that you already fixed your issue, but this is just for those who may run into your same issue again in the future.
I just had this issue, and spent hours trying to figure out what to do. I was reading the app (Smart Switch), and one of the steps it gives you is that you can download Smart Switch to another computer, write down the recovery code that it gives you when you get that error, plug that recovery code in the app on the other computer, and then try the download again. Worked like a charm for me. Even though, I didn't read the app at first, and it took me 3 hours to finally figure it out (duh). So far, my phone is up and running like normal. Maybe that will help someone for next time.
Device ID - IMEI - S/N -MAC; in Google Playstore.
Aircondition said:
Can you boot into download mode? press power on, volume down and home button. Then you download Samsung Kies 3 and go to "firmware upgrade and initialization", type model name "SM-G920F", then write your serial number which you can find on a sticker on back of your phone. If you can't boot into download mode its impossible to recover your phone.
Click to expand...
Click to collapse
The freeware ap in the heading of this post works well.
Device ID - IMEI - S/N -MAC