Develop Bugs

Have I bricked my phone :( - Experts plz help!

Guys,
!!!!! N00B Alert - I am not an expert in what I am doing. Just following instructions from experts like you. I will try to be as technically articulate as possible !!!
I had recently (about a month ago) rooted my phone to install CM 10.2. I love CM.
In an attempt to unlock my phone I wanted to get back to stock ROM. So I googled and bumped into a way to do it from Kies (not sure if it was a good idea). I followed the instructions and boom the firmware initialization failed half way through. Now when I turn my phone on I get this error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". So I tried again multiple times but it won't work.
Then I thought may be there is another way and googled and found this thread - http://forum.xda-developers.com/showthread.php?t=2186967
Followed the instructions to the word, but I see the dreaded FAIL message in ODIN.
Below is the log. (I tried twice in one stretch).
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Another thing is I am not able to get to recovery mode. When I try I can only get to the Firmware error screen I mentioned above.
Any help to get out of this mess would be great!

did you make sure you had the LK3 bootloader before trying to flash stock? if so I also had Odin fail while flashing this firmware. only one that worked for me was root66 firmware. i never booted all the way in but i read that you have to uncheck "auto restart" before flashing, once it is done pull battery and boot into recovery and factory reset. if that doesn't work you can do what I did. Odin flash cwm and install a rom from your sdcard
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

andrewjae04 said:
did you make sure you had the LK3 bootloader before trying to flash stock? if so I also had Odin fail while flashing this firmware. only one that worked for me was root66 firmware. i never booted all the way in but i read that you have to uncheck "auto restart" before flashing, once it is done pull battery and boot into recovery and factory reset. if that doesn't work you can do what I did. Odin flash cwm and install a rom from your sdcard
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your response.
I didnt know I have to have the LK3 bootloader, may be I missed in the instructions.
Anyway, how do I flash Clockworkmod from Odin? if I can do that I can get back to CM 10.2 and then try paying for unlock code.

http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att/philz_touch_6.07.9-d2att.tar.md5
this is what I used but it didn't work for me without first flashing root66 firmware. i will try to find that link and post it also.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

http://click.xda-developers.com/api...747UCDLK3.7z&jsonp=vglnk_jsonp_13911206638286
this is the link to root66 for att.
BEFORE YOU DO ANY OF THIS YOU ARE ON AT&T RIGHT?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

Make sure the bootloader that's currently on your phone is not from the 4.3 OTA update. If it is, you can't use Odin to restore a stock rom, you'll have to find a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.

andrewjae04 said:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att/philz_touch_6.07.9-d2att.tar.md5
this is what I used but it didn't work for me without first flashing root66 firmware. i will try to find that link and post it also.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank You!
andrewjae04 said:
http://click.xda-developers.com/api...747UCDLK3.7z&jsonp=vglnk_jsonp_13911206638286
this is the link to root66 for att.
BEFORE YOU DO ANY OF THIS YOU ARE ON AT&T RIGHT?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I am on AT&T.
After I read your post about flashing CWM with ODIN I researched and found a method. I tried it and it PASSED!. Then my phone restarted and boom it booted directly into CM 10.2. Not sure how, felt a bit creepy. Then I updated to latest Nightly CM 11 build and brough back all my apps and my phone has LIFE right now. Thanks for the tip! :good:

audit13 said:
Make sure the bootloader that's currently on your phone is not from the 4.3 OTA update. If it is, you can't use Odin to restore a stock rom, you'll have to find a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.
Click to expand...
Click to collapse
May be it is, I updated to 4.3 thru OTA and after a few days rooted and installed CM 10.2. How do I check?
Then this should be the reason that ODIN didnt work for me. Which genuine source I should look at for a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.

mr_legolas said:
May be it is, I updated to 4.3 thru OTA and after a few days rooted and installed CM 10.2. How do I check?
Then this should be the reason that ODIN didnt work for me. Which genuine source I should look at for a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.
Click to expand...
Click to collapse
I believe if you were originally on 4.1 then you still have that bootloader. I dont think OTA updates the bootloader so you should be able to downgrade with the root66 if that is the case.

audit13 said:
Make sure the bootloader that's currently on your phone is not from the 4.3 OTA update. If it is, you can't use Odin to restore a stock rom, you'll have to find a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.
Click to expand...
Click to collapse
when you say "find" an AT&T 4.3 rom, I wish you could give me a link. I am working with a device that was handed to me that was on 4.3 then flashed to a t999 rom. Now I cannot get it to flash ANYTHING AT&T 4.3 (and I've looked all over), neither in odin, nor in recovery, except, oddly enough it will reflash the same t999 image. The radio (modem) also no longer works.

mr_legolas said:
May be it is, I updated to 4.3 thru OTA and after a few days rooted and installed CM 10.2. How do I check?
Then this should be the reason that ODIN didnt work for me. Which genuine source I should look at for a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.
Click to expand...
Click to collapse
This is why your flash to stock failed, lucky for you. The MJB bootloader is not downgradable and if 'successful' is bad news...aka brick, requiring serious hacking if not JTAG service to repair. As far as ROM's go as long they do not attempt to change the bootloader (none i've seen do, but you never know) the worst that could happen is a 'status 7' fail in recovery and no change to your firmware, pertaining to the bootloader that is. There are any number of other reasons why something could go wrong during the process. MJB has been around long enough most customs ROM's have probably adapted their updater-script to include it. If not there are ways around this I (and several others) have documented elsewhere. My advice moving forward, make sure to educated yourself thoroughly before attempting anything that can brick your device and if you are not sure, ask first flash later.

dmplus said:
when you say "find" an AT&T 4.3 rom, I wish you could give me a link. I am working with a device that was handed to me that was on 4.3 then flashed to a t999 rom. Now I cannot get it to flash ANYTHING AT&T 4.3 (and I've looked all over), neither in odin, nor in recovery, except, oddly enough it will reflash the same t999 image. The radio (modem) also no longer works.
Click to expand...
Click to collapse
I assume your can get into download mode. If that is the case, try flashing this in Odin: http://forum.xda-developers.com/showthread.php?t=2498233

audit13 said:
I assume your can get into download mode. If that is the case, try flashing this in Odin: http://forum.xda-developers.com/showthread.php?t=2498233
Click to expand...
Click to collapse
I had tried to flash that via odin without success. What I was able to do to fix the issue was to flash a custom recovery via odin (TWRP). Then use the custom recovery to blind flash (no signature or md5 check) the ATT modem, and then I was able to flash the link you sent. After that it still didnt boot, so i had to reboot in TWRP, dump caches, reboot again, wait, literally like 5 minutes and it came back to life. Whew, what a day.

[Q&A] [HOWTO] [ROOT] No Tripping Flash Counter - [ATT / Bell / Telus / Rogers / Sask

[Q&A] [HOWTO] [ROOT] No Tripping Flash Counter - [ATT / Bell / Telus / Rogers / Sask
Q&A for [HOWTO] [ROOT] No Tripping Flash Counter - [ATT / Bell / Telus / Rogers / Sasktel]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [HOWTO] [ROOT] No Tripping Flash Counter - [ATT / Bell / Telus / Rogers / Sasktel]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

DocHoliday77 said:
Has no one given this a try???
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Hi,
I'm completely new to phone rooting. I know the user guides say for noobs not to be the first to root with a new file but I have been watching this thread and have a Rogers S3 I747 with 4.4.2 on it. MrRobinson posted root66_RWC_I747MVLUFNF2.7z but nobody has posted anything in regards to this file. Has anybody rooted with this successfully? Should I go ahead and try it?
Thanks

Maverick0140 said:
Hi,
I'm completely new to phone rooting. I know the user guides say for noobs not to be the first to root with a new file but I have been watching this thread and have a Rogers S3 I747 with 4.4.2 on it. MrRobinson posted root66_RWC_I747MVLUFNF2.7z but nobody has posted anything in regards to this file. Has anybody rooted with this successfully? Should I go ahead and try it?
Thanks
Click to expand...
Click to collapse
You are on stock Rogers 4.4.2 ROM? If you are, do not flash any of the ROMs from the link in the first post as this could brick your phone.

audit13 said:
You are on stock Rogers 4.4.2 ROM? If you are, do not flash any of the ROMs from the link in the first post as this could brick your phone.
Click to expand...
Click to collapse
Yes I am on 4.4.2 baseband version I747MVLUFNF2. Ya the first page are older files, I am wondering about the latest that MrRobinson had posted with file name root66_RWC_I747MVLUFNF2.7z. Just wondering if anyone has used this successfully as being a noob it probably would take me forever to fix it if I screwed it up.

Stuck a Samsung screen
So I did try the latest injected root tar for rogers 4.4.2 root66_RWC_I747MVLUFNF2.7z with out good luck, Odin installed fine no errors at all after phone reboot wont past the Samsung glowing logo I still can get into download mode and stock recovery I wipe everything then try to flash back the root image and still got on the same problem wont finish booting anyways cant get it back to stock cause there is no stock image for 4.4.2 cant find one. any helps or future steps
View attachment 3027002
View attachment 3027003
View attachment 3027004

root/unlock galaxy s3
I have a Galaxy s3 (i747m) running 4.4.2 And need to root/unlock the device. I tried towelroot, but it just end up with application not installed. From what I read, there is one rooted rom from rogers uner 4.4.2. My phone is from bell can I install this rom ? Otherwise what can I do to root it ?

Rooting will not sim unlock the phone and there is no need to root the phone in order to enter a sim unlock code.
The best thing to do is sim unlock the phone using the proper code, install recovery, install supersu.

Rooting Problem with SGS3 I-747 ATT Unlocked
Hi,
I was following the steps shown in this thread : http://forum.xda-developers.com/showthread.php?t=1739426
to root my Samsung Galaxy S3 I-747 AT&T. My 2 year contract has ended, my phone is unlocked and I am using a T-Mobile simcard on this phone at the moment. I encountered a problem while Odin wanted to start the rooting process from "aboot.mbn". It shows an error:
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I am using the ATT IMAGE (Current I747UCDLK3 (JB 4.1.1)) as PDA
I also tried Heimdall and got the same error in aboot.mbn.
I'd really appreciate it if you could help me here. I tried restarting the phone a few times and repeating the rooting but everytime it stops there.
My phone info:
SAMSUNG-SGH-I747
Android 4.4.2
Kernel : 3.4.0-1514807
Thank You,
Soheyl

The Odin flash is failing because you are trying to downgrade the bootloader.
Search the General forum to find a stock rom that is compatible with your bootloader.

4.4.2 denied me towelroot, looking for something easier...
So I'd attempt this method if I know whether it works on the most recent version of 4.4.2.,
A bit about my situation -- some of you may be able to stop me and tell me it's not my operating system but maybe a sensor issue. I've been unable to 100% charge naturally and safely and whenever I see a green lit notification, if I take off my phone from the charger, the battery plummets to a lifespan of 2 hours. the biggest culprit is Android System. My immediate desire was to root and try a new rom but I heard others with similar situations.. So I tried three different fresh batteries with no luck. I turned off playstore and google functions.. Samsung things, AT&T you name any bloat, even facebook is off the phone. The phone drops dramatically in battery, then it rises back up, and then it falls again. It's too unpredictable and I would rather wait until the s6 comes out before I upgrade.
So 4.4.2 changed Wake lock detector and since I need root access for the best out of greenify, here I am.
can anyone help me out? I tried towelroot, and v3 doesn't support my device. I really want to rely on my phone again. Please help.

If you have no warranty left on your phone, I suggest flashing the latest Philz Touch for the d2lte via Odin, flash supersu from recovery, boot the phone, allow supersu to update, allow supersu to disable knox, done.

CuCh0 said:
So I did try the latest injected root tar for rogers 4.4.2 root66_RWC_I747MVLUFNF2.7z with out good luck, Odin installed fine no errors at all after phone reboot wont past the Samsung glowing logo I still can get into download mode and stock recovery I wipe everything then try to flash back the root image and still got on the same problem wont finish booting anyways cant get it back to stock cause there is no stock image for 4.4.2 cant find one. any helps or future steps
Click to expand...
Click to collapse
I have this same problem.

Samsung Galaxy s3 soft brick
I got an over the air update from AT&T which I guess didn't go well because the settings app kept crashing. I had never done anything technical with the phone so I called them and they recommended doing a factory reset. I tried this and it didn't solve the problem and I was out of warranty so I decided to try and fix it myself. I have tried a few different methods of trying to get the phone to work with different md5 files but nothing has worked so far. I can get to download mode and recovery mode but nothing else. I tried putting version on called root66_ATT_I747UCDLK3.7z and got this error message (see below). This one seemed to get the furthest but I'm at a loss now. I believe I have already rooted the phone but at this point I'm not sure what has stuck. I followed the instructions from http://forum.xda-developers.com/showthread.php?t=1739426 but now I'm thinking it might have something to do with the update version I had on it originally? I have been reading that you can't go back to a previous version if you already installed a later one. So lost and I don't know what stuck with the OTA update.
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> NON-HLOS.bin
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Odin mode
Product name:sgh-1747
Current binary :custom
System status: custom
Qualcom secureboot: enable
Warranty bit:1
Bootloader ap swrev: 3
Secure check fail: modem

Do not flash anything ROMs with Odin as the phone is running at least a 4.3 bootloader.
I recommend installying a custom recovery, installing a custom ROM, and confirming the bootloader and modem on your phone before flashing anything else.

[Q] What is the best method to unroot my Note 4?

Stupid me, didn't read up enough to realize that rooting the Note 4 breaks OTA updates. It looks like I can pull the update down via Kies 3. But before I do that I want to make sure I'm going in the right direction.
So far I've found two options, would any of these work to allow OTA updates to work again?
1) Use Kies 3 and install the update
2) Reinstall the original ROM following the instructions on this page...
http://androidromupdate.com/2014/11/07/n910pvpu1anie-sprint-samsung-note-4-sm-n910p-stock-firmware/
3) hit the "full unroot" button in SuperSU Free
Any recommendations guys?

MeepZero said:
Stupid me, didn't read up enough to realize that rooting the Note 4 breaks OTA updates. It looks like I can pull the update down via Kies 3. But before I do that I want to make sure I'm going in the right direction.
So far I've found two options, would any of these work to allow OTA updates to work again?
1) Use Kies 3 and install the update
2) Reinstall the original ROM following the instructions on this page...
http://androidromupdate.com/2014/11/07/n910pvpu1anie-sprint-samsung-note-4-sm-n910p-stock-firmware/
3) hit the "full unroot" button in SuperSU Free
Any recommendations guys?
Click to expand...
Click to collapse
There is already an updated stock rom floating around. Do you have Odin downloaded to your computer?
---------- Post added at 05:21 PM ---------- Previous post was at 05:19 PM ----------
cmdauria said:
There is already an updated stock rom floating around. Do you have Odin downloaded to your computer?
Click to expand...
Click to collapse
Just follow this thread and you will be golden!! Very easy thing to do.
http://forum.xda-developers.com/note-4-sprint/general/stock-n910pvpu1anie-stock-tar-t2944867

MeepZero said:
Stupid me, didn't read up enough to realize that rooting the Note 4 breaks OTA updates. It looks like I can pull the update down via Kies 3. But before I do that I want to make sure I'm going in the right direction.
So far I've found two options, would any of these work to allow OTA updates to work again?
1) Use Kies 3 and install the update
2) Reinstall the original ROM following the instructions on this page...
http://androidromupdate.com/2014/11/07/n910pvpu1anie-sprint-samsung-note-4-sm-n910p-stock-firmware/
3) hit the "full unroot" button in SuperSU Free
Any recommendations guys?
Click to expand...
Click to collapse
1. My phone was stock rooted, I upgraded using Kies and the phone status changed from custom to Official. Then I rerooted and it changed back to custom again. That leads me to believe that if you upgrade using Kies and don't re-root it will accept OTA updates again. I can't confirm that though. (The Knox flag of course remained tripped, no way to fix that as of now)
2. Don't know, but I would expect any full stock Odin would allow OTA as long as the status is Official.
3. NO, I tried the full unroot button on SuperSU and the status remains Custom, and it won't even check for OTA.
Kies was very easy for me, I didn't have to unroot and at least in my case all data and apps were retained. With Odin you will end up with a factory fresh phone and have to restore all your data and apps.

That answers my question. I'll try the kids method and re root later. Thanks for the help

MeepZero said:
That answers my question. I'll try the kids method and re root later. Thanks for the help
Click to expand...
Click to collapse
and did the OTA do anything for ya??? good or bad??

Quick reply, in case someone finds this looking for a similar solution. I removed root completely via the app and then updated via Kies, can't tell yet if I'll be able to OTA update from now on but it was a successful update.

poit said:
1. My phone was stock rooted, I upgraded using Kies and the phone status changed from custom to Official. Then I rerooted and it changed back to custom again. That leads me to believe that if you upgrade using Kies and don't re-root it will accept OTA updates again. I can't confirm that though. (The Knox flag of course remained tripped, no way to fix that as of now)
2. Don't know, but I would expect any full stock Odin would allow OTA as long as the status is Official.
3. NO, I tried the full unroot button on SuperSU and the status remains Custom, and it won't even check for OTA.
Kies was very easy for me, I didn't have to unroot and at least in my case all data and apps were retained. With Odin you will end up with a factory fresh phone and have to restore all your data and apps.
Click to expand...
Click to collapse
Let me get this straight...
You were rooted on NK2 and plugged into Kies and just installed the OB7 without having to flash to factory and update OTA and it worked good? I do have a custom rom installed though.
Once i am re-rooted on OB7 I will not be installing anything but ROMs so I do not need to worry about OTA using Kies would make this sooooooo much easier.

Note 4 sm-n910G
Hi all Android fans of the world. I own a stock rooted Kitkat Galaxy note4. I have Kies 3 and Odin installed and would like to go back to stock unrooted in order to get L-5.0.1 OTA when it finally comes. Can anyone show me a link for the firmware on Sammobile or elsewhere plz... i am a recent convert from iphone and just learning things from scratch. Thankyou in advance

LightspeeDLee said:
Hi all Android fans of the world. I own a stock rooted Kitkat Galaxy note4. I have Kies 3 and Odin installed and would like to go back to stock unrooted in order to get L-5.0.1 OTA when it finally comes. Can anyone show me a link for the firmware on Sammobile or elsewhere plz... i am a recent convert from iphone and just learning things from scratch. Thankyou in advance
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3056478
Sent from my SPH-L710 using xda app-developers app

unroot failed
so i finally managed to find a download for my note 4 that wasnt just jargon. Loaded to ODIN hit the start button all looked good and then i get a fail at the end.
no stuck on the downloading screen with a message:
Volume size is too big
ODIN: Invalid ext4.img
This is what is in the ODIN message if this helps you at all :
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910FXXU1BOC5_N910FEUR1BOD2_N910FXXU1BOC4_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> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!

technophobe321 said:
so i finally managed to find a download for my note 4 that wasnt just jargon. Loaded to ODIN hit the start button all looked good and then i get a fail at the end.
no stuck on the downloading screen with a message:
Volume size is too big
ODIN: Invalid ext4.img
This is what is in the ODIN message if this helps you at all :
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
N910FXXU1BOC5_N910FEUR1BOD2_N910FXXU1BOC4_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Added!!
Odin v.3 engine (ID:5)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
aboot.mbn
NAND Write Start!!
sbl1.mbn
rpm.mbn
tz.mbn
sdi.mbn
NON-HLOS.bin
boot.img
recovery.img
system.img.ext4
modem.bin
cache.img.ext4
hidden.img.ext4
RQT_CLOSE !!
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Removed!!
Click to expand...
Click to collapse
Is your phone SM-N910P or SM-N910F?
You posted in SPRINT Q&A FORUM.
If phone truly is SM-N910F, please post in correct forum.
SM-N910P? Download tar from this post below, the md5 is 68EC06027A3ECFE8471263256B139257
http://forum.xda-developers.com/showpost.php?p=62230599&postcount=1
I'd suggest that one for faster download but only for SM-N910P.
Edit: never mind; try KIES instead.
Sent from my SM-N910P using Tapatalk

sorry my bad
its a SM910F btw still no luck but have put in my original message which is what i thought i was in already...

technophobe321 said:
its a SM910F btw still no luck but have put in my original message which is what i thought i was in already...
Click to expand...
Click to collapse
Got it. So it was rooted at one point with another firmware on it? Did KIES emergency recovery do anything for it?
So I'm guessing it has stock recovery but won't flash or boot at this point. If so, boot into recovery, factory reset, reboot recovery and factory reset again. Power down, remove battery, wait 30 seconds and boot into download mode and flash the stock tar with auto reboot disabled (preferably one that has a md5 checked against downloaded zip, then drag the tar.md5 image out of opened archive with 7zip). You'd only have F. Reset Time enabled in Odin options.
Pass or fail, power down, pull battery, wait 30 seconds, boot into download mode and flash stock tar with auto reboot enabled plus the F. Reset Time enabled. Close Odin with each flash attempt.
One other thing that has worked in the past is considering the suggestions given, use your imagination to try similar things with custom recovery or flashing parts of the stock tar like extracted bootloader and kernel and (emergency) recovering with KIES. Or even flash CWM recovery, write everything, reboot recovery, wipe again, flash a rooted SM-N910F ROM, un-root it and wipe everything, power down, pull battery and flash stock tar. Take notes of attempt to avoid trying the same thing twice until you succeed. I think you will eventually get it. If so report, the steps that you think were primarily responsible for success.
Best wishes for success and return of the phone.
Sent from my SM-N910P using Tapatalk

thanks
thanks for the info it seems the main problem i have is getting the valid file. everyone i try fails with 2 mb left or a 1.7gb file turns into 3.2gb i have paid for sammobile super download and also rapid transfer but both are either corrupted files or just jargon. The one from rapid transfer almost worked until it got near the end and as the file was 3.2 gb it was too large.
i need the correct file for an SM910F unlocked from a reliable source and the genuine file everywhere i try fails or is a virus.

technophobe321 said:
thanks for the info it seems the main problem i have is getting the valid file. everyone i try fails with 2 mb left or a 1.7gb file turns into 3.2gb i have paid for sammobile super download and also rapid transfer but both are either corrupted files or just jargon. The one from rapid transfer almost worked until it got near the end and as the file was 3.2 gb it was too large.
i need the correct file for an SM910F unlocked from a reliable source and the genuine file everywhere i try fails or is a virus.
Click to expand...
Click to collapse
These should also be trusted sources for SM-N910F.
http://forum.xda-developers.com/showpost.php?p=58814028&postcount=1
I think your ISP may be contributing to bad downloads. You may have to download from another location.
SMH; the other suggestions stemmed from previous difficulties with other users after crashing Odin with wrong stock tar. Hopefully your case is as simple as getting a good download for the SM-910F.
Sent from my SM-N910P using Tapatalk

SAMSUNG NOTE 4 SM-N910P SPRINT USA:
I am getting an error while downloading the update to marshmallow when i just clicked on the software update it says "The operator system in your phone is modified through unauthorized way please try to install update through smart switch or visit a customer service" is anyone can help me to figure out this issue i needs to update my phone as soon as it possible. I did check as well my phone has not rooted so far but still is giving an error mentioned above.

Help with a soft-bricked SGH-I747

This SGH-I747 (I think it is for AT&T, but I'm in Canada so I'm not sure) updated OTA from 4.3 to 4.4.2 (I think), and rebooted OK. Next, I let it update KNOX, and on the next reboot it went into a reboot loop. Now I'm trying to fix that. I can't get into recovery mode (it shows the blue "RECOVERY BOOTING..." text at the top of the screen, but reboots before reaching the recovery menu), but I can get it into download mode. Neither Kies or ADB recognize the device when it is plugged in my Windows 7 machine, but Odin can connect and flash firmware to it. This is my first try fixing a bricked phone.
I've tried flashing a few different versions of stock images from sammobile, but most fail within a few seconds of starting the process with Odin (1.85, 3.9, or 3.10) with 'Fail (Auth)' in Odin's messages. I guess that is KNOX blocking downgrades to anything under 4.4.2 or 4.3. I can get all the way through the flashing process with I747MVLUFOB1_I747MOYCFOB1_I747MVLUFOB1_HOME.tar.md5 (Bell 4.4.2 for SGH-I747M) however the phone is still stuck in a reboot loop afterwards. Odin's output from that is:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747MVLUFOB1_I747MOYCFOB1_I747MVLUFOB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> NON-HLOS.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Right now, the top left of the phone's 'Downloading...' screen says:
ODIN MODE
PRODUCT NAME: SGH-I747M
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER RP SWREV: 2
The sticker behind the battery says the phone is an SGH-I747 (not a SGH-I747M). I think I should be looking for a AT&T 4.4.2 ROM, but I haven't found one yet (just the Canadian carrier versions, or OTA upgrade packages that look too small to be useful). I don't have a SD card to use. What should I try next to get this phone working again? There's no important data on this phone to lose, and I don't mind using non-official software if I have to. I don't know much about boot loaders or custom recovery mods yet.

Do not try to flash i747m bootloader to an i747 as this would probably brick your phone.
There is no stock ATT 4.4.2 ROM as AT&T never made it available. 4.4.2 was only available as an OTA update.

> Do not try to flash i747m bootloader to an i747 as this would probably brick your phone.
Too late! Did it before I even posted here The fun part is to figure out what I can do next. I can still get to the download screen. I've tried flashing it with an AT&T 4.1.1 ROM (I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5), but Odin fails like this:
<ID:0/004> Odin engine v(ID:3.1005)..
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
From what I'm reading, it is a bit more work to downgrade from 4.3 (even I hadn't flashed the I747 with I747M firmware) because KNOX locks the bootloader somehow. I'm guessing that putting a new bootloader on the phone is a step in the right direction towards getting the stock 4.1.1 firmware running. I found this thread, but I'm not sure if it is what I need: http://forum.xda-developers.com/showthread.php?t=2321310

If the phone does not say i747m on the label in the battery compartment, the phone is an AT&T version of the s3. I have 3 s3 phones is various states of disrepair and they all say i747m.
You flashed a 4.4.2 i747m ROM, including bootloader and modem, onto the i747. You cannot flash any bootloader that is older than the one you installed. It is not knox that is blocking the bootloader downgrade.
Knox has nothing to go with locking the bootloader as all bootloaders on the i747 and i747m have never been locked. Using apps that "unlock" the bootloader will probably brick the phone, as will flashing an internation s3 ROM.

Thanks for helping me confirm it is the AT&T version. Since there is no official AT&T 4.4.2 (or newer) firmware, restoring the phone using any sort of official Samsung firmware must not be an option. Do you think using a newer 3rd party ROM is an option? I see this list of ROMs with Android 4.4.4 and 5.x (http://forum.xda-developers.com/galaxy-s3-att#romList), but I wonder if I can install any of them over what's on the phone right now (Bell 4.4.2). I don't think I have anything to lose by trying these out, unless there is something more reliable I should try first.

The phone may not be booting because the file ROM, boot, and modem paritions on an i747 maybe different from an i747m.
You could flash a custom recovery (CWM, Philz Touch, or TWRP) to the phone and use that to install a custom ROM. If the ROM boots, that would be a start. If the ROM can start and you can get a signal to make a call and surf via cellular networks and wifi, that would be great.

Enewman17 has a thread with stock 4.4.2 for the i747, he built it from image dumps. I believe there is an option to revert to stock recovery if needed.
---------- Post added at 11:04 PM ---------- Previous post was at 11:02 PM ----------
dawgdoc said:
Enewman17 has a thread with stock 4.4.2 for the i747, he built it from image dumps. I believe there is an option to revert to stock recovery if needed.
Click to expand...
Click to collapse
This is the thread http://forum.xda-developers.com/showthread.php?t=2788357

> The phone may not be booting because the file ROM, boot, and modem paritions on an i747 maybe different from an i747m.
Is this something that a PIT file can help with? I found one called sgh-i747-16gb.pit at d-h.st/x9S that I could try running with Odin.
I rooted the phone with CF-Auto-Root (CF-Auto-Root-d2att-d2uc-samsungsghi747.zip from autoroot.chainfire.eu) via Odin, and flashed it with CWM 6.0.4.7 (CWMS3ATTrecovery.tar galaxys3root.com/cwmtwrp-recovery/) with Odin as well. Now I can get into CWM Recovery! That's progress. I could not get into stock recovery earlier. I'll try more tomorrow.
I'll be very happy if I can get this device running and connecting to Wi Fi. Cellular is not important right now.

Since the phone has a custom recovery, are you able to flash the latest cm11 to the phone and have it boot properly?
The pit file may not help without a stock rom that can be flashed in Odin but I am not sure about this as I have no experience with cross-flashed bootloaders or modems.

Yeah, this must look pretty weird. I bought a SD card and I'm deciding what to try next. I know the bootloader version is I747MVLUFOB1. I downloaded some Cyanogen builds for the I747 and I'm looking in their `updater-script` files to see if any will install over what I have.
cm-11-20140210-SNAPSHOT-M3-d2att is looking for certain boot loaders and won't install on a device with I747MVLUFOB1.
Then there are the newer unified builds:
cm-11-20141112-SNAPSHOT-M12-d2lte isn't picky about boot loaders. It just checks ro.product.device and ro.build.product is acceptable (d2att in my case), so that could work.
cm-11-20150426-NIGHTLY-d2lte isn't picky about boot loaders. It just checks ro.product.device and ro.build.product is acceptable (d2att in my case), so that could work.
I'll try cm-11-20141112-SNAPSHOT-M12-d2lte, then cm-11-20150426-NIGHTLY-d2lte if M12 doesn't work.

I tried installing cm-11-20141112-SNAPSHOT-M12-d2lte and cm-11-20150426-NIGHTLY-d2lte from a .zip file on the SD card (16GB class 10). I wiped the phone's caches first. Neither resulted in the phone booting successfully. After rebooting from CWM, the Samsung logo appears, and then the screen goes back to black. I wait a few minutes, and then pull the battery when it doesn't look like there is any activity.
I can still access CWM which is promising. I'm going to look into riskier stuff like dawgdoc's suggestion, or trying to install a I747 boot loader unless people have other suggestions.

xancow said:
I tried installing cm-11-20141112-SNAPSHOT-M12-d2lte and cm-11-20150426-NIGHTLY-d2lte from a .zip file on the SD card (16GB class 10). I wiped the phone's caches first. Neither resulted in the phone booting successfully. After rebooting from CWM, the Samsung logo appears, and then the screen goes back to black. I wait a few minutes, and then pull the battery when it doesn't look like there is any activity.
I can still access CWM which is promising. I'm going to look into riskier stuff like dawgdoc's suggestion, or trying to install a I747 boot loader unless people have other suggestions.
Click to expand...
Click to collapse
how about trying a different recovery as @audit13 suggested earlier. if i'm not mistaken cwm development stopped long ago.
good luck.
"all i can really do , is stay out of my own way and let the will of heaven be done"

mrrocketdog said:
how about trying a different recovery as @audit13 suggested earlier. if i'm not mistaken cwm development stopped long ago.
good luck.
Click to expand...
Click to collapse
Thanks for the reminder! I skipped over Philz Touch and installed TWRP (twrp.me/devices/samsunggalaxys3att.html) with Odin 3.10.6. TWRP looks like it hasn't been updated in 3 years (github.com/TeamWin/device_samsung_d2att) but it was able to flash cm-11-20141112-SNAPSHOT-M12-d2lte. This time I can boot into CyanogenMOD, use WiFi and both cameras. ADB recognizes the device. Big success! The funny part is the phone still thinks its model number is SGH-I747M in Settings > About Phone.
Next step is installing the Google apps, and then curiosity will drive me to try out other versions of Cyanogen or other operating systems.
Thanks for the help audit13 & mrrocketdog! Hopefully I've left a good trail of info for anyone else who screws their phone up line this.

good to here. all credit to @audit13.:good:
"all i can really do , is stay out of my own way and let the will of heaven be done"

A pleasant surprise (I swear, this wasn't the goal) - I put a Fido sim card into the phone and it could make and receive calls, and use data. I didn't try texting.

Does everything now work? Your phone is still recognized as an i747m?

audit13 said:
Does everything now work? Your phone is still recognized as an i747m?
Click to expand...
Click to collapse
Everything I've tried so far works. No stability issues browsing the net over WiFi which is what it will mostly be used for. The OS thinks the model number is SGH-I747M. Baseband version is from the Bell 4.4.2 ROM I flashed to it. The Kernel and Build # are from CyanogenMOD.

Well, this is certainly interesting because it appears that cross-flashing will turn an i747 into an i747m which makes recovering from a bad flash much easier.

Samsung Tab 8.4 sm-t320 bootloader locked?

HI All
Firstly, long time read of this forum/app, first time poster. Flashed a number pf phones/tablets over the years since i first flashed my Windows HTC HD (?) to Android Gingerbread. Forgive the details there, it was a long time ago and I could be slightly wrong.
In any case I usually have no problem following the odd customer rom flashing guide or rooting guide, etc and generally get done what I need to,. However after a few late nights and admittedly having not flashed anythign for a couple of years I am really struggling to flash my t320 with anything!
I cannot seem to flash TWRP so I am coming to te conclusion the bootloader is locked. I have read around and it seems as though it shouldnt be locked or I should have an OEM Unlock option in developer options - I do not!
I have managed to root it though using Odin and the CF Auto Root but if I try runnig TWRP app to flash TWRP or Flashify to flash a lineage ROM I do not seem to get anywhere. It just boots as normal with TWRP and I dont get any TWRP in recovery mode. Flashify result in a boot loop so I had to reflash the root to get it to boot,
When I enter into download recovery mode the following shows on the screen:
ODIN MODE
PRODUCT NAME: SM-T320
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
WRITE PROTECTION: Enable
UDC Start
I am hoping someone can dicipher this and tell me what the problem is. Clearly it looks like somethign is securing the bootloader.
Oh yes and this is the UK WIfi model running stock Kitkat 4.4 (updated as far as I can get it OTA)
Thanks in advance

@radioshed I've flashed my T325 again not to long ago, after I had to return to stock. So I know bootloader isn't locked.
Did you take care to boot directly into TWRP after flashing it via Odin?
If you let it reboot automatically the stock recovery gets reanimated.
Uncheck "auto reboot" in Odin and do it manually.
I never use anything else but Odin and read that TWRP app isn't recommended to use.
Know nothing about flashify.
Rooting stock isn't necessary as you're going to flash a custom ROM anyhow.

Yea I had auto reboot off and booted into recovery when Odin finished.
Looked just the same. No TWRP
Not sure what else to do

bmwdroid said:
@radioshed I've flashed my T325 again not to long ago, after I had to return to stock. So I know bootloader isn't locked.
Did you take care to boot directly into TWRP after flashing it via Odin?
If you let it reboot automatically the stock recovery gets reanimated.
Uncheck "auto reboot" in Odin and do it manually.
I never use anything else but Odin and read that TWRP app isn't recommended to use.
Know nothing about flashify.
Rooting stock isn't necessary as you're going to flash a custom ROM anyhow.
Click to expand...
Click to collapse
Rather than using Odin to flash TWRP and then that for a customrom, can I just use Odim for the rom?
If so which box do I use in Odin?
Thanks for your response btw

radioshed said:
Yea I had auto reboot off and booted into recovery when Odin finished.
Looked just the same. No TWRP
Not sure what else to do
Click to expand...
Click to collapse
Which file did you take and where from?

radioshed said:
Rather than using Odin to flash TWRP and then that for a customrom, can I just use Odim for the rom?
If so which box do I use in Odin?
Thanks for your response btw
Click to expand...
Click to collapse
Odin can not flash custom ROMs

bmwdroid said:
Which file did you take and where from?
Click to expand...
Click to collapse
I have the cf auto root for the t320 which I downloaded. That worked tho
I got the tar file for TWRP from the TWRP website, the apk too.
I've tried both to flash the TWRP recovery but I still seem to end up with the original recovery screen

radioshed said:
I have the cf auto root for the t320 which I downloaded. That worked tho
I got the tar file for TWRP from the TWRP website, the apk too.
I've tried both to flash the TWRP recovery but I still seem to end up with the original recovery screen
Click to expand...
Click to collapse
After flashing turn it off and reboot with button combo.
Perhaps you were not fast enough when rebooting directly after flashing. I sometimes need to flash TWRP several times.
You've put it in "AP" didn't you?

You've flashed tar file?

bmwdroid said:
After flashing turn it off and reboot with button combo.
Perhaps you were not fast enough when rebooting directly after flashing. I sometimes need to flash TWRP several times.
You've put it in "AP" didn't you?
Click to expand...
Click to collapse
Yea in the AP section. Auto reboot off.
Boot straight into recovery. No change

What does Odin say after flashing?

bmwdroid said:
You've flashed tar file?
Click to expand...
Click to collapse
Yeaa I have, don't have the filename to hand as it's on my laptop. But yea I've done it a few times

Which Odin btw?

Ermm I have 2 versions. One that came with the auto root and a slightly newer version.
I'll confirm when I get on my laptop

The older the stock the older Odin has to be.
Try 3.09 or older.

Ooo ok never thought of that thanks for the tip.

OK So i have some more details...still no change here though unfortunately
I have just tried a few TWRP flashes using Odin 3.09 but also tried 3.14.1 and 3.10.6 for CF-Auto-Root-mondrianwifi-mondrianwifixx-smt320.tar.md5 which does work
I have tried flashing the following files from https://eu.dl.twrp.me/mondrianwifi/:
twrp-2.8.4.1-mondrianwifiue.img.tar
twrp-3.1.1-0-mondrianwifiue.img.tar
twrp-3.1.1-0-picassowifi.img.tar (not sure where i got this one from)
twrp-3.5.2_9-0-mondrianwifi.img.tar
not sure what else to do but cant get rid of the download recovery screen

bmwdroid said:
What does Odin say after flashing?
Click to expand...
Click to collapse
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/008> Added!!
<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> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/008> Removed!!
<ID:0/008> Added!!
<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> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

radioshed said:
OK So i have some more details...still no change here though unfortunately
I have just tried a few TWRP flashes using Odin 3.09 but also tried 3.14.1 and 3.10.6 for CF-Auto-Root-mondrianwifi-mondrianwifixx-smt320.tar.md5 which does work
I have tried flashing the following files from https://eu.dl.twrp.me/mondrianwifi/:
twrp-2.8.4.1-mondrianwifiue.img.tar
twrp-3.1.1-0-mondrianwifiue.img.tar
twrp-3.1.1-0-picassowifi.img.tar (not sure where i got this one from)
twrp-3.5.2_9-0-mondrianwifi.img.tar
not sure what else to do but cant get rid of the download recovery screen
Click to expand...
Click to collapse
After flashing around that much it might be helpful to return to a clean system/device by flashing multiple part stock ROM via Odin and then start again flashing just TWRP without CF prior to that.
picassowifi is the 10.1" tab btw.
I'd stick to 3.09 until TWRP is flashed as I know it worked on mine while having stock.

bmwdroid said:
After flashing around that much it might be helpful to return to a clean system/device by flashing multiple part stock ROM via Odin and then start again flashing just TWRP without CF prior to that.
picassowifi is the 10.1" tab btw.
I'd stick to 3.09 until TWRP is flashed as I know it worked on mine while having stock.
Click to expand...
Click to collapse
Thanks pal, I tried that last night, flashed back to stock 4.4.2 using Odin 3.09.
Altho the download I found for it only seemed to have one tar file. Not sure if I need a BL tar too.
Still no dice tho dammit