Hello, I have attempted to root my galaxy s3 through Odin and although Odin said that the flashing passed, my device keeps sending me an error message that SuperSU has stopped. Also, the device randomly shuts off and then attempts to power on again, and fails 8/10 times. I can't even boot the device into download mode or recovery mode when it shuts down on its own. It successfully powers on occasionally and I can use the software for a short time, so I know its not bricked. Any way I can fix it?The device model is SGH-T999 (T-Mobile) and it is running Android 4.3 JellyBean (Im going to flash CM12.1 once I get it successfully rooted)
Best advice is to use one of the moments that it works to flash a stock rom via odin and start again. Make sure you are using the correct cfautoroot for your device. If no cfautoroot exists and you are using an app like kingroot etc then make sure your firewall or any other software isnt interfering, ie kies.
I think something didnt flash right..
I wish I stole my HTC M9.
Related
I installed KIES>update KIES>put phone in download mode>plugged in the phone>let KIES findit>in KIES choose emergency Firmware (?) Kies downloaded and installed, Phone boots in new Android 4.1.2.
No root off course but so far everything works.
Original thead
http://forum.xda-developers.com/showthread.php?t=2162043
Wel, I have the same problem.
Samsung SIII International version. After installing a new rom (believe it was "jellybam-v6.1.0_i9300-STABLE.zip") but I am not sure, the phone boots only to the original logo and then the screen goes black. Nothing more.
I can get into recovery mode and download mode so I tried several recovery versions (CWM, TEAMWIN, latest ClockworModRecovery v 6.0.2.8.) and several ROM.
No mater what I install, I get the same results. Boot phone and it hangs after the standard Samsung logo.
I was able to find out "/sdcard" could not be mounted. All the recovery programs I used with the option "mount unmount" reporting the same "/sdcard could not be mount" error.
Formatting /sdcard all so won't work.
I am thinking installing a new kernel but I have some difficulties in finding witch one will work with my phone?
Any suggestions or help is really appreciated b/c I have no idea what to do next.
Samsung I9300
Win 7
Latest USB drivers from Samsung installed
No Kies installed.
Odin3_v3.07 installed.
Using Odin I flashed:
CF-Root-SGS3-v6.4.tar
recovery-cwmtouch-6.0.2.8-GTI9300.tar
recovery-stock-dlj4-GTI9300.tar
recovery-stock-blg9-GTI9300.tar
And a few more.
Due to being unable to acces the phone installing a zip file is not possible. Using "installing a rom from zip, or sdcard" from recovery is not possible.
I tried installing a file using sideload but was not succesfull. I can get the phone in receiving a file from sideload but was unable to send a file from the PC.
Thanx in advance
Thanks to all reading and thinking about a solution :good:
I had a hard time finding relative posts/reply's etc mentioning a SIII stuck after the standard Samsung etc. message and the screen goes black.
Is this "glitch" I had happened before?
Using KIES to fix the problem? Never crossed my mind. Why? I rooted the phone, flashed ROM etc. Flash counter at least at 12 so why should an official program from Samsung is any help?
Software Updates won't work on the phone: You have a modified phone. no updates available is the message I get trying updating through standard channels.
I guess KIES and Samsung support really developed in an actual usable program. Coming from a SGSI, KIES was not a program I could use. Most of the time it didn't even see my SI.:good:
Well, everything seems to be working. I won't be rooting my phone for the moment, but TB has all my backups so not rooting at all is no option.
I am fairly certain that my phone can't be recovered, but I want to be sure so I'm asking for a bit of help here.
Phone is a Samsung S2X SGH-T989D, on Koodo (a child of Telus). It was running Android 4.1.2. Unfortunately I can't get into the phone for more details.
I tried to flash a custom recovery using Odin v1.85. It was a CWM recovery md5 file, but I don't have the version number (it wasn't listed in the guide I was using - http://www.theandroidsoul.com/easil...gh-t989-installs-busybox-superuser-app-52203/)
The process seemed to complete normally, but when I restarted the phone I ended up with a "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Loading Kies (Odin not running) it detect when the phone is connected and tries to read the details from the phone, but after several minutes it complains of a connection error and tells me to reboot the device. This is all I can get Kies to do.
Odin detects the phone normally. I try to restore the stock Telus/Koodo firmware (T989DTLUMC4_T989OYBMC4_T989DTLUMC4_HOME.tar.md5) using Odin v3 or Odin v1.85 and Odin goes through all the steps successfully. After all is done I restart the phone and get the same error message.
"adb.exe devices" at a Windows 7 command prompt does not list any devices.
So this is where I am... I have a physically mint condition Samsung S2X SGH-T989D phone that I cannot get to boot past this error screen.
Is there anything else I can try?
FIXED!
Yay!
I solved my problem... Using Odin3 v1.85 I tried to flash the phone one more time. The only difference is that I left the Auto Reboot checkbox selected. The process went through like every other time except at the end the phone restarted. IT CAME UP LIKE NOTHING WAS WRONG!
So, I didn't lose any data and my phone is working fine now.
Makes me VERY happy. There are TOO MANY PHONES to choose from these days. My head was spinning trying to decide on a replacement phone.
Hope this helps someone in the future!
My phone kept saying there was an update available, but it would always stop at 28%. I have rooted my phone before, so I tried to use Odin to update to Kit Kat from Jelly Bean. Big mistake. Now my phone won't boot. It turns black at the Samsung screen and still plays the AT&T sound. I tried using Odin to load the original firmware but Odin gave me an error. I tried to do recovery mode, but it said something about not being able to mount. I can still get to the download mode so I'm hoping thats a good sign. Please help if you can.
Edfox023 said:
My phone kept saying there was an update available, but it would always stop at 28%. I have rooted my phone before, so I tried to use Odin to update to Kit Kat from Jelly Bean. Big mistake. Now my phone won't boot. It turns black at the Samsung screen and still plays the AT&T sound. I tried using Odin to load the original firmware but Odin gave me an error. I tried to do recovery mode, but it said something about not being able to mount. I can still get to the download mode so I'm hoping thats a good sign. Please help if you can.
Click to expand...
Click to collapse
Which version of KK did you try? What errors are you getting in Odin? More info is very helpful.
So I have a S4 i9545 for Verizon. It was on 4.2.2 rooted and I upgraded using Fireflash with I545_OC1_Stock_DeOdexed_ROMwNK4_BL.zip. Everything seemed fine so I was using Titanium back up to remove the bloatware and then my battery died. When I charged it and booted up it got to the Verizon screen and hung there. I reset and tried several more times. I tried to use odin and flash a stock ROM SCH-I545_VZW_1_20140330160240_yni63xq6zh and I also tried one more. Odin gave a an error and failed. I then tried going into the boot loder and flash the I545_OC1_Stock_DeOdexed_ROMwNK4_BL.zip. Not sure if this was foolish or not. When I booted up I got to a black screen and there was a voice talking, maybe some sort of training, but I couldn't do anything.
If anyone can point me in the right direction on how to unbrick my S4 I would appreciate it. I know I screwed up.
Right now when I turn on the phone it says firmware upgrade encountered an issue. Please select recovery mode in kies and try again. I tried connected to my computer and opening kies but it doesn't find it.
Try disconnecting your phone, completely closing Kies, then re-launching it with your phone still disconnected. Then click Tools > Firmware Upgrade and Initialization then follow the prompts
Hello,
I've recently acquire an used Samsung Galasy S3 (I9300) and since Android 4.3 is quite old I've decided to update the phone. So I've started by rooting the device which have gone well. Then I decided to unlock the bootloader of my phone, and for this i've used the app "EZ Unlock", I clicked on the "unlock" button and then I've reboot my phone. And this is where the problems begins. When I'm booting there is a screen stuck on the device saying : "Downloading... /n Do not turn off target!" without the little white text in the upper left corner. I eventually did managed to install a recovery, the TWRP 3.1.0. But I can't do anything, when I'm trying to flash a ROM from the recovery mode I have an error 7. I also tried to flash the stock firmware via Odin, but it get stuck. Thank you for any help.
Ps : My engliski is bad, i know.
Pss : I'm not stressed by this whole situation as the phone was already quite at the end of his life.
You've probably killed it with that ez-unlock crap..
1. Do you know exactly which variant of the i9300 you have?.
2. Does the stock firmware you're trying to flash match that device/region.
The stock firmware you're trying to flash must be android 4.3. You cannot downgrade once it has been updated to 4.3, the lowest you can go is 4.3.
3. Have you rebooted the device since? What is displayed on the screen right now?.
If you have the international (btu) version I have a stock firmware to flash via odin.
Beamed in by telepathy.
The bootloader on the phone was never locked so, as @shivadow said, the app probably did something to the phone.
What error are you getting in Odin? Post the Odin log and maybe someone can help interpret the results.
You tried using Odin with different USB cables, and USB ports?
Hello and thanks for the replies,
I did finally managed to flash android 7, I just choosed the wrong image. Sorry for my noobness.
Thanks y'all !