Database Users

[Q] AT&T Galaxy S5 Update G900AUCU2ANG3 - Issues after update

I have tried searching and do not see anyone with a similar issue. I was previously rooted with TowelRoot, but somehow my phone not only allowed the G900AUCU2ANG3 update today to download, but also allowed it to install. I know I should have removed TR before continuing, but stupid stuff like that happens when you see the update waiting when you first wake up and don't have contacts in or glasses on...
I can fully restore my phone to normal use, other than wifi. For whatever reason, the failed update shows to have changed the baseband, but I have no ability to connect to a wifi network, and despite about 15 factory resets since this morning, my device status still shows "Custom." Here is exactly what I see when I go into Download Mode (or as close as I can replicate it):
ODIN MODE
PRODUCT NAME: SM-G900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A2, P1
UDC START
At this point, I can't find anyone with an NG3 stock firmware to use with Odin, and Odin keeps failing because the old firmwares won't pass the authorization stage. I attached the Odin screenshot to this post in case someone has other ideas. I can actually use my phone (not bricked), but wifi will not connect even though it can see various open and secure networks. I get an error stating "Failed to Obtain IP" when trying to connect to networks with "Very Strong" signal strength (I can see the AP from my desk).
Thus, I really need to be able to do 1 of 2 things:
1) Restore it to stock myself so I can have wifi, or
2) Be able to get it to show "System Status: Official" so that the local AT&T Device Service Center I drive by twice a week taking my kid to hockey practice will plug it in and update it and restore it. They managed to save my wife's Note 3 from a fairly bad soft brick / boot loop issue, but I also know that the "Custom" thing will pretty much guarantee they don't work on it.
Thanks in advance.

..

fffft said:
Writing a full stock firmware image, followed by a factory data reset will remove the custom status. So that would satisfy No. 2.
As to your first wish, I find it hard to believe that you couldn't find an ATT firmware image anywhere. There are dozens of firmware sites and I can only assume that you just did a short or cursory search. If you spend a few minutes with Google you can surely locate any ATT firmware version that has been release longer than one day.
Either way, use Odin to write a firmware image as the fastest way to resolve the situation. If you have difficulties, try this guide
If the problem persists, then you need to provide us with more details. Notably, the verbatim Odin error log, along with the exact file name you are trying to write and a detailed, step by step description of how you are using Odin.
.
.
Click to expand...
Click to collapse
I definitely have searched high and low for a stock version (both before the original post and just now) that will work with the failed update G900AUCU2ANG3. No one has a stock firmware I can find, and I cannot find any method by which to downgrade to an older version that I can find, such as G900AUCU1ANCE.
Here is what my phone says in Settings --> About device:
Baseband Version:
G900AUCU2ANG3
Build Version:
KOT49H.G900AUCU2AND3
File name I'm trying (but know won't work...not the newest baseband): G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar
Odin Error Log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

..

fffft said:
The additional information definitely helps. But it's still a drop in the bucket. You didn't give us a detailed, step by step description of how you are using Odin e.g. what version of Odin you are using , which line you entered the firmware file line on (e.g. AP, PDA, etc) and so forth. And most importantly, did you try the procedure that I linked to in my last post?
We can't see your phone and these details are important as any one of them could cause failure. So we need to check off each item that you are doing.
Nominally the Odin error you posted says that your bootloader refused the firmware version you tried to write. More likely it is a timing error from a marginal USB cable or port. Odin is well known as tempermental with respect to USB timing. Try a different USB cable (yes, really. and yes, it is important. don't skip this step) and different USB port.
Most critically, ensure that you are entering download mode by removing the phone battery, then replacing it and using the volume down + home +power key sequence. And also important, if the first Odin write fails, do not close the Odin window. Instead remove the phone battery again, go into download mode again and then hit write again in the open Odin window. Inevitably, the second attempt will then succeed.
Try the very good procedure that is listed here <---- click on the link
Odin can be frustrating, but with a modicum of patience and attention to detail you will succeed. Good luck
.
Click to expand...
Click to collapse
I ended up going to the local AT&T Device Support Center (luckily it's about 2 miles from the ice rink at which my son practices) and they flashed it back to stock with no problems. She said I was one of 4 people that day who had issues with that particular update, and since my Knox Warranty showed 0x0, she thankfully ignored the "Custom" on device status. All is well and I have a clean backup in Kies if needed in the future and TowelRoot back on the device to kill some bloat. Thanks!

Can I get a flashable G900AUCU2ANG3? I am selling the phone and they want it stock and updated. I can't flash it back to stock. I didn't update it but it gives me the same Odin error as though I was trying to downgrade. Used to be able to downgrade it and do whatever I wanted when I was tinkering with getting SuperSU to stick after update. I've made no major changes. Did something come down from Samsung that locks Odin? I froze Knox and thought that might have something to do with it so I thawed it and factory reset after unrooting. No good.
Long story short I'd like an Odin flashable latest firmware to see if it will take. Sorry I don't have more info right now but the buyer has the phone right now.

[Q] Note 3 SM-900 Stuck on Splash Logo (Download Mode Works)

Hi Everyone,
Having a problem here with a SM-900 Note 3 sent back to the US here by a relative. A relative asked me to purchase it off Amazon with their credit card (prime shipping), so it comes from a trustworthy source. AFAIK the phone was unrooted (Knox counter 0) and apps were installed through the play store. The phone is stuck at the initial "Samsung Galaxy Note 3 SM-900" screen. The logo is not steady, instead it keeps flashing every 3 seconds. Recovery mode does not work, or at least the phone keeps flashing the logo. Download Mode, however, works and the phone stays turned on steady. Kies keeps saying connecting and Jodin3 keeps saying my phone isn't connected. I have tried all 4 ports and 3 separate usb cables. I don't have access to a Windows machine only an iMac. I'm not sure what is wrong. I'm going to try downloading odin to my mac to see if it will work. If all else fails, I plan on contacting Samsung to see if they will fix it seeing as it was purchased only 4 months ago. Any help is greatly appreciated.

Hiya Buddy said:
Hi Everyone,
Having a problem here with a SM-900 Note 3 sent back to the US here by a relative. A relative asked me to purchase it off Amazon with their credit card (prime shipping), so it comes from a trustworthy source. AFAIK the phone was unrooted (Knox counter 0) and apps were installed through the play store. The phone is stuck at the initial "Samsung Galaxy Note 3 SM-900" screen. The logo is not steady, instead it keeps flashing every 3 seconds. Recovery mode does not work, or at least the phone keeps flashing the logo. Download Mode, however, works and the phone stays turned on steady. Kies keeps saying connecting and Jodin3 keeps saying my phone isn't connected. I have tried all 4 ports and 3 separate usb cables. I don't have access to a Windows machine only an iMac. I'm not sure what is wrong. I'm going to try downloading odin to my mac to see if it will work. If all else fails, I plan on contacting Samsung to see if they will fix it seeing as it was purchased only 4 months ago. Any help is greatly appreciated.
Click to expand...
Click to collapse
If you were using a Windows PC, install Kies 3 to get a correct driver to be installed, then download a stock firmware for your device and flash via Odin. That could help to fix the problem.
I'm not familiar with iMac so I don't know what software can be a replacement for the Odin.
You can try Heimdall.

vndnguyen said:
If you were using a Windows PC, install Kies 3 to get a correct driver to be installed, then download a stock firmware for your device and flash via Odin. That could help to fix the problem.
I'm not familiar with iMac so I don't know what software can be a replacement for the Odin.
You can try Heimdall.
Click to expand...
Click to collapse
I managed to go over a friend's house and use his windows machine. I got the correct file and used Odin and it said "PASS". Unfortunately, the Note 3 is still having the same problem with the splash logo flashing every three seconds. Not sure whats wrong. Could it be hardware related? The battery contacts on the phone are fine. I don't think there is anything wrong with the battery itself because download mode works just fine. It seems to start the phone up its having trouble getting past the initial splash screen. Safe mode is not working either. Looks like I might have to put in a call to Samsung for warranty repair.

Hiya Buddy said:
Hi Everyone,
Having a problem here with a SM-900 Note 3 sent back to the US here by a relative. A relative asked me to purchase it off Amazon with their credit card (prime shipping), so it comes from a trustworthy source. AFAIK the phone was unrooted (Knox counter 0) and apps were installed through the play store. The phone is stuck at the initial "Samsung Galaxy Note 3 SM-900" screen. The logo is not steady, instead it keeps flashing every 3 seconds. Recovery mode does not work, or at least the phone keeps flashing the logo. Download Mode, however, works and the phone stays turned on steady. Kies keeps saying connecting and Jodin3 keeps saying my phone isn't connected. I have tried all 4 ports and 3 separate usb cables. I don't have access to a Windows machine only an iMac. I'm not sure what is wrong. I'm going to try downloading odin to my mac to see if it will work. If all else fails, I plan on contacting Samsung to see if they will fix it seeing as it was purchased only 4 months ago. Any help is greatly appreciated.
Click to expand...
Click to collapse
1. You will have to download one of the latest firmware of: HERE. I supose you don't know the CSC (country CODE) of your device. We don't know what firmware had your device either. Try to flash one of the newest for avoid active KNOX to 0x1 in future if you have to come back to one older firmware. Flash the firmware of the correct country if you know it ofc.
2. ODIN don't works in Mac.... use HEIMDALL. Lil guide: HERE

Hiya Buddy said:
I managed to go over a friend's house and use his windows machine. I got the correct file and used Odin and it said "PASS". Unfortunately, the Note 3 is still having the same problem with the splash logo flashing every three seconds. Not sure whats wrong. Could it be hardware related? The battery contacts on the phone are fine. I don't think there is anything wrong with the battery itself because download mode works just fine. It seems to start the phone up its having trouble getting past the initial splash screen. Safe mode is not working either. Looks like I might have to put in a call to Samsung for warranty repair.
Click to expand...
Click to collapse
Can you show the Odin screenshot? And also the full Odin log file?

UPDATE:
Vndnguyen; Sorry for the long wait as the past couple of weeks have been hectic with a family member in the hospital. Samsung Customer Support was obviously unhelpful but someone managed to find the true country of origin of my phone. They said (Samsung CS) based on IMEI it is from Taiwan. Now that I know the proper firmware I have downloaded the corresponding country version from Sam Mobile. Currently leaving Odin running to see if that does anything to fix it. Regardless, I will still post a screen shot and the log file.
P.S. It was confirmed the battery was not the problem, a Samsung Rep at a Best Buy store pulled out a battery from a working display Note 3 and used it in mine, but still no dice.

I tried the Taiwan firmware from Sam Mobile (N900ZSUENI3_N900OZSENI3_N900XXUENG1_HOME.tar.md5) but Odin reported fail. Even after 3 attempts it still reported fail. After contacting the third party seller via Amazon, they replied that the Note 3 was meant for Latin America. I picked one of the countries (Panama: N900UBUENJ2_N900UWAENJ2_N900UBUENG1_HOME.tar.md5) and Odin reported Pass! But it still keeps flashing at the boot screen.
This is the log for the Panama Firmware:
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900UBUENJ2_N900UWAENJ2_N900UBUENG1_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> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
I'm not sure about "removed" because I left the Note 3 plugged in.
Here is the log for the Taiwan Firmware:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900ZSUENI3_N900OZSENI3_N900XXUENG1_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> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> modem.bin
<ID:0/004> param.bin
<ID:0/004> sboot.bin
<ID:0/004> cache.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Here is a screenshot of Odin. With the phone still plugged in to the computer.

[Q] Bricked Sprint Galaxy S4 (L720T)? Need help.

Hello, everyone.
I'm new to this forum and new to working with cell phones.
I have (rather - created) a problem - my former Sprint Galaxy S4 (L720T) probably bricked: the phone shows "Firmware upgrade encountered an issue, please select recovery mode..."
This happened after I tried to downgrade from OA3 firmware to MK5.
I can still get to download mode by pressing Vol-/"center button"/power and start Odin (1.82 or 3.07 or 3.09) and start flashing (thru PDA), but the process freezes and Odin stops responding.
what led to it?
I'll try to explain everything I did before.
I have two phones (galaxy s4 sprint) and for both I obtained MSL 6-digit numbers (from sprint).
I unlocked first phone (which had ...MK5 version) to use over GSM network: it was rooted, I added superSU, Titanium backup, went through *#0011# command and changed settings (found on this forum), virtual terminal (did something through it, too) and, then, "applied" SSU.apk to actually unlock the phone. It didn't go as fast and smooth, because some things did not go as described in the tutorials and instructions. The phone works.
The second phone has ...OA3 version and I did as much (and relatively in the same order) work as with the first one. EXEPT, SSU.apk did not unlock the phone in this particular version (it was designed for MK5).
So, I thought that downgrading from ...OA3 (Android 4.4.2) to ...MK5 Android 4.3) is a sound solution. and I tried, using Odin(s) and file "L720TVPUAMK5_L720TSPTAMK5_L720TVPUAMK5_HOME.tar.md5" (through PDA button in Odin.)
The odin took long time to process it and it seemed to finish the job (I really don't remember what exactly happened that time) and I either turned off the phone or unplugged usb cord, and remember seeing blue "status bar" on the phone below the logo and message below it.
I realized that I screwed up after seeing the "dreadfull" message: Firmware upgrade encountered an issue, please select recovery mode...
I turned on phone in download mode and used odin (versions 1.85, 33.07, 3.09) to try to download firmware (MK5) ( I used buttons "bootload", PDA) to no avail.
I also tried to get into recovery mode (Vol+/center button/power) - nothing happened.
Now I'm stuck - I don't know how to re-install the original firmware (MK5) on this phone (or OA3).
I was looking for a solution (and still looking), but I found no answer so far.
Thus, I turned to you, knowledgeable people, to help me and lead in (point to) the right direction.
I know almost nothing about Android programming and the smart phones. I know veeery little about Linux (for PC - as an end user), so bear this in mind when you reply.
Thank you in advance.
Meanwhile I'll keep looking for solution anyway.

http://forum.xda-developers.com/galaxy-s4-sprint is where you need to go to get your questions properly answered, as you had posted this originally in the international S4 forum.
I'll let a mod know the thread needs to be moved.

Thread moved to proper forum.

update
Mr. Clown said:
Thread moved to proper forum.
Click to expand...
Click to collapse
Update:
Before I messed with the phone, I copied all the folders from the phone to my PC. When I plugged the phone, windows window (sounds stupid) popped up and I double-clicked on "phone" and copied all available files, e.g. "Alarms", "Android", "Applications" etc. I didn't perform backup at all.
I store this phone without battery now.
Also, when I tried to flash with "L720TVPUAMK5_L720TSPTAMK5_L720TVPUAMK5_HOME.tar.md5", Odin froze, the blue status bar on the phone just appeared and froze, too.
Another update,
I tried to use Kies to use tool "emergency firmware recovery" - I\it couldn't connect with the phone.
Yesterday I tried to connect with the working phone - same thing - no connection. The usb cable is original Samsung's.

update #2
UPDATE (yes - all in caps!)
1 . I booted phone in download mode (Vol-/Home center button/power)
2. pressed Vol + (to continue)
3. plugged usb cord
4. started Odin 3.04
5. checked options "Auto Reboot" and "F. Reset time"
6. ckicked on PDA button and chose file "openrecovery-twrp-2.8.0.1-jfltespr.tar" (It was downloaded from one of youtube instructions.)
7. clicked on START
8. the process went through and passed:
+++
<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
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
<ID:0/005> Added!!
++++
10. the phone rebooted and back to "normal" (means stil Sprint), rooted but still with "invalid card" message.
11. KNOX 0x1
12. baseband version is L720TVPUOA3, Android version: 4.4.2, kernelversion: 3.4.0-3892813 [email protected] #1 Thu Jan 15 09:50:12 Kst 2015.
Now...
the SSU.apk will not work, as it was design for android version 4.3 (this app unlocks the sprint phones (used it before on another phone)).
I'll look for SAFE downgrading to 4.3 (MK5) if not, I'll look for unlocking (similar to SSU.apk) for 4.4.2 version.
And I still need to re-check all the settings (like *#0011#).
conclusion: the bricked phone is revived now.
I'd like to thank this forum anyway for keeping a lot of information (sometimes overwhelming amounts of info).

[please help] galaxy s5 firmware issue!

Hey, if anyone could help me with this, I would love it. I NEED this phone working again and every source I've found either doesn't mention my model or doesn't work.
I tried rooting my US Cellular Galaxy S5 SM-G900R4 using CF Auto Root and Odin 3.10.6. I followed all the steps and made sure I started the process in download mode, 75% battery, did it in AP, unchecked re-partition, and also had the correct root file. It was going fine until it got stuck on "CACHE". I kept waiting until it eventually said "FAIL". My S5 was still showing the blue download bar but I figured it was OK anyway. I clicked "RESET" and it did. I unplugged my phone and then tried turning it on but it came up with a yellow triangle in between a desktop logo and my phone logo and it said "Firmware Update Encountered an Error. Select Restore in Kies and Try Again". It does go into download mode but besides that nothing else. It's just stuck there.
After some research I found out you could fix the issue with Samsung Kies, so I installed it and everything looked fine and the drivers installed so I connected the phone and it just stuck on the "connecting" screen forever. I unplugged and tried Samsung Kies 3 but it immediately said "phone unsupported". On Kies I tried going into the update initialization mode and I typed the model number but it said the S/N was incorrect. On the back of this phone it shows the IMEID (H) number and the IMEID (D) and I tried both...
So the last method I had was using ODIN 3.10.6 to flash the stock ROM. My phone was not rooted when this whole thing happened but it does have USB debugging enabled and yes, the Samsung USB drivers are installed. Anyway, I downloaded the stock ROM for my model, and I started it through AP and everything but it immediately failed and said this:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please please PLEASE help me! I am at such a loss and any help would be greatly appreciated

faur.ionutz said:
try to flash another build newer by release date
Trimis de pe al meu SM-G920F folosind Tapatalk
Click to expand...
Click to collapse
What I did try was flashing the official 6.0.1 stock but it failed

try a fresh download. where did you get yours from? sammobile.com is the most trustworthy place, its slow from there, but theyre legit. You probably have a bad download, its the most frequent cause of issues like these

youdoofus said:
try a fresh download. where did you get yours from? sammobile.com is the most trustworthy place, its slow from there, but theyre legit. You probably have a bad download, its the most frequent cause of issues like these
Click to expand...
Click to collapse
If you can give me the link to a legit download for my model that would be great. I tried a couple ROMS but they don't work, and SamsMobile doesn't carry the ROM for my model btw

Try this
http://upload.teamuscellular.com/36p
Or this
http://upload.teamuscellular.com/8zz
Which I found here. http://forum.xda-developers.com/galaxy-s5/unified-development/cellular-galaxy-s5-sm-g900r4-t3024022

[Kernel is not Seandroid Enforcing] bootloop

I really messed up my phone :/
Hi, so about one month ago I decided to root my phone, but I did not know what I was doing since it was my first time and I was VERY confused. I ended up causing my phone to go into a bootloop, I'd first to even get it to work make it I'd make it go into download mode then restart from there. It'd just say in the top right corner "kernel is not seandroid enforcing" then afterwords it'd flicker the bottom buttons to just turn off completely. Any advice or help would be amazing , I won't mind spending time just to fix this so I'm all open

I recomend to flash the stock firmware on your phone.
Get the firmware file from fw.updato.com(fast but sometimes website is down)
Or
sammobile.com(slow but reliable)
Since you already sayd you tryed to root ur phone i suppose you know where to get odin3
Extract the firmware zip file y downloaded inside should be a .tar file put that in AP in odin and click start
Also i recomend a wipe but in theory it should* start working without.
Hope this helped you

Rainbow_Dash said:
I recomend to flash the stock firmware on your phone.
Get the firmware file from fw.updato.com(fast but sometimes website is down)
Or
sammobile.com(slow but reliable)
Since you already sayd you tryed to root ur phone i suppose you know where to get odin3
Extract the firmware zip file y downloaded inside should be a .tar file put that in AP in odin and click start
Also i recomend a wipe but in theory it should* start working without.
Hope this helped you
Click to expand...
Click to collapse
I've tried it before but I'll try it again, nothing really happens when I do it but mabey It'll work this time. I'll tell you whether it work or not

Nooooxa said:
I've tried it before but I'll try it again, nothing really happens when I do it but mabey It'll work this time. I'll tell you whether it work or not
Click to expand...
Click to collapse
Quick edit, my phone doesn't show up on the ID:COM area at all, I've tried other cables but it just won't work at all. I'm pretty sure it's from my phone itself and not the program

Nooooxa said:
Quick edit, my phone doesn't show up on the ID:COM area at all, I've tried other cables but it just won't work at all. I'm pretty sure it's from my phone itself and not the program
Click to expand...
Click to collapse
Oh no I forgot y need to have installed special drivers otherwise in some cases it won't show up. Get it from here în my experience first time it can take up to 1 hour for phone to be recognized. Also make sure ur phone is well enterd in download mode (volume down+home+volume up+power) a blueish screen appears and volume up again) there is no way it's bcuz of the phone. Also use the cable that came with the device and if it still doesn't work (for some reason) try in another pc (or mac)

Rainbow_Dash said:
Oh no I forgot y need to have installed special drivers otherwise in some cases it won't show up. Get it from here în my experience first time it can take up to 1 hour for phone to be recognized. Also make sure ur phone is well enterd in download mode (volume down+home+volume up+power) a blueish screen appears and volume up again) there is no way it's bcuz of the phone. Also use the cable that came with the device and if it still doesn't work (for some reason) try in another pc (or mac)
Click to expand...
Click to collapse
I got the driver installed and so far it's actually being able to connect ! but I have no luck at all, I put it in downloading mode, opened up oden then at a certain point my phone randomly went black then said "An error occurred while updating the device software. Use the Emergency recovery function in the smart switch PC software" Which I did end up doing but even while using that it will randomly shut off :/. Here's the oden log
"<ID:0/003> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)"

Nooooxa said:
I got the driver installed and so far it's actually being able to connect ! but I have no luck at all, I put it in downloading mode, opened up oden then at a certain point my phone randomly went black then said "An error occurred while updating the device software. Use the Emergency recovery function in the smart switch PC software" Which I did end up doing but even while using that it will randomly shut off :/. Here's the oden log
"<ID:0/003> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)"
Click to expand...
Click to collapse
Nevermind I found the issue! For some reason, my phone wasn't charged and my computer couldn't charge it enough. Dude, I can't thank you enough, I've been at this for a month now and never thought of going onto a forum. I was about to pay some guy $30 to fix it for me.

Nooooxa said:
I really messed up my phone :/
Hi, so about one month ago I decided to root my phone, but I did not know what I was doing since it was my first time and I was VERY confused. I ended up causing my phone to go into a bootloop, I'd first to even get it to work make it I'd make it go into download mode then restart from there. It'd just say in the top right corner "kernel is not seandroid enforcing" then afterwords it'd flicker the bottom buttons to just turn off completely. Any advice or help would be amazing , I won't mind spending time just to fix this so I'm all open
Click to expand...
Click to collapse
do you have flahed a custom rom?
or flash custom kernel? like audax kernel?