Database Develop

I9305t 4.3 wont boot

HI all,
Today I decide to update my i9305t to the 4.3 rom. I unrooted my phone and reset the custom counter and all was good. I flashed the telstra rom and all was good. Because of the locked dock Icons I thought I would flash a different unbranded rom. During the installation (via odin) it went skew if and froze. It sat there for ages but I ended up having to do a battery pull.
When I went to the download menu on the phone, knox had been tripped and there was 47 instances. Any way I reflashed the telstra firmware. It passed but now the phone gets stuck on the Samsung logo.
OK now I have already.....
Pulled the battery.
Removed all cards sim and sd.
Restored different firmwares.
factory reset, clear cahce etc.
Installed custom recovery and cleared devalk cache.
Googled for similar events.
Nothing I have read has worked.
I cant think of what else to do. When I restore a firmware via odin everything is OK, it passes but on the reboot it just stops at Samsung logo and goes no further.
I gather that because the phone can still get into recovery and download mode there must be something can sort this out.
Thanks in advance.

flash the original firmware from samsung.....the 4.3 since you updated it...
after it finishes and reboots it will enter a boot loop....IT'S NORMAL.....pull out the battery and start the phone in recovery mode(stock one) and do a wipe data - factory reset and wipe cache partition...it should work without a problem...did this many times...
after you updated to 4.3 you should have done a full wipe...

spiderman07 said:
flash the original firmware from samsung.....the 4.3 since you updated it...
after it finishes and reboots it will enter a boot loop....IT'S NORMAL.....pull out the battery and start the phone in recovery mode(stock one) and do a wipe data - factory reset and wipe cache partition...it should work without a problem...did this many times...
after you updated to 4.3 you should have done a full wipe...
Click to expand...
Click to collapse
Yeah I have done that. I have tried it about 10 times. Im going to give it another bash today as I am stuck using my wife's old Iphone and its horrendous.

try installing your firmware with a .PIT file and check repartition box...search for the pit file....
if this doesn't work i suggest going to local repair shop and let them have a look...
maybe something got broke when you flashed the unbranded firmware...

spiderman07 said:
try installing your firmware with a .PIT file and check repartition box...search for the pit file....
if this doesn't work i suggest going to local repair shop and let them have a look...
maybe something got broke when you flashed the unbranded firmware...
Click to expand...
Click to collapse
Thanks for the info. Im unsure what a PIT file is. Are they phone specific or just model specific.
Cheers
Pat

Filipiak said:
Thanks for the info. Im unsure what a PIT file is. Are they phone specific or just model specific.
Cheers
Pat
Click to expand...
Click to collapse
Found the pit file and read up on it. Tried to use it but it fails as soon as it starts.

Best of luck
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )

AMoizK said:
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
Click to expand...
Click to collapse
Knox was tripped when the firmware install crashed. So knox tripping is no issue. Thanks for the information. I will have a go tommorrow.
I did manage to restore a cm9 backup but my IMEI is now gone and I cant get to the menu to restore my back up. Seems like Samsung has done a number on my phone. In all the years ive been fingering phones with custom firmware and modding I have never had anything stuff up this bad. Its rather amusing that it has happened flashing a stock rom that belongs to my phone.

AMoizK said:
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
Click to expand...
Click to collapse
AMoizK you are the ****en man. Worked. The part that worked for me was the format everything. IMEI restored as well. Phone is perfect. Now i dont need to use my wifes crappy old iphone.
WOOT!!!!

Filipiak said:
AMoizK you are the ****en man. Worked. The part that worked for me was the format everything. IMEI restored as well. Phone is perfect. Now i dont need to use my wifes crappy old iphone.
WOOT!!!!
Click to expand...
Click to collapse
Cheers

Filipiak said:
HI all,
Today I decide to update my i9305t to the 4.3 rom. I unrooted my phone and reset the custom counter and all was good. I flashed the telstra rom and all was good. Because of the locked dock Icons I thought I would flash a different unbranded rom. During the installation (via odin) it went skew if and froze. It sat there for ages but I ended up having to do a battery pull.
When I went to the download menu on the phone, knox had been tripped and there was 47 instances. Any way I reflashed the telstra firmware. It passed but now the phone gets stuck on the Samsung logo.
OK now I have already.....
Pulled the battery.
Removed all cards sim and sd.
Restored different firmwares.
factory reset, clear cahce etc.
Installed custom recovery and cleared devalk cache.
Googled for similar events.
Nothing I have read has worked.
I cant think of what else to do. When I restore a firmware via odin everything is OK, it passes but on the reboot it just stops at Samsung logo and goes no further.
I gather that because the phone can still get into recovery and download mode there must be something can sort this out.
Thanks in advance.
Click to expand...
Click to collapse
It happened to me once, i found that 4.3 won't boot if baseband and imei are unknown. when you were trying to flash with odin and your phone got stuck it probably has damaged or ( erased ) your imei partition. try flashing 4.1.1 ( the package file without bootloader files ) it will definitely work for you. the reason is simple , Samsung's stock 4.3 never boots if the imei is corrupt or unknown (baseband is then usually too ) so, flash 4.1.1 , root your phone and install Persus kernel +any modem / baseband file, this is the only solution as i dont know how but does repair your imei , but you will be stuck at 4.1.1.

[Q] Help needed for GT-I9295

Hello, i've updated my i9295 to 4.4.2 using the official stock rom for netherlands with odin. (sammobile.com/firmwares/3/?download=30085)
Model: GT-I9295
Model name: GALAXY S4 Active
Country: Netherlands
PDA: I9295XXUCNE5
The phone started after flash and worked very well, but then after a shutdown, it doesn't work telling me that system process is shutdown, after some seconds it reboots and keep on samsung logo..i've tried to wipe cache etc on recovery, but it works only one time, after one boot and shutdown it does the same. I can't understand why this firmware is not working
The CSC of my phone is different from the one i updated from, and i can't be able to downgrade back to 4.2.2 because of knox restriction..
what can i do to restore a working firmware?
does this unworking depends from CSC Code that needs to be changed?
I've seen that also the PDA code of the firmware is different from the original phone one (I9295XXUBMK3)
If i wait for 4.4.2 firmware with the same PDA, will it be working again? Or there is something else i can do?
waiting for an answer,
Thanks

no one can tell me something about this problem?

Hi
Normally CSC don't make troubles.
I advise you to first perform a full wipe in recovery, if this not solve your problem or you want to disable knox, flash super su in CWM.
When you'll launch supersu, it will ask you if you want to disable knox.

thanks for reply,
the recovery full wipe and format for data doesn't help,
but how can i flash super su in CWM? root is needed to use supersu,
Anyway i think i cannot downgrade cause 4.4.2 to 4.2.2, because bootloader block downgrade, or if i disable knox i can downgrade?

If you root your present rom you'll be able to de-knox.
Step by step.
1-install ClockWorkMod trough odin
2-Download supersu.zip, place in your phone memory and in CWM go to "install zip" and install supersu
3-reboot and open your brand new app "supersu", it will say you knox was detected and ask if you want to disable.
4-Your phone is rooted and de-knoxed
You can find all these tools in this forum but here they are.
Unzip CWM and flash
don't modify supersu and place it to the root of your phone's internal memory

thank you, i was able to do this procedure, getting root and deknoxing using supersu tool,
but i was not able to reistall 4.2.2 firmware cause bootloader still block my attempt when i try to replace the bootloader with the old one
My problem is that i cannot run 4.4.2 cause after 1 boot and 1 shutdown of the device, it doesn't boot anymore, getting stuck on Samsung logo.
I have to wipe data and cache every time i want to run..and so I cannot use the phone
I would like to find a way to return to 4.2.2 stock, or to get this 4.4.2 working more then 1 time after device restart
Is this possible in some way?
Just to remember, i used a firmware with different PDA code from the official of my phone, could it be the cause of the samsung logo after 1 boot?
Thanks

mmmmh pretty strange, look like your bootloader is locked like I537.
The CSC do nothing normally, my phone come with a non european CSC and I flash a nordic rom in france.
Did you perform a wipe of dalvik cache (in CWM "advanced" "wipe dalvik") plus the other wipes.
To make a good one, you have to wipe 3 things and the cache is not the most important.
The files build.prop stay in dalvik cache (if my memory's good) and load the new version only when wipe dalvik.
The build.prop is a kind of ID card (maybe the source of your trouble).

It doesn't helped, i wiped dalvik but the dalvik folders seems to be not present as i can saw in the logs of recovery...
But when you flashed your firmware, you used the same PDA or different? Have you ever used a different PDA?
To be precise, the second time i try to boot after shutdown it teels me that system process has crashed, the phone do not respond on touch, and then it reboots automatically and get stuck on samsung logo on next boots
I don't know what could be the cause of this, are present log files to investigate what fails in the boot of the system?
The only thing i have doubt is about PDA code of the firmware

i have the same problem
hi. i have the same problem with my s4 active i9295. region TTT
Phone: Samsung S4 Active
Model: GT-I9295 (unlocked)
OS: Android 4.2.2 (J.B.)
AP: I9295VJUBMK4
CP: I9295VJUBMK4
CSC: I9295UUBBMK1
Build #: JDQ39.I9295VJUBMK4
Kernel: 3.4.0-2045428
[email protected] #1
Tues Nov 19 20:37:24 KST 2013
i am now on a boot lop and cannot install back 4.2.2. what is the ideal rom that is compatible with my phone region???
thanks in advance

[Q] help! soft-bricked my phone :/

Hi. I'm new to the forum but not new to android and samsung. I got greedy and impatient and wanted to load the lollipop G900T update on my G900A. I got root with the OA1 update, installed busybox, installed safestrap. Tried to install G900T update, but the phone rejected it. Thought I could be even more adventurous and install cyanogenmod so I went into safestrap and did a system wipe, which is where my problems began.
Here's what I can do:
-go into recovery
-go into download mode
-install files from odin
-see the battery charge animation when the phone is off
Here's what my problem is:
as soon as i start the phone, i get the galaxy s5 logo powered by android along with the giant unlocked lock that says custom (busybox or safestrap i assume). then i see the samsung animation and then it freezes. then i get a black screen with the pulsating blue light at the top of the phone. my guess is that it was soft brick so i tried to find every guide on the internet to reset it and it still comes back to that unlocked lock and freezing animation. as probably few of you have experienced, i began to think the worst - should i sell it for parts? is there a religious ritual? what am i going to do?
Here's what i've tried:
-following these http://forum.xda-developers.com/showthread.php?t=2785363
-flashing stock from sammobile
-doing both along with a nand erase all function
-attempting to install the BL file from the first link (fail)
i know the g900a isn't particularly a developer-friendly device with the locked bootloader and att being att, but please tell me there's hope. i can supply any odin logs you want.
p.s. if it helps, i get the fused 2 binary 1 when i try to flash sammobile stock file. or the bootloader file from the first link.

U can try by starting here.
http://forum.xda-developers.com/showthread.php?p=58621872
The general section had quite few good threads on updating g900a.

ovodennis said:
Hi. I'm new to the forum but not new to android and samsung. I got greedy and impatient and wanted to load the lollipop G900T update on my G900A. I got root with the OA1 update, installed busybox, installed safestrap. Tried to install G900T update, but the phone rejected it. Thought I could be even more adventurous and install cyanogenmod so I went into safestrap and did a system wipe, which is where my problems began.
Here's what I can do:
-go into recovery
-go into download mode
-install files from odin
-see the battery charge animation when the phone is off
Here's what my problem is:
as soon as i start the phone, i get the galaxy s5 logo powered by android along with the giant unlocked lock that says custom (busybox or safestrap i assume). then i see the samsung animation and then it freezes. then i get a black screen with the pulsating blue light at the top of the phone. my guess is that it was soft brick so i tried to find every guide on the internet to reset it and it still comes back to that unlocked lock and freezing animation. as probably few of you have experienced, i began to think the worst - should i sell it for parts? is there a religious ritual? what am i going to do?
Here's what i've tried:
-following these http://forum.xda-developers.com/showthread.php?t=2785363
-flashing stock from sammobile
-doing both along with a nand erase all function
-attempting to install the BL file from the first link (fail)
i know the g900a isn't particularly a developer-friendly device with the locked bootloader and att being att, but please tell me there's hope. i can supply any odin logs you want.
p.s. if it helps, i get the fused 2 binary 1 when i try to flash sammobile stock file. or the bootloader file from the first link.
Click to expand...
Click to collapse
Head over to this link http://forum.xda-developers.com/att...to-root-g900aucu2aoa1-4-4-4-2-3-2015-t3021120 and download the G900A_Downgrade_to_NCE.tar and flash via odin. Take the 2 ota updates and your phone will be all fixed. THis will delete all of your data though.

Thanks! I posted a similar issue after I downgraded from OA1 to NCE using the stock NCE bundled with 4 files. It is important to use the downgrade, not the 4 file NCE stock.

ovodennis said:
Hi. I'm new to the forum but not new to android and samsung. I got greedy and impatient and wanted to load the lollipop G900T update on my G900A. I got root with the OA1 update, installed busybox, installed safestrap. Tried to install G900T update, but the phone rejected it. Thought I could be even more adventurous and install cyanogenmod so I went into safestrap and did a system wipe, which is where my problems began.
Here's what I can do:
-go into recovery
-go into download mode
-install files from odin
-see the battery charge animation when the phone is off
Here's what my problem is:
as soon as i start the phone, i get the galaxy s5 logo powered by android along with the giant unlocked lock that says custom (busybox or safestrap i assume). then i see the samsung animation and then it freezes. then i get a black screen with the pulsating blue light at the top of the phone. my guess is that it was soft brick so i tried to find every guide on the internet to reset it and it still comes back to that unlocked lock and freezing animation. as probably few of you have experienced, i began to think the worst - should i sell it for parts? is there a religious ritual? what am i going to do?
Here's what i've tried:
-following these http://forum.xda-developers.com/showthread.php?t=2785363
-flashing stock from sammobile
-doing both along with a nand erase all function
-attempting to install the BL file from the first link (fail)
i know the g900a isn't particularly a developer-friendly device with the locked bootloader and att being att, but please tell me there's hope. i can supply any odin logs you want.
p.s. if it helps, i get the fused 2 binary 1 when i try to flash sammobile stock file. or the bootloader file from the first link.
Click to expand...
Click to collapse
A couple more things because of the G900A locked down bootloader you won't be able to flash any Lollipop Roms until ATT drops official update.
You also CANNOT flash any ASOP Roms or custom kernels.

gentlemen!
i followed your advice and flashed the downgrade rar. sat in my chair with a frown as i waited for it to load until i heard the infamous at&t tone, the screen light up, and the 'connect to wifi' screen come up.
blessed! thank you! i promise to be patient and always be grateful to the xda community. many thanks again!
:good:

Back to stock

Hy
I see that a lot of people (so did I) had problems of going back to stock, so i wil write a little guide for doing this.
I am not responsibility i anything goes wrong.
Before starting you need the following:
Odin3-v3.07 => you can find it here (CF-Auto-Root)
firmware => http://www.sammobile.com/firmwares/
Before we begin, we need two files. The firmware that you have downloaded and also a file rom this firmware called hidden.img.tar.
Open your firmware with winrar and extract the file "hidden.img". When you have this file rename it to "hidden.img.tar"
Now we can really begin
step 1: (optional)
go to recovery (Vol+ & home & Pwr) and wipe your phone.
step 2:
Open Odin as administrator and put your phone in download mode ( Vol - & home & Pwr)
Click on the "AP" button and choose your firmware.
When the firmware is loaded click "start". The firmware will now being flashed on your phone. Most likely you wil get an error after a while when it was flashing the "hidden.img" file (no stress
step 3:
Unplug your phone and reboot it again to download mode (nothing else will work at this point) and connect it again to your PC. In Odin click again on the "AP" button and choose the file that we have created before the "hidden.img.tar" file. When loaded click on "start".
You don't get an error this time and your phone will restart and your phone is being flashed. when your are stuck at a bootloop, go to step 4
step 4:
Put your phone in recovery mode (will look a bit different if you had custom recovery before) and wipe your phone back to factory settings
I hope that this can help other people who where stuck trying to go back to stock

That's a good guide, thank you, worked for me flawlessly.
It might however be good to add: be patient on first boot! It takes ages

Hmm I am not sure. But for me the step 3 was not needed. I did not get error for hidden.img
Is it OK ? I was following your guide did everything as you wrote here till step 3 but during flashing the error was not there
Hope it will be working. Right now it is doing the first boot so waiting and waiting. Hope it will work as I need to return this phone to my older brother who borrow it to me. And I want to give him the phone as it was when he gave it to me.

Hello, i have bought Samsung Galaxy S5 MINI model SM-G800F.
There is Cyanogenmod 12.1-20150707-unofficial-kminilte
android version 5.1.1
baseband (i think) G800FXXU1AOF5
Problem is with MMS - I cant send or receive it thats why
id like to go back to stock rom, but i need few details.
i know how to do it in theory, but first of all, i dont know nothing about what last user have done witch phone, what schould i check to not brick my phone?
in your description is written to download Firmware, tell me pls, which version i have to download, my orginal is (i think) :
PDA/AP Version G800FXXU1AOF5
CSC Version G800FDBT1AOF1
MODEM/CP Version G800FXXU1AOF5
Region DBT — Germany
Build Date 2015-06-29
Changelist 5268468
OS KitKat
OS Version 4.4.2
but this is old kitkat and now i have got version 5.1.1 can i use any rom or that one orginal or only newer or the same version is already installed?
second question i bought this phone from Germany and i live in Poland, can i flash my phone with stock polish version of for example PLAY carrier or i have to do it only witch orginal German stock ROM?
thanks for replay T_M
now i know my model is SM-G800FZKADBT so i can only download rom for this model - yes?

Sorry for pulling this old thread from its grave.
I have wiped my Samsung S5 min (SM-G800F, DBT) completely, i.e. all(!) partitions and also did a "format data", since no data worth to keep were on it. Then I started Odin as admin, placed the official latest Samsung FW (G800FXXU1CRG3_G800FDBT1CRE1_G800FXXU1CRG3_HOME.tar.md5) in the "AP" field, had only "Auto Reboot" and "F. Reset Time" under "Options" ticked, and nothing under "Pit". The flashing worked without errors and the S5 mini rebooted. The "SAMSUNG" logo was blinking for about 10 minutes, but I was already warned that this first boot may really take a while. Finally, the device successfully booted into regular/stock system.
Now my questions:
So far, have I done everything right to go back to stock? I have not tampered with a "hidden.img" or "hidden.img.tar" file, hence this question.
Next, I would like to flash the latest official TWRP. Is it right to put "twrp-3.3.1-0-kminilte.img.tar" in the "AP" field of Odin (as before for the stock FW) and flash it? I would this time not select "Auto Reboot", but instead after successful flashing, plug the USB cable, remove the battery, place it back, and start the S5 mini (SM-G500F) to recovery by holding power + home + volume up. Correct?
Finally, I would lake to have Magisk. Is it right to place the official "Magisk-v20.2.zip" on the external SD card (oh, I wiped that before, too) and to flash it from recovery (TWRP) and then reboot the device to system?
Do I have to enable the developer options and (also?) ADB debugging for any of the aforementioned steps?
Thanks a lot for your helpful hints.
PS:
Stock worked nicely. Then I enabled developer options, ADB debugging, and flashed 1. TWRP (step 2 above) and 2. Magisk (step 3 above). Booting to system took much longer while a message about Android being started and App No. x of y being optimized. Since stock ROM contains tons of crappy apps, this took quite a while. I wonder why now (after flashing TWRP and Magisk) the system sees the need to optimise apps. Ah, is it because I also wiped cache and dalvik cache from TWRP after flashing Magisk? Maybe this was not needed, I dunno...

[SOS] - Calling All Devs - G920T - Stuck on 6.0.1 without an unlocked bootloader

Hello guardians of the Android Phones. I ran into a major issue while updating from 5.1.1 custom ROM to 6.0.1 that I found on this thread : http://forum.xda-developers.com/tmo...20t-android-6-0-1-marshmallow-update-t3356838
Steps I took:
1) Upgraded TWRP to 3.0.2.0 (3.0.2.1 doesn't work properly on my device. it flashes the TWRP 3 logo and then goes black) ... So I ended up re-installing TWRP 2.8.7.2 and then flashed TWRP 3.0.2.0
2) Copied the ROMS of choice to the SDCARD
3) Using Odin 3.10.7 I flashed using Twisted Sixx Custom ROM (which didn't work correctly due to the bootloader not being Marshmallow 6.0.1 compatible) from my understanding of what i've read through these threads.
4) Flashed the AP using G920TUVU3EPD1_G920TTMB3EPD1_G920TUVU3EPD1_HOME.tar.md5
Now i'm 100% locked out from downgrading Stock or Custom ROMS. TWRP can no longer be installed.
Having a feeling I used a Bear Trap ROM.
What do I do? Feeling like throwing this out the window. *sigh*.
Thanks ahead of time... anything to point me in the right direction would be greatly appreciated.

I am not a dev... but I tried smartswitch, perhaps it can help you. Hopefully you didn't do factory reset.
Try that and then if it doesn't work, again, wait for the experts.

What is SmartSwitch? Do you have a URL or THREAD with information and download links?
Thanks for the tip.
britchel said:
I am not a dev... but I tried smartswitch, perhaps it can help you. Hopefully you didn't do factory reset.
Try that and then if it doesn't work, again, wait for the experts.
Click to expand...
Click to collapse

I did an Odin flash of EPF1 and didn't lose the ability to flash recovery. I have not yet tried downgrading. I would take a deep breath, drink a beer or two, and go back through things step by step. At this point I would suggest using Odin to flash a complete image, perhaps of a different version, and go from there.

ninjadroids said:
What is SmartSwitch? Do you have a URL or THREAD with information and download links?
Thanks for the tip.
Click to expand...
Click to collapse
http://www.samsung.com/us/smart-switch/assets/downloads/Smart_Switch-PC_setup.exe
Hey can u reboot to recovery and to download mode?
You need to be in download mode to use smart-switch
Here's another tread alike to yours....
http://forum.xda-developers.com/tmo...rick-wont-boot-successful-odin-flash-t3435751

Smiles on the beer or two!
Are you using the G920T also? Which image did you Odin flash with? Do you have the direct link? I do like your idea of flashing with a different 6.x image variant as opposed to downgrading.
socal87 said:
I did an Odin flash of EPF1 and didn't lose the ability to flash recovery. I have not yet tried downgrading. I would take a deep breath, drink a beer or two, and go back through things step by step. At this point I would suggest using Odin to flash a complete image, perhaps of a different version, and go from there.
Click to expand...
Click to collapse

Yes I can reboot into recovery and to download mode. Thank you for the link.
britchel said:
http://www.samsung.com/us/smart-switch/assets/downloads/Smart_Switch-PC_setup.exe
Hey can u reboot to recovery and to download mode?
You need to be in download mode to use smart-switch
Here's another tread alike to yours....
http://forum.xda-developers.com/tmo...rick-wont-boot-successful-odin-flash-t3435751
Click to expand...
Click to collapse

ninjadroids said:
Smiles on the beer or two!
Are you using the G920T also? Which image did you Odin flash with? Do you have the direct link? I do like your idea of flashing with a different 6.x image variant as opposed to downgrading.
Click to expand...
Click to collapse
I don't unfortunately - Google is your friend. Some firmwares that come to mind are DOJ7, DOJC, and COF6.
But first: Is your bootloader locked? If you have not yet unlocked it, that may be a problem. I unlocked mine as soon as I got my phone (and yes I'm on a G920T). A locked bootloader may prevent downgrading although it should not prevent a rescue Odin of the same or newer firmware.

Yes it's locked.
Is there a way to unlock it while maintaining my current image?
All those firmware are 5.x
I'm stuck on unlocked Marshmallow 6.0.1
And according to Smart Switch. I'm one version down from latest with it prompting to upgrade.
I'm going to hold off on that for the moment...

If you flashed edp1, you are far from latest.
Lemme know if i am wrong at anything
If you can access download and recovery, that means the phone is in a bootloop when booting up..
Since you flashed the edp1 firmware, your bootloader must have been updated so now you can only use mm roms.
As for recovery, is it stock or twrp?
Also when in download modex whats your system status - stock or custom?

Well if EDP1 is far from latest, then that is great news. I can boot into my firmware. It's for sure stock as far as I can tell.
Download mode output:
RED: ODIN MODE
PRODUCT NAME: SM-G920T
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
FAP LOCK: OFF
BLUE: Secure Download: Enabled
Knox Warranty Void: 1 (I tripped it when rooting it in 5.x)
AP SWREV: B:3 K:2 S:2
It won't let me get into TWRP after flashing it... when I try it says the following:
RED: "RECOVERY IS NOT SEANDROID ENFORCING"
It doesn't matter which version of TWRP I attempt to flash with.
Thanks!
danveer said:
If you flashed edp1, you are far from latest.
Lemme know if i am wrong at anything
If you can access download and recovery, that means the phone is in a bootloop when booting up..
Since you flashed the edp1 firmware, your bootloader must have been updated so now you can only use mm roms.
As for recovery, is it stock or twrp?
Also when in download modex whats your system status - stock or custom?
Click to expand...
Click to collapse

Did you flashed root or anything after you tried to flash recovery via odin?
Also when you flashed edp1, phone still didnt boot?
Edp1 is about the march or april update i think
The next main update is epf1 because it restricts going back futher
Then there came a update 5 days ago.. just a security update... havent flashed that coz i am rooted..
Anyways lets concentrate on edp1
Since its a mm rom, going back to 5.1 roms means a bootloop, so ill suggest not doing that
Also after flashing the mm rom, if you flash anything over it, you wont be able to boot a system because a new dm verity check mm has introduced.. to bypass it, you either need to flash a mm root file or a kernel that can disable the check.
I was stuck at the same thing since i Flashed recovery and that failed the checks so was getting bootloops..
I was able to go in recovery and download mode but not boot up..
Since you have a custom status, it can be a reason for bootloops
http://forum.xda-developers.com/gal...y-official-twrp-galaxy-s6-edge-t3354508/page8

The phone boots. I just cannot get root. I guess I don't understand the terminology regarding "bootloops" or "MM" ... I attempted a APK root... which failed. And still using my previous kernel unless flashing the custom ROM overwrote that.
So I can login to the phone and connect it to USB and sideload APK files, no problem. I just cannot TWRP flash properly and enter it using the UP recovery mode. And when I tried flashing other ROMS in Download recovery mode either ODIN crashes or it gives me a NAND WRITE error.
Which root and / or kernel files would you suggest to me to flash in ODIN to break this protection that's preventing a full root on this image? Or would it be preferable in my situation to find a different ROM and resolving the ODIN crash problem to achieve a full 6.x marshmallow root?
Thanks again! Greatly appreciated Sir.
danveer said:
Did you flashed root or anything after you tried to flash recovery via odin?
Also when you flashed edp1, phone still didnt boot?
Edp1 is about the march or april update i think
The next main update is epf1 because it restricts going back futher
Then there came a update 5 days ago.. just a security update... havent flashed that coz i am rooted..
Anyways lets concentrate on edp1
Since its a mm rom, going back to 5.1 roms means a bootloop, so ill suggest not doing that
Also after flashing the mm rom, if you flash anything over it, you wont be able to boot a system because a new dm verity check mm has introduced.. to bypass it, you either need to flash a mm root file or a kernel that can disable the check.
I was stuck at the same thing since i Flashed recovery and that failed the checks so was getting bootloops..
I was able to go in recovery and download mode but not boot up..
Since you have a custom status, it can be a reason for bootloops
http://forum.xda-developers.com/gal...y-official-twrp-galaxy-s6-edge-t3354508/page8
Click to expand...
Click to collapse

ninjadroids said:
The phone boots. I just cannot get root. I guess I don't understand the terminology regarding "bootloops" or "MM" ... I attempted a APK root... which failed. And still using my previous kernel unless flashing the custom ROM overwrote that.
So I can login to the phone and connect it to USB and sideload APK files, no problem. I just cannot TWRP flash properly and enter it using the UP recovery mode. And when I tried flashing other ROMS in Download recovery mode either ODIN crashes or it gives me a NAND WRITE error.
Which root and / or kernel files would you suggest to me to flash in ODIN to break this protection that's preventing a full root on this image? Or would it be preferable in my situation to find a different ROM and resolving the ODIN crash problem to achieve a full 6.x marshmallow root?
Thanks again! Greatly appreciated Sir.
Click to expand...
Click to collapse
Which odin are you using?
Try 3.10.7 because using older odin on mm gives that nand write error...
That could explain a lot of things

I'm using 3.10.7 latest.
danveer said:
Which odin are you using?
Try 3.10.7 because using older odin on mm gives that nand write error...
That could explain a lot of things
Click to expand...
Click to collapse

http://forum.xda-developers.com/che...rite-start-fail-odin-soluction-t2851096/page5
Try this thread..
It has solutions when nand write fails...
Also trying a different verion pf odin might work like 3.10.6 or another maybe

ninjadroids said:
Yes it's locked.
Is there a way to unlock it while maintaining my current image?
All those firmware are 5.x
I'm stuck on unlocked Marshmallow 6.0.1
And according to Smart Switch. I'm one version down from latest with it prompting to upgrade.
I'm going to hold off on that for the moment...
Click to expand...
Click to collapse
EPD1 and EPF1 are 6.0.1 Marshmallow.
@ninjadroids:
Take this as you will but reading back through this thread gives me the impression that you lack the necessary know-how to customize your phone. I highly suggest you leave it stock for the time being until you know EXACTLY what you are doing.
My reasons for saying this:
-In your first post you state that "using Odin 3.10.7 I flashed using Twisted Sixx Custom ROM". To my knowledge there are NO custom ROMs designed to be flashed via Odin. They are in .zip files, to be installed via recovery ONLY.
-This is actually my mistake - the G920T bootloader does not have a lock function; flashing a custom recovery will simply trip the e-fuse and render it Knox 0x1 warranty void.
-You are not familiar with what Odin images are for the G920T, or what version they are. You should NEVER flash ANYTHING via Odin unless you are absolutely sure it is intended for your specific device.
-In the 9th post you state your bootloader is unlocked (again I apologize for the confusion) but in the 3rd line you say you're on unlocked Marshmallow. I'm going to assume you have limited knowledge of what the bootloader, the recovery, download mode, and system are.
-You mention seeing the red "RECOVERY IS NOT SE ANDROID ENFORCING". This is an error message generated by the bootloader saying the recovery is custom and did not pass the security check...but it is also completely normal. I get it every single time I go into TWRP...which works just fine.
-You do not understand what "MM" means when all of us including you are talking about Marshmallow.
-You do not understand what a "bootloop" is. For the sake of education, a bootloop is exactly what it sounds like - your device gets stuck in a loop while booting. This is generally mentioned when it is persistent - the device does not complete the boot process, coming to a stable useable Android interface. This is indicative of several possible problems; most likely you did something incorrectly, causing the boot process to halt, in which case the phone restarts itself to attempt to boot again, hence the loop.
-You do seem to understand sideloading via ADB and I'll give you credit for that. But when using the button combo (Vol Up+Home+Pwr) to boot into recovery, you WILL boot into recovery...whether that is stock recovery or TWRP. Some reboots may prevent this; if in doubt, hold Vol Down+Home+PWR until the screen shuts off; immediately go to Vol UP while still holding Home and Power.
-In the 13th post you ask about flashing kernels via Odin. Firstly: custom ROM .zips contain the kernel intended to work with that ROM. There is no need to flash anything separately. I am a little fuzzy on how root is accomplished on stock Marshmallow; it used to be we could flash SuperSu via recovery, but now there is talk about systemless...Anyway, I will reiterate what I was saying about Odin: DO NOT USE IT unless you know EXACTLY what you are doing. You have the potential to turn your phone into an expensive paperweight.
I am not trying to put you on blast or criticize you; I'm trying to help you avoid bricking your phone. There are a lot of things that could go wrong; you shouldn't be messing with something you don't understand, especially if you don't know how to fix it if something goes wrong.

For now even i am confused as to what is causing error.
Its probably that his storage is not curropt causing namd write fail..
I would recommend doing a backup. since you can turn on a phone, connect it to pc and move the important files and contacts to it.
Then download stock rom via sam mobile and do a clean install..
Ill prefer pf1 because, if memory serves right, edp1 had that notorious auto brightness bug.. If odin is not helping then try smart switch.
Boot up system, see if everything is working..it should be fresh as new.
After that follow the instructions as to flash twrp from the link i gave in one of my previous posts.. twrp should now flash...( i dont see any reason it shouldnt )
Flash root via recovery, or a custom rom you wanna flash but make sure its a 6.0.1 one ( xtre sto lite or alexis recommended )
That should root your phone too...
P.s. mm -> short for MarshMallow
Bootloop, when all you see is samsung logo which comes during boot... it wont go past that.. you never reach your lock screen or are able to unlock your phone... as mentioned in detail by -> socal
Flashing any rom overwrites kernel so if you flashed edp1, you are now on stock kernel...
P.p.s when you said sideload apk.. was it via adb shell or simply installing apk from internal memory of phone?

You answered a lot of my questions in that last post. Thank you kindly.
socal87 said:
EPD1 and EPF1 are 6.0.1 Marshmallow.
@ninjadroids:
Take this as you will but reading back through this thread gives me the impression that you lack the necessary know-how to customize your phone. I highly suggest you leave it stock for the time being until you know EXACTLY what you are doing.
My reasons for saying this:
-In your first post you state that "using Odin 3.10.7 I flashed using Twisted Sixx Custom ROM". To my knowledge there are NO custom ROMs designed to be flashed via Odin. They are in .zip files, to be installed via recovery ONLY.
-This is actually my mistake - the G920T bootloader does not have a lock function; flashing a custom recovery will simply trip the e-fuse and render it Knox 0x1 warranty void.
-You are not familiar with what Odin images are for the G920T, or what version they are. You should NEVER flash ANYTHING via Odin unless you are absolutely sure it is intended for your specific device.
-In the 9th post you state your bootloader is unlocked (again I apologize for the confusion) but in the 3rd line you say you're on unlocked Marshmallow. I'm going to assume you have limited knowledge of what the bootloader, the recovery, download mode, and system are.
-You mention seeing the red "RECOVERY IS NOT SE ANDROID ENFORCING". This is an error message generated by the bootloader saying the recovery is custom and did not pass the security check...but it is also completely normal. I get it every single time I go into TWRP...which works just fine.
-You do not understand what "MM" means when all of us including you are talking about Marshmallow.
-You do not understand what a "bootloop" is. For the sake of education, a bootloop is exactly what it sounds like - your device gets stuck in a loop while booting. This is generally mentioned when it is persistent - the device does not complete the boot process, coming to a stable useable Android interface. This is indicative of several possible problems; most likely you did something incorrectly, causing the boot process to halt, in which case the phone restarts itself to attempt to boot again, hence the loop.
-You do seem to understand sideloading via ADB and I'll give you credit for that. But when using the button combo (Vol Up+Home+Pwr) to boot into recovery, you WILL boot into recovery...whether that is stock recovery or TWRP. Some reboots may prevent this; if in doubt, hold Vol Down+Home+PWR until the screen shuts off; immediately go to Vol UP while still holding Home and Power.
-In the 13th post you ask about flashing kernels via Odin. Firstly: custom ROM .zips contain the kernel intended to work with that ROM. There is no need to flash anything separately. I am a little fuzzy on how root is accomplished on stock Marshmallow; it used to be we could flash SuperSu via recovery, but now there is talk about systemless...Anyway, I will reiterate what I was saying about Odin: DO NOT USE IT unless you know EXACTLY what you are doing. You have the potential to turn your phone into an expensive paperweight.
I am not trying to put you on blast or criticize you; I'm trying to help you avoid bricking your phone. There are a lot of things that could go wrong; you shouldn't be messing with something you don't understand, especially if you don't know how to fix it if something goes wrong.
Click to expand...
Click to collapse

Wonderful. Thanks man. I will be attempting a Stock ROM Odin flash and go from there. I will update my progress. Thank you all very much for the answered questions and pointing me in the right direction. Hopefully this thread will prove useful for anyone who is attempting to deal with a G920-T and attaining root the proper way for Marshmallow 6.x
danveer said:
For now even i am confused as to what is causing error.
Its probably that his storage is not curropt causing namd write fail..
I would recommend doing a backup since you can turn on a phone
Then downloading stock rom via sam mobile and do a clean install...if odin is not helping doing that then try smart switch.
Boot up system, see if everything is working..
After that follow the instructions as to flash twrp from the link i gave in one of my previous posts.. twrp should now flash...( i dont see any reason it shouldnt )
Flash root via recovery, or a custom rom you wanna flash vut make sure its a 6.0.1 one ( xtre sto lite or alexis recommended )
That should root your phone too...
Click to expand...
Click to collapse