Database Users

[Q] My device won't boot anymore (bootloop?)

This is the first time I tried to root my phone. My phone is a Galaxy s4 GT-i9505
I followed this guide to the letter and it was supposed to be easy peasy. https://www.youtube.com/watch?v=LlVCjtRUrgs
Well when I was doing all that I got to the last step where I had to update my binaries but that didn't work and superSU kept closing itself down.
Someone recommended I do an factory reset and repeat all the steps, but then when I got back into my system I kept getting errors saying SuperSU has stopped and Youtube has stopped.
Those were really annoying and I tried another factory reset but I couldn't get rid of them, somehow they kept inserting themselves in my app list eventhough the apps did not work.
So I used TWRP to do an advance wipe and that's when things went horribly wrong since I had no clue what I am doing :S
I ticked the boxes Dalvik cache - Internal storage - Data and something else I can't remember.
After that was completed I could not boot up my phone anymore and now I'm freaking out trying to follow guides to fix this.
like this one : http://trendblog.net/fix-soft-bricked-android-device-first-aid-guide/
I installed this toolkit: http://forum.xda-developers.com/showthread.php?t=2226263
But the problem is that my computer is not opening the device anymore through the USB port, and when I try to install these drivers : http://androiddrivers.net/samsung-android-drivers/galaxy-s4-windows-drivers-3264bit/
there's an error when installing it fails on mobile device MTP or something probably since my computer does not reckognize the mobile device anymore.
I don't have a SD card atm I never owned one. I might need to get one in order to fix this?
I'm totally new to this and totally regretting ever trying this and being so stupid and impatient as to try an advanced wipe before informing myself well enough.
I'm freaking out like mad here and now I have to go to sleep which I won't be able to catch ofc I'm so afraid I need to toss my phone and when I think about the $$$ .. well you know what I mean.
I've tried looking through these forums and guides but I just don't understand most of it and I can't get it figured out it's driving me insane.

Just chill, there is nothing wrong with your phone. You cannot kill your phone doing the things you did.
Just flash a stock firmware true Odin and everything will be working again. Pick a 4.4.2 rom though.
The reason why you are messing up is because you tried to use a year old rooting method.
So the steps you want to take:
- Flash a stock firmware
- Flash cf-auto root http://forum.xda-developers.com/showthread.php?t=2219803
- Flash TWRP
- Flash this script in TWRP http://forum.xda-developers.com/galaxy-s4/general/scriptknoxout-complete-brutal-knox-t2807172
done.

Summary of my mistakes Rooting my R1 and removing ads. Phone is now Total Brick.

So, I figured my mistakes can save some others some grief. Part of the problem is that this phone is relatively new and information is scattered all over so it is hard to find all that is necessary at a singe source.
I had the Amazon Prime 8 gb with 6.1 firmware. I first installed the SP Flashing tool and flashed the TWRP_Scatter_R1_Prime.zip. I already had the MTK preloader drivers installed. I then flashed the TWRP scatter file, Download Only, and all went well. I did a complete back up to my SD card. I wanted to run the debloating scripts at this point, but I had missed installing them on the SD card, so I installed SuperSU from TWRP after pressing Vol+ and power to reboot. Then I did a regular reboot. The phone booted just fine so I added the scripts to the SD card. I then rebooted into TWRP and ran all three debloating scripts and rebooted. Again, all went well.
Here is where I made my First Error. I reset the phone to factory defaults so I could go through the setup procedure. One of the video guides suggested this. I am assuming that one of the debloat scripts deleted the setup procedure since I now wound up in a perpetual loop where the phone kept telling me it could not run set up.
So, as I had made a complete backup in TWRP, I rebooted into TWRP and did a restore from my back up file. FAIL. No idea why. I then went to the video outlining the procedure for restoring a bricked phone using SP Flash and the correct txt file for flashing the default 6.4 firmware, being told that updating was OK. ERROR. SP Flash said I needed to re-run using the setting Format+Download.
Second Mistake. Half way through, another ERROR. And I now had a total brick. No recognition on a PC; no TWRP boot; no power up no matter how long I held the power button. DOA.
Please weigh in on anything I am missing or am mistaken on. Also, help other users in pointing out anything I did wrong and missed. At least this is only $50. But I am skipping this phone and staying with my old model.

chas0039 said:
So, I figured my mistakes can save some others some grief. Part of the problem is that this phone is relatively new and information is scattered all over so it is hard to find all that is necessary at a singe source.
I had the Amazon Prime 8 gb with 6.1 firmware. I first installed the SP Flashing tool and flashed the TWRP_Scatter_R1_Prime.zip. I already had the MTK preloader drivers installed. I then flashed the TWRP scatter file, Download Only, and all went well. I did a complete back up to my SD card. I wanted to run the debloating scripts at this point, but I had missed installing them on the SD card, so I installed SuperSU from TWRP after pressing Vol+ and power to reboot. Then I did a regular reboot. The phone booted just fine so I added the scripts to the SD card. I then rebooted into TWRP and ran all three debloating scripts and rebooted. Again, all went well.
Here is where I made my First Error. I reset the phone to factory defaults so I could go through the setup procedure. One of the video guides suggested this. I am assuming that one of the debloat scripts deleted the setup procedure since I now wound up in a perpetual loop where the phone kept telling me it could not run set up.
So, as I had made a complete backup in TWRP, I rebooted into TWRP and did a restore from my back up file. FAIL. No idea why. I then went to the video outlining the procedure for restoring a bricked phone using SP Flash and the correct txt file for flashing the default 6.4 firmware, being told that updating was OK. ERROR. SP Flash said I needed to re-run using the setting Format+Download.
Second Mistake. Half way through, another ERROR. And I now had a total brick. No recognition on a PC; no TWRP boot; no power up no matter how long I held the power button. DOA.
Please weigh in on anything I am missing or am mistaken on. Also, help other users in pointing out anything I did wrong and missed. At least this is only $50. But I am skipping this phone and staying with my old model.
Click to expand...
Click to collapse
With format+download make sure preloader is not checked....

For anyone interested, BLU really doesn't want to repair the phone. Their regular rep said that I needed to send it back to Amazon as it was too early for them to repair it even with the warranty voided. I got a supervisor and they said that actually, they would fix it and the current cost with no physical damage would be $28.50. So with $4 shipping on my part I am back in business.
So anyone with a 6.6 brick has an option that is not too bad.

chas0039 said:
For anyone interested, BLU really doesn't want to repair the phone. Their regular rep said that I needed to send it back to Amazon as it was too early for them to repair it even with the warranty voided. I got a supervisor and they said that actually, they would fix it and the current cost with no physical damage would be $28.50. So with $4 shipping on my part I am back in business.
So anyone with a 6.6 brick has an option that is not too bad.
Click to expand...
Click to collapse
If you had a Prime version and it was within the first 30 days of purchase, you could've send it back to Amazon to get a replacement, no questions asked, for free (this only works once by the way). Either way, glad to see Blu is willing to fix our mistakes. Maybe request that your R1 is restored with older, non-6.6 firmware. Probably won't work, but it's worth a try.

But do note that if you send it back to Blu for repair, it is very likely that when you get it back it will have the latest 6.6 update on it that disables SPFT so you won't have root, be able to disable ads, flash non-prime rom or any of that stuff.

yaconsult said:
But do note that if you send it back to Blu for repair, it is very likely that when you get it back it will have the latest 6.6 update on it that disables SPFT so you won't have root, be able to disable ads, flash non-prime rom or any of that stuff.
Click to expand...
Click to collapse
My guess is, they will load it with the factory shipped image, unless QA loads the update during testing, but perhaps they wont.... Kinda like a roll of the dice on this one...

I found a similar problem on an other mtk device thread. Where either through formating or failed flashing that you end up in am appearently dead device. If it is the same, it is from the battery stats getting woped out. And the solution is to leave it plugged in for two to three days then try to connect to spft again.
I am skepticle but what harm could if do to try.
I beleive the boot ROM section is not writeable and not formatable. (The first 2mb of device chip) so, it should be seen by PC as some kind of com port
I did not have success flashing pree loader with spft but @Persuasion89 has recovered his phone and as soon as he replies to my request for a file list you should be all set for a repair.

This is why I just paid the extra $50 and bought the ad free version. $110 is still a great price for the device, and no hassles with any ad removing nonsense

mrmazak said:
I found a similar problem on an other mtk device thread. Where either through formating or failed flashing that you end up in am appearently dead device. If it is the same, it is from the battery stats getting woped out. And the solution is to leave it plugged in for two to three days then try to connect to spft again.
I am skepticle but what harm could if do to try.
I beleive the boot ROM section is not writeable and not formatable. (The first 2mb of device chip) so, it should be seen by PC as some kind of com port
I did not have success flashing pree loader with spft but @Persuasion89 has recovered his phone and as soon as he replies to my request for a file list you should be all set for a repair.
Click to expand...
Click to collapse
Im sorry for the delay, ive been trying to drop a transmission into my car but I'll try to get a list together for you tonight. I did some manual tinkering with my scatters and frankenstein work with file lists so i'll need some time, but ill get back to you when i can.

I wish I have seen this before bricking mine......

How did you brick it? I have rooted and twrped two of them now without any issues. What did you do that people need to be careful to NOT do?

[Dirty-Santa Root] Bricked Verizon LG V20 Please Help!!!

I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was the first boot I expected a decently long wait, after about 25 minutes I followed the guide's instructions for Verizon since it did say some Verizon users were experiencing long first boot times. I took the battery out like it said, put it back in, then proceeded to fastboot boot2.img, like the guide said. After letting it sit for an hour this time, I got the idea that something was obviously wrong. After multiple attempts with no success I tried to fix it myself. So far I have learned that on the fastboot screen it says my bootloader is locked again, even after unlocking it. I have tried flashing TWRP as a recovery, just to at least have a recovery boot, that does not work either unfortunately. So as of right now, all I have is a v20 that has no OS, a locked bootloader, no way of booting recovery, I can fastboot with no ADB, and its virtually a paperweight. If anyone has a solution to at least get back to Stock, I would greatly appreciate it! Thanks!

First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.

Did you get it fixed?

frome901 said:
Did you get it fixed?
Click to expand...
Click to collapse
He has not responded to my pm

What roms can we use with dirty santa root?

me2151 said:
First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.
Click to expand...
Click to collapse
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...

TheDantee said:
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...
Click to expand...
Click to collapse
In his case we needed to redo from step 3.

I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc) http://www.hardreset.info/devices/lg/lg-v20/
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.

Bricked T-Mobile v20
I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was flash a new rom on it then i get boot loop with TWRP. so i decide to OEM LOCK again after that everything was stuck on my phone just boot loop with LG so any solutions please help me...... THx u for help me.

Kinda nerve wrecking to read about all these "bricked" phones popping up after trying this method lol.. Perhaps I'll just wait until a more tried and true way comes out...

Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into

For anyone that isnt on sprint that has "bricked" their phone. There are kdz's that will allow you to reflash back to 'stock". Someone had an issue with the kdz, but it was an easy fix. If you failed the process, it can be restored. Just if it doesnt want to boot, just lock and unlock the bootloader...
If your phone doesnt have a kdz, I know TeamDev is working on a custom kdz for such phones. Don't bug him if it isn't finished as I type this.
Anyone that can't get into TWRP, or has failed the process. Either start back at step 3, or if you have TWRP installed but can't get to it, the manual way to get into TWRP is a pain.
Keep your back cover off and hold the volume down button for ease. Now press the power button and as soon as you see an LG logo, let go and repress the power button. Its tricky.... If you get the corrupted screen, pop your battery out and put it back in quick and repress volume down and power. Usually if Im quick enough the first LG logo will hang a lot longer than usual and that gives me time to enter TWRP. A factory reset screen will pop up. Hit Yes twice.

Please help urgent
lcovel said:
I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc)
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.
Click to expand...
Click to collapse
Please can u help ke unbrick mine i bought this mobile in my country its expensive and has no support. I have tried all tools but still getting the error model unknown please help sir

Jaistah said:
Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into
Click to expand...
Click to collapse
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.

yuppicide said:
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.
Click to expand...
Click to collapse
it means dirty santa root got a high posibility rate of bricking a device compared to other root methods for other devices and if you have no experience in bricking phones before then you're screwed if it happens to you

Actually, if you follow the directions, almost none of the problems create a true brick-- which means unrecoverable. For most of the cases, you might get a soft brick, meaning you have to back out, use a KDZ to repair it or reflash something else, or start over from scratch and try again-- but usually (maybe with some help from here) you can pull the phone back into a usable state.
I would hazard to guess for the vast majority the process works fine, maybe with a hiccup, but I've not seen many reports of a truly unrecoverable brick from this method. It's complicated, yes, and you need to be ready to read a LOT to understand what's going on, but it seems pretty difficult to end up with a $700 paperweight with this.

So i have been trying tonroot my sprint lg v20 and everytime i try and go to the phone on mobile terminal to enter id
Then enter the apply patch /system/bin/atd /storage/emulated/0/dirtysanta i get this message and i cant go to step 2 to boot into recovery

Any help would be appreciated: i have a sprint v20 and i wanted to know if i have to flash the stock sprint rom or can i just flash lineage rom following this guide? I have it running on AT&T and i want to keep it on AT&T...

can you please assist
Could you help out, please? I don't believe I have hard bricked my LG V20 H910. However, I have read and tried all of the unbrick info out. It seems my screw up is unique. I completed dirty Santa then went to flash a custom. in the boot between that. I get a black screen and cant do anything even download mode will not come up. My PC does make its usual noises when i connect or disconnect, but my phone does nothing.

Ok, I managed to brick mine too. It's a VS995, it was running stock 1AC. I used the LGUP tool to downgrade it to VS99512A, and then did Dirty Sanata and TWRP. After booting into TWRP I decided to try lineage OS with Android 8.0, I did not make a backup of the Stock ROM, which was very stupid. Lineage OS 15.1 flashed but I had no cell service so I panicked and instead of wiping it in TWRP and using the backup of stock I should have created, I just opened LGUP and tried to downgrade it back to stock VSS99512A. Well LGUP said it worked, but when it went to boot it would hang at the Verizon logo with 4 pastel dots. Device manager could see an ADB device and I could connect to it with ADB. So I did and read the logcat. I could see it was trying to update as part of the rollback, but it appeared that some components from Android 8x could not be "upgraded" to Andoird 7.x. There was a repeated error about failing to update SQLite instance version from 3 to 1.
The one feature that could fix this is if the refurbish function worked with any of the VS995 KDZ files we all have access to. But alas, none work instead we only get the upgrade function... or so I thought. Somewhere in my search for the past 2 weeks I found a modified LGUP https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
**Please be warned what I did was absolutely ****ing stupid, and it was sheer luck I didn't screw anything up.**
From what I can tell if you only flash ("LGUP Upgrade") the KDZ from the same model it never clears the partition it just adds to it. My problem was there was stuff from lineage OS 15 stuck on one of the partitions that was making the rollback to stock fail because it kept saying it couldn't update the SQLLite DB from 3 to 1. So no "upgrade" within LGUP would work because the upgrade function does not clear internal storage. But the link above is to a version someone modded so you can force a partition update from any KDZ onto the system. So I started playing around with forcing KDZs from other models onto my VS995, and I noticed when using the Partion DL function with non-VS995 KDZ files it would say something about the partition changing. All I can assume is that the partition layout is so different on each model and it forces LGUP to re-partition the storage.
**Again I state for the record this was stupid, and I'm only fortunate it worked.**
I forced Partion DL of H91510d_00_VTR_CA_OP_1110.kdz, then H990N10b_00_OPEN_HK_DS_OP_1017.kdz, then back to VS99512A_06_1114_ARB00.kdz, then when it booted it gave the Verizon hello, and moved on finally but the setting service kept crashing while it was trying to load the Secure Boot screen. So I yanked the battery and went into the boot menu and did the Factory Reset function, and it worked.
Lesson learned, always make a backup and don't be so hasty to use tools that aren't fully functional (LGUP).
Perhaps what I've done may help others, maybe I've found out how to reimage or unbrick our V20s. Or maybe I just got really stupid lucky.

Not sure what I did, boot I am stuck in a boot loop

Started off by unlocking the bootloader on the December update (just got device the other day)
Used @munchy guide to install twrp and root the device
everything looked great
backed up stock
flashed everything but internal storage
installed lastest version of AOSiP
crashed during install so I thought ok, bad download. did a restore and got an error that system wasn't mounted. unchecked the box under mount, and restored. I reboot and all hell has broken loose. Fore close left and right. I go back to try and get to TWRP, and it's stock Recovery.
Follow guide again and get back into TWRP. I see that all my stuff is still there. So I do some reading and saw some folks having similar problems with TWRP not sticking, so I find some instructions in the TWRP thread that I need to flash the TWRP image to both slots, run the install patcher and should be all set. I do that...wipe again, restore and now I am in a continuous bootloop. I tried to switch slots, do a restore on the other slot....bootloop.
I feel really stupid and really bummed out that even with all my years and experience, I somehow found myself in this noob trap. Is anyone able to help me at least get back to just stock? All I really want at this point is to be back on stock with root so I can run an ad blocker. Thanks everyone

Mods - could you please close? I know have a hardware issue (lol), a rubber ring on the inside of USB port has come out and wedged inside the port, rendering the device defective. Thank you

Trying to install TWRP and Lineage . . . vbmeta is in the way

I've been trying for the last few days to root and install Lineage on a brand new S6 lite tablet. I've downloaded Lineage, Odin, stock rom, ADB/platform tools, Ls4 tool, the 7 whatever it is extraction tool. I've unlocked the bootloader (I can recite every option under developer options). I've installed Magisk hoping that it might help if I rooted the dumb thing (spoiler alert: it rooted, it didn't help). I've tried to install it using ADB (before reading that Samsungs don't play nice with it ). I tried to side load it with an SD card; tablet liked the card, poo poo'd the files on it. I've used ODIN in every way shape and form, it always says "Yay! You Pass!" then my tablet reboots saying "Boo! You Lose!". I then reinstall the stock ROM, try something else, reinstall stock ROM, try this solution, reinstall stock ROM. The latest and greatest hurdle: when trying to install TWRP I get the error message VBMETA Error verifying image, not signed (3), verification disabled bit is set. I found info on that here, downloaded vbmeta from my stock ROM, tried to use a blank vbmeta, even went overboard and did something with the PIT function in Odin (saw it in the internet, it HAS to be correct, right?). Nothing nothing nothing.
I've rooted and installed custom ROM on Samsung tablets in the past, but this is ridiculous. It would take me a LONG time to give all the details of everything I've tried, if needed I can. At this point it's the principal of the matter . . . I am going to make this happen one way or another, and any advice someone might have would be appreciated.
About me!
Samsung Galaxy Tab S6 tablet LITE, SM-P610, running Android 11, UI 3.1, WIFI only.

vstarjewel said:
I've been trying for the last few days to root and install Lineage on a brand new S6 lite tablet. I've downloaded Lineage, Odin, stock rom, ADB/platform tools, Ls4 tool, the 7 whatever it is extraction tool. I've unlocked the bootloader (I can recite every option under developer options). I've installed Magisk hoping that it might help if I rooted the dumb thing (spoiler alert: it rooted, it didn't help). I've tried to install it using ADB (before reading that Samsungs don't play nice with it ). I tried to side load it with an SD card; tablet liked the card, poo poo'd the files on it. I've used ODIN in every way shape and form, it always says "Yay! You Pass!" then my tablet reboots saying "Boo! You Lose!". I then reinstall the stock ROM, try something else, reinstall stock ROM, try this solution, reinstall stock ROM. The latest and greatest hurdle: when trying to install TWRP I get the error message VBMETA Error verifying image, not signed (3), verification disabled bit is set. I found info on that here, downloaded vbmeta from my stock ROM, tried to use a blank vbmeta, even went overboard and did something with the PIT function in Odin (saw it in the internet, it HAS to be correct, right?). Nothing nothing nothing.
I've rooted and installed custom ROM on Samsung tablets in the past, but this is ridiculous. It would take me a LONG time to give all the details of everything I've tried, if needed I can. At this point it's the principal of the matter . . . I am going to make this happen one way or another, and any advice someone might have would be appreciated.
About me!
Samsung Galaxy Tab S6 tablet LITE, SM-P610, running Android 11, UI 3.1, WIFI only.
Click to expand...
Click to collapse
Stumbled upon the answer to get Lineage OS and recovery installed . . . AND IT FREAKIN WORKED! Happy Dance!!!!!

vstarjewel said:
Stumbled upon the answer to get Lineage OS and recovery installed . . . AND IT FREAKIN WORKED! Happy Dance!!!!!
Click to expand...
Click to collapse
How did you fix? Just for a reader's curiosity sake.

Real_fakename said:
How did you fix? Just for a reader's curiosity sake.
Click to expand...
Click to collapse
I believe he used LineageOS Recovery instead of TWRP (since the latter has been abandoned by the developer due to too many problems getting it working properly).

MJPollard said:
I believe he used LineageOS Recovery instead of TWRP (since the latter has been abandoned by the developer due to too many problems getting it working properly).
Click to expand...
Click to collapse
What he said . . . still my hero!!!! Not sure if it matters or not, but I ended up using Heimdall/ADB to install Lineage. More key strokes but it worked the first time I tried it. Thumbs up for it

I'm hanging installing the recovery, see: https://forum.xda-developers.com/t/...s-on-galaxy-tab-s6-lite.4417629/post-86603873
How to reboot into recovery after flashing? I always land into Stock ROM

I mistakenly thought that Heimdell could get you right into recovery mode, but upon reading the instructions I sent you it says you need to boot into recovery manually . . . I apologize for the wrong info. I can say that I found that if you don't move them fingers FAST from the reboot mode to recovery mode buttons, you will keep getting plopped back to the stock ROM. Like the SECOND the screen goes dark you switch over to the power and volume up buttons, AND DO NOT LET GO! I do remember having a bit of a pause when booting into the Lineage recovery, and I thought I would have to start over when the recovery screen came up. I did a triple take, couldn't believe I got it to work.

vstarjewel said:
I mistakenly thought that Heimdell could get you right into recovery mode, but upon reading the instructions I sent you it says you need to boot into recovery manually . . . I apologize for the wrong info. I can say that I found that if you don't move them fingers FAST from the reboot mode to recovery mode buttons, you will keep getting plopped back to the stock ROM. Like the SECOND the screen goes dark you switch over to the power and volume up buttons, AND DO NOT LET GO! I do remember having a bit of a pause when booting into the Lineage recovery, and I thought I would have to start over when the recovery screen came up. I did a triple take, couldn't believe I got it to work.
Click to expand...
Click to collapse
Did your S6 happen to show "KG STATE: Checking" constantly? After 2 hours, even though the console shows that there was success, the device itself appears to constantly be downloading, as per the instructions. But even after 2 hours, there is no notification on the tablet that shows the download is complete.