Database Info

[Q] how do i bring back root on my i9023 ics 4.0.4

I have just updated my nexus s to the latest 4.0.4 update..now i want to bring back root access .. as we all know were going to loose root access if we updated. anyway i previously used this method http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ now im wondering if this also applies to 4.0.4 update and what is the best recovery to flash on this update?

The only thing i did was upgrade to 4.04, dont reboot but flash superuser, all clear, root is back.

[Q](solved) how do i bring back root on my i9023 ics 4.0.4
willemt158 said:
The only thing i did was upgrade to 4.04, dont reboot but flash superuser, all clear, root is back.
Click to expand...
Click to collapse
hmn... what i did was
i went to adb
open cmd
flashed recovery3101.img
after that i installed superuser using CWM recovery . if your using the stock recovery it will only show an error msg. didnt wipe anything ... all is ok and well hehehe cheers!

I have issue with CWM and Root. I've follow the guide here.
I manage to successfully do up to step 4 without error. After that, when I reboot the device, it have a message "android installing update". I installed titanium backup and it says no root access. Superuser is available. When I tried to update on Play "Update for Superuser could not be downloaded due to an error (941)"
I tried to go back to recovery, it is the stock recovery instead of CWM. I've updated my 9023 from 4.0.3 (stock non root) to 4.0.4 using CWM. I've installed superuser using CWM as well. But when I reboot the device, it went back to stock recovery. I've tried fastboot CWM, turn off, then turn back on to go recovery, it is using CWM. But when I reboot, and try to go back to recovery, it goes to the stock recovery.
Appreciate some help. Hope my explanation is clear.
Will

First try flashing the latest Superuser than reboot, then open rootexplorer
Rename "/system/etc/install-recovery.sh" to "/system/etc/install-recovery.sh.bak".
All Stock ROMs replace the recovery on each Boot if it isn't the stock one. Renaming this script stops that. After you do this, flash CWM one more time and it'll stick.
Thanks to harbb who helped me with the same isseu

not sure if this is legit... I found a few sites with the same tutorial but different backup apps same file download though... can anyone varify?
filename: Superuser-3.0.7-efghi-signed, from a mediafire download (/?57iroxlzh8bb5qi)
from tutorial: Root Nexus S with Android 4.0.4 ICS IMM76 Firmware, from androidlot.com
(sorry can't post link)
it just said to do a recovery from bootloader, no other tampering needed... was thinking of using it if it worked as I just did the Nexus S 19023 OTA update 2.3.6 - 4.0.4 found on this forum but wanted to root to use voodoo sound... first timer and dont want to mess around with roms or cwm... figure no harm rooting as Nexus S probably won't get anymore official updates

Signature verification failed
well i have tried to install the superuser from recovery (apply update from SDcard) but every time i try to install the zip file it gives me signature verification error .

Mansuur said:
well i have tried to install the superuser from recovery (apply update from SDcard) but every time i try to install the zip file it gives me signature verification error .
Click to expand...
Click to collapse
That means your not in CWM Recovery. You have to follow the guide and use fastboot to flash a custom recover. Thats why we use a custom recovery, to bypass the signiture check

so wats da final result?
in ics 4.04 how to flash cwm and root and install vodoo?

ended up using m.sabra's one click root and flash cwm tool (/showthread.php?t=1544940) worked a charm, downloaded voodoo sound plus so i didnt have to flash new kernel, putting music back on phone now (had to unlock bootloader) to see how it sounds
also used appbackup&restore, copied backup folder from sd to computer, used the root tool, redownloded appbackup&restore, copied folder back from computer to phone, allowed install from non market, reinstalled all apps
now have superuser and cwm and all my apps back

Hope this may help. it's the way a did it on my Nexus S
Download fastboot for Windows or Mac.
Make sure you have the Android SDK installed.
Download ClockworkMod Recovery.
Download the Rooted Su Binary for 4.0.4
Make sure you have the necessary drivers installed for your device
Put your device into Bootloader Mode (turn your device off, then hold Volume Up + Power).
Once in Bootloader Mode, type the following into your Command Window
fastboot oem unlock
You should now see a couple of lines go through on your Window.
Then Type the following:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Provided this went correctly (it should), you now want to cycle down to “Recovery” on your device using the Volume buttons and press Power to confirm. This should boot you into ClockworkMod.
Select Recovery again, navigate to “Mounts & Storage” and then to “Mount USB Storage”. Once this has been done, your SD Card should appear on your PC.
Copy the Rooted Su Binary you have downloaded to your SD Card, and then Unmount USB Storage on your device.
Navigate back to the main menu of ClockworkMod and select “Install zip from sdcard”, then “Choose zip from sdcard” and select the package you just copied across, and then confirm the installation. This should install the package and root your device.

Hey guys sorry i was on vacation, thats why it took me so long time to come back, anyways... here is the link of the step by step procedure on rooting your nexus s, this is what i followed, http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
but what i did was ;
1. after updating i lost root
2. open adb tool
3. flash new recovery3101.img ( this is to replace default recovery from the stock ics 4.0.4)
4.then installed superuser from the new recovery that i installed ( CWM)
i wont go through all the details since , the link already explained that there....so cheers and hope this works for you , all the needed files is in the link also.

Mrbalders said:
Hope this may help. it's the way a did it on my Nexus S
Download fastboot for Windows or Mac.
Make sure you have the Android SDK installed.
Download ClockworkMod Recovery.
Download the Rooted Su Binary for 4.0.4
Make sure you have the necessary drivers installed for your device
Put your device into Bootloader Mode (turn your device off, then hold Volume Up + Power).
Once in Bootloader Mode, type the following into your Command Window
fastboot oem unlock
You should now see a couple of lines go through on your Window.
Then Type the following:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Provided this went correctly (it should), you now want to cycle down to “Recovery” on your device using the Volume buttons and press Power to confirm. This should boot you into ClockworkMod.
Select Recovery again, navigate to “Mounts & Storage” and then to “Mount USB Storage”. Once this has been done, your SD Card should appear on your PC.
Copy the Rooted Su Binary you have downloaded to your SD Card, and then Unmount USB Storage on your device.
Navigate back to the main menu of ClockworkMod and select “Install zip from sdcard”, then “Choose zip from sdcard” and select the package you just copied across, and then confirm the installation. This should install the package and root your device.
Click to expand...
Click to collapse
wow very detailed cheers man!

Glad to help, and hope you've got your Nexus back to root

[GUIDE] Videocon A55 HD Rooting and Recovery related stuff

Heya,
Since there is not enough info on the web regarding the rooting procedure for Videocon A55 HD and custom recovery for this awesomely smooth device, I'm uploading the necessary files and step by step guide. Hope it helps all the users of this device.
Remember rooting would tamper the warranty of the device and should be exercised carefully. The procedures mentioned below have been personally tested by me however I take no responsibility in case you ruin your device although I would be here to help you in such a scenario. Besides this the rooting script was not created by me and all the credit goes to the respective developer.
1. Rooting Procedure
Make sure you have enabled "USB Debugging" under Developer Options on your phone.
Keep your phone disconnected from computer via USB
a) Download and Install the ADB Interface driver for MTK 6589
Link to ADB Drivers
b) Download and extract the rooting package
Link to the Rooting Package
c) Now go to the extracted package and open a command prompt to that location as Administrator.
d) Type run.bat in Command Prompt and a message must appear "Press enter to root your phone..."
e) Press any key
f) Now after a few seconds the message should be " * daemon started successfully *"
g) Now connect your phone via USB to the computer
h) The cmd would automatically start pushing the necessary files onto your phone and when the process completes your phone will restart
Now you are rooted.To check install any Root checker application from playstore. Remember to grant permission while running Root Checker app when a pop up appears. It is suggested to update the SuperSU app from playstore and execute it at least once after that to update the su binary. You can also update the busybox package from playstore because busybox supplied with the rooting package is pretty old.
2. Installing CWM Recovery
Okie, since you are now rooted, most likely you would require a custom recovery to create full nandroid backups or test different ROMs. The CWM recovery provided here was created using MTKDroid Tools and is version 5.x (Non Touch). Again all credit goes to the developer of MTKDroid Tools for making such a powerful piece of software.
a) Download and extract the recovery package.
Link to CWM 5.x and Original Recovery for A55 HD
b) There are two files in the package , one is the custom CWM recovery and the other one is Stock Recovery (Names are pretty self understood)
c) Copy "Custom_Recovery_CWM_A55HD.img" to the root of your SD card
d) Rename it to "recovery.img"
e) Install Mobile Uncle Tools [MUT] from the playstore.
f) Open MUT and go to recovery update
g) Now you must see the recovery.img in a list. Just select it and follow the pop ups.
h) Now your phone would restart.
i) To check if the recovery update was successful, go to MUT and select "Reboot into Recovery" and your phone would most likely start in CWM recovery..
Alternative to get into recovery mode is to Press Power button + Volume Down key together when switched off.
3. Stock ROM for Videocon A55 HD
Okie, here we go, as I mentioned that I had got hold of the stock rom, so here I'm publishing it. The credit goes to Pratap Solunke (psolunke) for providing the Factory ROM zip.
I have just divided it into update.zip and files for SPFT for ease of downloading. Besides I have splitted each section into 4 parts and reuploaded it so you can download them at your ease. I'm providing the link for the whole folder which includes the changelog, update.zip and files for SPFT.
The ROM version is V7 (2013.07.15) which is different from the original ROM which was V5 (2013.06.08).
You can read the changelog for the updates in this ROM.
Link to ROM Folder
If using update.zip to flash this ROM, then
Step 1. Open the update.zip with winrar, Do not extract.
Step 2. Navigate to \META-INF\com\google\android\updater-script and extract this file only, then use "Notepad++" to open the file.Don't use default notepad.
Step 3. Delete assert(getprop("ro.product.device") == "A55HD" || getprop("ro.build.product") == "A55HD");
Step 4. Save the file, put it back to the same location in archive (It will take some time to add to archive)..Done...then proceed as usual.
a) update.zip is for reinstalling Factory Image of the ROM from recovery mode. The zip file is signed.
b) Files for SPFT are to be used with SP Flash Tool and can be used in case your phone is bricked. Do not flash the preloader unless you know what you are doing.
c) To download the files just go to the respective folder and right click on each file and hit download. After all four parts are downloaded, extract Part 1 of the downloaded splitted files and the files would be ready to be used as is.
d) Keep all four parts of the splitted files in a single folder and do not rename the splitted files.
If you have any questions related to A55 HD you can ask them here and I would try to help you the best way I can.
I'm still testing some custom ROMS but none seem to work . So far I've tested LEWA OS and MIUI ROM for xiacoao G6 Youth. However I'll keep trying and update once I have a working Custom ROM.
One more project in mind is to port Custom ROMS to A55 HD if none is available as is on the web.
If anyone of you is able to find a working Custom ROM for A55 HD kindly post it here so that we can have a repository of successful and useless attempts. I'm sure it would help others.

Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also.
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also. All the recoveries shown in the list are only remote recoveries

nanachitang420 said:
Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also.
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also. All the recoveries shown in the list are only remote recoveries
Click to expand...
Click to collapse
I forgot to mention , rename the recovery image to "recovery.img" and then put it in root of SD card and it would get detected by MUT...It will get detected instantly...Thankyou for bringing it to notice...Just updating the post...

done but some observations!!!!
DONE.
Some observations:
1. In CWM, cant see internal SD card. While, after mounting usb storage, can see external SD card only. NOTE, CANT SEE INTERNAL SD CARD ONLY WHEN TRY TO MOUNT INTERNAL PHONE STORAGE IN CWM. WHILE NORMAL WORKING NO PROBLEM.
2. Deleted.
3. Deleted.
4. Deleted,
5. Deleted.
6. The font size of Stock and CWM recovery is very small still it can serve the purpose.
Do any body have original/stock update.zip from Company?
Updates:
I think I figured out the problem with touch. Uninstalled an application called "Go Power Master" and the touch is ok even after connecting USB or charger. Thanks man. The phone is working very nice after rooting.

nanachitang420 said:
DONE.
Some observations:
1. In CWM, cant see internal SD card. While, after mounting usb storage, can see external SD card only.
2. After rooting, before even installing CWM, got some irratic behavior with touch. Like, while USB is connected, touch was not working as expected, it took long time to make USB storage active as after touching a specific required operation, like pulling down task bar it was doing something else like opening play store, opening game, or opening date and time settings. While unlocking lock screen, it was just opening any random phone application and is not even allowing to go back with back button or home button. Don't know this is related with what?
3. Irratic application were opening while touching different application but after removing USB, things were working better.
4. Rebooted in CWM and first tried to "fix permissions" to avoid that irratic touch behavior, thinking there was problem with permissions. Took nandroid back up, after fixing permissions. Wiped cache and dalvik cache and restarted.
5. Now, till now phone is not connected to PC with USB cable or connected to charging; it behaves better with touch but it is very troublesome to perform any operation after phone connected to PC with USB or to charger.
May be you have faced these issues or may not! Any suggested solution? Do any body have original/stock update.zip from Videocon?
Updates:
I think I figured out the problem with touch. Uninstalled an application called "Go Power Master" and the touch is ok even after connecting USB or charger. Thanks man.
Click to expand...
Click to collapse
For me the touch works without any problems...and as for detecting internal sd card...that also works flawlessly..i don't have the phone with me right now...Yesterday I was trying something and the nvram got corrupted [No baseband]...so right now it is resting at service center...Hope to get it next week...
One suggestion never install Carliv Touch Recovery on this phone...it messes with the baseband and display...Stick to this recovery until I build a more updated CWM...

Latest V-Store attached
Attached

nanachitang420 said:
Attached
Click to expand...
Click to collapse
Nice...let's make this thread a repository of A55 HD..And I have also got hold of the original update.zip and files for SPFT ...Will split them and upload to my google drive...and then share them..

update.zip
Aaaaanuj1 said:
Nice...let's make this thread a repository of A55 HD..And I have also got hold of the original update.zip and files for SPFT ...Will split them and upload to my google drive...and then share them..
Click to expand...
Click to collapse
The current version of my phone is 08062013. Can I flash this latest version through CWM and upgrade?

Tried to flash update.zip through CWM...
Installing: /sdcard/update.zip
Finding update package...
Opening update package....
Installing update....
assert failed: getprop("ro.product.device")=="A55HD" || getprop("ro.build.product")=="A55HD".
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted...
Restored nandroid backup after this.

nanachitang420 said:
Installing: /sdcard/update.zip
Finding update package...
Opening update package....
Installing update....
assert failed: getprop("ro.product.device")=="A55HD" || getprop("ro.build.product")=="A55HD".
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted...
Restored nandroid backup after this.
Click to expand...
Click to collapse
Okie it is an easy fix...
Step 1.Open the update.zip with winrar, Do not extract.
Step 2.Navigate to \META-INF\com\google\android\updater-script ,use "Notepad++" to open the file.Don't use default notepad.
Step 3.delete assert(getprop("ro.product.device") == "A55HD" ||
getprop("ro.build.product") == "A55HD");
Step 4.Save the file, update to archive..Done

Done
Successful.
Please add in above step 2 "to extract file Updater-script on PC" and then use N.........
Flashed modified update.zip from CWM and phone upgraded to version 15072013. To be strange it is showing v1.0 20130715 in build ie in about phone. All the applications were intact but lost root and also CWM recovery; then managed to root the phone and flash CWM with your fantastic guide.
After booting in CWM, wiped cache and dalvik cache(why? don't know). Phone is working nice. Thanks,

nanachitang420 said:
Successful.
Please add in above step 2 "to extract file Updater-script on PC" and then use N.........
Flashed modified update.zip from CWM and phone upgraded to version 15072013. To be strange it is showing v1.0 20130715 in build ie in about phone. All the applications were intact but lost root and also CWM recovery; then managed to root the phone and flash CWM with your fantastic guide.
After booting in CWM, wiped cache and dalvik cache(why? don't know). Phone is working nice. Thanks,
Click to expand...
Click to collapse
Nice...Yeah, people at Videocon forgot to change the version number i guess...and loss of root and cwm was due to restoring of system.img and recovery.img in the ROM file...so it's normal..
Besides one should always perform a clean install from CWM..i.e. Clear Data, Clear Cache, Clear Dalvik Cache, Format /system/ and then install ROMS..
And yes this ROM is a bit better then the one on phone..I received my phone today from service center and software was updated to this ROM..It felt much better .And the version was same , so this seems to be the latest ROM for A55 HD.. Enjoy

How to flash phone with sp flash tools
was trying to flash a recovery build on CWM site. I think it has spoiled baseband. No sim is getting detected. Any idea how to flash phone with SP tool? Don't have access to service station as am very far.
Edit: Managed to flash with SP tool. Used the files you have uploaded for SPFT. Selected all options and now phone is on and showing base band version, also sim are getting detected. The issue was preloader drivers for windows 8 which managed to install by disabling driver signature verification. Device rooted and installation of CWM through MUT was successful. Thanks.
Try this and this. Its as good as custom rom installation works very well with MTK6589

nanachitang420 said:
was trying to flash a recovery build on CWM site. I think it has spoiled baseband. No sim is getting detected. Any idea how to flash phone with SP tool? Don't have access to service station as am very far.
Edit: Managed to flash with SP tool. Used the files you have uploaded for SPFT. Selected all options and now phone is on and showing base band version, also sim are getting detected. The issue was preloader drivers for windows 8 which managed to install by disabling driver signature verification. Device rooted and installation of CWM through MUT was successful. Thanks.
Try this and this. Its as good as custom rom installation works very well with MTK6589
Click to expand...
Click to collapse
You must understand that the recovery partition is of 6 mb....and most likely the recovery you received from CWM online builder was more than 6 mb..hence your secro.img was also overwritten...hence the problems with baseband and imei....same thing happened with me 7 days back when I had to submit my phone to Service center. Unfortunately i didn't had the flash image then but it is good to know that it can also recover baseband and imei. And congrats for recovering your phone and I'm glad my contribution helps you...
Just remember one thing...if the boot, recovery,secro partitions are of more than 6mb then don't flash them as they would mess one thing or other...and hopefully you had disabled preloader in SPFT.....if not then from next time onwards please do it....because rarely you need to flash preloader...and a wrong flash can make your device a brick which can only be recovered by Test points.Hence never flash preloader until unless you know what you are doing.....And yes, I already use Gravity Box along with Xposed Framework...Great mod...Besides them I also use xhalofloatingwindow with bubble launcher and lwinrecent ...Both are xposed modules and work as expected.I also have init.d support which allows to make boot persistent changes on device....Along with that a few build.prop tweaks that take my ROM to the custom level...Let me know if you need any of this...

Please
Thanks for preloader advise. was not that much aware and will take care next time. Please share init.d support, build.prop tweaks and their usefulness.

For init.d, use term-init by ryuinferno.
http://forum.xda-developers.com/showthread.php?t=1933849
This is the link to the thread. Do not use zip-init or uni-init. Follow the guide on the thread. It works flawlessly.
Sent from my A55HD using Tapatalk

Which other phones has MTK6589 and same config ?
Tell me model number and brand, i will try to upload stock firmware.
it will help us built custom rom with custom features.
@anuj - Anyways if it brick again and need to send service center, please text me imei and location, i will make it done fast for you dear.:fingers-crossed:

Thank you Pratap bro. I'll let you know next time if I get to the point where I need to go to service center but I'm sure that with the ROM you provided I wouldn't need to go to one. And yes people you can ask for stock ROM from Pratap. He has excellent connections and can get you at least the Videocon ROM and may be others . Don't forget to thank him. Besides he is an excellent person who wouldn't shy away from helping you if he can. Ciao Pratap brother.
Sent from my A55HD using Tapatalk

Any new updates from Videocon for our A55HD?

File not found
File not found bro

[Q] GT-P5113 Root problems, SuperSu binary issue. Could sure use help.

Tablet: Samsung Galaxy Tab 2 10.1 (GT-P5113) Wifi only.
OS: Android 4.2.2 Jellybean
Build#: P5113UEUCMK3
So here is what I have done:
Ran Odin v3 1.85 and pushed CF-Auto-Root-expresso10wifi-expresso10wifibby-gtp5113.tar.md5
I followed the instructions to the letter. The Odin process runs, red Android screen....tablet process runs...neither process reports errors...No Root.
When I try SuperSU I get "There is no SU binary installed...." blah blah see it all over the forums but nothing I have tried has fixed either problem. I even put the SuperSU.apk on a micro SD and it won't install over to replace the binary. SuperSU does not show up in my Applications list so I cannot remove it.
So I did hard resets, wiped cache etc..
No change.
Next I downloaded the factory ROM P5113UEUCMK3_P5113XACCND2_HOME.tar.md5 from Samsung and pushed it over successfully.
No change.
I cannot get root to take so I cannot manually remove SuperSU using a file manager (requires root)
I would really like to get my tablet rooted so i can install other apps.
Any one with information that will help me solve this will be my new hero...briefly...
Thanks in advance!

Did you check "unknown sources" in security/developer section?
Pp.

PanchoPlanet said:
Did you check "unknown sources" in security/developer section?
Pp.
Click to expand...
Click to collapse
Yes I did.

I'm having the exact same problem with my P5110.

Is anyone really gonna help here?
I have the same issue with GT-P3113.

To root or not to root?
Which one is it people? If you can't file explore because you don't have root you just delete SU from your apps (Manage apps) drawer.
Then you just go about your typical rooting, following the Op instructions and your done.
Pp.

I can only turn on and off supersu, can't delete or uninstall it.
Also despite turning it off and checking the appstore, there's no uninstall button, even when I did update it with a new apk it still won't do anything. Still says the same thing. no Binary and can't even install one.

PanchoPlanet said:
To root or not to root?
Which one is it people? If you can't file explore because you don't have root you just delete SU from your apps (Manage apps) drawer.
Then you just go about your typical rooting, following the Op instructions and your done.
Pp.
Click to expand...
Click to collapse
As I mentioned SU is not in my App manager and therefore cannot be removed. I attempted to download and install the SU apk from micro SD and it failed.
So I am stuck with no root and unable to get a file manager running to manually remove SU.

I have the same problem with my P3113

Do you have a custom recovery (CWM or TWRP) installed? If so you can download and flash the latest SuperSU.zip
Sent from my Nexus 4 using XDA Premium HD app

Well I had the exact same problem, and I think that the SuperSU included on the CF-Auto-Root file is outdated or something.
I was on android 4.2.2 but I have the Galaxy Tab 2 10.1 P5110.
I searched the forums and came up with a solution for our problem. I think that SuperSU is outdated on that CF-Auto-Root file or it was the custom recovery that it installs thats outdated or messed up for android 4.2.2, because right after it does its thing, we get the tablet default recovery again.
Since I dont know how to make a new CF-Auto-Root file, I tried to install an updated custom recovery through Odin3 instead of the CF-Auto-Root file, and it worked. Then I entered on the TWRP recovery and installed an updated SuperSU, restarted the tablet, and it worked too. I had now a rooted tablet with a permanent custom recovery, So i followed to install a custom rom, etc.
So now the steps I did:
(I am not responsible if it doesnt work for your tablet and messes something up or brick it, so please follow on your own risk, or maybe wait for some expert on this things to say if its safe or not. All i know is that it worked for me.)
Step 1: Download Stuff
Download and install samsung usb drivers
Go to Samsung website and search for your device. Go to downloads and download the USB Driver and install it.
Download Odin3 1.85_3
Go to this topic and download Odin3 3.85_3 from the "What you need:" section. Extract it on your computer.
Download TWRP recovery
Go to TWRP website, click "Get TWRP for your device", search for 5110 (doesn't have the 5113 version, and I think that the 5110 is the same and works too), scroll down to "Download - Odin Flashable Tar:" and click the "5110 only" version. It will open another page, scroll down for the most recent version and download the .tar file. Extract it on your computer.
Download SuperSU for TWRP
Go to Chainfire website and download that SuperSU version for TWRP. Dont extract, just put it on your SD card for the tablet.
Step 2: Doing stuff.
Install samsung drivers, extract Odin to your computer and put the SuperSU file on your SD card for the tablet.
(To avoid confusion about using the Volume rocker switch, I'll refer to side closest to POWER button as LEFT/Volume DOWN and side away from power switch as RIGHT/VolumeUP. )
1: Turn off the tablet and restart it on download mode. To enter download mode, press Power Button + Volume Right. When the warning appears press Volume Left to enter download mode.
2: Now open Odin3 1.85, click PDA, select the TWRP .tar file you downloaded.
3: Make sure to uncheck the "Auto Reboot" option. The only checked thing must be "F. Reset Time".
4: Connect usb cable to tablet. Press start. When it finishes, the box will turn green and says "pass!" you can remove the cable.
5: Now press Power button + Volume Left. Keep pressing it, the tablet should restart and when the samsung galaxy tab 2 screen appears, let go of the power button, but keep pressing Volume Left until the TWRP recovery screen appears.
6: Now inside TWRP recovery menu, press Install. On the top part of the screen press Storage and and change to external storage or SD card. Now select the SuperSU file and install it by swiping that thing. After it install and says successful, press reboot.
Congratulations ! Now you have successfully rooted your tablet and you have a permanent custom recovery ! You can now install a custom rom, etc.
Some notes:
I used TWRP recovery because i used it on my smartphone. So thats what I learned to use, so I used it on the tablet too. Feel free to use other custom recovery and adapt the tutorial for it.
It worked for me. If it doesn't work for you, or something is failing on some step, try to read everything again and re-do.
Credits:
* I based this on this topic and its replys (the last comment on this page.)
* Also credits for the Odin3 creator, SuperSU creator and TWRP team.
I just put together things from here and there, but without this persons, creators and stuff, we would not be able to make this happen.

Need help with TF700T with Katkiss 6.0 installed

I recently bought a second hand TF700T that has been rooted with Katkiss 6.0 but it has numerous problems that I need to know which is the best way to resolve. This is what I have:
Model: TF700T
Android Version: 6.0.1
Kernel Version: 3.1.10 katkernel-tf700
Build: Katkiss-024.6.0.1
ClockworkMod Recovery v6.0.4.7
The problems I have are:-
1. It has no Play Store and I am able to download the apk file but 'can't read/open' so it won't install from download (yes I have allowed apps from unknown sources). I managed to pull the apk file using ADB but the Play Store simply opens and closes a white page.
2. If I go to settings there is a SuperSU – clicking on it I get 'Unfortunately, settings has stopped'. I don't think this should happen. I don't know how to check if Super SU Beta 2.52 is installed.
3. If I go to Accounts I have Personal (IMAP) and + Add Account where I only have Exchange and Personal (IMAP). So I can't seem to be able to select a Google Account.
Presently I have nothing on the tablet I need (i.e. no data I need to keep) so if I have to start again I am happy to do that but I'm just learning so saying 'flash the rom' or such is too vague for me at this stage. I'm also not sure what or how to get 'data as f2fs' if that is important.
If someone could assist with a clear step by step of how I might resolve these issues I'd be very grateful. Happy to provide any other info sought. Not sure if this was caused when the seller wiped his personal data before selling or what, he says Play Store was working, so don't know if he bungled the rooting or what.

I got your PM and first of all, congrats you did a good amount of reading and you are on the right track.
Your problems with Google account and Play Store are probably due to either the wrong gapps (Google apps) version or the previous owner did a wipe of /data and did not reflash properly. Yep, arm 6.0 is right, but it has to be the pico edition. Since you did buy the tablet used, it probably would be a good idea to start from scratch. At least you would then know that if something won't work, it's because of something you did.
And yes, I agree with the advice to flash the Kang TWRP recovery. I have no idea if CWM supports f2fs but I don't think so. Most people use TWRP as recovery - it's the right way to go.
So let's get you prepped:
Download the rom, gapps and SuperSU from the links in Tim's thread (first post) and put them on a microSD. http://forum.xda-developers.com/transformer-tf700/development/rom-t3282166
Then head here and download the flashable zip of the Kang TWRP recovery: http://forum.xda-developers.com/showpost.php?p=59299365&postcount=2
Also copy that to the microSD
Boot into CWM recovery, go to Install and navigate to the Kang TWRP zip.
To tell the truth I can't even remember if CWM supports the microSD but I think it does. If it doesn't you have to use adb to push the zip to internal memory and then flash it from there.
Anyway, flash the Kang TWRP and then reboot. Let it boot up, then turn the tablet off and boot via buttons (Power and Vol Down to get into bootloader, VolUp on flashing RCK) into recovery which should be TWRP at this time.
Go to Wipe > Format data > type "Yes" and go have a beer (did I mention the battery needs to be full before you start?). This will take 60 minutes plus and may look as if nothing happens but it does, don't mess with it!
Once that is done follow this guide to convert internal data to f2fs: http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Start at step 4 and ignore any instructions related to data2sd/rom2sd.
Alright, now you got a squeaky clean tablet itching for a rom.
In TWRP go to Install > navigate to the microSD and select the rom zip. If you like, you can line up the other two files to be flashed right after the rom zip:
Touch: Add another zip, and repeat this for both the gapps and the supersu zips.
Or you flash them one by one - doesn't matter. But all 3 have to be flashed without rebooting in between and the rom has to be first!
Make sure "verify zip signature" is not checked, then swipe the button.
Have another beer
Once it's done, reboot to system and set up your new rom.
You definitely want to install the SuperSU app from the Play Store. You gain root by flashing the SuperSU zip, but you need the app to manage root.
If anything is unclear: Ask!
Have fun!

I'm up to the part where I get to have a beer...haaa. Wasn't all plain sailing. Having TWRP as an img file wasn't recognised on the sd card so I was unable to flash twrp that way. I managed to push twrp using ADB. (The small issue I had here originally was when I renamed the img file from say twrp-2.8.x.x-xxx.img to twrp.img (for ease of typing in adb) it was really twrp.img.img as it appears with a zip icon on my XP. After realising this it was straightforward after putting twrp.img into the adb folder and connecting the device and accessing the command prompt:
C:\adb>adb devices (to check I'm connected)
response:
List of devices attached
(numbers&letters here) device
C:/adb>adb reboot bootloader
This reboots the device into the bootloader and you hear the device buzz
C:/adb>fastboot flash recovery twrp.img
response
sending 'recovery' (7038kb)
Okay
writing 'recovery'
Okay
finished total time etc
then
c:/adb>fastboot reboot
rebooting....
I then used the power vol down buttons and yahoo I'm in TWRP and currently at the wipe data phase.
Can't tell you how much I appreciate this help and I'll repost a report after I get further along. Hope this helps others also.

Unexpected Clean Android waiting for a ROM
Beers were great. I finished the bit of 'convert internal data to f2fs' and thought when I rebooted, well don't know what I expected but 'squeaky clean tablet itching for a rom' wasn't a still present KatKiss rom logo start but that's what happened. Then I went to 'Install > navigate to the microSD and select the rom zip' and nothing on the SD card seemed to be recognised other than a self created 'LOST.DIR' directory so I copied the files into this directory ( Heh, at least it can see this directory). So I'm now in the process of installing KatKiss, Gapp 6 pico and SU User Beta.
If I'm on the wrong track here please let me know. Cheers
Paul;

No, you're doing good. You formatted /data, so did not touch /system where the rom lives. That's why your old room still boots. /system gets formatted during installation of the new rom = squeaky clean.
Sent from my Nexus 5X using Tapatalk

berndblb said:
No, you're doing good. You formatted /data, so did not touch /system where the rom lives. That's why your old room still boots. /system gets formatted during installation of the new rom = squeaky clean.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I've completed all the instructions - changed data to f2fs and then starting with the Katkiss, then Gapp pico and SuperSU (adding one zip after the other) and rebooted. Rebooted and device installed 73 apps and took me to a welcome screen with a language dropdown and a swipe button. I can access and change the language but the swipe button won't work so I'm locked on this screen. I went back to TWRP and pressed 'reboot' but what happened was the reboot button(located bottom right), settings button above it and the two bottom buttons on the left disappeared... so from there it wouldn't reboot. I had to hold the power button down to reboot and back in the flash screen but still can't get past that.

plato2 said:
I've completed all the instructions - changed data to f2fs and then starting with the Katkiss, then Gapp pico and SuperSU (adding one zip after the other) and rebooted. Rebooted and device installed 73 apps and took me to a welcome screen with a language dropdown and a swipe button. I can access and change the language but the swipe button won't work so I'm locked on this screen. I went back to TWRP and pressed 'reboot' but what happened was the reboot button(located bottom right), settings button above it and the two bottom buttons on the left disappeared... so from there it wouldn't reboot. I had to hold the power button down to reboot and back in the flash screen but still can't get past that.
Click to expand...
Click to collapse
Heck! I did not think we needed to check your bootloader if it had Katkiss on it, but now I think we do:
Boot into fastboot and read the tiny text top left. The part with 10.6.1...... is what we need

Bootloader problem now! More beer required....
berndblb said:
Heck! I did not think we needed to check your bootloader if it had Katkiss on it, but now I think we do:
Boot into fastboot and read the tiny text top left. The part with 10.6.1...... is what we need
Click to expand...
Click to collapse
OK, I went back to the wipe data bit and did it all again.... I noted that when installing the Katkiss, Gapps and SuperU zips I saw 2 lines:
checking for md5 file
skipping md5 check: No md5 file found
Have no idea if it matters or not....
OK the tiny writing at top on fastboot (why does this have to be so small....really).
Anyway it says:
Key Driver not found.. booting as
Android CardHU-User Bootloader <2.0 e> released by "ww_epad-10.6.1.14.10-2013601" A?3
It is hard to be exact with it that small so hope that helps, but the 10.6.1.14.10 is correct can't be as sure with the last numbers though.

Thinking about a solution
plato2 said:
OK, I went back to the wipe data bit and did it all again.... I noted that when installing the Katkiss, Gapps and SuperU zips I saw 2 lines:
checking for md5 file
skipping md5 check: No md5 file found
Have no idea if it matters or not....
OK the tiny writing at top on fastboot (why does this have to be so small....really).
Anyway it says:
Key Driver not found.. booting as
Android CardHU-User Bootloader <2.0 e> released by "ww_epad-10.6.1.14.10-2013601" A?3
It is hard to be exact with it that small so hope that helps, but the 10.6.1.14.10 is correct can't be as sure with the last numbers though.
Click to expand...
Click to collapse
I've done a bit of reading and I'm currently downloading ww_10_6_1_18_SDupdate.zip
I think my next step will be to unzip this file and find the T4_SDupdate file and put it on the sdmicro in root and boot into recovery. I'm guessing it will be located and the update begin. After that I'm not sure of what to expect. Will I have to go and flash twrp, wipe date, change to f2fs and install Katkiss,Gapps and SuperSU again? Will it matter if other files (TWRP, Katkiss, Gapps,SuperSU) are also on the microsd while this happens. If you could let me know if I'm on the right track that would be great.

plato2 said:
I've done a bit of reading and I'm currently downloading ww_10_6_1_18_SDupdate.zip
I think my next step will be to unzip this file and find the T4_SDupdate file and put it on the sdmicro in root and boot into recovery. I'm guessing it will be located and the update begin. After that I'm not sure of what to expect. Will I have to go and flash twrp, wipe date, change to f2fs and install Katkiss,Gapps and SuperSU again? Will it matter if other files (TWRP, Katkiss, Gapps,SuperSU) are also on the microsd while this happens. If you could let me know if I'm on the right track that would be great.
Click to expand...
Click to collapse
Sorry, that should be 22_10_26_1_18_SDupdate.zip

plato2 said:
Sorry, that should be 22_10_26_1_18_SDupdate.zip
Click to expand...
Click to collapse
Third time luck...(should be) ww_10_26_1_18_SDupdate.zip

plato2 said:
Third time luck...(should be) ww_10_26_1_18_SDupdate.zip
Click to expand...
Click to collapse
Don't do that!!
Whatever it is that is not firmware for the TF700!
You are on the latest bootloader, no reason to mess with it!!
---------- Post added at 09:29 AM ---------- Previous post was at 09:28 AM ----------
Give me some time, I'll get back to you
Sent from my Nexus 5X using Tapatalk

That was TF701 firmware you were thinking to flash. It is totally incompatible with your tablet and the T4 SD Update method works only with stock recovery. But all that aside....
Ok, what you experience is quite weird and I have no idea what caused it. Maybe a bad download maybe something went wrong during the flash - I have no idea...
So what is your situation now? Can you reboot from TWRP? Does the recovery work normally?
Because if not, that is the first thing you need to fix.
You may want to reflash TWRP anyway - just to be sure it did not get corrupted. You know how to flash in fastboot - excellent! Then let's do it that way.
Download from the first link for Kang TWRP 2.8.7.4. https://www.androidfilehost.com/?fid=24352994023705509
Look at the info under "Download information" on that page: You'll see the md5 checksum for that file. That is control value to make sure the file you downloaded is complete and not corrupted.
You'll need a small program like Hashtab on your PC to check the md5. Install it, then right click on a zip, go to Properties and there you'll see a new tab: FileHashes. Copy the string from the download page into the "Compare" box and it instantly tells you if the file you have on your PC matches the one on the server. TWRP has a feature that it will compare the md5 if you have it along with the zip in form of a small text file on your microSD. If it doesn't find a md5 it just skips the integrity check.
Your microSD - something else to check. That TWRP doesn't see the downloaded files unless they are in the LOST directory is totally crazy. How is that microSD formatted? You got another one you can use? One that actually works and does not add another question mark to this situation? If not, at least format the microSD to fat32 on your PC, load your files and then check if TWRP sees them. Also check the md5 AFTER copying the files to the card.....
Do that with all the files you downloaded.
So, first thing is to flash TWRP again. Then make sure it works, you can reboot from it etc.
Then just perform a quick wipe in TWRP. From Home select Wipe > swipe the button > done
Then reflash the rom zip, gapps and supersu on which you checked the md5.
Let me know how that goes.....

Thanks for that info. No I wasn't going to do anything stupid without you OKing it first.
I redownloaded Kang TWRP 2.8.7.4 and pushed it again successfully with adb no problem. I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU. Still frozen on front screen of rom. I put the twrp.img file onto the micro SD Card and tried to flash. It gives me an option to select staging which I didn't tick so it tells me no partitions selected for flashing. Didn't want to tick something and stuff it up. I think TWRP is OK as it did work fine before I installed the other 3 programs.
The micro SD is fine it's FAT32 formatted. The issue with the recovery program not seeing the zip files in the root dir was when I was using CWM - no longer a problem.

plato2 said:
Thanks for that info. No I wasn't going to do anything stupid without you OKing it first.
I redownloaded Kang TWRP 2.8.7.4 and pushed it again successfully with adb no problem. I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU. Still frozen on front screen of rom. I put the twrp.img file onto the micro SD Card and tried to flash. It gives me an option to select staging which I didn't tick so it tells me no partitions selected for flashing. Didn't want to tick something and stuff it up. I think TWRP is OK as it did work fine before I installed the other 3 programs.
The micro SD is fine it's FAT32 formatted. The issue with the recovery program not seeing the zip files in the root dir was when I was using CWM - no longer a problem.
Click to expand...
Click to collapse
There's some fundamental flaw in your thinking: You cannot flash the .img file in TWRP.
twrp_tf700t_kang_2.8.7.4.img - this file you have to flash in fastboot (fastboot flash recovery twrp_tf700t_kang_2.8.7.4.img)
twrp_tf700t_kang_2.8.7.4-signed.zip - this is the same recovery packaged into a flashable zip. This you can flash in recovery
I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU
Click to expand...
Click to collapse
You mean rebooting from recovery??? That sentence does not make sense. And something else is going on. Flashing a rom, gapps, supersu cannot have anything to do with your recovery not working properly. The recovery lives on it's own partition and boots from there.
Maybe time to take a break and retrace your steps. I cannot put my finger on it but somewhere you are doing something wrong.
Edit: Ha! Interesting! Just remembered that something changed in TWRP and yes, this latest version lets you flash an .img file to staging (from where it will get installed to it's proper partition during the next boot). I have no idea how solid this new feature is, so I'd still recommend falshing TWRP in fastboot.
But 2.8.7.4 works fine flashing Katkiss and associated files. Tried it myself this afternoon. All the components work. So the problem is most likely in the "how", not the "what".....

Sorry for the confusion. Really can't see what I may be doing wrong here. I followed exactly the same procedure as I did when I installed TWRP over CWM initially. I re-downloaded twrp_tf700t_kang_2.8.7.4.img , placed it in the adb folder and renamed it twrp.img. I then followed the same procedure I did originally:
C:\adb>adb devices (to check I'm connected)
response:
List of devices attached
(numbers&letters here) device
C:/adb>adb reboot bootloader
This reboots the device into the bootloader and you hear the device buzz
C:/adb>fastboot flash recovery twrp.img
response
sending 'recovery' (7038kb)
Okay
writing 'recovery'
Okay
finished total time etc
then
c:/adb>fastboot reboot
rebooting....
However, this time the response to the last command:
c:/adb>fastboot reboot
(waiting for device) and it hangs and the device doesn't reboot from recovery. However, all the other stuff before it is the same. Not sure what to try next.

plato2 said:
However, this time the response to the last command:
c:/adb>fastboot reboot
(waiting for device) and it hangs and the device doesn't reboot from recovery. However, all the other stuff before it is the same. Not sure what to try next.
Click to expand...
Click to collapse
Elaborate on this please.
You are in fastboot.
The command fastboot reboot does nothing?
Then what? Did you reboot manually?
You are not in recovery here, so i do not understand "the device does not reboot from recovery".....

Sorry, my lack of understanding. I suppose I mean I am in the bootloader which is where adb>reboot>bootloader puts me so that I can flash twrp.img. Then to get out of there and go back to the rom fastboot>reboot would put me back into the rom and I would get the response >rebooting. Now that doesn't happen it simply says (waiting for device)....So I have to reboot manually.

Just got home and playing around with it. I went into the bootloader and installed just the katkiss rom. It installed fine and then I clicked reboot and it rebooted no problem. But of course that doesn't give me any Play Store or SuperSU.... so there's still hope. So now I'm back in the bootloader and going to try the 3 together again and see what happens.Let you know shortly

Setup wizerd stopped - google play services stopped
plato2 said:
Just got home and playing around with it. I went into the bootloader and installed just the katkiss rom. It installed fine and then I clicked reboot and it rebooted no problem. But of course that doesn't give me any Play Store or SuperSU.... so there's still hope. So now I'm back in the bootloader and going to try the 3 together again and see what happens.Let you know shortly
Click to expand...
Click to collapse
So now when I install the katkiss, Gapps and SuperSU from TWRP and reboot I get 2 repeating messages Setup wizerd has stopped' and Google Play Services has stopped. It just goes from one to the other when I press OK....

Japanese S7 Edge SCV33/SC-02H Magisk root and other tweaks!

This thread is for Japanese s7 edge scv33 that’s being booted up with SC-02H firmware after carrier unlocking.
This guide covers/ will help you
• Install Latest available Twrp recovery (Caution: will Trip Knox!)
• Magisk Root
• Remove Japanese carrier bloatwares.
• Make the default device language to English.
• Install latest available updates via default or, will add additional useful Samsung apps (will update the device stock apps like SMS, Touch wiz launcher, AOD, Contacts, etc to latest available.
• Various tweaks like sms delivery options turned on by default, always on display turned on by default etc-etc.
Overall, this guide is to help your Japanese S7 Edge scv33/SC-02H to look more like a standard international model.
So let’s begin.
Step 1:
All required files can be downloaded from here
https://drive.google.com/open?id=1XElzbRcvlqf1CXjGK8Oiu6rmlnAvcphY
Caution. Backup all of your personal data. This process will need you to factory reset or will erase all of your data including your personal photographs, apps, videos etc.
You will also require to have a fresh piece of sd card (16 gb or more recommended) to store the twrp nandroid backup if anything goes wrong.
So, First, you will need to remove the modifications that were made to your device stock boot image. If you have flashed the modified kernel or have rooted using super-su, then, you will need to undo all the changes. You can flash the stock boot image file only but I would recommend you to flash the whole latest firmware that you can find easily over UPDATO Firmware website to start better all over again.
Here is the link to the latest SC-02H android 7.0 firmware:
http://updato.com/firmware-archive-select-model?record=AD3D69507E2D11E7963AFA163EE8F90B
Download and extract it. You will find 5 files. You can ignore the HOME……. file. Flash the 4 firmware file using latest Odin.
After flashing, let it boot up. Finish the setup wizard and turn off the device.
Step 2:
Flash the TWRP that you downloaded from here. Download Link is same as above.
https://drive.google.com/open?id=1XElzbRcvlqf1CXjGK8Oiu6rmlnAvcphY
Twrp Bug: Device will reboot to twrp recovery if you choose to power down the phone from recovery option. You will have to choose “Reboot System” from twrp menu to solve this.
After installing, boot into twrp recovery. Go to Wipe and at the bottom right, you will have option to format data. Perform a Format data process. Then, make a TWRP backup to your sd card.
I repeat. Make a backup. This will help u a lot if anything goes wrong
Step 3:
Time to install magisk.
Extract root.zip file and there you’ll see magisk.zip
Flash this magisk installer file from twrp and reboot the device.
Install the latest magisk manager app apk.
Now your device is rooted with the latest magisk available.
Step 4:
Time to remove the bloatwares.
You will need ES file manager and System app remover from playstore.
Grant super-user access to both apps. Navigate to device/system/preloadFactoryResetOnly using es file manager and delete all the contents inside that folder.
Download the apps.zip file from here
https://drive.google.com/open?id=1XElzbRcvlqf1CXjGK8Oiu6rmlnAvcphY
Extract it to your pc. Copy all the extracted apps including their folder to your device and paste it inside the same path i.e, device/system/preloadFactoryResetOnly folder.
Important: You will need to change the copied each app file permission to RW-R-R.
You do-not need to change the folder’s permission. But you will need to change the each apk’s permission one by one. Long press on the apk and then go to properties. Tick mark on (read-write, read, read).
But there will still remain some Japanese DoCoMo bloatwares. You will not be able to remove it by simply using system app remover.
So, use the system app remover app to track down the bloatware’s location by long pressing and delete it by using es file manager. Remember, only delete the bloatwares that are found in device/system/priv-app and device/system/app folders.
Caution:
You do-not need to super trim down your system in hopes for getting more internal space or whatsoever by deleting the bloatwares that you don’t know. Just delete the DoCoMo apps that you can see in the app drawers.
So be aware.
Factory reset after the above step.
Step 5:
Now comes the last part:
CSC Tweaks:
Download the 3 modified csc files from above link. Copy and replace them to path device/system/csc
Change the copied file permission to (rw-r-r).
To change the default device language and set the sms delivery option on by default, copy the Customer.xml file to your pc and edit it by using Notepad++.
Find the line as shown as in the picture below and modify as in it. Save it and replace it back to where it was from which will be device/system/csc and change its file permission again to rw-r-r.
Now turn off your device and boot into TWRP recovery. Perform a factory reset and reboot.
You will have latest apps with all the custom changes including your default language changed to English.
No need to install magisk manager apk as it is already there in the apps.zip folder.
Done!
Credit goes to all the rightful owners.
Special thanks to Mr. Buddha Tuladhar again for the phone.

Android 8.0 rom..and root/ twrp for scv33/sc-02h
Stock rom is in the link given
then flash
TWRP_3.1.1_hero2qltedcm.tar ( Wipe Data ->yes)
Boot to twrp and install:
1: no-verity-opt-encrypt-6.0.zip
2: Magisk-vXX.X.zip
Download link for all files
https://www.mediafire.com/folder/kn5cg1rolfjas/

Well done sir! thank you very much.
It would be wonderful if you can upload an odin flashable all in one file.
Appreciate your time and effort very much!

01. Flash 2017.03.07_SC02HOMU1BQC4 with Odin (upload by tienquynh93)
02. Flash 2017.04.07_1BQC4_Gobal_ManhIT.zip with Odin (upload & rebuild by ManhIT)
03. Flash 2017.03.17_TWRP_3.1.0 with Odin (AP) (Rebuild by ManhIT)
3.1 Reboot to TWRP Flash:
3.2 MaGisk to root (topjohnwu)
3.3 xPosed SDK 24 (Android 7.0) (rovo89)
This rom support multilanguage with defaulft vietnamese.
Lasest firmware: 2017.12.12_SC02HOMU1BQL3

Confused.
DariasLuc said:
01. Flash 2017.03.07_SC02HOMU1BQC4 with Odin (upload by tienquynh93)
02. Flash 2017.04.07_1BQC4_Gobal_ManhIT.zip with Odin (upload & rebuild by ManhIT)
03. Flash 2017.03.17_TWRP_3.1.0 with Odin (AP) (Rebuild by ManhIT)
3.1 Reboot to TWRP Flash:
3.2 MaGisk to root (topjohnwu)
3.3 xPosed SDK 24 (Android 7.0) (rovo89)
This rom support multilanguage with defaulft vietnamese.
Lasest firmware: 2017.12.12_SC02HOMU1BQL3
Click to expand...
Click to collapse
Is it necessary to flash 2017.03.07_SC02HOMU1BQC4 and 2017.04.07_1BQC4_Gobal_ManhIT.zip ? Or can i just simply flash the latest firmware 2017.12.12_SC02HOMU1BQL3 and root my phone?

Thank you, great job on compiling all this! It took quite a bit of study, but I understand now. Thanks again.

This root works.. but it kills NFC and Beam, Is that a known issue?
I tried this out about 15-20 different times this weekend. I was trying to get obtain root without losing NFC or Beam. (I need NFC on a daily basis).
Galaxy S7 Edge SC-02H (Docomo)
I have no problem installing TWRP. I can get root by either SuperSU or Magisk. Both kill NFC though.
I have tried so many different procedures.
1) Flash stock room (see below *) using Odin 3.12.3 and 3.12.5 (.5 works better)
As soon as installation was complete, I tested out NFC to make sure it works. It does. Then configured Developer options.
2) Then install TWRP (3.1.1 and 3.2.1) via Odin 3.12.5
3) Format then wiped (I also tried wipe without formatting)
4) Installed Magisk via TWRP. (I tried SuperSU as well)
5) Rebooted to system. I also tried Wiped cache, then reboot to system.
6) Once booted up, the first thing I did was check and see if NFC or Beem work. No.
Next I installed Magisk Manager app. I tried the one posted here. Also tried updating to the latest. And also tried installing the latest version of Magisk first.
I tested out root by using ES explorer and opening up the root directory. It worked.
I checked to see if NFC or Beam worked afterwards.. no.
7) Deleted bloatware. Followed this post's Step 5 exactly as is. Root stilled worked. NFC still didn't work.
So as much as I tried.. is it a known that NFC will not work if rooted?
* Firmwares tried:
SC02HOMU1BRG1
SC02HOMU1BRE1
SC02HOMU1BQL3
SC02HOMU1CRH5 (8.0)
SC02HOMU1BQC5 (Travis82's Nougat firmware)
SC02HOMU1BQC5 (the one posted on this thread)

Hi
audioqueso said:
This root works.. but it kills NFC and Beam, Is that a known issue?
I tried this out about 15-20 different times this weekend. I was trying to get obtain root without losing NFC or Beam. (I need NFC on a daily basis).
Galaxy S7 Edge SC-02H (Docomo)
I have no problem installing TWRP. I can get root by either SuperSU or Magisk. Both kill NFC though.
I have tried so many different procedures.
1) Flash stock room (see below *) using Odin 3.12.3 and 3.12.5 (.5 works better)
As soon as installation was complete, I tested out NFC to make sure it works. It does. Then configured Developer options.
2) Then install TWRP (3.1.1 and 3.2.1) via Odin 3.12.5
3) Format then wiped (I also tried wipe without formatting)
4) Installed Magisk via TWRP. (I tried SuperSU as well)
5) Rebooted to system. I also tried Wiped cache, then reboot to system.
6) Once booted up, the first thing I did was check and see if NFC or Beem work. No.
Next I installed Magisk Manager app. I tried the one posted here. Also tried updating to the latest. And also tried installing the latest version of Magisk first.
I tested out root by using ES explorer and opening up the root directory. It worked.
I checked to see if NFC or Beam worked afterwards.. no.
7) Deleted bloatware. Followed this post's Step 5 exactly as is. Root stilled worked. NFC still didn't work.
So as much as I tried.. is it a known that NFC will not work if rooted?
* Firmwares tried:
SC02HOMU1BRG1
SC02HOMU1BRE1
SC02HOMU1BQL3
SC02HOMU1CRH5 (8.0)
SC02HOMU1BQC5 (Travis82's Nougat firmware)
SC02HOMU1BQC5 (the one posted on this thread)
Click to expand...
Click to collapse
Hi, what Twrp Work in Android 8.0 you can Shared whith me?

3.1.1, 3.2.1 and 3.2.3
They all worked. I had originally started working with 3.1.1 and 3.2.1. However, I tried the latest 3.2.3 because I couldn't get NFC to work. I did it just to give it a try.
But all three versions that I listed had no problem installing.
Are you having trouble installing TWRP?

Yes, recovery is not remplace
Will you have a link and instructions for Android 8?

How to install TWRP on Galaxy S7 Edge (SC-02H)
TWRP Installation:
1) Download and installed Odin 3.12.5 (or the latest)
2) Turn off phone. Pressed and hold Volume Down+Home+Power at the same time to get to Download Mode. Once you see the Download Mode page, let go of the buttons. Press Volume Up to accept. (To cancel, press Volume Down )
3) Open Odin and click on AP. Load the TWRP file from your computer.
4) On the second tab of Odin, uncheck "Auto-reboot" (you need to have auto reboot disabled in order to successfully install TWRP). Press 'Start'.
5) Once the Odin status changes to a green "Pass", the installation is complete.
At this point, your phone will still be in Download Mode screen. For this step only, you will need to do two steps back to back. First, press and hold Vol.Down+Home+Power in order to get the phone out of the Download Mode screen.
As soon as the screen changes, press Volume UP+Home+Power.
You will see TWRP load.
That's it. You have successfully loaded TWRP.
From here on out, you will need to press Vol. Up+Home+Power in order to boot into TWRP. If you reflash your phone back to stock firmware using Odin, you will lose TWRP and will need to repeat these steps in order to install TWRP again.

audioqueso said:
TWRP Installation:
1) Download and installed Odin 3.12.5 (or the latest)
2) Turn off phone. Pressed and hold Volume Down+Home+Power at the same time to get to Download Mode. Once you see the Download Mode page, let go of the buttons. Press Volume Up to accept. (To cancel, press Volume Down )
3) Open Odin and click on AP. Load the TWRP file from your computer.
4) On the second tab of Odin, uncheck "Auto-reboot" (you need to have auto reboot disabled in order to successfully install TWRP). Press 'Start'.
5) Once the Odin status changes to a green "Pass", the installation is complete.
At this point, your phone will still be in Download Mode screen. For this step only, you will need to do two steps back to back. First, press and hold Vol.Down+Home+Power in order to get the phone out of the Download Mode screen.
As soon as the screen changes, press Volume UP+Home+Power.
You will see TWRP load.
That's it. You have successfully loaded TWRP.
From here on out, you will need to press Vol. Up+Home+Power in order to boot into TWRP. If you reflash your phone back to stock firmware using Odin, you will lose TWRP and will need to repeat these steps in order to install TWRP again.
Click to expand...
Click to collapse
Could you provide a link to the latest version of twrp?

Joslem said:
Could you provide a link to the latest version of twrp?
Click to expand...
Click to collapse
http://bfy.tw/KPwS

For Root SC02HOMU1CRH5
TWRP_3.1.1_hero2qltedcm.tar ( Wipe Data ->yes)
no-verity-opt-encrypt-6.0.zip
Magisk-vXX.X.zip
From: https://itok01.com/2018/09/23/root-sc-02h/

Global Rom for SCV33/SH-02H 8.0
https://drive.google.com/uc?id=1MiYK-VSYLRH_9T43sYbfgfvvKqqwRJjO&export=download
Go to Recovery and run "graphic test" > "Format Data" > ReBoot.
Install Magisk to root:
https://forum.xda-developers.com/showpost.php?p=77942910&postcount=14

DariasLuc said:
For Root SC02HOMU1CRH5
TWRP_3.1.1_hero2qltedcm.tar ( Wipe Data ->yes)
no-verity-opt-encrypt-6.0.zip
Magisk-vXX.X.zip
Click to expand...
Click to collapse
it works, thank you very much!!

S7 Edge Docomo sc-02h lost imei after factory reset
Sorry for being off topic, but please cam someone help me out in the regard that my S7 Edge Docomo sc-02h lost imei after just the factory reset. Any recommendation what i can do to get it back as my sim signals are now gone as well that means i cant make any calls or msg whatsoever.
Thanks in advance

usmann93 said:
Sorry for being off topic, but please cam someone help me out in the regard that my S7 Edge Docomo sc-02h lost imei after just the factory reset. Any recommendation what i can do to get it back as my sim signals are now gone as well that means i cant make any calls or msg whatsoever.
Thanks in advance
Click to expand...
Click to collapse
you just need working 3G sim card to fix your imei... after put 3g sim card to your phone and reboot imei will appear and you can use your normal sim again!

everyonesweird said:
This thread is for Japanese s7 edge scv33 that’s being booted up with SC-02H firmware after carrier unlocking.
I need help in order to compile all of these tweaks into an Odin flashable file so that users can simply flash it and make the changes.I would also like to add App-lock feature and international Samsung keyboard with secondary symbol in but can’t seem to make it work. So, if you are interested or have tried, please let me know.....
Click to expand...
Click to collapse
Very thank, im removed almost bloat of AU. But, what happen if i dont have CSC folder? and how to add Vietnamese laguage to SCV33 (AU) stock rom?

audioqueso said:
This root works.. but it kills NFC and Beam, Is that a known issue?
I tried this out about 15-20 different times this weekend. I was trying to get obtain root without losing NFC or Beam. (I need NFC on a daily basis).
Galaxy S7 Edge SC-02H (Docomo)
I have no problem installing TWRP. I can get root by either SuperSU or Magisk. Both kill NFC though.
I have tried so many different procedures.
1) Flash stock room (see below *) using Odin 3.12.3 and 3.12.5 (.5 works better)
As soon as installation was complete, I tested out NFC to make sure it works. It does. Then configured Developer options.
2) Then install TWRP (3.1.1 and 3.2.1) via Odin 3.12.5
3) Format then wiped (I also tried wipe without formatting)
4) Installed Magisk via TWRP. (I tried SuperSU as well)
5) Rebooted to system. I also tried Wiped cache, then reboot to system.
6) Once booted up, the first thing I did was check and see if NFC or Beem work. No.
Next I installed Magisk Manager app. I tried the one posted here. Also tried updating to the latest. And also tried installing the latest version of Magisk first.
I tested out root by using ES explorer and opening up the root directory. It worked.
I checked to see if NFC or Beam worked afterwards.. no.
7) Deleted bloatware. Followed this post's Step 5 exactly as is. Root stilled worked. NFC still didn't work.
So as much as I tried.. is it a known that NFC will not work if rooted?
* Firmwares tried:
SC02HOMU1BRG1
SC02HOMU1BRE1
SC02HOMU1BQL3
SC02HOMU1CRH5 (8.0)
SC02HOMU1BQC5 (Travis82's Nougat firmware)
SC02HOMU1BQC5 (the one posted on this thread)
Click to expand...
Click to collapse
I am also struggling about this. I think the problem only concerns TWRP or Root. However I think the problem is TWRP, because when I flash stock rom, nfc ok. Next, i flash TWRP (not root yet), nfc has been disabled now. So i think TWRP causes this problem. However, if i reflash stock recovery, everything remains unchanged, NFC is still turned off. so it is very contradictory.
Now I think of a test, after installing all (root), backing up all android. Then flash again with stock rom, check NFC. Finally, restore the backup. The goal is to completely remove the TWRP from the process but still root the device. I hope it will work. Will try if i have the time