HTC 10 *ONE CLICK ROOT*
ANDROID OREO & ALL VERSION
VIDEO DEMOSTRATION
youtu.be/Y00fzX9Ok4g
BOOTLOADER MUST BE UNLOCKED
AND USB DEBUGGING ENABLED
Download File:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HTC-10_ONE-CLICK-ROOT.exe
Thanks to Magisk and Twrp
Celular.Doctor
I will test this for other users, is this MAGISK or SuperSU?
GROOVYJOSHCLARK said:
I will test this for other users, is this MAGISK or SuperSU?
Click to expand...
Click to collapse
It's magisk
stefan1234566789 said:
It's magisk
Click to expand...
Click to collapse
Thanks, I hate magisk, I am a SuperSU guy but I have tested it for others and works
GROOVYJOSHCLARK said:
Thanks, I hate magisk, I am a SuperSU guy but I have tested it for others and works
Click to expand...
Click to collapse
I'm curious, why do you hate magisk? What's it's downside compared to SuperSU?
jabia said:
I'm curious, why do you hate magisk? What's it's downside compared to SuperSU?
Click to expand...
Click to collapse
Loss of ROOT, sound issues with certain AOSP ROMs, buggy interface, continual root permissions denied when set to allowed, ETC. The list goes on and on, but I am NOT saying I will never return to MAGISK as it is great for things like Pay and hiding root. I just cannot use it nor rely on it until it is stable without issues. I run numerous production scripts and remote calls (for work and personally for backups) throughout the night that ALL rely heavily on ROOT, without ROOT, they fail and cannot move onto the next steps. I cannot have these processes fail by losing root, and as of now, MAGISK lost root 5 out of the 10 nights when I test MAGISK. I have tried every version, including the latest and there are still issues with stability.
Again, once these are worked out and once it is stable, I will most definitely be testing it for daily use but it is no where near ready yet.
I should not have said I HATE it, that was the wrong wording and not my intended wording. Readers may see this and get the wrong impression og MAGISK. I should have said, I cannot use it until its stable, so I apologize for that and to the devs of MAGISK, it is not my intention to bad mouth MAGISK. Its just not ready yet for daily use for what I need it for.
GROOVYJOSHCLARK said:
Loss of ROOT, sound issues with certain AOSP ROMs, buggy interface, continual root permissions denied when set to allowed, ETC. The list goes on and on, but I am NOT saying I will never return to MAGISK as it is great for things like Pay and hiding root. I just cannot use it nor rely on it until it is stable without issues. I run numerous production scripts and remote calls (for work and personally for backups) throughout the night that ALL rely heavily on ROOT, without ROOT, they fail and cannot move onto the next steps. I cannot have these processes fail by losing root, and as of now, MAGISK lost root 5 out of the 10 nights when I test MAGISK. I have tried every version, including the latest and there are still issues with stability.
Again, once these are worked out and once it is stable, I will most definitely be testing it for daily use but it is no where near ready yet.
I should not have said I HATE it, that was the wrong wording and not my intended wording. Readers may see this and get the wrong impression og MAGISK. I should have said, I cannot use it until its stable, so I apologize for that and to the devs of MAGISK, it is not my intention to bad mouth MAGISK. Its just not ready yet for daily use for what I need it for.
Click to expand...
Click to collapse
That's weird. I haven't encountered any of these problems. I have used Magisk on RR, LOS, Viper and Leedroid without any problem.
If I'm not mistaken developer of Magisk owns a HTC 10 as daily driver and I thought HTC 10 is the most supported device for using Magisk.
Sir-Shadow said:
That's weird. I haven't encountered any of these problems. I have used Magisk on RR, LOS, Viper and Leedroid without any problem.
If I'm not mistaken developer of Magisk owns a HTC 10 as daily driver and I thought HTC 10 is the most supported device for using Magisk.
Click to expand...
Click to collapse
That may be very true for sense based ROMs but entirely not true for any AOSP ROMs. It's riddled with bugs for AOSP, I don't use any sense based ROMs as my DD but I do test them for others.
Magisk loses root for AOSP users (and not just myself) many others have reported the same (again in AOSP), the audio issues were also ruled to magisk (again may only be on AOSP). So I only ever recommend SuperSU to AOSP users until magisk issues are working on AOSP. Again I am NOT saying root does with MAGISK but it does LOSE root over time so its possible you never noticed it as an issue. It is definitely an issue. You can read about it in the PF forums, or RR forums (basically the most used AOSP forums for the HTC10), its all over the forums.
sent from my HTC 10 droid running AOSP ***note do not PM me, I do not check PM's ever, instead ping me on the forums***
test
works well on htc10 3.16.400.3
GROOVYJOSHCLARK said:
Loss of ROOT, sound issues with certain AOSP ROMs, buggy interface, continual root permissions denied when set to allowed, ETC. The list goes on and on, but I am NOT saying I will never return to MAGISK as it is great for things like Pay and hiding root. I just cannot use it nor rely on it until it is stable without issues. I run numerous production scripts and remote calls (for work and personally for backups) throughout the night that ALL rely heavily on ROOT, without ROOT, they fail and cannot move onto the next steps. I cannot have these processes fail by losing root, and as of now, MAGISK lost root 5 out of the 10 nights when I test MAGISK. I have tried every version, including the latest and there are still issues with stability.
Again, once these are worked out and once it is stable, I will most definitely be testing it for daily use but it is no where near ready yet.
I should not have said I HATE it, that was the wrong wording and not my intended wording. Readers may see this and get the wrong impression og MAGISK. I should have said, I cannot use it until its stable, so I apologize for that and to the devs of MAGISK, it is not my intention to bad mouth MAGISK. Its just not ready yet for daily use for what I need it for.
Click to expand...
Click to collapse
its simple, i use magisk becouse supersu fail in last new versions of android, and as we know chainfire lives supersu... magisk works perfect on android oreo phones, like htc 10 but supersu is fully of bugs. its a fact, chainfire say it, supersu is dead.
hernankano said:
its simple, i use magisk becouse supersu fail in last new versions of android, and as we know chainfire lives supersu... magisk works perfect on android oreo phones, like htc 10 but supersu is fully of bugs. its a fact, chainfire say it, supersu is dead.
Click to expand...
Click to collapse
That's really interesting, I have found the complete exact opposite results. I ONLY use SuperSU, including Oreo 8.1 (AOSP). This could very well be the opposite with Sense OS but not with AOSP and derivatives. I don't run Sense OS in any form other than to test things for other users so my phone is only AOSP, take what I'm saying with a grain of salt if you're a stock Sense user.
sent from my HTC 10 droid running AOSP ***note do not PM me, I do not check PM's ever, instead ping me on the forums***
Did you mean AOSP 8.1 ROM for HTC 10? Is so, which ROM is it? Is it stable enough for daily drive? Thanks.
GROOVYJOSHCLARK said:
That's really interesting, I have found the complete exact opposite results. I ONLY use SuperSU, including Oreo 8.1 (AOSP). This could very well be the opposite with Sense OS but not with AOSP and derivatives. I don't run Sense OS in any form other than to test things for other users so my phone is only AOSP, take what I'm saying with a grain of salt if you're a stock Sense user.
sent from my HTC 10 droid running AOSP ***note do not PM me, I do not check PM's ever, instead ping me on the forums***
Click to expand...
Click to collapse
---------- Post added at 07:38 PM ---------- Previous post was at 07:36 PM ----------
Did you mean AOSP 8.1 for 10? If so, which ROM is it? Is it stable enough for daily drive? Thanks.
GROOVYJOSHCLARK said:
That's really interesting, I have found the complete exact opposite results. I ONLY use SuperSU, including Oreo 8.1 (AOSP). This could very well be the opposite with Sense OS but not with AOSP and derivatives. I don't run Sense OS in any form other than to test things for other users so my phone is only AOSP, take what I'm saying with a grain of salt if you're a stock Sense user.
sent from my HTC 10 droid running AOSP ***note do not PM me, I do not check PM's ever, instead ping me on the forums***
Click to expand...
Click to collapse
Steinard said:
Did you mean AOSP 8.1 ROM for HTC 10? Is so, which ROM is it? Is it stable enough for daily drive? Thanks.
---------- Post added at 07:38 PM ---------- Previous post was at 07:36 PM ----------
Did you mean AOSP 8.1 for 10? If so, which ROM is it? Is it stable enough for daily drive? Thanks.
Click to expand...
Click to collapse
I actually meant AOSP in general (including 8.1 Oreo). AOSP 8.0/1 are still early on in development but try out AOSiP 8.1 or PureFusion 8 if you're itching to test it.
AOSiP works pretty well with most things including ril (cell) but there's an open issue with the main speaker. I used it for my DD for a few days and was pretty happy with it, I only rolled back to ReserectionRemix (N) because I like to watch/listen to Netflix during my workday so no sound killed that idea.
I used PureFusion (8.0) as my DD for a good month straight when it was first released and was really happy with it, I only stopped using PF because the devs are actively working on 8.1 PF so 8 development was moved into 8.1. I will return to one or both of them in time once the bugs are worked out.
Thanks for the quick answer. I guess I will also give PF a try when the bugs are addressed. At the moment I plan to stick to stock Oreo for a while even thoogh the battery life is realy not that great
GROOVYJOSHCLARK said:
I actually meant AOSP in general (including 8.1 Oreo). AOSP 8.0/1 are still early on in development but try out AOSiP 8.1 or PureFusion 8 if you're itching to test it.
AOSiP works pretty well with most things including ril (cell) but there's an open issue with the main speaker. I used it for my DD for a few days and was pretty happy with it, I only rolled back to ReserectionRemix (N) because I like to watch/listen to Netflix during my workday so no sound killed that idea.
I used PureFusion (8.0) as my DD for a good month straight when it was first released and was really happy with it, I only stopped using PF because the devs are actively working on 8.1 PF so 8 development was moved into 8.1. I will return to one or both of them in time once the bugs are worked out.
Click to expand...
Click to collapse
Steinard said:
Thanks for the quick answer. I guess I will also give PF a try when the bugs are addressed. At the moment I plan to stick to stock Oreo for a while even thoogh the battery life is realy not that great
Click to expand...
Click to collapse
I hear ya on the battery life. If you wanted to taste AOSP O either option would work AOSiP or PF.
Personally I'm using RR (N OS) on (MM firmware) until the buggies are sorted. This setup works pretty good with no issues and is my DD I fall back to when I need stability. ReserectionRemix Nougat is pretty flawless in my opinion without the need to tweak or use any aftermarket kernels.
sent from my HTC 10 droid running AOSP ***note do not PM me, I do not check PM's ever, instead ping me on the forums***
This does not work on Verizon. Only installed root checker pro. Had to manually fastboot flash twrp, then flashed latest Magisk.
I can't Download the exe file
Does it work on 3.16.401.2?
Sent from my [device_name] using XDA-Developers Legacy app
Tried it on US Unlocked model, working fine so far, thanks!
adb service out of date
hi everyone, im getting one message saying "adb service is out of service. killing..." does anyone have any clue?
Fails to work on Unlocked Sprint HTC 10
Cmd "Adb devices" sees the phone, but OneClickRoot can't see it, just says "waiting for device" and error: *something protocol* sorry-its late and I'm frustrated with it.
OneClickRoot did *almost* work, as it installed Root Checker the first time I tried, but then it failed a couple times, saying "adb didn't ack", even if I manually terminated the process in Task Mgr -Win10 latest update PC. It kept killing and restarting and spitting out daemon error msgs. It said it installed TWRP at least once, but I'm not convinced anything has installed correctly.
The most recent fail had me stuck in Download Mode screen with Start Downloading highlighted but all buttons unresponsive. After forced reboot, the device restarted fine, but now OneClickRoot keeps saying device disconnected even though CMD/adb can see it.
Using original HTC cable and the PC USB port that worked fine for unlocking with HTVdev procedure.
This phone has me more than thoroughly annoyed lately. Thanks in advance for any help and input.
Related
I've been a member since my first ever android device, HTC Wildfire Mini. I've rooted and installed custom ROMs since back then. Ever since grabbing my self a Pixel device I felt all my needs were catered for, until now.
I miss managing my standby time battery using Greenify and a custom kernel. Not that I don't get great standby time on my phone currently but I feel the itch to get tweaking again. haha oh I miss Viper4Android
I was wondering:
1. Can I still have root access and use Google Pay/mobile banking apps?
2. Xposed framework, is that still a thing? haha I used to love those little tweaks.
3. ROMs, what's everyone using?
4. I've not used Magisk before, can anyone point me in the right direction?
Thanks,
bleepsake said:
I've been a member since my first ever android device, HTC Wildfire Mini. I've rooted and installed custom ROMs since back then. Ever since grabbing my self a Pixel device I felt all my needs were catered for, until now.
I miss managing my standby time battery using Greenify and a custom kernel. Not that I don't get great standby time on my phone currently but I feel the itch to get tweaking again. haha oh I miss Viper4Android
I was wondering:
1. Can I still have root access and use Google Pay/mobile banking apps?
2. Xposed framework, is that still a thing? haha I used to love those little tweaks.
3. ROMs, what's everyone using?
4. I've not used Magisk before, can anyone point me in the right direction?
Thanks,
Click to expand...
Click to collapse
Welcome Back!
1. Yes, google pay and most banking apps work but I believe it depends on what bank you use. (I use Chase)
2. Xposed is questionable at best for the moment, at least for Pie. It's still in beta for 8.1 and, as far as I know, Rovo89 hasn't mentioned any development in that regard
3. Personally, I prefer stock. I use elemental kernel, magisk modules and substratum.
4. Magisk is simple enough to use, but some have had issues since Pie. To get a general idea of how magisk works, start here: https://forum.xda-developers.com/pixel-2-xl/development/2017-11-6-root-pixel-2-xl-t3701176
bleepsake said:
I've been a member since my first ever android device, HTC Wildfire Mini. I've rooted and installed custom ROMs since back then. Ever since grabbing my self a Pixel device I felt all my needs were catered for, until now.
I miss managing my standby time battery using Greenify and a custom kernel. Not that I don't get great standby time on my phone currently but I feel the itch to get tweaking again. haha oh I miss Viper4Android
I was wondering:
1. Can I still have root access and use Google Pay/mobile banking apps?
2. Xposed framework, is that still a thing? haha I used to love those little tweaks.
3. ROMs, what's everyone using?
4. I've not used Magisk before, can anyone point me in the right direction?
Thanks,
Click to expand...
Click to collapse
1. I personally don't use any banking apps for making payments but from doing some reading it seems most will work as long as you don't have the Xposed framework installed.
2. It is a thing up to Oreo. It is still in beta for Oreo, however when I used it I had no issues. It felt stable as far as I'm concerned. However, it did slow down my device a bit and I also found alternate apps for the Xposed mods I used.
3. I'm on Liquid Remix and I love it! HavocOS is really great too. I've been a long time Flash kernel user, but now that is EOL. I have now switched to Kirisakura.
4. You just need to download the Magisk zip from the official thread and flash it in recovery. After you reboot you'll see the Magisk Manager app and it's pretty straightforward and self-explanatory at that point!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello my fellow SM-T560NU (gtelwifiue) owning friends, I thought I'd share with you my build of LineageOS 15.1.
This build contains the July 5 2019 security patch level. Please leave a thumbs up if this is useful to you.
If you need root, flash Magisk from recovery and install Magisk Manager.
I you wish to install the Google apps, flash opengapps from recovery after first boot (you need to get the ARM version for Android 8.1 nano package is recommended).
Code:
All information and files — both in source and compiled form — are provided on an as is basis.
No guarantees or warranties are given or implied. The user assumes all risks of any damages
that may occur, including but not limited to loss of data, damages to hardware, or loss of
business profits. Please use at your own risk. Note that unless explicitly allowed by the warranty
covering your device, it should be assumed that any warranty accompanying your device will
be voided if you tamper with either the system software or the hardware.
Download link: lineage-15.1-20190707-UNOFFICIAL-gtelwifiue.zip
Source: Galaxy-MSM8916 on Github
I have one of these tablets and would love to use it but the custom rom seems to slow it down. It's Android 7. I have TWRP in it but I cannot seem to find a lighter rom to help speed things up. Any thoughts, suggestions?
upyisfar said:
Hello my fellow SM-T560NU (gtelwifiue) owning friends, I thought I'd share with you my build of LineageOS 15.1.
This build contains the April 5 2019 security patch level, and I have not encountered any issues with it so far. Please leave a thumbs up if this is useful to you. I am planning to produce more builds of this ROM in the coming months.
Download link: lineage-15.1-20190409-UNOFFICIAL-gtelwifiue.zip
Source: Galaxy-MSM8916 on Github
Click to expand...
Click to collapse
Appreciate it. I hope you continue to support this tablet of mine ! I've been a fan of LineageOS for awhile !
Build 20190516
Here is a new build of that includes the May 5th 2019 Android security patch level.
lineage-15.1-20190516-UNOFFICIAL-gtelwifiue.zip
Can I install this ROM on a SM-T560 (Wi-Fi) tablet?
davideakc said:
Can I install this ROM on a SM-T560 (Wi-Fi) tablet?
Click to expand...
Click to collapse
Hello, I don't know if you can. This ROM is for devices codenamed gtelwifiue. You should search the forum and find out if the SM-T560 falls under that category.
Zbanded said:
I have one of these tablets and would love to use it but the custom rom seems to slow it down. It's Android 7. I have TWRP in it but I cannot seem to find a lighter rom to help speed things up. Any thoughts, suggestions?
Click to expand...
Click to collapse
Anything older than Nougat will probably suffer from multiple security vulnerabilities. Lineage 15.1 is the only ROM I found that works bug free on my tablet (14.1 has camera issues and 16.0 doesn't wake up when pushing the home button).
upyisfar said:
Anything older than Nougat will probably suffer from multiple security vulnerabilities. Lineage 15.1 is the only ROM I found that works bug free on my tablet (14.1 has camera issues and 16.0 doesn't wake up when pushing the home button).
Click to expand...
Click to collapse
same boat i am in sir
terribly slow with lineage 16
Here is a new build of that includes the June 5th 2019 Android security patch level.
lineage-15.1-20190612-UNOFFICIAL-gtelwifiue.zip
upyisfar said:
Here is a new build of that includes the June 5th 2019 Android security patch level.
Click to expand...
Click to collapse
What is the process after I download the file?
Just open it?
I am new to these kind of updates. Thank you for the post. Trying to get some good lock options on my 560.
tc3500 said:
What is the process after I download the file?
Just open it?
I am new to these kind of updates. Thank you for the post. Trying to get some good lock options on my 560.
Click to expand...
Click to collapse
Hi @tc3500. If you have a previous build of lineage os 15.1 installed you can just flash the new zip in twrp and then reboot. If your tablet is stock, then you need to first root it and then install twrp recovery for the gtelwifiue first. The procedure for doing this is explained in another post on the forum. Please ensure that your model is SM T560NU or else this ROM might not work.
upyisfar said:
Hi @tc3500Please ensure that your model is SM T560NU or else this ROM might not work.
Click to expand...
Click to collapse
I don't have Lineage and have not used TWRP.
But in will search for the thread with the information.
It has been awhile since I rooted a device. But I should be able to.
Thanks very much for your reply. I appreciate it.
.....And my model is exactly that number.
Says it's SM-T560NU. running 7.1.1, last patch 10/1/17.
---------- Post added at 11:54 AM ---------- Previous post was at 11:41 AM ----------
tc3500 said:
.....and my model is exactly that number.
Says it's sm-t560nu. Running 7.1.1, last patch 10/1/17.
Click to expand...
Click to collapse
sm-t560nuueu1cqk2.
tc3500 said:
I don't have Lineage and have not used TWRP.
But in will search for the thread with the information.
It has been awhile since I rooted a device. But I should be able to.
Thanks very much for your reply. I appreciate it.
.....And my model is exactly that number.
Says it's SM-T560NU. running 7.1.1, last patch 10/1/17.
Click to expand...
Click to collapse
From memory, I rooted my tablet by flashing CF-Auto-Root-gtelwifiue-gtelwifiue-smt560nu.zip using Odin (PDA button)on Windows. Can't remember if that gave me twrp or if I had to install it seperately. Hope this helps a bit.
Note: Enable Developer Options: go to Settings -> About device. Tap 7 times on Build number to enable Developer options. Enable OEM unlock and USB debugging options ( Settings -> Developer options )
Note: you will need to have the Samsung USB drivers installed, you can get those by installing the Samsung Kyes software.
Note: Make sure your device is in ODIN download mode (usually you can get there by holding VolDown+Home+Power when the device is turned off)
Backup of my twrp recovery in case you need it.
upyisfar said:
Note: you will need to have the Samsung USB drivers installed, you can get those by installing the Samsung Kyes software.
Click to expand...
Click to collapse
I will download TWRP and the drivers to my laptop.
The other functions are done. Really awesome of you to take your time and reply.
tc3500 said:
I will download TWRP and the drivers to my laptop.
The other functions are done. Really awesome of you to take your time and reply.
Click to expand...
Click to collapse
You're welcome. I hope you succeed at installing LineageOS 15.1 on your tablet. If anything goes wrong, you can download the original firmware for your device from the sammobile.com website and flash using 0din.
upyisfar said:
You're welcome. I hope you succeed at installing LineageOS 15.1 on your tablet. If anything goes wrong, you can download the original firmware for your device from the sammobile.com website and flash using 0din.
Click to expand...
Click to collapse
I have all of the files downloaded to my laptop.
And that took some time. I got a Note 9 last year and I rarely even turn my PC on anymore. So there were many updates and and misc things to attend. Also it is frustratingly slow compared to my phone, haha.
I do need to get CF Root.
But my concern is that my Tab E is a Wifi model. And I am not sure how to verify if it will accept this modification.
It is definitely an SM-T560NU. Specifically an
SM-T560NUUEU1CQK2. I think it's an A3L, not a
gtlewifiue. So I am trying to figure that out. I backed up the device and don't mind trying to move forward if there is more of a chance that I can at least recover it to oem rather than brick it. Any advice on verification of model or recovery if install fails?
Only a guess or opinion, I know that there are no guarantees, lol. But it is very slow and I do need to make my best attempt to improve it.
Thanks.
tc3500 said:
I have all of the files downloaded to my laptop.
And that took some time. I got a Note 9 last year and I rarely even turn my PC on anymore. So there were many updates and and misc things to attend. Also it is frustratingly slow compared to my phone, haha.
I do need to get CF Root.
But my concern is that my Tab E is a Wifi model. And I am not sure how to verify if it will accept this modification.
It is definitely an SM-T560NU. Specifically an
SM-T560NUUEU1CQK2. I think it's an A3L, not a
gtlewifiue. So I am trying to figure that out. I backed up the device and don't mind trying to move forward if there is more of a chance that I can at least recover it to oem rather than brick it. Any advice on verification of model or recovery if install fails?
Only a guess or opinion, I know that there are no guarantees, lol. But it is very slow and I do need to make my best attempt to improve it.
Thanks.
Click to expand...
Click to collapse
From what I gather the letters and digits that follow SM-T560NU describe the carrier or the country of origin but I could be wrong.
I can't advise you to try or not to try flashing this ROM but there is near certainty that you can restore your original firmware from this site using the Odin method if anything goes wrong as I've mentioned in my previous post. If what you're after is speed you could even flash an older firmware (lollipop or marshmallow) and disable auto-update but you'd be left exposed to multiple android security vulnerabilities that aren't present in this updated ROM.
upyisfar said:
From what I gather the letters and digits that follow SM-T560NU describe the carrier or the country of origin but I could be wrong.
I can't advise you to try or not to try flashing this ROM but there is near certainty that you can restore your original firmware from this site using the Odin method if anything goes wrong as I've mentioned in my previous post. If what you're after is speed you could even flash an older firmware (lollipop or marshmallow) and disable auto-update but you'd be left exposed to multiple android security vulnerabilities that aren't present in this updated ROM.
Click to expand...
Click to collapse
I keep the tablet pretty clean. It's an 'extra' device.
Don't really store anything on it. Use if for the web and take it on the boat or guests can use it. I will gl with 15.1 and see what happens. Thanks so much.
I did get the Firmware downloaded, that site is SLOW if you're cheap like me, haha. Hope your day is a good one.
upyisfar said:
From what I gather the letters and digits that follow SM-T560NU describe the carrier or the country of origin but I could be wrong.
I can't advise you to try or not to try flashing this ROM but there is near certainty that you can restore your original firmware from this site using the Odin method if anything goes wrong as I've mentioned in my previous post. If what you're after is speed you could even flash an older firmware (lollipop or marshmallow) and disable auto-update but you'd be left exposed to multiple android security vulnerabilities that aren't present in this updated ROM.
Click to expand...
Click to collapse
Does this look correct?
Is it the 0:[com5] that let's it know to flash the tablet and not my laptop? Lol......
---------- Post added at 10:38 PM ---------- Previous post was at 10:12 PM ----------
@upyisfar....
Did I need to install Lineage or TWRP to the tablet before rooting?
I used the cf-auto root file from the XDA Thread on rooting the sm-t569nu.
......here.... https://consumingtech.com/how-to-root-the-samsung-galaxy-tab-a-9-7/
tc3500 said:
Does this look correct?
Is it the 0:[com5] that let's it know to flash the tablet and not my laptop? Lol......
---------- Post added at 10:38 PM ---------- Previous post was at 10:12 PM ----------
@upyisfar....
Did I need to install Lineage or TWRP to the tablet before rooting?
I used the cf-auto root file from the XDA Thread on rooting the sm-t569nu.
......here.... https://consumingtech.com/how-to-root-the-samsung-galaxy-tab-a-9-7/
Click to expand...
Click to collapse
When I did mine almost a year ago, I rooted first, then I flashed the TWRP img from an app such as rashr or flashify (might have to install the SuperSU app first to get the permission dialogs). Then rebooted into recovery and flashed lineage from there. But now I'm wondering if you might be able to flash TWRP directly from Odin without needing to root first. I wish someone with a fresh experience could chime in here.
Anyhow here's a video I came across that might be helpful to you:
Samsung Galaxy Tab E 9.6 Root & Install TWRP Recovery 100% Working
And yes the SamMobile site is painfully slow but it is a lifesaver if you brick your device. Once you have obtained the firmware, it is really easy to recover your device with Odin.
Hello my friends, we want to participate in the largest number of members to support oneplos 7T ( hotdogb ) For his support of Rom havos os
As you know, support stopped at the beginning of the year and we want support for this Rom .
Do you support the idea?
تم الإرسال من HD1903 باستخدام Tapatalk
slsl20005 said:
Hello my friends, we want to participate in the largest number of members to support oneplos 7T ( hotdogb ) For his support of Rom havos os
As you know, support stopped at the beginning of the year and we want support for this Rom .
Do you support the idea?
تم الإرسال من HD1903 باستخدام Tapatalk
Click to expand...
Click to collapse
The dev of those old builds doesn't have the device. He was blind building and decided not to continue. So I don't think this will happen unless you know someone willing to maintain for the device.
I support too. I miss using Havoc OS after shifting from OP6 to OP7T.
shaunakdsilva said:
I support too. I miss using Havoc OS after shifting from OP6 to OP7T.
Click to expand...
Click to collapse
The same thing [emoji21]
تم الإرسال من HD1903 باستخدام Tapatalk
I'm thinking about buying the 7T but I'm not sure because I have been using Havoc for years on my Moto and really love it. Hope Havoc comes to 7T soon.
havoc? that's a mess...why people like that [email protected]#@%
We've got RR
There is no scope for development of more roms unless a proper working recovery is available on op7t
0402Aman said:
There is no scope for development of more roms unless a proper working recovery is available on op7t
Click to expand...
Click to collapse
There is no need of recovery to have roms developed for this device. There are already two fully functional roms MSM Xtended and RR available and being used.
The issue anyway I believe is a lot of developers choose to go with Pro series like 7Tpro 7Pro or 8 series. So less developers results in less development.
Sent from my HD1901 using Tapatalk
Who wants to build when flashing is such a pita no proper functioning twrp/recovery is the main reason we have such limited development for 7t series . Also Android 10 out of the box hasn't helped. I believe the decryption issued faced in the development of twrp for 7t isn't present in op8 or the Nord. The issue is with OnePlus and how they have implemented broken decryption on the 7t but not on the op8 or Nord.
slsl20005 said:
Hello my friends, we want to participate in the largest number of members to support oneplos 7T ( hotdogb ) For his support of Rom havos os
As you know, support stopped at the beginning of the year and we want support for this Rom .
Do you support the idea?
تم الإرسال من HD1903 باستخدام Tapatalk
Click to expand...
Click to collapse
No flame, but that was legit my genuine reaction at this post
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That rom was (and probably still is) just a big mess, why would you even want something like that when you have already other better options such as AOSiP?
If it will come, it will come, i don't think there's need to make a post just to let other people know you want it, that's my 2 cents
See ya.
0402Aman said:
There is no scope for development of more roms unless a proper working recovery is available on op7t
Click to expand...
Click to collapse
TWRP has absolutely nothing to do with lack of development.
People who owns this device simply do not have enough resources to build ROMs. The actual work is already laid out.
---------- Post added at 11:26 AM ---------- Previous post was at 11:23 AM ----------
a g bell said:
Who wants to build when flashing is such a pita no proper functioning twrp/recovery is the main reason we have such limited development for 7t series . Also Android 10 out of the box hasn't helped. I believe the decryption issued faced in the development of twrp for 7t isn't present in op8 or the Nord. The issue is with OnePlus and how they have implemented broken decryption on the 7t but not on the op8 or Nord.
Click to expand...
Click to collapse
It's a PITA? Tell whatever rom "dev" to build correctly then.
I installed a custom rom with literally 2 commands, it was easier without TWRP if I'm being honest.
Hint; AOSiP developer knows what he is doing.
(And decryption is only a problem on OOS so unrelated to custom ROMs).
And, read my comment above.
Why not ask for lineage OS? I already heard the news of carbon rom support coming months ago. We got omni too but God knows what's happening. This device is going down to be the least active custom development in One Plus history....
Lossyx said:
TWRP has absolutely nothing to do with lack of development.
People who owns this device simply do not have enough resources to build ROMs. The actual work is already laid out.
---------- Post added at 11:26 AM ---------- Previous post was at 11:23 AM ----------
It's a PITA? Tell whatever rom "dev" to build correctly then.
I installed a custom rom with literally 2 commands, it was easier without TWRP if I'm being honest.
Hint; AOSiP developer knows what he is doing.
(And decryption is only a problem on OOS so unrelated to custom ROMs).
And, read my comment above.
Click to expand...
Click to collapse
Sorry you installed and fixed any possible issues locally without a pc or another device with fastboot enabled ? the fact is flashing is easier with twrp working . I wouldn't test my go to Devs build for this reason not because it would be unstable but he is not that arrogant to think his build couldn't have issues. I use my device as a daily driver and don't want to carry otg and two phones around with me in case l needs fastboot. Sorry but l disagree but respect what you mean.
a g bell said:
Sorry you installed and fixed any possible issues locally without a pc or another device with fastboot enabled ? the fact is flashing is easier with twrp working . I wouldn't test my go to Devs build for this reason not because it would be unstable but he is not that arrogant to think his build couldn't have issues. I use my device as a daily driver and don't want to carry otg and two phones around with me in case l needs fastboot. Sorry but l disagree but respect what you mean.
Click to expand...
Click to collapse
>Who wants to build when flashing is such a pita no proper functioning twrp/recovery
This is what you said. I am simply correcting you that it's completely false.
I understand that TWRP is convenient in case any issues appear, however, I have been running an unofficial build for the last 5 months now (including 3 weeks where I was without PC) and never had any issues that forced to me clean flash(or any use of twrp/fastboot).
Most ROMs don't and shouldn't have any issues that cause clean/dirty flash, rather in most cases, it's a user error, which is completely unrelated on why the lack of ROM development.
Lossyx said:
>Who wants to build when flashing is such a pita no proper functioning twrp/recovery
This is what you said. I am simply correcting you that it's completely false.
I understand that TWRP is convenient in case any issues appear, however, I have been running an unofficial build for the last 5 months now (including 3 weeks where I was without PC) and never had any issues that forced to me clean flash(or any use of twrp/fastboot).
Most ROMs don't and shouldn't have any issues that cause clean/dirty flash, rather in most cases, it's a user error, which is completely unrelated on why the lack of ROM development.
Click to expand...
Click to collapse
Most roms shouldn't have issues most don't but sometimes when updates happen things go borked as l am sure you know. To say what l have said is completely false kind of contradicts saying twrp is convenient meaning finding a device with fastboot can be more of a pita than simply booting twrp recovery. I am sure that there are many people who have bought the op7t and are disappointed that twrp is the way it is.
Betting there put off by having to use command line to do stuff that they have done on most of there previous devices using twrp.
Some ROM /kernel developers build to share and get known others don't of course. The ones that do would be thinking what's the point of building if only 10 people are going to flash.Which in my opinion will reduce the amount of roms/kernels being developed for the op7t.
The blame is simply in oneplus's lap.i have read a post stateing the next update description will be fixed I'd post a link but about to crash.leta hope they were truthful
rob420p said:
The blame is simply in oneplus's lap.i have read a post stateing the next update description will be fixed I'd post a link but about to crash.leta hope they were truthful
Click to expand...
Click to collapse
Lol was that my post in twrp thread?
a g bell said:
Lol was that my post in twrp thread?
Click to expand...
Click to collapse
By truthful I sent oneplus
Lossyx said:
TWRP has absolutely nothing to do with lack of development.
People who owns this device simply do not have enough resources to build ROMs. The actual work is already laid out.
---------- Post added at 11:26 AM ---------- Previous post was at 11:23 AM ----------
It's a PITA? Tell whatever rom "dev" to build correctly then.
I installed a custom rom with literally 2 commands, it was easier without TWRP if I'm being honest.
Hint; AOSiP developer knows what he is doing.
(And decryption is only a problem on OOS so unrelated to custom ROMs).
And, read my comment above.
Click to expand...
Click to collapse
Me and a few others built everything over the last 10 months since 7t release. Mostly we all settled on something to stick with. Twrp is no issue, I agree, but people acting like there is none is kinda shortsighted. The Chinese twrp is absolutely impeccable on oos or custom.
So I came back to the forum after 6 months and was pleasantly surprised by the number of custom roms available now. From the few (currently trending) threads I checked out, I see that either there are still some kind of bugs are still lingering or the dev abandoned the project or the thread was closed or ... I think you get the point. For this reason, I'd rather stick with the official stock rom but I never quite liked the bloatware (both mi and google) and google tracking. To maximise performance and battery life, I wish to clean my rom of all of these stuff or, if possible, install a pre-configured one.
I have some questions though:-
1. Best way to debloat?
Yes, I have tried adb uninstall command when I first got the phone but for some reason, that didn't work. I saw a recent guide on the forum for this purpose that I could try later.
2. Any experience with microG on MIUI?
I don't know if it's possible/working on MIUI roms since this is my first Xiaomi device.
3. Recommended custom ROM?
I may have missed out on all the good stuff during my absence. If you could recommend a rom you find the most stable and clean, even if it is AOSP, it would save me a lot of time.
Look, you are probably going to tell me that I could have done a bit more search on my own before posting here. The thing is, I have returned to the whole modding stuff after 4 years so lest I might break/mess up things, I deemed it more reasonable to ask here.
Hope someone sees this. Thank you.
You're looking for the exact same thing I did.
For me the solution was lineageos with microg, magisk, fdroid store + aurora store.
Lineageos has some minor bugs for me, as well as cameras not working properly.
Reason for most bugs in the most roms is probably that they are based on Android 10,
the devs will probably be able to solve all the bugs as soon as Xiaomi releases miui 12 for this device, which will be based on Android 10.
What you are looking for is probably miui EU rom.
You can easily debloat most of the unwanted sofware with "Xiaomi ADB/Fastboot tools".
Your problems with ADB probably has to do with SU priviligies.
If I remeber correctly you have to use Xposed framework in order to get microg running on miui, I could be wrong on this!
Hope this helps a bit!
SkogstaTarzan said:
You're looking for the exact same thing I did.
For me the solution was lineageos with microg, magisk, fdroid store + aurora store.
Lineageos has some minor bugs for me, as well as cameras not working properly.
Reason for most bugs in the most roms is probably that they are based on Android 10,
the devs will probably be able to solve all the bugs as soon as Xiaomi releases miui 12 for this device, which will be based on Android 10.
What you are looking for is probably miui EU rom.
You can easily debloat most of the unwanted sofware with "Xiaomi ADB/Fastboot tools".
Your problems with ADB probably has to do with SU priviligies.
If I remeber correctly you have to use Xposed framework in order to get microg running on miui, I could be wrong on this!
Hope this helps a bit!
Click to expand...
Click to collapse
Thanks! I am more inclined to use vanilla Android than MIUI. At least now I know my desired setup is within the realm of possibility. Will surely give LineageOS a try.
Is is worth rooting the Pixel 6 Pro now that one doesn't have to disable verity and because repainter now requires root to apply the AMOLED background? If so, what are the steps for installing OTAs, and what are the chances of bricking your device. If you have rooted, do you use quick switch and do you think it is worth it? ThanksIs is worth rooting the Pixel 6 Pro now that one doesn't have to disable verity and because repainter now requires root to apply the AMOLED backround? If so,
It has always been worth it imho. Adaway, V4A, SwiftBackup, AinurNarsil, Substratum... there is a lot of stuff you can't do without root. Especially decent adblock, backup and better music is important to me. All stuff Google could implement on its own without issues, but Google being Google...
With Zygisk/hide & the fix for SafetyNet, all my apps/banking stuff/GPay is working fine, so there is no "downside" to rootinng, except updating firmware.
By updating firmware you mean OTAs right? What are the steps for installing them?
Divine Bicycle said:
By updating firmware you mean OTAs right? What are the steps for installing them?
Click to expand...
Click to collapse
Hi. Click the How To Guide filter above the Pixel 6 Pro section and you'll find all the directions you need.
Keep in mind that although disabling Verity and Verification are no longer required for root, some custom kernels for stock still require that. If you're not going to ever use a custom kernel, then it's not a concern.
At least one custom kernel developer wasn't sure if it was still necessary so still advises it for use with their custom kernel.
At this point, I'm reversing my own personal expression and still planning on disabling then when the late January update comes out side I use that custom kernel, at least until another guinea pig reports it's not necessary, or I have time to make sure I have everything backed up and try it myself.
It's possible I'll have time when that update comes out.
Morgrain said:
It has always been worth it imho. Adaway, V4A, SwiftBackup, AinurNarsil, Substratum... there is a lot of stuff you can't do without root. Especially decent adblock, backup and better music is important to me.
Click to expand...
Click to collapse
Can you explain the "better music" part; and, is substratum still in development? I thought it was heavily discontinued.
RetroTech07 said:
Can you explain the "better music" part; and, is substratum still in development? I thought it was heavily discontinued.
Click to expand...
Click to collapse
V4A is supposed to make your music sound better. I've never used it, but a lot of rooters swear by it.
roirraW edor ehT said:
At this point, I'm reversing my own personal expression and still planning on disabling then when the late January update comes out side I use that custom kernel, at least until another guinea pig reports it's not necessary, or I have time to make sure I have everything backed up and try it myself.
It's possible I'll have time when that update comes out.
Click to expand...
Click to collapse
I am doing the same. I have it disabled on the December build and will keep it disabled on the January build just so I have some flexibility if I decided to use a kernel that requires it to be disabled. Currently I'm on Kiri so I don't need it disabled, but my fickle mind may want to switch for whatever mad reason it gives me
Lughnasadh said:
I am doing the same. I have it disabled on the December build and will keep it disabled on the January build just so I have some flexibility if I decided to use a kernel that requires it to be disabled. Currently I'm on Kiri so I don't need it disabled, but my fickle mind may want to switch for whatever mad reason it gives me
Click to expand...
Click to collapse
I'm not entirely sure on this...have we established whether disabling verity/verification still results in Rescue Party on the factory boot image, patched or no?
roirraW edor ehT said:
V4A is supposed to make your music sound better. I've never used it, but a lot of rooters swear by it.
Click to expand...
Click to collapse
I use it alongside JamesDSP (I really prefer the bass of JamesDSP over V4A) and have since Ice Cream Sandwich. I'm not sure if "better" is the right word, but it does allow you to adjust the sound more the way you want it.
Lughnasadh said:
I am doing the same. I have it disabled on the December build and will keep it disabled on the January build just so I have some flexibility if I decided to use a kernel that requires it to be disabled. Currently I'm on Kiri so I don't need it disabled, but my fickle mind may want to switch for whatever mad reason it gives me
Click to expand...
Click to collapse
I love how often you find the upside-down smiley useful. LOL! I often don't know whether to like, love, laugh, or wow at your posts. Madness for everyone!
Edit: Even my one cat thinks it's funny.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Sorry guys i have to post here since no one answered my 5 years ago posts asking about stuff, so i have to say it here
Note 10 plus when are we getting the ui 4.0?? It s 11th of jan already and i have only december security update
ramharb said:
Sorry guys i have to post here since no one answered my 5 years ago posts asking about stuff, so i have to say it here
Note 10 plus when are we getting the ui 4.0?? It s 11th of jan already and i have only december security update
Click to expand...
Click to collapse
Hi, check over here:
Samsung Galaxy Note 10+
The Samsung Galaxy Note 10+ is a 6.8" phone with a 1440x3040p resolution display. The Exynos 9825/Snapdragon 855 chipset is paired with 12GB of RAM and 256/512GB of storage. The main camera is 12+12+16MP and the selfie camera is 10MP. The battery has a 4300mAh capacity.
forum.xda-developers.com
Cheers
ramharb said:
Sorry guys i have to post here since no one answered my 5 years ago posts asking about stuff, so i have to say it here
Note 10 plus when are we getting the ui 4.0?? It s 11th of jan already and i have only december security update
Click to expand...
Click to collapse
This really isn't the place to ask about anything not related to the Pixel 6 Pro. As for as the P6P and the January update, it's been previously announced that it would come for the P6 & P6P in late January.
December 2021 Update Paused
V0latyle said:
I'm not entirely sure on this...have we established whether disabling verity/verification still results in Rescue Party on the factory boot image, patched or no?
Click to expand...
Click to collapse
I haven't seen or heard of any changes that would say otherwise, but I could be wrong. The only change that I'm aware of is the change in Canary Magisk 23016 that eliminates the need to disable verity & verification when rooting. Thus, I would imagine that disabling those would still result in Rescue Party on the stock boot image since Canary Magisk is not involved, as well as on some custom kernels without being rooted (e.g. CleanSlate where tbalden isn't sure if it is still needed with his kernel and I believe he disables verity & verification just in case).
So my understanding is that on stock boot image disabling those will result in Rescue Party, on a Canary Magisk 23016 patched boot image it will not, and for some custom kernels (without being rooted) it may or may not depending on the kernel and whether the magiskboot binaries the kernel uses were updated to 23016.
That is, if I'm understanding you correctly.
roirraW edor ehT said:
I love how often you find the upside-down smiley useful. LOL! I often don't know whether to like, love, laugh, or wow at your posts. Madness for everyone!
Edit: Even my one cat thinks it's funny.
Click to expand...
Click to collapse
Embrace the madness!!!
Lughnasadh said:
I haven't seen or heard of any changes that would say otherwise, but I could be wrong. The only change that I'm aware of is the change in Canary Magisk 23016 that eliminates the need to disable verity & verification when rooting. Thus, I would imagine that disabling those would still result in Rescue Party on the stock boot image since Canary Magisk is not involved, as well as on some custom kernels without being rooted (e.g. CleanSlate where tbalden isn't sure if it is still needed with his kernel and I believe he disables verity & verification just in case).
So my understanding is that on stock boot image disabling those will result in Rescue Party, on a Canary Magisk 23016 patched boot image it will not, and for some custom kernels (without being rooted) it may or may not depending on the kernel and whether the magiskboot binaries the kernel uses were updated to 23016.
That is, if I'm understanding you correctly.
Click to expand...
Click to collapse
For what it's worth, back awhile after I had been rooted with Magisk Canary 23015, I temporarily restored the stock unrooted boot.img and was able to boot fine after verity and verification had already been disabled. But possibly you're talking of a slightly different scenario.
roirraW edor ehT said:
For what it's worth, back awhile after I had been rooted with Magisk Canary 23015, I temporarily restored the stock unrooted boot.img and was able to boot fine after verity and verification had already been disabled. But possibly you're talking of a slightly different scenario.
Click to expand...
Click to collapse
Yeah, that makes sense because you only restored the stock boot image, but not the stock vbmeta so verity and verification remained disabled, allowing you to flash whatever you heart desires.
I'll test it right now. Stock P5, January update, Magisk patched boot image. Let's see what happens...
Reflashed vbmeta and disabled verity/verification. Boot image is patched. Result: Rescue Party.
Reflashed unpatched boot image. Result: Rescue Party
Reflashed vbmeta without options, reflashed patched boot image. Result: Successful boot.
Alright, I was thinking about not rooting at first but now I'm getting that itch. Welp.....time to try and root this joint
roirraW edor ehT said:
At this point, I'm reversing my own personal expression and still planning on disabling then when the late January update comes out side I use that custom kernel, at least until another guinea pig reports it's not necessary, or I have time to make sure I have everything backed up and try it myself.
Click to expand...
Click to collapse
I've been usng Dec build without veritfy/verification disabled (with Canary 23016 & Kiri 1.40) since mid December & have no issues to report. Guinea pig status: achieved?