Database Info

[Q] Unable to factory reset

Yesterday my phone started acting up. All running process crashed and not many was able to start. I had to constantly click "force close". I think this started after I installed the Google+ app, but not sure.
I have tried uninstalling all unnecessary apps, without luck. I then tried wiping to factory settings by using the Android menu, but without any changing. I then tried by holding vol+ and power, going in to recovery and wiping both to factory and app cache. This doesn't change anything either. By googling I can see some suggests to hold vol- and power, to get to a another wiping-functionality but this just boots my Nexus S to normal state - no menu appears.
Has anybody an idea of what I can do?
Edit: more info; if I click "Report" and investigate the message sent to Google, I see that error has something to do with SQLite-relatet classes. Which makes some sense, alot of my changes are reset each time the phone is rebooted. For instance did I miss a call a couple of hours before the phone went crazy - this is shown at each boot in the notification area eventhough I clear the area and/or goes to missed call section

Factory reset via menu does delete all your "custom" apps, so I'd say it's not one of the existing apps causing problems.
The way you describe function after your factory reset sounds like factory reset didn't work properly.
If you feel safe I'd recommend rather flashing 2.3.4 again using either Odin or the OTA zip from Google (requires open bootloader).

I think you're right that factory reset doesn't do what is expected. Once I click it, the phone reboots and shows the Android guy next to an unwrapping package. This lasts only 2 seconds, then it reboots itself again and goes into normal phone mode (where all the app-crashing starts again).
I have not flashed or rooted my phone before, but I will consider this now since my NS is pretty much a brick. Thank you for your swiftly response.
Edit: Shouldn't I get a menu, when I push and hold vol- button, while turning on the device? Right now it just boot as normal.

Before you use odin....try going into rom manager a reflashing clockwork! Ive had that android dude on my screeen but reflashibg via rom manager always fixed it. Try that
Sent from my Nexus S using XDA Premium App

Wow my Nexus has totally shut me out.
I cannot use ClockworkMod unfortunately since I am not able to root my phone. It is not detectable via USA (when I use vol+/pwr and connect USB). I am unable to check the USB Debugging option on the phone. Each time I check it, go to home-screen and back to the menu, it has de-selected it again. Also I noticed when I read the info that is sent to Google for all those app-crashes I get, I see SQLiteException and error in an SQLite.java file. So it seems like some database layer is broken.
I read one could copy the ClockWork.img to my phone and use the standard recovery option to flash the img (I think). But when I go into the recovery menu, the file is gone. When I boot the phone again, it has deleted the .img file - eventhough if I copy it to several different folders, they are all gone :-(.
I feel pretty screwed at the moment. How can I else wipe all data?

I'd recommend to check if your device is correctly identified in windows. Missing USB drivers might cause problems. Get the latest drivers and a guide from here.
If you succeed booting into fastboot properly (vol up and power) you can follow this guide. Get the latest cwm recovery.img here.
Last option would be to boot into download mode (vol up + vol down + power + plugging in usb cable) and use Odin from samfirmware.com
--
All options require correctly working USB drivers.

I managed to unlock the bootloader, by quickly turning on USB-debugging (before any processes started to crash) and install the drivers from this post:
http://forum.xda-developers.com/showpost.php?p=6819751&postcount=4
A reboot later, I got this message:
"System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Right below was a button saying "Im feeling lucky" (??)
I installed ClockworkMod using fastboot and tried "Fixing permissions" with no luck. I will try some ROM later on, and hope it will bring my phone back

Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.

rentaric said:
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
Click to expand...
Click to collapse
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything

DennisRP said:
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
Click to expand...
Click to collapse
See I'm no expert on this whole thing. At this point I'd just flash a whole new system via Odin. Prolly not the smartest or safest option, but that's what I'd do because I don't know better. If that wouldn't fix it either, I'd return the phone on warranty

I was looking at Odin from the start, since nothing else seemed to be working.
So right now I got started on Odin. Followed the .pdf steps and flashed the bootloader at first succesfully. I was asked to remove the battery and re-connect my NS. Began downloading "pda" and "phone", but at around 10% a big fat red "fail" message appeared and now I just see the Google-logo on startup. I still cant flash any roms via fastboot.
Im too tired too right now, been working with this for 14 hours straight. I will look at it tomorrow evening. Thanks for your help rentaric

Weird, you're not the first one who had trouble running Odin using their guide.
Overall it's pretty simple.
Enter download mode. Vol up vol down and power at the same time while plugging in the USB cable. Start Odin, should show a yellow colored box with a port number. Uncheck everything but reset timer and auto reboot. Unzip the correct zip file from samfirmware.com (check if you got i9020 or i9023 and get the universal Odin exe), apply file from the folder accordingly. Bootloader and bootloader. Phone and modem. Pda and pda. Csc can remain empty (will change carrier info in fastboot).
Double check md5 hash to avoid broken files.
Sent from my Nexus S using XDA App

rentaric said:
Weird, you're not the first one who had trouble running Odin using their guide.
Click to expand...
Click to collapse
Of course I did not go to bed, how should I be able to sleep with a broken phone .
The firmware suggested on samfirmware.com for my phone, was 2.3.3 and some other version (my phone was 2.3.4.2/GRJ22 or something similar, I suspect that might be the cause. Also I unchecked everything, that might also have been of importance). The flash will always fail when everything was downloaded - it then said something about "remote" and "Loke" and then fail. But as I mentioned, I had succesfully flashed boot.img (2.3.3) thus no boot occured now. I googled the correct bootloader, used fastboot and was booting succesfully again.
I began looking more into the sdcard, as error-messages was leading me this way. To compress 4 hours of investigations into a few lines, it seems as my PBA is malfunctioning as other xda-members have experinced. Only solution is sending the phone to Samsung for a PBA replacement. I purchased the phone in Bestbuy USA and the danish Samsung partners are not too joyfull about this - I will contact Samsung and hope they can help me.
I experinced the exact same thing as this poor guy - http://forum.xda-developers.com/showthread.php?t=993403
Every thing you try to do to /sdcard is worthless.
Formatting (USB/using CWM/using adb shell linux commands) says "Succes" but nothing happens.
Copying files says "Succes" but nothing happens. If I boot phone into CWM, mount usb and upload new rom/apk/whatever and try to do a "install update.zip" it fails with some mounting errors.
Im ready to go cry in a corner - I really want this to be fixable via software, but I probably have to realize that this is a hardware issue.

Apparently Samsung doesn't offer worldwide warranty for cellularphones :´(. God it sucks to pay repair-expenses on a 1 month old mobile.

This is how to Root Rogers Samsung Rugby!

Been trying to Root this phone for a couple of days. Finally manged to do it!
Its the Rogers Samsung Galaxy Rugby. The (GT-S5690R) model.
I had to add the (R) in the updater script. Thats how I got it too root.
1. Put the file on your sd-card Universal_GB_ROOT_v5_patched_for_S5690.zip
2. Turn phone off
3. Boot in to Recovery ( press Power, Vol-up, and center button on bottom of phone all at same time. The samsung logo will appear, keep holding all buttons, then the logo will dissapear then re-appear, when it comes back let go of the power button only. The phone should boot into the 3e recovery)
4. use vol keys to navigate through menu, and use center button on the bottom of the phone to select.
5. Select install update from sd card.
6. press on the Universal_GB_ROOT_v5_patched_for_S5690.zip
7. phone should install root, wait till the 'Success' appears, then reboot.
You should find Superuser app when your phone reboots. You are Rooted!!
Now im just trying to figure out how to get a custom recovery!!

Perfect!
This zip file worked perfectly on my Rogers Galaxy Rugby. Many thanks!

Happy to hear
Sent from my GT-S5690R using xda premium

Big problem now though....
So the root went swimmingly, but I got a little too excited removing pre-installed apps. I backed up and removed Samsung Home, and removed and NOT backed up SNS 1.0. The phone will now refuse to boot unless I wipe data/factory reset in recovery mode, but after that it just ends up crashing during the Android wizard start up....
This is a brand new phone, what can I do to restore those apps, and get it back to the way I received it earlier today?!

There is a way to boot into safe mode, head Google mod2extreme and I find the forum for our phones (currently the only one) find advise there
Sent from my GT-S5690R using xda premium

Thanks for the name of that forum! I've found the guide someone posted here: http://www.mod2xtreme.com/showthread.php?t=12386 and I've decided to try it.
I'm using the first firmware listed in this thread: http://www.mod2xtreme.com/showthread.php?t=11744 (S5690XXKL1 2.3.6 2011 December S5690OXFKL1) mostly because under Country/Carrier it has nothing, so I'm assuming it's more generic than the others. I'm also keeping in mind this is for the 5690, not the 5690R, so it may not work at all. But, worth a shot since my only other recourse is to break down and cry in front of a Rogers attendant to see if he can give me a new one. "Root? What's root? Like ginger?"
I'm using v.1.83 of Odin3, which is listed as supported the 5690.
Downloaded KIES 2.0 from http://www.samsung.com/my/support/usefulsoftware/KIES/JSP - It gave me two DLL registration (COM) errors during installation on Windows. Uncertain if this will end up screwing me over or not.
Be right back, rebooting now that KIES is installed... will edit this post when there's more to report.
EDIT: Yeah, so I ended up trying both Odin version 1.83 and 1.85, with the Marvell .pit file, and the firmware from that thread. I learned that I had to put the phone into Download Mode, NOT Recovery Mode while trying Odin. Even still, nothing worked. I've given the phone up to Rogers and they will try to replace the original ROM, hopefully they won't notice that I've rooted it and really mucked everything up. They said if it doesn't work they'll send it off to Samsung to get it repaired. Anyone know if they find out I rooted it, I'd have to pay for voiding a warranty or anything?

i have the same device hae you manage to get clockworkmod recovery on it?

Does this method erase all personal data/downloaded apps from phone?

Great it worked perfectly...
did you success in installing different firmware?
Thanks again

Thanks a lot, worked like a charm.
Is there a way I can install Clockwork Mod? Rom manager doesn't recognise the s5690r. It gives me the option of selecting the Epic4G or the GalaxyS i9000. will either of these work?
Also, once I get that figured out, is there any roms compatible with the s5690r? I've scoured the webs with no luck. Not a very popular phone, eh?
Thanks again.

markdexter said:
Been trying to Root this phone for a couple of days. Finally manged to do it!
Its the Rogers Samsung Galaxy Rugby. The (GT-S5690R) model.
I had to add the (R) in the updater script. Thats how I got it too root.
1. Put the file on your sd-card Universal_GB_ROOT_v5_patched_for_S5690.zip
2. Turn phone off
3. Boot in to Recovery ( press Power, Vol-up, and center button on bottom of phone all at same time. The samsung logo will appear, keep holding all buttons, then the logo will dissapear then re-appear, when it comes back let go of the power button only. The phone should boot into the 3e recovery)
4. use vol keys to navigate through menu, and use center button on the bottom of the phone to select.
5. Select install update from sd card.
6. press on the Universal_GB_ROOT_v5_patched_for_S5690.zip
7. phone should install root, wait till the 'Success' appears, then reboot.
You should find Superuser app when your phone reboots. You are Rooted!!
Now im just trying to figure out how to get a custom recovery!!
Click to expand...
Click to collapse
Good Day, I am also working on the Bell Canada Version of the Rugby. It is the GT-s5690m model. I am now stuck in a bootloop and don't know how to fix it. I have played around with the root and unroot zip files that have been floating around but I am certain that the bootloop is due to not being able to clear the Delvik Cache. As you are aware Clockworkmod recovery is not supported on our devices. I am unsure how to get it to work. Until then I just keep trying different things to hopefully get this phone up and working. It is quite a rugged device and would be great with a custom rom and recovery. Could you explain to me in layman's terms how I might create a flashable clockwork image to flash via Odin or even through stock recovery. I would love to get this phone up and working. Thanks in advance

Sasktel Rugby
Hi there. I am working on the Sasktel version of this phone as well. I tried to change the model from R to M because this phone is the same as the bell model version but it would not install it. I found it on the external SD card but it will not run the zip file from the 3e recovery. Any ideas why this might be happening?
Thanks,

[Q] In a Bit of a Predicament with Nexus S 4G; is it possible to fix?

So like the genius that I am, I decided to mess with my Nexus S 4G. Right now, my PC will not detect my phone at all (won't show up at ALL, in my Device Manager or any toolkit that I've tried). Please note I had little experience and will probably look like a complete idiot, but bare with me.
So the steps I took were as followed (my phone came already unlocked)
1.) I first installed PDANet to get my computer to recognize my phone and install the right drivers
2.) After that, I flashed the latest, stable clockwork recovery mod
3.) Then, I downloaded the Hellybean ROM and installed it via clockwork recovery mod, with no problems
4.) I downloaded the Google Apps archive and dropped it onto my sdcard
5.) I then installed the google apps zip and then it all went down hill from then
Every time I turned on my phone, the nice Cyanogen mod logo popped up, and then once it was done booting up, it popped up with two error messages:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
Unfortunately, SetUp wizard has stopped.
Both of these error messages will not stop popping up and my phone is currently useless at this stage.
So, I went back into fastboot mode, and tried to fix it with these steps:
1.) I downloaded the "Factory Image "sojua" for Nexus S (850MHz version, i9020a)" images, and followed the instructions on this thread
2.) Once I flashed the bootloader image, my PC no longer detected my phone. It won't show up on my device manages (not even as an unrecognized Android 1.0 phone)
I installed the bootloader image because it was apart of the tutorial on how to do a complete factory reset, I now know that was stupid and not necessary.
So, you can obviously see I didn't know what I was doing, and what I did was quite stupid and careless. So unless you have any suggestions or want to help me, please do not patronize me, I am already mad enough at myself.
With that said, I am unable to even flash anything to my phone anymore, and I don't know what I can do. I tried using Wug's Nexus Toolkit to try and install the drivers, but it won't detect anything. On top of that, I am not sure if I have even flashed the correct bootloader image. Any help or suggestions would be very much appreciated.

Carbon131 said:
So like the genius that I am, I decided to mess with my Nexus S 4G. Right now, my PC will not detect my phone at all (won't show up at ALL, in my Device Manager or any toolkit that I've tried). Please not I had little experience and will probably look like a complete idiot, but bare with me.
So the steps I took were as followed (my phone came already unlocked)
1.) I first installed PDANet to get my computer to recognize my phone and install the right drivers
2.) After that, I flashed the latest, stable clockwork recovery mod
3.) Then, I downloaded the Hellybean ROM and installed it via clockwork recovery mod, with no problems
4.) I downloaded the Google Apps archive and dropped it onto my sdcard
5.) I then installed the google apps zip and then it all went down hill from then
Every time I turned on my phone, the nice Cyanogen mod logo popped up, and then once it was done booting up, it popped up with two error messages:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
Unfortunately, SetUp wizard has stopped.
Both of these error messages will not stop popping up and my phone is currently useless at this stage.
So, I went back into fastboot mode, and tried to fix it with these steps:
1.) I downloaded the "Factory Image "sojua" for Nexus S (850MHz version, i9020a)" images, and followed the instructions on this thread
2.) Once I flashed the bootloader image, my PC no longer detected my phone. It won't show up on my device manages (not even as an unrecognized Android 1.0 phone)
I installed the bootloader image because it was apart of the tutorial on how to do a complete factory reset, I now know that was stupid and not necessary.
So, you can obviously see I didn't know what I was doing, and what I did was quite stupid and careless. So unless you have any suggestions or want to help me, please do not patronage me, I am already mad enough at myself.
With that said, I am unable to even flash anything to my phone anymore, and I don't know what I can do. I tried using Wug's Nexus Toolkit to try and install the drivers, but it won't detect anything. On top of that, I am not sure if I have even flashed the correct bootloader image flashed. Any help or suggestions would be very much appreciated.
Click to expand...
Click to collapse
Good luck. Flashed a sojua stock ROM on a sojus phone, bootloader and all. I don't know if you'll ever be able to fix this. :|

polobunny said:
Good luck. Flashed a sojua stock ROM on a sojus phone, bootloader and all. I don't know if you'll ever be able to fix this. :|
Click to expand...
Click to collapse
Hopefully someone may know what to do.

Carbon131 said:
Hopefully someone may know what to do.
Click to expand...
Click to collapse
If you can put it into download mode you might be able to use Odin with a factory image to bring it back to life.

polobunny said:
If you can put it into download mode you might be able to use Odin with a factory image to bring it back to life.
Click to expand...
Click to collapse
Yeah I can't seem to do that.

Carbon131 said:
Yeah I can't seem to do that.
Click to expand...
Click to collapse
Make sure your cable is connected when you try to put your phone in download mode. Turn off the phone, then hold both volume + and -, and press power. Continue holding volume buttons until you see download mode.

[GUIDE] How to root a Sprint Samsung Galaxy Tab 3 7" (SM-T217S)

There are a couple other guides on here but they are mostly just links to videos or ad infested download links and none of them worked for me so this is how I ended up getting it to work. Everything I used is attached
For the more experienced readers it's simple, flash TWRP using Odin, boot into recovery and TWRP will prompt you to root.
For the only slightly experienced:
Boot into Download Mode (Hold Vol Down +Power to turn on the Device)
Unzip the TWRP Recovery Image after downloading it below.
Connect your tablet to your PC, unzip and run Odin, click the PDA button and select the TWRP md5 file you just unzipped.
Begin holding the Volume Up button on your Tablet and hit the start button in Odin (this will ensure you reboot into the new recovery)
Once in TWRP if you select the reboot option under advanced you should be prompted to root your device if it's not already rooted. If that doesn't happen for some reason you can use adb to sideload the SuperSU zip I've attached, or put it on an sd card and find the flash zip from sdcard option in TWRP to flash it.

Thanks Justin! Works great. Someone should sticky this.
Luckily I had a Windows computer I could use for this, but my main machine is a MacBook Pro. I wish someone would do a nice clear walkthrough like this one for using Heimdall on a Mac.

To start I have rooted many phones but am stumped on this tablet. After getting it to start with holding the volume down and power key it stops on the downloading screen. Once I can get it to reboot I held the volume up and power key and got into system recovery. If I am not mistaken I can boot from here also. Right??

Thanks it was very useful!

Will this trigger the Knox 0x1 problem? I just got this tablet and I want to be able to take it in to Sprint for repairs if I need to.

Thanks!!!
Justin Buser said:
There are a couple other guides on here but they are mostly just links to videos or ad infested download links and none of them worked for me so this is how I ended up getting it to work. Everything I used is attached
For the more experienced readers it's simple, flash TWRP using Odin, boot into recovery and TWRP will prompt you to root.
For the only slightly experienced:
Boot into Download Mode (Hold Vol Down +Power to turn on the Device)
Unzip the TWRP Recovery Image after downloading it below.
Connect your tablet to your PC, unzip and run Odin, click the PDA button and select the TWRP md5 file you just unzipped.
Begin holding the Volume Up button on your Tablet and hit the start button in Odin (this will ensure you reboot into the new recovery)
Once in TWRP if you select the reboot option under advanced you should be prompted to root your device if it's not already rooted. If that doesn't happen for some reason you can use adb to sideload the SuperSU zip I've attached, or put it on an sd card and find the flash zip from sdcard option in TWRP to flash it.
Click to expand...
Click to collapse
Thanks for the help! This is my first root I've done myself and it works like a charm. Now my next step is to flash it to any carrier. Does anyone know how to flash the sprint device to a different carrier? If anyone could help me out, that would be greatly appreciated.

Thanks for this. I finally got a couple Galaxy Tab 3's (One 210 and one 217) to upgrade my girls from their Kindle Fires.
Really needed this root to remove all the factory loaded crap.
Thanks.

colt223 said:
Thanks for this. I finally got a couple Galaxy Tab 3's (One 210 and one 217) to upgrade my girls from their Kindle Fires.
Really needed this root to remove all the factory loaded crap.
Thanks.
Click to expand...
Click to collapse
I just recently got this tablet from a deal sprint had. What version was your tablet on before rooting? Right now mine is on 4.2.2, but there is an update out. I dont want to update if it wont work with this root.

slickdealers said:
I just recently got this tablet from a deal sprint had. What version was your tablet on before rooting? Right now mine is on 4.2.2, but there is an update out. I dont want to update if it wont work with this root.
Click to expand...
Click to collapse
I believe it was on 4.2.2 when I rooted. I will have to double-check that when I get home tonight.
What model number do you have? I had to use a different TWRP download for each one of mine, meaning I had to find a different one for the 210.

colt223 said:
I believe it was on 4.2.2 when I rooted. I will have to double-check that when I get home tonight.
What model number do you have? I had to use a different TWRP download for each one of mine, meaning I had to find a different one for the 210.
Click to expand...
Click to collapse
My model number is T217S. I tried to do some extra googling and came up with a post saying that the update after 4.2.2 installed KNOX on their tablet, which made their tablet come up with errors when trying to root. Based on your answer and what I found, I'm assuming I'm alright to give it a try. I do have one other question though. After rooting do you know if it would be possible to unroot incase I have to go back to Sprint with a problem?

slickdealers said:
My model number is T217S. I tried to do some extra googling and came up with a post saying that the update after 4.2.2 installed KNOX on their tablet, which made their tablet come up with errors when trying to root. Based on your answer and what I found, I'm assuming I'm alright to give it a try. I do have one other question though. After rooting do you know if it would be possible to unroot incase I have to go back to Sprint with a problem?
Click to expand...
Click to collapse
I am honestly not sure about going back, but I have had no problems. In fact, when I booted after root, something (sorry I dont remember if it was during root, or after) asked me if I wanted to disable Knox. I said yes, and smooth sailing ever since. I think it might have been the super user app itself that disabled it for me.

colt223 said:
I am honestly not sure about going back, but I have had no problems. In fact, when I booted after root, something (sorry I dont remember if it was during root, or after) asked me if I wanted to disable Knox. I said yes, and smooth sailing ever since. I think it might have been the super user app itself that disabled it for me.
Click to expand...
Click to collapse
Just tried it and successfully rooted! I got the same message that you described about Knox. It appears when you go to update SuperSu. Thank you for the help!
For anyone else wondering about going back to stock, I found a thread to the stock firmware.
http://forum.xda-developers.com/showthread.php?t=2512172

I found the answer in another thread. Flashing TWRP will trip Knox.

Didn't work for me
I did the TWRP stuff and all it did was trigger that warranty bit. Still no root.

colt223 said:
I am honestly not sure about going back, but I have had no problems. In fact, when I booted after root, something (sorry I dont remember if it was during root, or after) asked me if I wanted to disable Knox. I said yes, and smooth sailing ever since. I think it might have been the super user app itself that disabled it for me.
Click to expand...
Click to collapse
Yeah, same story here. After flashing TWRP then installing SuperSU first via the TWRP option by booting directly to recovery before OS after flashing TWRP through odin.....then once I clicked the SuperSU app after the OS loaded I chose first the "play" option to update SuperSU then the TWRP option to install the binary update. When it next booted it informed me that Knox was installed and asked whether to disable or not..I said yes and haven't had any problems at all...just trying to find a good ROM now^^

awesome thanxs for the info..... now if we could only get cm11 on this puppy

Root Failure, odd case
I have twins - they are both, identically:
Software Version: T217VPUAMH9
Hardware Version: T217S.04
Model Number: SM-T217S
Android Version: 4.2.2
Baseband Version: T217SVPUAMH9
Kernel Version: 3.4.0-1458241
Build Number: JDQ39.T217SVPUAMH9
Jim Trotter III-style, I-DENTICAL!
I successfully rooted one with:
1: Enable debugging
2: Boot into Download Mode (from poweroff, hold Vol Down+Power)
3: terminal: sudo heimdall flash --RECOVERY ./T217S.TWRP2.7.0.0.flashable/recovery.img
4: poweroff ; boot to TWRP. From TWRP, wipe [factory reset], then install: ./root/SuperSU-v1.93.zip
With the second (apparently evil) twin, at the heimdall command, I get:
...
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
0%
ERROR: Failed to send file part packet!
ERROR: RECOVERY upload failed!
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
Re-attaching kernel driver...
On the device, the blue progress bar grows to about 2% and stops.
I even tried using a different cable in case one had gone wonky, to no avail.
I am at a total loss here.

... and SUCCEED, but via strangeways
...
So, mounting frustration.
I tried instead a slightly different version of TWRP:
$ sudo heimdall flash --RECOVERY recovery/T217S.TWRP.2.7.0.0.recovery/recovery.tar.md5
This time the result is different, but still no success:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
... but it stuck at 100% and did not continue. Device also stuck.
^C, hard reboot of device.
Tried again to double check, same result - sticks at 100%, progress bar on device sticks at somewhere around 5%.
Aware of the possible futility, but bored, I tried first one again:
$ sudo heimdall flash --RECOVERY ./T217S.TWRP2.7.0.0.flashable/recovery.img
SUCCEED.
So, apparently it has to be "knocked loose"?
Dunno. I'm in. Hope this helps someone else.

Root NB8
This won't work with NB8 EDIT: I was wrong this does work on NB8

Apparently had to reinstall the drivers a few times to get it to take on Windows. Still no clue what the issue was with Heimdall.

Verification failed error on my Galaxy S8+

So I decided to manually update my galaxy s8+ since samsung oficially stopped suporting it for future feature updates and my phone started to get too slow, so my idea was to put the lighter lineage os on it.
To do that, first, I first had to get root.
To do that, I followed an step by step guide and I finished it (im new so i cant put the link to the guide, but it's form androidinfotech/.com and the title is "Root Samsung Galaxy S8 Plus SM-G955F Pie 9.0 using TWRP"). Then I finally rebooted my phone to see if I had root installed, and an error popped up: Verification failed, unable to restart your device, that after a little of research I realized it was quite a common error on samsung devices.
After that I checked threads of people that this had happened to and it said to reboot in twrp, which of course, I installed before rooting my phone, and wipe the data and some other steps.
But the problem is that after hitting reset and inmediately hitting the button combination for recovery mode, it just launched recovery mode for a few seconds and then the screen goes black inmediately after, and sends me back to the verification failed error. So basically I can't initiate in recovery mode.
I've tried other keys combinations and they either don't work or aren't of any use. Also, I can acces download mode, if that is of any use.
Does anyone know what to do here or something?

Figured it out
turns out i hadn't wipe the data properly. from that verification failed screen i turned my phone off like you normally do it, with the power button. then accessed the recovery mode after the phone was off. that was why i couldn't access the recovery mode before. after that, i found a fix for the error that showed while wiping data and then i re installed everything i had installed before and rebooted and now everything works. hope this helps someone...?

Guy this quite helped me but my trial for s8+ exynos 9.0 at first I successfully flashed twrp via Odin but the files (magical zip,mmstate zip ,some security patch zip with noverity zip ) allowed me to root well only to end up with 1gb internal storage, I then reflashed stock how ever after that I can't flash recovery via Odin as its always shows failed official binary allowed only. I'm sure its possible to root but am missing something important. Hope to gain some enlightment as a newbie. Thanks in advance

Abdul-Hanan. B. Jonathan said:
Guy this quite helped me but my trial for s8+ exynos 9.0 at first I successfully flashed twrp via Odin but the files (magical zip,mmstate zip ,some security patch zip with noverity zip ) allowed me to root well only to end up with 1gb internal storage, I then reflashed stock how ever after that I can't flash recovery via Odin as its always shows failed official binary allowed only. I'm sure its possible to root but am missing something important. Hope to gain some enlightment as a newbie. Thanks in advance
Click to expand...
Click to collapse
homie, youre best off posting up an entirely new thread with your issue as most folks will likely miss a post like this on a year old thread. the 1gb of storage is usually fixed with a factory reset done in recovery. If not, youre going to have to flash the stock FW on it again via Odin to tell its storage table how much storage it actually has