Database Users

Rooted, Custom Rom a huge fail

Hello dear Community!
It is depressing that my first appearance here is to ask for help, but I am going crazy.
So, I tried to Root my phone via Odin + CF Autoroot klte and it seemed to have been a success.
The root checker also said, that my device was rooted so I went on and installed TWRP to be able to install Lineage OS.
After getting Lineage to work I got a few error messages suddenly popping up, telling me that either "Music had stopped" or other android operation were closed because they didn't work properly.
I tried to install Gapps, it seemed to have worked but I was only able to open and enter the store once, afterwards the store never managed to load and then the app closed itself after starting it.
So I checked again with Root Checker, but this time it gave me an error message, too. It said, that my device was not rooted properly.
I guess this is were I made it worse by deciding to just root the phone again. Obviously, it didn't work either.
Afterwards I thought that maybe installing The Original Android OS and then unrooting the phone would be the best solution to be able to start anew.
First I tried to flah Lineage again and that made it impossible for me to boot the phone. The farthest I got was the setup page, were it tells you Hello and were you can choose a Language, but clicking the arrow key didn't do anything at all.
The recovery mode was also not the TWRP one anymore, but the original Android one and that was a huge problem for me.
Then I tried to flash the 6.1 OS for the S5 (I made sure it was the correct version), but now it is stuck at the "Samsung" screen while it boots.
It never boots though.
I don't know what to do anymore.
Please, I beg you, could anyone help me out?

Don't flash the latest Lineage OS ROM
Hello AsylumAlice u shouldn't have flashed the latest Lineage OS ROM because now u will need a new motherboard for your S5 since the ROM corrupts the MMC chip now u will need to get a new MMC chip or a new Motherboard sorry that your s5 is now hard bricked but when u get it fixed flash the DreamUX S8 Rom it works flawless on my S5 SM-G900i
Yours Sincely
Matty Bourke

mattybourke1994 said:
Hello AsylumAlice u shouldn't have flashed the latest Lineage OS ROM because now u will need a new motherboard for your S5 since the ROM corrupts the MMC chip now u will need to get a new MMC chip or a new Motherboard sorry that your s5 is now hard bricked but when u get it fixed flash the DreamUX S8 Rom it works flawless on my S5 SM-G900i
Yours Sincely
Matty Bourke
Click to expand...
Click to collapse
What are the grounds for your claims?
You needn't root via CF-autoroot if your end goal was to flash lineage. CF autoroot was intended to root stock roms with ease and less effort.
Flash The LATEST, official TWRP via odin then do a FULL WIPE. Wipe system, data, cache and dalvik cache.
From here on, you have two options:
1.) Sideload the LineageOS rom via ADB
2.) Transfer it to the phone's storage via MTP and flash it from TWRP.
As for how to accomplish this, the forum search bar and Google has your back. You need only choose one procedure.
If you need the Play Store, flash gapps AFTER flashing LINEAGE AND BEFORE REBOOTING.
Since you were under the idea that utilizing CF-autoroot was a necessity, I suggest that you re-read this post thoroughly before actually putting it into practice.

Kinloch said:
What are the grounds for your claims?
You needn't root via CF-autoroot if your end goal was to flash lineage. CF autoroot was intended to root stock roms with ease and less effort.
Flash The LATEST, official TWRP via odin then do a FULL WIPE. Wipe system, data, cache and dalvik cache.
From here on, you have two options:
1.) Sideload the LineageOS rom via ADB
2.) Transfer it to the phone's storage via MTP and flash it from TWRP.
As for how to accomplish this, the forum search bar and Google has your back. You need only choose one procedure.
If you need the Play Store, flash gapps AFTER flashing LINEAGE AND BEFORE REBOOTING.
Since you were under the idea that utilizing CF-autoroot was a necessity, I suggest that you re-read this post thoroughly before actually putting it into practice.
Click to expand...
Click to collapse
Thank you so much for your fast reply!
-> I flashed the newest Version for klte via Odin, but I can't get into the boot mode.
I only am able to enter the download mode. What can I do now?

Flash TWRP via odin again, untick the Auto-Reset option of Odin first. Then try booting to recovery via long holding the power, home and volume up button simultaneously without releasing any of the buttons until you successfully see the TWRP splash screen.
If that still doesn't work, reboot to recovery via adb from download mode. You need the adb and the usb drivers for your device.
If that still doesn't work, you might have flashed an incompatible version of TWRP.

Kinloch said:
Flash TWRP via odin again, untick the Auto-Reset option of Odin first. Then try booting to recovery via long holding the power, home and volume up button simultaneously without releasing any of the buttons until you successfully see the TWRP splash screen.
If that still doesn't work, reboot to recovery via adb from download mode. You need the adb and the usb drivers for your device.
If that still doesn't work, you might have flashed an incompatible version of TWRP.
Click to expand...
Click to collapse
Thank you so much, it worked perfectly!
I can now start my phone and use it normally.
But the Root Checker still says:
"Sorry! Root access is not properly installed on this device.
Device: SM-G900M
Android version: 7.1.2"
What should I do from now on?
Thank you so much for your help (agaiN).
And as for why I used the auto-root, well I just followed a guide that I found, it only had positive reviews so I assumed it was a correct tutorial.

AsylumAlice said:
Thank you so much, it worked perfectly!
I can now start my phone and use it normally.
But the Root Checker still says:
"Sorry! Root access is not properly installed on this device.
Device: SM-G900M
Android version: 7.1.2"
What should I do from now on?
Thank you so much for your help (agaiN).
And as for why I used the auto-root, well I just followed a guide that I found, it only had positive reviews so I assumed it was a correct tutorial.
Click to expand...
Click to collapse
just flash supersu in twrp

AronFerr said:
just flash supersu in twrp
Click to expand...
Click to collapse
I thought about doing that, but wasn't sure how exactly to proceed and what Version to install.
I downloaded SuperSU v.2.82 and put it on my internal storage.
Just install over TWRP the same way that I Installed Lineage and Gapps I suppose?
I guess if it doesn't work out, I just follow the steps from above again and retry?
Thank you so much. I feel like in idiot in this situation.

AsylumAlice said:
I thought about doing that, but wasn't sure how exactly to proceed and what Version to install.
I downloaded SuperSU v.2.82 and put it on my internal storage.
Just install over TWRP the same way that I Installed Lineage and Gapps I suppose?
I guess if it doesn't work out, I just follow the steps from above again and retry?
Thank you so much. I feel like in idiot in this situation.
Click to expand...
Click to collapse
yes just flash it but no wipes

Help install OxygenOS

Hey. I long story short - I have wiped OS, and the only thing that I can do is use fastboot and also install TWRP or stock recovery.
I found OxygenOS file, but cant install it as there are problems sideloading the file to the device, it looks like ADB drivers on PC are not recognizable. Can someone help me to get back OS? Thanks
Tried a lot of things but anyway nothing happens.

BooBzi said:
Hey. I long story short - I have wiped OS, and the only thing that I can do is use fastboot and also install TWRP or stock recovery.
I found OxygenOS file, but cant install it as there are problems sideloading the file to the device, it looks like ADB drivers on PC are not recognizable. Can someone help me to get back OS? Thanks
Tried a lot of things but anyway nothing happens.
Click to expand...
Click to collapse
Push the OOS rom via usb to the phone, command: adb push namerom /scard
Next time check the drivers installation result first.

I wish I knew the reply above mine.
How I fixed my issue:
I installed the latest TWRP 3.1.1 in one of the installation guides on this forum for the OP5. Make sure you pick the version that is called the "last latest build". I was able to flash a full zip for 4.5.2 and it worked!

chaojimbo said:
I wish I knew the reply above mine.
How I fixed my issue:
I installed the latest TWRP 3.1.1 in one of the installation guides on this forum for the OP5. Make sure you pick the version that is called the "last latest build". I was able to flash a full zip for 4.5.2 and it worked!
Click to expand...
Click to collapse
I had problems with ADB drivers, anyway got back to life:
1) booted to TWRP
2) adb push ".zip" /sdcard/.
3) tried installing it at TWRP, no success, so get back stock recovery and flashed the file there.
So my issue is resolved. thanks!

Help installing TWRP as zip file (no go through Fastboot)

I downgraded from custom Nougat to stock Marshmallow as I discovered that the incall sound (hearing the caller from the ear speaker) is louder and clearer, so of course I lost TWRP recovery and root in the process which is normal. However, I now can't re-install TWRP as a .img file since although I can boot into Android Recovery I can't go into Fastboot mode (phone just re-starts every time) so of course it's no go whether I try Axon Toolkit or ADB via computer. I also tried the EDL route but same thing.
I have all the required ZTE and Qualcom drivers installed. My phone's model is the 2017G and the bootloader is still unlocked.
Only thing I can try is installing TWRP as a zip file through Android Recovery or directly from 'system update' via the phone's menu. Problem is I can't find a zip version of TWRP for the Axon 7
Any help/suggestions most grateful.

xectis said:
I downgraded from custom Nougat to stock Marshmallow as I discovered that the incall sound (hearing the caller from the ear speaker) is louder and clearer, so of course I lost TWRP recovery and root in the process which is normal. However, I now can't re-install TWRP as a .img file since although I can boot into Android Recovery I can't go into Fastboot mode (phone just re-starts every time) so of course it's no go whether I try Axon Toolkit or ADB via computer. I also tried the EDL route but same thing.
I have all the required ZTE and Qualcom drivers installed. My phone's model is the 2017G and the bootloader is still unlocked.
Only thing I can try is installing TWRP as a zip file through Android Recovery or directly from 'system update' via the phone's menu. Problem is I can't find a zip version of TWRP for the Axon 7
Any help/suggestions most grateful.
Click to expand...
Click to collapse
If you can use miflash there is a thread somewhere that has stock everything with twrp included. I'm on my phone so I can't find it right now. But if you can't find it by the time I get to my computer I'll look through my history to try and find it.

JTruj1ll0923 said:
If you can use miflash there is a thread somewhere that has stock everything with twrp included. I'm on my phone so I can't find it right now. But if you can't find it by the time I get to my computer I'll look through my history to try and find it.
Click to expand...
Click to collapse
Thanks for the response. I looked around for the thread you mentioned but had no luck in finding it yet but I'll keep looking meantime.
Thanks

xectis said:
Thanks for the response. I looked around for the thread you mentioned but had no luck in finding it yet but I'll keep looking meantime.
Thanks
Click to expand...
Click to collapse
So the thread I found was actually not for the g model sadly. But, have you seen this thread?
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547/page10
Down a ways there is a "TWRP flashable bootstack/stock system images" section. I think if you can flash those (maybe with miflash?) You should then have fastboot available to flash twrp again.

When you unlocked surely you learned how to use the tools to flash twrp without fastboot.
You can use miflash, the toolkit, tenfar's tool or tenear's tool.
There's a million and one guides on how to to this plus the actual tool threads.
Even the twrp thread has a guide.

JTruj1ll0923 said:
So the thread I found was actually not for the g model sadly. But, have you seen this thread?
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547/page10
Down a ways there is a "TWRP flashable bootstack/stock system images" section. I think if you can flash those (maybe with miflash?) You should then have fastboot available to flash twrp again.
Click to expand...
Click to collapse
I took a look. Not sure which version I should download. Am on B10 and that section only has bootstack versions up to B9. Does it matter which one I choose or should I get the closest which is B9. Also, should I install the stock system that goes with the bootstack version or just the bootstack.
Thanks for the link.

xectis said:
I took a look. Not sure which version I should download. Am on B10 and that section only has bootstack versions up to B9. Does it matter which one I choose or should I get the closest which is B9. Also, should I install the stock system that goes with the bootstack version or just the bootstack.
Thanks for the link.
Click to expand...
Click to collapse
Okay so since I was not paying that much attention (sorry) I just realized that those are bootstacks and stock systems that you can flash in TWRP. My bad. But I have been looking around and on that thread I just had you go to he mentions another thread with step by steps that may help you! Here it is. Good luck!

xectis said:
I took a look. Not sure which version I should download. Am on B10 and that section only has bootstack versions up to B9. Does it matter which one I choose or should I get the closest which is B9. Also, should I install the stock system that goes with the bootstack version or just the bootstack.
Thanks for the link.
Click to expand...
Click to collapse
JTruj1ll0923 said:
Okay so since I was not paying that much attention (sorry) I just realized that those are bootstacks and stock systems that you can flash in TWRP. My bad. But I have been looking around and on that thread I just had you go to he mentions another thread with step by steps that may help you! Here it is. Good luck!
Click to expand...
Click to collapse
Ignore the fastboot part. Just reinstall twrp with axon7tool, then install raystef66's TWRP flashable B09 bootstack and stocksystem zips (plus magisk if you won't relock), then follow his guide on how to get rid of the 5 seconds screen to get fastboot and, well, get rid of the 5 seconds screen
p.s. I basically just found out that I said the exact same thing on that crappy Q&A thread...

Choose an username... said:
Ignore the fastboot part. Just reinstall twrp with axon7tool, then install raystef66's TWRP flashable B09 bootstack and stocksystem zips (plus magisk if you won't relock), then follow his guide on how to get rid of the 5 seconds screen to get fastboot and, well, get rid of the 5 seconds screen
p.s. I basically just found out that I said the exact same thing on that crappy Q&A thread...
Click to expand...
Click to collapse
The link you provided is titled 'Get TWRP and root after updating to Nougat'. As am on Marshmallow I'll have to first update to Nougat? . So do I go ahead and flash stock Nougat from ZTE's page before following the instructions on that page? Sorry for my confusion.
**Update** I followed instructions of link you provided to install TWRP but I came to a brick wall every time. Short story is no matter what I tried I cannot install anything with either ADB, Miflash or Axon Toolkit. The big problem here is the Fastboot issue which otherwise would make things so much easier. Only thing left for me to do is just to upgrade stock firmwares via the phone's update option and remain bootloader unlocked. The Axon 7 is still a great phone, it's just too much hustle getting things done so I'll just have to sell it. Samsung and HTC phones are much easier to work with when it comes to rooting/installing custom ROMs.
***Update 2*** Success!! I managed to install fastboot/bootloader mode by following the section 'Get Fastboot' from that same link you provided so now I have latest TWRP installed and the 5 second notice has also disappeared. Am back in the running now. Many thanks for your help

xectis said:
The link you provided is titled 'Get TWRP and root after updating to Nougat'. As am on Marshmallow I'll have to first update to Nougat? . So do I go ahead and flash stock Nougat from ZTE's page before following the instructions on that page? Sorry for my confusion.
**Update** I followed instructions of link you provided to install TWRP but I came to a brick wall every time. Short story is no matter what I tried I cannot install anything with either ADB, Miflash or Axon Toolkit. The big problem here is the Fastboot issue which otherwise would make things so much easier. Only thing left for me to do is just to upgrade stock firmwares via the phone's update option and remain bootloader unlocked. The Axon 7 is still a great phone, it's just too much hustle getting things done so I'll just have to sell it. Samsung and HTC phones are much easier to work with when it comes to rooting/installing custom ROMs.
***Update 2*** Success!! I managed to install fastboot/bootloader mode by following the section 'Get Fastboot' from that same link you provided so now I have latest TWRP installed and the 5 second notice has also disappeared. Am back in the running now. Many thanks for your help
Click to expand...
Click to collapse
You could have bricked your device. I specifically told you not to follow that part. Also what has adb, axon7toolkit and miflash got to do with that guide? You have to use axon7tool just like a) it says there and b) i told you on the q&a thread

Choose an username... said:
You could have bricked your device. I specifically told you not to follow that part. Also what has adb, axon7toolkit and miflash got to do with that guide? You have to use axon7tool just like a) it says there and b) i told you on the q&a thread
Click to expand...
Click to collapse
Yes you did warn me about the fastboot part but I was stuck as nothing else worked. By using the Fastboot instructions I managed to install TWRP and root the phone. I used Miflash to install the fastboot package which was successful. Now I can boot to Fastboot and bootloader via TWRP. Remember am on Marshmallow so I guess that helped not to brick the phone? I don't know but it worked.

xectis said:
Yes you did warn me about the fastboot part but I was stuck as nothing else worked. By using the Fastboot instructions I managed to install TWRP and root the phone. I used Miflash to install the fastboot package which was successful. Now I can boot to Fastboot and bootloader via TWRP. Remember am on Marshmallow so I guess that helped not to brick the phone? I don't know but it worked.
Click to expand...
Click to collapse
Well again, if you want to be on Nougat, download raystef66's flashable B09 bootstack and stocksystem, flash them on TWRP with Magisk 15.2, and follow his guide on how to get rid of the 5 seconds screen (all in twrp, don't get out of it).
Just do all of that or you'll lose fastboot. Also that zip that you got from that ancient guide doesn't work on anything else than Marshmallow

Choose an username... said:
Well again, if you want to be on Nougat, download raystef66's flashable B09 bootstack and stocksystem, flash them on TWRP with Magisk 15.2, and follow his guide on how to get rid of the 5 seconds screen (all in twrp, don't get out of it).
Just do all of that or you'll lose fastboot. Also that zip that you got from that ancient guide doesn't work on anything else than Marshmallow
Click to expand...
Click to collapse
Thanks for the advice. If I keep the phone I'll wait for a stable Oreo update. Nougat didn't impress me much.

Stuck at bootloader--HELP!

Let's get this out of the way. I don't have much experience flashing ROMs. I've done it on a few phones, but I can't say I really understood what I was doing. I'm just good at following directions. So, I know about enough to get into trouble.
And ...I've gotten into trouble. My goal is to install LineageOS on my brother's Essential Phone. Based on directions I found here, I determined the active slot was b, so I installed TWRP on slot a. TWRP worked in recovery, but without touch. I then flashed twrp-3.2.3-0-mata.img to the non-active slot. Lastly, I sideloaded twrp-installer-mata-3.2.3-0.zip. I then changed the active slot back to b and rebooted. It now boots only to the bootloader and not to the OS. No matter what option I select--Start, Bootloader, Recovery--it reboots to the bootloader.
Any help to get out of this would be greatly appreciated.

Lineage can be installed more easily using Lineage's own Recovery rather than using TWRP. The Lineage Recovery is a pre-built replacement for your boot.img file.
Links for Lineage OS 17.1 (mata) and its corresponding Recovery (mata):
https://download.lineageos.org/mata
Link for Installation using Lineage Recovery:
https://wiki.lineageos.org/devices/mata/install
Hope this helps

MuddyDog said:
Lineage can be installed more easily using Lineage's own Recovery rather than using TWRP. The Lineage Recovery is a pre-built replacement for your boot.img file.
Links for Lineage OS 17.1 (mata) and its corresponding Recovery (mata):
https://download.lineageos.org/mata
Link for Installation using Lineage Recovery:
https://wiki.lineageos.org/devices/mata/install
Hope this helps
Click to expand...
Click to collapse
Thanks for the suggestion. I had actually already tried that. That's when I got desperate and tried generic TWRP. When I try to flash the Lineage recovery image I get a "No such partition" error, no matter which partition is active. I read somewhere that the flash boot_[letter] command might work, but I get "Couldn't parse partition size '0x'.

mcmc08 said:
Thanks for the suggestion. I had actually already tried that. That's when I got desperate and tried generic TWRP. When I try to flash the Lineage recovery image I get a "No such partition" error, no matter which partition is active. I read somewhere that the flash boot_[letter] command might work, but I get "Couldn't parse partition size '0x'.
Click to expand...
Click to collapse
Try:
Fastboot flash:raw boot_slot recovery.img

So, I found a solution. In order to overcome the errors I was getting, I had to use the raw command. So it was fastboot flash:raw boot [image file]. Once Lineage recovery was installed, I could boot to recovery and sideload Lineage.

MuddyDog said:
Try:
Fastboot flash:raw boot_slot recovery.img
Click to expand...
Click to collapse
I guess our replies crossed. At any rate, the raw command did the trick. Thanks for your help.

I'm having the same problem, and the raw command doesn't seem to help. Trying to install twrp causes it to be stuck in the bootloader. I somehow was able to install the lineage recovery, then to install the lineage OS. Because I am thinking of trying other ROMs, I decided to go back to trying the TWRP install. Now everything seems broken. When I use the a slot (where I installed TWRP), I'm stuck in the bootloader. When I shift to the b slot, I'm stuck on the Lineage splash page.
(By the way, while I was in the Lineage recovery at some point in the middle of all this, I also sideloaded the TWRP install zip.)
I've tried flashing the TWRP numerous times, and it always seems to work, but the result still is the same.
Any help would be appreciated.
Edit: I was able to get out of the loop by reflashing the Lineage Recovery, booting into that recovery, then doing a factory wipe. I was able to boot into Lineage. But why can't I successfully install TWRP? Or, I guess, alternately, is it possible to use the Lineage Recovery to flash different ROMs? (Sorry if this goes beyond the scope of the original question.)

Is Lineage using an Android 10 security update after January? January is the last update for Android 10 that TWRP worked with. Once Essential went belly up the TWRP devs just stopped updating when it broke with February security update. Anyway, I just thought I would mention it.

rocketrazr1999 said:
Is Lineage using an Android 10 security update after January? January is the last update for Android 10 that TWRP worked with. Once Essential went belly up the TWRP devs just stopped updating when it broke with February security update. Anyway, I just thought I would mention it.
Click to expand...
Click to collapse
I installed Lineageos directly on the february android stock version. (which is the last one from Essential)
Simply by following the tutorial on the LineageOS website.
Everything worked the first time.
So there is no need to switch back to the January android stock version. The image recovery provided by Lineage works very well.
And for your information LineageOS is updated almost every Monday.
Moreover the developers of the TWRP are not the developers of Essential. Company which closed at the end of February.
---------- Post added at 11:18 AM ---------- Previous post was at 11:14 AM ----------
KJannot said:
I'm having the same problem, and the raw command doesn't seem to help. Trying to install twrp causes it to be stuck in the bootloader. I somehow was able to install the lineage recovery, then to install the lineage OS. Because I am thinking of trying other ROMs, I decided to go back to trying the TWRP install. Now everything seems broken. When I use the a slot (where I installed TWRP), I'm stuck in the bootloader. When I shift to the b slot, I'm stuck on the Lineage splash page.
(By the way, while I was in the Lineage recovery at some point in the middle of all this, I also sideloaded the TWRP install zip.)
I've tried flashing the TWRP numerous times, and it always seems to work, but the result still is the same.
Any help would be appreciated.
Edit: I was able to get out of the loop by reflashing the Lineage Recovery, booting into that recovery, then doing a factory wipe. I was able to boot into Lineage. But why can't I successfully install TWRP? Or, I guess, alternately, is it possible to use the Lineage Recovery to flash different ROMs? (Sorry if this goes beyond the scope of the original question.)
Click to expand...
Click to collapse
Which Rom would you like to install instead of Lineage?

groovebox said:
Which Rom would you like to install instead of Lineage?
Click to expand...
Click to collapse
I'm of two minds; one is just to go with something stock android-ish, which leads me to Evolution X or Pixel Experience. The other is to cut myself from Google entirely, which leads me to /e/. I'm also looking at Paranoid, just because it looks like it's stable. Any thoughts on any of those?
I had updated Essential to the February update; would that be why TWRP would not successfully install on my phone?
Would that still be true if I had flashed Lineage?

KJannot said:
I'm of two minds; one is just to go with something stock android-ish, which leads me to Evolution X or Pixel Experience. The other is to cut myself from Google entirely, which leads me to /e/. I'm also looking at Paranoid, just because it looks like it's stable. Any thoughts on any of those?
I had updated Essential to the February update; would that be why TWRP would not successfully install on my phone?
Would that still be true if I had flashed Lineage?
Click to expand...
Click to collapse
Paranoid Android: What I heard is VoLTE broken, if you enable it, SMS/MMS might not work properly.
Evolution: No update in Android 10 since August, not sure they contine to support Essential phone for Android 11
Pixel Experience: I don't think they Anroid 10 for Essential phone, only official Anroid 9 which is too old
TWRP issue: You need to go back to Jan stock rom before going to any rom if you just flashed LOS
What current stable rom with Nov security update: I'm using crDroid 6.12 (unofficial release but from XDA reliable source)
https://forum.xda-developers.com/essential-phone/development/rom-crdroid-v6-7-t4129739

Galaxy Tab A 10.1 (2019) sm-t510 stuck on TWRP Splash screen

Flashed twrp 3.3.1-1 with Odin. Flashed successfully after literal hours of failure and multiple reflashes of the original ROM. After successful flash, it only boots to the TWRP splash screen. Doesn't progress any further, no matter how long. I can hold the power and volume down buttons, and it'll restart the tablet, but will only reboot into the twrp screen. Wtf can I do now? Wait until it dies, charge it for a bit, and reflash the stock ROM?
Bootloader is unlocked
OEM is unlocked
USB enabled

Maybe wipe cache and retry

Shrijon said:
Maybe wipe cache and retry
Click to expand...
Click to collapse
I can't. My PC doesn't recognize it as a device, because it is stuck on that splash screen. Literally the only thing I can do is hold the power+volume down buttons and restart it, but no matter what else I do, it always launches back into the splash screen.

Lestat5721 said:
I can't. My PC doesn't recognize it as a device, because it is stuck on that splash screen. Literally the only thing I can do is hold the power+volume down buttons and restart it, but no matter what else I do, it always launches back into the splash screen.
Click to expand...
Click to collapse
here:
[ROM][SM-T510][UNOFFICIAL] LineageOS 18.1 for Galaxy Tab A 10.1 (2019)
In the spirit of moving custom ROM development along for the 2019 Galaxy Tab A 10.1 [SM-T510], here's a build of LineageOS 18.1 I just created based on the latest OEM stock firmware and @AndyYan's latest LineageOS 18.1 GSI. It's very much a work...
forum.xda-developers.com
under the part named "From OEM stock firmware:" is a link names "Unlock bootloader".
cklick on it and read the whole page from comment #1, esp. what is written under section "Buttons" downwards
you'll find the right things need to be done

So I let it die, and was able to boot back into the Downloader and reflash the Samsung ROM, so it's like it never happened. Still, it's not rooted, and I'm at my wits end.

rw_on_xda said:
here:
[ROM][SM-T510][UNOFFICIAL] LineageOS 18.1 for Galaxy Tab A 10.1 (2019)
In the spirit of moving custom ROM development along for the 2019 Galaxy Tab A 10.1 [SM-T510], here's a build of LineageOS 18.1 I just created based on the latest OEM stock firmware and @AndyYan's latest LineageOS 18.1 GSI. It's very much a work...
forum.xda-developers.com
under the part named "From OEM stock firmware:" is a link names "Unlock bootloader".
cklick on it and read the whole page from comment #1, esp. what is written under section "Buttons" downwards
you'll find the right things need to be done
Click to expand...
Click to collapse
Like I said before, my bootloader was unlocked. I even did the little "change the date" hack to get the OEM toggle to appear. The bootloader was definitely unlocked, and still is.

if u want root then install magisk and youre good to go...
if recovery is corrupted then flash it from megadenz's post

Shrijon said:
if u want root then install magisk and youre good to go...
if recovery is corrupted then flash it from megadenz's post
Click to expand...
Click to collapse
Okay, how? Everywhere I look online, they say to install TWRP first. Is there a way to keep the OEM ROM, and install Magisk?

Lestat5721 said:
Okay, how? Everywhere I look online, they say to install TWRP first. Is there a way to keep the OEM ROM, and install Magisk?
Click to expand...
Click to collapse
First of all, you have to have the right version of the stock ROM installed. To do what I suggest, you need the BTH4 or BTFN version. Then install the Nexus ROM found here. It includes TWRP . Boot to TWRP and FORMAT the data partition. Notice, that is FORMAT, NOT wipe. Then flash the ROM again to get the correct data partition with gapps. Then flash Magisk to get root.