Related
As it says in the title I've already unlocked and flashed several times (downloaded multiple versions of TWRP to see if it was just the download itself, as well as checking the MD5 to see if it was corrupt.) I flash it it gives the usual partition message when I go to boot recovery I just get a Bootup failed. Lost as to what to do from here. Trying to root my phone. My phone still works as I'm able to use it atm but I don't know what else to do.
It seems if I reboot, and try going into recovery then it doesn't give me a bootup failed message but I get the android icon where he fell over and has the red triangle coming out of his chest.
Dunno if this is part of the issue but my phone isn't being detected as a adb device either, and there's not ADB debugging option to enable under developer setting just usb debugging which is enable. The drivers are install so I know it's not a driver issue.
First off, sorry if this is the wrong section for this.
Basically, I tried rooting my phone (Galaxy S6 SM-G920T) using KingRoot, and it got to 20% and shut off. Now on boot I get "KERNAL IS NOT SEANDROID ENFORCING, CUSTOM BINARY BLOCKED BY FRP LOCK"
I'd appreciate if someone could let me know whether or not there is a fix for this.
Thanks.
Kingroot is not for the Tmobile variant. You need to download Odin onto your computer and flash TWRP and Unikernel (unikernel will root the phone).
I would suggest you restore your phone to factory status by downloading Samsung Kies software.
Once that completes then enable Developer options and turn on OEM and allow USB debugging.
Then once you've done that, use the Odin to root the device and install recovery.
https://www.youtube.com/watch?v=F7W-3yo89UI&feature=youtube_gdata_player
I've followed all of the steps from this guide: http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1
I've got to the end where I am running the code snippets to flash everything, but everything fails. The error stated is FAILED: remote failure. I am not sure if this is related to my developer options being turned off, but I think it might be.
Is there a way to turn developer options on while in fastboot mode or perhaps a way around this error? The reason I am stuck in the fastboot is because the boot image can't be validated, I am not at the fastboot by choice, haha.
No. If your recovery is still stock, flash the Android N Preview 1 OTA or an Android 6.0.1 OTA image from Google. One of those will restore your Nexus to operating condition, and from there you can try again. If your recovery is TWRP, flash a custom ROM.
Strephon Alkhalikoi said:
No. If your recovery is still stock, flash the Android N Preview 1 OTA or an Android 6.0.1 OTA image from Google. One of those will restore your Nexus to operating condition, and from there you can try again. If your recovery is TWRP, flash a custom ROM.
Click to expand...
Click to collapse
I apologize for my ignorance since this is all new to me, but could you explain a few things to me.
Is this what you're referring to when you say Android N Preview 1 OTA: 'https://developer.android.com/preview/download.html'
Secondly, in order to flash these, am I still following the steps I was before, or should I be following a new set of steps?
You don't need the N Preview anymore. Download your Android 6.0.1 image from the Google page and flash using the instructions given on that page.
I went to the page and followed the directions. Still doesn't work. The flash-all script reboots after the first two commands, which lock the phone. But even then, it is still giving the error FAILED:remote failure.
me too!
I seem to be having the exact same issue! i just bought a Nexus 6 online that wasn't booting, it would only show a green led when plugged in. so here I am doing everything I can think of to fix the issue but then I get hit with the "remote failure" when i try to oem unlock the bootloader! (and since the phone wont't boot i can't check the "unlock bootloader" box in the developer options) so yeah I am going to keep researching this but if anyone has any good ideas about to get around the bootloader being locked please jump right in.
anyways I may have deeper issues, the battery will not charge. i know this because when i load up the fastboot menu, which i have to do by holding the buttons while plugging it in, it should say battery charging but all it says is battery ok
I also can't load recovery because when im in the fastboot menu and i choose recovery the phone freezes and the green led comes back on... *sigh*
They have the full ota packages posted on Google site now you can and push through the stock recovery
Here just make sure you get the shame version
https://developers.google.com/android/nexus/ota#hammerhead
Sent from my Nexus 6 using XDA-Developers mobile app
I have the OTA. I also installed Wugs toolkit.
My phone is in fastboot mode due to the boot image not being able to be validated. I didn't voluntarily open up fastboot using the shortcut.
The phone is UNLOCKED until bootloader is rebooted, then it is LOCKED. If I click start, it becomes UNLOCKED again. Wug's toolkit tries to UNLOCK the phone even while the phone says it is UNLOCKED. I don't think the phone is actually UNLOCKED, however whenever it tells me it is UNLOCKED, I try to proceed with flashing and it gives me a remote failure message on each command.
The next thing I am going try is the drivers and Wug's toolkit has a driver option, so I will try that. Besides the drivers, any other ideas?
You seem to be inexperienced in rooting Android devices. If you aren't, I apologize for the assumption. However, you should learn how to use adb and fastboot without relying on the toolkit. Toolkits tend to hide diagnostic messages that adb and fastboot generate while running. This missing information makes solving problems much more difficult.
Strephon Alkhalikoi said:
You seem to be inexperienced in rooting Android devices. If you aren't, I apologize for the assumption. However, you should learn how to use adb and fastboot without relying on the toolkit. Toolkits tend to hide diagnostic messages that adb and fastboot generate while running. This missing information makes solving problems much more difficult.
Click to expand...
Click to collapse
I am inexperienced, I stated that earlier. I have check a bunch of different forum posts and a bunch of different guides. Nothing seems to be helping and it seems like such a simple problem, a boot image that can't be validated. I am not trying to do anything special with my phone, I am just trying to get it to work. I woke up and it was stuck in this 'AP Fastboot Flash Mode (Secure)' mode. It is very bare bones, not even similar to the screens within videos I have seen. One moment the phone says it's UNLOCKED, the next it's LOCKED.
You are the expert, I am not. I am merely following your directions and they don't seem to be working. I did some outside research, came to a toolkit. Toolkits are great for beginners, especially since they are UI built, are built by someone who knows the area of interest, which makes researching easier and more efficient, but on top of that, it seems to be getting me much farther than your advice, although nothing is successful at this moment.
Here is a little more context into my situation. My phone seems to be recognized by Fastboot, but not ADB (From what I found, fastboot will find devices in fastboot, and adb will find devices functioning normally, don't know how true that is.). In addition, my phone seems to switch from UNLOCKED TO LOCKED after reboots, but can become UNLOCKED again if I push ANY button. Every command I issue (i.e flash bootloader, flash radio, flash system, flash userdata) result in the message, FAILED:remote failure, which I am not sure how to avoid (I have googled, checked these forums, checked other forums and there doesn't seem to be much, if any documentation on the error), but I think it is related to the fact my developer options are turned OFF. My next course of action is to install new drivers (I checked my drivers which are said to be up to date, I also installed google USB driver through the sdk, but now I am going to look into an adb or universal driver?) and attempt to rerun everything successfully.
If you have any other ideas, or don't think its the drivers, feel free to bring it up.
As a couple of fellows said before, try this:
https://developers.google.com/android/nexus/ota
Flash a FULL OTA from the link above, not a factory image. To flash any OTA you don't need to be unlocked. I think you might be confusing the terms (with the OTA you don't have to flash anything using fastboot)
In the link there are the instructions, it's pretty straight forward and easy if you have the correct drivers installed.
OTA requires that u can startup into recovery, I cannot I can startup fastboot through key combo but when I go to select recovery the green led comes back on and the screen displaying the fastboot options remains static
I think the phone freezes because it does not appear to be able to use the battery. though there is a firm battery connection it will not charge or power on without being plugged in. maybe when I select recovery I can quickly unplug and replug the USB and maybe hold the power button to try to simulate a successful reboot.. idk just thinking aloud and working with what I got..
I also can not start in recovery mode and the OTA requires ADB, which isn't recognizing my device. I have also stated that I have followed those instructions, and nothing resulted from them, except the same messages I have been stating these last few posts.
I will try this first chance I get later tonight..
http://forum.xda-developers.com/nexus-6/help/solution-stuck-bootloop-locked-t3053783
Listen the ota doesn't get installed through fast boot, you have to select recovery through the fast boot then install the update by pushing it as bootloader does not need to be unlocked!
Sent from my Nexus 6 using XDA-Developers mobile app
holeindalip said:
Listen the ota doesn't get installed through fast boot, you have to select recovery through the fast boot then install the update by pushing it as bootloader does not need to be unlocked!
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Ok, well it seems we are at an impasse. You seem to think I can do something, so I am going to show some pictures of my screen. Its going to be blurry because I had to take it with my computer, so I apologize, but I will elaborate on each picture.
Qwertyismypw said:
Ok, well it seems we are at an impasse. You seem to think I can do something, so I am going to show some pictures of my screen. Its going to be blurry because I had to take it with my computer, so I apologize, but I will elaborate on each picture.
Click to expand...
Click to collapse
The first two pictures are when the phone is 'UNLOCKED'. The second two pictures are when the phone is 'LOCKED'. The moment I press anything in 'LOCKED' mode, the little android man goes away, and it becomes the first two pictures. WHENEVER I push a button in 'UNLOCKED' mode, nothing happens, except in the bootloader logs screen says, 'FAILED TO VALIDATE BOOT IMAGE RET -1'. I have done everything on that OTA page in every way possible. It has done me no good.
Ok, I made a little progress I think. Wugs toolkit allowed me to use TWRP on my phone and ADB is recognizing my phone now. There are a lot of options within TWRP though, so I am going to look through them all for anything relevant. Anything I should keep an extra eye out for?
If you can use twrp just download a custom ROM to your phone and move it over to SD card and flash it, then you will be able to boot and unlock the bootloader in developer ootions, that is your best bet, if you keep getting force closes after flashing a custom ROM your going to have to do a factory reset from within twrp
Sent from my Nexus 6 using XDA-Developers mobile app
holeindalip said:
If you can use twrp just download a custom ROM to your phone and move it over to SD card and flash it, then you will be able to boot and unlock the bootloader in developer ootions, that is your best bet, if you keep getting force closes after flashing a custom ROM your going to have to do a factory reset from within twrp
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't have an SD card, can I move it to the internal storage? And how exactly do I do this? I can't copy/paste anything into the phone (it says the phone doesn't actually exist, even though adb is recognizing it as in recovery) or do I sideload it? When I try to sideload it though, the device disappears (and device manager sees nexus 6 under other devices, but the driver isn't up to date and no drivers seem to work. I've tried the google usb driver with no luck.) and it won't allow me to sideload it.
Hello All,
Device always flashed with stock DT Germany firmware. A couple of months back I toggled OEM Unlocking (off-on-off) by mistake and next morning device reboots stating "Custom binary blocked by FRP Lock", single red line on top of screen, no other information.
I have tried to flash stock DT Germany firmware several times.Process through ODIN goes fine and completes successfully but phone reboots again in "Custom Binary blocked by FRP Lock".I can only access download mode, no other modes are available (not even recovery)
Below I have attached some screen shots of download mode and ODIN process.
https://drive.google.com/open?id=10aWMWozVCweBe3UTch9PBvvw6fboYjEQ
I have tried several combination files and all have failed.
I hope anyone has faced and sorted this out
Regards
are flashing the same firmware which was on you phone? If not then try the same firmware. Because that is the only reason i think is not resetting the FRP lock.
Munawar Mehmood said:
are flashing the same firmware which was on you phone? If not then try the same firmware. Because that is the only reason i think is not resetting the FRP lock.
Click to expand...
Click to collapse
Hello Munawar,thank you for your reply. I tried to flash same stock firmware which was on phone at the time and it failed with "sw rev check fail(bootloader) device 3 binary 2". I guess this happens because last night I flashed July 2019 stock firmware (ODIN passed it successfully) and bootloader does not allow an older version. I tried with February firmware, March firmware same problem.
What I have noticed is that if I uncheck auto-reboot (ODIN) and flash latest stock AP is passes successfully and on device (download mode) CURRENT BINARY states "Samsung Official" but when I try to reboot it goes back to 'Custom binary blocked by FRP Lock' and CURRENT BINARY switches back to CUSTOM.
besmirgogu said:
Hello Munawar,thank you for your reply. I tried to flash same stock firmware which was on phone at the time and it failed with "sw rev check fail(bootloader) device 3 binary 2". I guess this happens because last night I flashed July 2019 stock firmware (ODIN passed it successfully) and bootloader does not allow an older version. I tried with February firmware, March firmware same problem.
What I have noticed is that if I uncheck auto-reboot (ODIN) and flash latest stock AP is passes successfully and on device (download mode) CURRENT BINARY states "Samsung Official" but when I try to reboot it goes back to 'Custom binary blocked by FRP Lock' and CURRENT BINARY switches back to CUSTOM.
Click to expand...
Click to collapse
your device wasint logged out of google/samsung b4 reset.
dont know where or how you got it but thats what FRP lock is.. also regardless of if you think you flash the "same" firmware as phone was on, i suspect that you did in fact not know which FW it was on. because the message you are getting:
"sw rev check fail(bootloader) device 3 binary 2"
means you are flashing old firmware on a device which has a new bootloader than the one you are trying to flash.
all in all, searching on xda would have provided the information you are seeking.
now flash back stock firmware from July or August 2019.
bober10113 said:
your device wasint logged out of google/samsung b4 reset.
dont know where or how you got it but thats what FRP lock is.. also regardless of if you think you flash the "same" firmware as phone was on, i suspect that you did in fact not know which FW it was on. because the message you are getting:
"sw rev check fail(bootloader) device 3 binary 2"
means you are flashing old firmware on a device which has a new bootloader than the one you are trying to flash.
all in all, searching on xda would have provided the information you are seeking.
now flash back stock firmware from July or August 2019.
Click to expand...
Click to collapse
@bober10113, thank you for your explanation...
I have just tried to flash (again) the following stock firmware (DT Germany-July 2019)
AP_N960FXXS3CSFC_CL16141281_QB24489477_REV00_user_low_ship_meta_OS9.tar
BL_N960FXXS3CSFC_CL16141281_QB24489477_REV00_user_low_ship.tar
CP_N960FXXS3CSG1_CP13173080_CL16141281_QB24586509_REV00_user_low_ship.tar
CSC_OMC_ODX_N960FODX3CSF3_CL16070506_QB24108956_REV00_user_low_ship.tar
I did use Odin3 v3.13.3...
Behaviour is the same:
ODIN completes successfully and it claims PASS in green, device tries to reboot and throws black screen with "Custom binary blocked by FRP Lock"
I will try DT Germany-August 2019 or a SAMMOBILE August version as well but I would expect the same behavior as I have tried during all these months.
I also tried nand erase and Re-partition by extracing PIT file from CSC file above
if anything else comes to mind please let me know...
besmirgogu said:
@bober10113, thank you for your explanation...
I have just tried to flash (again) the following stock firmware (DT Germany-July 2019)
AP_N960FXXS3CSFC_CL16141281_QB24489477_REV00_user_low_ship_meta_OS9.tar
BL_N960FXXS3CSFC_CL16141281_QB24489477_REV00_user_low_ship.tar
CP_N960FXXS3CSG1_CP13173080_CL16141281_QB24586509_REV00_user_low_ship.tar
CSC_OMC_ODX_N960FODX3CSF3_CL16070506_QB24108956_REV00_user_low_ship.tar
I did use Odin3 v3.13.3...
Behaviour is the same:
ODIN completes successfully and it claims PASS in green, device tries to reboot and throws black screen with "Custom binary blocked by FRP Lock"
I will try DT Germany-August 2019 or a SAMMOBILE August version as well but I would expect the same behavior as I have tried during all these months.
I also tried nand erase and Re-partition by extracing PIT file from CSC file above
if anything else comes to mind please let me know...
Click to expand...
Click to collapse
why are your files named . tar?
i think your not even flashing anything. how long does it take to flash?
bober10113 said:
why are your files named . tar?
i think your not even flashing anything. how long does it take to flash?
Click to expand...
Click to collapse
actually files are in ".tar.md5" but I did not include this extension, I am sorry for the confusion.
last flash took around 4minutes
Should they be in another format?
besmirgogu said:
actually files are in ".tar.md5" but I did not include this extension, I am sorry for the confusion.
last flash took around 4minutes
Should they be in another format?
Click to expand...
Click to collapse
nah i was just wondering if they acctualy were real stock unaltered firmware files.
but anyways. that should have fixed it. so i dont know what to tell you. search around i guess
bober10113 said:
nah i was just wondering if they acctualy were real stock unaltered firmware files.
but anyways. that should have fixed it. so i dont know what to tell you. search around i guess
Click to expand...
Click to collapse
ok, thank you for your help...
well start from scratch.
clean your phone port with a tooth brush gently.
remove samsung drivers, then install latest samsung drivers again. and change usb port (version 2.0) and usb cable. because sometimes damage cable cause this issue. run odin as administrator (right click on odin icon and select run as administrator) and then select nand erase and pit file and flash latest stock firmware.
Munawar Mehmood said:
well start from scratch.
clean your phone port with a tooth brush gently.
remove samsung drivers, then install latest samsung drivers again. and change usb port (version 2.0) and usb cable. because sometimes damage cable cause this issue. run odin as administrator (right click on odin icon and select run as administrator) and then select nand erase and pit file and flash latest stock firmware.
Click to expand...
Click to collapse
I tried as per above guidelines. stock firmware flashed:
AP_N960FXXS3CSG5_CL16141281_QB25130720_REV00_user_low_ship_meta_OS9.tar.md5
BL_N960FXXS3CSG5_CL16141281_QB25130720_REV00_user_low_ship.tar.md5
CP_N960FXXS3CSG2_CP13219698_CL16141281_QB24670232_REV00_user_low_ship.tar.md5
CSC_OMC_OXM_N960FOXM3CSG3_CL16141281_QB24861261_REV00_user_low_ship.tar.md5
ODIN passed it successfully. Device in download mode says CURRENT BINARY: Custom and of course "Custom binary blocked by FRP lock"
besmirgogu said:
I tried as per above guidelines. stock firmware flashed:
AP_N960FXXS3CSG5_CL16141281_QB25130720_REV00_user_low_ship_meta_OS9.tar.md5
BL_N960FXXS3CSG5_CL16141281_QB25130720_REV00_user_low_ship.tar.md5
CP_N960FXXS3CSG2_CP13219698_CL16141281_QB24670232_REV00_user_low_ship.tar.md5
CSC_OMC_OXM_N960FOXM3CSG3_CL16141281_QB24861261_REV00_user_low_ship.tar.md5
ODIN passed it successfully. Device in download mode says CURRENT BINARY: Custom and of course "Custom binary blocked by FRP lock"
Click to expand...
Click to collapse
you are doing something wrong. as stock firmware is the only option to remove custom binary error. try someone else PC and data cable.
Munawar Mehmood said:
you are doing something wrong. as stock firmware is the only option to remove custom binary error. try someone else PC and data cable.
Click to expand...
Click to collapse
I am trying to understand which of the steps I am doing wrong. I managed to successfully flash a Galaxy Note 8 today so I know that laptop, cable and steps followed are fine.
What seems strange to me is that on this Galaxy Note 9 ODIN completes successfully in 2 min and 14 seconds but every time phone states CURRENT BINARY: Custom making me think that device is not being flashed at all. Any ideas how to confirm this?
Did you flash anything onto this device that would cause a "Custom" status? For one im not sure how you managed to even get a Custom Binary without setting the Warranty Bit. 2nd I noticed "Eng Mode: Dev Device" in Download Mode. And thirdly How do you manage to tick OEM Unlocking Off, On and then back Off accidentally? Changing the OEM Unlocking setting requires a Factory Reset each time.
last1youlove said:
Did you flash anything onto this device that would cause a "Custom" status? For one im not sure how you managed to even get a Custom Binary without setting the Warranty Bit. 2nd I noticed "Eng Mode: Dev Device" in Download Mode. And thirdly How do you manage to tick OEM Unlocking Off, On and then back Off accidentally? Changing the OEM Unlocking setting requires a Factory Reset each time.
Click to expand...
Click to collapse
I have never flashed anything other than stock DT firmware on this device (multiple times). It was never rooted...
It seems strange to me as well that Warranty bit is 0 while it says "Current Binary: Custom".
It says "Eng Mode: Dev Device" as this is a testing device that Samsung releases to its partners (mainly Telco Partners) for testing and development, so it never was a commercial unit for sale.
OEM Unlocking was off and I remember ticking it "on" by mistake as I did not intend to perform any flashing at the time. As I can recall I left it on and next morning phone reboots claiming "Custom binary blocked by FRP Lock". I would bet that I left it on but in download mode you can see that it says "OEM LOCK: ON" which I guess means "OEM UNLOCK: OFF".
besmirgogu said:
I have never flashed anything other than stock DT firmware on this device (multiple times). It was never rooted...
It seems strange to me as well that Warranty bit is 0 while it says "Current Binary: Custom".
It says "Eng Mode: Dev Device" as this is a testing device that Samsung releases to its partners (mainly Telco Partners) for testing and development, so it never was a commercial unit for sale.
OEM Unlocking was off and I remember ticking it "on" by mistake as I did not intend to perform any flashing at the time. As I can recall I left it on and next morning phone reboots claiming "Custom binary blocked by FRP Lock". I would bet that I left it on but in download mode you can see that it says "OEM LOCK: ON" which I guess means "OEM UNLOCK: OFF".
Click to expand...
Click to collapse
so this is the problem, you are flashing commercial firmware on testing device to rectify the custom lock. try flashing combination firmware. in this guide is a link to download combination firmware. it is official combination firmware to solve device problems.
Munawar Mehmood said:
so this is the problem, you are flashing commercial firmware on testing device to rectify the custom lock. try flashing combination firmware. in this guide is a link to download combination firmware. it is official combination firmware to solve device problems.
Click to expand...
Click to collapse
I managed to flash COMBINATION_FAC_FA81_N960FXXU3ASF1_BoxWares.tar.md5. Phone tries to reboot showing corrent model but on top of screen it says "Boot image signature check fail!!!" and "Reboot to avoid Warranty bit set!!!"
In download mode CURRENT BINARY:Custom and SYSTEM STATUS:Custom
I have added below a couple of screen shots of the situation now:
https://drive.google.com/open?id=1lwbblCDLKnvDkyBMtlsOOhH_F1c4HpeJ
i have once again gone through the entire thread and i see that you mention odin version 3.13.3, while the latest version of odin is 3.13.1. and i am using odin version 3.13.1. try this specific version of odin. and flash combination firmware. it seems from latest screen shot that your phone is not flashing any firmware. it just shows progress on pc but on phone it is not happening at all. try the odin version i mentioned.
My working theory is that because this is a testing device it's marking any firmware that isn't the specific engineering firmware the device shipped with as a "Custom Binary" you wouldn't be able to flash official releases. (Including Combination Firmware) You would probably need to return the device to the manufacturer or provider and request that the original operating system image be restored.
However please take this with a grain of salt. I'm not certain this is the case.
last1youlove said:
My working theory is that because this is a testing device it's marking any firmware that isn't the specific engineering firmware the device shipped with as a "Custom Binary" you wouldn't be able to flash official releases. (Including Combination Firmware) You would probably need to return the device to the manufacturer or provider and request that the original operating system image be restored.
However please take this with a grain of salt. I'm not certain this is the case.
Click to expand...
Click to collapse
you sir are making alot of sense.
Hi everyone,
I have retrieved a Samsung Tab 3.7.0 SM-T210. The OS was the old KitKat 4.4.2, very slow and buggy. I tried to flash a new recovery and OS and spent the 3 last days getting fails. I think I have read the all internet about this situation and would like to make a last try with your help.
When I got the tablet, I was surprised that in download mode it was indicated custom and custom binary and not official as it has not, I think, been flashed in the past by the people owning it. With HW rev 0x5 at the end.
The first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. After reading some people on forumes saying that this device might not have a locked bootloader, I finally thought that this tablet did not have its bootloader locked. Then I decided to go further with the flash of a TWRP recovery.
At the beginning the stock recovery was working. I am under archlinux, I have fastboot and heimdall. To do it as right as possible I installed a VM with Windows 10 and tried to flash a custom TWRP corresponding to the tablet with Odin. But the process got stuck at the SetupConnection step. I installed Windows 7 too, tried 5 different Windows OS, tried 4 different USB cables, reinstalled the USB drivers, tried 5 different Odin versions, tried different archives, just recoveries and all stock system. Still getting stuck at the SetupConnection.
I finally decided to try heimdall thinking that the VM could be the problem. With heimdall I run flash commands such as heimdall flash --RECOVERY twrp-3.2.3-0-lt02ltespr.img --no-reboot and got it doing something, the shell was saying it's 100% done and the tablet, in download mode, was showing a complete blue bar. Then, the recovery was just broken. Could not access it anymore, the Samsung Tab3 logo showing up and staying when trying to access it. I tried to flash some others archives, I opened it off and remove the battery for 5 minutes, still the same thing.
The operating system was still accessible and buggy, applications saying connection issues, etc. I did a factory reset from the running KitKat android OS and now have the Samsung Tab3 logo showing up and staying when trying to access it.
Now, I can only access the download mode and that's all. I have the impression that I am not the first one having these kind of trouble with this tablet. Is it a hardware issue on all these tablets ? Should I try something more advanced with heimdall, dd ?
Does someone have a solution in this situation ?
Thanks for your time and help.
I finally used heimdall and was able to flash all the partitions with the stock images. Now I am back in stock version. I would like to flash a TWRP recovery.
Can someone tell me if I have to unlock the bootloader with this device ? If it is, how can unlock it ? I can not find anything in the settings developer section, and can not use a call number input in order to enter a system code as it's a tablet. Do I have to wipe something from the stock recovery in order to see it ?
Thanks for your time.
Hi -yo-.
You don't need to do OEM unlock as this device is so old.
Also twrp-3.2.3-0-lt02ltespr.img is NOT for this device.
For recovery look from here and for ROM here.
Thanks jonezy82 for the answer. Indeed, I figured all of that out.
I decided to get it back stock and not trying to flash anything custom.
Thanks for your time.