Database Develop

No way to get my XZ3 into recovery mode--- because of some spyware?

Good evening and sorry if post a thread of which I see two similar oness
However, I could not find a solution in the other ones and have questions which go a little further and really hit my privacy.
I have two XZ3 and both could go into recovery node when I bought them and after a while could not.
I used the reset to factory seting fo wiping cache etc. quite regularly as I had/have reasons to belive that I was/am spied on.
Sice the recovery mode possibility is gone I feel totally unsafe with both phones.
I tried all possibilities I can find of this website or any other in internet, and all were without success.
As described by others, after pushing the power button, there is no led light and it boots suoer-quicklyto the blue stripe view in which we wait till the boot is complete.
Till two days ago I thought ok, the phone just needs a flash, wipe everything away once and all would be resolved.
Well, two days ago I flashed my phone the first time from lollipop to kitkat, which worked without problems and then rooted it with gifroot and then put back lollipop.
Everything ran smoothly and after the whole process I had a rooted lollipop version with a working recovery. I tried the apps which confirm if the root works abd everything was great.
Tthe morning after, however the recovery possibility was gone. The phone was still rooted for everything, but for recvery mode.
I tried several apps, which I gave superuser access with SuperSu, but even from the apps the boot goes always just the NORMAL way without recovery.
To give it another try today I flashed that xz3 again, then rooted it with Kingo root, which in Kitkat firmware worked lalso super easy, the checked with other apps whihchconfirmed that the root works, but still no recovery possibility, no matter with which app..
I really need a specialist who can explain that to me, as I am going mad to think that someone else has total control over my phones.
How realistic is that some spyware does not allow the recovery as of course it knows that it would be eliminated then.
Please give me your thuoghts or knowledge. Everything helps. And if you know a method with which I can be sure that nothing is keft on the phone, I would appreciate.
Thanks and Regards

iFran72 said:
Good evening and sorry if post a thread of which I see two similar oness
However, I could not find a solution in the other ones and have questions which go a little further and really hit my privacy.
I have two XZ3 and both could go into recovery node when I bought them and after a while could not.
I used the reset to factory seting fo wiping cache etc. quite regularly as I had/have reasons to belive that I was/am spied on.
Sice the recovery mode possibility is gone I feel totally unsafe with both phones.
I tried all possibilities I can find of this website or any other in internet, and all were without success.
As described by others, after pushing the power button, there is no led light and it boots suoer-quicklyto the blue stripe view in which we wait till the boot is complete.
Till two days ago I thought ok, the phone just needs a flash, wipe everything away once and all would be resolved.
Well, two days ago I flashed my phone the first time from lollipop to kitkat, which worked without problems and then rooted it with gifroot and then put back lollipop.
Everything ran smoothly and after the whole process I had a rooted lollipop version with a working recovery. I tried the apps which confirm if the root works abd everything was great.
Tthe morning after, however the recovery possibility was gone. The phone was still rooted for everything, but for recvery mode.
I tried several apps, which I gave superuser access with SuperSu, but even from the apps the boot goes always just the NORMAL way without recovery.
To give it another try today I flashed that xz3 again, then rooted it with Kingo root, which in Kitkat firmware worked lalso super easy, the checked with other apps whihchconfirmed that the root works, but still no recovery possibility, no matter with which app..
I really need a specialist who can explain that to me, as I am going mad to think that someone else has total control over my phones.
How realistic is that some spyware does not allow the recovery as of course it knows that it would be eliminated then.
Please give me your thuoghts or knowledge. Everything helps. And if you know a method with which I can be sure that nothing is keft on the phone, I would appreciate.
Thanks and Regards
Click to expand...
Click to collapse
Spyware cannot affect Recovery unless it is granted root permissions and is embedded on system.
Also do not use KingoRoot, a thread in the SG note 3 forums reported Spyware installed after using it, source. For now steer clear of that application until all claims have been proven false
At any rate, ( assuming you have Unlocked Bootloader ) just flash another kernel with recovery, do a full wipe including formating the system partition and restore your system via flashing a rom

9
Revontheus said:
Spyware cannot affect Recovery unless it is granted root permissions and is embedded on system.
Also do not use KingoRoot, a thread in the SG note 3 forums reported Spyware installed after using it, source. For now steer clear of that application until all claims have been proven false
At any rate, ( assuming you have Unlocked Bootloader ) just flash another kernel with recovery, do a full wipe including formating the system partition and restore your system via flashing a rom
Click to expand...
Click to collapse
i got that problem i cant hard reset my phone i forgott my posswords and the key combo dosent work and i have never rooted before, can you give me a step by step for dummie (me)

petterssonjohan said:
9
i got that problem i cant hard reset my phone i forgott my posswords and the key combo dosent work and i have never rooted before, can you give me a step by step for dummie (me)
Click to expand...
Click to collapse
If you can enter flash mode, flash the latest firmware and software for your device using flash tool.

What is flash mode? I can get the phone in a mode where the indicator lamp turns blue is it that?

get Flashtool @ https://xperiafirmware.com/flashtool/
it includes Xperiafirm so you can download a stock ROM for your device and build an .ftf file
when you have the ftf file, drag it into the main Flashtool window
follow prompts

Stop Update in Recovery Mode? SM-G870A - 4.4.2

Backstory:
I have spent best part of the day trying to resolve this update issue and lo and behold the past 3 hours before posting this I've been searching everywhere how to get around this.
My phone which I have only just fixed up (screen smashed back in May of this year) I had the phone in airplane mode when I smashed the phone with a swipe lock on digitizer was shot so no way to unlock device. The unit was until right now in pristine 4.4.2 condition.
Story:
I have been the last couple of days researching and trying to root, custom rom the device. Not being fluent in what I'm doing it has taken me a long time, but I was pleased to say I got rooted and have flashroot and SuperSU installed and felt I was moving forward. With that, it felt like a good days work was done and this afternoon I powered down the unit.
I had during/previously disabled the system update pending but to my surprise, some time later this afternoon, with the device powered down, the unit booted up and was installing at 25% by the time I noticed of said unwanted update. I ripped out the battery and saved myself an irksome update.
Facts surrounding the phone prior to this: I had left the phone in Wifi mode without a SIM while I rooted the device.
I'm now stuck with a device that will only boot in Recovery Mode straight to 25% of the update or boot it into Odin Mode. The good news is the device was rooted. I have nothing precious on the device so I'm happy to flash the device from here but I'm still not clear what steps I need to do from where I am. Would I need to install a new bootloader? OR ... can I somehow stop the recovery mode from trying to install the update?
I am unbiased about which custom ROM to use, but from my days trawling these threads the ones that seems most straight forward either been closed/superseded, or have been replaced by something else that doesn't support my device or are offering me more bling than I care for. Could someone point me where to go from here?
Before replying please take time and consider people like me who have spent hours trying to find articles that aren't time wasters so many great articles are sabotaged by tonnes of junky replies and trolly comments about "read the FAQ" or pointing to obnoxious links to unrelated or out of date threads.

@Neilisin although i have never had this happen to me, i have read many many post in my days in XDA and they have ask days that, If you are rooted, then the ota will not be able to push through. Meaning it may download it and go through all the steps bit it will not be able to install. However since it hasn't gone the yet you should be able to go to one of Muniz pot and download the " nce downgrade" file that he post in step 4 out his threads. Boot into download mode And flash that with odin in the ap slot.

Success
dirtydodge said:
@Neilisin although i have never had this happen to me, i have read many many post in my days in XDA and they have ask days that, If you are rooted, then the ota will not be able to push through. Meaning it may download it and go through all the steps bit it will not be able to install. However since it hasn't gone the yet you should be able to go to one of Muniz pot and download the " nce downgrade" file that he post in step 4 out his threads. Boot into download mode And flash that with odin in the ap slot.
Click to expand...
Click to collapse
Hi @dirtydodge,
Thanks for your advice! This morning, I flashed the device with G870AUCU1ANE4_Full_Odin.tar using Odin's PDA/AP slot... and was returned to pre-root condition 4.4.2.
(For information about where I got these links please go to: [How-To] Update to G870A_OF3 (Active Model Only) - 5.0 and KeepRoot)
I'm taking christmas vacation now and will return to try and custom rom the unit after the vacation. Thanks for the tips even if totally simple!

[GUIDE] How to root Salaxy Tab S2 T817T

How to Root Samsung Tab S2 T817T (Step-By-Step Guide)
Obligatory notices
This procedure is only for the Samsung Tab S2 SM-T817T
Performing any of the operations in this post risks bricking your device
Performing any of the operations in this post will irreversibly void your warranty
Performing any of the operations in this post will irreversibly trip Knox and make it unusable for Samsung Pay (and any other features which require Knox)
I am not using a SIM card with my device, so I have no idea how this procedure will impact that functionality. People on the XDA thread (forum.xda-developers.com/tab-s2/help/sm-t817t-root-t3206079) where I pieced together these instructions from suggested that the SIM card still works for mobile data. UPDATE: Later in this thread people have confirmed that mobile data DOES work after rooting. Yay!
Introduction
OK, so a brief story of how/why I was forced to figure this method out. I found a listing on eBay for the Samsung Tab S2 T810N, paid $300 for it and received it into my impatient hands. Without checking the specific version of the tab I push right into the rooting procedure I had thoroughly researched for the T810N. Suddenly my tablet is in a bootloop and I am panicking that it is ruined. In the recovery mode I see that I have the T817T. Anger towards the seller aside, I frantically research how to recover the T817T. There is virtually no documentation for this procedure, so I am forced to mix-and-match. After about 5 hours, the tablet is finally up, running, and rooted!
TL;DR - verify your model number before attempting root
Files
All the files can be found here (drive.google.com/folderview?id=0BxPb6XhrMsaoa01zdjVUVWMzQWs&usp=sharing). Let me explain what each file is:
T817TUVS2AOL1_T817TTMB2AOL1_TMB.zip (drive.google.com/file/d/0BxPb6XhrMsaoeGpmbnRoeFA5MUU/view?usp=sharing) - This is an Android 5.1.1 image for Samsung Tab S2 T817T. You may not even need this, but just in case. If you use this, unzip the file to get the .md5 file!
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.51.0.exe (drive.google.com/file/d/0BxPb6XhrMsaoc09qNm41OFhKLWc/view?usp=sharing) - Necessary Windows drivers for Samsung devices. Install this!
Odin3_v3.10.6.zip (drive.google.com/file/d/0BxPb6XhrMsaoLWtkek9UYWZGNGM/view?usp=sharing) - A flashing tool for Windows. Unzip these files!
twrp_2.8.7.1_LL_5.1.1_t810.tar (drive.google.com/file/d/0BxPb6XhrMsaoN0N6V3JzX290aGc/view?usp=sharing) - This is a custom recovery tool for Android. Although designed for the T810 series, it does work on the T817T. Do not untar these files!
Tab_S2_t817T_boot.zip (drive.google.com/file/d/0BxPb6XhrMsaob0hyME0zV2EtSnc/view?usp=sharing) - A custom bootloader for the T817T which is required to root. Do not unzip these files!
BETA-SuperSU-v2.52.zip (drive.google.com/file/d/0BxPb6XhrMsaoNk9uWkxRZ0wwTE0/view?usp=sharing) - A newer version of SuperSu which works on the T817T. Do not unzip these files!
Preparation
Download all the files above. Install, unzip, and untar (or not) as instructed.
Settings -> About device - Verify that you have the SM-T817T
Settings -> About device - Verify that you are running Android 5.1.1
Backup all your files, contacts, apps, etc.
Verify that your device has at least 80% charge
Rooting Procedure
(OPTIONAL) Flash Android 5.1.1 image. This step is not necessarily required. If you are running Android 5.1.1, then you should be fine. However, this is what I had to do, since I got into a bootloop by not checking my version number first (yes, stupid me). Further, if you have any errors or issues below you absolutely will need to perform this step to recover and restart the rooting procedure. Anyway:
Turn off your tablet
Boot into 'download mode' by holding POWER + VOLUME DOWN + HOME. Verify by pressing VOLUME UP
Run program Odin3 v3.10.7.exe
Plug your device to the computer with a USB cable
Verify that Odin message window states "<ID:#/###> Added!!"
Click the "AP" button in Odin and select T817TUVS2AOL1_T817TTMB2AOL1_T817TUVS2AOL1_HOME.tar.md5 file
Press "Start" button and wait for Green "PASS" message to appear. This will take a long time since this is a large file
Your device will automatically reboot
Perform basic setup procedures on Android so that you can access the Settings menu
From this point onward your must perform every step in the exact order as stated. Not doing so seriously risks putting your device into a bootloop or bricking it. You should be able to recover from that, but still...
Enable developer options:
Settings -> About device - click on "Build number" like 10 times until "Developer options" are enabled and button is added to Settings menu
Settings -> Developer options - enable:
Developer options - ON
OEM unlock - ON
USB debugging - ON
Flash TWRP recovery software:
Turn off your tablet
Boot into 'download mode' by holding POWER + VOLUME DOWN + HOME. Verify by pressing VOLUME UP
Run program Odin3 v3.10.7.exe
Plug your device to the computer with a USB cable
Verify that Odin message window states "<ID:#/###> Added!!"
Click the "AP" button in Odin and select twrp_2.8.7.1_LL_5.1.1_t810.tar (drive.google.com/file/d/0BxPb6XhrMsaoN0N6V3JzX290aGc/view?usp=sharing) file
Press "Start" button and wait for Green "PASS" message to appear
Your device will automatically reboot, verify that the tablet boots properly
Copy bootloader and SuperSu to tablet:
With your tablet on, attach it to your computer with a USB cable
Navigate to the root directory of the tablet storage
Copy Tab_S2_t817T_boot.zip (drive.google.com/file/d/0BxPb6XhrMsaob0hyME0zV2EtSnc/view?usp=sharing) and BETA-SuperSU-v2.52.zip (drive.google.com/file/d/0BxPb6XhrMsaoNk9uWkxRZ0wwTE0/view?usp=sharing) files to the root directory
Detach tablet from your computer
Flash custom bootloader with TWRP:
Turn off your tablet
Boot into 'recovery mode' by holding POWER + VOLUME UP + HOME
Select "Install"
Select Tab_S2_t817T_boot.zip and click "Install"
Verify install with slider
STOP HERE!!! READ THE NEXT STEPS CAREFULLY!!!
TWRP will now offer to install SuperSu for you. DON'T DO IT!! Doing this will cause your tablet to bootloop because it is not the right version of SuperSu
Decline the SuperSu installation and restart your tablet
Verify that the tablet boots properly
REPEAT "Flash TWRP recovery software:" instructions. This is a necessary step. Without it your tablet will go into a bootloop and you will need to start the root procedure over. Weird, I know. Just do it.
Flash SuperSu with TWRP:
Turn off your tablet
Boot into 'recovery mode' by holding POWER + VOLUME UP + HOME
Select "Install"
Select BETA-SuperSU-v2.52.zip and click "Install"
Verify install with slider
Reboot the tablet
DONE! Assuming your tablet boots properly your should now be rooted and see the SuperSu app installed on your tablet.
Recovery
If you need to recover from some error you will need to start over completely. Use the Android 5.1.1 image file T817TUVS2AOL1_T817TTMB2AOL1_TMB.zip (same as above) to perform this. You can also use this Android image to restore the device to an unrooted version. This will not restore your warranty or Knox.
Extras
To get rid of the pesky KNOX security notification which will persist, use a program like ROM Toolbox Lite (play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&hl=en). In the App Manager select the following apps and 'freeze' them:
SecurityLogAgent 4.1.4 (this one is critical to freeze!)
KNOX 2.3.0
KNOX 2.3.1
KNOX II 2.3.0
KNOX SetupWizardClient 2.3.0
KnoxFolderContainer 2.4.0
To get rid of the "No SIM card inserted" notification (if you aren't using a SIM card) use the build.Prop Editor in ROM Toolbox Lite. Add the following entry:
Property Name: ro.config.donot_nosim
Property Value: 1
Conclusions
I put this guide together for people who are having trouble finding a simple and easy-to-follow guide for rooting the T817T. Hopefully this can save you a number of frustrating and worrisome hours (not that rooting your Android device is ever a calm undertaking).
Please let me know if there are any errors in the procedure or if you have any suggestions regarding the steps or presentation of the material. Enjoy being a super-user!
Original content: blog.mchristian.co/blogs/post/How-to-Root-Samsung-Tab-S2-T817T/

phduhblog said:
Long time user, first time poster.
First off, let me say, THANK YOU XDA! You guys have been a crazy valuable resource over the years.
However, with regard to the T817T, the documentation is lacking severely. I have created a comprehensive step by step guide to rooting the T817T. Unfortunately, as a first time poster, I cannot post links or anything like that so...if somebody could fix that I would appreciate it. I spent a long time formatting the posting and adding file download links with the XDA formatter so that it wouldn't look like I was link whoring to my blog, just to be told to **** off... . Seeing as that's not possible, here is the url to my blog with the rooting instructions:
blog.mchristian.co/blogs/post/How-to-Root-Samsung-Tab-S2-T817T
Click to expand...
Click to collapse
http://blog.mchristian.co/blogs/post/How-to-Root-Samsung-Tab-S2-T817T
Thanks my friend
Edit: Completely professional and well done how to.. written just the way I like it, fantastic!! I think you should just edit your first post and paste all this in here on XDA... and ill be happy to carry your url link for you.

Complete text of the GUIDE
Edited and posted it above. Good luck with the rooting. Thanks!

An excellent guide. I'd spent the last few hours reading post after post gathering the correct information for the T817T specifically. I had come to the same basic conclusion as your guide states but its great to have some confirmation! I have a few differences in my install process than you did though. I did things in this order:
Enable developer options:
Copy bootloader and SuperSu to tablet:
THEN
Flash TWRP recovery software:
and between 6 and 7
Uncheck AutoReboot in the Options tab
7. Press "Start" button and wait for Green "PASS" message to appear
8. Use Power+VolumeDown+Home to reboot from bootloader and AS SOON as the screen goes black slide your finger from VolumeDown to VolumeUp
This should boot you into TWRP
Flash custom bootloader with TWRP:
after 4:
press "add another zip" and select the SuperSU zip as well.
5. Verify install with slider
6. Reboot
Done
By booting directly into TWRP the stock recovery doesn't have a chance to overwrite it. It won't need to be flashed a second time. You can also flash the kernel (...boot.zip) and SuperSU zip in the same pass. Saves a couple steps.
Either way I can confirm this works and all of the files are correct!
Thanks again for organizing all of this and making this great guide!

patrioticparadox said:
An excellent guide. I'd spent the last few hours reading post after post gathering the correct information for the T817T specifically. I had come to the same basic conclusion as your guide states but its great to have some confirmation! I have a few differences in my install process than you did though. I did things in this order:
Enable developer options:
Copy bootloader and SuperSu to tablet:
THEN
Flash TWRP recovery software:
and between 6 and 7
Uncheck AutoReboot in the Options tab
7. Press "Start" button and wait for Green "PASS" message to appear
8. Use Power+VolumeDown+Home to reboot from bootloader and AS SOON as the screen goes black slide your finger from VolumeDown to VolumeUp
This should boot you into TWRP
Flash custom bootloader with TWRP:
after 4:
press "add another zip" and select the SuperSU zip as well.
5. Verify install with slider
6. Reboot
Done
By booting directly into TWRP the stock recovery doesn't have a chance to overwrite it. It won't need to be flashed a second time. You can also flash the kernel (...boot.zip) and SuperSU zip in the same pass. Saves a couple steps.
Either way I can confirm this works and all of the files are correct!
Thanks again for organizing all of this and making this great guide!
Click to expand...
Click to collapse
I'm glad you have figured out another way! This is turning into what a proper thread on rooting should look like
I had actually tried the non-auto-reboot from Odin method too, but couldn't time the change to VOLUME UP correctly. After a couple times I just gave up and tried things the long way around. Never thought to flash the zip files in the same TWRP session though. I generally like doing things the long way around and getting confirmation that things still work after each and every step. Whatever works though!
Thanks for the reply

phduhblog said:
I'm glad you have figured out another way! This is turning into what a proper thread on rooting should look like
Click to expand...
Click to collapse
Indeed it is.
Are your volume buttons functioning properly after this? Just noticed yesterday mine aren't adjusting the volume.

patrioticparadox said:
Indeed it is.
Are your volume buttons functioning properly after this? Just noticed yesterday mine aren't adjusting the volume.
Click to expand...
Click to collapse
Hmmm, odd. Sorry to hear that. Yes, mine work just fine.

Turns out my volume buttons are fuctioning just fine. I think I just pressed it wrong and didn't have a minute to double check it at the time.

patrioticparadox said:
Turns out my volume buttons are fuctioning just fine. I think I just pressed it wrong and didn't have a minute to double check it at the time.
Click to expand...
Click to collapse
Whew! I'm glad to hear that. Now people can root their T817T without concern!

Yep! Been using this for two weeks now and no problems!

Can anyone confirm that the mobile internet still work when you have a SIM card in? Thanks.

phduhblog said:
Can anyone confirm that the mobile internet still work when you have a SIM card in? Thanks.
Click to expand...
Click to collapse
SIM does not work-- just restored back to stock.. going to wait a little bit before re-rooting.

androidcues said:
SIM does not work-- just restored back to stock.. going to wait a little bit before re-rooting.
Click to expand...
Click to collapse
Hmmm. Well that's good to know at least. Thanks for the update!
Also I'm glad you were able to revert to stock and get it working.

Yeah... Ive fully unrooted and gone back to samsung for a bit.. wont be long because I automatically gravitate back to CM. hehe.
vibration doesnt work on CM... that was a big thing because i rely on tactile vibration for notifications.... (i am deaf so.. the noisy parts are useless ?)
but anyway... taking a moment to thank you again for your writeup...i really needed that...soon after i read your blog i was rooted and rocking!
But Samsung sucks bro... i cant stand all these ****ty apps on my tablet so maybe I'll come back sooner.
0x1
Sent from my Nexus 5X using XDA Premium HD app

androidcues said:
Yeah... Ive fully unrooted and gone back to samsung for a bit.. wont be long because I automatically gravitate back to CM. hehe.
vibration doesnt work on CM... that was a big thing because i rely on tactile vibration for notifications.... (i am deaf so.. the noisy parts are useless )
but anyway... taking a moment to thank you again for your writeup...i really needed that...soon after i read your blog i was rooted and rocking!
But Samsung sucks bro... i cant stand all these ****ty apps on my tablet so maybe I'll come back sooner.
0x1
Sent from my Nexus 5X using XDA Premium HD app
Click to expand...
Click to collapse
Yep, I can definitely see why vibration notifications would be important for you!
As much as I dislike bloatware, from any company, Samsung just makes the most powerful tablets/phones. My best solution is to root and disable all the bloatware.
I'm glad the guide was well received and it seems to work for people.

My mobile data and SIM functions all work fine. Not sure why yours didn't

patrioticparadox said:
My mobile data and SIM functions all work fine. Not sure why yours didn't
Click to expand...
Click to collapse
Awesome! That is weird it didn't work for the other guy. Did you flash the provided Android version first or just go straight into the rooting? Thanks for the update!

phduhblog said:
Awesome! That is weird it didn't work for the other guy. Did you flash the provided Android version first or just go straight into the rooting? Thanks for the update!
Click to expand...
Click to collapse
Sorry for the late reply. I Odined the latest firmware to reset everything to a stock base before then flashing as your steps suggest (with the noted exceptions from my first post). My mobile data has worked flawlessly and I have had zero SIM related issues. In fact, I have had no issues what-so-ever. (I did think I had an issue with my volume rocker not working but that was user error. I have my tablet in a case of sorts and was not pressing hard enough). @phduhblog and @androidcues are you both still experiencing mobile data and SIM issues as of now?

patrioticparadox said:
Sorry for the late reply. I Odined the latest firmware to reset everything to a stock base before then flashing as your steps suggest (with the noted exceptions from my first post). My mobile data has worked flawlessly and I have had zero SIM related issues. In fact, I have had no issues what-so-ever. (I did think I had an issue with my volume rocker not working but that was user error. I have my tablet in a case of sorts and was not pressing hard enough). @phduhblog and @androidcues are you both still experiencing mobile data and SIM issues as of now?
Click to expand...
Click to collapse
Wording changed! Thanks for the update.

One question pls. I have the T817V tab 9.7 w/OEM bootloader option button. Is any of this available to use for my tab? TWRP recovery maybe? Any files? Any reply is appreciated. Novice seeking knowledge. Thank you so much.

HELP, I think I may have finally killed my Tab S2 (T710)

Over the past couple years and up until last week I've been able to kill and revive my tablet. This time I'm really stuck.
Setup: I have TWRP running fine, not sure if it was 3.5.2_9 or 3.6.0. I've playing around with different ROMs for the past few weeks, seeing which one I wanted to use. Friday I reinstalled LineageOS 18.1, but I click the replace/keep up to date option which now guess replaced TWRP because it was no longer there when I booted in recovery.
I've tried reinstalling TWRP, CF autoroot, etc. But the closest I've gotten is TWRP coming up, then displaying errors quickly and the system rebooting. I know just enough to be dangerous, but not enough to know exactly what I'm suppose to do in what order to get the system back up (or which versions of the files I've downloaded I should actually be using.
Any help to get back to where I can run TWRP again would be helpful, I can probably take it from there. I can get the tablet in download mode, but that's about it.

We have same device, but still i can't upgrade my tab in any roms. And unable to install TWRP higher than 3.1 version.

davidzvi said:
Over the past couple years and up until last week I've been able to kill and revive my tablet. This time I'm really stuck.
Setup: I have TWRP running fine, not sure if it was 3.5.2_9 or 3.6.0. I've playing around with different ROMs for the past few weeks, seeing which one I wanted to use. Friday I reinstalled LineageOS 18.1, but I click the replace/keep up to date option which now guess replaced TWRP because it was no longer there when I booted in recovery.
I've tried reinstalling TWRP, CF autoroot, etc. But the closest I've gotten is TWRP coming up, then displaying errors quickly and the system rebooting. I know just enough to be dangerous, but not enough to know exactly what I'm suppose to do in what order to get the system back up (or which versions of the files I've downloaded I should actually be using.
Any help to get back to where I can run TWRP again would be helpful, I can probably take it from there. I can get the tablet in download mode, but that's about it.
Click to expand...
Click to collapse
Have you just tried flashing stock firmware, using odin?

I was trying the CF_autoroot (and other kernels(?)) and TWRP in odin.
Oddly over the weekend I left it plugged in for a day and and when I opened the cover it was in TWRP.
I was able to wipe, format, and load a ROM. But I think I might have broken the battery connection now, it doesn't seem to want to plug into the main board. So it doesn't want to do anything now. I'll probably play around with the connector a bit and see if I can sort that out.
But I'm not sure what @rufio85 issue might be and I would be the last person to advise anyone on this stuff.

Question Download Incomplete, Reboot every 60 Sec?

This was my first attempt at ever trying to put custom rom on a phone, so don't laugh too hard at me. I used the the twrp.img found in this forum, had it going right but when I did something trying to go back to stock for an update, it went into bootloader, but nothing else, no system no recovery. I tried to use the fastboot tool on here, and it reached this and stopped. Any help or is it done for?
PS, I did manage to follow one tutorial to a T, and did great my second time around.

btflyrose said:
This was my first attempt at ever trying to put custom rom on a phone, so don't laugh too hard at me. I used the the twrp.img found in this forum, had it going right but when I did something trying to go back to stock for an update, it went into bootloader, but nothing else, no system no recovery. I tried to use the fastboot tool on here, and it reached this and stopped. Any help or is it done for?
PS, I did manage to follow one tutorial to a T, and did great my second time around.
Click to expand...
Click to collapse
So your second round where you stuck at..?

Have your tried getting factory file...boot img..flashing boot img through fastboot..?

have you tried...fastboot boot " fastboot getvar current-slot " see what slot you on...change to other slot ...see if it boots up...?

What model do you have..?

the more details you give to more people can help you..just saying

I'm sorry, I've not been back online. Single mom, busy. Kids getting older, I have a little more spare time during school hours but this past week has been hectic.
I tried to flash the original boot.img with no luck. It goes black when it connects to a computer but vibrates but isn't recognized on my adb or the fastboot tool. So far nothing.
My second time was another phone, same phone though. OnePlus 10 pro NE2015 model.

The issue also could be that there are no real custom ROMs for this phone yet... you might have flashed a malicious file and killed the phone. Unless you were hopping to GSI. Only real suggestion is to try a complete flash from TWRP or pay for MSM.
If you can't get into recovery, can you flip the boot slot with the hardware combo and get in then? May be your last hope besides EDL/MSM.

This issues happend to Oneplus 9 series with bad update (F.19), but I see this issues for the first time on Oneplus 10 Pro. Is it really on OP10P?

Prant said:
The issue also could be that there are no real custom ROMs for this phone yet... you might have flashed a malicious file and killed the phone. Unless you were hopping to GSI. Only real suggestion is to try a complete flash from TWRP or pay for MSM.
If you can't get into recovery, can you flip the boot slot with the hardware combo and get in then? May be your last hope besides EDL/MSM.
Click to expand...
Click to collapse
How exactly do I do a flip? If it's even possible to get into recovery. So far, I've not had luck.

kouzelnik3 said:
This issues happend to Oneplus 9 series with bad update (F.19), but I see this issues for the first time on Oneplus 10 Pro. Is it really on OP10P?
Click to expand...
Click to collapse
Yes, it's the 10 pro. I was too eager to root a phone and must have missed something, or done something somewhere. I've done several tablets, but not any phone. I've always had Samsung phones through carriers, so I couldn't figure knox out. But I've been researching and reading for months about rooting a phone, and decided that the OP 10 pro would be my first try. I'm not sure where I went wrong. I managed to get a second one, and followed the guide again, and well, that is the one I'm on now, and it seems fine.

btflyrose said:
How exactly do I do a flip? If it's even possible to get into recovery. So far, I've not had luck.
Click to expand...
Click to collapse
AFAIK, according to @g96818 as well, you have to hold all three hardware buttons down, let it attempt to boot, continue holding the buttons and it should like shut off immediately right after the boot logo and switch to the other boot slot.
btflyrose said:
Yes, it's the 10 pro. I was too eager to root a phone and must have missed something, or done something somewhere. I've done several tablets, but not any phone. I've always had Samsung phones through carriers, so I couldn't figure knox out. But I've been researching and reading for months about rooting a phone, and decided that the OP 10 pro would be my first try. I'm not sure where I went wrong. I managed to get a second one, and followed the guide again, and well, that is the one I'm on now, and it seems fine.
Click to expand...
Click to collapse
Yeah, the key to this device is basically do not flash anything to it, just boot from images. You CAN flash TWRP but I would personally recommend against it for daily use right now until data decryption is fixed fully. Just BL unlock, root it, and play with some Magisk modules like V4A, that's all we got on 10Pro for now.

Just some pics of the device...
But @Prant I'm curious to know, what is the difference between having the TWRP and not having it installed regarding rooting? Luckily, OP makes rooting for easier with unlocking the BL. But honestly, the confusion I've had the most understanding in the rooting process at this point is the whole difference between having TWRP and not having it, while installing Magisk.
(Y'all have to excuse me for my not having as much knowledge. I'm just basically a bored at home Mom with kids getting older, and tries to find something to get interested in that wasn't so old lady like. I've never been one to enjoy sewing, knitting, gardening, etc... HA!)

btflyrose said:
But honestly, the confusion I've had the most understanding in the rooting process at this point is the whole difference between having TWRP and not having it, while installing Magisk.
Click to expand...
Click to collapse
This is a bit of a dated thing from 6-8 years ago or so, TWRP used to be the gold standard for recovery on a phone. However, nowadays companies have gotten smarter and want more control over their device, so they add things like Knox (in Samsung) to keep the device "safe." OPPO/OnePlus has started doing this with the OP9 and the OP10 is their first attempt at keeping the device "basically" locked.
Long story short, TWRP is useful to do backups but I've even seen cases of backups on this device in particular failing when restored. And it used to be the main entry point, the first step to rooting any android device. However in recent years, it's become less and less necessary as you can do almost everything you can do in TWRP, through ADB and fastboot. Flashing is still a no go (on this device, thanks to OPPO magic) , but booting a patched image works for now. In the next years I'm sure even that will be secured somehow.
And, haha, there's nothing wrong with getting into tinkering, it's a helluva rabbit hole that's for sure.
Good luck and feel free to reach out if you have any questions.

Prant said:
This is a bit of a dated thing from 6-8 years ago or so, TWRP used to be the gold standard for recovery on a phone. However, nowadays companies have gotten smarter and want more control over their device, so they add things like Knox (in Samsung) to keep the device "safe." OPPO/OnePlus has started doing this with the OP9 and the OP10 is their first attempt at keeping the device "basically" locked.
Long story short, TWRP is useful to do backups but I've even seen cases of backups on this device in particular failing when restored. And it used to be the main entry point, the first step to rooting any android device. However in recent years, it's become less and less necessary as you can do almost everything you can do in TWRP, through ADB and fastboot. Flashing is still a no go (on this device, thanks to OPPO magic) , but booting a patched image works for now. In the next years I'm sure even that will be secured somehow.
And, haha, there's nothing wrong with getting into tinkering, it's a helluva rabbit hole that's for sure.
Good luck and feel free to reach out if you have any questions.
Click to expand...
Click to collapse
Is there a reason that the OP10 doesnt have any roms but the OP9 has lots?

w_tapper said:
Is there a reason that the OP10 doesnt have any roms but the OP9 has lots?
Click to expand...
Click to collapse
Easiest answer is that there is no free / public MSM tool. Which means no way to recover from a bad flash without paying OPPO, essentially. That's not very developer friendly.