Hello,
Before the update of 4.3, everything was working perfectly. The phone was rooted prior to the update.
After the update, I can't root the phone. I tried Odin 1.85/87, 3.07 & 3.09. It always says the same error (beside the 1.85v which just stop working).
The phone works well. It connects to the computer too. Only the Odin 1.87 see the phone when it is in download mode. The other versions I had to boot the phone connect it, **** it down then go into download mode for odin to say ''added''.
Anyway... I am about to throw this phone in the garbage. Un-rooted phone are not fun. Pun intended.
Maybe you need updated drivers? Did you follow the 4.3 rooting guide?
If your phone still has warranty, rooting a stock 4.3 ROM will it.
Problem fixed!
/Thread.
Used windows XP.
No more warranty. Never used anything else than the stock simply because I just don't have the time and am quite lost with all the custom rom and their advantages.
------
EDIT: I used Odin 3.09 clicked on AP then selected the .md5 file. It passed but I got the message that it didn't work. Herm.
Related
AT&T Galaxy SIII Bricked While Trying to Flash Back to Stock... Desperate For Help
Had my AT&T Galaxy S III rooted, stock ROM. Was having some issues after rooting so I decided to go back to bone stock, completely unroot so I flashed the I747UCALEM build from these forums on Odin 3.07. Needless to say the phone was held up mid flash, and I got a "FAIL" in Odin. When I tried to reboot the phone, I got a "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" When I reboot the phone this comes up and it's almost like a permanent download mode. I tried to reflash in Odin to unbrick the phone and it fails every single time.
Am I completely screwed? If I send it back to Samsung like this they'll see the that I rooted (didnt trip the flash counter) and void my warranty. Not sure what to do here. Thanks for any advice guys.
statusnone said:
Had my AT&T Galaxy S III rooted, stock ROM. Was having some issues after rooting so I decided to go back to bone stock, completely unroot so I flashed the I747UCALEM build from these forums on Odin 3.07. Needless to say the phone was held up mid flash, and I got a "FAIL" in Odin. When I tried to reboot the phone, I got a "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" When I reboot the phone this comes up and it's almost like a permanent download mode. I tried to reflash in Odin to unbrick the phone and it fails every single time.
Am I completely screwed? If I send it back to Samsung like this they'll see the that I rooted (didnt trip the flash counter) and void my warranty. Not sure what to do here. Thanks for any advice guys.
Click to expand...
Click to collapse
Sounds like you got a bad file re-download the AT&T software again from here http://forum.xda-developers.com/showthread.php?t=1737848 make sure you have Kies disabled i do think if its running in the background odin won't flash right don't hold me to it.and as long as you can get in download mode you should be able to fix it.also check here http://forum.xda-developers.com/showthread.php?t=1727443
statusnone said:
Had my AT&T Galaxy S III rooted, stock ROM. Was having some issues after rooting so I decided to go back to bone stock, completely unroot so I flashed the I747UCALEM build from these forums on Odin 3.07. Needless to say the phone was held up mid flash, and I got a "FAIL" in Odin. When I tried to reboot the phone, I got a "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" When I reboot the phone this comes up and it's almost like a permanent download mode. I tried to reflash in Odin to unbrick the phone and it fails every single time.
Am I completely screwed? If I send it back to Samsung like this they'll see the that I rooted (didnt trip the flash counter) and void my warranty. Not sure what to do here. Thanks for any advice guys.
Click to expand...
Click to collapse
Hmm this actually happened to me first time I tried to root (stupid computer fell asleep mid flash) however I was just able to reenter download mode and flash again, curious though , what did the screen say and where In the flash process did the Odin fail, for Me luckily it was 2/3 of the way through flashing system so I didn't have much to worry about. Though I imagine if it was writing something important like the sbl or somethimg and it failed you might be in trouble . All in all I would say try flashing again a few times maybe the file you downloaded is bad.
bec48 said:
Sounds like you got a bad file re-download the AT&T software again from here http://forum.xda-developers.com/showthread.php?t=1737848 make sure you have Kies disabled i do think if its running in the background odin won't flash right don't hold me to it.and as long as you can get in download mode you should be able to fix it.also check here http://forum.xda-developers.com/showthread.php?t=1727443
Click to expand...
Click to collapse
Downloading the UCALEM build from that link now on my laptop (my PC is notorious for connection issues with this phone, I should of known) and I'll pray for the best. Thank you very much for the help, I'll post back once I'm on my way.
I can't even download either firmwares. The direct downloads stop for some random reason at around 33 MB and there's 0 seeders for the torrent versions. Any other way to get these firmwares? Samsung updates isn't being nice tonight.
statusnone said:
I can't even download either firmwares. The direct downloads stop for some random reason at around 33 MB and there's 0 seeders for the torrent versions. Any other way to get these firmwares? Samsung updates isn't being nice tonight.
Click to expand...
Click to collapse
The update is in Kies as well.
Finally got the update to download, used a different browser. Flashed the new build through Odin and it worked, unbricked the phone. Apparently it is the connection through my regular PC. Thanks for everyones help!
Hi, I started out with a stock tmobile s3 and tried to root it for the first time today, I followed this video
http://www.youtube.com/watch?v=mndQZqom3Ac
which asked me to use this cf-root 6.4
http://forum.xda-developers.com/showthread.php?t=1695238
when I hit start on that .tar file under odin, it failed stating "complete (write)operation failed)
since then, my device would boot with error "firmware upgrade encountered an issue" nothing else would happen.
I tried to go into recovery mode again and this time when I tried to retry the odin tar install, it would give me a new fail of cannot open com3
When I tried to use kies, it would just forever try to connect and never connect. so I couldnt do anything there.
What can I do? I would preferably try to retain all my saved data.
I also suspect my usb port might be faulty, sometimes need to press it in firmly to make the usb mass storage to work properly.
Thanks in advance
What is your Current android version ?
Perseus71 said:
What is your Current android version ?
Click to expand...
Click to collapse
i really didnt note which version i have... noob mistake i kmow. i think it is 4.2...is there any way i can check?
Ok, I totally messed up when I first attempted this. The .tar I used was for an international s3 and I have a tmobile us version!. the OP of the thread says it may even brick my phone if I attempt this on a non international version.
competely my fault, but what should I do to fix this and save my phone?
I cannot connect to kies, reinstalled the drivers and it still wont connect. just gets stuck in "connecting"
The odin now doesnt load a tar because it says "cannot open com3 "
EDIT:
fixed it, odin was not working due to kies running in the background and I finally was able to flash the correct chainfire for my phone
Glad its sorted out. I assume no issues now ?
Hello guys.
I got a SM-T310_NA. It was not rooted and everything original.
I tried to root it a few times following this droidviews dot com/root-galaxy-tab-3-8-0-sm-t310-on-kitkat guide.
Odin always said that everything worked and my tablet restarted, I didn't know what the problem was. I had drivers installed and everything.
So then I tried to flash a firmware over Odin, but then something didn't work out and my tablet didn't get the full flash.
Now I get the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". I tried to recover it with Kies, it didn't work.
I downloaded the original firmware from sammobile and tried to flash it, it didn't work either. I think I need a 3-part-flash with Odin, but I don't know where to get the datas.
Can you guys help me out?
So I'm an idiot. I was attempting to upgrade from 2.3.6 to 4.0.4 on my (rooted) SGH-T989 Samsung Galaxy S2 Hercules, flashing in Odin 3.07, but placed the .tar in the CSC place instead. Now, I can't even access recovery, my phone instantly boots up into Firmware Upgrade Encountered an issue screen. By an off chance, my phone connected and was detected by Odin once. However, in my attempt to revert to a stock rom, it failed. Now Odin AND KIES won't recognize my phone. I have attempted to re-download Odin/drivers and restart phone/computer. I have tried different drivers. Any help would be much appreciated.
Hi,
If your device is showing up in you PC's device manager as QSUSB_DLOAD or similar... You are bricked, and likely need a repair center to fix it.
I will have your thread moved to your device section for other opinions.
Good luck!
Hi, I have an N7105 running android 4.2.2 latest version in my country. Recently, my phone got semi bricked, not sure why, and wouldn't get past the logo. I flashed the stock rom (N7105XXUFNJ1_N7105OLBFNJ1_MM1) for the first time via ODIN 3.07 and ODIN failed. However, I still manage to get into download mode. So i decided to update the samusng mobile phone drivers via kies, used a different USB port and charged the battery for awhile before trying again. I flashed the same firmware with the same ODIN version (3.07) and unfortunately, it failed again. As in it didn't even managed to inject the system successfully. Now, I have a bricked device that neither will boot into download/recovery mode. May I know what's the cause of the issue? Is there any way to revive it? Thanks so much.