Develop Bugs

[Q] [Help] Flashed stock ROM via ODIN, hangs at T-Mobile splash screen

Need to warranty my Note 3 due to hardware camera problem. I unlocked my factory 4.3 bootloader, installed TWRP, and went to W03 Slim 8.5. I have never ran the official 4.4.2 update which I believe implies my bootloader is still the 4.3 version.
I launched ODIN 3.07, and flashed the N900TUVUBMI7 rom from this page: AndroidRootz
Everything appears to have ran in ODIN successfully:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900TUVUBMI7_N900TTMBBMI7_N900TUVUBMI7_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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
The phone boots up with no warnings on the Samsung splash and then gets to the white T-Mobile 4G LTE splash and just hangs there. I've tried reflashing the firmware from ODIN with the same result.
What should I do? Should I flash up to the 4.4.2 version? The phone is going back regardless so I don't care about anything other than getting this to boot up so I can exchange it.

Tried from ODIN 3.09 with the same result. I have the 4.4.2 firmware but I am hesitant to flash it until someone can shed some light on this issue.

negativefx said:
Tried from ODIN 3.09 with the same result. I have the 4.4.2 firmware but I am hesitant to flash it until someone can shed some light on this issue.
Click to expand...
Click to collapse
Try wiping /data or a factory reset in recovery.

Have you tried re-downloading the 4.3 firmware. Sometimes this can happen from a bad download.

Shawn said:
Try wiping /data or a factory reset in recovery.
Click to expand...
Click to collapse
You read my mind... Just read that an ODIN firmware flash doesn't wipe. Booted to recovery, did a wipe data from recovery and rebooted. Works like a champ. Thanks!

happened to almost everyone, I had to odin v3.09 and run 2 times... the 1st time it said it was successful, but stuck at the Samsung screen, the 2nd time booted up just fine..
on my link I have odin and the new firmware, old firmware my stock not rooted roms... all u need for my stock not rooted is chainfire superuser app, then download busybox, your done,
look on my signature for any files needed, also uploading the Samsung driver.. no kies needed.

negativefx said:
You read my mind... Just read that an ODIN firmware flash doesn't wipe. Booted to recovery, did a wipe data from recovery and rebooted. Works like a champ. Thanks!
Click to expand...
Click to collapse
No problem, I used to forget to wipe when I put my phones back to stock with Odin.

I'm currently running an AOSP rom 4.4.2...what are the steps to flash the 4.3 stock rom touchwiz??

4.4.2 is out? newest firmware available atm is nk3 4.4.2
anyway
1. d/l firmware file from sammobile.com
2. boot to download mode
3. run odin and plug phone into pc(if you have a mac your on your own from here as i have a pc and not a mac)
4. load file you just d/led(in tar.md5 format) into the pda slot(i'm assuming you have odin 3.07)
5. click start and wait to profit.
you can also d/l 4.3 firmware from same site if you really want it.
good luck

I meant I have a AOSP custom rom its regular google not touchwiz
Sent from my SM-N900T

right. thats how you restore stock touchwiz though. it's pretty simple.

will I lose root?..so if I have this current baseband which is MI7..does that mean that I still have 4.3 bootloader?
Sent from my SM-N900T

yeah you will lose root. but you can reroot it afterwards. and yes if you flash the 4.3 firmware it'll keep the 4.3 bootloader or should anyway. might want to wait on someone else to chime in here on the bootloader and baseband though as i am not really sure. i just upgraded from a note 2 to my note 3. and i run nk3 on my note 3. it's fine with all the roms i have tryed so far though. no issues at all.

I'll wait a lil bit cause someone just told me that since I'm on 4.4.2 custom aosp rom I won't be able to revert back to 4.3 Touch wiz
Sent from my SM-N900T

i'd just go with the nk3 firmware. it's 4.4.2 stock touchwiz. works great. but thats me. hehe

this is my android version and that is my baseband..im soo confused
View attachment 3079890
Sent from my SM-N900T

ok. your baseband and bootloader are 4.3, but your custom rom is a 4.4.2 rom. if you install the nk3 firmware. you'll have stock touchwiz 4.4.2 with the nk3 baseband and bootloader along with the csc file. and a bunch of otherstuff. it will all be upgraded. instead of having a custom 4.4.2 rom you'll be on the newest stock touchwiz version which is nk3.
nk3 can be rooted. you can install a custom recovery and still reinstall custom roms.
if that makes sense.

that's wat I was looking for, thanks dude..this is my version of ODIN that I have..this is what I used to root the phone when I first got it last year
View attachment 3079899
Sent from my SM-N900T

1.8.5 will work. been so long since i seen that version. just add the tar.md5 file to the pda slot. click start and profit

is it better to upgrade ODIN to tge latest version or just stick with 1.85?
Sent from my SM-N900T

[Q] Looking to update older phone onto newer rom

I've not touched my phone in over a year (at least it seems that way)
I'm on an older version on Android (4.1.2) and baseband MD4
What do i need to flash one of these new roms? I haven't flashed or checked up on roms etc in a long time. So i'm kind of lost with all this new ND8 stuff.
Any help would be great, as to what i need to do in order to flash a newer rom.

zookeeper525 said:
I've not touched my phone in over a year (at least it seems that way)
I'm on an older version on Android (4.1.2) and baseband MD4
What do i need to flash one of these new roms? I haven't flashed or checked up on roms etc in a long time. So i'm kind of lost with all this new ND8 stuff.
Any help would be great, as to what i need to do in order to flash a newer rom.
Click to expand...
Click to collapse
Ignore the ND8 stuff, as that is indicitive of a newer modem and bootloader, and you would be getting yourself deep into Samsung KNOX territory. If you don't know what KNOX is, there's plenty of info on it here on XDA and on the web. All I can say is be careful with KNOX.
If you flash PhilZ recovery via ODIN and your ROM of choice and GAPPs via PhilZ, you shouls be good to go.
PhilZ DL link:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
.MD5 files are for ODIN, .zip files are for later updating the recovery within the recovery.
GAPPs DL link:
http://paranoidandroid.co/gapps/

Higgs_Boson said:
Ignore the ND8 stuff, as that is indicitive of a newer modem and bootloader, and you would be getting yourself deep into Samsung KNOX territory. If you don't know what KNOX is, there's plenty of info on it here on XDA and on the web. All I can say is be careful with KNOX.
If you flash PhilZ recovery via ODIN and your ROM of choice and GAPPs via PhilZ, you shouls be good to go.
PhilZ DL link:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
.MD5 files are for ODIN, .zip files are for later updating the recovery within the recovery.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2768483
that is the rom that i'm looking to flash. It says that i need to be on ND8 or it will brick my phone. So do i need to flash a stock ND8 rom or something with the philz touch recovery?
Is there a tutorial some where for flashing PhilZ? I don't really remember how to use ODIN.

zookeeper525 said:
http://forum.xda-developers.com/showthread.php?t=2768483
that is the rom that i'm looking to flash. It says that i need to be on ND8 or it will brick my phone. So do i need to flash a stock ND8 rom or something with the philz touch recovery?
Is there a tutorial some where for flashing PhilZ? I don't really remember how to use ODIN.
Click to expand...
Click to collapse
If you have your sights on that ROM, I encourage you to read that thread's original post carefully.
There is a link where you should direct your questions regarding that ROM.
As for using ODIN, it's quite simple. Just download it and run the program from the folder directly (no installation required). Choose "PDA", find the recovery file (.MD5), and press start.
If the recovery doesn't stick, you may have to uncheck the "auto-reboot". Retry the flashing process. Once finished (should read "PASS" in green), unplug the USB remove the battery, re-insert the battery while holding Power+Vol UP+Home. That should take you into PhilZ.

Higgs_Boson said:
If you have your sights on that ROM, I encourage you to read that thread's original post carefully.
There is a link where you should direct your questions regarding that ROM.
As for using ODIN, it's quite simple. Just download it and run the program from the folder directly (no installation required). Choose "PDA", find the recovery file (.MD5), and press start.
If the recovery doesn't stick, you may have to uncheck the "auto-reboot". Retry the flashing process. Once finished (should read "PASS" in green), unplug the USB remove the battery, re-insert the battery while holding Power+Vol UP+Home. That should take you into PhilZ.
Click to expand...
Click to collapse
What version of ODIN are you using? I got "Odin-v3-09" off google and there doesn't seem to be a "PDA" option.

zookeeper525 said:
What version of ODIN are you using? I got "Odin-v3-09" off google and there doesn't seem to be a "PDA" option.
Click to expand...
Click to collapse
I use 3.07, but the "AP" option will flash it for you.

Higgs_Boson said:
I use 3.07, but the "AP" option will flash it for you.
Click to expand...
Click to collapse
Do i have to boot into download mode or something to flash the recovery?
If i just have my phone on this is all it does
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.25.0-d2lte.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..
I'm not sure what i'm doing wrong.

Yes, boot into Download Mode. Power+Vol Down+Home.

Higgs_Boson said:
Yes, boot into Download Mode. Power+Vol Down+Home.
Click to expand...
Click to collapse
Hm, it connected to the phone that time, but it failed.
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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Would it be better if i just flash a stock ND8 rom and then reflash the phone?

zookeeper525 said:
Hm, it connected to the phone that time, but it failed.
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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Would it be better if i just flash a stock ND8 rom and then reflash the phone?
Click to expand...
Click to collapse
Try ODIN 3.07 and use the PDA option. Not sure if that'll help, but give it a go.

The ND8 works great for some, and others dont like it. Personally id flash ND8 as i get better LTE signal with it. After ND8 boots flash philz recovery in odin 3.07 like he suggested.. go back to recovery and root with the philz option, under the "advanced" menu i believe, and install supersu on the stock rom. Run supersu and it will prompt you to disable knox, just hit yes. Then update to your rom of choice.
Sent from my SPH-L710 using XDA Free mobile app

Higgs_Boson said:
Try ODIN 3.07 and use the PDA option. Not sure if that'll help, but give it a go.
Click to expand...
Click to collapse
Thanks for the help. I ended up just flashing the stock ND8 run and reflashing using Auto-Root or w/e it's called. Then i flashed the "Tribute" rom and it seems to be working great.
Thanks again!

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.

need to reprogram as the phone stuck at Samsung Galaxy S III

My phone got crashed which can't bootup. The phone always stayed with Official release, never rooted. I am not sure which version has been upgraded to, now it stuck with Galaxy S 3 screen, only thing I know it has the SecureLinux enabled, so it must be either 4.3 or 4.4. I wanted to reprogram to the official firmware, but not sure if I reprogram to the wrong version, would that causes any problem?
Please help.

additional infomation:
at download mode:
PRODUCT nAME: SGH-T999
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOM SECUREBOOT: ENABLE

Does this download menu look like 4.2?
Or it is 4.3 , I dont see warrenty flag.
Thanks.

No mention of arrange bit or Knox is the screen so the phone must be running a 4.2.2 or older rom.

audit13 said:
No mention of arrange bit or Knox is the screen so the phone must be running a 4.2.2 or older rom.
Click to expand...
Click to collapse
The phone is T999 for T-mobile, but seems there is one time only that it had official release of 4.2.1 or 4.2.2 available. I am not sure if I should flash the 4.1.2 or 4.2.1 back. But I seem can't find the 4.2.1 or 4.2.2 firmware on line anymore.
Question is that if I try to flash 4.1.2 to the phone, would it cause any problem if it was in 4.2.1?
Thanks all, I know this probably an old issue.

Flashing 4.1.1 or 4.1.2 should be fine.

audit13 said:
Flashing 4.1.1 or 4.1.2 should be fine.
Click to expand...
Click to collapse
###Right now I can't go to recovery mode, so I am trying to program the stock recovery, but failed. When I tried to odin the stock 4.1.2 it failed too. Here is the error during flashing stock recovery.
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Tried different USB cables? Different USB ports? The rom cam from sammobile.com?

audit13 said:
Tried different USB cables? Different USB ports? The rom cam from sammobile.com?
Click to expand...
Click to collapse
Here is the error msg:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)

It's stops when trying to flash the bootloader. Either you're using the wrong file or the phone does have a 4.3 bootloader. The download screen info provided in your post mentions nothing about warranty bit or Knox.

audit13 said:
It's stops when trying to flash the bootloader. Either you're using the wrong file or the phone does have a 4.3 bootloader. The download screen info provided in your post mentions nothing about warranty bit or Knox.
Click to expand...
Click to collapse
thanks for your response, yes the bootloader seems is 4.1.2, right now I am getting impatient about this, So I also tried to repartition it, reload the 4.1.2 bootloader. I can reload the 4.1.2 bootloader, that is only flash got success, flashed the 4.1.2 bootloader.
I have a second identical phone, So I can risk everything in the phone. Is there anyway I can just program it to 4.3?

You can flash a newer stock rom via Odin if you want to. If the bootloader is 4.1.2 and you have the correct stock rom, Odin should be able to flash the aboot.mbn file it Odin can't which tells me the file is wrong for the phone or the phone does have a 4.3 or newer bootloader.

thanks for your response, yes the bootloader seems is 4.1.2, right now I am getting impatient about this, So I also tried to repartition it, reload the 4.1.2 bootloader. I can reload the 4.1.2 bootloader, that is only flash got success, flashed the 4.1.2 bootloader.
I have a second identical phone, So I can risk everything in the phone. Is there anyway I can just program it to 4.3? All I want is just get the phone back. I tried to load 4.3 bootloader, but it failed.

audit13 said:
You can flash a newer stock rom via Odin if you want to. If the bootloader is 4.1.2 and you have the correct stock rom, Odin should be able to flash the aboot.mbn file it Odin can't which tells me the file is wrong for the phone or the phone does have a 4.3 or newer bootloader.
Click to expand...
Click to collapse
There is possibility that the pit is wrong, I tried to load the downloaded T999-16Gb pit from download site, maybe that file is not right? Since I can flash the stock boot.img by using Odin for version 4.1.2, the bootloader must be right???, Don't know what aboot.mbn would be affected by anything else.
I am wondering if someone can provide the T999 regular 16GB pit file, the early version of T999, Thanks.

A pit file only needed if Odin cannot read the partition info from the phone and, based on the logs, a pit should not be necessary.

audit13 said:
A pit file only needed if Odin cannot read the partition info from the phone and, based on the logs, a pit should not be necessary.
Click to expand...
Click to collapse
is it possible that the phone is upgrading from 4.1.2 to 4.3 and got crashed. but the bootloader is still showing 4.1.2?
what other possible reason that I can't flash aboot.mbn?

Boot into download mode again and let me know what it says. It the bootloader was corrupt, that would be a problem.
Just to confirm: you're using firmware from sammobile.com and you are using the original Samsung USB cable to flash the phone.

audit13 said:
Boot into download mode again and let me know what it says. It the bootloader was corrupt, that would be a problem.
Just to confirm: you're using firmware from sammobile.com and you are using the original Samsung USB cable to flash the phone.
Click to expand...
Click to collapse
Reboot to download mode, it is saying the same.
I am trying to flash stock recovery, modem, bootloader, all stock version 4.1.2 Only it can flash 4.1.2 bootloader, the recovery and modem always fails. Also the stock rom got failed.
With the same setting I can flash my other S3 recovery without problem, so the Odin, USB cable should not be an issue.
Thanks.

Yes, this is weird. You have 2 identical phones? You can pull the pit file from the working phone and use it to flash the problematic phone.

audit13 said:
Yes, this is weird. You have 2 identical phones? You can pull the pit file from the working phone and use it to flash the problematic phone.
Click to expand...
Click to collapse
the only problem is that my other working phone is running 4.3. I don't know what is the procedure to program it to 4.3 if my crashed one is in 4.1.2

Upgrade to 6.0 help?

Hello all, I have not been on this site in a long time and was wondering if i can be pointed in the right direction to upgrade to 6.0? Currently, I am on OJ7 5.1 with hacker kernel, TWRP. I dont even know how many updates have been made since 0j7. I did find this, http://forum.xda-developers.com/sprint-galaxy-s6/general/sprint-galaxy-s6-sprint-mm-6-0-odin-t3333530 but will i just flash this and i'll be good? do i need to flash a different kernel, radio, etc? Also I am looking to try out a different kernel, so any suggestion would be great. thank you in advance.

Everything that you need (files, instructions) is here: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862

koop1955 said:
Everything that you need (files, instructions) is here: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
Click to expand...
Click to collapse
Thanks for the quick reply, finally just finished downloading all files needed, haha. Using my 4G hotspot. so just flash the PG3 tar and I'll be golden? No need to flash a separate kernel, or anything like that besides the recovery and Super Su?

P1_e85 said:
Thanks for the quick reply, finally just finished downloading all files needed, haha. Using my 4G hotspot. so just flash the PG3 tar and I'll be golden? No need to flash a separate kernel, or anything like that besides the recovery and Super Su?
Click to expand...
Click to collapse
It all depends on what you want. Flash the TAR in Odin, then BEFORE you root or install TWRP, take the update to PI3 if you like. (Some people have reported faster battery drain and it is only a minor security update, so decide what you want.) You'll be 6.01 either way.
Flash the CG-auto root file and then TWRP and you will have Root and Recovery.
Renegade is the only current ROM (even that is no longer supported) and SkyHigh the only kernel, but neither are really necessary. Look in the Android Development section and make up your own mind.

Well hopefully someone can help me, figured i'd ask in same thread first. The upgrade to 6.0 was successful also rooting and hotspot mod which was m main concern. but after all that was done I tried to flash Magisk v7, according to the thread it said to flash two files the v7 and phh zips. After that it would not boot up, just stuck on Samsung Galaxy S6 powered by android screen. I already tried to reflash 6.0 tar file but it gives error.
<ID:0/008> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
any help much appreciated, I am still searching for a fix. As now i can still go into recovery and download mode, tried to restore a old 5.1 back up I had and same thing happens stuck at Samsung screen.

P1_e85 said:
Well hopefully someone can help me, figured i'd ask in same thread first. The upgrade to 6.0 was successful also rooting and hotspot mod which was m main concern. but after all that was done I tried to flash Magisk v7, according to the thread it said to flash two files the v7 and phh zips. After that it would not boot up, just stuck on Samsung Galaxy S6 powered by android screen. I already tried to reflash 6.0 tar file but it gives error.
any help much appreciated, I am still searching for a fix. As now i can still go into recovery and download mode, tried to restore a old 5.1 back up I had and same thing happens stuck at Samsung screen.
Click to expand...
Click to collapse
First thing to try, since you can get into recovery, is a factory reset.
Big note: After any version update (5.x to 6.x) never try to restore any earlier version.

koop1955 said:
First thing to try, since you can get into recovery, is a factory reset.
Big note: After any version update (5.x to 6.x) never try to restore any earlier version.
Click to expand...
Click to collapse
Already tried the factory reset, any advanced wipe maybe? I tried the restore after the wipe did nothing.

Try flashing the new PI3 TAR file here: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862

koop1955 said:
Try flashing the new PI3 TAR file here: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
Click to expand...
Click to collapse
Thanks after flashing multiple files and such and no luck I finally tried renegade rom and it booted. Yipee, not sure if i'm going to mess around a lot more haha, probably will though. Might try to flash back to stock touch wiz with the provided tar. and hopefully 7.0 comes for the s6. thenf or sure flashing that.