Related
Ok, before I get flamed, I did search (and search and search and search)...
Here's the back story. I have a VZW Galaxy Tab, and I was running OldMacNut's Honeycomb alpha on my tab... I wanted to be able to use 3G, so I wanted to use another ROM, so I attempted to flash one through recovery. It failed everytime I tried, so I went back to Heimdall and did a clean original stock download, and everything went wonderful...
Me, not being able to leave the damn thing alone figured I would root it, and then throw CWM back onto it, then install the GB rooted ROM on... Well, when I ran CWM it converted the the file extention, and when it went to reboot, it just boot looped.
So I held the power button down, and shut it down. I had it plugged into the charger and walked away from it for a few minutes to take care of something else, and when I came back to it, the sceen showed the battery icon like it was charging, but a multi-lined circle in the middle of the battery, and the green moving part of the battery wasn't working like I have seen on the Galaxy S devices...
I went to try to turn it back on, and nothing happened, so I researched some, and left well enough alone and let it charge.
Now, the battery icon isn't even on the screen, and the screen stays black all the time.... No matter any combination of buttons or screen holds I do, it isn't turning back on now, even while it is plugged directly into the wall.
I'm at a lost.
Any help would be AWESOME!!!!
THANKS IN ADVANCE!!!!!
EDIT: I let the Tab sit for a LONG time, and I got the battery icon thing back... Still afraid to try anything else atm.
PLEASE PLEASE HALP!!!!!
Can you get to download mode?
Tabulous said:
Can you get to download mode?
Click to expand...
Click to collapse
That's the issue... I can't. I've tried and tried. I left the tab plugged in overnight, so I'm hoping that it at least is fully charged now, so I can try to mess with it today some.
here's what you should do. let's start from the very beginning.
1. download heimdall. get it here: http://forum.xda-developers.com/showthread.php?t=755265
2. download the stock verizon files. get them here: http://www.blackmugmedia.com/Android...n/VZW Stock/
you need all four files.
3. download the drivers for the samsung sch-i800. find those here: http://downloadcenter.samsung.com/co...v1.3.350.0.exe
4. unzip heimdall. go into the drivers folder, and run zadig.exe. at the top, select 'list all devices'. go to the dropdown menu, and select Samsung Composite USB (i'm pretty sure that's what it was called.) click start, and let it run.
5. open the heimdall front end.
6. put system in system (if you're flashing to ec02, then put factory in system) put cache into cache put param into param put the zimage into both the kernel and recovery slots.
7. turn your tab off, and plug it into the computer using USB. hold down the power and the volume down buttons until you see the little droid dude with a shovel.
8. click the start button on heimdall.
9. wait for the flash to complete (don't unplug your device, obviously, during the flashing.) once your phone reboots, it's okay to unplug it.
10. now, boot into the stock recovery, and wipe data and cache. update to ec02
11. enable usb debugging.
12. plug your phone back in to the computer.
13. now run superoneclick for root. get that here: http://forum.xda-developers.com/showthread.php?t=803682
14. either play with it in stock, or go find oldmacnut's excellent Better Than Life Rom, and follow the instructions to flash that.
15. enjoy your tab!
Hit me on the thanks button if you find it useful ; )
Sent from my Galaxy Tab using xda premium
That's good advice for some people infinity, but as detailed in the immediately prior post, the OP cannot access Download Mode, rendering your instructions unworkable. Without either Recovery or Download modes, there's not much you can do unless you're willing to try the UnBrickable Mod (search for it).
Hope that helps.
First, thank you to the mods for putting my last post in the right place (and now I know where the right place is).
Anyhoo, my previous problem was a hardware issue that I've had repaired.
Now, this is no longer critical since I bought a replacement phone (Xperia Z if anyone cares) that is happily rooted and running CM. However, I'd still like the S4 rooted with CM and ready to go in an emergency.
The downside of the repair was that the shop I took it too re-flashed it back to stock (I wasn't happy, but hell, it gives me something to do, practically risk free now). Having soft bricked the I9505 three times, I've brought it back to life. However, I'd like to get twrp on there (Honestly, CWM is stepping backwards rather than forwards IMHO, dumbing down to the lowest common denominator). I have the flash files, and for good measure, I have a stock G4 recovery.
Now my problem,. whilst the phone will boot normally without an issue (I said I brought it back from dead), I can't boot to any recovery, either from the phone itself with HW keys, or via adb. It simply sits there at the Samsung logo pretending to boot. This is with both TWRP and stock, so I'm stumped.
I get the Samsung logo, with the little blue too tiny to read text top left, and there it stays. Normal reboot works just peachy with both. Not rooted as best as I can tell (though it should be). i.e. In developer options, none of the root stuff (enhanced reboot, root options etc.) are missing.
So, whilst not critical (it will still be a handy backup phone), any ideas?
you wouldn't have any advanced reboot options unless they were in the rom, and you can't have TWRP without root. maybe the phone shop left you with nothing as a recovery because they forgot ???
In Odin, uncheck everything except f.reset time, flash the tar version of TWRP in Odin, when you see the word "reset" in the status window, remove USB cable from the phone, remove battery, wait 5 seconds, replace battery, use buttons to get into recovery.
Getting into recovery.
*Press the three button combo of vol.up+home+power button
*As soon as Samsung appears relase the combo and in a jiffy press only the volume up+home button.
Hurray! :')
In order:
I've reflashed TWRP, stock, and CWM - all the successful, but same result
No Odin,. Linux user exclusively - so Heimdall
Three button combo starts recovery reboot (the giveaway is the too small to read blue text top left), but there it hangs. Using abd results in the same.
It simply hangs on booting recovery, whichever recovery, but will boot normally without a problem. Tried with and without SIM/SDCard/both/neither.
Probably worth adding, I'm not new to rooting (done it with my last 7 phones, including the one I'm currently using (Xperia Z)), and the S4 was rooted with CM13 before the shop got their hands on it.
After flashing twrp, are you letting the phone auto reboot from Odin?
How many times. Linux user - no Odin (that's Windows) - Heimdall, and it's not just TWRP, it's stock, TWRP and CWM
Personally, recommend trying to flash with Odin. I use Mac OSX myself.
I only have two options for Odin, either via a VM or using wine, and neither lets it detect the phone in download mode.
However, heimdall has always worked well (previously on this phone) so I'm not convinced that's the problem.
Don't know why, but it's finally worked.
How do I mark solved?
Hi Guys,
Long story short, I got the root to work at first, but I was having issues with PlayStore as I couldn't install most of the apps. Then I tried wipe data and restored TWRP backup which didn't fix the problem and lost SuperSU. I tried to reflash SuperSU and failed. Lastly, I did a factory reset via the OS's settings menu and my phone would never boot into System again. I tried using LGUP tool to flash the TOT tool, but it doesn't find my device. My phone is now officially softbricked. Any help is appreciated. I will donate if that is needed
Thanks
alane708 said:
Hi Guys,
Long story short, I got the root to work at first, but I was having issues with PlayStore as I couldn't install most of the apps. Then I tried wipe data and restored TWRP backup which didn't fix the problem and lost SuperSU. I tried to reflash SuperSU and failed. Lastly, I did a factory reset via the OS's settings menu and my phone would never boot into System again. I tried using LGUP tool to flash the TOT tool, but it doesn't find my device. My phone is now officially softbricked. Any help is appreciated. I will donate if that is needed
Thanks
Click to expand...
Click to collapse
I haven't run into this on my V20, but a couple times on my V10 when i'd softbricked my device and couldn't seem to revive it (even with ToT or KDZ files on LGUP) i was able to recover with LG bridge. Basically you go to the third tab titled "software update" but instead of selecting software update, select the "update error recovery" link at the bottom right. It takes awhile but i think it downloads and restores files (or maybe partitions) that other recovery methods don't. Give it a try and let us know if it worked.
jaysonic88 said:
I haven't run into this on my V20, but a couple times on my V10 when i'd softbricked my device and couldn't seem to revive it (even with ToT or KDZ files on LGUP) i was able to recover with LG bridge. Basically you go to the third tab titled "software update" but instead of selecting software update, select the "update error recovery" link at the bottom right. It takes awhile but i think it downloads and restores files (or maybe partitions) that other recovery methods don't. Give it a try and let us know if it worked.
Click to expand...
Click to collapse
LG Bridge doesn't see my device either =(
alane708 said:
LG Bridge doesn't see my device either =(
Click to expand...
Click to collapse
When you plug it in does it even show up in Device Manager on your computer? If so what does it show up as?
jaysonic88 said:
When you plug it in does it even show up in Device Manager on your computer? If so what does it show up as?
Click to expand...
Click to collapse
Yeah windows sees it as a Portable Device (Attached), I can transfer files to it.
This is very similar to what happened to me, I couldn't get into TWRP though.
I could not find a resolution then and still havent, but I did return my phone for a new one.
slayerh4x said:
This is very similar to what happened to me, I couldn't get into TWRP though.
I could not find a resolution then and still havent, but I did return my phone for a new one.
Click to expand...
Click to collapse
Now I wish it was hard bricked so I could exchange for new one.. I don't think they can do it now since it shows I modified it
alane708 said:
Now I wish it was hard bricked so I could exchange for new one.. I don't think they can do it now since it shows I modified it
Click to expand...
Click to collapse
Mine showed the bootloader message and they still took it back.
slayerh4x said:
Mine showed the bootloader message and they still took it back.
Click to expand...
Click to collapse
I guess I can only wait for a custom ROM now
I'm having the same issue. I've tried every step here. I've flashed multiple ROMS, just hoping one would boot and every one keeps booting right back into TWRP after showing the "your device software cannot be checked for corruption...".
PLEASE HELP! LOL...not sure what else to do. I'm, using the latest version of TWRP and I can get into bootloader.
Tried running the "EasyRecowvery.cmd" and it loads fine. I go into twrp and do the format data and then attempt to run any of the options and I get a "This Device doesn't look like a T-Mobile V20. Proceed anyway? I stop and can't get anything. But when it initially ran it said SUCCESS when locating adb .exe and found the device as well omni_h918.
No matter what it continues to go into TWRP. ANY ANY ANY additional help would be great. I want to return this device to T-Mobile before my 14 days is up. Please help out if you can.
mrbigdrawsz said:
I'm having the same issue. I've tried every step here. I've flashed multiple ROMS, just hoping one would boot and every one keeps booting right back into TWRP after showing the "your device software cannot be checked for corruption...".
PLEASE HELP! LOL...not sure what else to do. I'm, using the latest version of TWRP and I can get into bootloader.
Tried running the "EasyRecowvery.cmd" and it loads fine. I go into twrp and do the format data and then attempt to run any of the options and I get a "This Device doesn't look like a T-Mobile V20. Proceed anyway? I stop and can't get anything. But when it initially ran it said SUCCESS when locating adb .exe and found the device as well omni_h918.
No matter what it continues to go into TWRP. ANY ANY ANY additional help would be great. I want to return this device to T-Mobile before my 14 days is up. Please help out if you can.
Click to expand...
Click to collapse
I had this issue on my Verizon variant the other day and I tried everything I could think of. I flashed roms, restored backups, redid the dirtysanta method several times, flashed the boot images in fastboot, and nothing worked. What finally did work (can't make any promises but this worked for me): steps below
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power, as soon as you see the LG logo let go of power for a breif moment and press and hold it until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount button, and reboot system.
This got me out of TWRP and booting normally. I haven't had an issue since.
alane708 said:
Hi Guys,
Long story short, I got the root to work at first, but I was having issues with PlayStore as I couldn't install most of the apps. Then I tried wipe data and restored TWRP backup which didn't fix the problem and lost SuperSU. I tried to reflash SuperSU and failed. Lastly, I did a factory reset via the OS's settings menu and my phone would never boot into System again. I tried using LGUP tool to flash the TOT tool, but it doesn't find my device. My phone is now officially softbricked. Any help is appreciated. I will donate if that is needed
Thanks
Click to expand...
Click to collapse
What variant are you using?
imucarmen said:
I had this issue on my Verizon variant the other day and I tried everything I could think of. I flashed roms, restored backups, redid the dirtysanta method several times, flashed the boot images in fastboot, and nothing worked. What finally did work (can't make any promises but this worked for me): steps below
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power, as soon as you see the LG logo let go of power for a breif moment and press and hold it until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount button, and reboot system.
This got me out of TWRP and booting normally. I haven't had an issue since.
Click to expand...
Click to collapse
You, sir, are a lifesaver. I jumped through all the same hoops as you and was actually starting to panic a little, as the last time I got into a similar string of unsuccessful fixes, I managed to hard brick my Note 2. This worked like a charm on my Verizon variant (the backup part was seemingly unnecessary, as my backup was toast by this point). You definitely have my thanks!
WishRyder said:
You, sir, are a lifesaver. I jumped through all the same hoops as you and was actually starting to panic a little, as the last time I got into a similar string of unsuccessful fixes, I managed to hard brick my Note 2. This worked like a charm on my Verizon variant (the backup part was seemingly unnecessary, as my backup was toast by this point). You definitely have my thanks!
Click to expand...
Click to collapse
Awesome. I was getting a little worried myself when I was stuck in TWRP because I was trying everything I could think of.
I didn't think the backup part was necessary but it's one of those things where you mention everything you did just in case.
check this out https://forum.xda-developers.com/v20/help/lg-v20-access-to-fastboot-t3557328
imucarmen said:
I had this issue on my Verizon variant the other day and I tried everything I could think of. I flashed roms, restored backups, redid the dirtysanta method several times, flashed the boot images in fastboot, and nothing worked. What finally did work (can't make any promises but this worked for me): steps below
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power, as soon as you see the LG logo let go of power for a breif moment and press and hold it until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount button, and reboot system.
This got me out of TWRP and booting normally. I haven't had an issue since.
Click to expand...
Click to collapse
^ This 100% worked for me after my h918 got stuck in recovery after I got a system update message and accidently selected "reboot & install".
Thank you imucarmen!!!!:good::highfive:
OMG thank you so much. Merry Christmas to me. It worked like a charm. Tytyty
imucarmen said:
I had this issue on my Verizon variant the other day and I tried everything I could think of. I flashed roms, restored backups, redid the dirtysanta method several times, flashed the boot images in fastboot, and nothing worked. What finally did work (can't make any promises but this worked for me): steps below
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power, as soon as you see the LG logo let go of power for a breif moment and press and hold it until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount button, and reboot system.
This got me out of TWRP and booting normally. I haven't had an issue since.
Click to expand...
Click to collapse
I had the same issue after rooting with Dirty Santa and have been sweating it for the past hour. Stumbled upon your solution and voila! THANK YOU!!
imucarmen said:
I had this issue on my Verizon variant the other day and I tried everything I could think of. I flashed roms, restored backups, redid the dirtysanta method several times, flashed the boot images in fastboot, and nothing worked. What finally did work (can't make any promises but this worked for me): steps below
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power, as soon as you see the LG logo let go of power for a breif moment and press and hold it until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount button, and reboot system.
This got me out of TWRP and booting normally. I haven't had an issue since.
Click to expand...
Click to collapse
I had some trouble following this at first but it indeed worked.
My v20 was stuck in TWRP (3.0.2-1) after forgetfully hitting OK on the System Update, it was running H91810q and was previously rooted.
I first backed up my phone in TWRP to my SD card and then copied that to my laptop.
In TWRP: Mount > System, I have 3 buttons on the bottom: 'Mount USB Storage', 'Select Storage', and 'Disable MTP'. If I choose 'Mount USB Storage' it goes to the next screen and the only button is Unmount. I cannot get it to shutdown without pulling the battery.
What is missing here is to press Unmount go back to the main TWRP menu, then Reboot > Power Off.
I held Power+VolumeDown, released Power while still holding volume down and I got the white Factory data reset screen. I choose Yes on the next two options to perform the factory reset.
Then it restarted and went back into TWRP. I choose Mount, selected System, pressed Mount USB Storage, then Unmount, Reboot, System.
It booted and took a while since I also flashed the H91810t rom to do an upgrade at the same time from here:
https://forum.xda-developers.com/v20/development/rom-h91810q-stock-rom-twrp-flashable-zip-t3681312
Interesting all my apps, and settings were still on the phone.
THANK YOU FOR SAVING MY PHONE, TIME AND $ !!!
0m3ga said:
I had some trouble following this at first but it indeed worked.
In TWRP: Mount > System, I have 3 buttons on the bottom: 'Mount USB Storage', 'Select Storage', and 'Disable MTP'. If I choose 'Mount USB Storage' it goes to the next screen and the only button is Unmount. I cannot get it to shutdown without pulling the battery.
What is missing here is to press Unmount go back to the main TWRP menu, then Reboot > Power Off.
https://forum.xda-developers.com/v20/development/rom-h91810q-stock-rom-twrp-flashable-zip-t3681312
Interesting all my apps, and settings were still on the phone.
THANK YOU FOR SAVING MY PHONE, TIME AND $ !!!
Click to expand...
Click to collapse
Glad you got it working. As far as the issue with the instructions that could be down to a change in the newer versions of TWRP. I posted this 16 months ago and many new versions of TWRP have come out since. I remember trying to be extremely accurate in my instructions but it is possible I screwed up. Been too long ago and I can't remember now.
Hi, I don't have enough posts to ask this in the actual DirtySanta thread.
I meticulously followed the steps in the DirtySanta thread making sure I had all the correct software, all the pre-requisites, all files in my ADB folder (except SuperSU zip, which is on the SD card on the phone). Suffice it to say that I did all the steps exactly as written in the guide. I was prompted when to run the next batch files each time, etc. Entered the proper commands in the terminal utility, and so on. Everything as written.
After clicking on step3.bat, the phone immediately rebooted to a Fastboot screen. In the meantime, the batch files disappeared off my desktop.
So, for the past 15 minutes or so the phone has been sitting on Fastboot and vibrating away.
Here's what I see in the small Fastboot screen:
Fastboot Mode (in red)
stuff like Product_name, Variant, HW_Version, etc. up until it says LOCK_STATE.
Ok, after all of that basic stuff, it says:
[1090]
[1140] Fastboot mode started
[1670] fastboot: processing commands
[17600] usb_read() transaction failed; txn_status= -1
[17650] usb_read: DONE: ERROR len=64
[1700] fastboot: oops!
[17750] fastboot: processing commands
And that's where it sits, doing seemingly nothing and vibrating away.
Can anyone assist?
Try a different usb port. then rerun step 3.
me2151 said:
Try a different usb port. then rerun step 3.
Click to expand...
Click to collapse
Will do...was just thinking of doing that since it said "usb read error". Will report back.
Heyitsrick said:
Will do...was just thinking of doing that since it said "usb read error". Will report back.
Click to expand...
Click to collapse
First off, a big thanks for helping me.
Update: OK, changing the USB port worked I re-ran Step3.bat. I have made it through getting to TWRP, and have done these steps:
Verizon(VS995) and ATT(H910):
4.1) Flash SuperSU.zip
4.2) Go back to Main-menu > Wipe > [Format Data] > Type ?Yes?
4.3) Go back to Wipe > Advanced > Check Dalvik, Data and Cache > Slide to wipe
4.4) Go back to Main-menu > Reboot > System
So, with that all complete, it's rebooted to a Verizon screen (horizontal progress dots) and a low buzzing.
I did try what you mentioned in the guide to get over the wait time by pulling the battery, reinserting with vol down key pressed and re-attaching the USB to flash boot2.img via fastboot, but it didn't get back to fastboot after the battery/voldown/usb. It went back to the same Verizon screen after the obligatory "Corrupt" screen came on.
Can I assume that I can wait this out for 20 minutes, or did I miss something in how to interrupt this waiting period for first setup? I do want to (and know I have to) flash boot2.img.
EDIT: wasn't holding vol key down long enough to get into fastboot. Doh. Just flashed boot2.img and rebooted.
Looks like I made it! It's at the "Prepare your Phone Screen". Fingers crossed.
Heyitsrick said:
Looks like I made it! It's at the "Prepare your Phone Screen". Fingers crossed.
Click to expand...
Click to collapse
Are you still stuck?
I ran into this EXACT same issue on my brand new Verizon v20 on step 3 (both 13a and 12a firmware gave me this issue) and I had to figure out my own solution, even tho I read that 'dirty santa root' thread a thousand times front to back.... (no disrepsect to the OP/Devs of that thread btw!)
Anyways, below, is the link to my solution on my brand new Verizon v20, in case you're still stuck. I've actually reflashed (via LGUP) back to stock a couple times, then re-root/unlock to test out 13a and 12a firmwares to benchmark various battery life/performance markers for a tech site I write for. Ultimately, I have to go through the exact same steps everytime for my Verizon v20.
I know I wasn't too specific in my post below... but if you have any questions, don't hesitate to ask
https://forum.xda-developers.com/showpost.php?p=71371141&postcount=24
NegativeX said:
Are you still stuck?
I ran into this EXACT same issue on my brand new Verizon v20 on step 3 (both 13a and 12a firmware gave me this issue) and I had to figure out my own solution, even tho I read that 'dirty santa root' thread a thousand times front to back.... (no disrepsect to the OP/Devs of that thread btw!)
Anyways, below, is the link to my solution on my brand new Verizon v20, in case you're still stuck. I've actually reflashed (via LGUP) back to stock a couple times, then re-root/unlock to test out 13a and 12a firmwares to benchmark various battery life/performance markers for a tech site I write for. Ultimately, I have to go through the exact same steps everytime for my Verizon v20.
I know I wasn't too specific in my post below... but if you have any questions, don't hesitate to ask
https://forum.xda-developers.com/showpost.php?p=71371141&postcount=24
Click to expand...
Click to collapse
I read your "fix" post to see exactly where you got stuck, as I got stuck first due to the USB port not being able to work correctly and had to switch USB ports on my pc before I could re-run step3.bat.
I see now that you're talking about the long Verizon logo screen with progress dots issue after rebooting post-running step3.bat that I ran into, as well.
OK, what worked for me was much easier in the end than what you did. After step3.bat and the reboot, it would just sit there on the Verizon logo with the progress dots, as you know. There is a notation on the first page of the DirtySanta thread that in order to get around this, unplug the USB cable and remove the battery.
This is the actual note from the DirtySanta thread for Verizon users with the long Logo screen issue:
*****VERIZON USERS******
It has come to my attention that some users have encountered abnormally long first boot time(over 20 minutes before first time setup)
To resolve this issue:
Boot into bootloader by pulling the battery and reinserting it and holding VOL- and phugging in the phone. then typing:
Code:
fastboot flash boot boot2.img
fastboot reboot
**************
Click to expand...
Click to collapse
Once I removed the battery and usb cable, the phone was completely off, of course. Then, I just needed to get it back into "fastboot" on the phone, itself, in order to flash boot2.img via ADB on the PC. When the phone was on the never-ending Logo screen with progress dots, I found that ADB could see the phone ok via the adb devices command, but if I tried to flash anything at that point, it would just say something like "pending", as if it were waiting for the device to be free to flash. So, that wasn't going to work, obviously. I needed the phone to be in the flashboot screen, not the logo screen. I did a ctrl-c to cancel out of the adb flash command, and then set out to pull the battery/usb cable and then reconnect the battery, and while holding the Vol Down button reinserting the USB cable.
The first time I tried this, it booted up fine, but it went right back to the Logo screen. Doh! I figured perhaps I wasn't waiting long enough with the Volume Down button so I tried it again. What happened the first time when it rebooted to the Logo screen is I released the Volume Down button the moment the phone started to turn on (you feel the vibration). That's when it booted back to the Logo. This second time, I removed the battery again while it was on that never-ending Logo screen to power it off and disconnected the USB cable again. I put the battery back in, then with the Volume Down button pressed down, I reconnected the USB cable. The difference this time is that I did not release the Volume Down button this time UNTIL I saw it was in the Fastboot screen and not the Verizon Logo.
So, at this point the phone was on the Fastboot screen and I saw it was it was ready to go, so I initiated the ADB command to flash boot2.img. It went through its paces and once it got back to the ADB command prompt, I did an ADB Fastboot Reboot command. It rebooted, first with the obligatory corrupt warning, then the Verizon Logo and progress dots, but then after a short while I got the "Hello" screen in red and I knew it was actually going to finish. Whew! Relief! At that point I was eventually at the phone's setup screen for a new user, and I finished setting up the phone, reinstalling apps, etc.
One caveat in this: I don't know why, but even though I had gone through all the steps in "4" section of the instructions, when I checked Root, I wasn't rooted! Huh?
In other words, I had already gone through this part:
Verizon(VS995) and ATT(H910):
4.1) Flash SuperSU.zip
4.2) Go back to Main-menu > Wipe > [Format Data] > Type ?Yes?
4.3) Go back to Wipe > Advanced > Check Dalvik, Data and Cache > Slide to wipe
4.4) Go back to Main-menu > Reboot > System
Click to expand...
Click to collapse
After setting up the phone and reinstalling my apps, I opened up the SuperSU app, and it said there was no executable installed. In other words, it didn't recognize that I had flashed it in step 4.1. Perhaps flashing boot2.img overwrote that? Not sure, but at this point, I set about to figure out how to boot into TWRP Recovery on the phone (not fastboot) to flash it from there (again).
It took me a while to find the instructions on how to boot into TWRP, lol, and it's a little unnerving that before it boots to TWRPyou are warned that all your data is going to be overwritten before you can boot to it, but it did get me back into TWRP. Once in TWRP, I re-flashed Supersu-blahblah.zip and rebooted via the system reboot. (did not wipe any caches again, though).
After reboot, I checked root again, and this time after a bit SuperSu brought up the permissions screen for the Root app that I had to allow, and it brought back a successful Root message.
I then set about to do what I really wanted to do with root - bypass the Verizon entitlement check for hotspot usage, and got that working fine.
All in all, I have to say this was the diciest rooting I've ever had to go through. I guess that's because of Nougat and that there can't be (at least not yet) a "one-click" root. But man, was I worried when I was at the point where I first posted in this thread. I bought this phone as a "new-resale" (never used) phone from Swappa.com for $450, so if I bricked it, I was out of luck. But it seems to be ok now.
Heyitsrick said:
I read your "fix" post to see exactly where you got stuck, as I got stuck first due to the USB port not being able to work correctly and had to switch USB ports on my pc before I could re-run step3.bat.
I see now that you're talking about the long Verizon logo screen with progress dots issue after rebooting post-running step3.bat that I ran into, as well.
OK, what worked for me was much easier in the end than what you did. After step3.bat and the reboot, it would just sit there on the Verizon logo with the progress dots, as you know. There is a notation on the first page of the DirtySanta thread that in order to get around this, unplug the USB cable and remove the battery.
This is the actual note from the DirtySanta thread for Verizon users with the long Logo screen issue:
Once I removed the battery and usb cable, the phone was completely off, of course. Then, I just needed to get it back into "fastboot" on the phone, itself, in order to flash boot2.img via ADB on the PC. When the phone was on the never-ending Logo screen with progress dots, I found that ADB could see the phone ok via the adb devices command, but if I tried to flash anything at that point, it would just say something like "pending", as if it were waiting for the device to be free to flash. So, that wasn't going to work, obviously. I needed the phone to be in the flashboot screen, not the logo screen. I did a ctrl-c to cancel out of the adb flash command, and then set out to pull the battery/usb cable and then reconnect the battery, and while holding the Vol Down button reinserting the USB cable.
Click to expand...
Click to collapse
I saw that 'fix' and it never worked for me at the point in the rooting process I was in... sadly. You have to be able to even get to TWRP, do the SU install then format/wipe, then you can flash the boot2.img to speed up the booting process. In my case, I was never able to even get to TWRP. Trying to flash boot2.img before being able to get to TWRP, would soft brick my phone with the 'password' screen on bootup and I was never able to get around it, requiring me to LGUP back to stock and try again. Luckily I was able to still figure it out.
As you said, definitely the 'diceist' rooting process I've ever encountered... and I've been rooting phones since the original Motorola Droid 1/Milestone phone. Good times tho! Haha
NegativeX said:
I saw that 'fix' and it never worked for me at the point in the rooting process I was in... sadly. You have to be able to even get to TWRP, do the SU install then format/wipe, then you can flash the boot2.img to speed up the booting process. In my case, I was never able to even get to TWRP. Trying to flash boot2.img before being able to get to TWRP, would soft brick my phone with the 'password' screen on bootup and I was never able to get around it, requiring me to LGUP back to stock and try again. Luckily I was able to still figure it out.
As you said, definitely the 'diceist' rooting process I've ever encountered... and I've been rooting phones since the original Motorola Droid 1/Milestone phone. Good times tho! Haha
Click to expand...
Click to collapse
Late response - sorry.
There must be something we each did differently, as we both have the same phones, same carrier, same software revision (13a). I was able to get to TWRP via the button method on the phone. Didn't use ADB for that. I was presented with an ominous white screen about all files will be wiped/deleted, but when accepting that (and hoping for the best, lol), it just went to TWRP. So, again...something or some step(s) must be done differently to get to that point on your end from what I did.
I'm guessing you're through with doing the flashing on this thing, so this is all moot now.
Hey guys i actually was having the same issues as you were now however after the SU install the wipe etc i reboot to TWRP no matter what i do even when i restart through bootloader or take the battery off it keeps booting to the same place instead to the verizon wizard help please
kratos380 said:
Hey guys i actually was having the same issues as you were now however after the SU install the wipe etc i reboot to TWRP no matter what i do even when i restart through bootloader or take the battery off it keeps booting to the same place instead to the verizon wizard help please
Click to expand...
Click to collapse
Called a twrp loop. Easy fix. Been posted a lot. Look around for it
me2151 said:
Called a twrp loop. Easy fix. Been posted a lot. Look around for it
Click to expand...
Click to collapse
I have been looking for 2 days haha literally have like 30 tabs open shifting through i dont know what to do next, i backed up wiped my cache data etc installed SU which had no problems wiped again/ rebooted system and back to twrp, i read that you might need to flash a system.img but i dont know where to find one, would appreciate the help kind sir
kratos380 said:
I have been looking for 2 days haha literally have like 30 tabs open shifting through i dont know what to do next, i backed up wiped my cache data etc installed SU which had no problems wiped again/ rebooted system and back to twrp, i read that you might need to flash a system.img but i dont know where to find one, would appreciate the help kind sir
Click to expand...
Click to collapse
Look at team digitals ROM thread. Stockish one. Look at post 3. If you still can't find it I'll quote it directly later. I'm busy right now
me2151 said:
Look at team digitals ROM thread. Stockish one. Look at post 3. If you still can't find it I'll quote it directly later. I'm busy right now
Click to expand...
Click to collapse
Couldnt find it sorry im new to this forum please link it when you are free thanks again for the help much appreciated
kratos380 said:
Couldnt find it sorry im new to this forum please link it when you are free thanks again for the help much appreciated
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=70393155&postcount=3
Sorry for the constant posts but i followed the steps on that thread, deleted the misc/fota files and it stopped it going to twrp and booted to the lg logo with the black screen, i waited there for about 2-3 hours to no avail rebooted into bootloader tried the fastboot img 2 and the same thing happened it was just stuck at the lg logo now when it boots to the fastboot screen however adb doesnt recognize the device anymore but fastboot does. Is it time to kdz and start over ?
There are lots of root and recovery guides here, so why am I posting this? Well, because I tried them, and they either didn't work or were outdated. Also, the install instructions on Lineage OS's site flat out wouldn't work. So here's how I did it!
These instructions are for Windows users, and uses Odin not Heimdall. I'm using Windows 10 Pro. I can't guarantee that it will work on other versions, but I can't see why it wouldn't. YMMV on other versions. I tried Heimdall and no matter what I did, I could not get it to flash anything to my tablet. After much google-fu, I found several people saying Heimdall is broken. I don't know if it is, but it wouldn't work for my on Windows or on Debian linux. So this install uses Odin, which was super easy and I wished I'd have done it in the first place and saved a ton of time and frustration messing around.
For those of you that know what you're doing already, here's the short version:
Enable OEM Unlock in the Developer settings of your stock Samsung OS.
Download TWRP recovery image (the .img.tar version, not the .img version), Lineage OS zip, Lineage Add-on SU zip, Gapps, and Odin (latest versions of all - links are below in the more detailed instructions)
Make sure your stock OS tablet can be seen by your PC - you can copy files back and forth between them. Copy over the Lineage OS, Add-on SU, and Gapps files to your tablet's SD card.
Boot your tablet into Download Mode (Home + Power + Volume Down), tap Vol Up to accept the warning message.
Open Odin on your PC, then plug in your tablet to the PC, note the green COM port number.
Open the Options tab of Odin and make sure the ONLY option checked is the F. Reset Time option. (You don't want it to auto-reboot, and you definitely do NOT want it to re-partition anything).
Click the AP button in Odin and select your TWRP image file. Then click Start in Odin to flash it.
When it's done flashing, disconnect the USB cable from the tablet and exit Download Mode (hold Power + Home + Vol Down), but release them as soon as the screen goes blank and switch to Power + Home + Volume Up so that it boots into recovery. If you miss it, booting into the stock OS will wipe out the TWRP recovery and you'll have to flash it again with Odin.
Once in TWRP recovery, flash the lineage OS file, the add-on-su file, and the gapps file. If asked about encryption, go ahead and tell it to wipe everything out. It's going to wipe your data partition anyway, and if you don't it will screw things up and you'll end up locking TWRP out of the data partition. This can be resolved by rebooting into Recovery and using TWRP to wipe the data partition and then flashing the lineage OS, add-on, and gapps files again.
Once you've flashed lineage OS, add-on-su, and gapps, go ahead and use the on-screen option to wipe the cache and davlik partitions, then reboot into the system.
The first boot will take some time, so go get a beer/coffee/soda and relax. Once it is booted up, it will take you through the Lineage OS setup.
After you complete the setup, you can enable Root on this device by going into Developer Options (under Settings > System > Advanced > Developer Options) and tapping Root Access and selecting from Disabled, Apps Only, ADB Only, Apps and ADB options.
Notes (lessons learned):
Don't flash any of Chainfire's SuperSU packages. They won't work with Lineage OS and will goober up the add-on-su package install. I had to wipe my device and reinstall Lineage from scratch (with the add-on-su and not Chainfire's SuperSU) before mine would work.
Also, I ran into trouble with the encryption of the Data partition. I can't remember the exact sequence of events, but there was a selection when I was installing Lineage for the first time about the encryption of the partition, and apparently I chose wrong. The OS didn't install, it didn't boot right, and TWRP refused to mount the Data partition. I had to reboot into recovery (from recovery) and use TWRP to wipe the Data partition, then reflash lineage OS, add-on-su, and gapps. Then it worked fine.
The LONG Version (more detailed instructions):
Step 1) Gather the files you'll need:
Go to lineage's site and grab the latest OS version. Currently that's v16.0 (Android v9.0 Pie)
https://download.lineageos.org/gts28vewifi
Go to lineage's site and grab the add-on-SU package. Get the arm64 one (second from the top) named addonsu-16.0-arm64-signed.zip
https://download.lineageos.org/extras
Go to Team Win's site and download the twrp package for the Samsung Galaxy Tab S2 8.0 (known as "gts28vewifi" on most of these sites). Be sure to grab the .img.tar version of the file, NOT the .img version.
https://dl.twrp.me/gts28vewifi/
Go to the Odin website and download the latest version of Odin. (At the time of this writing, it is v3.13.1) Note there are links there for multiple versions. I used v3.12.3, but v3.13.1 will work too.
https://odindownload.com/
Go to the OpenGapps.org site and grab the nano version of Gapps. Be sure to select ARM64 for the platform, v9.0 for the Android version, and nano for the variant. (You can choose any variant you like. I used nano. If you know what you're choosing, go for it.)
https://opengapps.org/
Step 2) Enable OEM Unlock on your tablet
On your tablet, go into the Developer settings and enable OEM Unlock. (If you don't have Developer settings in your Settings menu, go to About Tablet and tap the Build Number several times in a row. (As you tap it, it will countdown the number of taps until Developer mode is turned on. Once you've tapped it seven or so times, you can go back to the Settings menu and there will be a new entry there Developer settings. The OEM Unlock is in there, enable it.
Also, back up your tablet contents, because this will wipe your tablet's internal storage (not your SD card though). How you backup is up to you and beyond the scope of this post.
Step 3) Get a good quality/reliable USB-to-micro-USB cable (one came with your tablet).
Using a cheap cable will cause you headaches, and you don't won't to be flashing your recovery partition using a lousy cable.
Step4) Copy the needed files to your tablet's SD card.
In my case, those files were:
lineage-16.0-20190523-nightly-gts28vewifi-signed.zip (517MB)
addonsu-15.1-arm64-signed.zip (1MB)
open_gapps-arm64-9.0-nano-20190529.zip (175MB)
Do not copy it to the tablet's internal storage, as that's gonna get wiped out. You can make a new folder on the SD card or just put it in the root of the card. The simplest way to do this is to have your tablet powered up under the original factory OS and just plug it into your PC with the USB-to-micro-USB cable. It will appear in Windows as a device with two "folders" in it - one for internal storage and one for the SD card. Just drag and drop the files over.
Step 5) Let's flash that recovery! (this is the tricky part):
Make sure your tablet has at least 75% charge before you begin this step. If it doesn't charge it until it does.
Disconnect your tablet from your PC. (unplug the USB cable)
Unzip Odin to a folder - it doesn't really matter where, I put mine on my Desktop. It is handy if you copy the twrp .img.tar file into the Odin folder, but not necessary. When I started Odin, I right-clicked on it and clicked Run As Administrator, then clicked Yes to the windows pop-up. I probably did NOT need to do this, but I didn't want anything getting in the way when it came time to flash the recovery partition of my tablet.
With Odin open, you'll notice that all the blocks across the top are greyed out and blank. That's good because we haven't done anything yet. Notice the left-most small grey block has ID:COM written above it. When you plug in your tablet, it will show what COM port your tablet is on.
Before you plug in your tablet, you need to boot it into Download Mode. To do so, power off the tablet. Then hold the Home button, the Volume Down button, and the Power button at the same time. Within a few seconds, it will boot into a light blue screen that warns you about the dangers you are about to embark upon. Let go of the three buttons you're holding and tap the Volume Up button to let it know that you've got this and you're gonna make this tablet submit to your will! Once you press the Volume Up button, it will go to another light blue screen that says Download and has a message about not turning off the device.
Once you're at that light blue Download screen, you can plug your tablet into your PC with the USB cable. Almost immediately, the ID:COM box should turn green and show a com port number, such as COM4. If you don't get anything give it a minute. If nothing happens, then you may need to install drivers for your tablet. The easy way to do that is to install Samsung's official PC application. It used to be Kies, but now it is called Smart Switch. You can download it here:
https://www.samsung.com/us/support/owners/app/smart-switch
If you need to install Smart Switch, close Odin and unplug the USB from your tablet. Take the tablet out of Download Mode while you take care of business installing Smart Switch. To get the tablet out of Download Mode hold the Home, Volume Down, and Power buttons at the same time for about 10 seconds. When the light blue screen goes away release the buttons or you'll end up back in Download Mode.
After installing Smart Switch, plug in your tablet via USB (make sure it is booted up in the stock OS, not in Download Mode) and make sure your PC detects the tablet and that you can copy files to/from the tablet. When it does, you're ready to disconnect the USB to the tablet and boot the tablet into Download Mode again. Then start Odin, then plug in the USB to the tablet and see if you get a nice green com port showing.
Now that you've got Odin running, the tablet connected, and the com port showing green, you're ready to flash TWRP. Click the AP button in Odin, which will open a standard Windows open-a-file window. Navigate to where you saved the twrp .img.tar file (in my case it was named twrp-3.3.1-0-gts28vewifi.img.tar). Select that file and click OK. Now the Odin window will show the location/filename of your twrp file next to the AP button.
On the left side of the Odin window, click on the Options tab. By default the Auto Reboot and F. Reset Time options will be checked. Uncheck the Auto Reboot option and MAKE SURE THE F. RESET TIME OPTION IS THE ONLY OPTION CHECKED!
Now you're ready to click the Start button which is what flashes the TWRP recovery to your tablet. Go ahead and click Start. The flash will take about 20 seconds or so, and when it is done, the grey blocks above the ID:COM block will be green and will say PASS and have a time under it. (It might have said OK instead of PASS, I can't remember now...) Anyway, you'll know it was OK because its green. If the flash did not work, it will be red and say FAIL! If it fails, make sure you specified the twrp .img.tar file with the AP button and NOT a twrp .img file. (common mistake - .img.tar files are for Odin and .img files are for Heimdall) You can also try rebooting your tablet back into Download Mode, and make sure it is seen by Odin (Odin shows the com port in green).
Assuming that Odin is green and OK, you're ready to unplug the tablet from the PC.
The next step is a little tricky so get your head right before you do it. You're going to reboot the tablet out of Download Mode and directly into Recovery. It is important that you do NOT allow the tablet to boot as normal into the OS. (That's because the stock OS will see that your recovery partition has been changed and it will change it back to the stock recovery and you'd have to start over and flash twrp again.). To make this happen correctly you have to hold the Home + Power +Volume Down at the same time, BUT as soon as the light blue screen goes away, let all three go, then hold Home + Power + Volume Up! So you're basically switching one finger from Volume Down to Volume Up. It may sound tricky, but it really isn't. Just be sure to switch as soon as the light blue screen goes away. Worst case, you miss it and it boots back into the factory OS and you have to do this whole step over again.
Step 6) Time to flash the OS and other goodies!
Once you completed the above step and successfully booted into TWRP recovery, you've completed the tricky parts. The rest is rather simple and done entirely on the tablet.
In TWRP Recovery tap the Install button. Tap the Select Storage button at the bottom. Select MicroSD from the list and tap OK. Now use the folder structure on-screen to navigate to where you saved the lineage OS, add-on-su, and gapps files. If you're smart, you saved them to the root of the SD card and they're already listed on the screen. Tap the Lineage OS file first (in my case it was the lineage-16.0-20190523-nightly-gts28vewifi-signed.zip file). The screen will change and have an Add More Zips button, tap it. Tap the add-on-su file (addonsu-15.1-arm64-signed.zip) and tap Add More Zips, and tap the Gapps file (open_gapps-arm64-9.0-nano-20190529.zip). Now you're ready to flash, so swipe the bar at the bottom to the right. It will start the flash and this will take a few minutes.
Now, I apologize for this next part, I didn't write down exactly what happened... but the gist of it is: the Data partition of my tablet was encrypted (according to TWRP, I hadn't encrypted it via the stock OS), and that messed up the flash. TWRP asked me about the encryption but I was unclear what option to pick. Obviously I picked wrong, because the result was that the flash didn't work, and the Data partition of my tablet was unwritable/unmountable for TWRP and the process blew a bunch of errors. The good part is that the fix was simple. I rebooted from TWRP back into TWRP (tap Reboot then tap Recovery). After rebooting back into TWRP, I tapped Wipe, then Advanced Wipe, checked the Data partition and swiped right. It wiped the encrypted Data partition, and I flashed the lineago OS, add-on-su, and gapps files again. That time it went perfectly. So, if you're reading this now, you may just want to save yourself a little bit of time and before you try to flash the first time, wipe the Data partition. Warning: there's no going back from this, your Data partition will be blank, so be sure to have backed it up before you started down this road, or be ready to proceed with flashing Lineage OS and don't look back.
When the flash process is complete (and error free), go ahead and tap the option to wipe your cache and davlik partitions, then reboot. Both options are on the screen that shows right after the flash process.
Step 7) Let it boot into Lineage OS and enable Root (or not)!
The first boot will take some time, so go get a drink and be patient. It didn't take a whole 10 minutes, but it seemed like it. Once it boots, it will take you through the Lineage/Android setup process. Go ahead through that, then if you want Root, go to Settings > About Tablet and tap the build number seven times, it will do a countdown as you tap to turn on Developer Mode. Hit the back button, tap System > Advanced > Developer Options and scroll down until you find Root Access. Tap it and select from the options: Disabled, Apps Only, ADB Only, Apps and ADB. I suggest Apps Only, as I don't need ADB. YMMV. You now have a rooted Samsung Galaxt Tab S2 with Lineage OS and TWRP. Congrats!
I seem to have painted myself into a corner. After the flashing step apparently I encountered the encryption problem, too. However, no matter what I try I cannot wipe the data partition. I just fails every time. I can get into TWRP. But if I let it try to boot normally I get an error that it needs a factory reset. Even letting it do that doesn't seem to help. Not sure what my next step should be.
EDIT:
Oh wait, I think I got it. What I did in this state was power off (using power button) and choose power off from the menu that pops up. Then I rebooted back into TWRP. Before I tried anything else I chose to format data then wipe data (probably redundant but I don't care). Then I reflashed the 3 packages. That seems to work now...
EDIT 2:
So yeah it did work. Thanks so much! I haven't had a rooted Android device in years. Nice to have that ability back. Wish I could do that to my phone (Verizon S10+).
Will this work for Tab S2 9.7 T813 too? What is the device name of it? gts210vewifi is that correct? So I just have to download the TWRP for gts210vewifi and follow the same guide? What is different to your guide compared to the Lineage OS guide https://wiki.lineageos.org/devices/gts210vewifi/install ?
First of all, thank you very much for this detailed post. Worked like a charm on my client's T713.
The only thing I cannot do is enable encryption, it just reboots the phone. I've tried everything and am running into brick walls. My guy needs to get on work VPN, so encryption is a must. If anyone has an idea, please chime in, I'd be indebted to you.
I keep getting an error 255 and then I read you need to flash a 64 bit rom with an unofficial 64 bit twrp, which I can't find. Anyone know where I can find it or a link? Thanks.
To those having Error 7 while flashing, Open the updater-script file and add TZ.BF.3.0.3-00021 (If you android 6.0) or delete the assert lines altogether.
Man, I followed your instruction word in word and I didn't a single problem upgrading my Tab S2 713 from 7.0 stock to Lineage 16.0. I really appreciate the detailed instruction on how to do this.
Hey there. Found this guide as I recently got a tab s2 and it's very well written, but one step is really hard and it's the whole "boot into recovery from download mode". Whatever I try I can't get it to work.
I assume when you say to hold the Download mode combo (pwr+home+volDown) you mean while the screen is blue with the message "Downloading....". I do this and as soon as the screen turns off I switch to recovery combo (pwr+home+volUp) but I always land at the "Samsung Galaxy Tab S2" screen and it just stays there.
Is there a way to completely turn OFF the tablet from Download mode so I can start into recovery easier? I don't know why it's not working for me tbh. I've tried timing it, tried being a second earlier, later, whatever. Always the same thing. I fear I might be doing something wrong tbh.
(A note: I don't have the "enable unlock OEM" option in my developer options but apparently that means I don't need to enable it. Odin works just fine and I get a pass after 3 seconds. Oh, and my KNOX WARRANTY VOID: went from 0 to 1 so I assume it worked).
EDIT: I want to add my TabS2 is model SM-T815, in case that matters.
One must not click "install TWRP" or it will boot loop into recovery after loading the OS. This is very frustrating, make sure you do not load the TWRP app when installing!
Hope this saves someone time.
Thanks for this post! SUPER helpful.
any guide on how to enable encryption ?
I already format data using twrp 3.2.3.
I did that and now cannot get out of it. UGH
---------- Post added at 06:46 AM ---------- Previous post was at 06:18 AM ----------
avongil911 said:
One must not click "install TWRP" or it will boot loop into recovery after loading the OS. This is very frustrating, make sure you do not load the TWRP app when installing!
Hope this saves someone time.
Click to expand...
Click to collapse
Any way to fix this? I screwed up and installed it.
Hi
Very detailed guide.
I am writing to ask for your help:
I managed to boot into TWRP after ODIN, but it seems i am unable to access micro sd card. There is the option micro sd but i can't select it. As a result, i can't flash lineage.
I click install - select storage -
Internal storage (0mb)
MicroSd (0mb)
USB OTG (0mb)
Do you have any ideas?
I have the lineageos files,gapps to sd card.
Should i proceed with TWRP--> Wipe, then Advanced Wipe-> Data partition -- swipe right, then should i able to access the sd card?
Edit: just tried wipe - advanced wipe - data - and i get Wipe complete: FAILED
could not mount/data and unable to find crypto footer.
Failed to mounf /data (invalid argument)
unable to recreate /data/media folder
Unable to mount storage
Hello. Does the fingerprint scanner work with lineage os ? Thanks in advance!
Edit: yes it does, found it
---------- Post added at 02:48 PM ---------- Previous post was at 01:50 PM ----------
First time i got the failed to mount /data error.
I fixed it like this
Press back at recovery.
=> Wipe
=>advance wipe
=>check data
=>repair or change file system
=>ext2
swipe right
now go back, change file system again to ext4.
Now just install as per OPs instructions and all will be great.
morfeas-dsl- said:
Hello. Does the fingerprint scanner work with lineage os ? Thanks in advance!
Edit: yes it does, found it
---------- Post added at 02:48 PM ---------- Previous post was at 01:50 PM ----------
Mine always fails with too many tries, so I just use a PIN.
Click to expand...
Click to collapse
lloydsw said:
morfeas-dsl- said:
Hello. Does the fingerprint scanner work with lineage os ? Thanks in advance!
Edit: yes it does, found it
---------- Post added at 02:48 PM ---------- Previous post was at 01:50 PM ----------
Mine always fails with too many tries, so I just use a PIN.
Click to expand...
Click to collapse
Try registering your fingerprint from different angles and sideways.
Click to expand...
Click to collapse
So I have one issue, my father was given one by an older gentleman from his work its a brand new looking 713 it has been registered. however, the man does not remember what account nor the perspective password for this tablet, will this work without enabling OEM unlock? if not it goes back to being a fancy paperweight once again.
Sadly, it seem the OEM Unlock is blocked out for me on my S2 with July 2018 as the last update for it, Tried the change date back and auto off steps and such several times but it just does not appear, guess Samsung for even more greedy and blocked that method, so nice of them to make a $600 tablet a paper weight with a 3 year old OS stuck on it..Last time i buy a Samsung device.
morfeas-dsl- said:
lloydsw said:
Try registering your fingerprint from different angles and sideways.
Click to expand...
Click to collapse
Worked! Thanks you!
Click to expand...
Click to collapse
Hello! Could I flash only TWRP and Magisk following this guide? I have Android 7.
I'd like also to know if the tablet would get formatted during these operations thank you in advance!