This belongs to this thread: http://forum.xda-developers.com/showthread.php?t=1324831
Sorry if I do not mention every problem in this thread, for there is a lot that can go wrong! If there are any further questions, please feel free to ask. Also, I am not responsible if anything goes wrong, obviously you have a choice to install this ROM. Finally, I am not a dev, I wish I was though. If I have crossed some boundaries, please let me know, I'm sorry this is my first major post. So help me, to help you!
Here is how to install and also get 3G working, don't complain, I tried.
If there are any questions, again, ask.
First, get this ODIN one click, http://forum.xda-developers.com/showthread.php?t=731989 , thank you DG, you are a stud. Download the latest Nightly ,http://download.cyanogenmod.com/?device=captivatemtd , (I used 181). Grab the attached update.zip as well, this will be your CWM, to access it, use the 3 button method to get to recovery (press volume up and down, plus the power. release the power button when you see the ATT logo). Lastly, download Alpha 6, along with the Enable 3g zip and the superuser zip. Put nightly 181, the Alpha 6.zip, superuser.zip, update.zip, and the Enable 3g. zip on your sdcard.
Basic Outline of what needs to be done for original Alpha 6:
Download all the .zip's and the odin. Install drivers, and open up the ODIN.
Put the 4 zip's (Nightly 181, Alpha 6, Enable 3g, and update) on the root of your SDcard.
Open ODIN, and enter download mode on your phone. Connect your phone to your computer.
Press start on ODIN, and let it work.
Once the phone reboots, enter recovery mode. Choose reintsall packages, or install update.zip, whichever is there.
The phone will come back to that same recovery, choose reinstall packages or install update.zip again.
Choose install zip from SDcard, then choose zip form SDcard, and pick the cm7 nightly 181. Let that install.
Once CM7 is intalled, go back to recovery. Choose install zip from SDcard, then choose zip from sdcard, and install Alpha 6. You may have to repeat this step.
Go back into recovery, select install zip from SDcard, choose zip form SDcard, install the superuser.zip. Reboot the phone.
Once booted, log into you Google account, and download Script Manager.
Press the Menu soft key, System Settings, More..., Mobile Networks, Access Point Names, Menu soft key, New APN, Select Name and enter ATT WAP, then select APN and enter wap.cingular, Menu soft key and select save.
Reboot into recovery, install zip from SDcard, choose zip from SDcard, select the Enable 3g.zip, install.
Reboot the phone, open Script Manager.
Select the folder ".." twice (it should be the top folder), your now at the root folder, select etc, then init.d, select 99enable3g. Make sure "Run as root", "Run at boot", and "Run on net.change" are selected. Press save.
Reboot and it should work! Questions? Concerns? Let me know!
Basic Outline of what needs to be done for the Alpha 6 with Hardware Acceleration:
This is optional, but I went back to stock. You need the JF6 like before as well as the update.zip and the Alpha 6HW2D.zip on the SDcard.
Flash back to stock.*
Once finished going back to stock, go into recovery and reinstall packages. Let it reboot and select reinstall packages again.
First, do delete all user data and cache. It works.
Select install zip from SDcard, then choose zip from SDcard.
Select Alpha 6HW2D.zip. Let it complete. Then go back into recovery and repeat. It must be flashed twice.
TADA! let it boot and you should be good to go!
I will be adding more to this, but it will take some time. Thank you.
goob1284 said:
This belongs to this thread: http://forum.xda-developers.com/showthread.php?t=1324831
Sorry if I do not mention every problem in this thread, for there is a lot that can go wrong! If there are any further questions, please feel free to ask. Also, I am not responsible if anything goes wrong, obviously you have a choice to install this ROM. Finally, I am not a dev, I wish I was though. If I have crossed some boundaries, please let me know, I'm sorry this is my first major post. So help me, to help you!
Here is a video on how to install and also get 3G working, don't complain, I tried.
If there are any questions, again, ask.
First, get this ODIN one click, http://forum.xda-developers.com/showthread.php?t=731989 , thank you DG, you are a stud. Download the latest Nightly ,http://download.cyanogenmod.com/?device=captivatemtd , (I used 181). Grab the attached update.zip as well, this will be your CWM, to access it, use the 3 button method to get to recovery (press volume up and down, plus the power. release the power button when you see the ATT logo). Lastly, download Alpha 6, along with the Enable 3g zip and the superuser zip. Put nightly 181, the Alpha 6.zip, superuser.zip, update.zip, and the Enable 3g. zip on your sdcard.
(this video will be added hopefully by the end of today)
Basic Outline of what needs to be done:
Download all the .zip's and the odin. Install drivers, and open up the ODIN.
Put the 4 zip's (Nightly 181, Alpha 6, Enable 3g, and update) on the root of your SDcard.
Open ODIN, and enter download mode on your phone. Connect your phone to your computer.
Press start on ODIN, and let it work.
Once the phone reboots, enter recovery mode. Choose reintsall packages, or install update.zip, whichever is there.
The phone will come back to that same recovery, choose reinstall packages or install update.zip again.
Choose install zip from SDcard, then choose zip form SDcard, and pick the cm7 nightly 181. Let that install.
Once CM7 is intalled, go back to recovery. Choose install zip from SDcard, then choose zip from sdcard, and install Alpha 6. You may have to repeat this step.
Go back into recovery, select install zip from SDcard, choose zip form SDcard, install the superuser.zip. Reboot the phone.
Once booted, log into you Google account, and download Script Manager.
Press the Menu soft key, System Settings, More..., Mobile Networks, Access Point Names, Menu soft key, New APN, Select Name and enter ATT WAP, then select APN and enter wap.cingular, Menu soft key and select save.
Reboot into recovery, install zip from SDcard, choose zip from SDcard, select the Enable 3g.zip, install.
Reboot the phone, open Script Manager.
Select the folder ".." twice (it should be the top folder), your now at the root folder, select etc, then init.d, select 99enable3g. Make sure "Run as root", "Run at boot", and "Run on net.change" are selected. Press save.
Reboot and it should work! Questions? Concerns? Let me know!
I will be adding more to this, but it will take some time. Thank you.
Click to expand...
Click to collapse
Question on the necessity of installing CM7. I came from JF6 stock, and I'm rolling just fine(for a Alpha)
EDIT** adding links for downloads:
A6 Cappy: http://api.viglink.com/api/click?fo...97 ICS!!! A6&jsonp=vglnk_jsonp_13219900825961
SuperuserFix: http://forum.xda-developers.com/attachment.php?attachmentid=776518&d=1320787022
Enable3gv2 fix: http://forum.xda-developers.com/attachment.php?attachmentid=790072&d=1321869485
ICS_VoiceSearchFix: http://forum.xda-developers.com/attachment.php?attachmentid=790280&d=1321887896
Calendar Fix: http://forum.xda-developers.com/attachment.php?attachmentid=790037&d=1321868087
Does downloading apps from the Market work for you? I get the "Insufficient space" error.
swapnil said:
Does downloading apps from the Market work for you? I get the "Insufficient space" error.
Click to expand...
Click to collapse
I am not having that problem. Try clearing the market cache, and reboot
kangi26 said:
Question on the necessity of installing CM7. I came from JF6 stock, and I'm rolling just fine
EDIT** adding links for downloads:
A6 Cappy: http://api.viglink.com/api/click?fo...97 ICS!!! A6&jsonp=vglnk_jsonp_13219900825961
SuperuserFix: http://forum.xda-developers.com/attachment.php?attachmentid=776518&d=1320787022
Enable3gv2 fix: http://forum.xda-developers.com/attachment.php?attachmentid=790072&d=1321869485
ICS_VoiceSearchFix: http://forum.xda-developers.com/attachment.php?attachmentid=790280&d=1321887896
Calendar Fix: http://forum.xda-developers.com/attachment.php?attachmentid=790037&d=1321868087
Click to expand...
Click to collapse
Thank you for the links! I might need help with those instructions, Ill try to look them up. Ill add more to this later, Im gonna be busy for the next couple hours with some house work. Ill be adding the video and clean up the OP. with CM7, ill see how that goes, I just added that in there cause thats how i did it. Ill see if theres a better way. thank you very much for your help!
Just to ask the question - why is the JF6 with bootloaders necessary? Is the current state of the ICS port not compatible with GB bootloaders? Or is it just to have CWM available for flashing?
I'm just asking because if it's just a matter of being on a stock scenario, it would be safer to come from a non-bootloader stock package.
Combined patch:
http://forum.xda-developers.com/showpost.php?p=19596674&postcount=2081
I also did not go from CM7.
Went from KK2 rom --> recovery, clear data, flash ROM -> recovery, clear data, flash ROM --> flash ROM (just for good measure, since I was in endless boot animation) --> flash superuser zip and enable3gv2 zip --> scriptmanager, set script settings --> reboot
Good to go with 3g working. other fixes can be applied too. I think the above package contains all of them.
jmtheiss said:
Just to ask the question - why is the JF6 with bootloaders necessary? Is the current state of the ICS port not compatible with GB bootloaders? Or is it just to have CWM available for flashing?
I'm just asking because if it's just a matter of being on a stock scenario, it would be safer to come from a non-bootloader stock package.
Click to expand...
Click to collapse
You can go with the GB bootloaders, I guess its personal preference. And I did it as a precaution. I like going back to COMPLETE stock to make sure I start from scratch.
zeezz said:
Combined patch:
http://forum.xda-developers.com/showpost.php?p=19596674&postcount=2081
I also did not go from CM7.
Went from KK2 rom --> recovery, clear data, flash ROM -> recovery, clear data, flash ROM --> flash ROM (just for good measure, since I was in endless boot animation) --> flash superuser zip and enable3gv2 zip --> scriptmanager, set script settings --> reboot
Good to go with 3g working. other fixes can be applied too. I think the above package contains all of them.
Click to expand...
Click to collapse
Thank you for that link. And Ill change the directions as soon as i post up that video!
jmtheiss said:
Just to ask the question - why is the JF6 with bootloaders necessary? Is the current state of the ICS port not compatible with GB bootloaders? Or is it just to have CWM available for flashing?
I'm just asking because if it's just a matter of being on a stock scenario, it would be safer to come from a non-bootloader stock package.
Click to expand...
Click to collapse
I dont think it is, I like to make sure I have a known good baseline for testing, so I almost always go to JF6 and MC when I install ROM's like this
Here - I've whipped up a pack with all the fixes (and directions) except the A6 file (as that's pretty big). Enjoy.
SMS Issues
If you're having problems sending SMS:
Open Dialer *#*#4636#*#*
Click: phone info
Press refresh next to smsc and see if the number is 07913121139418f0
If it isn't, input that number and hit Update
Reboot
Thanks Twicebak3d!
jmtheiss said:
Here - I've whipped up a pack with all the fixes (and directions) except the A6 file (as that's pretty big). Enjoy.
Click to expand...
Click to collapse
Wow. Thats amazing. I might do that with all the files! Thanks
FYI, Running A6 with the Cappy kernel. I'm testing the battery now, and hit 100% last night before bed, unplugged, and overnight, dropped to 43%. Limited use since 9am PST, now down to 16%. Something interesting, Screen use is 45%, Phone Idle 20%, Android OS 9%
Device not going to sleep?
kangi26 said:
FYI, Running A6 with the Cappy kernel. I'm testing the battery now, and hit 100% last night before bed, unplugged, and overnight, dropped to 43%. Limited use since 9am PST, now down to 16%. Something interesting, Screen use is 45%, Phone Idle 20%, Android OS 9%
Device not going to sleep?
Click to expand...
Click to collapse
Thats what i think too. Im checking voltage control every once in a while, and the unused state is sleep. 100Mhz is at like 43%+.
goob1284 said:
Thats what i think too. Im checking voltage control every once in a while, and the unused state is sleep. 100Mhz is at like 43%+.
Click to expand...
Click to collapse
Rumor has it that onecosmic is going to release A7 soon. I'll hold on to A6 until then and reflash then. See if that changes anything
I'm getting 65% in deep sleep and 20% in 100mhz...
Sent from ICS captivate. Be jello.
Captivate install instruction for A6
So we start off, of course we need some files & requirements:
Make sure you have a WiFi connection available
The ROM itself: http://forum.xda-developers.com/showpost.php?p=18877954&postcount=1
SuperUser fix: http://forum.xda-developers.com/attachment.php?attachmentid=776518&d=1320787022
3G: fix http://forum.xda-developers.com/attachment.php?attachmentid=790072&d=1321869485
Voicesearch fix: http://forum.xda-developers.com/atta...0&d=1321887896
Calendar Fix: http://forum.xda-developers.com/attachment.php?attachmentid=790037&d=1321868087
I put all of them in a folder called ICS, you name it whatever you want
First of all we need to make sure you do not have simlock enabled.
To disable:
1. Go to settings
2. Go to the security tab
3. Click on sim card lock, and disable it.
You do NOT have to be on any particular ROM to install ICS. I prefer to start from JF6 and Master Clear.
If you are on a custom ROM:
Make sure to disable any lagfix if you have one enabled
Copy folder with your downloads onto your devices SD
If you want to make a backup of your current ROM, now would be the time to do that
Once that is done, power off, and just for safety sake, I remove my Ext SD and SIM
Now we need to wipe the phone.
1. In the recovery menu select “wipe data/factory reset”
2. Go ahead and go to the “advanced” option
3. In there select “wipe Dalvik Cache”
4. Go back to the menu you were before.
5. In the recovery menu navigate to “install zip from sdcard” and press your selection key
6. Now choose the option “choose zip from sdcard”
7. Navigate to the ICS Folder
8. Select the ROM
9. Now navigate to the option “Yes – ROM NAME HERE”
It will now flash the rom.
Once this is done, go back and install the ROM one more time
Once we have done this, go ahead and hit the “reboot system now” option.
Wait for the phone to boot, if it does not go past the boot screen after a few min, pop out the battery, re-install the battery, re-boot into recovery and start at step #1 again
Reboot in recovery.
1. In the recovery menu navigate to “install zip from sdcard” and press your selection key
2. Now choose the option “choose zip from sdcard”
3. Navigate to the ICS folder
4. In there select “Superuser-3.0.6-efgh-signed.zip”
5. Now navigate to the option “Yes – install Superuser-3.0.6-efgh-signed.zip”
Once it’s done, “reboot system now”
Once you’ve restarted. You’ll need to install script manager. For this you must have a WiFi connection, the device will not have a data connection yet. Open up the market and search in for “script manager”, and download & install Script Manager FREE.
When it’s done installing, we are going to add YOUR APN.
1. Open the settings app
2. Click on “more…”
3. Now press “Mobile networks”
4. Then click “Access Point Names”
5. And hit the menu button, then press “new APN”
For AT&T, I have been successful with:
Name: ATT
APN: wap.cingular
Proxy: Not Set
Port: Not Set
Username: Not Set
Password: Not Set
Server: Not Set
MMSC: Not Set
MMS Proxy: Not Set
MMS Port: 80
MCC: 310
MNC: 410
Authentication Type: Not Set
APN Type: Not Set
When you have put these in, hit menu and save
Reboot into Recovery:
1. Navigate to “install zip from sdcard” and press your selection key
2. Now choose the option “choose zip from sdcard”
3. Navigate to the ICS folder
4. Select “enable3gv2.zip”
5. Now navigate to the option “Yes – install enable3gv2.zip”
When it’s done flashing hit the “reboot system now” option.
Thank you to WarDrake in the i9000 threads who simplified this fix. I’m using his instructions and all credits go to him
1. Open script manager and go navigate to : /etc/init.d
2. In here select the script named 99enable3g and open it as a script
3. Now select run as root, run at boot, run on network change (DO NOT RUN IT)
4. Hit the “save” button.
5. Exit script manager
Reboot into Recovery:
1. In the recovery menu navigate to “install zip from sdcard” and press your selection key
2. Now choose the option “choose zip from sdcard”
3. Navigate to the ICS folder
4. Select “ICS_VoiceSearchFix.zip”
5. Now navigate to the option “Yes – install ICS_VoiceSearchFix.zip”
1. Select “choose zip from sdcard”
3. Navigate to the ICS folder
4. Select “CalendarFix.zip”
5. Now navigate to the option “Yes – install CalendarFix.zip”
Reboot, and you should be running ICS.
If you cannot send SMS(Thanks to Thanks Twicebak3d)
Open Dialer *#*#4636#*#*
Click: phone info
Press refresh next to smsc and see if the number is 07913121139418f0
If it isn't, input that number and hit Update
Reboot
jmtheiss said:
Here - I've whipped up a pack with all the fixes (and directions) except the A6 file (as that's pretty big). Enjoy.
Click to expand...
Click to collapse
This looks like I can flash from CWM. Is that right?
Sent from my SGH-I897 using xda premium
elmerct said:
This looks like I can flash from CWM. Is that right?
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Each individual file, yes
Does wi-fi tethering work?
First up - Let me say that the complete credit to the method goes to two members here as in the thread https://forum.xda-developers.com/galaxy-tab/help/galaxy-tab-active-2-forum-question-t3712591
BUT BUT BUT what the two experts have missed out is on explaining a clear step by step guide for a complete noob like me . So this is an attempt to explain every step. My tab had root in less than 10 mins .
why i needed the root ?
16gb is not enough for the tab so i wanted to apps and data to be moved to the sd card .
Here are the steps
On the Pc
1. Download the stock firmware (must be the same as in your tab) from samfirmware or any other source.
2. Extract the firmware and the extract archive called AP... . Once extracted you will have a boot.img file in it.
On the TAB
3. Activate developer options by clicking the software version 5 times.
4. In the developer options check OEM unlock and USB debugging
5. Download Magisk Manager v16 from xda and install on the TAB.
Connect the tab to the pc
6. Copy the boot.img file from pc to the tab.
7. Run Magisk Manager and in settings choose the output format as odin compatible tar,
8. Click the INSTALL button in the MAGISK manager and choose 'patch boot image file'
9. After a few minutes a dark screen will appear will read all ok boot image patched...now copy that patched_boot.img.tar file from the tab to the PC and rename it as boot.img.tar
On the Tab
10. Recheck under developer options if check OEM UNLOCK and USB DEBUGG
11. DELETE the GOOGLE account (crucial)
12. Switch of the tab
13. Go to download mode by holding vol down, menu and power together , once asked press vol up to go to the download mode.
14. Connect tab to PC.
On the PC
15. Download ODIN and once downloaded right click and run as administrator.
16. Choose AP and select the previously patched boot.img.tar file.
17. Click START
On the TAB
18. It will run the download and restart , restart will say "VERIFICATION FAILED and aask to RESET and erase .
19. CLICK RESET
20. wait for reset saying ERASING and let the tab restart.
NOW the next step is the most crucial one and it is where i got stuck as none of the members who have rooted their device mention it. I did all of the above procedures repeatedly and failed to get root until i realized there was one FINAL CRUCIAL STEP before enjoying the root.
LAST STEP
ON THE TAB
After the TAB restarts , fill in the initial details (google , samsung account, wifi etc) and before you do anything else INSTALL THE MAGISK MANAGER V16 app you downloaded from XDA .......thats it ....you have root access now . ENJOY!
How did you install Magisk?
When I open Magisk Manager v5.6.4, I get a "Magisk is not installed" and I only have the settings option.
No "install" options.
I have the same tablet. don't know of any twrp that can work with it, therefore leaving me with Magisk Manager only.
Id' be glad to get some help
Thanks,
SOLVED: You must have a functioning network interface in order for the "install" button to appear and you need internet connection to "install the v16 zip".
Magisk is OpenSource though, right? so probably it can be changed to allow offline installation as well.
Rooteed
Well Crap...I just got my Nice, New, Sparkleing Tab Active2 and cant root it yet. I have the New US version SM-T397U Unlocked model. cant find a Stock firmware on Sammobile as of yet...any ideas?
EDIT: Neeeevermind... I did a lil hacking and cracking (for about 26min, lol) to find the files I needed for the SM-T397U. If anyone is looking for em let me know and I'll shoot em' your way. Guessing I'm the first person to root a T397U, hope more will follow. I havent even had this thing 6 hours yet. Thanks for the write up and all those that contributed to the tools and info!
I followed every steps till the end and everything went smoothly. But once I rebooted the tablet, I got the red label on the top left corner: "custom binary blocked by OEM lock". The tablet won't boot properly anymore "OEM unlock" was enabled in the Developers options, I double checked to be sure before flashing.
Edit:
Actually, the "custom binary blocked by OEM lock" appears as soon as I modify the system partition (I wanted to modify the Generic.kl in the keylayout folder on the system partition). If you do not touch anything, everything is fine.
[X-POST from here ]
Worked perfectly, Thank you very much!
WARNING: THIS WILL WIPE EVERYTHING ON YOUR TABLET.
Backup all of your important files before you flash the patched boot.img using odin.
I tried to backup my app data using samsung switch and it worked, but didn't restore most of my device settings and all of my app data.
(Good thing I kept backups for my important apps that had in app backup functionality - like Nova launcher and Squid)
Keep in mind that you probably won't be able to get OTA updates after you perform these steps, it doesn't matter though since this tablet isn't going to be updated that frequently (The 8.0 update is going to come at the end of 2018, source)
Hello.
I tried this but when i using the magisk manager i have an error meassage and the following log:
- Copying image to cache
- Device platform: armeabi-v7a
- Existing zip found
1038+1 records in
1038+1 records out
1063528 bytes transferred in 0.022 secs (48342181 bytes/sec)
- Unpacking boot image
MagiskBoot v18.1(18100) (by topjohnwu)
- Boot Image Modification Tool
mmap failed with 12: Out of memory
! Unable to unpack boot image
! Installation failed
Can you help what i did wrong?
Thank you
oem unlock does not appear
SOLUTION FOUND
how do you oem unlock
I have wasted hours on this, waited weeks, tried the date trick with a legit setup, but the oem unlock never appears, running oldest version of firmware 7.1.1 feb 2018, what gives?
Tried reinstalling firmware via odin, successful flash but no factory reset. Suspect this made no difference. Got the security fail on PIT error, needed a new version of odin and selecting individual AP etc. files fixed this.
apparently you need a samsung or google account
So trying a samsung account... no dice
Now trying adding a sim card as well... success
OK after months of waiting and trying things, this just worked!
Update- I lost the date trick, have to wait 7 days after step 7 on auto date, just appears in developer options no need to press manual update.
https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-skip-rmm-prenormal-install-t3749468
- try downloading UK rom which was released before december '17 (october)
See if it lets the below process work again?
0/ install sim card (was not even the original carrier one in my case although my phone is not carrier locked)
1/ factory reset
2/ on reboot skip all accounts, do not enter a name do not turn on wifi, accept minimal amounts of things
3/ set date to 1/4/19 - turn off automatic date
4/ turn off automatic software updates
5/ enable developer options and turn off auto update system
6/ turn on wifi (date changes)
6b/ change date back
7/ Install samsung account (I went to samsung cloud) (date not changed but software update now triggered despite not touching manual update)
8/ (for interest look at manually check for software updates - it already says 1/4/19 last checked)
9/ reboot
10/ (date is now changed back to today again without my permission)
11/ (it pops up asking to install an update, despite auto updates turned off. - LATER)
12/ (last checked software date is now today (because I left wifi on I think through a reboot) this is 4/5/19 over 1 month later)
13/ go to developer options for the 27868745# time
OEM UNLOCK APPEARED HOLY ****
It is between Bluetooth HCI snoop log and Running services on the dev page, top of the developer options
Since the RMM prenormal thing triggered I had to do this again, so the above instructions do work.
If you stuff up the date just factory reset and start again. Reflash not required
I used a brand new throwaway samsung account for this but thats possibly up to you.
RMM state prenormal
OK now that I've jumped through hoops, installed TWRP
I go to reboot and it's locked recovery again - repeat above OEM unlock reappearing act steps fixes RMM=prenormal. Now it's official again.
Apparently you need to install an RMM patch as well which is not mentioned in this thread.
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
So, odin -> ap -> TWRP download
quickly press power-up-home when it resets!!!
recovery is not seandroid enforcing appears and TWRP starts.
1. back up all partitions to microsd!
2. install
a TWRP -> magisk
b TWRP -> RMM disabler - this writes to /system defeating the purpose of magisk???
wipe cache/dalvik reboot
on boot:
"Verification failed"
"Unable to restart your device the integrity verification has failed.... erase all your data"
Well recovery boots this time not an RMM error thats nice... oh it runs a few commands and automatically restarts again.
"Verification failed..."
I guess that is a boot loop then, thanks TWRP for not stopping at a menu ffs.
Reflash TWRP with odin, now it halts at TWRP menu.
https://forum.xda-developers.com/ga...t/how-to-recover-verification-failed-t3775722
Apparently I should put in download mode and cancel - Result = fail & TWRP bootloop -> reinstall TWRP
unmountable /data partition - yep thats me - could try format to exfat - ext4 - Result = Verification failed ffs
---------- Post added at 01:52 PM ---------- Previous post was at 01:00 PM ----------
Take 3
"Looks like you didnt flash encryption breaker." no-verity-no-encrypt_ashyx.zip or no-verity-opt-encrypt-6.0 zip well duh of course but which one for t395
https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
seems a few up to 6.0
BTW if you don't press reset and instead try and reboot into recovery you don't have to reflash TWRP
Verification FAIL.
https://forum.xda-developers.com/galaxy-note-8/how-to/guide-how-to-root-device-encryption-t3742493
Take 4 - try reinstating boot.img with no mods.
Try flashing stock AP -> twrp -> DMM fix -> magisk in quick succession & booting tablet
Verification Failed! Reset
Goes to recovery - less errors on TWRP (no mount errors like before) but verification failed again.
Because TWRP is installed I don't get the erasing screen as described by OP....? TWRP does something very quickly I think it says formatting cache, it is doing a standard factory reset. Trying manual factory reset with TWRP does not work.
So I think I need TWRP to prevent DMM tripping and install magisk but I need stock recovery to avoid the verification failing constantly.
Or a new version of TWRP that supports encryption? 3230+ I have 3230...?
Try Stock RO system - twrp - dm verity - magisk
Verification failed. Reset - no dmm error thats nice. TWRP did some extra stuff.
Verification failed again.
#&%^&^#%$#[email protected]#%[email protected]#%#$%
Option 556
Install dmverity patch using stock recovery.
Gives error can't find /misc partition - pretty sure these are TWRP zips only.
Magisk website says install TWRP so I can't see how to avoid TWRP and this annoying verification fail. Maybe try an older version of magisk???
Verification bootloop FIX:?
I tried booting stock, it says something like data corrupt on start, looks the same as the verification failed but with the different message. I let it erase/factory reset with stock recovery.
DMM preload did not trigger on this!
As soon as it succeeded I installed TWRP in case DMM triggers.
Now with fixed data partition (presumably) retry TWRP
1. no verity patch (6.0)
2. magisk
cannot install DMM as it alters system partition...?
No cache wipe.
Lets see what happens...... Black screen but this time
'encryption failed' reset. Press reset.... TWRP does a factory reset
'encryption failed'
LOL now I have an encryption failed bootloop.
Reinstall stock and use stock factory reset again - boot to recovery straight away, wipe data & cache
Now install TWRP (not booted once yet)
Install verity patch 6.0
install magisk 19.1
Boot system for the first time. - got a bootloop? no just taking it's sweet time. Fingers crossed!
Android is starting... WELCOME
HOLY **** IT WORKED
DMM patch not installed and it hasn't tripped DMM yet (the old 7 day wait issue)
SUMMARY:
1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps
2/ flash stock AP - do NOT boot system yet
3/ stock recovery - wipe data and cache
4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar
5/ twrp - install no-verity-opt-encrypt-6.0.zip
6/ twrp - install magisk 19.1
7/ Boot system for the first time
So I have not installed RMM patch (system untouched) but I did install the no encryption/dm verity patch.
It actually boots now.... will update if further problems
Interestingly OEM unlock has disappeared, so RMM must be prenormal so it will probably die on reboot. Argh. But everything is restoring OK for now. See what happens...
Magisk app auto installed and passes safetynet. Preserve force enctyption and AVB 2.0/dm-verity unchecked.
Annoyingly despite backing up all my messages to samsung they are not restoring past 20 april. Not the end of the world.
Skype keeps stopping.
Reboot and YES only officially released binaries are allowed to be flashed boot loop.
So lets do this again!
SUMMARY:
1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps
8skip 2/ flash stock AP - do NOT boot system yet
8skip 3/ stock recovery - wipe data and cache
4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar
5/ twrp - install no-verity-opt-encrypt-6.0.zip
6/ twrp - install magisk 19.1
7/ Boot system for the second time
Pretty sure I already tried this so it won't work. &^%#@&^$#$#%#$%@##%@
Oh great it has managed to install the update and now the date fix doesn't work. &^#%&^#$#@$%@#$
After waiting 7 days
1/ Use stock recovery factory reset, then immediately hold down-home-power download mode
2/ Odin TWRP, then immediately hold up-home-power to enter TWRP
2a/ TWRP swipe to allow modifications (for RMM patch)
3/ TWRP install RMM patch
4/ TWRP install no verity patch
5/ TWRP install latest Magisk
NB Magisk seems to install itself as an app - its just there.
...Safetynet pass despite RMM editing /system phew
Hello,
With the last version of Magisk, we no longer have the setting to choose the output format as odin compatible tar.
How can we deal with this, please ?
Regards,
Driss35 said:
Hello,
With the last version of Magisk, we no longer have the setting to choose the output format as odin compatible tar.
How can we deal with this, please ?
Regards,
Click to expand...
Click to collapse
You don't have to choose any file type. Magisk scans files automatically.
Also, if your file type is ".lz4", you have to change it to ".img". Unless, you can't continue.
@Drnms thanks for this thread. But, some places have to be updated because of new Magisk versions.
Did App data remain after rooting
Drnms said:
First up - Let me say that the complete credit to the method goes to two members here as in the thread https://forum.xda-developers.com/galaxy-tab/help/galaxy-tab-active-2-forum-question-t3712591
BUT BUT BUT what the two experts have missed out is on explaining a clear step by step guide for a complete noob like me . So this is an attempt to explain every step. My tab had root in less than 10 mins .
why i needed the root ?
16gb is not enough for the tab so i wanted to apps and data to be moved to the sd card .
Here are the steps
On the Pc
1. Download the stock firmware (must be the same as in your tab) from samfirmware or any other source.
2. Extract the firmware and the extract archive called AP... . Once extracted you will have a boot.img file in it.
On the TAB
3. Activate developer options by clicking the software version 5 times.
4. In the developer options check OEM unlock and USB debugging
5. Download Magisk Manager v16 from xda and install on the TAB.
Connect the tab to the pc
6. Copy the boot.img file from pc to the tab.
7. Run Magisk Manager and in settings choose the output format as odin compatible tar,
8. Click the INSTALL button in the MAGISK manager and choose 'patch boot image file'
9. After a few minutes a dark screen will appear will read all ok boot image patched...now copy that patched_boot.img.tar file from the tab to the PC and rename it as boot.img.tar
On the Tab
10. Recheck under developer options if check OEM UNLOCK and USB DEBUGG
11. DELETE the GOOGLE account (crucial)
12. Switch of the tab
13. Go to download mode by holding vol down, menu and power together , once asked press vol up to go to the download mode.
14. Connect tab to PC.
On the PC
15. Download ODIN and once downloaded right click and run as administrator.
16. Choose AP and select the previously patched boot.img.tar file.
17. Click START
On the TAB
18. It will run the download and restart , restart will say "VERIFICATION FAILED and aask to RESET and erase .
19. CLICK RESET
20. wait for reset saying ERASING and let the tab restart.
NOW the next step is the most crucial one and it is where i got stuck as none of the members who have rooted their device mention it. I did all of the above procedures repeatedly and failed to get root until i realized there was one FINAL CRUCIAL STEP before enjoying the root.
LAST STEP
ON THE TAB
After the TAB restarts , fill in the initial details (google , samsung account, wifi etc) and before you do anything else INSTALL THE MAGISK MANAGER V16 app you downloaded from XDA .......thats it ....you have root access now . ENJOY!
Click to expand...
Click to collapse
Hi Dmms,
Please confirm if the data remained (i.e. was not erased) after the rooting?
Thanks in advance.
Hi, in case it is still relevant:
- Tab does a factory reset when booting first time after the boot img is flashed, data on the device is lost. Data on the SD card is not affected
- In my case, flashing boot.img with Odin didn't work. Odin said success, but no root. Heimdall worked fine, tab was rooted at first attempt
Does this guide also work for Android 9 ?
Edit: So it works with Android 9 also but I had to unpack the boot.img with 7zip ZS according to this post https://forum.xda-developers.com/t/samsung-a40-how-to-root.3929496/post-79902328
and re-pack it with normal 7zip according to these steps:
Do you have the boot.img.lz4 file to boot.img unpacked?
You have renamed the magisk_patched.img to boot.img?
You used the normal 7zip to package into a .tar file? Not the 7zZs?
You used the normal Odin 3.14?
Hello, did you manage to remove the "format as internal" lock?
Hi guys,
Trying to root this tablet, when I load the patched magisk file in Odin and perform the download. The tablet restarts and loads like normal but the tablet isn't rooted.
Any ideas?
alguma fortma?
What You'll Need:
The experimental firmware: https://androidfilehost.com/?fid=745425885120704448 (Thanks @NavSad !)
My updated G900A RootPack: https://drive.google.com/file/d/1U7vwyq4T4609SiUQz43zLXvYOu9Hqohb/view?usp=sharing
(Windows Defender may detect TowelRoot as an Android Malware Exploit, you may need to disable defender temporarily.)
If you want to downgrade to NCE/KitKat: The G900A_NCE.Zip file: https://drive.google.com/file/d/1ahpVGnG3bQ-mEoztN4XUvdbTOW64IdoT/view?usp=sharing
Get Ready:
You will need to extract the RootPack files and move the RootPack folder along with the G900A_Firmware.zip to an external SD and put it in your phone.
What To Do:
Step 1: Go back down!
Download the experimental firmware and extract the zip on your computer.
Open Odin3, select the AP slot, and specify the experimental firmware so you can flash it.
Under Options, Make sure only "AutoReboot" and "F. Time Reset" are selected.
FLASH
Step 2: Our Old Friend
After the OS is installed, go to the file manager and install Flashfire, SuperSU, TowelRoot, BusyBox, and SafeStrap.
Run towelroot. Simply hit "make it ra1n" and 3 seconds later you'll have the root binaries installed.
Now open the SuperSU app and hit "continue", let it do its thing and then update the SU binaries (you don't have to reboot)
Step 3. Where to go?
You now need to determine where you want to go?
You can downgrade to NCE or upgrade to OF3
NCE DOWNGRADE/ROOT GUIDE
(KitKat) (Will downgrade you to KitKat and root it)
Now open BusyBox, dismiss the social prompt, and hit install
Now open SafeStrap Installer, grant SU Permissions, and Install recovery (DO NOT Reboot into it)
Open FlashFire, Grant SU Permission, and Accept the Disclaimer.
Hit the '+' and hit 'Flash Firmware Package', navigate and select the G900A_NCE.Zip, and let it scan the archive.
Check Recovery, System, Cache, and Persist. Uncheck modem/Firmware
Hit the Check in the Top Right to confirm changes and Hit the '+' again
Select Wipe System. 3rd Party Apps, Cache Partition, Cache Partition Format, and select the check in the top right to confirm changes
Drag wipe above the flash firmware package
Select EverRoot, Uncheck "Inject SuperSU" (If you don't, it will cause a kernel panic)
Select Reboot, Check Select "Preserve Recovery", and select the check in the top right to confirm changes (If you don't do this, you won't have recovery once you downgrade.)
HIT FLASH and OK (This will work, don't panic) It may take up to five minutes for the process to complete, if it fails, reflash combination.
After the OS is installed, go to the file manager and install TowelRoot, SuperSU, BusyBox, And SafeStrap
Run towelroot. Simply hit "make it ra1n" and 3 seconds later you'll have the root binaries installed.
Reboot to make SuperSU detect root.
Now open the SuperSU app and hit "continue", let it do its thing and then update the SU binaries (Yes, Reboot now)
Now open BusyBox, grant SU Permissions, dismiss the inital message and install busybox
Now open SafeStrap, grant SU Permissions, Install Recovery.
Your all set.
OF3 UP/DOWNGRADE/ROOT GUIDE
(Lollipop) (Will downgrade you to Lollipop and root it)
Open FlashFire, Grant SU Permission, and Accept the Disclaimer.
Select "Flash Zip/OTA" and Select the G900A_OF3.zip
Mount /system read/write
Select "Flash Zip/OTA" and Select the G900A_OF3_Tether.zip
Mount /system read/write
Select Wipe System. 3rd Party Apps, Cache Partition, Cache Partition Format, and select the check in the top right to confirm changes
Drag wipe above the flash firmware package (This will fix battery/heating/lag issues while your on OF3) (Trust Me)
Select Wipe System. 3rd Party Apps, Cache Partition, Cache Partition Format, and select the check in the top right to confirm changes
Drag below the G900A_OF3.zip (This will clean up the setup) (Trust me)
Hit "flash", let it flash, reboot, and load.
HIT FLASH and OK
After OS is installed, you will have root.
Copy G900A_OF3_Kernel.zip to the RootPack folder.
Install BusyBox, open and grant SU, Install BusyBox
Install SafeStrap, open and grant SU, Install to Recovery. (DO NOT Reboot into it)
Download the NCE_Flasher then install it, and open it up then hit " flash", wait for it to finish then hit "tap to reboot" and it will take you directly to SS recovery. Then you can flash whatever MODs or addons you wish or even ANOTHER ROM, just make sure you wipe everything but the external SD card if you are flashing a new ROM and you should be good.
Remember to ReFlash the G900A_OF3_Kernel.zip file in SafeStrap before you exit SafeStrap otherwise you will not be able to reboot.
If you forget and end up with an error, Just flash G900A_OF3_Kernel.zip with Odin3. (It won't wipe anything)
Marshmallow
---Working on a method---
(Won't stop until I have every update rooted.)
Marshmallow is currently unrootable on the G900A and G900V (CID 11). A method will likely appear in the future.
It is safe for you to flash to the latest Marshmallow, you will be able to restore the experimental combination to root again.
Notes: This guide is an updated version of AptLogic's Guide. ( Can a mod please sticky that thread )
I have created this thread as an "elimination of confusion"/"Catch All" and I will update the thread once I get root on Marshmallow , https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196.
Thank you to AptLogic and everyone involved in the development of root for this device.
Which File where?
So which files go in which slots in ODIN ?
NM...I get it now. Thanks will let you know how it worked for me !
CheeseMerchant said:
So which files go in which slots in ODIN ?
NM...I get it now. Thanks will let you know how it worked for me !
Click to expand...
Click to collapse
Guide Updated.
Works Great !
Justin1198 said:
Guide Updated.
Click to expand...
Click to collapse
Thank you !!! This worked great!
It has not worked for me or something I did wrong
please help me
Since I can downgrade my S5 to kitkat does that mean that I can use the CyanogenMod build for kitkat on the s5 or will it brick my phone ?
First off, thank you so much for this guide! I recently got an old Galaxy S5 from my Dad, and rolled it back to KitKat using these instructions.
I'm experiencing two rather strange issues, though.
1) KitKat doesn't seem to be remembering my Wi-Fi password. I'm having to re-enter it every time I reboot the phone.
2) I'm getting a message on booting that "Safestrap is disabled. System will start in 10 seconds." The system starts like it should, but this message pops up every time. Is this normal, or will something correct it?
Any assistance would be appreciated. Thanks!
The Google Drive links are dead. Could we get new ones please @Justin1198?
Thanks in advance!