Database Info

[Q] OTA 4.4.2 update failed, Samsung Experience no help, Please help me

I did the verizon pushed update to 4.4.2 today on my SCH I535 S3 which was totally stock with encryption. After the install finished "upgrading apps" it then did a re-boot and asked for my encrypt pin then showed the outline Andy. Then after a couple of vibrations it re-boot again and will continue this cycle until battery is removed. After sitting on the phone for several hours and conversing with Samsung and Verizon they pointed me to Samsung Experience in a Best Buy and if that doesn't work I have to send it to Samsung for re-flash. They said they couldn't get their software to recognize my phone. The guy there recommended using odin to download a stock rom.
I have downloaded odin 3.07 and have downloaded a 4.3 stock rom. I set up odin with auto reboot and F. reset time checked and nothing else. I select the .tar.md5 in the bootloader and here is my odin output:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I535VRUCNC1_I535VZWCNC1_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> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
My phone says:
ODIN MODE
PRODUCT NAME: SCH-I535
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECURE BOOT: ENABLE
BOOTLOADER AP SWREV: 2
SW REV CHECK FAIL : Found 2 > Binary 1
Please tell me how to recover my phone. I am new to this so give me detail please.

I believe since u pushed the 4.4.2 ne1 update u need to Odin the 4.4.2 ne1 tar file, not the 4.3 file

Thanks so much! I tried the 4.4.2 tar file and... it worked. I thought that since the 4.4.2 update is what failed I'd have to go back to the 4.3 but that was clearly flawed thinking on my part. I can't believe that it worked and best of all everything is still there! I still have all my apps and data, as if nothing at all happened.
Thanks so much for your suggestion!

4theluvof2 said:
Thanks so much! I tried the 4.4.2 tar file and... it worked. I thought that since the 4.4.2 update is what failed I'd have to go back to the 4.3 but that was clearly flawed thinking on my part. I can't believe that it worked and best of all everything is still there! I still have all my apps and data, as if nothing at all happened.
Thanks so much for your suggestion!
Click to expand...
Click to collapse
No problem!! Glad it worked, hit that thanks button if you don't mind!

SCH-I535
hey did you get back on 4.3 or not???? plz if u did then refer me link plzzzzzzzz

hammadsalik said:
hey did you get back on 4.3 or not???? plz if u did then refer me link plzzzzzzzz
Click to expand...
Click to collapse
No I didn't get the 4.3 working. I did get the 4.4.2 working though. I am not sure how exactly you'd revert back to an older version, Sorry.

[Q] S6 Bricked??

Hey all,
So yesterday I rooted using PingPong root, went fine, didn't trip Knox etc etc.
Installed Lucky Patcher, ended up getting the "out of space" error when trying to install apps so done a factory reset.
Get up to the point when setting the phone up and it just hung at "Just a sec...", no matter what I done, nothing changed. So I downloaded official Samsung firmware from sammobile and that's where I'm stuck now. Odin has been sitting at "NAND write start!!" for about ten minutes, nothing is happening.
Any advice at all? Pulling my hair out, the phone is only a week old.
Odin log;
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU1AOCY_G920FEVR1AOC1_G920FXXU1AOCW_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!!

Got the same problem 2 daya earlier. Just downloaded smart switch from samsung and restored my phone using emergency bla bla

AskinSavascisi said:
Got the same problem 2 daya earlier. Just downloaded smart switch from samsung and restored my phone using emergency bla bla
Click to expand...
Click to collapse
I forgot to mention, did try that briefly earlier but the download got stuck on 0%, left it maybe 5 mins. Any way I can use the downloaded firmware with smart switch?
Also, phone is now stuck at the downloading screen lol, how the hell do I turn the thing off?!
EDIT: NVM, got it turned off, will try smart switch again.
EDIT 2: Smart switch is actually downloading the firmware this time, panic over! Cheers for your help.

Ur welcome

Ive just found the reason why...
i forgot to turn off reactivation lock... when i disabled it, flashing was succesfull afterwards

Any Possible Solution for my GT-P3100 "firmware upgrade encountered an issue"?

Any Possible Solution for my GT-P3100 "firmware upgrade encountered an issue"?
My P3100 gave up on me about a month ago. It was just stuck with "Samsung galaxy tab 2" on the screen. I tried rebooting many times with no success. I read so many threads and tried many alternatives using Odin but my tablet is still not responsive. Currently, it will just have the "firmware upgrade encountered an issue" message until the battery runs out. Pressing buttons won't get to download mode.
I was so disappointed for not finding any solution that I gave up searching for 2 weeks. Now I am giving it one last shot with proper guides before I throw it to the trash.
If anyone can spare me some time, this is roughly what I had been doing:
- Odin3 (versions 07, 09, 1.85, 10.6, 10.7)
- Firmwares from Sammobile (India, China versions)
- universal roots for galaxy tab2
- CWM_ROOT_P3100.tar.md5
- CF-Auto-Root-espressorf-espressorfxx-gtp3100
- I tried through Kies but it won't recognize the device, and "firmware upgrade and initialization" returns "GT-P3100" does not support initialization"
- Remove Kies, block antivirus, switch usb cables and usb ports!
All of this was done desperately, randomly, and with lot of frustration.
Now I am hoping that someone can guide me for one last chance. And I am willing to try anything regardless of the outcome.
Thanks in Advance!
Sibson

Will I ever get any attention? I am still struggling alone in the darkness, stumbling from here to there, but I still believe there gotta be someone out there who will have a bit of care for my concerns. I randomly got that far with my p3100:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P3100_JB_SBL.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> Sbl.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
But even though it renders a success, the screen still shows the "firmware upgrade encountered an issue..." message. So I tried again with another tar file and got the same thing:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-espressorf-espressorfxx-gtp3100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
"Firmware upgrade encountered an issue..." message still comes back.
Can you tell me anything about this? Please? Really begging now? :crying: ?

Don't run KIES or any KIES service in background while using Odin.

Android-Andi said:
Don't run KIES or any KIES service in background while using Odin.
Click to expand...
Click to collapse
Thanks for the reply. I have killed all Kies processes in the background but there is no change.

Uninstall KIES and reboot. Make sure keeping the drivers.
Start odin as administrator.
Connect your tab being on the issue screen ("Black Screen of death" - in case you like to search some more). On this screen, dlmode is running in background automatically.
Now make sure using the right rom for your device and use odin to flash it.
Good luck!

Android-Andi said:
Uninstall KIES and reboot. Make sure keeping the drivers.
Start odin as administrator.
Connect your tab being on the issue screen ("Black Screen of death" - in case you like to search some more). On this screen, dlmode is running in background automatically.
Now make sure using the right rom for your device and use odin to flash it.
Good luck!
Click to expand...
Click to collapse
I have followed the procedure but I still get no change:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P3100DDCNA3_P3100ODDCNB1_P3100DDCLK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> MLO
<ID:0/005> param.lfs
<ID:0/005> Sbl.bin
<ID:0/005> modem.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
The tablet turns off after <ID:0/005> RES OK. I wait but it does not reboot. When I press the power button, the same "Firmware upgrade encountered an issue" shows up. I tried with 3 other rooms but ends the same.
I want to point out that my P3100 is the international version. Is there any specific recommendations?

Bad emmc? Could be the reason for bootloop too...

Android-Andi said:
Bad emmc? Could be the reason for bootloop too...
Click to expand...
Click to collapse
Thanks for that point. I was hoping to find a way to troubleshoot the emmc but couldn't find any. And if the emmc is at fault I guess there is nothing I can do.
The only update is that when I start Odin flash, the tab screen shows a bue progress bar but doesn't go all the way even though Odin says " PASS". I have attached a pic, in case any other possibility comes in mind.
https://www.dropbox.com/sh/oyq71eb1rqcbak4/AAArGKrWaWh5l7_4zILRIHCRa?dl=0
Thanks for your time. I will just keep surfing for possibilities and will update you if I get any solution.

You could try flashing an older stock rom, maybe 4.1 or 4.0.3

Hi Android-Andi,
I haven't gotten any solution but I got few changes. Thought I should share them in case it can bring some leads.
After all the failures I tried things randomly and I decided to flash the PIT. I used 3 pits from different sources but all failed with "there is no PIT partition".
Then I decided to use files from other models to flash. I downloaded a PIT file for Tab3 7.0 3G.
This also failed, but strangely the device was able to boot to "Samsung Galaxy Tab2 7.0" and nothing else (Pic. 1). I tried the buttons and was able to get real download mode for the first time (Pic. 2 &3).
Link to the pictures: https://www.dropbox.com/sh/oyq71eb1rqcbak4/AAArGKrWaWh5l7_4zILRIHCRa?dl=0
Even though I already flashed many times with odin "PASS", I noticed that the download mode screen says this:
PRODUCT NAME: GT-P3100
CUSTOM BINARY: NO
CURRENT BINARY: SAMSUNG_OFFICIAL
I tried to flash again with "PASS" but still the same.
So I guess that the old system is still inside with no change, and probably blocking the flashing procedure.
Now, my question is whether there is an option in odin to force and wipe everything before I flash.

sibson said:
I tried to flash again with "PASS" but still the same.
So I guess that the old system is still inside with no change, and probably blocking the flashing procedure.
Now, my question is whether there is an option in odin to force and wipe everything before I flash.
Click to expand...
Click to collapse
This (and your other symptoms) is consistent with a bricked emmc.
However, if that is not the case, you could try flashing it from linux using heimdall. I believe that has a wipe option.

I think you can go to recovery mode and do a factory reset and wipe cache. If nt there are ways in which you can flash a custom rom through odin and try going to stock firmware using odin now.

Can't restore note 5 to stock

I am trying to restore my phone to stock because only stock modified rom works with VR, but doesn't play nice with android wear.
So back to stock I go, however when I put it in download mode load up AP with the file, and hit start it says "FAIL!" I have team win installed and that is how I get to download mode. I only had Auto Reboot and F. Reset time selected as well.
Can anyone advise me on what I may be doing wrong?
Here is the log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<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> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!

Download the stock firmware again the one you're using might be corrupt, also make sure drivers are installed

I have the drivers installed, also tried 2 firmwares, trying one more now.
Was following this guide:
http://www.droidviews.com/restore-t-mobile-galaxy-note-5-sm-n920t-to-stock-5-1-1-lollipop-firmware/

no firmware seems to be working. I also tried a new cable and a few ports. No change.

tried a different odin, got a bit further but ran into the get PIT for mapping...
Seriously, whoever can get me back to stock, i'll send a paypal donation to say thanks.

Are you using 3.10.7?

I experienced the same problem. I was rooted, running whatever custom ROM my heart desired, but unable to flash to stock....until I tried one too many times and had a soft brick. After some research I found I needed a PAC file. You can get it here: http://dl.samfirm.net/page/2. There's not too much to say. Each segment is loaded seperately and take your time. If this works for you I'm happy for you and want nothing more than to help a fellow traveler.

Drachnem said:
tried a different odin, got a bit further but ran into the get PIT for mapping...
Seriously, whoever can get me back to stock, i'll send a paypal donation to say thanks.
Click to expand...
Click to collapse
How are you entering download mode?
Sent from my SM-N920T using Tapatalk

I've done it by using teamwin, also by holding pwr + home + volume down

guaneet said:
Are you using 3.10.7?
Click to expand...
Click to collapse
tried two...3.10.6, and 3.10.7

audscott said:
I experienced the same problem. I was rooted, running whatever custom ROM my heart desired, but unable to flash to stock....until I tried one too many times and had a soft brick. After some research I found I needed a PAC file. You can get it here: http://dl.samfirm.net/page/2. There's not too much to say. Each segment is loaded seperately and take your time. If this works for you I'm happy for you and want nothing more than to help a fellow traveler.
Click to expand...
Click to collapse
You have to pay 10.00 to download the files

Drachnem said:
You have to pay 10.00 to download the files
Click to expand...
Click to collapse
Last time I checked you donated if you wanted, not forced to

Drachnem said:
Last time I checked you donated if you wanted, not forced to
Click to expand...
Click to collapse
Donated to try this fix, hope it works...

Drachnem said:
You have to pay 10.00 to download the files
Click to expand...
Click to collapse
As I recollect the fee is for the latest PAC, the others are free.

So it got further with the files and the pit file, but it didn't seem to fully work and I want to understand what may be wrong. It said failed in the first box but continued then the next box said pass.
The phone is now booted in setup mode but I wanted to understand what i may run into with this error or if I am fine...
Here is the log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_TMB_N920TUVS2COKC_N920TTMB2COKC_CL5966591_QB7480468_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:1/004> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:1/004> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:1/004> File analysis..
<ID:1/004> SetupConnection..
<ID:0/005> SetupConnection..
<ID:1/004> Initialzation..
<ID:1/004> Set PIT file..
<ID:1/004> DO NOT TURN OFF TARGET!!
<ID:1/004> Get PIT for mapping..
<ID:1/004> Firmware update start..
<ID:1/004> SingleDownload.
<ID:1/004> sboot.bin
<ID:1/004> NAND Write Start!!
<ID:1/004> param.bin
<ID:1/004> cm.bin
<ID:1/004> boot.img
<ID:1/004> recovery.img
<ID:1/004> system.img
<ID:0/005> Can't open the serial(COM) port.
<ID:1/004> modem.bin
<ID:1/004> cache.img
<ID:1/004> RQT_CLOSE !!
<ID:1/004> RES OK !!
<ID:1/004> Removed!!
<ID:1/004> Remain Port .... 1
<OSM> All threads completed. (succeed 1 / failed 1)

audscott said:
I experienced the same problem. I was rooted, running whatever custom ROM my heart desired, but unable to flash to stock....until I tried one too many times and had a soft brick. After some research I found I needed a PAC file. You can get it here: http://dl.samfirm.net/page/2. There's not too much to say. Each segment is loaded seperately and take your time. If this works for you I'm happy for you and want nothing more than to help a fellow traveler.
Click to expand...
Click to collapse
These files did end up working out, ran pit first then the other file. Gave me an error but seems to be working fine for now.
Thanks again.

Drachnem said:
These files did end up working out, ran pit first then the other file. Gave me an error but seems to be working fine for now.
Thanks again.
Click to expand...
Click to collapse
I don't often have an answer, but after being the benefactor of the knowledge and kindness of others through the years, I'm glad to help when I can.

Drachnem said:
I've done it by using teamwin, also by holding pwr + home + volume down
Click to expand...
Click to collapse
That's the problem you are using twrp enter download mode by volume up+pwr+home
Sent from my SM-N920T using Tapatalk

Drachnem said:
These files did end up working out, ran pit first then the other file. Gave me an error but seems to be working fine for now.
Thanks again.
Click to expand...
Click to collapse
Are you able to post the files here (if that doesn't violate an XDA rule)? Trying to get the old ones and they seems to be gone and really don't want to have to pay, but I guess I will if I have to.

Hey Guys,
Having an issue getting one of my Galaxy Note 5 (SM-N920T) back to stock. I am able to flash stock firmware in Odin 3.10.7 but the phone is bricked. When I flash any stock firmware the phone reboots and is stuck at the Note 5 Splash Screen. If i reboot into recovery and try to do the factory wipe it tells me it can't find "E:" and fails. Only way I can get the phone to boot is if I flash a rooted kernel. Then I noticed it says the Baseband is unknown in settings. I was going to try flashing through ADB but it tells me ADB is disabled, same with flashing from external storage. I cant even get it to reboot into bootloader. I am starting to think the phone needs IMEI repair..

Samsung Galaxy s6 G920I (Aus)

Hey guys; New to the forums; Read a few guides nothing has really helped so far but I could just have missed something;
So what happened is;
I have succesfully taken all the bloatware off my s6 Edge; I was trying to do the same for the misses phone (Galaxy s6) Yes i made sure to get the right firmware
I downloaded from sammobile.com the G920I XSA so i could get rid of her telstra bloatware. However halfway threw the installation (Odin) it said failed and the phone was stuck in download mode for ages; I decided to just try a reset (after about 45 - 1hr) then it started booting up with a ! saying an error has occurred while updating the device software Use the Emergency Recovery function in the Smart Switch PC software;
Which I have tried doing; However it keeps getting to about 1 or 2% of the installation (yes it has finished the download read something on here about people getting stuck at 51% download) Then it asks me for a recovery code from a previous computer; I bought this phone used off someone with all the stock bloatware from telstra so I dont have the recovery code; How can I get around this ? I dont have their phone number either as it was on my old sim which didnt fit into this phone and I have already given my other phone away...
As of this min I am downloading the telstra version of the firmware again, Will this fix it ? and then will I be able to put the XSA firmware on ?
Thanks for any help
Appreciate it
EDIT...
This is what I get in odin
Code:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<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> cm.bin
<ID:0/004> boot.img
<ID:0/004> __XmitData_Write
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

whipz said:
Hey guys; New to the forums; Read a few guides nothing has really helped so far but I could just have missed something;
So what happened is;
I have succesfully taken all the bloatware off my s6 Edge; I was trying to do the same for the misses phone (Galaxy s6) Yes i made sure to get the right firmware
I downloaded from sammobile.com the G920I XSA so i could get rid of her telstra bloatware. However halfway threw the installation (Odin) it said failed and the phone was stuck in download mode for ages; I decided to just try a reset (after about 45 - 1hr) then it started booting up with a ! saying an error has occurred while updating the device software Use the Emergency Recovery function in the Smart Switch PC software;
Which I have tried doing; However it keeps getting to about 1 or 2% of the installation (yes it has finished the download read something on here about people getting stuck at 51% download) Then it asks me for a recovery code from a previous computer; I bought this phone used off someone with all the stock bloatware from telstra so I dont have the recovery code; How can I get around this ? I dont have their phone number either as it was on my old sim which didnt fit into this phone and I have already given my other phone away...
As of this min I am downloading the telstra version of the firmware again, Will this fix it ? and then will I be able to put the XSA firmware on ?
Thanks for any help
Appreciate it
EDIT...
This is what I get in odin
Code:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<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> cm.bin
<ID:0/004> boot.img
<ID:0/004> __XmitData_Write
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
My bad, I didnt know you needed to restart computer after each Odin; Reset the computer and the phone and everything is working smoothly now; Just got to find the right stockfirmware without all that bloat crap