Related
Hey all
I am considering purchasing RCA Pro 10 tablet that runs Android 4.4. From the research I did on XDA for it I was able to find that it can be rooted using Kingo. But I couldn't find any mention of a custom recovery that can support it. As you know we need the custom recovery to flash ROMs and such. Anyone know of any custom recovery that will work with this tablet?
Thanks
it hasent been rooted yet the 4.4 one which is the one walmart had on black friday is differen t some how then the orginal the connectors are in different places and the modle number is different kingo does not work
I rooted mine but it was a jumbled mess of a process. First install SuperSU, then install and run iroot, afyer that using pdanet drivers plug it into your computer and use kango, open SuperSu and update your binary, finally use a root browser and remove the app iroot installed. Iroot installs the su binary but doesnt set anything up properly, kango will set everything up but cant install the files needed for some reason so you have to use them together. Its messy but it works.
I got 2of the new of the rca pro 10 edition with the 1.5 GHz quad core m/n rct6203w46 the easyist way to root it is plug it in your PC let it download the drivers download pdanet on your PC see if there's more drivers 4 it download Kingo root set tab to USB debuging open kingo root plug in tab to USB kingo root will find it click root it will go through a few steps it will ask if u have a special kernal choose other opt it will restart tab few times and it will say its rooted and install super su if not click root again then it should be rooted restart tab after it says rooted keep attached to PC it will say root status yes then should be 2 options remove root and root again hope this helps you guys who bought the new one on black Friday big plus it never deleted Aney apps app data pics music ect and you don't need SD chip for it ... as far as a custom kernal / recovery i have no idea sorry regarden that
I have my Pro10 RCT6203W46 rooted and have TWRP installed as custom recovery. Here is a link to another thread that may help: http://forum.xda-developers.com/showpost.php?p=57437408&postcount=113
Droidify said:
I have my Pro10 RCT6203W46 rooted and have TWRP installed as custom recovery. Here is a link to another thread that may help: http://forum.xda-developers.com/showpost.php?p=57437408&postcount=113
Click to expand...
Click to collapse
Cab you elaborate on how you got TWRP installed? I have it rooted via Kingo Root!
Thanks
Sargeue said:
Cab you elaborate on how you got TWRP installed? I have it rooted via Kingo Root!
Thanks
Click to expand...
Click to collapse
Sargeue,
Using the link I supplied, I downloaded (using my PC) the TWRP image from the last link PaTF provided. I copied the TWRP image over to my tablet. Then using the link mexicandroid provided to the Rashr flash tool on Google Play, I installed it and followed the instructions in the app to flash the TWRP image to my tablet and voila!, I had a custom recovery.
I can also verify everything works in TWRP, such as backup and restore, wipe menu, etc. No custom ROMS available that I know of, so did not try to flash any ROM.
Of note: If you allow an update to the RCA firmware, you will need to re-flash TWRP as the firmware update overwrites the custom recovery.
Hope this helps.
Droidify said:
Sargeue,
Using the link I supplied, I downloaded (using my PC) the TWRP image from the last link PaTF provided. I copied the TWRP image over to my tablet. Then using the link mexicandroid provided to the Rashr flash tool on Google Play, I installed it and followed the instructions in the app to flash the TWRP image to my tablet and voila!, I had a custom recovery.
I can also verify everything works in TWRP, such as backup and restore, wipe menu, etc. No custom ROMS available that I know of, so did not try to flash any ROM.
Of note: If you allow an update to the RCA firmware, you will need to re-flash TWRP as the firmware update overwrites the custom recovery.
Hope this helps.
Click to expand...
Click to collapse
Great, will try it out. Really don't need custom rom, just like having nandroid backup. Thanks for you help!
Perfect! Worked great, easiest recovery I installed to this date. Thanks for your help again Droidify.
Thanks to the thread maker. I knew a lot with this thread.
Thanks
Thanks to Patf for posting the files, Sargeue for asking Droidify to elaborate, and Droidify for elaborating I was able to do this with no problem. This wasn't my first time rooting, and I've flashed a cfw that already had a custom recovery on it which rooted a device( don't know if thats particularly considered rooting), but I think this was the first time I flashed a custom recovery. The TWRP recovery boots just fine how it should and everything works if the instructions are followed. Thanks a bunch guys. I had already got an update prior to this and I am not sure nor do I remember what it exactly was. Its the only update I've got since I had the tablet. I still attempted this, so it was risky, but never the less everything went fine.
Hi all! I somehow soft bricked my RCA tab after updating to an OTA. Anyone have a nandroid backup of the stock ROM? Thanks!
Same problem here. OTA update screwed it up looking for help.
RCA RCT6203W46 1.9.50 firmware upgrade failures
Below is the method I found to resolve the issue I had with the most recent firmware upgrade failing. Use at your own risk.
How to resolve RCA RCT6203W46 1.9.50 firmware upgrade failures (this should also unbrick your device provided you can access stock recovery):
1. Place these 1.3.51 and 1.9.50 update zip files on your external sdcard. If you can only boot into recovery, you will need to eject the sdcard and use an alternative method to transfer these files from your PC to the sdcard and then place the card back into your tablet.
2. Boot into stock recovery. You can do this from a powered off state by simultaneously depressing the power and volume buttons until the white RCA boot screen appears. Once this screen appears, release the power button but REMAIN DEPRESSING THE VOLUME BUTTON until you are in recovery.
3. Select: Wipe cache partition. (use the volume button to move selection up or down, press the power button to make selection)
*Factory reset wipes cache too in step 4, but I am cautious.
4. Select: Wipe data/factory reset. Warning: you will lose any app you had installed.
5. Select: apply update from sdcard. Select the 1.3.51 zip file. Allow it to complete.
6. Select: apply update from sdcard. Select the 1.9.50 zip file. Allow it to complete.
7. Select: reboot system now.
8. Enjoy your upgraded RCA RCT6203W46 once again!
Probable causes for issue:
Rooted system (forgot to unroot prior to upgrade)
Removed or froze any stock app (including Vudu, Walmart, etc)
Modified a system file (build.prop, etc)
Bad luck
installation aborted...
Hello! I just did this guide but it didn't work. I always get Installation Aborted with Step 5 and Step 6 both of them are Aborted. I followed carefully your guide but still no good for my tab. I uploaded the two installation aborted message from android recovery. The first photo is when i update the firmware 1.3.51.zip and the second photo is installation aborted too when i update the firmware to 1.9.50.zip... Please see those photos if you can see what it made to abort the installation process. I hope you can help Droidify. And also, when i rooted my tab pro 10, i only remove the Vudu app and another app that was included but not the Walmart app...
Did not work for me...
Droidify said:
Below is the method I found to resolve the issue I had with the most recent firmware upgrade failing. Use at your own risk.
How to resolve RCA RCT6203W46 1.9.50 firmware upgrade failures (this should also unbrick your device provided you can access stock recovery):
1. Place these 1.3.51 and 1.9.50 update zip files on your external sdcard. If you can only boot into recovery, you will need to eject the sdcard and use an alternative method to transfer these files from your PC to the sdcard and then place the card back into your tablet.
2. Boot into stock recovery. You can do this from a powered off state by simultaneously depressing the power and volume buttons until the white RCA boot screen appears. Once this screen appears, release the power button but REMAIN DEPRESSING THE VOLUME BUTTON until you are in recovery.
3. Select: Wipe cache partition. (use the volume button to move selection up or down, press the power button to make selection)
*Factory reset wipes cache too in step 4, but I am cautious.
4. Select: Wipe data/factory reset. Warning: you will lose any app you had installed.
5. Select: apply update from sdcard. Select the 1.3.51 zip file. Allow it to complete.
6. Select: apply update from sdcard. Select the 1.9.50 zip file. Allow it to complete.
7. Select: reboot system now.
8. Enjoy your upgraded RCA RCT6203W46 once again!
Probable causes for issue:
Rooted system (forgot to unroot prior to upgrade)
Removed or froze any stock app (including Vudu, Walmart, etc)
Modified a system file (build.prop, etc)
Bad luck
Click to expand...
Click to collapse
First of all Thank You for trying to help, you are doing more that Walmart & RCA combined.
I followed your instructions and this process did not work for me. I have attached pictures of my screen after using both zip files...
Also I only rooted the tablet using Kingo I didn't remove any system apps
I think a key difference in my case is that I had TWRP installed and was able to boot into the system and unroot, install stock recovery, and then perform this procedure. Seems like you guys never had TWRP installed as recovery. I have a couple other tricks I am working on, but be patient as I vet them and see if something might work. Sorry this didn't work for you guys!
Any updates on this?
Droidify said:
I think a key difference in my case is that I had TWRP installed and was able to boot into the system and unroot, install stock recovery, and then perform this procedure. Seems like you guys never had TWRP installed as recovery. I have a couple other tricks I am working on, but be patient as I vet them and see if something might work. Sorry this didn't work for you guys!
Click to expand...
Click to collapse
No didn't use TWRP.
My tab is only 20 days old & still under warranty so I'm just going to send it back to RCA.
Was hoping to fix it myself so I wouldn't have to wait 4-6 weeks.
PHug said:
No didn't use TWRP.
My tab is only 20 days old & still under warranty so I'm just going to send it back to RCA.
Was hoping to fix it myself so I wouldn't have to wait 4-6 weeks.
Click to expand...
Click to collapse
Unfortunately, I'm boned as far as returning it goes because rooting voids your warranty.
PHug said:
No didn't use TWRP.
My tab is only 20 days old & still under warranty so I'm just going to send it back to RCA.
Was hoping to fix it myself so I wouldn't have to wait 4-6 weeks.
Click to expand...
Click to collapse
Well then there is no sense for me to keep trying to resolve this considering I have no way to test fixes, especially if what I posted resolved my particular case. I did send someone a test to try and if that is successful I will share, but outside of that I tried guys.
I guess the lesson learned here is that we all have to remember to unroot and not delete the apps that came with the device, only freeze them using Titanium or similar and unfreeze them before updating.
I think I finally bricked my device. I'm guilty. Just want to keep track of everything I did and share how it's bricked.
1. Everything starts because the 4g LTE stopped working. The device starts to give me "Invalid SIM" message no matter how I try. Same message with either T-mobile sim card or the stock AT&T sim card. At this time, the device is on TWRP 2.8.1.0 with Thor Gapps Rom ( 13.3.2.4 ).
2. Thinking it might be a ROM issue, I restored 13.3.2.3.2. Same error message: Invalid SIM.
3. Thinking to restore everything stock before returning it to amazon, I flash stock recovery.img to overwrite TWRP and restored 13.3.2.6 backed-up with safestrap. System starts up but has some issue: it always goes back to selecting language page.
4. Flashed update-kindle-13.4.5.2_user_452004120-twrp.zip to stock slot with safestrap in hope of fixing everything. Now system stalls at the white "Kindle fire" screen.
I know that zip is for twrp, but I thought twrp can take backup made with safestrap, why not the other way around?! Well, I'm unlucky this time. One shall never touch stock slot with safestrap. I think I should have used the official update-kindle-13.4.5.2_user_452004220.bin and update through Device-update menu. Oh well.
Any way I can still play with this device before it set off for amazon?
In
shadowcliffs said:
I think I finally bricked my device. I'm guilty. Just want to keep track of everything I did and share how it's bricked.
1. Everything starts because the 4g LTE stopped working. The device starts to give me "Invalid SIM" message no matter how I try. Same message with either T-mobile sim card or the stock AT&T sim card. At this time, the device is on TWRP 2.8.1.0 with Thor Gapps Rom ( 13.3.2.4 ).
2. Thinking it might be a ROM issue, I restored 13.3.2.3.2. Same error message: Invalid SIM.
3. Thinking to restore everything stock before returning it to amazon, I flash stock recovery.img to overwrite TWRP and restored 13.3.2.6 backed-up with safestrap. System starts up but has some issue: it always goes back to selecting language page.
4. Flashed update-kindle-13.4.5.2_user_452004120-twrp.zip to stock slot with safestrap in hope of fixing everything. Now system stalls at the white "Kindle fire" screen.
I know that zip is for twrp, but I thought twrp can take backup made with safestrap, why not the other way around?! Well, I'm unlucky this time. One shall never touch stock slot with safestrap. I think I should have used the official update-kindle-13.4.5.2_user_452004220.bin and update through Device-update menu. Oh well.
Any way I can still play with this device before it set off for amazon?
Click to expand...
Click to collapse
Did you already try just holding onto the power button for over 20sec , to force a hard reset and get back into RECOVERY
the rest I'm not sure about you say you are on Thor gapps? with our new 2. 8. 1. 0?
did he make that compatible? I didn't realize Thor gapps was compatible
and what are you even doing with the update .5.2 ?that is the KitKat update and is completely incompatible with safestrap or older kernels so I am really confused on what you have stated in above post
or do you have that TRW P recovery flashed and somehow using safestrap also?
looks like to me you have flashed everything but the right thing but then again it's really hard to tell what you have going on here.
Holding the power button for over 20 sec does me nothing. I can enter "Kindle Fire System Recovery" the same way I entry twrp though by holding power and volume up during booting. There are two options there:
Reboot your Kindle
Reset to Facotry Defaults
I tried both and none helped me to boot into system.
I hate it that HDX is not like Samsung Galaxy phones which have a true recovery mode that can flash file, or a download mode that allows access via adb.
I think the reason that my hdx is bricked are:
1. First, I overwrote twrp with stock recovery 13.3.4 (because I want to restore to stock mode for return). Otherwise if I can still enter twrp, I will be saved.
2. Second, the file I flashed to stock slot with safestrap, update-kindle-13.4.5.2_user_452004120-twrp.zip, is made to boot with twrp. I guess it doesn't go well with the stock recovery 13.3.4.
jimyv said:
InDid you already try just holding onto the power button for over 20sec , to force a hard reset and get back into RECOVERY
the rest I'm not sure about you say you are on Thor gapps? with our new 2. 8. 1. 0?
did he make that compatible? I didn't realize Thor gapps was compatible
and what are you even doing with the update .5.2 ?that is the KitKat update and is completely incompatible with safestrap or older kernels so I am really confused on what you have stated in above post
or do you have that TRW P recovery flashed and somehow using safestrap also?
looks like to me you have flashed everything but the right thing but then again it's really hard to tell what you have going on here.
Click to expand...
Click to collapse
Hello there,
Well, to preface what has led me into the situation that I am in right now, I had installed SS in the hope of creating a virtual ram disk and installing a custom rom within it. Where I messed up is that, despite me having the virtual rom created, I flashed a ROM zip over the stock android rom and not on the virtual rom slot, thus locking me out of my phone. I had done a standard factory wipe before installing the new rom and (unless I am incorrect) have wiped out the usb debugging functionality I had previously enabled as a result. When starting my phone, I am still able to access the custom recovery that SS has installed (I545 Safestrap 3.75 (TWRP v2.7.10)). However, from there I attempt to boot the phone into system, I get an error notice to the effect of "There is software Verizon doesn't supprot please take this to your nearest Verizon store, etc, etc." With a notice at the top saying kernel failed - and at that point if I attempt to start the phone by pulling out battery and restarting, it negates the option to log into SS/TWRP recovery and leads me to that verizon incompatibility screen all over again.
This is where it get interesting though
(I would use link functionality to post a Heimdall screenshot but I couldn't remember my old xda account info and it prohibits users w/ less than 10 posts from posthing links)
If I attempt to reflash the MDK kernel through Heimdall, despite it saying that it failed in the log, my phone reboots and it once again brings me to the SS splash screen at the ability and I able to get back into the SS/TWRP recovery yet again. Very weird.
I have been primarily following instructions from this site: droidview's "how-to-install-latest-official-firmware-on-samsung-galaxy-s4-all-models" (which you can find easily via those terms in google without me posting link)
I have been using the original .pit file that I have pulled from my own phone from heimdall myself (before I locked myself out of stock rom compeltely) but do have a PIT file copy from the website where I have been referencing before.
I have yet to try to flash a zip file of a 4.4.2 verizon ROM via the SS/TWRP recovery because I don't have any SD card readers in my computer and had previously put the custom firmware I had wished to install on my sd card via mounting my phones SD card through the stock ROM to my pc before I messed up overwriting it. The functionality for SS mounting sd card via the recovery itself seems to be broken so that isn't an option. However, I could borrow a phone from someone else and mount my SD card through their phone and access it from my PC that way.
All attempts of reflashing via ODIN on my windows partition have failed as well. ODIN recognizes my device but, following the instuctions from the instructions I referenced earlier, have resulted in it displaying a "FAIL" message almost immediately.
Thanks for taking the time to read this much and I'd appreciate any help I can get.
Hi,
I have a samsung S3 and I want to update it to lollipop or above as my nexus 5 has started randomly rebooting and I need a phone to use whilst I sort a replacement.
I have been following this guide: wccftech.com/install-aosp-android-5-1-1-lollipop-on-galaxy-s3/ as I'm a bit of a noob when it comes to this custom rom business.
I have rooted the device and installed clockworkmod recovery v6.0.1.2. and copied over the rom and the gapps file to my phone.
I then booted into recovery mode and made a backup of the current setup.
I then did the factory reset and the cache wipe(s) and installed the new zip for lollipop and then the gapps.
This is where I received an error "E: Error in /sdcard/0/0/0/Download/gapps-lp-20150314.zip (status 7) installation aborted".
I figured that I should restore to my backup now but when I press it, the app says that files can't be found.
I can see that the files that I backed up do exist but they appear to have been dumped inside a new directory called /0/0/0 (I think this has got three levels because I've tried this a few times).
Now I can't boot into an OS to get any other roms on the phone and I can't edit the files on there (I googled and saw a possible fix for the gapp status 7) and I can't get clockworkmod to recognise an external SD card so I can copy over a new rom or file to try (I have googled and it's suggested the FAT32 is the format for this phone and my size of SD card (16GB)).
Can anyone offer me some advice on how to get out of this situation?
Thanks
Sounds like you're at a place where you should start exploring using your computer instead of a recovery in order to fix your system.
I recommend using the PC software Odin and installing a stock ROM of your device. (Or perhaps using fastboot)
There's plenty of guides on how to use Odin both here on XDA and on the rest of the internet if you just look around a bit
EDIT: This link contains a (possible) fix for your problem.
http://forum.xda-developers.com/showthread.php?t=2522762
Don't use cwm as it is an outdated recovery. Use twrp instead.
Sgt.Mindfudge said:
Sounds like you're at a place where you should start exploring using your computer instead of a recovery in order to fix your system.
I recommend using the PC software Odin and installing a stock ROM of your device. (Or perhaps using fastboot)
There's plenty of guides on how to use Odin both here on XDA and on the rest of the internet if you just look around a bit
EDIT: This link contains a (possible) fix for your problem.
http://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
I had a look at the link you suggested and it's one of the suggestions that had come up whilst I was googling for a fix. Unfortunately, I don't have any way to get the updated script onto the phone as the phone isn't picked up by my pc whilst it's in this state, and I can't get the recovery tool to recognise the sd card so I can't put it on there either.
I'll take a look at the stock rom or fastboot option and see if I can get back into the phone. Maybe then I can apply the fix in the suggested post.
Thanks
audit13 said:
Don't use cwm as it is an outdated recovery. Use twrp instead.
Click to expand...
Click to collapse
I'll see if I can install twrp through odin.
Thanks for your help
If the phone works in download mode, try to flash a stock rom too.
Update - fixed
Hi all, just wanted to let you know that I fixed the device with the combined advice from here:
I installed TWRP after holding the volume down + power + home buttons and then pressing volume up when the message appears (I can't remember what this mode is called). I then flashed the device with the TWRP image.
After this I rebooted into the TWRP recovery mode (Volume up + home + power and then release power button when the samsung logo appears).
At this point, the device appeared on my windows machine so I could upload a new image to the internal memory.
I decided to copy on CM13 and GApps.
I then wiped the cache, system, data, and davik cache using TWRP, then I installed CM13 and GApps.
After a reboot the device came back up as a new install.
Hopefully that information may be useful to somebody.
Thanks for all your help
I'd say I'm above average when it comes to rooting and installing ROMS, but this one has be stumped. It may just be that I simply need to flash the stock ROM and try again, but here's my dilemma.
I successfully installed the correct version of TWRP for my tablet, as was I able to root it, but Xposed posed an issue. Upon flashing Wanam's custome Xposed zip, I am got the dreaded "Encryption Failed" screen. Assuming that Wanam's custom Xposed zip is what I need, because I'm using a Samsung device, what might I have done wrong? I have now formatted and wiped everything and am back to the setting up the device run through, but TWRP is still installed. If I do need to flash the stock ROM (firmware), I can't because I have not found it when searching here or Google.
If anyone has successfully installed TWRP, rooted, and installed Xposed on this tablet, I beg of your assistance. Also, a link to the stock firmware would be amazing.
EDIT: I will add that after I was able to get back to setting up the tablet and no longer facing the "Encryption" boot loop, as well as flashing Wanam's Xposed uninstall zip, I no longer have root and flashing the Chainfire SuperSU does not give root, but brings back the "Encryption" boot loop.
EDIT 2: I have found the stock firmware for this tablet. I found it on two file hosts. One is the well-known RapidGator. The other is an obscure (to me anyway) filehost called Alfafile. I am downloading it from Alfafile because RapidGator makes you pay for their premium service to download a file this large (1.6 GB), but the speed is awful to say the least. Once I download it, I want to share it. Where could I upload this that it would be available to everyone without paying a premium price, a site we are allowed to link on here??
Success... at last!
I did download the correct stock ROM (including boot.img, recovery.img and system.img). It was found as XAR-T580UEU1APG1-20160905144918.zip located HERE. This is the correct stock ROM for this device.
Before trying any of these steps, make sure you have installed the latest Samsung drivers. It may take a few minutes during some of these steps for the drivers to install. If at any point during these steps Windows has a notification that it is installing drivers, stop and wait until the drivers are finished installing. I noticed that a "Gadget Serial" installed when I connected my tablet to Odin in Download Mode. If that happens it's fine, let the drivers install before moving forward. Also it should be noted that this was performed using a PC with Windows 7 Professional.
COME WITH ME ON MY JOURNEY TO FREEDOM!
1. Boot in stock recovery
Hold Volume Up button + Home button + Power button
-OR-
Power off, wait for battery charge screen to come up, the hold Volume Up button + Home button + Power button
2. Wipe data & Factory reset
Press the Volume Down button until wipe data/factory reset is selected (highlighted/colored), then press the Power button, on the following screen use the Volume Up button or Volume Down button to select Yes and then press the Power button, once your screen is back on the main screen where you started, continue to step 3
3. Boot to Download Mode from stock recovery (do not boot to Android OS)
Press and hold Volume Down button + Home button + Power button
4. Odin, prep for flash and connect tablet (latest version, v3.12 at the time of this posting)
Open Odin and click options, then uncheck Auto reboot, and finally plugin your the USB cable into your tablet and PC. Once Odin recognizes your tablet, the far left box under ID:COM will turn blue and the Log tab will say "Added!!"
5. Flash TWRP custom recovery (twrp-3.0.2-0-gtaxlwifi.img.tar)
Click the AP button and find where you saved the TWRP zip.
Once the box next to AP is checked, click Start, if successful the Log will say "Successful 1 / Fail 0".
If this was successful, move on to step 6. Note that you don't have to unplug your tablet from the PC, just close Odin.
6. Boot to TWRP recovery (do not boot to Android OS). This step can be a tricky one and requires good timing. It is important to do these steps quickly.
From Download Mode, press and hold the Volume Down button + Home button + Power button (the Download Mode combo) until the screen goes black, then immediately press and hold the Volume Up button + Home button + Power button (the Recovery mode combo). You must switch from the Download Mode button combo to the Recovery Mode button combo before the Galaxy Tab boot screen appears. If you're too slow, you will have to go back to flash the stock ROM back to the tablet and start back at step 1.
Once in Recovery Mode, swipe the bar at the bottom of the screen, tap mount, and verify that the box next to Data is checked. Once that is verified, you can flash the SuperSU (SR4-SuperSU-v2.78-SR4-20161115184928.zip).
If you had not already copied it to your tablet, you can do this now since Windows should recognize it and allow you to copy the zip file to the table. You can also copy it to the external SD card if you have one and flash from there.
Once you have the SuperSU on your tablet, tap install from the main TWRP screen and then find it (you may have to search the folders), tap on it, and then tap install. If you are wanting to flash Xposed (xposed-v87.1-sdk23-arm-custom-build-by-wanam-20161125.zip), or the boot image patcher (no-verity-no-encrypt_ashyx.zip), do not check the reboot box. Just swipe and flash SuperSU. Once done, go back and select the Xposed zip and flash. Once it is finished, go ahead and reboot, unless you also want to flash the boot image patcher to remove encryption. If you do, install, flash, and then reboot system.
NOTE: If you are going to flash all 3 (SuperSU, boot image patcher, and Xposed) do them in that order.
7. Confirm your work
Once Android is booted, check the SuperSu app and you'll verify you're rooted. Go ahead and reboot into TWRP recovery and you're Data partion is mounted and unencrypted. Now go ahead and install Xposed Installer (XposedInstaller_3.1.1.apk) and you're ready to download and use Xposed modules.
I followed these steps and have my Samsung Galaxy Tab A 10.1 (2016) (Model SM-T580NZWAXAR) rooted, unencrypted (data partition mounts in TWRP recovery), and Xposed framework installed flawlessly with no boot loops, no lost Data partition, no Encryption errors, and no hassel. All credit for the mentioned files and part of the steps to achieve this go to those that the credit is due. My contribtion is merely my journey and this 5 times tested, yes, I completely wiped and formatted my entire device and did this method 4 more times after I had success before writing this, to help others that might be frustrated for days as I was.
:victory:FREEDOM!!:victory:
Thanks for this, I'll be looking to root my tab after the holidays.....:fingers-crossed:
Hello!
Would someone be so kind and explain the following sentence to me:
tpsped said:
If you're too slow, you will have to go back to flash the stock ROM back to the tablet and start back at step 1.
Click to expand...
Click to collapse
Why should it be necessary to flash the whole ROM again?
I know that many ROMs reset the recovery to default, if TWRP hasn't patched the system, but then it should be enough to flash the custom recovery again.
DЯΦ[email protected]П said:
Hello!
Would someone be so kind and explain the following sentence to me:
Why should it be necessary to flash the whole ROM again?
I know that many ROMs reset the recovery to default, if TWRP hasn't patched the system, but then it should be enough to flash the custom recovery again.
Click to expand...
Click to collapse
When flashing the custom recovery, your Data will be unencrypted until you boot to Android OS.
In order to have an unencrypted Data partition, you have to follow these instructions in this order. If you are too slow and boot into the Android OS, you have missed the step and Data will become encrypted. Going back to Stock will once again reset the Data partition to unencrypted in order to properly make it permanently unencrypted.
Anyone unencrypted Data partition is needed in order to flash SuperSU, Xposed, the unencrypted method, or anything else in TWRP. The only exception may be flashing from external sd.
Anyone can correct me if I'm wrong, but I believe this should answer your question.
Wow thank you worked so well best of all guides
tpsped said:
Going back to Stock will once again reset the Data partition to unencrypted in order to properly make it permanently unencrypted.
Click to expand...
Click to collapse
To achieve this it is sufficient to format data partition in TWRP before flashing files, see https://forum.xda-developers.com/ga...ifi-galaxy-t3437666/post68154208#post68154208
ThemGo said:
To achieve this it is sufficient to format data partition in TWRP before flashing files, see https://forum.xda-developers.com/ga...ifi-galaxy-t3437666/post68154208#post68154208
Click to expand...
Click to collapse
Thanks for the info. I do welcome improvements to my instructions. I want to emphasize that these steps were the steps I took and that I figured out these steps on my own because there were no other instructions available that I could find. I'm always learning and growing!
tpsped said:
I'm always learning and growing!
Click to expand...
Click to collapse
Me too, I think everyone should :highfive:
Thank you for your guide, I like the clear steps.