[Recovery][UNOFFICIAL TWRP 3.5.2_9 for Samsung SM-T710] - Galaxy Tab S2 Android Development

PLEASE BEFORE YOU decide to try this recovery, you MUST read all of post 1 and 2 (about 3 minute read). If you think this is an unreasonable request, then stop reading now and find another recovery. Thank you.
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this software.
BACKUP YOUR DATA BEFORE trying this TWRP.
Source code
Kernel source
https://github.com/retiredtab/android_kernel_samsung_universal5433
Device tree
https://github.com/retiredtab/TWRP_gts28wifi/tree/main/gts28wifi
TWRP source code (built using minimal manifest TWRP 7.1)
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-7.1
Download TWRP from
https://sourceforge.net/projects/retiredtab/files/SM-T710/TWRP/
Installation Instructions
You MUST be running stock 7.0 to have the latest bootloader before flashing this TWRP.
Note I do NOT run Windows OS so there are no provided instructions on how to install TWRP using Windows. There's lots of tutorials and videos online on how to install TWRP via Windows. Do your own research. If this is unreasonable to you, don't use this TWRP. Questions regarding how to install TWRP using Windows/odin will go unanswered.
You need to boot the T710 into download mode. Power off. Press home button + power + volume down (farthest away from power button) at the same time. Let go when you see "Warning" text on the screen, then choose volume up to continue. Your screen should now show "Downloading... Do not turn off target"
Linux users can use heimdall to flash this recovery. For example,
Code:
heimdall flash --RECOVERY TWRP_3.5.2_9_SM-T710_20210719_Unofficial.img
After flashing the recovery image, you must boot into recovery immediately (using the hardware key combination) to run TWRP, otherwise the Samsung software will overwrite TWRP and you will have to start over again. I usually am already pressing the recovery hardware key combination while the recovery image is being flashed. The flash process will be very quick (a few seconds at most).
The recovery hardware key combination is home button + power + volume up (volume up is closest to the power button) all pressed at the same time.
Updates
Unless Android 12 or LineageOS 19.0 requires some mandatory changes to TWRP, this will be the only TWRP build I make for the forseeable future. There will be no planned updates to 3.5 unless there's a major bug or security vulnerability. The only time you need to boot into TWRP is to upgrade the custom rom.
I have been using this TWRP since Aug 19, 2021.
The "official" TWRP T710 ALL have broken MTP and adb in every version which is why I built my own despite reporting these problems to the maintainer.

Reserved.

Thank you so much for this! I teared my hair out for many, many hours thinking I had issues with drivers on my PC why adb or MTP never worked in every official TWRP release I've tried... I thought I'd give yours a try and voila! It works! Beautifully so.
Thank you, thank you, thank you!

Whenever i flash this specific build of TWRP my tab instantly bootloops.

cammykool said:
Whenever i flash this specific build of TWRP my tab instantly bootloops.
Click to expand...
Click to collapse
What bootloops? Is it TWRP that bootloops? Stock Samsung OS? LineageOS? How are you flashing it? Heimdall? Odin? Give more details.

retiredtab said:
What bootloops? Is it TWRP that bootloops? Stock Samsung OS? LineageOS? How are you flashing it? Heimdall? Odin? Give more details.
Click to expand...
Click to collapse
Sorry. Was a quick type. And I've done a bit more troubleshooting. The older builds with broken MTP seem to boot perfectly. But flashing the build outlined here seems to get the tablet stuck at the Tab S2 screen. The only place it can go is DL. system won't boot again unless I reflash a system image. The tablet was still on a build of 5.1.1 though and I know these modern recoveries probably don't expect that so i am letting it update the stock stuff now.

Yup that was it. Updated to 7.0 and the recovery flashed and ran perfectly! Thank you!

cammykool said:
Yup that was it. Updated to 7.0 and the recovery flashed and ran perfectly! Thank you!
Click to expand...
Click to collapse
Thanks for reporting back. I added this one line to the installation instructions in post #1.
"You MUST be running stock 7.0 to have the latest bootloader before flashing this TWRP."
PS. If you want to use my 18.1 T710 rom, it's over at
https://forum.xda-developers.com/t/...neageos-18-1-for-sm-t710-may-12-2022.4430339/

retiredtab said:
Thanks for reporting back. I added this one line to the installation instructions in post #1.
"You MUST be running stock 7.0 to have the latest bootloader before flashing this TWRP."
PS. If you want to use my 18.1 T710 rom, it's over at
https://forum.xda-developers.com/t/...neageos-18-1-for-sm-t710-may-12-2022.4430339/
Click to expand...
Click to collapse
Thank you! That was actually the plan! Running it now and posted in the other thread!

Thank you for nice work, I've installed it on my T715, it works very well, just now my device is recognized as T710 too. Could you please provide a build for T715? As the function of adb/mpt doesn't work on all of twrp for T715 too.

Was running LoS 16 and decided to update. Went to stock 7.0 then LoS 18.1 using this version of TWRP without any problems or the issues some other versions of TWRP have! Thanks

Related

[RECOVERY] [OFFICIAL] TWRP for Shield Portable

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
Direct device link
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
TWRP for Shield Portable, Tool/Utility for the Nvidia Shield
Contributors
Steel01
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Created 2016-06-01
Last Updated 2016-05-31
Well, I finally bit the bullet and took official maintainership of the Shield devices for TWRP. So, here's the pure upstream release. It's sideways due to lack of rotation support, but it should have every feature any other TWRP supported device does. The OP is a little different from other TWRP threads because I don't want to keep updating the changelog and version numbers, but those can be found on the twrp homepage linked there. Enjoy.
Steel01 said:
Well, I finally bit the bullet and took official maintainership of the Shield devices for TWRP. So, here's the pure upstream release. It's sideways due to lack of rotation support, but it should have every feature any other TWRP supported device does. The OP is a little different from other TWRP threads because I don't want to keep updating the changelog and version numbers, but those can be found on the twrp homepage linked there. Enjoy.
Click to expand...
Click to collapse
I'm pretty sure there's a sideways TWRP theme. I recall using it to get it to display properly on molly (Google's ADT-1 Developer Kit).
Have you tried setting the TWRP theme like this? :
Code:
TW_THEME := landscape_hdpi
r3pwn said:
I'm pretty sure there's a sideways TWRP theme. I recall using it to get it to display properly on molly (Google's ADT-1 Developer Kit).
Have you tried setting the TWRP theme like this? :
Code:
TW_THEME := landscape_hdpi
Click to expand...
Click to collapse
Yeah, the only thing that changes is the aspect ratio, not the orientation.
Thank you! Thank you!
Just updated to 110, and installed TWRP you posted. All went perfect.
Just FYI, sometimes when I flash a new TWRP recovery, it doesn't take the first time, so I just flash it a few times, then test to see if it took, if it didn't take, I flash a few times more until it finally flashes.
Is there a specific key combo you can use to go right into recovery? Right now, I boot into the bootloader by pressing and holding the back, home and nvidia buttons till it boots into the bootloader, then I select recovery to go into TWRP. Just wanted to know if there's was a key combo to go directly into recovery.
Thanks again for providing and posting the latest TWRP for the Portable!!
Hello, quick question. I have a previous version of TWRP installed and want to update to the new one.
Is it possible to apply the OTA to 110 with this TWRP or do I need the stock bootloader?
If I need the stock one, does anyone have a link to it? I didn't make a backup, unfortunately
No need to apply the ota, download the recovery image from Nvidia and fastboot flash blob, boot, and system. You'll lose any modifications to system (such as root) as expected, but that's easy enough to restore.
https://developer.nvidia.com/shield-open-source
But there's no real reason not to update twrp. The older multirom based version has screen rotation, but that's no big deal. And the newer updates have current selinux policies, so they'll be much less likely to cause issues with newer android versions (for those using CM13 and hopefully 14 sometime soon).
Steel01 said:
No need to apply the ota, download the recovery image from Nvidia and fastboot flash blob, boot, and system. You'll lose any modifications to system (such as root) as expected, but that's easy enough to restore.
https://developer.nvidia.com/shield-open-source
But there's no real reason not to update twrp. The older multirom based version has screen rotation, but that's no big deal. And the newer updates have current selinux policies, so they'll be much less likely to cause issues with newer android versions (for those using CM13 and hopefully 14 sometime soon).
Click to expand...
Click to collapse
Ah, I didn't know nvidia published those files like that. That's actually really great!
I'm all up to date now, including the latest TWRP
Hmm I tried TWRP 3.1 from the TWRP website and the touch interface doesn't work. Also, 3.0.2 seems to have problems mounting and wiping data?
Meh, okay. I saw a similar touch problem on a local twrp build. I've requested that the build be removed from the official site. I'll look into the problem when I have time.
Haven't had any trouble on 3.0.2 myself. Did you enable encryption or adopted storage in your ROM?
Great, thanks!
I didn't enable encryption, and it was the latest stock rom. I'm not really sure what happened. It just seemed to be having trouble mounting and wiping a few partitions on the stock system rom, so I flashed the 3.0.0.0 TWRP from the multirom. I seem to recall that having issues wiping too though. However, now that I've flashed LineageOS onto the system partition, I don't get any errors with 3.0.0.0 anymore. I haven't updated to 3.0.2.0 to see if the errors are gone in that build (nor do I want to wipe anything at this point).
As I wrote in the LineageOS thread, I had the same problem with touchscreen. I was hoping to solve the non working touchscreen problem during Aroma OpenGapps install.. is there any hope it gets solved? I think it would be very useful to be able to choose exactly what to install on the Shield, considering its little system partition.
Hmm, seems 3.1.0.0 and 3.1.1.0 don't work on the Shield Portable. After the first start no touch gesture is recognized. If you connect a USB mouse you can get past this...
But after a new start to the recovery everything you select results in "wipe factory settings" - which I assume you won't
PS: Landscape would be nice.
astuermer said:
Hmm, seems 3.1.0.0 and 3.1.1.0 don't work on the Shield Portable. After the first start no touch gesture is recognized. If you connect a USB mouse you can get past this...
But after a new start to the recovery everything you select results in "wipe factory settings" - which I assume you won't
PS: Landscape would be nice.
Click to expand...
Click to collapse
I too have this issue. Seems they messed up screen as portrait mode.
I see the problem with touch on the newer builds. Would have sworn I had at least one of those removed due to issue, but it apparently came back. Looking into updating all the internal files for 7.1. Working on testing and fixing that right now. The problem is that the touch screen userspace is trying to start before selinux is set to permissive by twrp. So, I have to make sure everything is labelled correctly and that's causing issues. If I'm lucky, I'll be uploading a test build later today. But as with all this type of work, I can't 100% guarantee anything.
astuermer said:
Landscape would be nice.
Click to expand...
Click to collapse
The rotation code no longer exists, it was deemed too slow and hacky. I have to set it up in portrait or not at all, unfortunately.
Edit:
So, not having much luck with making it play nice on default settings. Here's a build with selinux explicitly disabled and touch works as expected. As I have time, I will continue to work on this and get it upstreamed. For the moment, use this 3.1.1 build.
twrp-3.1.1-0-unofficial-roth.img
Finally got around to pushing updates to official twrp. So if you've had issues in the past, please try again. Should be easier to test and fix stuff now that I've got all that pushed.
Side Note: This is fully a 7.1.1 recovery and build. Blasted recovery from N works better than the roms themselves...
Some updates have been pushed for this. 3.2.1.0 has been release as of a few hours ago. If any issues are found, please report.
When trying to flash the 2018-02-11 LineageOS nightly with 3.2.1.0, I get the following error;
Code:
Updating partition details...
...done
Full SELinux support is present.
Installing zip file '/sdcard/lineage-13.0-20180211-nightly-roth-signed.zip'
Checking for digest file...
Skipping Digest check: no Digest file found
Verifying zip signature...
Zip signature verified successfully,
[B]This package is for device: roth; this device is .[/B]
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/lineage-13.0-20180211-nightly-roth-signed.zip'
Updating partition details...
...done
The flash does not proceed beyond this point - apparently can't identify the device type (see bolded text above). If I repeat the process using version 3.1.1-2 or version 3.0.2.0 it works fine, though.
Let me know if you'd like me to pull any logs etc

Help with Treble ROMs

I have the PRA-LX1 with already unlocked bootloader and got it rooted with TWRP + Magisk before the last OTA.
I'm not a beginner with rooting this phone but only got Problems with installing any Treble Rom (tried Lineage and Aosp) and every try ended with a bootloop I don't know what I'm doing wrong.
So please can anyone give me a step by step instruction?
Which Treble Rom is a good one and recommended for this phone?
Which TWRP do I need?
And how exactly do I flash them correctly? What do I wipe?
Sorry for this noob questions but I failed so many times with Treble and don't want to do the reinstall with erecovery for the 10000 time :crying:
Thanks
Try to install the stock recovery and ramdisk.
+1
I also have this problem. Wich TWRP works with treble roms? i tryed everything and everytime i get a boot loop.
Please help.
After I flashed a treble gsi, I need to flash stock recovery?
Atiqx said:
After I flashed a treble gsi, I need to flash stock recovery?
Click to expand...
Click to collapse
Yes. if u still get bootloop flash stock recovery and ramdisk first then flash gsi. make sure u factory reset on stock recovery after u flash gsi.
ppdr07 said:
Try to install the stock recovery and ramdisk.
Click to expand...
Click to collapse
ppdr07 said:
Yes. if u still get bootloop flash stock recovery and ramdisk first then flash gsi. make sure u factory reset on stock recovery after u flash gsi.
Click to expand...
Click to collapse
And which TWRP should I use for flashing?.. And how can I flash GSI with stock?
That makes no sense to me sorry
Flash via fsstboot. Stock recovery and ramdisk flash via fastboot. Im not using twrp so idk.
---------- Post added at 08:38 AM ---------- Previous post was at 08:37 AM ----------
U can see a tutorial at xda how to flash gsi without twrp. Google it.
ppdr07 said:
Flash via fsstboot. Stock recovery and ramdisk flash via fastboot. Im not using twrp so idk.
---------- Post added at 08:38 AM ---------- Previous post was at 08:37 AM ----------
U can see a tutorial at xda how to flash gsi without twrp. Google it.
Click to expand...
Click to collapse
I googled it, pretty much every source says that you require a custom recovery in order to flash a GSI or any custom ROM.
XDA XILFY said:
I googled it, pretty much every source says that you require a custom recovery in order to flash a GSI or any custom ROM.
Click to expand...
Click to collapse
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ u will find Flash GSI without TWRP
ppdr07 said:
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ u will find Flash GSI without TWRP
Click to expand...
Click to collapse
Oh, well that's pretty cool. Either way, I just tried flashing Official Resurrection Remix GSI with no luck. Stock recovery, attempted to flash through fastboot and it just gives me a bootloop, exactly like TWRP does. Followed the guide you linked to etc, just keeps rebooting.
XDA XILFY said:
Oh, well that's pretty cool. Either way, I just tried flashing Official Resurrection Remix GSI with no luck. Stock recovery, attempted to flash through fastboot and it just gives me a bootloop, exactly like TWRP does. Followed the guide you linked to etc, just keeps rebooting.
Click to expand...
Click to collapse
Go to openkirin.net/download download the rr beta 3
Atiqx said:
I have the PRA-LX1 with already unlocked bootloader and got it rooted with TWRP + Magisk before the last OTA.
I'm not a beginner with rooting this phone but only got Problems with installing any Treble Rom (tried Lineage and Aosp) and every try ended with a bootloop I don't know what I'm doing wrong.
So please can anyone give me a step by step instruction?
Which Treble Rom is a good one and recommended for this phone?
Which TWRP do I need?
And how exactly do I flash them correctly? What do I wipe?
Sorry for this noob questions but I failed so many times with Treble and don't want to do the reinstall with erecovery for the 10000 time :crying:
Thanks
Click to expand...
Click to collapse
Well, I finally got it all working.
You know the risks, don't blame me if something goes wrong, I did these exact steps to manage to root my phone without breaking it. C432, Dual SIM and PRA-LX1.
Have everything stock before following this short guide: Firmware, all stock recovery etc.
Installing the ROM and GApps
First, download necessary GSI files.
(Personally I got Official Oreo Resurrection Remix, here).
(Although you could find yourself using virtually any other GSI, I like the look and feel of RR, though I'll be changing my boot animation with root). Many people would probably recommend you to use something like an AOSP, or LOS which I was also considering on installing. They may also come bundled with GApps, which would negate the later need for installation or download of separate GApps.
This may include GAPPS but you should understand this from the GSI page, so for example on RR I had to download both the latest base ROM .img and the micro GApps.
So to do this I had to use the right architecture (For the P8 Lite 2017, this is ARMx64, do your good research, since my problem was getting this wrong with my PRA-LX1 (Mine was A-ONLY), this stands for the base ROM and GApps.
After this I actually didn't use TWRP as user @ppdr07 advised. I followed the guide he linked us to and did as so, without following the -u command, since it wasn't working for me (didn't affect anything, try it, if it doesn't work, just take that bit out).
The ROM ended up installing and posting through, everything set up perfectly.
After this I was like "Huh, so what now? How am I to flash GApps on this without TWRP?". I went for it and booted into fastboot where I flashed Askuccio's TWRP for hi6250 devices. At this point I worried that the ROM wouldn't post again - though it did, so from there I enabled dev options and switched on advanced power options just for ease of usage. From there I rebooted straight to recovery which posted fine, too.
At this point, you need to flash the GApps. Go for the one that the original GSI page recommends. Flash it to the System Image partition. Don't wipe anything. At this point I recommend that if you realise that you forgot to transfer any files to the SD card, you should do it from the system. It works better compared to the MTP on TWRP. Either way, that should work properly. Now, reboot the system, and it should work perfectly.
Enjoy, it took me months to get to this point lol
Rooting Your New ROM With Magisk
(Before installing this consider the other root options. I believe there's SuperSU and another possibly that I'm less aware of. Either way, in my opinion Magisk comes with the most benefits so I'll be helping you out with that).
After this I ended up flashing Magisk in order to use Snapchat and other apps similar to it. Firstly you'll want to set up Google stuff which has been newly added to the system, and then you'll want to go to chrome and download the Magisk Manager .apk from here. The main and most reliable place to get it is from the creator's project page found here, all main links stand out in the middle fairly well.
(Remember to enable downloading of unknown apps for Chrome in it's app settings, otherwise it won't download or install.)
If it still doesn't work at this point, I ended up holding down on the Magisk Manager link and pressing Download Link (or something to that effect). From this point just install it as you would any other out-of-store app.
Now, you'll need to download these two files from the Magisk page onto your computer: Stable Installer and Uninstaller. Next, while booted into Android, copy them over to either Internal or External storage and when it's done, reboot into TWRP again, either by advanced power menu or using the button commands for recovery. Personally, I think I need the power options with this phone.
In TWRP, simply go to Install, navigate to /externalsd/***[WHEREVER YOU PLACED YOUR MAGISK FILES]***, then install the Magisk installer .zip. If unchanged, the filename should be something like "Magisk-v17.1.zip". Install it, then give rebooting a go. Hopefully it'll post, if not, go back into TWRP and run the Uninstaller .zip, it's saved me a bunch of times.
Unblocking Apps That Say Something Like "Your Phone is Rooted or Modified, no access blah blah blah..."
(Snapchat is the example used here. It won't work upon login if you don't follow this step. Some apps don't work with this alone however, though somebody may have produced a separate guide or easily installable Magisk module with a solution for it. One that won't be fixed singularly with Magisk Hide is Google Pay).
After posting, if you need to unblock Snapchat or something, go to Magisk Manager (which should now be more green), open the top left context menu, tap on Magisk Hide, and search "snap" until you see the Snapchat logo pop up, then select it, then back out with the back button. It should stay selected in Magisk, and the app should now be usable and shouldn't give you any annoying errors, if not give it a reboot and see if it's solved.
Good luck!

[Guide] [SM-T350] Root and Update Galaxy Tab A 8.0 to ANDROID PIE

I am not responsible for bricked devices, or any other hardware malfunctions that come as a result of flashing anything. Please do some research if you have any concerns about features included in this ROM before flashing it
Hey everyone,
I am writing this guide because I spend all day trying to figure out how to upgrade my grandma's tablet from android 7 TouchWiz to android 9 pie. I did not create any of the files that I am about to link just putting all the info in one place because I feel it's needed.
Before starting my grandam's tablet was running android 7.0 TouchWiz. So if you are in the same situation do the following.
Download the following
Odin3-v3-10-7
SM-T350 Marshmallow Firmware (check second post for faster mirror)
TWRP-3.2.1
PIE ROM of Choice
Open Gapps (Remember Platform: ARM | Android Version : 9.0| Variants: Your Choice)
Root (Optional): Magisk
Instructions
1. Put your tablet in download mode by turning it off then pressing and hold [Power] [Vol-Down] & [Home] at the same time till a cyan warning screen appear.
2. Press Volume Up to Continue.
3. Connect the Tablet to the computer via USB stick
4. Extract the Odin and Marshmallow Firmware zip files and place it on the desktop
5. Run Odin and make sure you can see your device
6. Click on [AP] button and find the marshmallow firmware. Let Odin verify the file (take a second) then click start to begin the flashing process
7. After flashing the firmware the tablet will reboot and just wait for the welcome screen.
8. In the welcome screen skip everything till you get to the home screen then turn the tablet off and put it back into download mode (see step 1)
9. Now your tablet should still be connected to the computer and Odin should still be open.
10. In Odin go to the second tab (OPTIONS) and uncheck Auto Reboot (VERY IMPORTANT)
11. Now click on the [AP] button and find the TWRP zip file then click start to flash it
12. After the flashing process has been successful press and hold [Power] [Vol-Down] & [Home] to reboot. AS SOON AS THE SCREEN GOES BLACK LET GO OFF THE BUTTONS AND PRESS AND HOLD [POWER] [VOL-UP] and [ HOME] AT THE SAME TIME.
13. If you did it right you should be in TWRP. If not you have to repeat step 11 and 12
14. Make a NANBACKUP in TWRP and copy it to your computer
15. After that copy the PIE ROM and GAPP of your choice. (MAGISK IF YOU WANT ROOT) to the internal memory card or sd card whichever you have. I don't have an SD card so I copied it to the internal memory
16. In TWRP Wipe the System, Cache, Data and ART/Dalvik cache. (Recommended)
17. Flash the ROM, GAPPS
18. Flash the root solution of your choice (optional).
19. Reboot your device.
Thanks to @lividhen99 for the post that I got all this info
Thanks to everyone who creates and ported recoveries and ROM to this device. My grandma appreciated it ( we both hate TouchWiz)
PS. I will eventually come back and make a mirror of the marshmallow firmware file because it is so long and slow. If anyone wants to beat me to it please do
https://drive.google.com/open?id=1WyafpwMlGbBmocWhwhHxcrtgS0mFpoes
Heres a google drive mirror.
Is there a 64 bit version of Android Pie for the SM-T350? After following these instructions I couldn't install the 64 bit version of GApps, said it was not compatible. Is that a holdover from the Marshmallow firmware? The SM-T350 supposedly has an ARM 64bit processor so you'd think it could take the 64 bit GApps install but after these updates it shows that it'e the 32 bit version of Pie. I know I'm kind of rambling here but I guess you can follow what I'm trying to do. Thanks!
is this compatible with the sm-p355?
Is it necessary to do this from Marshmallow 6? Will this procedure work for Nougat 7.1.1?
Wimmer4Archery said:
Is it necessary to do this from Marshmallow 6? Will this procedure work for Nougat 7.1.1?
Click to expand...
Click to collapse
It should technically work, but if you get a black screen, downgrade to marshmallow and try again. Not all devices need to be downgraded, and nobody knows why
Great, thanks for the info! This sounds like a, great summer project while we are all locked in quarantine.
2 different PIE roms, when I follow the path to add an account (google) the screen goes black with small top bar icons and does not allow the process to continue (setup). which specific ROMS have worked>
ygthb said:
2 different PIE roms, when I follow the path to add an account (google) the screen goes black with small top bar icons and does not allow the process to continue (setup). which specific ROMS have worked>
Click to expand...
Click to collapse
Same issue. Hopefully someone has an answer
sunnyd71 said:
Same issue. Hopefully someone has an answer
Click to expand...
Click to collapse
Could you and ygthb send me the links for the rom's forums? in fact, you might want to ask the question on the rom's respective forum.
lividhen99 said:
Could you and ygthb send me the links for the rom's forums?
Click to expand...
Click to collapse
if ur talking about a tab a then youre in it already
elliwigy said:
if ur talking about a tab a then youre in it already
Click to expand...
Click to collapse
This is a thread on how to install roms on this device, it provides no roms besides the marshmallow one to fix the black screen issue.
Trying to get this to work, everything is fine until I try to load the new ROM and GAps, it's giving me error 7, specifically this:
- Confirming target device...
mount: Failed to mount /dev/block/by-name/vendor at /vendor: No such
file or directory
ui_print(): Failed to parse the argument(s)
Updater process ended with ERROR: 7
browenb said:
Trying to get this to work, everything is fine until I try to load the new ROM and GAps, it's giving me error 7, specifically this:
- Confirming target device...
mount: Failed to mount /dev/block/by-name/vendor at /vendor: No such
file or directory
ui_print(): Failed to parse the argument(s)
Updater process ended with ERROR: 7
Click to expand...
Click to collapse
What partitions did you wipe?
I might be a little late posting here but I am currently trying this with the SM-T350 that came with 7.1.1 and for some reason when I load the Marshmallow firmware to my tablet it never actually boots, it gets as far as flashing the Samsung logo on a black background then says Touchwiz.exe has encountered an error. Am I doing something wrong? I am following the instructions word for word as far as I can tell.
The marshmallow firmware never has to boot. If you want it to boot, factory reset (wipe data and dalvik cache). But you wipe system data and cache anyway when you install a rom.
lividhen99 said:
The marshmallow firmware never has to boot. If you want it to boot, factory reset (wipe data and dalvik cache). But you wipe system data and cache anyway when you install a rom.
Click to expand...
Click to collapse
Basically I just want to use TWRP to flash Magisk and use it to spoof for Pokemon Go. I did it previously on a Galaxy S5 but I never had a problem booting into the OS and just turning the phone off when I wanted to boot into recovery mode (TWRP) so I don't really know what I am doing but I am assuming I need it to boot normally for magisk to root the device. Unfortantely when I try to flash TWRP with the 7.1.1 firmware that comes stock on the device recovery just boots to a black screen so searching around has led me to the conclusion I need to downgrade to Marshmallow then try flashing TWRP but I never expected it to not boot normally xD Sorry this is a bit outside of my technical knowledge to say the least.
---------- Post added at 01:05 AM ---------- Previous post was at 12:50 AM ----------
I believe I understand what I need to do now. I managed to load into TWRP so at that point I can just flash any rom and use magisk to root. Any particular one you might suggest? Thanks for all the help by the way!
Gemininja said:
Basically I just want to use TWRP to flash Magisk and use it to spoof for Pokemon Go. I did it previously on a Galaxy S5 but I never had a problem booting into the OS and just turning the phone off when I wanted to boot into recovery mode (TWRP) so I don't really know what I am doing but I am assuming I need it to boot normally for magisk to root the device. Unfortantely when I try to flash TWRP with the 7.1.1 firmware that comes stock on the device recovery just boots to a black screen so searching around has led me to the conclusion I need to downgrade to Marshmallow then try flashing TWRP but I never expected it to not boot normally xD Sorry this is a bit outside of my technical knowledge to say the least.
---------- Post added at 01:05 AM ---------- Previous post was at 12:50 AM ----------
I believe I understand what I need to do now. I managed to load into TWRP so at that point I can just flash any rom and use magisk to root. Any particular one you might suggest? Thanks for all the help by the way!
Click to expand...
Click to collapse
OH! Well, now that you have that specific version of twrp booted, I would recomend either lineage os or crdroid for the SM-T350. If you just want stock Samsung, you can reflash the stock 7.1.1 firmware and grab the Nougat twrp for the sm-T355 from ashyx's galaxy tab a twrp page here: https://forum.xda-developers.com/galaxy-tab-a/development/recovery-t3426560 . It will boot on Nougat (7.1.1) but it cannot flash android pie (9.0) or Q (10.0) roms. It can still flash magisk though.
Crdroid (I released a newer build on the second to last page ?): https://forum.xda-developers.com/galaxy-tab-a/development/rom-galaxy-tab-8-0-t3912517/page32
Lineage: https://forum.xda-developers.com/galaxy-tab-a/development/rom-t3903258/page31
If you do end up flashing a custom rom, just wipe system, data, cache, and dalvik cache. Then flash the ROM zip, the gapps zip, and the magisk tnstaller zip. Just remember to enable magisk hide to pass safetynet whether you go custom rom, or not.
If you want the marshmallow firmware to boot, I think just wipe cache and dalvik cache. If that doesn't work, wipe data.
Wiping data will delete all your apps and settings and passwords, etc. It is essentially a factoy reset.
64 bit
Bookworm214 said:
Is there a 64 bit version of Android Pie for the SM-T350? After following these instructions I couldn't install the 64 bit version of GApps, said it was not compatible. Is that a holdover from the Marshmallow firmware? The SM-T350 supposedly has an ARM 64bit processor so you'd think it could take the 64 bit GApps install but after these updates it shows that it'e the 32 bit version of Pie. I know I'm kind of rambling here but I guess you can follow what I'm trying to do. Thanks!
Click to expand...
Click to collapse
the device isnt capable of running ARM64 however you can find regular ARM variants of lineageOS (what i used instead of flashing the stock firmware) and of gapps. my galaxy tab a (sm-t350) now runs android 10 and gapps 10.0 full, through this guide. just ignore the first software package and continue with the guide.
help! flashed from stock firmware (i don't remember version)...after a lot of time, is in the wizard section with a lot of error (unfortunately the process xxx has stopped), and the tablet reboot...what should i do?

can't flash TWRP 3.3.1 - 3.0.2 works just fine

I'm having difficulty getting TWRP 3.3 working on my z3c. I'm not new to the process, and have done it a few times on a few phones. Right now my z3c has TWRP 3.0.2-1-z3c. I'm wanting to try the new Android 10 ROM that came out, but it requires TWRP 3.3 to work. So I got the TWRP provided in the thread. I'm flashing from Linux, so I did run
Code:
./fastboot flash recovery twrp 3.3.1-1-A10.0-z3c.img
When I reboot and hold the power down button it skips over TWRP and just boots the ROM I have installed.
Okay, so I downgrade to TWRP 3.0.2-1 and reboot...hold volume down...TWRP boots just fine.
Flash TWRP 3.3 again....no joy. It just boots straight to ROM.
RNZL3R said:
I'm having difficulty getting TWRP 3.3 working on my z3c. I'm not new to the process, and have done it a few times on a few phones. Right now my z3c has TWRP 3.0.2-1-z3c. I'm wanting to try the new Android 10 ROM that came out, but it requires TWRP 3.3 to work. So I got the TWRP provided in the thread. I'm flashing from Linux, so I did run
Code:
./fastboot flash recovery twrp 3.3.1-1-A10.0-z3c.img
When I reboot and hold the power down button it skips over TWRP and just boots the ROM I have installed.
Okay, so I downgrade to TWRP 3.0.2-1 and reboot...hold volume down...TWRP boots just fine.
Flash TWRP 3.3 again....no joy. It just boots straight to ROM.
Click to expand...
Click to collapse
Same. Couldnt find a proper answer to this. Still have trouble with this? I'm on CR6.1, that's android 8.1 and I'd like to try later versions (lineage os or maybe CR7.0)
liberteus said:
Same. Couldnt find a proper answer to this. Still have trouble with this? I'm on CR6.1, that's android 8.1 and I'd like to try later versions (lineage os or maybe CR7.0)
Click to expand...
Click to collapse
Screwed badly with the systems to the point where I softbricked the phone, and had to revert to stock. Will try going straight to 3.3.1 instead now.
Edit: I used adb to go to fastboot (adb reboot bootloader), from there I tried all the different twrp images I have, including latest Android 10 one using the fastboot boot image.img (replace image by name of image, I name them A8, A9, A10 to match android version).
All of them booted, which means I can flash them without issues. I don't know which version I want to install though for now, and I don't want to be stuck again on a version that I won't be able to upgrade later on... so will probably go straight to A10 and Lineage 17 even if it's quite buggy.
liberteus said:
Same. Couldnt find a proper answer to this. Still have trouble with this? I'm on CR6.1, that's android 8.1 and I'd like to try later versions (lineage os or maybe CR7.0)
Click to expand...
Click to collapse
did you found a solution? i have the same issue...

I need help with root motoG6 Android 9.0 (ali)

I saw old guide but guy who made this can't help me because he not have this phone I need to find dm-verify disabler and other files to root my motoG6 but what to do if i get into a bootloop?
Will I be able to install android via Smart Assistant after doing the wipe? (if I broke something)
Someone know how can I make copy for my apps and data? I have mutch modded apk.
i know what adb is for but i don't know kommend anyone can help with root?
XWacoX said:
I saw old guide but guy who made this can't help me because he not have this phone I need to find dm-verify disabler and other files to root my motoG6 but what to do if i get into a bootloop?
Will I be able to install android via Smart Assistant after doing the wipe? (if I broke something)
Someone know how can I make copy for my apps and data? I have mutch modded apk.
i know what adb is for but i don't know kommend anyone can help with root?
Click to expand...
Click to collapse
I used:
https://forum.xda-developers.com/t/guide-root-moto-g6-ali-twrp-root-and-magisk-installation-guide.3816569/page-41.
It worked out well. As long as you have TWRP, you should be able to recover from bootloops.
HDXKohl said:
I used:
https://forum.xda-developers.com/t/guide-root-moto-g6-ali-twrp-root-and-magisk-installation-guide.3816569/page-41.
It worked out well. As long as you have TWRP, you should be able to recover from bootloops.
Click to expand...
Click to collapse
page not found ( (sorry is my second acc I can't log in to my main acc)
RogalDDL said:
page not found ( (sorry is my second acc I can't log in to my main acc)
Click to expand...
Click to collapse
Try this:
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide.
Update March 23, 2019: I'd like to apologize to everyone. It looks like I am not going to be able to actively keep this thread updated like I used to. I have had too much going on at home an work and it doesn't look like it's going to settle...
forum.xda-developers.com
Also, I do not think you need the boot images. Check the comments for pie, since the guide was written for oreo.
I also used this for the dm-verity zip:
[GUIDE] A faster and updated guide to root, magisk and return to stock
#Prerequisites: Stock Rom: https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/ TWRP: https://dl.twrp.me/ali/twrp-3.3.0-0-ali.img Dejello TWRP: https://drive.google.com/open?id=1QWYIcti-wJPPMAc8Ol5pnoO3b8CqtKFn (Unofficial) //Only for...
forum.xda-developers.com
HDXKohl said:
Try this:
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide.
Update March 23, 2019: I'd like to apologize to everyone. It looks like I am not going to be able to actively keep this thread updated like I used to. I have had too much going on at home an work and it doesn't look like it's going to settle...
forum.xda-developers.com
Also, I do not think you need the boot images. Check the comments for pie, since the guide was written for oreo.
I also used this for the dm-verity zip:
[GUIDE] A faster and updated guide to root, magisk and return to stock
#Prerequisites: Stock Rom: https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/ TWRP: https://dl.twrp.me/ali/twrp-3.3.0-0-ali.img Dejello TWRP: https://drive.google.com/open?id=1QWYIcti-wJPPMAc8Ol5pnoO3b8CqtKFn (Unofficial) //Only for...
forum.xda-developers.com
Click to expand...
Click to collapse
ok I will try tomorrow.
HDXKohl said:
Try this:
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide.
Update March 23, 2019: I'd like to apologize to everyone. It looks like I am not going to be able to actively keep this thread updated like I used to. I have had too much going on at home an work and it doesn't look like it's going to settle...
forum.xda-developers.com
Also, I do not think you need the boot images. Check the comments for pie, since the guide was written for oreo.
I also used this for the dm-verity zip:
[GUIDE] A faster and updated guide to root, magisk and return to stock
#Prerequisites: Stock Rom: https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/ TWRP: https://dl.twrp.me/ali/twrp-3.3.0-0-ali.img Dejello TWRP: https://drive.google.com/open?id=1QWYIcti-wJPPMAc8Ol5pnoO3b8CqtKFn (Unofficial) //Only for...
forum.xda-developers.com
Click to expand...
Click to collapse
there is problem I downloaded twrp-3.5.2_9-0-ali.img but it stuck at twrp logo it only responds to vol + power but after that it starts to turn on the system. I using Windows 8.1 v. 6.3.9600. So why it not working???
When I turn on rebbot recovery I got stock recovery not twrp.
HDXKohl said:
Try this:
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide.
Update March 23, 2019: I'd like to apologize to everyone. It looks like I am not going to be able to actively keep this thread updated like I used to. I have had too much going on at home an work and it doesn't look like it's going to settle...
forum.xda-developers.com
Also, I do not think you need the boot images. Check the comments for pie, since the guide was written for oreo.
I also used this for the dm-verity zip:
[GUIDE] A faster and updated guide to root, magisk and return to stock
#Prerequisites: Stock Rom: https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/ TWRP: https://dl.twrp.me/ali/twrp-3.3.0-0-ali.img Dejello TWRP: https://drive.google.com/open?id=1QWYIcti-wJPPMAc8Ol5pnoO3b8CqtKFn (Unofficial) //Only for...
forum.xda-developers.com
Click to expand...
Click to collapse
hey dude next problem after install magisk I CAN'T BOOT INTO SYSTEM
RogalDDL said:
there is problem I downloaded twrp-3.5.2_9-0-ali.img but it stuck at twrp logo it only responds to vol + power but after that it starts to turn on the system. I using Windows 8.1 v. 6.3.9600. So why it not working???
When I turn on rebbot recovery I got stock recovery not twrp.
Click to expand...
Click to collapse
Which img did you use? I used:
[TWRP][UNOFFICIAL] TWRP 64 bit for ALI
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
Here's a newer one:
[TWRP][UNOFFICIAL] TWRP [64 Bit][3.7.0]
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
I have not used it before. I am by no means a pro at this, so maybe try looking around.
RogalDDL said:
hey dude next problem after install magisk I CAN'T BOOT INTO SYSTEM
Click to expand...
Click to collapse
How did you install? A lot of older guides say to flash magisk, but I did it through the apk, as that's what magisk recommends.
Also did you get recovery to work. From my experience, it's generally not good to proceed without recovery, as it is harder to recover from boot loops and other issues.
HDXKohl said:
How did you install? A lot of older guides say to flash magisk, but I did it through the apk, as that's what magisk recommends.
Also did you get recovery to work. From my experience, it's generally not good to proceed without recovery, as it is harder to recover from boot loops and other issues.
Click to expand...
Click to collapse
I had a copy of the system previously made, but after rebooting into the system it only turned on twrp, I had to upload the firmware again via smart assistant. First I did a wipe, then I installed no verify and magisk but later it did not boot system but it returned to twrp. I searched 1000 pages for .img to moto g6 android 9.0 Is it possible to downgrade to android 8.0 without root? I have no idea how to root on this anymore. my model is XT1925-5.

Categories

Resources