[Recovery][SM-T580][SM-T585][Official TWRP for Galaxy Tab A 10.1] - Samsung Galaxy Tab A series ROMs, Kernels, Recover

Official TWRP for Galaxy Tab A 10.1
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
How to Flash TWRP Recovery
Download the latest version of Odin and the Samsung USB drivers
Enable OEM unlock:
Go to Settings » About phone » and tap Build number seven times to enable Developer options.
Go back to main Settings page, scroll to bottom and select Developer options from there.
Under Developer options, look for Enable OEM unlock checkbox/toggle and enable it.
Boot your device into Download mode:
Switch off your device.
Press and hold “Home + Power + Volume down” buttons for a few seconds until you see a warning screen.
Press Volume Up on the warning screen to accept it and boot into Download mode.
Flash TWRP with Odin
Once your device is in download mode, connect it to the PC with a USB cable. The Odin window on PC should detect the device and show an “Added!!” message.
Now click on the AP tab on Odin window and select the TWRP recovery .tar file that you downloaded for your device.
Click the Start button on Odin and wait for it to finish the process. Once it has finished successfully, you’ll see a pass message on the Odin screen.
Your device will automatically reboot when Odin is done flashing. You can then disconnect your device.
How to boot TWRP Recovery
Switch off your device.
Press and hold “Home + Power + Volume Up” buttons for a few seconds and as soon as you see your device’ logo on-screen, release three buttons altogether. Your device will boot into TWRP recovery.
Downloads:
SM-T580
SM-T585

reserved

reserved too

Hi
Is there any advantage of installing the 3.3.1 recovery I have 3.2.1 recovery version installed at the moment
Thanks

terrorbite1492 said:
Hi
Is there any advantage of installing the 3.3.1 recovery I have 3.2.1 recovery version installed at the moment
Thanks
Click to expand...
Click to collapse
There has been a lot of changes and fixes. You can look at them here https://twrp.me/ . I would always recommend using the latest version.

Having a bit of trouble with the drivers I believe, I keep getting device unrecognized in Windows, tried two different machines, same issue. Any idea what is wrong?
I am getting the same when in recovery mode and in normal Android OS.
I am not getting the popup that says Use USB to transfer files etc, it just says slow charging.
Error is Uknown USB Device (Device Descriptor Request Failed)

sd_dracula said:
Having a bit of trouble with the drivers I believe, I keep getting device unrecognized in Windows, tried two different machines, same issue. Any idea what is wrong?
I am getting the same when in recovery mode and in normal Android OS.
I am not getting the popup that says Use USB to transfer files etc, it just says slow charging.
Error is Uknown USB Device (Device Descriptor Request Failed)
Click to expand...
Click to collapse
Install device drivers and adb/fastboot ones. Search here on XDA, I'm sure you'll find them :good:

Nimueh said:
Install device drivers and adb/fastboot ones. Search here on XDA, I'm sure you'll find them :good:
Click to expand...
Click to collapse
I have installed the ones linked at the top of this post. Is that the reason why is happening?
Is it not strange that when I am not in recovery and just booted to normal android and try to connect to my PC it also happens?
Hooked up my Samsung phone and Odin picked it up instantly - thinking the usb port on the table is gone and is only charging now. If that happened there is no way to TWRP without it right?
I'll look for those drivers thanks.

sd_dracula said:
I have installed the ones linked at the top of this post. Is that the reason why is happening?
Is it not strange that when I am not in recovery and just booted to normal android and try to connect to my PC it also happens?
Hooked up my Samsung phone and Odin picked it up instantly - thinking the usb port on the table is gone and is only charging now. If that happened there is no way to TWRP without it right?
I'll look for those drivers thanks.
Click to expand...
Click to collapse
Try these drivers and let me now if they fix your problem.
https://drive.google.com/open?id=1fjPf4m7XXmj2qIj4IO9_AO4LYYZfZnfG
Also you can try cleaning your usb port with a small piece of plastic or a pin. They can get packed with dirt sometimes. Also try a different cable.

Tried them too but it looks like the usb port is damaged and needs replacing

Got my usb port fixed, OEM unlock in dev mode, ran odin along with the twrp-3.3.1-1-gtaxlwifi.img.tar file but it doesn't seem to work. Tried twice and this is what I get after powering on with Power + Home + Up Volume which seems like the default bootloader?
Odin completed ok too. Any idea why it won't take?

sd_dracula said:
Got my usb port fixed, OEM unlock in dev mode, ran odin along with the twrp-3.3.1-1-gtaxlwifi.img.tar file but it doesn't seem to work. Tried twice and this is what I get after powering on with Power + Home + Up Volume which seems like the default bootloader?
Odin completed ok too. Any idea why it won't take?
Click to expand...
Click to collapse
It probably is taking but getting immediately overwritten because you are allowing it to reboot into the system. When you flash TWRP with Odin, you need to click Option and uncheck the auto reboot. Then, after flashing, hold the Home, Vol down and Power buttons until the screen goes black. Then, VERY quickly switch from Vol down to Vol up until the Samsung logo screen appears. Then release the Power button while still holding Vol up and Home and the tablet will boot into TWRP. After that, you can reboot system and TWRP will remain as the recovery app.

Yup that did the trick, thanks
How can I make a full backup of stock OS using TWRP? Is it safe to restore from that backup in the future if needed?

sd_dracula said:
Yup that did the trick, thanks
How can I make a full backup of stock OS using TWRP? Is it safe to restore from that backup in the future if needed?
Click to expand...
Click to collapse
You can't. The data partition is encrypted and TWRP can't handle it.

lewmur said:
You can't. The data partition is encrypted and TWRP can't handle it.
Click to expand...
Click to collapse
Ok so the only way would be to install the official ROM again right?

sd_dracula said:
Ok so the only way would be to install the official ROM again right?
Click to expand...
Click to collapse
There are backup apks in Play Store. You just can't use TWRP. Typically, people install TWRP because they want to root and use custom ROMs. Before using TWRP to flash custom ROMs, you must first format the data partition to get rid of the encryption. But that erases EVERYTHING on it. Including any saved video, audio, pictures or apps. Even Google apps. But remember, by installing TWRP, you have already tripped knox, so you won't be getting any further updates from Samsung.
If you really want a stock ROM that you can backup with TWRP, it might be possible to format the data partition and then flash the stock opengapps for the version of stock ROM, probably ARM 32bit 8.1. But I don't know of anyone whose tried it. Of course, you need to backup any data you want to save and reinstall any Play Store or sideloaded apks you are using.

Plan is to try a couple of custom ROMs and if any issues go back to one of these: https://www.sammobile.com/samsung/galaxy-tab-a/firmware/SM-T580/ that shouldn't be a problem right?
Also I have wiped data which cleared everything and then when I tried to go wipe dalvik/system/data/cache in preparation for LineageOS, but it keeps failing because of /data, still encrypted after the initial format?
Why does it not work?

sd_dracula said:
Plan is to try a couple of custom ROMs and if any issues go back to one of these: https://www.sammobile.com/samsung/galaxy-tab-a/firmware/SM-T580/ that shouldn't be a problem right?
Also I have wiped data which cleared everything and then when I tried to go wipe dalvik/system/data/cache in preparation for LineageOS, but it keeps failing because of /data, still encrypted after the initial format?
Why does it not work?
Click to expand...
Click to collapse
Did you choose the format Data option in the wipe screen? You should have typed yes to confirm.

Got it sorted in the end, the problem was I had booted to the OS after wiping that instead of just installing the zip which solved it, thx

So glad I was directed to this forum thx @srgrusso. I flashed the official version of TWRP using the TWRP app from the app store and it work just like it was supposed to. Thank for suggesting I give it a try. I will be using it go forward, to verify, backup and update my TWRP from the official web site. Thanks again for all you do for the T580 device, you have breath new life and interest into this device for me. I love playing around with now.

Related

[Q] Noob needing help on CM/Gapps update

I have an i777 that is running CM 10.1.3-RC2-i777. The phone was on a previous CM version, and I chose to update it to this version (simply through the setting options on the phone, thinking it would have to be pretty harmless and simple). (A friend had installed CM in the first place, so I know very little about it). After the update, I lost my unlock, but I solved that issue. Then I noticed none of my Google apps were working. After research, I saw that I needed to install GApps. I also see that there is a new stable version of CM (10.1.3). I really just want a functional phone, ideally with the latest features. But I'm not interested in frequently tweaking anything.
So I downloaded gapps-jb-20130812-signed.zip and cm-10.1.3-i777.zip and copied them on the sd card root folder. Actually, the first time I did this, I had unzipped the folders (habit I guess). So when I booted into recovery mode with clockworkmod and selected the files, it just open the folders rather than installing anything. I read on some install instructions to reset the phone or erase local data (I can't remember exact wording), but I chose to do it, wondering if that would help. I hadn't realized about the unzip issue.
Now when I go into recovery mode, I first get a warning screen, pushing volume up to continue. It then says ODIN MODE, Product Name: sgh-i777, custom binary download: YES (1 counts), current binary: custom, downloading...do not turn off target. But nothing happens, and it freezes there until I reboot it. So I can't get into clockworkmod, and install the zips.
How do I get past this and install the zip files? I assume the phone does not have clockwordmod anymore?
I have tried to find the answers online, but no luck for this specific situation.
Please be very specific with any help, and don't assume that I know the special lingo. Thank you so much!
Dugul said:
...Now when I go into recovery mode, I first get a warning screen, pushing volume up to continue. It then says ODIN MODE, Product Name: sgh-i777, custom binary download: YES (1 counts), current binary: custom, downloading...do not turn off target. But nothing happens, and it freezes there until I reboot it. So I can't get into clockworkmod, and install the zips.
How do I get past this and install the zip files? I assume the phone does not have clockwordmod anymore?
I have tried to find the answers online, but no luck for this specific situation.
Please be very specific with any help, and don't assume that I know the special lingo. Thank you so much!
Click to expand...
Click to collapse
what you describe above indicates that you entered download mode, not recovery mode.
starting with the phone off
to enter recovery mode on the I777:
with the USB cable UNPLUGGED, hold the volume up, volume down and power keys until the samsung logo appear, then release the keys. The phone will then boot into recovery mode.
to enter download mode on the I777:
with the USB cable PLUGGED INTO A COMPUTER, hold the volume up, volume down and power keys until the samsung logo appear, then release the keys. The phone will then boot into download mode.
Your issue of things not working after a cm update sounds like a dirty flash gone rogue. I suggest that instead of trying to correct the existing issues, you do a full wipe and reinstall. It will involve more time and reworking all of your settings, but in the end, (in my opinion) it's worth it to have a clean, maintenance free installation.
-Cyril
cyril279 said:
with the USB cable UNPLUGGED
Click to expand...
Click to collapse
Wow, that was the only problem. I obviously had no idea. I definitely had it connected with the USB. I easily entered into recovery mode and installed the zip files. So thank you very much for the clear instructions on this!
I'm not sure what a full wipe and reinstall would entail. But I may have been close to that with doing the factory wipe that I did. I have to reinstall all my apps and settings it seems. I'll see how it goes after that.
Thank you again!

[Q] Need help getting my E970 to boot

Ok, so I rooted my LGOG E970. I figured I better unlock it as well, so I used FreeGee and unlocked it. I tried to download CWM but it said it couldnt download file. So I thought I would reboot my phone. Now, all I get is the google logo, with the unlocked key underneath, and it then goes to the LG logo and back to Google and shuts off. I tried to hold down power and volume down, nothing, and power volume up nothing.:crying:
any ideas? Thanks in advance! I love this phone!
CJ
You too, huh?
I did this the other night, and when the CWM failed to install I went to download it myself... That's when I saw that CWM for geeb is 6.0.3.8, not 6.0.4.5 like FreeGee shows. (Looks like FreeGee has moved on to targeting G2 or another... Oops.)
I hope you backed up your EFS, because mine was screwed up and I needed to manually restore it from the backup I'd taken. (I've had my phone rooted for 9+ months, finally got fed up with stock and was looking to get onto a 4.4 ROM)
So here's what I did:
Held power button until phone was properly off (failed boot seemed to be a still partially on state)
Held volumn up first, then started holding power.
When phone vibrated slightly, I let go of power and kept holding volume up... You should be in boot loader now.
When your phone is in the bootloader, connect to your PC (Make sure you have the proper drivers if you use Windows; I use Linux which doesn't have the same nonsense setup for drivers like Windows does)
Make sure "fastboot devices" shows your phone and then type: fastboot flash recovery _____recovery file name.img____
Press volume down twice to select "Recovery", and press power once to select it... You should be booted into the recovery that you just installed.
Once you're in a recovery, you can push a ROM zip via ADB, flash, wipe data/dalvik cache and reboot.
thanks, Just a little more help
aedren said:
You too, huh?
I did this the other night, and when the CWM failed to install I went to download it myself... That's when I saw that CWM for geeb is 6.0.3.8, not 6.0.4.5 like FreeGee shows. (Looks like FreeGee has moved on to targeting G2 or another... Oops.)
I hope you backed up your EFS, because mine was screwed up and I needed to manually restore it from the backup I'd taken. (I've had my phone rooted for 9+ months, finally got fed up with stock and was looking to get onto a 4.4 ROM)
So here's what I did:
Held power button until phone was properly off (failed boot seemed to be a still partially on state)
Held volumn up first, then started holding power.
When phone vibrated slightly, I let go of power and kept holding volume up... You should be in boot loader now.
When your phone is in the bootloader, connect to your PC (Make sure you have the proper drivers if you use Windows; I use Linux which doesn't have the same nonsense setup for drivers like Windows does)
Make sure "fastboot devices" shows your phone and then type: fastboot flash recovery _____recovery file name.img____
Press volume down twice to select "Recovery", and press power once to select it... You should be booted into the recovery that you just installed.
Once you're in a recovery, you can push a ROM zip via ADB, flash, wipe data/dalvik cache and reboot.
Click to expand...
Click to collapse
I try to go to recovery and it just goes blank. What program with my crazy windows would be best to get a stock file to the phone? Or any other ideas>
thanks again
ZombieGeek said:
I try to go to recovery and it just goes blank. What program with my crazy windows would be best to get a stock file to the phone? Or any other ideas>
thanks again
Click to expand...
Click to collapse
Yeah, the stock recovery won't boot if you try it either. I forgot to tell you that. If you drop in a custom recovery (TWRP or CWM), it will work fine and you can both create a backup of your data and flash a new ROM...
If you want to try to get back to stock, LGNPST is what you should try. But to be completely honest, I don't know if you can LGNPST from the state that it's in. I haven't tried, and I'm using a custom ROM now (the whole reason I unlocked the bootloader to begin with).
bummer
aedren said:
Yeah, the stock recovery won't boot if you try it either. I forgot to tell you that. If you drop in a custom recovery (TWRP or CWM), it will work fine and you can both create a backup of your data and flash a new ROM...
If you want to try to get back to stock, LGNPST is what you should try. But to be completely honest, I don't know if you can LGNPST from the state that it's in. I haven't tried, and I'm using a custom ROM now (the whole reason I unlocked the bootloader to begin with).
Click to expand...
Click to collapse
again, thanks so much! you are my hero, only problem is, I loaded the kit kat bu houstonn and now I have no cellular? I hate it when your phone isnt a phone lol
ZombieGeek said:
again, thanks so much! you are my hero, only problem is, I loaded the kit kat bu houstonn and now I have no cellular? I hate it when your phone isnt a phone lol
Click to expand...
Click to collapse
Yeah, I got that too. I don't know if I got it fixed due to changing ROM, using the suggested recovery from the ROM, or if it was due to me restoring my EFS backup.
I flashed the TeamWin recovery found in the PSX instructions. Then I flashed PSX + Latest kernel + Banks Gapps + Banks Google Camera + AT&T NFC fix + SuperSU. I manually restored EFS from an ADB shell while in recovery.
When I booted I had: LTE works, Wifi works, NFC works, Camera works, ART works... The only things failing for me are the following:
Cell provider shows up as "Maritime" (display bug; as mentioned, LTE works fine and I'm on AT&T)
Settings > Developer Tools > Geeky Process Stats (does nothing)
Settings > Lockscreen > Slider Shortcuts (crashes as soon as I tap the middle ring)
LogCat is spammed with "QCOM PowerLock: Failed to acquire lock" whenever my finger is on the screen.
/system/xbin/mount --bind doesn't work (neither does mount -o bind). It gets sorta half-way-there, because the target directory can't be removed, but isn't bound properly it seems.
Other than that, it's been fast and smooth.

[Q] kitkat 4.4.2 Phone stuck at boot animation. device unauthorized in adb

Hi
I installed kitkat 4.4.2 omnirom on my GS2 i777. I guess the 4.4 gapps full stock package which I installed screwe up my phone. It booted once but there was no launcher/homescreen, I could get into settings via the notification panel. Then I restarted and its stuck at the boot screen overnight. The recovery button combinations don't work. Download mode doesn't work. When I tried to reboot via adb it says device unauthorized. There's no way I can authorize it on my phone since its stuck at the boot animation. Any suggestions or work around is much appreciated. Thanks in advance
Update: USB Jig did the job. its up and running now.
From Omni OP notes:
GApps: The size of full (system installed) Gapps packages prevent the use or ART runtime. Mini Gapps + google play installation of desired addons is a more efficient approach considering the resources available.
Click to expand...
Click to collapse
@avinash_kk, the fact that the device boots is a good sign.
Please verify that you are:
-attempting the recovery keystroke (vol+ & vol- & power) with the USB cable UNPLUGGED.
-holding the keystroke through two cycles of the initial SAMSUNG or GALAXY SII logo.
Once you are in recovery, you will need to:
-wipe cache & dalvik cache & /data & /system,
-install Omni, GApps (PA mini) & superSU
-reboot system
cyril279 said:
From Omni OP notes:
@avinash_kk, the fact that the device boots is a good sign.
Please verify that you are:
-attempting the recovery keystroke (vol+ & vol- & power) with the USB cable UNPLUGGED.
-holding the keystroke through two cycles of the initial SAMSUNG or GALAXY SII logo.
Once you are in recovery, you will need to:
-wipe cache & dalvik cache & /data & /system,
-install Omni, GApps (PA mini) & superSU
-reboot system
Click to expand...
Click to collapse
Thank you for the reply cryil279. But the recovery keystroke doesn't work. that is the reason I'm trying to reboot recovery via adb. but since its 4.2.2+ it needs a RSA key authorization and I'm stuck at the boot screen. so I can't accept the authorization on the phone. I was hoping if theres a work around for the RSA key authorization. Thanks
Did you flash omni using the instructions provided in the OP of the thread? Or did you use a different method?
If you're getting past the bootloader image to the boot animation, then the bootloader is intact. Are you saying that you cannot get to download mode either?
cyril279 said:
Did you flash omni using the instructions provided in the OP of the thread? Or did you use a different method?
If you're getting past the bootloader image to the boot animation, then the bootloader is intact. Are you saying that you cannot get to download mode either?
Click to expand...
Click to collapse
Yes I followed all the instructions in the OP of that thread. I updated recovery. and yes I cannot get into download mode.
When you stay "stuck at the boot screen" I assume you mean the initial samsung/galaxy sII logo. Whether this is an indication that the bootloader has completed or not, I cannot say for sure.
In short, if all three download-mode keystroke methods aren't working for you, then I am at the end of my ability to help. I am not ADB savvy, so I cannot help you there, and hope that one of our peers can step in and help further.
-Cyril
avinash_kk said:
Yes I followed all the instructions in the OP of that thread. I updated recovery. and yes I cannot get into download mode.
Click to expand...
Click to collapse
cyril279 said:
When you stay "stuck at the boot screen" I assume you mean the initial samsung/galaxy sII logo. Whether this is an indication that the bootloader has completed or not, I cannot say for sure.
In short, if all three download-mode keystroke methods aren't working for you, then I am at the end of my ability to help. I am not ADB savvy, so I cannot help you there, and hope that one of our peers can step in and help further.
-Cyril
Click to expand...
Click to collapse
Thank you. it passes the initial Samsung logo and is stuck at the Omni Boot Animation. so I think the bootloader is fine. I'm now looking for a way to Authorize my device to respond to ADB commands to reboot to recovery. before 4.2.2 it didn't ask for the Authorization. I believe that's the only way I can recover my phone now.
avinash_kk said:
... and yes I cannot get into download mode.
Click to expand...
Click to collapse
What methods have you tried? There are several possibilities.
This is puzzling since it freezes on the Omni logo after completing the Galaxy SII boot sequence. I can understand why you would not get into recovery with the three button sequence, but you should be able to get into download mode.
I know speaking from my experience with Omni, one of the downloads I flashed did kind of the same thing. I couldn't get into download mode at all. The key combination just wouldn't work. I ended up having to adb into download mode, but luckily could do so as I had already enabled adb debugging before the problem began.
It's troubling to know that with the bootloader intact, the keystroke fails. So in theory, if you hadn't enabled debugging, and therefore hadn't been able to send the command via ADB, you'd have been bricked?
I also can't help but wonder whether all of the keystroke sequences do exactly the same thing. -if ADB can send a successful command, then perhaps one of the sequences might work where another does not?
a) phone off, vol- then plug-in USB
b) vol + & vol - & power while USB is already plugged in
c) vol + & vol - then plug USB cable in
d) battery out(a)
e) battery out(c)
Clearly, I'm not in a hurry to test any of this.
Phalanx7621 said:
I know speaking from my experience with Omni, one of the downloads I flashed did kind of the same thing. I couldn't get into download mode at all. The key combination just wouldn't work. I ended up having to adb into download mode, but luckily could do so as I had already enabled adb debugging before the problem began.
Click to expand...
Click to collapse
cyril279 said:
It's troubling to know that with the bootloader intact, the keystroke fails. So in theory, if you hadn't enabled debugging, and therefore hadn't been able to send the command via ADB, you'd have been bricked?
I also can't help but wonder whether all of the keystroke sequences do exactly the same thing. -if ADB can send a successful command, then perhaps one of the sequences might work where another does not?
a) phone off, vol- then plug-in USB
b) vol + & vol - & power while USB is already plugged in
c) vol + & vol - then plug USB cable in
d) battery out(a)
e) battery out(c)
Clearly, I'm not in a hurry to test any of this.
Click to expand...
Click to collapse
I can say that with the battery IN, I had (previously when this happened) tested out A and B, neither worked. Hadn't tried C, and hadn't tried testing without the battery out. Interesting though, good to know I have some more options to think of IF it would ever happen again =D
cyril279 said:
It's troubling to know that with the bootloader intact, the keystroke fails. So in theory, if you hadn't enabled debugging, and therefore hadn't been able to send the command via ADB, you'd have been bricked?
I also can't help but wonder whether all of the keystroke sequences do exactly the same thing. -if ADB can send a successful command, then perhaps one of the sequences might work where another does not?
a) phone off, vol- then plug-in USB
b) vol + & vol - & power while USB is already plugged in
c) vol + & vol - then plug USB cable in
d) battery out(a)
e) battery out(c)
Clearly, I'm not in a hurry to test any of this.
Click to expand...
Click to collapse
I tried all but d and e. Will try today and update you guys.
avinash_kk said:
I tried all but d and e. Will try today and update you guys.
Click to expand...
Click to collapse
I can now confirm that none of those combinations work. does anybody think a USB jig will work??
avinash_kk said:
I can now confirm that none of those combinations work. does anybody think a USB jig will work??
Click to expand...
Click to collapse
I think it is certainly worth a try. I'm not speaking from personal experience of course, but using a USB jig has been reported several times as the only way to get a phone into download mode. Also, assuming that the previous assumptions are true for your phone, I'd say that if "adb reboot download" would work, then a jig would work too.
creepyncrawly said:
I think it is certainly worth a try. I'm not speaking from personal experience of course, but using a USB jig has been reported several times as the only way to get a phone into download mode. Also, assuming that the previous assumptions are true for your phone, I'd say that if "adb reboot download" would work, then a jig would work too.
Click to expand...
Click to collapse
adb reboot download doesn't work. it gives the same device unauthorized error. I'm gonna order a USB JIG. I'll report back once I try that route. Thank you all for your insight and support.
I'd bet a hundred bucks that a jig will get you to download mode in your situation. Always good to have around w/ this phone.
Sent from my SGH-I777 using XDA Premium 4 mobile app
So.. USB jig was the only way to go. the phone is up and running Omnirom without any hassles now. I made sure The RSA key is Authorized on my PC and hope this doesn't repeat. Thank you guys for your inputs and help.
Just a noob question, Does flashing another recovery/Kernel Change the RSA key? I think the key comes from the PC?
Thanks for providing the feedback.
To verify, I've just tried it (flashed render's 12-26 linaro kernel and it remained authorized, then back to render's 12-29 sabermod kernel, and again, still authorized), and it doesn't seem to care which kernel. I only tested by "adb devices". I'm not sure (and don't have time to test right now) whether a dirty-rom-flash would affect it.
Did you build or buy your jig? <--you already stated that you ordered one
-(if buy) then who did you buy it from?
avinash_kk said:
So.. USB jig was the only way to go. the phone is up and running Omnirom without any hassles now. I made sure The RSA key is Authorized on my PC and hope this doesn't repeat. Thank you guys for your inputs and help.
Just a noob question, Does flashing another recovery/Kernel Change the RSA key? I think the key comes from the PC?
Click to expand...
Click to collapse

Tab S6 stuck in bootloop, can't get to recovery mode

My Tab S6 tried to auto-install an update yesterday (it is rarely connected to Wifi/internet). It then rebooted. Since then, it's been stuck in a boot loop.
It will display the "Samsung Galaxy Tab S6 | Secured By Knox" logo screen for a few seconds, then switch to the blue "Installing System Update" screen (with the android logo). Installing System Update gets to 28% and stops. Then the rotating icon on the android freezes. Then the device reboots and starts all over again.
Edit: the tablet is 100% stock. It's not been rooted or had any custom ROMs loaded.
I have tried getting to recovery mode, by holding power+volup while it boots. This doesn't seem to change the behavior at all. Any advice is much appreciated.
Fedge7 said:
My Tab S6 tried to auto-install an update yesterday (it is rarely connected to Wifi/internet). It then rebooted. Since then, it's been stuck in a boot loop.
It will display the "Samsung Galaxy Tab S6 | Secured By Knox" logo screen for a few seconds, then switch to the blue "Installing System Update" screen (with the android logo). Installing System Update gets to 28% and stops. Then the rotating icon on the android freezes. Then the device reboots and starts all over again.
Edit: the tablet is 100% stock. It's not been rooted or had any custom ROMs loaded.
I have tried getting to recovery mode, by holding power+volup while it boots. This doesn't seem to change the behavior at all. Any advice is much appreciated.
Click to expand...
Click to collapse
can you shut it down? try volume down and power button ? if it don't shut down, do this soon as it reboots, hold volume up and down and plug in usb cable to desktop/laptop usb port! it will boot into download mode!
N1NJATH3ORY said:
can you shut it down? try volume down and power button ? if it don't shut down, do this soon as it reboots, hold volume up and down and plug in usb cable to desktop/laptop usb port! it will boot into download mode!
Click to expand...
Click to collapse
I can't actually shut it down. If I start holding power+voldown right after it boots, the tablet does reboot before getting stuck at 28%. But it reboots--it doesn't power off.
I tried download mode and that actually seemed to work! Specifically, I left the tablet overnight in the reboot loop until the battery drained. Just now, I held down volup+voldown and plugged it into my laptop. I got the green "Warning/Custom OS" screen and then pressed volup to continue. The tablet rebooted pretty quickly after that (I'm guessing due to low battery) so I didn't get a good look at the download mode options.
Once I'm in download mode, can I factory reset the tablet? I don't need to preserve any data/apps/settings.
Fedge7 said:
I can't actually shut it down. If I start holding power+voldown right after it boots, the tablet does reboot before getting stuck at 28%. But it reboots--it doesn't power off.
I tried download mode and that actually seemed to work! Specifically, I left the tablet overnight in the reboot loop until the battery drained. Just now, I held down volup+voldown and plugged it into my laptop. I got the green "Warning/Custom OS" screen and then pressed volup to continue. The tablet rebooted pretty quickly after that (I'm guessing due to low battery) so I didn't get a good look at the download mode options.
Once I'm in download mode, can I factory reset the tablet? I don't need to preserve any data/apps/settings.
Click to expand...
Click to collapse
You cannot reset the tablet from Download mode afaik- You need to enter Recovery Mode to do that.
You can however, flash stock from Download mode using Odin (3.13.3 is best). If you're not confident with doing that, your best option is Factory Reset in Recovery Mode. Hold Volume Up and Power when the Tablet is booting, let go when you see the Samsung logo. The timing can be tricky, but you should be able to do it. Also, you can force a reboot with Volume Down and Power.
Alternatively, if factory reset doesn't work, since you're completely stock, you will still be covered under warrenty.
bartleby999 said:
your best option is Factory Reset in Recovery Mode. Hold Volume Up and Power when the Tablet is booting, let go when you see the Samsung logo.
Click to expand...
Click to collapse
Thanks for the suggestion. I have tried this many many times. I've tried letting go of the buttons at different times. I've tried holding volup while letting go of power. I've tried this a ton of different ways, and no matter what, the tablet always shows the "Installing system update" screen. Some googling has led me to believe that sometimes, when performing a factory reset, the "Installing system update" screen shows up right before the normal recovery screen. Is it possible that the tablet is trying to get to recovery mode, but can't get past this first step?
Fedge7 said:
Is it possible that the tablet is trying to get to recovery mode, but can't get past this first step?
Click to expand...
Click to collapse
Honestly, I don't know - I'm not an expert but I guess it's possible that the update failed and corrupted both System and Recovery.
You'll be covered under warrenty, so maybe just return the Tablet from where you purchased or direct to Samsung, could take a while given the current situation though I guess. If you have a PC, then I think the best option would be to just flash stock yourself, since that's probably all Samsung will do. Even if that doesn't work you'd still be covered under warrenty, as far as I'm aware attempting to flash stock doesn't trip Knox.
Here is solution to unbrick your device!!!
Fedge7 said:
My Tab S6 tried to auto-install an update yesterday (it is rarely connected to Wifi/internet). It then rebooted. Since then, it's been stuck in a boot loop.
...
Edit: the tablet is 100% stock. It's not been rooted or had any custom ROMs loaded.
I have tried getting to recovery mode, by holding power+volup while it boots. This doesn't seem to change the behavior at all. Any advice is much appreciated.
Click to expand...
Click to collapse
Despair not...I have just come from resolving this exact situation not 30 minutes ago. I'd been trying to flash (using Odin as I decided to stay on Stock and not root this device, for a change) the latest OneUI2.1 releases for my device (SM-T865 - LTE version) and boom in the middle of the Odin update, the flash just failed...I then couldn't reboot and get into neither Recovery, nor Download Mode because it appears my bootloader and recovery both got corrupted.
Here's what you need....
1. Odin app for PC (am on Windows)
2. Your device's Stock firmware (sammobile firmware archive)
3. You will need someone to help you boot the device directly into Download mode (and this is the tricky part because for most of us we are used to get into Bootloader by using the key combination (from Powered Off device) Vol+ and Power On at the same time to get into stock recovery and then scrolling down to option 2 in this menu, "Reboot to Bootloader". Well now you are going to boot directly into Bootloader mode. Here's how you do it...
4. Get your friend to line up the USB-C cable into the port of the device, but DO NOT press it in...yet
5. Press Power off and Vol- buttons at the same time to turn off the device
6. And now you have to to be super fast: if device starts to turn on on its own, YOU press and hold Vol+ and Vol- both at the same time while YOUR FRIEND pushes the USB cable fully into the port - you should now have booted directly into Download mode. (if not repeat this, and remember to be super fast and sync with your friend pushing in the USB cable)...
7. When you get into Download mode, then you are home and dry...
8. Select ONLY the Bootloader file (BL...XX...) in Odin, make sure only "reset time" and "reboot" are ticked, and flash
9. When device reboots, press Vol+ and Power combo to get back into Bootloader mode again...but I think device will reboot into Download mode on its own
10. Now select all the files from your Stock file into the various tabs (BL, CP, CSC, AP...) do not select HOME_CSC as we want to flush this device clean...
11. Flash, and voila...success - you will have lost all your data but rather that than losing the device...
12. Feedback here and let us know if this works? For reference for others in the future...
FYI, I got in this situation, and the previous post did work for me, just takes good timing! Thanks!!!!
Same issue today for me. My tablet showed different screen with green and red text, it allowed me to delete app data, then booted into safe mode, then i had to do factory reset and now i am screwed, as it is refusing to restore any apps and their settings. I will try to flash it back to Android 9, maybe then it will do the restore. I forgot to do any manual backup to SD or so.
Edit: the device upgraded to 10, but reset itself after about 10 minutes of use.
Edit2: i found what caused it. It is caused by Nova Launcher, if i try to set wallpaper.
Just found a news article that there is a RGB/sRGB problem with wallpapers. It might be the problem i had.
I am adding a screenshot of the result.
Yeah, I had that kind of reboot loop from a wallpaper that I downloaded
Moe5508 said:
Here is solution to unbrick your device!!!
Despair not...I have just come from resolving this exact situation not 30 minutes ago. I'd been trying to flash (using Odin as I decided to stay on Stock and not root this device, for a change) the latest OneUI2.1 releases for my device (SM-T865 - LTE version) and boom in the middle of the Odin update, the flash just failed...I then couldn't reboot and get into neither Recovery, nor Download Mode because it appears my bootloader and recovery both got corrupted.
Here's what you need....
1. Odin app for PC (am on Windows)
2. Your device's Stock firmware (sammobile firmware archive)
3. You will need someone to help you boot the device directly into Download mode (and this is the tricky part because for most of us we are used to get into Bootloader by using the key combination (from Powered Off device) Vol+ and Power On at the same time to get into stock recovery and then scrolling down to option 2 in this menu, "Reboot to Bootloader". Well now you are going to boot directly into Bootloader mode. Here's how you do it...
4. Get your friend to line up the USB-C cable into the port of the device, but DO NOT press it in...yet
5. Press Power off and Vol- buttons at the same time to turn off the device
6. And now you have to to be super fast: if device starts to turn on on its own, YOU press and hold Vol+ and Vol- both at the same time while YOUR FRIEND pushes the USB cable fully into the port - you should now have booted directly into Download mode. (if not repeat this, and remember to be super fast and sync with your friend pushing in the USB cable)...
7. When you get into Download mode, then you are home and dry...
8. Select ONLY the Bootloader file (BL...XX...) in Odin, make sure only "reset time" and "reboot" are ticked, and flash
9. When device reboots, press Vol+ and Power combo to get back into Bootloader mode again...but I think device will reboot into Download mode on its own
10. Now select all the files from your Stock file into the various tabs (BL, CP, CSC, AP...) do not select HOME_CSC as we want to flush this device clean...
11. Flash, and voila...success - you will have lost all your data but rather that than losing the device...
12. Feedback here and let us know if this works? For reference for others in the future...
Click to expand...
Click to collapse
Bravo!!
Works for me.
Many thanks
I can get into download mode. But it kicks me out within a few seconds. Any help please
Moe5508 said:
Here is solution to unbrick your device!!!
Despair not...I have just come from resolving this exact situation not 30 minutes ago. I'd been trying to flash (using Odin as I decided to stay on Stock and not root this device, for a change) the latest OneUI2.1 releases for my device (SM-T865 - LTE version) and boom in the middle of the Odin update, the flash just failed...I then couldn't reboot and get into neither Recovery, nor Download Mode because it appears my bootloader and recovery both got corrupted.
Here's what you need....
1. Odin app for PC (am on Windows)
2. Your device's Stock firmware (sammobile firmware archive)
3. You will need someone to help you boot the device directly into Download mode (and this is the tricky part because for most of us we are used to get into Bootloader by using the key combination (from Powered Off device) Vol+ and Power On at the same time to get into stock recovery and then scrolling down to option 2 in this menu, "Reboot to Bootloader". Well now you are going to boot directly into Bootloader mode. Here's how you do it...
4. Get your friend to line up the USB-C cable into the port of the device, but DO NOT press it in...yet
5. Press Power off and Vol- buttons at the same time to turn off the device
6. And now you have to to be super fast: if device starts to turn on on its own, YOU press and hold Vol+ and Vol- both at the same time while YOUR FRIEND pushes the USB cable fully into the port - you should now have booted directly into Download mode. (if not repeat this, and remember to be super fast and sync with your friend pushing in the USB cable)...
7. When you get into Download mode, then you are home and dry...
8. Select ONLY the Bootloader file (BL...XX...) in Odin, make sure only "reset time" and "reboot" are ticked, and flash
9. When device reboots, press Vol+ and Power combo to get back into Bootloader mode again...but I think device will reboot into Download mode on its own
10. Now select all the files from your Stock file into the various tabs (BL, CP, CSC, AP...) do not select HOME_CSC as we want to flush this device clean...
11. Flash, and voila...success - you will have lost all your data but rather that than losing the device...
12. Feedback here and let us know if this works? For reference for others in the future...
Click to expand...
Click to collapse
Hi,
Really need your help, after I updated my firmware using Odin, updated BL, AP, CP, CSC, my tab cannot boot up stuck in logo. Doing the Power + volume up leads me to different screen now. I cannot access recovery mode or download page anymore,
What must I do? Pleasssee help. Added the pic, after doing hard reset (power + vol up)
I cannot connect back to Odin also. Always setup connection failed.
Please help. Really messed up big time
Just a thought... Can this be restored from service center?
Thank you in advance.
I have the same problem with a Tab S6 Lite, it is in bootloop and does not let me enter the recovery mode, I can go into download mode and I flashed the latest original firmware Android11, Android10 etc., . I tried them all but always goes in bootloop, and also the bootloop occurs only if I connect the usb cable to the PC, without any sign of life. Do I still have hopes or have I compromised the motherboard?
The reason for all this is because I had followed a guide to give root permissions with magisk, I did everything right, only that the guide was with Android10, while I had Android11 and I was deceived by the fact that in the title of the guide there was written "guide 2021"
, so I did not check the compatibility of operating systems, I was a fool, I know, I hope so much that I did nothing irretrievable, it's my son's tablet!
Genpis said:
I have the same problem with a Tab S6 Lite, it is in bootloop and does not let me enter the recovery mode, I can go into download mode and I flashed the latest original firmware Android11, Android10 etc., . I tried them all but always goes in bootloop, and also the bootloop occurs only if I connect the usb cable to the PC, without any sign of life. Do I still have hopes or have I compromised the motherboard?
The reason for all this is because I had followed a guide to give root permissions with magisk, I did everything right, only that the guide was with Android10, while I had Android11 and I was deceived by the fact that in the title of the guide there was written "guide 2021"
, so I did not check the compatibility of operating systems, I was a fool, I know, I hope so much that I did nothing irretrievable, it's my son's tablet!
Click to expand...
Click to collapse
Did you use HOME CSC or the non HOME CSC when flashing?
Genpis said:
I have the same problem with a Tab S6 Lite, it is in bootloop and does not let me enter the recovery mode, I can go into download mode and I flashed the latest original firmware Android11, Android10 etc., . I tried them all but always goes in bootloop, and also the bootloop occurs only if I connect the usb cable to the PC, without any sign of life. Do I still have hopes or have I compromised the motherboard?
The reason for all this is because I had followed a guide to give root permissions with magisk, I did everything right, only that the guide was with Android10, while I had Android11 and I was deceived by the fact that in the title of the guide there was written "guide 2021"
, so I did not check the compatibility of operating systems, I was a fool, I know, I hope so much that I did nothing irretrievable, it's my son's tablet!
Click to expand...
Click to collapse
Try to install a castom rooted rom which has pre installed also Twrp.
[MAGISK Rom / Firmware base convertor) 420rom-T860/5 - V13.3- CUE1 - ANDROID 10 - OneUI 3.1 - Sec Patch 05/2021 - Released 06/07/2021
WELCOME TO 420 ROM - MAGISK ROM FOR SAMSUNG GALAXY TAB S6 WiFi/4G (T860/5)! 420rom Telegram-Group: Please bear in mind that things will be added as and when my learning and time permits (being a dad with a family and having ADHD myself means...
forum.xda-developers.com
Download the android 11 last rooted rom from there. You install it with odin as as a normal original rom.
Disable in odin auto reboot. After rom install, restart manually and press the correct buttons immediately to boot in Twrp and not to system. Format (not wipe) data from there and reboot to system. If you are lucky it will work..
(I hope you unlocked bootloader before try to root. If you haven't unlocked bootloader this won't work also).
Moe5508 said:
Here is solution to unbrick your device!!!
Despair not...I have just come from resolving this exact situation not 30 minutes ago. I'd been trying to flash (using Odin as I decided to stay on Stock and not root this device, for a change) the latest OneUI2.1 releases for my device (SM-T865 - LTE version) and boom in the middle of the Odin update, the flash just failed...I then couldn't reboot and get into neither Recovery, nor Download Mode because it appears my bootloader and recovery both got corrupted.
Here's what you need....
1. Odin app for PC (am on Windows)
2. Your device's Stock firmware (sammobile firmware archive)
3. You will need someone to help you boot the device directly into Download mode (and this is the tricky part because for most of us we are used to get into Bootloader by using the key combination (from Powered Off device) Vol+ and Power On at the same time to get into stock recovery and then scrolling down to option 2 in this menu, "Reboot to Bootloader". Well now you are going to boot directly into Bootloader mode. Here's how you do it...
4. Get your friend to line up the USB-C cable into the port of the device, but DO NOT press it in...yet
5. Press Power off and Vol- buttons at the same time to turn off the device
6. And now you have to to be super fast: if device starts to turn on on its own, YOU press and hold Vol+ and Vol- both at the same time while YOUR FRIEND pushes the USB cable fully into the port - you should now have booted directly into Download mode. (if not repeat this, and remember to be super fast and sync with your friend pushing in the USB cable)...
7. When you get into Download mode, then you are home and dry...
8. Select ONLY the Bootloader file (BL...XX...) in Odin, make sure only "reset time" and "reboot" are ticked, and flash
9. When device reboots, press Vol+ and Power combo to get back into Bootloader mode again...but I think device will reboot into Download mode on its own
10. Now select all the files from your Stock file into the various tabs (BL, CP, CSC, AP...) do not select HOME_CSC as we want to flush this device clean...
11. Flash, and voila...success - you will have lost all your data but rather that than losing the device...
12. Feedback here and let us know if this works? For reference for others in the future...
Click to expand...
Click to collapse
Why flashing only the bootloader first? At the moment I'm trying to recover my s20 fe from a bootloop without losing my data
sosimple said:
Try to install a castom rooted rom which has pre installed also Twrp.
[MAGISK Rom / Firmware base convertor) 420rom-T860/5 - V13.3- CUE1 - ANDROID 10 - OneUI 3.1 - Sec Patch 05/2021 - Released 06/07/2021
WELCOME TO 420 ROM - MAGISK ROM FOR SAMSUNG GALAXY TAB S6 WiFi/4G (T860/5)! 420rom Telegram-Group: Please bear in mind that things will be added as and when my learning and time permits (being a dad with a family and having ADHD myself means...
forum.xda-developers.com
Download the android 11 last rooted rom from there. You install it with odin as as a normal original rom.
Disable in odin auto reboot. After rom install, restart manually and press the correct buttons immediately to boot in Twrp and not to system. Format (not wipe) data from there and reboot to system. If you are lucky it will work..
(I hope you unlocked bootloader before try to root. If you haven't unlocked bootloader this won't work also).
Click to expand...
Click to collapse
Any tips in recovering my stock s20 fe from a bootloop without losing data? already tried Odin but without success the first try
jointer said:
Same issue today for me. My tablet showed different screen with green and red text, it allowed me to delete app data, then booted into safe mode, then i had to do factory reset and now i am screwed, as it is refusing to restore any apps and their settings. I will try to flash it back to Android 9, maybe then it will do the restore. I forgot to do any manual backup to SD or so.
Edit: the device upgraded to 10, but reset itself after about 10 minutes of use.
Edit2: i found what caused it. It is caused by Nova Launcher, if i try to set wallpaper.
Click to expand...
Click to collapse
did you managed to not lose your data?
jrdef said:
Any tips in recovering my stock s20 fe from a bootloop without losing data? already tried Odin but without success the first try
Click to expand...
Click to collapse
Wiping cache partition in Recovery and reflashing the firmware are basically your only 2 options
jrdef said:
Any tips in recovering my stock s20 fe from a bootloop without losing data? already tried Odin but without success the first try
Click to expand...
Click to collapse
Flash in odin the same rom you had. There are 2 csc files in rom, which you use 1 in odin one. Try use the "home csc". Home csc keep KEEPS your data. If you're lucky it may work. (It would work in keeping your data 100% if your rom was ok. Because it isn't you have some changes to work.).
You must try with same rom or newer.
CSC – If you flash the CSC file, it’ll perform a factory reset of your Galaxy device and wipe all data while installing a new firmware to bring your device to the same state as it was when you purchased it. Go with CSC if you want a clean installation.
HOME_CSC – On the other hand, if you want to keep your Samsung phone’s data and settings even flashing the stock firmware, you can select the HOME_CSC file.

HELP! Broken Screen and stuck in TWRP

Here is the situation:
S9+ (F/DS) Model, ROOTED and TWRP installed, USB DEBUGGING ENABLED
I broke the screen and now no touch will register. I want to create a NANO backup to restore to a new device BUT:
1. When I plug the USB cable into my PC, my phone does not show up as an ADB device, instead it shows as a portable device.
2. I can see the device in ODIN, I can see the Internal storage and the SD card, but when I do adb devices, the phone is not listed
I've tried to install Google USB drivers and I've been seraching, but keeps saying it's not compatible for my device...
I am at a loss...
1. Can't get ADB to work,
2. Now I cant' even exit TWRP because that's all touch based as well, and I have no way to click on reboot or create backup.
madcaesar18 said:
2. Now I cant' even exit TWRP because that's all touch based as well, and I have no way to click on reboot or create backup.
Click to expand...
Click to collapse
You can reboot with your hard keys:
Press and hold down the Power and Volume Down buttons for 5-10 seconds
Continue holding these two buttons down until the the Galaxy S9 restarts
Then let go of these two buttons and wait for the device to boot back into Android
Click to expand...
Click to collapse
You can also try vol.up+power if the method above doesn't work.
Once you're in your OS, connect to adb and backup your files.
User699 said:
You can reboot with your hard keys:
You can also try vol.up+power if the method above doesn't work.
Once you're in your OS, connect to adb and backup your files.
Click to expand...
Click to collapse
Unfortunately this doesn't work, Volume Down + Power will restart the device, but it keeps going back into TWRP.
Volume Down + Power + Bixby gets me into download mode, again, clicking power down to "restart" in this mode also then goes back into TWRP :/
madcaesar18 said:
Unfortunately this doesn't work, Volume Down + Power will restart the device, but it keeps going back into TWRP.
Volume Down + Power + Bixby gets me into download mode, again, clicking power down to "restart" in this mode also then goes back into TWRP :/
Click to expand...
Click to collapse
Okay, if so I want to ask a few questions:
madcaesar18 said:
1. When I plug the USB cable into my PC, my phone does not show up as an ADB device, instead it shows as a portable device.
Click to expand...
Click to collapse
That means adb devices shows nothing?
madcaesar18 said:
I've tried to install Google USB drivers and I've been seraching, but keeps saying it's not compatible for my device...
Click to expand...
Click to collapse
I remember windows searched automatically for drivers. Doesn't that work? I don't have windows, so never had driver issues...
If you want (and are a little bit experienced with computers) we could try to create a linux live usb boot, install adb and fastboot tools onto it and then try to see if your device is being recognized.
But since it's a little bit of effort, you should do it only if the drivers keep failing.
madcaesar18 said:
2. Now I cant' even exit TWRP because that's all touch based as well, and I have no way to click on reboot or create backup.
Click to expand...
Click to collapse
But you're at that screen with all those buttons (install, reset, backup, restore, etc.)? It's not that screen where you have to swipe (the initial screen to grant write / readonly access)?
Maybe you can also try an otg mouse. I don't know if it works in twrp, though. But where I live we can actually ask to test the product first (and don't have to buy it) so maybe you could try that at your local store (if they aren't closed due to the current situation).
Easy fix; replace the display.
Always keep your critical data redundantly backed up... or someday you will lose it☠
There are two ways to learn; the easy way or the hard way.
The hard way leaves scars.
blackhawk said:
Easy fix; replace the display.
Always keep your critical data redundantly backed up... or someday you will lose it☠
There are two ways to learn; the easy way or the hard way.
The hard way leaves scars.
Click to expand...
Click to collapse
Yes, I assumed replacing the display is no option since he has/gets a new device:
madcaesar18 said:
I want to create a NANO backup to restore to a new device
Click to expand...
Click to collapse
User699 said:
Yes, I assumed replacing the display is no option since he has/gets a new device:
Click to expand...
Click to collapse
It's still a valuable device. A backup phone is always good to have.
This time though get a good case for it
I use the Bolt on my N10+ and it would be long dead* if not for this case.
*or in poor condition vs spotless A+ condition

Categories

Resources