I am still having hope I can recover my bricked Tab A. If there are any other suggestions than what I have tried, I would love to know!
I have attempted flashing, multiple times, stock ROMs, custom ROMs, stock boot and recovery files, CF Autoroot all unsuccessful at getting to boot.
:crying:
I can only boot into Download mode:
Product Name: SM-T580
FRP Lock: Off
System Status: Custom
Current Binary: Custom
Secure Download: Enabled
Warranty Void: 1 (0x0500)
AP SWREV: B:-1 K:1 S:2
I can flash the T580UEU4CRK5_T580XAR4CRK7_XAR AP and CSC Files but not the Bootloader curiously.
I can flash twrp-3.2.3-4-gtaxlwifi-OMNI6 but the device will not boot into Recovery Mode. (couintless attempts.)
I was hoping if I could get into TWRP then I could wipe the cache etc. but attempts have been fruitless.
I am all out of ideas.....
Flutterfly said:
I am still having hope I can recover my bricked Tab A. If there are any other suggestions than what I have tried, I would love to know!
I have attempted flashing, multiple times, stock ROMs, custom ROMs, stock boot and recovery files, CF Autoroot all unsuccessful at getting to boot.
:crying:
I can only boot into Download mode:
Product Name: SM-T580
FRP Lock: Off
System Status: Custom
Current Binary: Custom
Secure Download: Enabled
Warranty Void: 1 (0x0500)
AP SWREV: B:-1 K:1 S:2
I can flash the T580UEU4CRK5_T580XAR4CRK7_XAR AP and CSC Files but not the Bootloader curiously.
I can flash twrp-3.2.3-4-gtaxlwifi-OMNI6 but the device will not boot into Recovery Mode. (couintless attempts.)
I was hoping if I could get into TWRP then I could wipe the cache etc. but attempts have been fruitless.
I am all out of ideas.....
Click to expand...
Click to collapse
Try this thread https://forum.xda-developers.com/galaxy-tab-a/themes/mod-twrp-odin-t3650215 . And if you come to recovery do factory reset. Then reboot. Maybe help.
Thanks, I started reading this thread last night and attempted to download but the mirrors didn't work.
Download
[2x1]MOD_SM-T580XXU4CRK5_with_twrp-3.2.3-4-gtaxlwifi_and_patched_boot_with_disabled dm-verity, forced encryption disabled, Selinux permissive _without_CSC.zip
for the Samsung Galaxy Tab A 10.1 (2016)(SM-T585), by repey6
response: dc3.androidfilehost.com sent an invalid response.
Can you check the links? Thanks again!
Flutterfly said:
Thanks, I started reading this thread last night and attempted to download but the mirrors didn't work.
Download
[2x1]MOD_SM-T580XXU4CRK5_with_twrp-3.2.3-4-gtaxlwifi_and_patched_boot_with_disabled dm-verity, forced encryption disabled, Selinux permissive _without_CSC.zip
for the Samsung Galaxy Tab A 10.1 (2016)(SM-T585), by repey6
response: dc3.androidfilehost.com sent an invalid response.
Can you check the links? Thanks again!
Click to expand...
Click to collapse
Links work. Change your browser.
I use chrome, latest version/ any other suggestions? I can get your other links to download
Got it thank you! Stupid antivirus
Thanks Repey6 for your assistance, The device still will not flash a bootloader file. Any ideas what could be causing this failure or if it's fixable?
The process fails at the write phase "param.bin".
Flutterfly said:
Thanks Repey6 for your assistance, The device still will not flash a bootloader file. Any ideas what could be causing this failure or if it's fixable?
The process fails at the write phase "param.bin".
Click to expand...
Click to collapse
2nd entry at DuckDuckGo:
https://forum.xda-developers.com/galaxy-s3/help/odin-flash-sboot-bin-param-bin-nand-t3546535
Does flashing CF-AutoRoot succeed?
No,
virsys said:
2nd entry at DuckDuckGo:
https://forum.xda-developers.com/galaxy-s3/help/odin-flash-sboot-bin-param-bin-nand-t3546535
Does flashing CF-AutoRoot succeed?
Click to expand...
Click to collapse
When I tried autoroot, I get a PIT file error. and it fails.
Flutterfly said:
When I tried autoroot, I get a PIT file error. and it fails.
Click to expand...
Click to collapse
Providing screenshots of Odin's process in the different scenarios (flashing stock, custom, twrp, autoroot) / logs would help.
Could be a hardware damage as well. Then you will have to RMA it.
Flutterfly said:
Thanks Repey6 for your assistance, The device still will not flash a bootloader file. Any ideas what could be causing this failure or if it's fixable?
The process fails at the write phase "param.bin".
Click to expand...
Click to collapse
Your device is showing a bootloader revision of -1.
This is incorrect. Which is why you're having issues flashing any boot loader.
Something similar happened to another member who ended up with a rev -2 bootloader and had similar issues on another device.
He managed to fix it after some messing and got it booting again.
If I find the thread I'll post it.
https://forum.xda-developers.com/galaxy-tab-a/help/help-tab-t380-oreo-flashing-t3857266
This is what I have done before successfully with a different Samsung Galaxy Tablet and I unbricked that particular tablet. I used Kies to restore the original stock ROM to the tablet and I re-rooted it by using Odin and flashed the correct TWRP to the tablet. If you can get TWRP to work on anything I'd have to say that your technically rooted even without Supersu or Magisk.
Related
My girlfriend has been having S4 issues in the past such as random restarts and application issues probably related to a ROM issue. Her phone IS rooted. While I was at work, she went to my floormate for advice and he, who also has an I337M S4, suggested she reflash a ROM. Things went well according to him (i.e. no ODIN issues) and I trust him since he has been messing with these things for a while; however, now her phone will not boot past the Samsung logo. It won't reliably go past the simple "Samsung Galaxy S4" white-and-black splash screen and when it does it fails to progress to actually being on. I CAN reliably get the phone into download mode and CAN flash ROMs using ODIN; however, I have no idea how to fix this issue. :/ I have access to any necessary S4 files (such as the PIT file) from my floormate.
Since I can't get anything more useful than download mode, here's the information from that:
Product: SGH-I337M
Binary: Samsung Official
Status: Custom
Knox Lock: 0x0
Knox Warranty Void: 0x1
USB-Config-LSD: 0x30
Write Protection: Enable
MMC Burst Mode: Enable
I apologise if any of that isn't quite right as she has a crack in the top left of her phone that makes it very hard to read.
Thanks in advance,
Jacob
wethestill said:
My girlfriend has been having S4 issues in the past such as random restarts and application issues probably related to a ROM issue. Her phone IS rooted. While I was at work, she went to my floormate for advice and he, who also has an I337M S4, suggested she reflash a ROM. Things went well according to him (i.e. no ODIN issues) and I trust him since he has been messing with these things for a while; however, now her phone will not boot past the Samsung logo. It won't reliably go past the simple "Samsung Galaxy S4" white-and-black splash screen and when it does it fails to progress to actually being on. I CAN reliably get the phone into download mode and CAN flash ROMs using ODIN; however, I have no idea how to fix this issue. :/ I have access to any necessary S4 files (such as the PIT file) from my floormate.
Since I can't get anything more useful than download mode, here's the information from that:
Product: SGH-I337M
Binary: Samsung Official
Status: Custom
Knox Lock: 0x0
Knox Warranty Void: 0x1
USB-Config-LSD: 0x30
Write Protection: Enable
MMC Burst Mode: Enable
I apologise if any of that isn't quite right as she has a crack in the top left of her phone that makes it very hard to read.
Thanks in advance,
Jacob
Click to expand...
Click to collapse
Just boot into recovery and do a factory reset
Sent from my SAMSUNG-SGH-I727
jd1639 said:
Just boot into recovery and do a factory reset
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
I can't reliably get into recovery; however, I have done a factory reset on one of the times I was able to do so. This didn't fix the issue.
wethestill said:
I can't reliably get into recovery; however, I have done a factory reset on one of the times I was able to do so. This didn't fix the issue.
Click to expand...
Click to collapse
Custom roms are typically flashed through a custom recovery.. trwp, cwm, phils..... stock roms are flashed through odin.... 2 ways you can go here... flash custom recovery ( tripping knox btw) or download a stock rom from sam mobile.... making sure you get the right one of course.... and flash it through odin... sounds like currently you have a bad flash.......
Gage_Hero said:
Custom roms are typically flashed through a custom recovery.. trwp, cwm, phils..... stock roms are flashed through odin.... 2 ways you can go here... flash custom recovery ( tripping knox btw) or download a stock rom from sam mobile.... making sure you get the right one of course.... and flash it through odin... sounds like currently you have a bad flash.......
Click to expand...
Click to collapse
Sorry, I should have specified. What "Passed" on Odin is a stock ROM or at least it should be. I'm just trying to get the phone to a bootable state and am unconcerned with the end resulting ROM. Do you have a link to a recommended ROM that won't take an entire day to download?
wethestill said:
Sorry, I should have specified. What "Passed" on Odin is a stock ROM or at least it should be. I'm just trying to get the phone to a bootable state and am unconcerned with the end resulting ROM. Do you have a link to a recommended ROM that won't take an entire day to download?
Click to expand...
Click to collapse
If your coming from 4.3 there are a number of good roms... unfortunately they are all around 1.2 to 1.4 GB so if you have a slow connection it will take a while... I run Danvh's 4.4 http://forum.xda-developers.com/showthread.php?t=2537495 , there is also this one that people seem to like but I haven't tried it.... http://forum.xda-developers.com/showthread.php?t=2375180 you will need a custom recovery.... both of these suggest twrp.... I flashed with 2.6... 2.7 is out now and I don't know how it reacts but you will need a custom revovery to flash the zip file....
I guess the issue is you have to restore to stock via odin but you don't know what version bootloader you have? Guess you'll have to use samsung tool which will probably install knox?
Can you install custom recovery via odin?
Try with the new 4.4 files
sent from my mobile device
Knox is already tripped. I'd go into recovery, do a factory restore again and then plug it into the computer and do a restore with Kies.
Sent from my SGH-I337M using Tapatalk
Hey guys,
I'm a noobie to flashing my phone and have attempted to do so, with no success and now my device is bricked.....so i'm looking for a handout here before I totally give up and see if the local Verizon store will help me at this point.....
Here's the story,
I attempted to installed a custom ROM using Safe strap, but couldn't get it to take. So, I then decided I no longer wanted my phone rooted. Downloaded an MD5 file, and used ODIN to attempt to flash it back to stock. Hit start in ODIN, then immediately got an error message, and now my phone only says that a firmware installation has failed and use the backup program.
Ok, so I tried downloading the MD5 file again and still have the same results. I keep getting the following screen when I attempt to flash it via ODIN on my phone:
ODIN MODE
Product Name: SM-N900V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: OxO
KNOX WARRANTY VOID: Ox1
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, A1, A3, P1
WRITE PROTECTION: Enable
UDC START
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 1
So I have no idea what i've done here by poking at it......and have no idea what to do now besides crawl for help and ask for forgiveness at Verizon.....
I'm currently downloading the latest MD5 file from Sammobile.com in a last attempt. The previous MD5 files were obtained via other sites.
Again, any help is appreciated.....
moparman20 said:
Hey guys,
I'm a noobie to flashing my phone and have attempted to do so, with no success and now my device is bricked.....so i'm looking for a handout here before I totally give up and see if the local Verizon store will help me at this point.....
Here's the story,
I attempted to installed a custom ROM using Safe strap, but couldn't get it to take. So, I then decided I no longer wanted my phone rooted. Downloaded an MD5 file, and used ODIN to attempt to flash it back to stock. Hit start in ODIN, then immediately got an error message, and now my phone only says that a firmware installation has failed and use the backup program.
Ok, so I tried downloading the MD5 file again and still have the same results. I keep getting the following screen when I attempt to flash it via ODIN on my phone:
ODIN MODE
Product Name: SM-N900V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: OxO
KNOX WARRANTY VOID: Ox1
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, A1, A3, P1
WRITE PROTECTION: Enable
UDC START
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 1
So I have no idea what i've done here by poking at it......and have no idea what to do now besides crawl for help and ask for forgiveness at Verizon.....
I'm currently downloading the latest MD5 file from Sammobile.com in a last attempt. The previous MD5 files were obtained via other sites.
Again, any help is appreciated.....
Click to expand...
Click to collapse
You tried downgrading your bootloader. Flash your latest if you can find it.
Thank you for the help!
Is there any possibility I could ask for some help as to where to find the bootloader file? I'm assuming you find and download the file, then add it under the BL box in ODIN, in addition to checking the [Phone Bootloader Update] box?
Again, thank you for the help, I have no idea what to do next other than what you have helped with......and no phone now due to my own incompetence.....
moparman20 said:
Thank you for the help!
Is there any possibility I could ask for some help as to where to find the bootloader file? I'm assuming you find and download the file, then add it under the BL box in ODIN, in addition to checking the [Phone Bootloader Update] box?
Again, thank you for the help, I have no idea what to do next other than what you have helped with......and no phone now due to my own incompetence.....
Click to expand...
Click to collapse
If you have the N900V firmware file to upgrade to, the bootloader will automatically be flashed in the PDA all-in-one file. No firmware comes without a bootloader already inside.
Just flash the latest firmware using Odin (if you can) and then everything will be flashed as a new system except your data which may remain.
nicholaschum said:
If you have the N900V firmware file to upgrade to, the bootloader will automatically be flashed in the PDA all-in-one file. No firmware comes without a bootloader already inside.
Just flash the latest firmware using Odin (if you can) and then everything will be flashed as a new system except your data which may remain.
Click to expand...
Click to collapse
Got it. So, most likely what's happening is the MD5 (Frimware file) i'm trying to flash has an older bootloader than what's already on the phone, so i'm getting the error message telling me this. In essence, the phone is telling me i'm trying to downgrade and not allowing it.
I have located a new Frimware file via sammobile.com by typing in my model number (N900V) and the date was April 2014 for the file. Hopefully this is the right one, otherwise, I have no idea what to do next......as this is the latest file I can find by my limited experience/means.
So, once the download completes (not a paid member on sammobile) in about an hour, i'll give it a shot via ODIN and hopefully it works this time.
I will keep this thread updated as to the success/failure. Again, thank you for the help.......I have no idea what to do at this point other than take it in to the store and get scolded by them. Hopefully this MD5 file from sammobile is the right one
moparman20 said:
Got it. So, most likely what's happening is the MD5 (Frimware file) i'm trying to flash has an older bootloader than what's already on the phone, so i'm getting the error message telling me this. In essence, the phone is telling me i'm trying to downgrade and not allowing it.
I have located a new Frimware file via sammobile.com by typing in my model number (N900V) and the date was April 2014 for the file. Hopefully this is the right one, otherwise, I have no idea what to do next......as this is the latest file I can find by my limited experience/means.
So, once the download completes (not a paid member on sammobile) in about an hour, i'll give it a shot via ODIN and hopefully it works this time.
I will keep this thread updated as to the success/failure. Again, thank you for the help.......I have no idea what to do at this point other than take it in to the store and get scolded by them. Hopefully this MD5 file from sammobile is the right one
Click to expand...
Click to collapse
The MD5 single file should be the AIO file that you only need to flash through AP, and it will handle everything by itself.
The file from sammobile.com flashed perfect! I have a phone again, thank you so much! I see my KNOX counter is still set to 0x1, I assume that will always indicate it has been tampered with?
moparman20 said:
The file from sammobile.com flashed perfect! I have a phone again, thank you so much! I see my KNOX counter is still set to 0x1, I assume that will always indicate it has been tampered with?
Click to expand...
Click to collapse
Yeah KNOX 0x1 is permanent. No problem, next time just use the Thanks button!
please help. I had wifi on last night at home, i saw att pushed through an update but I couldn't stop it. it says updating management files.
when the phone tried to reboot, I got stuck on
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X0
CSB-CONFIG-LSB: 0X30
WRITE PROTECTION ENABLE
EMMC BURST MODE ENABLED
Downloading... do not turn off target!! screen
please help, what should i do now?
I take it that it won't reboot now? Do you know what firmware version you were on before the ota update?
Sent from my Nexus 5 using XDA Free mobile app
hotwell said:
please help. I had wifi on last night at home, i saw att pushed through an update but I couldn't stop it. it says updating management files.
when the phone tried to reboot, I got stuck on
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X0
CSB-CONFIG-LSB: 0X30
WRITE PROTECTION ENABLE
EMMC BURST MODE ENABLED
Downloading... do not turn off target!! screen
please help, what should i do now?
Click to expand...
Click to collapse
Is there a blue bar on the bottom?
Download Odin and choose a package from
http://forum.xda-developers.com/showthread.php?t=2616221
I would choose NB1 tr rootable version
http://forum.xda-developers.com/showthread.php?t=2674223
Reflash your firmware, you will loose all data but hey, your phone will work again
autonomousperson said:
Download Odin and choose a package from
http://forum.xda-developers.com/showthread.php?t=2616221
I would choose NB1 tr rootable version
http://forum.xda-developers.com/showthread.php?t=2674223
Reflash your firmware, you will loose all data but hey, your phone will work again
Click to expand...
Click to collapse
You're probably right. But are you sure he's not on mdl firmware? It would really suck if he is and he updated to nb1
Sent from my Nexus 5 using XDA Free mobile app
True, I guess he can just restore to MDL firmware...
He was in the middle of a update so I was just assuming that the BL is already locked
i don't remember the firmware. it was rooted with towelroot. it gets stucked with the screen that says downloading, do not turn off. no loading bar.
Just do a factory restore with odin... You will loose all your data! But I dont see any other way unless you have a unlocked bl and a custom recovery.
autonomousperson said:
Download Odin and choose a package from
http://forum.xda-developers.com/showthread.php?t=2616221
I would choose NB1 tr rootable version
http://forum.xda-developers.com/showthread.php?t=2674223
Reflash your firmware, you will loose all data but hey, your phone will work again
Click to expand...
Click to collapse
i tried to recovery with odin nb1 tr rootable version. when everything was completed, it says failed. on the screen, i see a msg telling me to get on recovery mode and connect to kies for recovery. I connected to kies, nothing can be detected... help please
finally got it to work! after i ran nb1 tr rootable version, it failed, then i did more digging and ran pit from this thread! http://forum.xda-developers.com/showthread.php?t=2404970
got it to work!
I guess your partitions were messed up if you needed to flash a pit file to fix it
autonomousperson said:
I guess your partitions were messed up if you needed to flash a pit file to fix it
Click to expand...
Click to collapse
before i flashed pit, i tried to flash stock firmware as suggested. no go. then flashed pit, it booted. root was removed. samsung keyboard failed to load. i tried to flash the stock firmware again but it still crash and failed to boot. i had to flash pit again... help please!!!
hotwell said:
before i flashed pit, i tried to flash stock firmware as suggested. no go. then flashed pit, it booted. root was removed. samsung keyboard failed to load. i tried to flash the stock firmware again but it still crash and failed to boot. i had to flash pit again... help please!!!
Click to expand...
Click to collapse
Did you try to root it afterwards? I thought you got it to work. What did you do to kill it?
autonomousperson said:
Did you try to root it afterwards? I thought you got it to work. What did you do to kill it?
Click to expand...
Click to collapse
omg! finally flashed stock firmware!!! my oem cable was bad!!!!! I used another cable!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! took me a whole week before I had time to fix this bs! thank you everyone for your supports!
Haha I was just about to suggest that.. You have no idea how many times ive flipped tables trying to figure out what drivers are not working when it was the cable all along
I have a verizon sgh-i545 running lollipop 5.1 which I rooted using kingroot. After rooting, I attempted to install philz touch recovery so I could flash a custom rom onto the phone.
I downloaded the newest philz touch for my particular model, but when I tried installing it the phone rebooted and displays a message stating "Software Update Failed" and it suggests using the Verizon software assistant to repair the device. At this screen at the top left, the following is displayed:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK: OFF
CSB-CONFIG-LS8: 0x30
SECURE DOWNLOAD: ENABLE
WRITE PROTECTION: ENABLE
EMMC BURST MODE: ENABLED
I tried flashing the stock rom onto the phone using odin because I saw someone had some success doing this.
When I try flashing the rom using odin, the program finishes flashing but displays there was an error and that the flashing attempt failed.
Am I able to use adb to obtain detailed information to help identify the problem while the phone is in this state?
talpamon said:
I have a verizon sgh-i545 running lollipop 5.1 which I rooted using kingroot. After rooting, I attempted to install philz touch recovery so I could flash a custom rom onto the phone.
I downloaded the newest philz touch for my particular model, but when I tried installing it the phone rebooted and displays a message stating "Software Update Failed" and it suggests using the Verizon software assistant to repair the device. At this screen at the top left, the following is displayed:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK: OFF
CSB-CONFIG-LS8: 0x30
SECURE DOWNLOAD: ENABLE
WRITE PROTECTION: ENABLE
EMMC BURST MODE: ENABLED
I tried flashing the stock rom onto the phone using odin because I saw someone had some success doing this.
When I try flashing the rom using odin, the program finishes flashing but displays there was an error and that the flashing attempt failed.
Am I able to use adb to obtain detailed information to help identify the problem while the phone is in this state?
Click to expand...
Click to collapse
Use a different usb port /differen usb cable.
Lennyz1988 said:
Use a different usb port /differen usb cable.
Click to expand...
Click to collapse
I have used multiple cables, including the one the that came with the phone. I read on a similar thread that the problem could possibly be related to the fact that write protection is enabled, but I am not certain as to the accuracy of this claim or how to go about disabling write protection.
talpamon said:
I have used multiple cables, including the one the that came with the phone. I read on a similar thread that the problem could possibly be related to the fact that write protection is enabled, but I am not certain as to the accuracy of this claim or how to go about disabling write protection.
Click to expand...
Click to collapse
You got a Verzion phone. Verizon sucks. They lock the bootloader so you cannot flash a custom recovery. That's why you got all that trouble.
Here is the section for your device.
http://forum.xda-developers.com/galaxy-s4-verizon
You cannot downgrade your firmware so make sure to flash the right one. Keep in mind that you shouldn't flash the latest firmware because that firmware cannot be rooted.
Lennyz1988 said:
You got a Verzion phone. Verizon sucks. They lock the bootloader so you cannot flash a custom recovery. That's why you got all that trouble.
Here is the section for your device.
http://forum.xda-developers.com/galaxy-s4-verizon
You cannot downgrade your firmware so make sure to flash the right one. Keep in mind that you shouldn't flash the latest firmware because that firmware cannot be rooted.
Click to expand...
Click to collapse
Thanks for the advice! =)
Hi I've been trying to root my S5 on Marshmallow 6.0.1 with little success. Having tried more than several times with Odin 3 as instructed in several guides, but all I've managed to achieve is a the addition of a boot message indicating that I've tripped KNOX; TWRP and ROM Manager tell me I'm not root!
I've rooted earlier versions of the Galaxy S, but to be fair I'm a little out of the loop. Could some kind soul help me out?
Uncheck "Auto Reboot" in ODIN
Copy SuperSU 2.71 beta to your phone/SD
Code:
https://mega.nz/#!2N4kECQb!Tjj5Q1VcQMU7TJ83MaTrtzdUeZsXBPZqgAtyl4qDXD8
Flash TWRP 3.0.0.0 or 3.0.2.0 with ODIN 3.10.7 (Newer versions of TWRP are broken)
TWRP 3.0.2.0
Code:
https://dl.twrp.me/klte/twrp-3.0.2-0-klte.img.tar.html
ODIN 3.10.7
Code:
https://mega.nz/#!vcIGmBTQ!Yr00OrGvUslQouU9E-zPf4SmpyVwL7mwIjeSG-0EAZg
When it's finished flashing, disconnect USB and pull the battery to power off
Replace battery and Boot immediately into TWRP and flash SuperSU
Reboot (Say no to any offer of rooting by TWRP if asked after already flashing manually)
*Detection* said:
Uncheck "Auto Reboot" in ODIN
Copy SuperSU 2.71 beta to your phone/SD
Code:
https://mega.nz/#!2N4kECQb!Tjj5Q1VcQMU7TJ83MaTrtzdUeZsXBPZqgAtyl4qDXD8
Flash TWRP 3.0.0.0 or 3.0.2.0 with ODIN 3.10.7 (Newer versions of TWRP are broken)
TWRP 3.0.2.0
Code:
https://dl.twrp.me/klte/twrp-3.0.2-0-klte.img.tar.html
ODIN 3.10.7
Code:
https://mega.nz/#!vcIGmBTQ!Yr00OrGvUslQouU9E-zPf4SmpyVwL7mwIjeSG-0EAZg
When it's finished flashing, disconnect USB and pull the battery to power off
Replace battery and Boot immediately into TWRP and flash SuperSU
Reboot (Say no to any offer of rooting by TWRP if asked after already flashing manually)
Click to expand...
Click to collapse
Hi Detection, thanks for the advice and links. I've done as instructed but still no root!
Installing SuperSu from the Play store reports no SU binary installed, if that helps.
Any advice?
Try again, that is the exact method myself and many others with G900F use, and it works fine
Double check it does say it is a G900F in download mode
List exactly what ODIN says after the flash, and what happens after the flash and you try booting into recovery
Just saying "Still no root" isn't explaining much
*Detection* said:
Try again, that is the exact method myself and many others with G900F use, and it works fine
Double check it does say it is a G900F in download mode
List exactly what ODIN says after the flash, and what happens after the flash and you try booting into recovery
Just saying "Still no root" isn't explaining much
Click to expand...
Click to collapse
My apologies, for not being particularly verbose. I shall try again and report more detailed results. I am very appreciative of your help!
sawest said:
Hi Detection, thanks for the advice and links. I've done as instructed but still no root!
Installing SuperSu from the Play store reports no SU binary installed, if that helps.
Any advice?
Click to expand...
Click to collapse
Don't add steps I haven't listed, no need to install anything from the play store, remove what you installed and follow the steps to a T
*Detection* said:
Try again, that is the exact method myself and many others with G900F use, and it works fine
Double check it does say it is a G900F in download mode
List exactly what ODIN says after the flash, and what happens after the flash and you try booting into recovery
Just saying "Still no root" isn't explaining much
Click to expand...
Click to collapse
In Download Mode it currently states:
ODIN MODE
PRODUCT NAME: SM-G900F
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, R1, A1, P1
SECURE DOWNLOAD : ENABLE
UDC START
However, upon flashing the zip file, TWRP reports "Failed to mount 'data' invalid argument"! In red, perhaps this is the reason I'm failing. Possibly it is because the internal storage was encrypted, though I though that I had unencrypted it already.
*Edit: After I had performed all of the steps, exactly as described, I tried some apps to check if I had root that is all.
Sounds like the encryption is causing the problem then, try TWRP 3.0.0.0 instead too
Otherwise factory reset and don't encrypt, then root
*Detection* said:
Sounds like the encryption is causing the problem then, try TWRP 3.0.0.0 instead too
Otherwise factory reset and don't encrypt, then root
Click to expand...
Click to collapse
Thanks, yes I had forgotten that encryption was irreversible. I wondered why removing the backup password seemed to 'unencrypt' the device a bit quickly DOH!
OK, so as I have already installed the TWRP custom recovery mode , I assume that a hard reset to factory defaults is going to be a little more involved. I'll give the earlier revision of TWRP a try first and see where that leaves me.
Once again thanks for your help and bearing with my stupidity.
Should be able to just factory reset from TWRP
Or from phone settings, and if it replaces recovery with stock, flash TWRP again
*Detection* said:
Should be able to just factory reset from TWRP
Or from phone settings, and if it replaces recovery with stock, flash TWRP again
Click to expand...
Click to collapse
No joy with either the earlier revision of TWRP, or a factory reset from the phone settings.
The phones factory reset boots me into TWRP and returns errors relating to can't mount '/data'. I also tried by recreating my initial phone backup password to see if that would help.
I'm stuck now, can't go forward and can't go back!
Any ideas on how I can proceed please?
Flash 6.0.1 stock ROM from sammobile .com with ODIN
Boot into recovery
Factory reset
Flash TWRP
Flash SuperSU