Related
Ok guys...here it goes.
I've had a long night of feeling like the biggest idiot to walk the Android planet. I just bought this phone off someone, and have done rooting/custom ROM installing before. But I messed up, and now I feel like I'm an idiot & screwed because I'm just so lost now. I love learning, but I feel like I'm in such a hole. Here's what happened:
I used "All In One Kit" to install "TWRP 2.6.0.0", and like anybody, I wanted to install a custom ROM after getting all the rooting done. So I went searching for CW10.1, and tried to install it. Kept getting "Failed" every time I tried to install CW10.1 with "TWRP", so I started googling why. Well, it said I had to install the boot.img with the whole "fastboot" process where I use the command "fastboot flash boot boot.img". So I did that...and man was that a mistake.
My phone after, would just stay stuck at the boot screen. So I didn't panic, and I went into "TWRP" and tried to restore from the backup I did, before I started trying to install a custom ROM...but the same thing happened. Fast forward 2 hours and now I feel like I've screwed myself. I thought "TWRP" backed everything up, but for all I know, my moronic self might have unchecked "Boot". So I believe I need to "fastboot" the correct/original boot.img, so the phone will boot normally, but I have no idea where to find it. I've tried looking, but I'm more finding the issue is solved by using RUU. Which I REALLY don't mind doing at all, but I'm scared now since there are so many different ones, and I can't figure out which one is the right one to use. My night has taken such a crappy turn, I'm afraid if I RUU once wrong, I will be in an even bigger mess, than trying to reach out to you guys first. It's crazy how comfortable I was doing all this, and now I feel like I shouldn't have ever tried.
Here is the phone info I can provide that is hopefully helpful:
The phone is an HTC One X+ AT&T USA
EVITARE_UL PVT SHIP S-ON RL
HBOOT: 1.40.0000
CPLD-None
MICROP-None
RADIO-SSD: 2.14.55.01
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM TYPE: MDM9215M
Dec 28 2012, 22:18:14
And I believe it was at 4.2.1 software...but I'm not 100% on that and don't know how to make sure.
Please guys, if anybody can help, I need it. I appreciate your time in reading this, even if you cannot help. I believe I either just need a stock boot.img for my phone, or linked the correct RUU (assuming I'm right in that will fix it and revert me back to having a phone again). Any questions feel free to ask me. I'm going to try to sleep now.
krayzed896 said:
Ok guys...here it goes.
I've had a long night of feeling like the biggest idiot to walk the Android planet. I just bought this phone off someone, and have done rooting/custom ROM installing before. But I messed up, and now I feel like I'm an idiot & screwed because I'm just so lost now. I love learning, but I feel like I'm in such a hole. Here's what happened:
I used "All In One Kit" to install "TWRP 2.6.0.0", and like anybody, I wanted to install a custom ROM after getting all the rooting done. So I went searching for CW10.1, and tried to install it. Kept getting "Failed" every time I tried to install CW10.1 with "TWRP", so I started googling why. Well, it said I had to install the boot.img with the whole "fastboot" process where I use the command "fastboot flash boot boot.img". So I did that...and man was that a mistake.
My phone after, would just stay stuck at the boot screen. So I didn't panic, and I went into "TWRP" and tried to restore from the backup I did, before I started trying to install a custom ROM...but the same thing happened. Fast forward 2 hours and now I feel like I've screwed myself. I thought "TWRP" backed everything up, but for all I know, my moronic self might have unchecked "Boot". So I believe I need to "fastboot" the correct/original boot.img, so the phone will boot normally, but I have no idea where to find it. I've tried looking, but I'm more finding the issue is solved by using RUU. Which I REALLY don't mind doing at all, but I'm scared now since there are so many different ones, and I can't figure out which one is the right one to use. My night has taken such a crappy turn, I'm afraid if I RUU once wrong, I will be in an even bigger mess, than trying to reach out to you guys first. It's crazy how comfortable I was doing all this, and now I feel like I shouldn't have ever tried.
Here is the phone info I can provide that is hopefully helpful:
The phone is an HTC One X+ AT&T USA
EVITARE_UL PVT SHIP S-ON RL
HBOOT: 1.40.0000
CPLD-None
MICROP-None
RADIO-SSD: 2.14.55.01
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM TYPE: MDM9215M
Dec 28 2012, 22:18:14
And I believe it was at 4.2.1 software...but I'm not 100% on that and don't know how to make sure.
Please guys, if anybody can help, I need it. I appreciate your time in reading this, even if you cannot help. I believe I either just need a stock boot.img for my phone, or linked the correct RUU (assuming I'm right in that will fix it and revert me back to having a phone again). Any questions feel free to ask me. I'm going to try to sleep now.
Click to expand...
Click to collapse
i think installing an international ROM on an AT&T device was the downfall here
you need to install a ROM here for an example, by following the instructions given:
http://forum.xda-developers.com/showthread.php?t=2098218
leefear said:
i think installing an international ROM on an AT&T device was the downfall here
you need to install a ROM here for an example, by following the instructions given:
http://forum.xda-developers.com/showthread.php?t=2098218
Click to expand...
Click to collapse
No you are completely right. This is where I messed up, and everything went bad. My only problem is I'm not sure how to get the ROM on my device. Every time I try "ADB Sideload", it says it's starting...and then...that's it. I can cancel it, but it never actually goes through with the side load. What should I try to do in this case, so I can get the ROM loaded?
And thank you for your quick response, it's greatly appreciated!
krayzed896 said:
No you are completely right. This is where I messed up, and everything went bad. My only problem is I'm not sure how to get the ROM on my device. Every time I try "ADB Sideload", it says it's starting...and then...that's it. I can cancel it, but it never actually goes through with the side load. What should I try to do in this case, so I can get the ROM loaded?
And thank you for your quick response, it's greatly appreciated!
Click to expand...
Click to collapse
assuming you have the htc driver installed for your device, adb commands should work, can you test with adb devices that should list your phone, if not get your htc drivers installed and make sure you have latest adb on your pc
move NAMEOFROM.zip to adb folder and use the sideload option in twrp and sideload rom and should work
and don't forget to flash the boot.img provided
question rolermi
leefear said:
assuming you have the htc driver installed for your device, adb commands should work, can you test with adb devices that should list your phone, if not get your htc drivers installed and make sure you have latest adb on your pc
move NAMEOFROM.zip to adb folder and use the sideload option in twrp and sideload rom and should work
and don't forget to flash the boot.img provided
Click to expand...
Click to collapse
I definitely have the drivers installed, mostly because they were required as part of rooting with "All in One" tool. I never installed anything for ADB, I simply assumed it was just used as an option in "TWRP", so I'll go download that. Thank you, and I will update with my results!
Ok, posting an update!
Thank you for your response, as this fixed my problem! I will sum up my problem/fix in this reply, in case anybody is also trying to fix the same problem.
I have at HTC One X+ for AT&T
I was in a boot loop, after I had successfully rooted my phone with TWRP. I used "fastboot" method to change the boot.img, and lost my original in the process. Stuck only being able to boot to the system, or recovery, I needed a way to fix my boot problem. The suggested method worked flawlessy. I downloaded Android SDK, installed Platoform-Tools from the SDK Manager. Opened up ADB in ADT>SDK>Platform-Tools and followed the necessary steps for "pushing a ROM with ADB" I had found. I used the recommend link above for ViperXL+. I was able to push the ROM in, boot into recovery, and finally install a proper ROM. I then did the "fastboot" method to install the ROM ViperXL+'s boot.img (As a side note your .zip might show up as "sideload" and not the ROM title for the .zip I didn't know this, and thought it somehow lied to me is 100% completion, until I tried selecting "sideload" to install, which I didn't believe to have seen before. And sure enough it was the ROM)
Now my phone boots sucessfully, and I have a custom ROM. THANK YOU so much for your help, big kudos to leefear for explaining what I needed to do, and linking me the ROM. I appreciate it so much man!!!
krayzed896 said:
Ok, posting an update!
Thank you for your response, as this fixed my problem! I will sum up my problem/fix in this reply, in case anybody is also trying to fix the same problem.
I have at HTC One X+ for AT&T
I was in a boot loop, after I had successfully rooted my phone with TWRP. I used "fastboot" method to change the boot.img, and lost my original in the process. Stuck only being able to boot to the system, or recovery, I needed a way to fix my boot problem. The suggested method worked flawlessy. I downloaded Android SDK, installed Platoform-Tools from the SDK Manager. Opened up ADB in ADT>SDK>Platform-Tools and followed the necessary steps for "pushing a ROM with ADB" I had found. I used the recommend link above for ViperXL+. I was able to push the ROM in, boot into recovery, and finally install a proper ROM. I then did the "fastboot" method to install the ROM ViperXL+'s boot.img (As a side note your .zip might show up as "sideload" and not the ROM title for the .zip I didn't know this, and thought it somehow lied to me is 100% completion, until I tried selecting "sideload" to install, which I didn't believe to have seen before. And sure enough it was the ROM)
Now my phone boots sucessfully, and I have a custom ROM. THANK YOU so much for your help, big kudos to leefear for explaining what I needed to do, and linking me the ROM. I appreciate it so much man!!!
Click to expand...
Click to collapse
hey buddy, glad you got it working, nothing worse than a broken phone! glad i could help! now, hit that thanks button!
ooh, my 200th post!
leefear said:
hey buddy, glad you got it working, nothing worse than a broken phone! glad i could help! now, hit that thanks button!
ooh, my 200th post!
Click to expand...
Click to collapse
Congrats on the 200th post! Sorry, very new to using the forums. I hit thanks on all your posts in the topic! :good:
Hi,
i have the same problem but it's a non LTE version HOX+ can someone advise on another ROM that will work in the same way?
My desesperation may have been my reaper.
I tried flashing a kdz file vb20 to my l9. I was trying to unlock bootloader, based on the main threads at the General forum (unlocking bootloader for noobs). I only worked with the written instructions, and the phone didn't show the recovery installer that was on SD (forgot to install, I guess?). I freaked out and thought that a boot to recovery could fix. WRONG. It made the recovery to the v20b file. Everything is mirrored,
PS, please me nice on me. I know I didn't prep as well as I thought I did, so just want advice
EDIT:
Never mind. Dodged a bullet. After a while, the screen came up when it was unlocked. Took a while, but I was able to use the same method to flash v20f, am now updating to v20h. WAAAYYYY too close a call!!!
Another edit: think I'm gonna have to give it up. I flashed the most updated version, but the keyboard and screen behave too erratically.
Just a quick question about "bump"ed TWRP images and why they might/might not work. I got my G3 a few days ago (came with Lollipop 5.0 stock) and finally got around to rooting it today. Naturally, I wanted to install TWRP after that so I could fire up some custom ROMs later on. I followed the guide in the official Bump! thread and ended up with recovery that wouldn't boot due to a "secure boot error". I then tried flashing the same, bumped, 2.8.7.0 image with Flashify, with the same result. Then I moved on to AutoRec, and for some reason that did the trick - after letting it flash TWRP, I could boot into recovery with no problems. I then flashed the (newer) bumped image I got from the Bump! thread that hadn't worked before and to my bewilderment, it worked as well. Can someone explain to me in broad strokes what exactly made the difference? And, if there is an additional step involved beyond just flashing a bumped TWRP, why is that not mentioned anywhere in the Bump! thread?
Also, from what I understand, "bump"ing an image just means signing it with LG's key that was extracted by the Bump! and open bump! developers. If that is the case, why are there still un-bumped recovery images floating around? What use are those to anyone, if aboot will refuse to boot them?
Cheers,
George
P.S. If there is a thread/post already out there somewhere (I'm pretty sure there is, but I couldn't find anything) with the information I'm looking for and/or more general information on the unlocking/signing process, I'd love to read it - I just haven't found anything like that so far.
Bump
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
AndriyEtch said:
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
Click to expand...
Click to collapse
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
cva_kabil said:
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
Click to expand...
Click to collapse
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
AndriyEtch said:
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
Click to expand...
Click to collapse
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
cva_kabil said:
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
Click to expand...
Click to collapse
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
I dont think so... I hv not tried... But as of i know if u edit it wrongly, u will not be able to flash that file. . Try others methods first... Hope it works
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
Hi OP, sorry for joining late to the party
So the thing is the OnePlus X is at opposites now since the official MM release on 29th September. The thing is if you are running the old bootloader (OxygenOS 2.x.x) or any ROM based on it, then the New TWRP will not boot, neither will the Stock Recovery that is hosted on the OnePlus download section for the X, which is where i assume you download the stock recovery from, right ? Also note that the official recovery hosted on the TWRP website is also yet to be updated, we're working on that.
So you are on the old Bootloader. Simple stuff. I have posted my guide a lot of time around the forums, its gained a lot of merit. You could follow it for your update process. I'll leave a link below. In case you wanna verify that the old bootloader is causing the issue my Index Thread pinned in the general section has a link for the Stock recovery for Old bootloader, try flashing that via fastboot, if it successfully boots then you're set.
Comprehensive guide to Update to Marshmallow Bootloader
The above guide is centered to the thread i have posted it on but the process is 99% the same. In the end, you could just stay with Oxygen OS 3.1.3, or flash any custom ROM based on the new Bootloader.
Now regarding your query about editing the META of the ROM, well Yes to an extent it IS risky if you ain't careful because my guide guides you to delete the one single line that removes the device check, so as long as you use the modified zip on OnePlus X only, there will be no issues.
Let me know for any further clarifications, also you're welcome to join our support group on Telegram, all of our developers are active there. Ping me (@ mellogang_unite) for an invite
I'd like to keep this simple. I tried rooting and not a single tutorial on here has ended with root privileges for various reasons. I'm done with it. I flashed stock firmware in hopes of removing any trace of files that may have been altered during the various root tutorials I followed, but Samsung Pass says the device is still rooted.
What do I need to do to return to 100% stock?
noxarcana said:
I'd like to keep this simple. I tried rooting and not a single tutorial on here has ended with root privileges for various reasons. I'm done with it. I flashed stock firmware in hopes of removing any trace of files that may have been altered during the various root tutorials I followed, but Samsung Pass says the device is still rooted.
What do I need to do to return to 100% stock?
Click to expand...
Click to collapse
I assume you unlocked the bootloader. Try Relocking and flash the firmware again.
Weather that will work is anybodys guess.
Rooting is a pretty simple procedure I can't think of any reason it didn't work except user error.
This method works perfectly on T860.
***********************
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
jhill110 said:
I assume you unlocked the bootloader. Try Relocking and flash the firmware again.
Weather that will work is anybodys guess.
Rooting is a pretty simple procedure I can't think of any reason it didn't work except user error.
Click to expand...
Click to collapse
Well, this isn't the first time I've rooted a device and I followed every step of every tutorial I found on here and, for some reason, it would not root. This is the first, and only, device I've had this much trouble with.
The tutorial for rooting without TWRP: I made the patched AP file and flashed it; however, I could not boot into recovery or download mode and it always stuck on the boot logo.
The tutorial for installing TWRP didn't have a link for the encryption disabler and the one I found did absolutely nothing and the folders in storage just showed as a string of numbers and letters.
Maybe, if someone could put together a full tutorial with the files being used within the tutorial, it would have worked.
noxarcana said:
Well, this isn't the first time I've rooted a device and I followed every step of every tutorial I found on here and, for some reason, it would not root. This is the first, and only, device I've had this much trouble with.
The tutorial for rooting without TWRP: I made the patched AP file and flashed it; however, I could not boot into recovery or download mode and it always stuck on the boot logo.
The tutorial for installing TWRP didn't have a link for the encryption disabler and the one I found did absolutely nothing and the folders in storage just showed as a string of numbers and letters.
Maybe, if someone could put together a full tutorial with the files being used within the tutorial, it would have worked.
Click to expand...
Click to collapse
Did you get the bootloader unlocked?
Unlocking the bootloader:
https://www.getdroidtips.com/how-to...to_Unlock_Bootloader_on_Samsung_Galaxy_Tab_S6
To get to download mode it's volume up and volume down then plug your pc into device. NOT POWER AND VOLUME DOWN. This can be a pain in the back side.
If you do it this way you'll get the option unlock / lock bootloader or go to bootloader mode.
If you follow the instructions perfectly and then follow the instructions for rooting it will work.
Move on to root.
ROOTING :
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
AP SLOT = PATCHED FILE
BL SLOT = BL FILE
CP SLOT = CP FILE (T865) NOT T860... T860 HAS NO CP FILE
CSC SLOT =HOME CSC FILE
DON'T forget to setup WiFi before installing magisk manager. ^^^^^^^^^
Install TWRP.
TWRP :
https://forum-xda--developers-com.c...b-s6/development/recovery-twrp-3-3-1-t3975587
I hope this helps you out.
If you have anymore questions just ask.
Disable DM VERITY ENCRIPTION DISABLER
PATCHED ODIN
jhill110 said:
Did you get the bootloader unlocked?
Click to expand...
Click to collapse
Yep, bootloader unlock was easy. I'll give root another try with your steps in a couple of days when I'm off work. Sorry if I came across a bit aggressive in my previous posts; I have a tendency to do so even when I'm not frustrated.
This has been so frustrating to me because I know rooting is usually a simple process; as you said previously.
jhill110 said:
ROOTING :
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
AP SLOT = PATCHED FILE
BL SLOT = BL FILE
CP SLOT = CP FILE (T865) NOT T860... T860 HAS NO CP FILE
CSC SLOT =HOME CSC FILE
DON'T forget to setup WiFi before installing magisk manager. ^^^^^^^^^
Click to expand...
Click to collapse
So, yea, I'm a bit late getting around to this. Sorry.
This is where things get hung up. Everything flashes just fine and I can even get into TWRP; however, when I try to boot the tablet i get the Galaxy Tab S6 screen, then the warning about the bootloader being unlocked, and back to the Galaxy Tab S6 screen but with a "unofficial software" warning....and repeat. It just boot loops and this is where I've since I started this thread.
Also, returning to stock doesn't completely remove root traces as I can't use Samsung Pass and I simply get a warning about the device seemingly being rooted even though it isn't.
If you installed TWRP, then you tripped Knox tripping Knox will permentally disable Samsung Pay as far as I'm aware. You'll never get it back, regardless of root or no root access.
Also, I'm not sure why you're installing TWRP AND trying to flash a Magisk patched OS. It's one or the other, you don't need to do both. Unless something has changed in Android 10?
If you're flashing TWRP, you just need to flash Magisk in TWRP(along with the other files!), no need to patch AP.
bartleby999 said:
If you installed TWRP, then you tripped Knox tripping Knox will permentally disable Samsung Pay as far as I'm aware. You'll never get it back, regardless of root or no root access.
Also, I'm not sure why you're installing TWRP AND trying to flash a Magisk patched OS. It's one or the other, you don't need to do both. Unless something has changed in Android 10?
If you're flashing TWRP, you just need to flash Magisk in TWRP(along with the other files!), no need to patch AP.
Click to expand...
Click to collapse
Not Samsung Pay, I couldn't care less about that, but Samsung Pass; I guess it looks for knox being tripped now too. That sucks, but I'll make do without it.
I was following the guides posted above. The root guide said to flash a Magisk patched OS and then there was a guide for installing TWRP. I never had this many issues or this much confusion with my 1st gen Tab S; maybe I just haven't kept as close of an eye on these things since I've been without a tablet for awhile before getting the Tab S6.
Anyway, for clarification, all I need to do is flash TWRP and then flash magisk from within TWRP? Or, just install the magisk apk after booting into Android?
noxarcana said:
Not Samsung Pay, I couldn't care less about that, but Samsung Pass; I guess it looks for knox being tripped now too. That sucks, but I'll make do without it.
I was following the guides posted above. The root guide said to flash a Magisk patched OS and then there was a guide for installing TWRP. I never had this many issues or this much confusion with my 1st gen Tab S; maybe I just haven't kept as close of an eye on these things since I've been without a tablet for awhile before getting the Tab S6.
Anyway, for clarification, all I need to do is flash TWRP and then flash magisk from within TWRP? Or, just install the magisk apk after booting into Android?
Click to expand...
Click to collapse
My bad for some reason I just read that as Samsung Pay. But yeah Samsung Pass also doesn't work with root, I'm not sure if that is permanent though as I've never used Samsung Pass, but did come across this thread https://forum.xda-developers.com/general/rooting-roms/samsung-pass-knox-tripped-devices-t3687977 it is possible to get some components of Knox to function again, (I have a working Secure Folder) so might be worth taking a look.
As for you question...
You should give this thread a good read... https://forum.xda-developers.com/galaxy-tab-s6/development/recovery-twrp-3-3-1-t3975587
Basic steps are... Unlock the bootloader and then boot into system and ensure it's unlocked in settings. You may need to connect to the web, I can't remember tbh
First you need to install TWRP, once that is done you need to reboot but YOU HAVE TO boot directly back into TWRP. You cannot boot into system, or TWRP will be overwritten by stock recovery and you'll need to start over again. Once TWRP is installed, boot into TWRP and format data then reboot recovery, flash Kernel then flash encryption disabler then unmount the system and flash Magisk 20.4 - Finally reboot to system.
I'd seriously and strongly suggest reading that TWRP thread to ensure things go smoothly.
bartleby999 said:
First you need to install TWRP, once that is done you need to reboot but YOU HAVE TO boot directly back into TWRP. You cannot boot into system, or TWRP will be overwritten by stock recovery and you'll need to start over again. Once TWRP is installed, boot into TWRP and format data then reboot recovery, flash Kernel then flash encryption disabler then unmount the system and flash Magisk 20.4 - Finally reboot to system.
I'd seriously and strongly suggest reading that TWRP thread to ensure things go smoothly.
Click to expand...
Click to collapse
I'll give those threads a thorough reading over tonight and tomorrow night while at work and then see if I can get this all sorted out Monday when I'm off. I remember Pass still working with root on the original Tab S so I'm hoping it hasn't changed.
Thanks for jumping in to try and help me with this. I'll update within a few days instead of months like my last update. ?
noxarcana said:
I'll give those threads a thorough reading over tonight and tomorrow night while at work and then see if I can get this all sorted out Monday when I'm off. I remember Pass still working with root on the original Tab S so I'm hoping it hasn't changed.
Thanks for jumping in to try and help me with this. I'll update within a few days instead of months like my last update. ?
Click to expand...
Click to collapse
It has definitely changed. Pass doesn't work on my Tab S6 and I'm rooted, I guess Knox is now integrated with alot of Samsung apps now. Not sure if it's possible or not to get it working again though, I've never bothered to research it as I don't need it for anything - But as I said, I got Secure Folder working again, so there's some hope for Pass I guess - That first thread I linked looked promising, but I only skimmed it, because frankly I'm not interested.
If you need anymore help, report back -I'll try my best. Also, the TWRP thread I linked is full of helpful people. :good:
bartleby999 said:
It has definitely changed. Pass doesn't work on my Tab S6 and I'm rooted, I guess Knox is now integrated with alot of Samsung apps now. Not sure if it's possible or not to get it working again though, I've never bothered to research it as I don't need it for anything - But as I said, I got Secure Folder working again, so there's some hope for Pass I guess - That first thread I linked looked promising, but I only skimmed it, because frankly I'm not interested.
If you need anymore help, report back -I'll try my best. Also, the TWRP thread I linked is full of helpful people. :good:
Click to expand...
Click to collapse
Perhaps I'm just not meant to have root with this device. Flashing that kernel causes Wifi not to work, but it does boot. Not flashing the kernel also booted, but I couldn't install Magisk Manager. Other than the bootloader still being unlocked, I'm back on stock firmware.
noxarcana said:
Perhaps I'm just not meant to have root with this device. Flashing that kernel causes Wifi not to work, but it does boot. Not flashing the kernel also booted, but I couldn't install Magisk Manager. Other than the bootloader still being unlocked, I'm back on stock firmware.
Click to expand...
Click to collapse
What firmware are you running?
I remember seeing something about one of the newer Kernels effecting WIFI on Android 10. Assume you're running that?
If that's the case, give the TWRP thread a browse - You maybe able to find an older version of the Kernel that'll work - As far as I'm aware, an older Kernel than what you currently installed will work, but a newer version than currently installed will possibly cause bootloop.
I can't help much with Android 10 specific stuff as I'm still running Android 9 because it's stable.
bartleby999 said:
What firmware are you running?
I remember seeing something about one of the newer Kernels effecting WIFI on Android 10. Assume you're running that?
If that's the case, give the TWRP thread a browse - You maybe able to find an older version of the Kernel that'll work - As far as I'm aware, an older Kernel than what you currently installed will work, but a newer version than currently installed will possibly cause bootloop.
I can't help much with Android 10 specific stuff as I'm still running Android 9 because it's stable.
Click to expand...
Click to collapse
I am definitely on the latest Android 10 update so I'll see if I can find an earlier version that will work. I'll see what I can find out on the TWRP thread.
noxarcana said:
I am definitely on the latest Android 10 update so I'll see if I can find an earlier version that will work. I'll see what I can find out on the TWRP thread.
Click to expand...
Click to collapse
If you can't find an older Kernel (I'm not sure there is one for Android 10), it may be the case that you'll need to wait for the Kernel to be updated.
bartleby999 said:
If you can't find an older Kernel (I'm not sure there is one for Android 10), it may be the case that you'll need to wait for the Kernel to be updated.
Click to expand...
Click to collapse
Yea, it looks like Samsung made some "wifi improvements" in OneUI 2.5 and that's causing some kernel issues preventing wifi from working. I think I could find a kernel fairly easily, but I think I'm just going to wait for a kernel update. If it never comes, I'll find an older kernel. Thanks for the help!