Hi Guys I flashed over to the stock firmware and then rooted it in order to use triangleaway.
initial binary count was 3 when I checked after using Triangleaway.
I used triangleaway but it is still showing as binary count 1.
What am I doing rom?
Using stock Telstra 4.1.1 firmware.
Did it come with a binary count with 1 for Telstra phones?
Any assistance would be great. This is for warranty purposes.
use TA, and then flash a stock rom before it reboots, then factory reset from recovery.
you have to be stock in every way for it to be zero
After I use TA. It gives me two options to reboot into download mode or for a normal reboot. Which do I select? Thanks
reboot to download mode and flash a stock rom. factory reset from recovery afterwards. there are plenty of guides to assist you
Thanks figured it out.
Selected Reboot in Download mode after TA. As soon as it went to reboot and screen went back I pulled out the battery. Booted it up manually to the Download Mode and it is now displaying "NO" or "0"
It's due to custom kernel, it must have stock one to reset counter
you're welcome
hi guys,
I'm a complete noob to all this but i have read through the q and a section and the noob guide to rooting.
I am running 4.3 on a 19305 and attempted to flash with odin 3.09.
i first tried flashing with CF-Auto-Root-m3-m3zh-gti9305.tar
and later recovery-cwmtouch-6.0.4.7-i9305
both times ive got the pass message on odin but when i check root status with root checker it says no access.
since i tried to flash i now get what i think are Knox alerts telling me its blocking things that are trying to access root or something.
i've tried copying supersu on to my sd card and installing from there and that hasn't helped.
If i put my phone in to download mode now this is what i see,
Odin mode
Product name GT-19305
Custom Binary Download: yes (6 count)
Current Binary: custom
Knox warranty void: 1
AP SWREV: AR
Can anyone tell me what to try next
thanks guys
When you flash cf auto root and you go to Play Store, do you see un update available of SuperSu? If yes, update and open SuperSu app to disable Knox.
Once you have flashed CF-Auto-Root-m3-m3zh-gti9305.tar re-boot.
Then download SU from the Google Play and install then reboot again, Root should then be ready...
I went to supersu in the play store and it only gave me the option to open it.
I tried un uninstalling the updates and re installing and rebooting.
I'm still getting this though
SOLVED
THANKS for everyone's help! ,
I booted in to recovery mode and installed the supersu zip file and then rebooted.
Loaded up supersu and this time it worked. It asked if I wanted to uninstall knox which I did.
I checked with root checker and I now have root'
Heaps happy
I would like to know if there is a way to completely remove root and CMW recovery, so i can flash the original ROM and send my device to warranty. Is that possible? Make everything looks original like it was when i bought the phone leaving no tracks of roots and flashs?
Well, i was able to reinstall the stock recovery extracting the recovery.img from the stock rom, converting it to md5 and flashing with Odin.
For the counter i used the app called triangle away, and it reset the counter to 0.
The root was removed with the "Remove all root" option on supersu config, the supersu app was removed from device, but the root permition persists, and the SE Linux status is Permissive.
How i can remove the root permission completely and make SE LInux status Enforcing so i can finally send my device to warranty?
frytec said:
Well, i was able to reinstall the stock recovery extracting the recovery.img from the stock rom, converting it to md5 and flashing with Odin.
For the counter i used the app called triangle away, and it reset the counter to 0.
The root was removed with the "Remove all root" option on supersu config, the supersu app was removed from device, but the root permition persists, and the SE Linux status is Permissive.
How i can remove the root permission completely and make SE LInux status Enforcing so i can finally send my device to warranty?
Click to expand...
Click to collapse
Have you tried flashing a stock ROM? That should wipe everything and return you to stock.
Devo7v said:
Have you tried flashing a stock ROM? That should wipe everything and return you to stock.
Click to expand...
Click to collapse
Yes. But im getting some red errors on stock recovery after flashing the stock rom via odin.
I took a picture of the recovery screen, can you guys please help me?
I need to send device to warranty but i cant send it with that bugged recovery.
I think these errors are related to some CWM recovery trash left behind.
This is really strange.
I attached a picture of the recovery screen, please check it!
i found this code: http://code.metager.de/source/xref/android/4.2/bootable/recovery/screen_ui.cpp
i dont know maybe it explain that missing bitmap erros.
Can someone take a look at it pls?
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