Database Info

[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.

[GUIDE] Wiko Pulp 4G + Pulp Fab 4G Root, Custom Recovery, Xposed, Unbrick (stock ROM)

I decided to write a guide for the Wiko Pulp 4G and Pulp Fab 4G to collect all the information and resources there are to be found on them in one thread, and to help those that aren't familiar with rooting and flashing etc. This guide will cover how to root your phone, install a custom recovery (TWRP), create a nandroid backup, install SuperSU (over KingRoot/KingUser), install Xposed and the Xposed framework, and how to do a hard reset and a full reset to stock ROM. There are many different ways to do these things but I will only discuss the easiest and safest ways to do them, without the need for a computer.
Okay so the first thing we want to do is create a Nandroid backup. This is a complete backup of our phone which we can use to fix it in case we manage to screw something up. To make Nandroid backups though, we first need to have a custom recovery. I will explain how to do this with Flashify, but to use Flashify our phone needs to be rooted first. Note that you should pay attention to your phone's battery life when doing these things because your phone can get bricked if it dies while in the middle of something.
1. Rooting your phone
These phones are very easy to root using the KingoRoot app from their website, however we will not want to use the newest version of the app but a version not older than 4.9.0. I will explain why later. To get this app, google 'KingRoot 4.9.0 APK' and download the apk file straight onto your phone. Now open it, enable 'Unknown sources' (your phone will prompt you to do this if you haven't done so already), and install. Open the app and follow the instructions, and your phone will automatically get rooted.
Once it is done rooting it will show you a screen like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just ignore this screen and close the app.
2. Installing TWRP (custom recovery)
Now that our phone is rooted, we can easily install a custom recovery using Flashify. You can download 'Flashify (for root users)' from the Play Store for free. Or if for some reason you don't have access to the Play Store, just google 'Flashify APK'.
Now we need an .img file of the custom recovery we are going to install that is compatible with our phone. Two users of this forum, sebi3481 and chuppito, worked on it and produced a custom recovery file that works on both the Wiko Pulp 4G and the Wiko Pulp Fab 4G which you can download here:
https://drive.google.com/file/d/0B3qXB-4YIhwXSHBleDVwbjQzbTA/view
Be sure to thank sebi3481 and thank chuppito for their work by clicking the 'Thanks' button in the lower right corner of their post!
After downloading the img file to your phone, open Flashify, tap 'Recovery image', select 'Choose a file', and tap 'File explorer' to look for the file you just downloaded (for some reason if you select 'Downloads' instead of 'File explorer', the file will be greyed out and you won't be able to select it). Select the img file, tap 'Yup', wait for it to finish, and tap 'Reboot'. Now your phone will reboot into its new custom recovery. Swipe to Allow Modifications and you are done!
If TWRP offers you to root your phone or to install SuperSU, select no. Your phone is already rooted and we will be installing SuperSU ourselves right after creating a Nandroid backup.
3. Creating a Nandroid Backup
In TWRP (our custom recovery), first go to the Settings to uncheck 'Enable screen timeout'. This will prevent our screen from locking while it is creating a backup. Then, go to Backup, check all boxes, tap 'Select Storage' to choose where to create the Nandroid backup, and Swipe to start the backup. These backups are quite large (over 6GB) and take quite a long time (can be over 30 minutes), so choose a place where you have enough space and don't worry if it appears to have frozen, just wait it out.
Once finished, tap 'Reboot system' to reboot back into Android.
4. Installing SuperSU
If you followed this guide and rooted your phone using KingRoot, it will have installed its own superuser app called KingUser (or something along the lines). The problem with this superuser app is that it isn't compatible with every root app there is, so we will want to delete it and replace it with SuperSU. This can very easily be done using the app Super-Sume Pro which you can get in the Play Store for $5 (though if you've gotten this far you should already know how you can pirate it if you want to try it before buying).
Note that Super-Sume Pro only works if you rooted your phone with a version of KingRoot 4.9.0 or older, which is why we used KingRoot 4.9.0 in step 1, rather than the newest version from their website.
Once installed, open Super-Sume, grant it root access, press the blue button, and wait for it to finish. Once it is finished, SuperSU with automatically be opened and prompt you to update the binary. Tap Continue and then choose Normal. When it finishes installing tap Reboot, and you are done!
5. Installing Xposed
First, download and install the Xposed apk from this thread (attachment at the bottom):
http://forum.xda-developers.com/showthread.php?t=3034811
Next, download the SDK and place it anywhere on your phone or SD card:
http://dl-xda.xposed.info/framework/sdk22/arm/xposed-v86-sdk22-arm.zip
Now open Flashify, select 'Zip file', and choose the zip file you just downloaded. Select 'TWRP or Philz' (don't check any of the boxes that come up after you do), tap Yup, and choose 'Use provided'. When the flash is complete, tap reboot. Now your phone will reboot and start installing the framework which will take some time. Again, don't worry if it seems to have frozen, just wait it out. Once your phone has rebooted, you should be good to go! If somehow it did not work, try doing it again but choose 'Copy first' instead of 'Use provided'.
Remember to thank rovo89 for his work by clicking the 'Thanks' button in the lower right corner of his post!
6. Unbricking
So we messed up and somehow bricked our phone, no worries! There are multiple things we can do to unbrick it. The first thing we want to try is enter the recovery mode to either restore from a Nandroid backup, or do a factory reset. We can enter our recovery by turning off our phone (by taking out the battery and putting it back in), and then pressing and holding the 'Volume +' and 'Power' buttons. Your phone will boot up and the Wiko logo will appear, but keep on holding the buttons until the recovery screen appears. For the Pulp Fab 4G, it is possible that you have to press the power button after the Android logo appears to enter recovery.
6.1. Restoring from Nandroid backup
If you have TWRP installed and have made a Nandroid backup, simply select Restore, select the backup you want to use, and Swipe to Restore. Remember to create a backup regularly and copy it to your PC or other storage devices!
6.2. Doing a Factory Reset
In case you don't have a Nandroid backup,
TWRP: Select 'Wipe' and then Swipe to Factory Reset (do not go into Advanced Wipe).
Stock recovery: Use the physical buttons to navigate to and select 'Factory reset'.
6.3. Reinstalling the stock ROM
If you could not fix your phone using the previous methods, there's one more thing you can try, and that is reinstalling the stock ROM. You can download the ROM for your device from their website. Unlike most ROMs though, these ROMs come with a tool to install it. For this you will need a computer. As far as I know you cannot get the ROM seperately to install it in the traditional way.
Pulp 4G stock ROM:
http://world.wikomobile.com/update-891-pulp-4g
Pulp Fab 4G stock ROM:
http://world.wikomobile.com/update-902-pulp-fab-4g
Extract the files to a new folder, open the exe file, and follow the instructions.
This guide is mostly finished so I'm already posting it but I will be be adding more stuff when I get the time.

Thanks a lot, Adnihil. I'm going to buy Wiko Pulp 4G next week and your thread looks very usuful. Will root/customize it ASAP. :laugh:

my flashify freeze when a push choose a file.

Adnihil said:
I decided to write a guide for the Wiko Pulp 4G and Pulp Fab 4G to collect all the information and resources there are to be found on them in one thread, and to help those that aren't familiar with rooting and flashing etc. This guide will cover how to root your phone, install a custom recovery (TWRP), create a nandroid backup, install SuperSU (over KingRoot/KingUser), install Xposed and the Xposed framework, and how to do a hard reset and a full reset to stock ROM. There are many different ways to do these things but I will only discuss the easiest and safest ways to do them, without the need for a computer.
Okay so the first thing we want to do is create a Nandroid backup. This is a complete backup of our phone which we can use to fix it in case we manage to screw something up. To make Nandroid backups though, we first need to have a custom recovery. I will explain how to do this with Flashify, but to use Flashify our phone needs to be rooted first. Note that you should pay attention to your phone's battery life when doing these things because your phone can get bricked if it dies while in the middle of something.
1. Rooting your phone
These phones are very easy to root using the KingoRoot app from their website, however we will not want to use the newest version of the app but a version not older than 4.9.0. I will explain why later. To get this app, google 'KingRoot 4.9.0 APK' and download the apk file straight onto your phone. Now open it, enable 'Unknown sources' (your phone will prompt you to do this if you haven't done so already), and install. Open the app and follow the instructions, and your phone will automatically get rooted.
Once it is done rooting it will show you a screen like this.
Just ignore this screen and close the app.
2. Installing TWRP (custom recovery)
Now that our phone is rooted, we can easily install a custom recovery using Flashify. You can download 'Flashify (for root users)' from the Play Store for free. Or if for some reason you don't have access to the Play Store, just google 'Flashify APK'.
Now we need an .img file of the custom recovery we are going to install that is compatible with our phone. Two users of this forum, sebi3481 and chuppito, worked on it and produced a custom recovery file that works on both the Wiko Pulp 4G and the Wiko Pulp Fab 4G which you can download here:
https://drive.google.com/file/d/0B3qXB-4YIhwXSHBleDVwbjQzbTA/view
Be sure to thank sebi3481 and thank chuppito for their work by clicking the 'Thanks' button in the lower right corner of their post!
After downloading the img file to your phone, open Flashify, tap 'Recovery image', select 'Choose a file', and tap 'File explorer' to look for the file you just downloaded (for some reason if you select 'Downloads' instead of 'File explorer', the file will be greyed out and you won't be able to select it). Select the img file, tap 'Yup', wait for it to finish, and tap 'Reboot'. Now your phone will reboot into its new custom recovery. Swipe to Allow Modifications and you are done!
If TWRP offers you to root your phone or to install SuperSU, select no. Your phone is already rooted and we will be installing SuperSU ourselves right after creating a Nandroid backup.
3. Creating a Nandroid Backup
In TWRP (our custom recovery), first go to the Settings to uncheck 'Enable screen timeout'. This will prevent our screen from locking while it is creating a backup. Then, go to Backup, check all boxes, tap 'Select Storage' to choose where to create the Nandroid backup, and Swipe to start the backup. These backups are quite large (over 6GB) and take quite a long time (can be over 30 minutes), so choose a place where you have enough space and don't worry if it appears to have frozen, just wait it out.
Once finished, tap 'Reboot system' to reboot back into Android.
4. Installing SuperSU
If you followed this guide and rooted your phone using KingRoot, it will have installed its own superuser app called KingUser (or something along the lines). The problem with this superuser app is that it isn't compatible with every root app there is, so we will want to delete it and replace it with SuperSU. This can very easily be done using the app Super-Sume Pro which you can get in the Play Store for $5 (though if you've gotten this far you should already know how you can pirate it if you want to try it before buying).
Note that Super-Sume Pro only works if you rooted your phone with a version of KingRoot 4.9.0 or older, which is why we used KingRoot 4.9.0 in step 1, rather than the newest version from their website.
Once installed, open Super-Sume, grant it root access, press the blue button, and wait for it to finish. Once it is finished, SuperSU with automatically be opened and prompt you to update the binary. Tap Continue and then choose Normal. When it finishes installing tap Reboot, and you are done!
5. Installing Xposed
First, download and install the Xposed apk from this thread (attachment at the bottom):
http://forum.xda-developers.com/showthread.php?t=3034811
Next, download the SDK and place it anywhere on your phone or SD card:
http://dl-xda.xposed.info/framework/sdk22/arm/xposed-v86-sdk22-arm.zip
Now open Flashify, select 'Zip file', and choose the zip file you just downloaded. Select 'TWRP or Philz' (don't check any of the boxes that come up after you do), tap Yup, and choose 'Use provided'. When the flash is complete, tap reboot. Now your phone will reboot and start installing the framework which will take some time. Again, don't worry if it seems to have frozen, just wait it out. Once your phone has rebooted, you should be good to go! If somehow it did not work, try doing it again but choose 'Copy first' instead of 'Use provided'.
Remember to thank rovo89 for his work by clicking the 'Thanks' button in the lower right corner of his post!
6. Unbricking
So we messed up and somehow bricked our phone, no worries! There are multiple things we can do to unbrick it. The first thing we want to try is enter the recovery mode to either restore from a Nandroid backup, or do a factory reset. We can enter our recovery by turning off our phone (by taking out the battery and putting it back in), and then pressing and holding the 'Volume +' and 'Power' buttons. Your phone will boot up and the Wiko logo will appear, but keep on holding the buttons until the recovery screen appears. For the Pulp Fab 4G, it is possible that you have to press the power button after the Android logo appears to enter recovery.
6.1. Restoring from Nandroid backup
If you have TWRP installed and have made a Nandroid backup, simply select Restore, select the backup you want to use, and Swipe to Restore. Remember to create a backup regularly and copy it to your PC or other storage devices!
6.2. Doing a Factory Reset
In case you don't have a Nandroid backup,
TWRP: Select 'Wipe' and then Swipe to Factory Reset (do not go into Advanced Wipe).
Stock recovery: Use the physical buttons to navigate to and select 'Factory reset'.
6.3. Reinstalling the stock ROM
If you could not fix your phone using the previous methods, there's one more thing you can try, and that is reinstalling the stock ROM. You can download the ROM for your device from their website. Unlike most ROMs though, these ROMs come with a tool to install it. For this you will need a computer. As far as I know you cannot get the ROM seperately to install it in the traditional way.
Pulp 4G stock ROM:
http://world.wikomobile.com/update-891-pulp-4g
Pulp Fab 4G stock ROM:
http://world.wikomobile.com/update-902-pulp-fab-4g
Extract the files to a new folder, open the exe file, and follow the instructions.
This guide is mostly finished so I'm already posting it but I will be be adding more stuff when I get the time.
Click to expand...
Click to collapse
>>> YAHOOOOO THANKS for who made this twrp recovery WORK for WikoPulp Fab 4G it.s working very good ! folow the steps from this topic exactly and it"s done! Thank you XDA and thank you SEBI3841 and chuppito great job there!:good::good:

when I arrived to swipe to allow modifications, the touch on twrp doesn't seem to work ... the only thing I can do is rebooting .... I managed to touch inside the twrp .. it seems a problem of not correspondancy of button and touch position .. now I've to put inside a 32 gb sd card to make the backup of the phone. without nothing on it should not take so long ..
Reinstalled the stock rom .. kingroot doesn't root my wiko pulp any more ... don't understand why ...

Adnihil said:
I decided to write a guide for the Wiko Pulp 4G and Pulp Fab 4G to collect all the information and resources there are to be found on them in one thread, and to help those that aren't familiar with rooting and flashing etc. This guide will cover how to root your phone, install a custom recovery (TWRP), create a nandroid backup, install SuperSU (over KingRoot/KingUser), install Xposed and the Xposed framework, and how to do a hard reset and a full reset to stock ROM. There are many different ways to do these things but I will only discuss the easiest and safest ways to do them, without the need for a computer.
Okay so the first thing we want to do is create a Nandroid backup. This is a complete backup of our phone which we can use to fix it in case we manage to screw something up. To make Nandroid backups though, we first need to have a custom recovery. I will explain how to do this with Flashify, but to use Flashify our phone needs to be rooted first. Note that you should pay attention to your phone's battery life when doing these things because your phone can get bricked if it dies while in the middle of something.
1. Rooting your phone
These phones are very easy to root using the KingoRoot app from their website, however we will not want to use the newest version of the app but a version not older than 4.9.0. I will explain why later. To get this app, google 'KingRoot 4.9.0 APK' and download the apk file straight onto your phone. Now open it, enable 'Unknown sources' (your phone will prompt you to do this if you haven't done so already), and install. Open the app and follow the instructions, and your phone will automatically get rooted.
Once it is done rooting it will show you a screen like this.
Just ignore this screen and close the app.
2. Installing TWRP (custom recovery)
Now that our phone is rooted, we can easily install a custom recovery using Flashify. You can download 'Flashify (for root users)' from the Play Store for free. Or if for some reason you don't have access to the Play Store, just google 'Flashify APK'.
Now we need an .img file of the custom recovery we are going to install that is compatible with our phone. Two users of this forum, sebi3481 and chuppito, worked on it and produced a custom recovery file that works on both the Wiko Pulp 4G and the Wiko Pulp Fab 4G which you can download here:
https://drive.google.com/file/d/0B3qXB-4YIhwXSHBleDVwbjQzbTA/view
Be sure to thank sebi3481 and thank chuppito for their work by clicking the 'Thanks' button in the lower right corner of their post!
After downloading the img file to your phone, open Flashify, tap 'Recovery image', select 'Choose a file', and tap 'File explorer' to look for the file you just downloaded (for some reason if you select 'Downloads' instead of 'File explorer', the file will be greyed out and you won't be able to select it). Select the img file, tap 'Yup', wait for it to finish, and tap 'Reboot'. Now your phone will reboot into its new custom recovery. Swipe to Allow Modifications and you are done!
If TWRP offers you to root your phone or to install SuperSU, select no. Your phone is already rooted and we will be installing SuperSU ourselves right after creating a Nandroid backup.
3. Creating a Nandroid Backup
In TWRP (our custom recovery), first go to the Settings to uncheck 'Enable screen timeout'. This will prevent our screen from locking while it is creating a backup. Then, go to Backup, check all boxes, tap 'Select Storage' to choose where to create the Nandroid backup, and Swipe to start the backup. These backups are quite large (over 6GB) and take quite a long time (can be over 30 minutes), so choose a place where you have enough space and don't worry if it appears to have frozen, just wait it out.
Once finished, tap 'Reboot system' to reboot back into Android.
4. Installing SuperSU
If you followed this guide and rooted your phone using KingRoot, it will have installed its own superuser app called KingUser (or something along the lines). The problem with this superuser app is that it isn't compatible with every root app there is, so we will want to delete it and replace it with SuperSU. This can very easily be done using the app Super-Sume Pro which you can get in the Play Store for $5 (though if you've gotten this far you should already know how you can pirate it if you want to try it before buying).
Note that Super-Sume Pro only works if you rooted your phone with a version of KingRoot 4.9.0 or older, which is why we used KingRoot 4.9.0 in step 1, rather than the newest version from their website.
Once installed, open Super-Sume, grant it root access, press the blue button, and wait for it to finish. Once it is finished, SuperSU with automatically be opened and prompt you to update the binary. Tap Continue and then choose Normal. When it finishes installing tap Reboot, and you are done!
5. Installing Xposed
First, download and install the Xposed apk from this thread (attachment at the bottom):
http://forum.xda-developers.com/showthread.php?t=3034811
Next, download the SDK and place it anywhere on your phone or SD card:
http://dl-xda.xposed.info/framework/sdk22/arm/xposed-v86-sdk22-arm.zip
Now open Flashify, select 'Zip file', and choose the zip file you just downloaded. Select 'TWRP or Philz' (don't check any of the boxes that come up after you do), tap Yup, and choose 'Use provided'. When the flash is complete, tap reboot. Now your phone will reboot and start installing the framework which will take some time. Again, don't worry if it seems to have frozen, just wait it out. Once your phone has rebooted, you should be good to go! If somehow it did not work, try doing it again but choose 'Copy first' instead of 'Use provided'.
Remember to thank rovo89 for his work by clicking the 'Thanks' button in the lower right corner of his post!
6. Unbricking
So we messed up and somehow bricked our phone, no worries! There are multiple things we can do to unbrick it. The first thing we want to try is enter the recovery mode to either restore from a Nandroid backup, or do a factory reset. We can enter our recovery by turning off our phone (by taking out the battery and putting it back in), and then pressing and holding the 'Volume +' and 'Power' buttons. Your phone will boot up and the Wiko logo will appear, but keep on holding the buttons until the recovery screen appears. For the Pulp Fab 4G, it is possible that you have to press the power button after the Android logo appears to enter recovery.
6.1. Restoring from Nandroid backup
If you have TWRP installed and have made a Nandroid backup, simply select Restore, select the backup you want to use, and Swipe to Restore. Remember to create a backup regularly and copy it to your PC or other storage devices!
6.2. Doing a Factory Reset
In case you don't have a Nandroid backup,
TWRP: Select 'Wipe' and then Swipe to Factory Reset (do not go into Advanced Wipe).
Stock recovery: Use the physical buttons to navigate to and select 'Factory reset'.
6.3. Reinstalling the stock ROM
If you could not fix your phone using the previous methods, there's one more thing you can try, and that is reinstalling the stock ROM. You can download the ROM for your device from their website. Unlike most ROMs though, these ROMs come with a tool to install it. For this you will need a computer. As far as I know you cannot get the ROM seperately to install it in the traditional way.
Pulp 4G stock ROM:
http://world.wikomobile.com/update-891-pulp-4g
Pulp Fab 4G stock ROM:
http://world.wikomobile.com/update-902-pulp-fab-4g
Extract the files to a new folder, open the exe file, and follow the instructions.
This guide is mostly finished so I'm already posting it but I will be be adding more stuff when I get the time.
Click to expand...
Click to collapse
Thank you friend. You helped me a lot. I had rooted my Pulp Fab 4G before and was able to flash TWRP and add Xposed Framework thanks to your post. I appreciate your post. I wish you all the best. Greetings[emoji106]
Sent from my PULP FAB 4G using XDA-Developers mobile app

thanks, this helped a lot

Hello,
Will this work on Wiko Pulp Fab 3G?

Hello, I bricked a Wiko Pulp 4G with kingo root.
My PC OS is Windows 10 64 bits.
I do not manage to install the drivers included by Wiko with the stock ROM.
Does someone have a file to put on a sdcard to flash it with the stock recovery (update from sd card option) ?
I can't see another way to fix this problem, maybe you can help me ?
Thanks,
Sebastien
--- Edit ----
It's ok i managed to flash it with a Windows XP...
Thanks for your guide i should have read it before trying to root my phone...

i need a new rom
good morning i don't understand why wiko pulp fab 4g doesn't support andorid 6.0. ( the compoments are very good) i need a custom rom, please help me!

sebaudry said:
Hello, I bricked a Wiko Pulp 4G with kingo root.
My PC OS is Windows 10 64 bits.
I do not manage to install the drivers included by Wiko with the stock ROM.
Does someone have a file to put on a sdcard to flash it with the stock recovery (update from sd card option) ?
I can't see another way to fix this problem, maybe you can help me ?
Thanks,
Sebastien
--- Edit ----
It's ok i managed to flash it with a Windows XP...
Thanks for your guide i should have read it before trying to root my phone...
Click to expand...
Click to collapse
I had some peculiar issue's with WIKO's flash software too.
It repeatedly failed at 94%
Then I was like "wtf, I'm going to check what it has done up to those 94% and if the system boots, I'll reflash it from there."
Turns out, failing at 94%, there was actually nothing missing from the firmware, it was 100$ perfectly installed.

Recovery mode don't work
Hello
I bricked my phone (Wiko pulp 4g), my recovery mode or fastboot mode won't open from any way, it just crashes and reboot the phone when I try to enter on recovery mode. (All the phone still work, the only thing that don't work is reading SIM cards).
What can I do? I already tried to install stock rom but my wiko program on pc don't want to download and inject the rom on android.

Sorry for the late reply.
Is your issue with loading fastload when you try to do it at boot (open bootloader trough button combination at powerup?)
Can you trigger fastload trough ADB instead?

Just to know: I'm not very used to Android, so I don't know how things work. The Pulp Fab 4g is not having, so far, an official 6 or 7 android upgrade, is it possible to install a custom ROM? I can't find any information on this...
Sorry if it's a stupid question, but I have no knowledge on Android!

What if i only do the kingroot thing?
I just want to root my phone... why would i want to do all those tings if with kingroot allready is rooted?

removed

Adnihil said:
I decided to write a guide for the Wiko Pulp 4G and Pulp Fab 4G to collect all the information and resources there are to be found on them in one thread, and to help those that aren't familiar with rooting and flashing etc. This guide will cover how to root your phone, install a custom recovery (TWRP), create a nandroid backup, install SuperSU (over KingRoot/KingUser), install Xposed and the Xposed framework, and how to do a hard reset and a full reset to stock ROM. There are many different ways to do these things but I will only discuss the easiest and safest ways to do them, without the need for a computer.
Okay so the first thing we want to do is create a Nandroid backup. This is a complete backup of our phone which we can use to fix it in case we manage to screw something up. To make Nandroid backups though, we first need to have a custom recovery. I will explain how to do this with Flashify, but to use Flashify our phone needs to be rooted first. Note that you should pay attention to your phone's battery life when doing these things because your phone can get bricked if it dies while in the middle of something.
1. Rooting your phone
These phones are very easy to root using the KingoRoot app from their website, however we will not want to use the newest version of the app but a version not older than 4.9.0. I will explain why later. To get this app, google 'KingRoot 4.9.0 APK' and download the apk file straight onto your phone. Now open it, enable 'Unknown sources' (your phone will prompt you to do this if you haven't done so already), and install. Open the app and follow the instructions, and your phone will automatically get rooted.
Once it is done rooting it will show you a screen like this.
Just ignore this screen and close the app.
2. Installing TWRP (custom recovery)
Now that our phone is rooted, we can easily install a custom recovery using Flashify. You can download 'Flashify (for root users)' from the Play Store for free. Or if for some reason you don't have access to the Play Store, just google 'Flashify APK'.
Now we need an .img file of the custom recovery we are going to install that is compatible with our phone. Two users of this forum, sebi3481 and chuppito, worked on it and produced a custom recovery file that works on both the Wiko Pulp 4G and the Wiko Pulp Fab 4G which you can download here:
https://drive.google.com/file/d/0B3qXB-4YIhwXSHBleDVwbjQzbTA/view
Be sure to thank sebi3481 and thank chuppito for their work by clicking the 'Thanks' button in the lower right corner of their post!
After downloading the img file to your phone, open Flashify, tap 'Recovery image', select 'Choose a file', and tap 'File explorer' to look for the file you just downloaded (for some reason if you select 'Downloads' instead of 'File explorer', the file will be greyed out and you won't be able to select it). Select the img file, tap 'Yup', wait for it to finish, and tap 'Reboot'. Now your phone will reboot into its new custom recovery. Swipe to Allow Modifications and you are done!
If TWRP offers you to root your phone or to install SuperSU, select no. Your phone is already rooted and we will be installing SuperSU ourselves right after creating a Nandroid backup.
3. Creating a Nandroid Backup
In TWRP (our custom recovery), first go to the Settings to uncheck 'Enable screen timeout'. This will prevent our screen from locking while it is creating a backup. Then, go to Backup, check all boxes, tap 'Select Storage' to choose where to create the Nandroid backup, and Swipe to start the backup. These backups are quite large (over 6GB) and take quite a long time (can be over 30 minutes), so choose a place where you have enough space and don't worry if it appears to have frozen, just wait it out.
Once finished, tap 'Reboot system' to reboot back into Android.
4. Installing SuperSU
If you followed this guide and rooted your phone using KingRoot, it will have installed its own superuser app called KingUser (or something along the lines). The problem with this superuser app is that it isn't compatible with every root app there is, so we will want to delete it and replace it with SuperSU. This can very easily be done using the app Super-Sume Pro which you can get in the Play Store for $5(though if you've gotten this far you should already know how you can pirate it if you want to try it before buying).
Note that Super-Sume Pro only works if you rooted your phone with a version of KingRoot 4.9.0 or older, which is why we used KingRoot 4.9.0 in step 1, rather than the newest version from their website.
Once installed, open Super-Sume, grant it root access, press the blue button, and wait for it to finish. Once it is finished, SuperSU with automatically be opened and prompt you to update the binary. Tap Continue and then choose Normal. When it finishes installing tap Reboot, and you are done!
5. Installing Xposed
First, download and install the Xposed apk from this thread (attachment at the bottom):
http://forum.xda-developers.com/showthread.php?t=3034811
Next, download the SDK and place it anywhere on your phone or SD card:
http://dl-xda.xposed.info/framework/sdk22/arm/xposed-v86-sdk22-arm.zip
Now open Flashify, select 'Zip file', and choose the zip file you just downloaded. Select 'TWRP or Philz' (don't check any of the boxes that come up after you do), tap Yup, and choose 'Use provided'. When the flash is complete, tap reboot. Now your phone will reboot and start installing the framework which will take some time. Again, don't worry if it seems to have frozen, just wait it out. Once your phone has rebooted, you should be good to go! If somehow it did not work, try doing it again but choose 'Copy first' instead of 'Use provided'.
Remember to thank rovo89 for his work by clicking the 'Thanks' button in the lower right corner of his post!
6. Unbricking
So we messed up and somehow bricked our phone, no worries! There are multiple things we can do to unbrick it. The first thing we want to try is enter the recovery mode to either restore from a Nandroid backup, or do a factory reset. We can enter our recovery by turning off our phone (by taking out the battery and putting it back in), and then pressing and holding the 'Volume +' and 'Power' buttons. Your phone will boot up and the Wiko logo will appear, but keep on holding the buttons until the recovery screen appears. For the Pulp Fab 4G, it is possible that you have to press the power button after the Android logo appears to enter recovery.
6.1. Restoring from Nandroid backup
If you have TWRP installed and have made a Nandroid backup, simply select Restore, select the backup you want to use, and Swipe to Restore. Remember to create a backup regularly and copy it to your PC or other storage devices!
6.2. Doing a Factory Reset
In case you don't have a Nandroid backup,
TWRP: Select 'Wipe' and then Swipe to Factory Reset (do not go into Advanced Wipe).
Stock recovery: Use the physical buttons to navigate to and select 'Factory reset'.
6.3. Reinstalling the stock ROM
If you could not fix your phone using the previous methods, there's one more thing you can try, and that is reinstalling the stock ROM. You can download the ROM for your device from their website. Unlike most ROMs though, these ROMs come with a tool to install it. For this you will need a computer. As far as I know you cannot get the ROM seperately to install it in the traditional way.
Pulp 4G stock ROM:
http://world.wikomobile.com/update-891-pulp-4g
Pulp Fab 4G stock ROM:
http://world.wikomobile.com/update-902-pulp-fab-4g
Extract the files to a new folder, open the exe file, and follow the instructions.
This guide is mostly finished so I'm already posting it but I will be be adding more stuff when I get the time.
Click to expand...
Click to collapse
______________________
Hello guys
1000 x Tanks for your job !
I have a little bug with the recovery (twrp) : part of the screen does not work (maybe size are not correct) Can you help me ?
And sorry for my clusmy english ...:angel:

Hello everyone, sorry I'm only getting back to you all now, I got really busy for apparently way longer than I thought! For your questions, I'm afraid that by now I've forgotten basically everything I knew about rooting this phone so I'm as clueless as you are... But I'll (try to) look into it!

Hi,
Sorry to bother you guys...Just wanted to let you know that the link for twrp recovery is not working ( the file might have been deleted). Is it possible to upload it again?
Thanks.

anyone has It? twrp (img) recovery file of Wiko pulp 4g?
PLEASE Respond I can't find it anywhere!! I even searched in Google

Blu studio xl2

This how you unlock bootloader.
Read all before doing anything!
Yes.
Backup all your ect unlocking bootloader will erase all your data.
1 first you will need to USB drivers including adb usb driver.
After that download minimal adb and fastboot.
Make sure you enable debuging and oem unlock in developer's settings.
Download inteladroiddrv.setup.
After you set this up test run "adb devices"
2. Download the twrp that I link in thread.
3.extract recovery .img to minimal directory.
4.open minimal app and run adb reboot bootloader.
5. Run fastboot oem unlock.
6.follow instructions and unlock bootloader.
7.next wait until process is over then it will reboot.
8. After reboot go settings about device go to build tap a bunch of times to reable
Developer's setting enable debugging.
9. Next go to minimal app run adb reboot bootloader your know in fastboot run fastboot boot recovery.img.
10 this will boot recovery then flash root.zip.
11. After that I recommend you do backup and yes it is big after done you can move it to your PC.
Do flash recovery permit touch doesn't work.
https://www.mediafire.com/file/d3h8cnouw8fih6s/android_cdc_driver.zip
Sent from my Studio XL 2 using xda premium
https://www.mediafire.com/file/s4aidnkyacpidjq/latest_usb_driver_windows.zip
https://www.mediafire.com/file/q7nt7xko0f653o4/IntelAndroidDrvSetup1.10.0.zip

skritch said:
I am very interested in rooting the Blu Studio XL2. Can you let me know how you accomplished it?
Click to expand...
Click to collapse
You need to get adb drivers.
Go to settings about device then tap many times on build then go to development settings enable debugging.
You need to unlock bootloader.
Make sure you backup your apps etc.
Unlocking bootloader will wipe user data.
After all USB stuff is in installed.
Adb reboot bootloader this will take you to fastboot next put fastboot oem unlock.
On your phone it will give a choice to unlock bootloader volume up unlocks volume down will keep it locked.
Just pressure you this is not hard to do.
I have two work able recoveries at the time they can bootloop you if you install I was told so here is my solution to this.
Adb reboot bootloader then do this fastboot boot recovery img.
Works like a charm after recovery boots up do a backup.
I will try to drop some links to recoveries for you.
You will likely need to install USB drivers manually local disc c/ programs go into like Intel Android Device USB driver.
This should take care of adb and fastboot problems.
https://www.mediafire.com/file/zy47tm55qr76fc4/SR3-SuperSU-v2.79-SR3-20170114223742.zip
https://www.mediafire.com/file/0ckf...XL+2+-+S0270UU_V08+-+MT6737+-+by+lopestom.zip
https://www.mediafire.com/file/jgpx...XL+2+-+S0270UU_V08+-+MT6737+-+by+lopestom.zip
https://www.mediafire.com/file/do0v472pgcxu3s0/minimal_adb_fastboot_v1.4_setup.exe
I f you need help pm me
I will being posting proof of root also.
Update twrp can be flashed on but no touch.
The garlic touch recovery can be flashed and it works.
Twrp can used only temporary by fastboot boot recovery.img.
Update the other recovery can't find SD card don't use it.
Sent from my Studio XL 2 using xda premium
Sent from my Studio XL 2 using xda premium

This works and is easy as hell. You can also install Magisk 14 install zip if so inclined. Instead of the SR3 SuperSU zip. I did because I wanted a properly working for all modules (mainly luckypatcher) Xposed. Normal Xposed v87 SDK 23 doesn't work. All modules report they are not activated when they are. I, after a couple hours dining and trying many things found out that the SR3 SuperSU zip I flashed coupled with BusyBox install on this phone, which has toybox caused and will cause many apps needing root and BusyBox to not work, re, adaway, Xposed official, Rom Toolbox, Luckypatcher and more. So I used my untouched, Ie, non rooted nandroid backup to restore too, rebooted and installed the Xposed Installer that the Magisk module recommend (been through the Magisk/Xposed rodeo many times) and back to fastboot for the cmd "fastboot boot recovery.img"
Flashed the downloaded Magisk v14 zip, reboot again and fastboot twrp boot to lastly install Xposed.v87.3_Sdk23_sytemless.zip.......
Every time I tried installing within Magisk Manager. I could not get it to work even though Magisk Manager reported all was ok and no errors. But zip Flash Xposed via TWRP does. Safteynet will fail but the Xposed Installer has a toggle for on off as well as a recovery disabler zip so one can toggle reboot and it passes or flash the disabler zip instead of uninstalling the framework.

im reading all this info but im still confused. is it possible for someone to make a video tutorial on how this is all done please??

Things are not going real great with this install. First of all I used a package called MTK USB Driver2014 which had an exe file named DPInst64.exe which I assumed was a good idea for my Win 7 64 bit. I got a message screen saying Google and two different groups of Media Tek usbser drivers with various ports defined are ready to use. I went through the routine then as was outlined in the first post. First I got USB debugging enabled on the phone after going through the initial user setup (this is a new phone). Then I set on the unlock option to on as well as usbdebuggin. Then I ran "adb devices" and got nothing. A couple of unplugs and replugs of the USB to the phone showed a USB driver installing. One stated it installed OK and the Media Tek failed. I ran another "adb devices" and saw the device listed, so I decided to continue.
The "fastboot oem unlock" went well and finished in a few seconds. Then the XL 2 screen showed text in tiny, tiny white on black with 3 options to choose. the default was on the reboot option and said to push volume up to select another or volume down to select the one defaulted. I pushed volume down and nothing happened. The device appeared locked. Would not respond to volume + power button or any other controls. I waited a half hour. So I looked online and it said this happens but to reboot it. I couldn't figure out how. So after more research I found that entering "fastboot reboot-bootloader" followed by "fastboot continue" would cause the phone to go back into normal mode where I once again reconfigured the phone from scratch and enabled Developer tool USB debugging.
Now I finished configuring again and the USB drivers started auto installing again and I got the MTK error on the driver install. I had to unplug the USB and replug and enter "adb devices" and at this point the phone asked for approval and I selected always from this computer. All is well so with the TWRP renamed to recovery.img in the adb program directory I entered "fastboot boot recovery.img" and the TWRP menu came up. I didn't back up because I don't have a SD card large enough and since I can't see any files from when I connect the USB cable, I wasn't sure how to download the backup image once it is stored on the phone. So at this point I selected the TWRP menu option to acomplete the install where future use of TWRP would not be read-only (forgot the exact wording, there was a slide to the right on the bottom of the screen to accept write mode).
Now I rebooted the phone by pressing the up button of the volume and the power button at once and I am still taken to the same green on black text that I saw before on the BLU "recovery menu" (without an obvious method to select TWRP). Is this something to be expected, that the TWRP menu is only available to boot via the PC using adb and fastboot or should the TWRP image somehow remained on my phone?
Thanks!
---------- Post added at 08:21 PM ---------- Previous post was at 08:07 PM ----------
Flex_or_fleece said:
This works and is easy as hell. .
Click to expand...
Click to collapse
Not so much for me LOL.
Can you tell me just how to install root, xposed and xprivacyLua on my phone? Would really be appreciative.
See above for how far I have gotten into the process. Not looking for a different image. This is only the second time I have working on this depth of changes. Again, thank you.

I have been working on this now for 2 full days. I managed to install Magisk 16.0 using TWRP, then without understanding or thinking this was old information, I selected Xposed from Magisk (installed from Magisk before I ready about needing to install it from TWRP) and all appeared to be well. I enabled Xposed and added XprivacyLua and enabled it via the Xposed module page. Everything appeared to be setup properly but Xprivacy said it wasn't installed and a log sent to the developer proved that it was not installed (even though the check box in Xposed said so.)
So after reading the posts above, I elected to remove Xposed via Magisk and install the Magisk version of Xposed (xposed-v89.2-sdk23-topjohnwu.zip) via TWRP. Got everything installed again and same results, everything showed the check boxes marked and therefore active but XprivacyLua would not work).
Now reading above about problems with Busybox, I decided to install Busybox and then the busybox binaries via TWRP, downloaded from this location. https://forum.xda-developers.com/an...zip-busybox-v1-26-2-flashable-binary-t3581875
Now after doing that, I am hung up when trying to open Magisk. It is a solid green screen now. Tired re-installing both the zip via TWRP and the apk and have the same results. I assume I am going to have to restore. This is all new to me and I did not make a backup image because I don't have a SD card where I am working on this. All I can find is a factrory image on Needrom website: BLU_S0270UU_V6.0.04.02_GENERIC_20180203.rar
Can anyone point me to a guide that explains in elementary (as possible) terms how to get this ROM onto my phone and with it restored with the factory image? THANK YOU!!!!!

Flex_or_fleece;73955523 my untouched said:
Hi, is there anyway you would be willing to share this backup? Thank you!. I live in a small town with no computer shops and I did not have a SD card to back up to. Thank you.
Click to expand...
Click to collapse

I am struggling with everything including lack of mini SD card while residing at the moment far away from a computer store, a USB cord that is flaky as the snow, and a bricked phone because I wrongly read in a prior post that installing Busybox was a way to resolve the issue of Xposed showing it was installed and working when it was not.
Now can anyone suggest a link that shows how to flash the ROM I found online at NeedROM: BLU_S0270UU_V6.0.04.02_GENERIC_20180203.rar to this phone? I am not an expert at this, having rooted only a few phones over the years where I wanted Xprivacy and mostly just entered a few commands to make it happen. Today its getting too complicated.
I don't know if this phone even works with the SP flash tool, and if it does the drivers I have found to attempt it are not working.
Any help would be appreciated. THANKS!

Donphillipe said:
I am struggling with everything including lack of mini SD card while residing at the moment far away from a computer store, a USB cord that is flaky as the snow, and a bricked phone because I wrongly read in a prior post that installing Busybox was a way to resolve the issue of Xposed showing it was installed and working when it was not.
Now can anyone suggest a link that shows how to flash the ROM I found online at NeedROM: BLU_S0270UU_V6.0.04.02_GENERIC_20180203.rar to this phone? I am not an expert at this, having rooted only a few phones over the years where I wanted Xprivacy and mostly just entered a few commands to make it happen. Today its getting too complicated.
I don't know if this phone even works with the SP flash tool, and if it does the drivers I have found to attempt it are not working.
Any help would be appreciated. THANKS!
Click to expand...
Click to collapse
Hello! Been through the same thing.
It is compatible with SP flash tool. Think about it: in the factory all phones come empty so there must be something to flash them. In case of Mediatek-based devices, it's SP Flash Tool.
And yeah, your drivers are broken. First of all, uninstall them. Can't tell exactly how because I don't know what you installed but you can try the programs list and the device manager.
After removing them, download mediatek-drivers.zip and extract it.
Now follow this carefully:
1) Go to device manager and click on Universal Serial Bus controllers.
2) Then go to Action >> Add legacy hardware.
3) Select Install the hardware that I manually select from a list (Advanced).
4) In the hardware types, select Show All Devices.
5) Click on Have Disk... >> Browse, browse to where you extracted the drivers, go to mediatek-drivers/Win7/ and select usb2ser_Win764.inf or usb2ser_Win7.inf if your system is 64 or 32 bits arch respectivelly.
6) Click Open and OK.
7) Select MediaTek DA USB VCOM PORT, then just Next everything.
Now repeat every step above but in step 7 select MediaTek PreLoader USB VCOM Port.
Your drivers should be installed by now.
Now if you haven't done it yet, download it here. Run it, go to Download and in Scatter-loading File, choose the MT6737M_Android_scatter.txt file that (hopefully) came with your ROM. If it didn't download it here and place it in the same folder as the .img files that came with your ROM.
If it shows all checkboxes marked, just mark system, boot and recovery. It's a soft brick, you don't need a full reflash. If it doesn't but has system boot and recovery it's fine too. Hit download. Now, with your phone turned off, hold the VolDown key and plug it in. It will start flashing.
A popup will appear when it's done. That's it! Unplug and restart it. Should be back from the dead now.
The TWRP build you are using can only be booted via fastboot but not installed. If you flash it, the touchscreen will not work nor power buttons so you can't select anything. However I found a working flashable TWRP build: TWRP 3.1.1 built by Vampirefo
This one has the touchscreen working so you can permanently flash it on your device. It's very important to have a working recovery on your device that can reboot to bootloader because Power+VolDown actually boots in some kind of hardware test mode on this phone. Basically, if you softbricked your system, no working recovery=no bootloader=no temp recovery. And it's way easier to just restore your backup if you brick your phone.
Also, you can flash it througt SP Flash Tool. Rename it to recovery.img and go for it.
Can you reply or PM me with the rom you found? Mine is really old and I always have to wait for OTA...
Also, if you have any progress with Xposed, please share couldn't get it working properly here. Not a single module works...
Tried installing it the regular way with SuperSU and Magisk and tried the systemless install within and out of Magisk. None worked so far.
Thank you!

Mark42XLII said:
Hello! Been through the same thing.
Can you reply or PM me with the rom you found? Mine is really old and I always have to wait for OTA...
Also, if you have any progress with Xposed, please share couldn't get it working properly here. Not a single module works...
Tried installing it the regular way with SuperSU and Magisk and tried the systemless install within and out of Magisk. None worked so far.
Thank you!
Click to expand...
Click to collapse
I got the ROM from needrom.com you have to create an account, then just search on Blu studio xl and scroll down to pull the 2 version. Restored using SP Flash tool with non problem.
This whole thing is really frustrating. Get Magisk installed via TWRP, then to load Xposed Framework, you have to load Xposed via TWRP and then if you follow comments here from Flex_or_fleeceand his mini guide for downloading from Magisk with download only and not an install, you get the universal Xposed Systemless zip that is supposed to be able to choose which OS version you need during the install but that doesn't work installing via TWRM installing the universal version of Xpozed seamless zip so you have to download from the XDA site the latest Xposed with the SDK of your OS, in my case SDK23 latest version for Android 6.0. Now once you get Xposed installed via TWRP, then everything appears to work but trying to load XprivacyLua says it is not installed when the Xposed Module list says it is installed and the module is checked as being active. Yet the XprivacyLua menu still says you need to fix the issue.
Flex_or_fleece who claimed to get this working in a prior post said he resolved his problem by going to the link for BusyBox XDA pages for a solution, well I tried that, first installing BusyBox free from playstore, made sure that it said it was installed, then I loaded the libraries they talk about that is supposed to fix the BusyBox with toybox and after installing and testing the free version of BusyBox, then booting to TWRP and installing the Busybox library zip, once you boot up, the Magisk Manager will never open up again, just a blank green screen.
Time for a restore and try something else next time but unfortunately (unless the guy I asked about what exactly he did regarding BusyBox will respond, which he hasn't yet, ) then it's anyone's guess and I am all fresh out of guesses

Donphillipe said:
This whole thing is really frustrating. Get Magisk installed via TWRP, then to load Xposed Framework, you have to load Xposed via TWRP and then if you follow comments here from Flex_or_fleeceand his mini guide for downloading from Magisk with download only and not an install, you get the universal Xposed Systemless zip that is supposed to be able to choose which OS version you need during the install but that doesn't work installing via TWRM installing the universal version of Xpozed seamless zip so you have to download from the XDA site the latest Xposed with the SDK of your OS, in my case SDK23 latest version for Android 6.0. Now once you get Xposed installed via TWRP, then everything appears to work but trying to load XprivacyLua says it is not installed when the Xposed Module list says it is installed and the module is checked as being active. Yet the XprivacyLua menu still says you need to fix the issue.
Click to expand...
Click to collapse
I already did the BusyBox thing you talked about before and it went the same way. The difference is that my first attempt was by downloading from XDA so I didn't went through the universal zip problem. Actually there is now inside Magisk both the universal zip and the targeted sdk version numbers ones. Also I installed GravityBox and it said that couldn't communicate to the framework or something like that. Basically same problem. But I noticed something: when you install Xposed and reboot for the first time, it says that the Xposed framework is installed but not active and tells you to check the logs. If you go there you can see that the log file apparently doesn't even exist. In the second reboot it tells you it's active and running but if you check the logs it still couldn't open it because it doesn't exist. So maybe the problem is that Xposed isn't even starting up.

Mark42XLII said:
I already did the BusyBox thing you talked about before and it went the same way. The difference is that my first attempt was by downloading from XDA so I didn't went through the universal zip problem. Actually there is now inside Magisk both the universal zip and the targeted sdk version numbers ones. Also I installed GravityBox and it said that couldn't communicate to the framework or something like that. Basically same problem. But I noticed something: when you install Xposed and reboot for the first time, it says that the Xposed framework is installed but not active and tells you to check the logs. If you go there you can see that the log file apparently doesn't even exist. In the second reboot it tells you it's active and running but if you check the logs it still couldn't open it because it doesn't exist. So maybe the problem is that Xposed isn't even starting up.
Click to expand...
Click to collapse
On one of my iterations I installed a playstore app Marshmellow SD fix which fixed my problem with Xposed saying it couldn't read the log file. https://forum.xda-developers.com/xposed/modules/xposed-marshmallow-sd-fix-write-t3403263 But then once I installed this, slide the slider for Xposed to "authorize to sdcard" and then Xposed no longer had the error saying it couldn't read the log file but then simply always said "log file empty".
I'm just trying for Xposed and XprivacyLua only. When if I don't install BusyBox or the follow up install of the BusyBox binary zip file (that locks up the Magisk screen) and when I only start with a full ROM restore, install Magisk with TWRP, bring up Magisk and install Magisk Manager, install Xposed Systemless via TWRP, bring it up then it says Xposed is active. In Xposed I download and install the latest XprivacyLua and click the box in the Xposed module listo enable XprivacyLua, the check box remain checked and show active but the XprivacyLua menu says it is not installed. I sent a trace to the developer of XPrivacyLua and he said that Xposed was never loading it, and this is to repeat with all the respective check box checked and everything but the actual app saying all are active.
Adding "BLU STUDIO XL 2" so maybe Google can find this thread when people don't append the 2 to the XL"

Xposed still not working
I won't use a phone without these tools so at the moment I am still using my old Blu Studio with Android 5 that has the cracked screen and it is getting more and more cracked and harder to read. From time to time I pull my new unused BLU STUDIO XL 2 out of the closet and go a few more rounds with it. I've searched high and dry for the FlexorFliece fellow who claims to have it working and can't find him on any other blog or forum and he doesn't respond to messages but I just don't see how he got the Xposed suite working on this phone. I just spent three 14 hour days working on it as of today and got so frustrated that I reflashed the stock ROM on it and set it back in the closet again to try again another day, perhaps waiting like last time for a few more releases of the respective apps and modules to try again.
Now with several iterations of installing Xposed I've gotten the "green light" from Xposed Installer menu saying that it's installed and working and with the latest release which I think I recall is Magisk 17.1 and Xposed seamless SKD23 at release 89.3. This is actually quite funny that the light is green with Xposed Framework indicated as active from the Xposed Installer menu. You can then start searching for and downloading modules from the Xposed Manager and eventually the "green light" will go red while none of the Xposed modules will ever work, green or red light. At least the red light finally gives you a real indication.
I've loaded versions of Magisk all the way back to V14 and Xposed seamless (SDK23) back to 87.3 and the results are always the same. I'm either in a boot loop on a bad try or on a good try I'm showing the green light on Xposed but with no module working and reaching a threshold of about 6 Xposed modules loaded, then the light finally turns to a red one saying it's not installed or working.
I tried Flex or Fleece's technique of adding the Magisk version (from its repository of Magisk modules), the busybox and the ADB/Flashboot modules as a prerequisite but that didn't do a thing.
Now here's some odd things about this phone and even getting it to a good point to experiment with it.
I've found if I start with a fresh flash of the stock ROM or the phone in any condition without USB Debugging on, for example if I start with a powered down phone and hold the VOL-UP and POWER button at the same time, I can go to the stock recovery to select boot to bootloader option. (Release the POWER button slightly before the VOL UP or you'll boot the phone instead.)
Next I move to the PC and begin fastboot commands:
- get the ADB command window up by bringing up Windows file explorer with the name of the ADB folder visible and while holding SHIFT I then right click on the ADB folder and select "Open command window here" which opens a "DOS prompt" with the adb files in the directory. It's assumed I have pre-copied the new recovery image recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img to the same directory (folder) as hosts the adb.exe and fastboot.exe. Here I go back up to Windows File Explorer open the folder containing ADB/fastboot and rename this image to a shorter name. (Could use the DOS rename command but the syntax is too long and too easy to make a mistake.) Here I have renamed it to simply recoveryTWRP.img
Now then on the PC command window I enter ....
fastboot devices (to check that my USB is working OK)
fastboot oem unlock (to unlock the bootloader)
fastboot flash recovery recoveryTWRP.img (recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img that's been renamed)
fastboot reboot (to reboot the phone)
The phone may not boot after a flash or after and adb/fastboot interaction if the USB cable is not unplugged when done, so be aware of that.
Now if you are fast, you can go ahead and hold VOL UP at the moment the phone begins to boot and at the moment you have completed the fastboot series of commands. As soon as you see the TWRP recover manager you can release the VOL UP and be patient while the TWRP Menu appears.
Note now that you won't be able to use the SD card you may have randomly installedwith TWRP unless you have initialized it via Settings on the phone where you have under Storage option, set the SD card type to be "portable storage". If it's not formated and initialized by this phone, TWRP won't let you select it.
Quirks seen here include a failed install with unable to mount errors on the TWRP console trying to root, that is unless you have actually initialized the phone and set on Developer Tools and turned on USB debugging. (Sounds crazy but that's what I am seeing.) So basically that's what you'll find. ALso this verion of TWRP on this phone will not mount USB storage as with TWRP on other BLU devices I've tested, so copy all l your potential zip files to install as well as your apks you plan to side load (e.g. Xposed Installer and Magisk Installer apk files to the SD card prior to loading TWRP and finding that the files are not on the card or in the phone storage yet.
Other caveats are, with USB debugging off, each time you plug in the USB cable and want to upload files to the phone, when you go looking for the files in Windows device manager you will see a blank white screen appearing like there are no files on the deivce. What you have to do is slide the phone messages up and down a few times (perhaps dragging down from the top if it's not on the main screen) and finally the small window will appear on the phone where it asks for USB Charging only which you can tap and change it to USB Media and at that point you can see the SD card and Internal Storage for the phone in the respective Pc window where you can drag files into the phone's folders from the Windows PC. Otherwise with the phone having USB Debugging on you are supposed to be able to set it permanently to USB Media but you actually can't set it permanently. If you do research you will see online articles claiming that with Developer Options enabled and USB Debugging on, that setting the option just above the green "input" word on the Developer options screen allows you to set USB Charging to USB Media and it should stay permanently. Well stay it does on the menu but the function itself does not stay. Here each time you plug the phone in with the USB cable you will be curious why you cannot access the phone's storage because you believe the menu in Developer options that says it has been set to USB Media. Yes, it shows that way but you still can't see the storage on the PC. What you have to do each time you attache the phone with a USB cable then is go to Developer Options (shortcut would be to click on the info bar stating USB Debugging is enabled and when you arrive at Developer options, page down to just above the green "input" word and then temporarily set the option from USB Media to one of the other options, then set it back again to USB Media and you once again can see the phone's storage on your Windows computer.
And all this work and dealing with quirks is required before you even try to root by using SU or Magisk zip files and attempting to install then via the new TWRP recovery image you installed and gain access to by rebooting and holding in the VOL UP button to access the TWRP menu.
Otherwise the best performing ROM I have found is BLU_S0270UU_V6.0.04.02_GENERIC but when I went looking for it just now, the only place I can find it is now with the new toll-booth controlled need.rom repository. Yes I now see that needrom.com has now started charging to download the zip recovery modules we all uploaded there for free. What a sneaky bunch of #$#R)!!! Also, the spamming of Google has made searching for ROMs and any information about rooting a phone all but worthless. For example when I searched for BLU_S0270UU_V6.0.04.02_GENERIC which I believe is the latest ROM. I know there is a V8 floating around out there that I loaded but just in setting it up, the layout of the screen first went crazy and then the wireless log-in gave problems and then and finally the turning point was that the camera or video wouldn't work, so I gave up that version of the ROM. Anyway, searching for the ROM resulted in 5 full pages of search results with every website on every page saying they had the rom to download but in fact none of them did. I got directed from everything from purchasing female teen clothes, to sports gambling sites to unending surveys to you name it. What a vast wasteland it is out there these days. Unless Google does something to stop this technique where every website says they have a hit on your phone model when all they do is to stuff your search argument into a page of generic randomly generic diatribe, one day we will no longer be able to use the Internet to find things, or certainly it will take more time while weeding through all the disinformation.
Now

Yes, but that is not the challenging part. The challenging part is to get Xposed installed and the Xposed apps working with your root that you can obtain by several methods.

TWRP and this phone is easy, as you said and as I agreed. You will not be able to get Xposed apps running if that is the goal - even with root.

What is the main interest in this phone rooted? No one has gotten Xposed working so far or if they do get the green banner saying it is installed, it doesn't work with any of the apps. (Reported as due to toybox.) The phone has been rootable for nearly a year now, it's just that you can't do much with the root once you get it.
I have had my phone rooted for over a year now. Every few months I try again installing the latest version of Xposed via SuperSU or Magisk. Xposed apps will not work with either.

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

Managed to root but cannot update

Hi!
Xperia ZXP was running the official Firmware fine. Then, I just decided to root. I followed this video:
Got my phone properly rooted.
Now I keep getting notification of an update that I had before but cannot install it. Also, I cannot setup my company work profile as it detects root.
I mainly wanted to use Cheat Engine that why I rooted.
How do I apply latest update?
How do I hide root status?

Download Flashtool and latest version of Xperifirm. Find latest firmware with Xperifirm. Should end in .107. Download it and decrypt it with Flashtool. Download Newflasher. Unzip Newflasher into the folder you have the decrypted files. Plug your phone into your computer. Make sure you have the correct driver. Developer option and usb debugging enabled on your phone. Put phone into flash mode and hit newflasher.exe and choose "n" for the first two choices and let it run. That will give you the latest and final update for this phone.
Now use twrp to install the latest Magisk version(search online), also have Magisk manager app(Play Store) on your phone. Once that's done and you've rebooted phone open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root. If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything.

bobsright said:
Download Flashtool and latest version of Xperifirm. Find latest firmware with Xperifirm. Should end in .107. Download it and decrypt it with Flashtool. Download Newflasher. Unzip Newflasher into the folder you have the decrypted files. Plug your phone into your computer. Make sure you have the correct driver. Developer option and usb debugging enabled on your phone. Put phone into flash mode and hit newflasher.exe and choose "n" for the first two choices and let it run. That will give you the latest and final update for this phone.
Now use twrp to install the latest Magisk version(search online), also have Magisk manager app(Play Store) on your phone. Once that's done and you've rebooted phone open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root. If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything.
Click to expand...
Click to collapse
Is there a place/page here that lists all these tools?

Fix after root effects
bobsright said:
Download Flashtool and latest version of Xperifirm. Find latest firmware with Xperifirm. Should end in .107. Download it and decrypt it with Flashtool. Download Newflasher. Unzip Newflasher into the folder you have the decrypted files. Plug your phone into your computer. Make sure you have the correct driver. Developer option and usb debugging enabled on your phone. Put phone into flash mode and hit newflasher.exe and choose "n" for the first two choices and let it run. That will give you the latest and final update for this phone.
Now use twrp to install the latest Magisk version(search online), also have Magisk manager app(Play Store) on your phone. Once that's done and you've rebooted phone open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root. If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything.
Click to expand...
Click to collapse
Here is how I'm going step by step:
Download Flashtool - Done
latest version of Xperifirm - Done
Find latest firmware with Xperifirm. Should end in .107 - Done
-- Download it - Done
-- decrypt it with Flashtool - Stuck
Download Newflasher - Done
-- Unzip Newflasher into the folder you have the decrypted files
Plug your phone into your computer
-- Make sure you have the correct driver - Done
-- Developer option and usb debugging enabled on your phone - Done
Put phone into flash mode and hit newflasher.exe
-- choose "n" for the first two choices and let it run
-- That will give you the latest and final update for this phone
I'm stuck at the decryption part... I downloaded the correct firmware for my phone and it is quite a load of files. But, the decrypt tool in Flashtool finds nothing to decrypt

Doomer D. Great said:
Here is how I'm going step by step:
• Download Flashtool - Done
• latest version of Xperifirm - Done
• Find latest firmware with Xperifirm. Should end in .107 - Done
○ Download it - Done
○ decrypt it with Flashtool - Stuck
• Download Newflasher - Done
○ Unzip Newflasher into the folder you have the decrypted files
• Plug your phone into your computer
○ Make sure you have the correct driver - Done
○ Developer option and usb debugging enabled on your phone - Done
• Put phone into flash mode and hit newflasher.exe
○ choose "n" for the first two choices and let it run
○ That will give you the latest and final update for this phone.
• Now use twrp to install the latest Magisk version(search online)
○ also have Magisk manager app(Play Store) on your phone
• Once that's done and you've rebooted phone
• open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root.
• If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything.
I'm stuck at the decryption part... I downloaded the correct firmware for my phone and it is quite a load of files. But, the decrypt tool in Flashtool finds nothing to decrypt
Click to expand...
Click to collapse
You have to select the location. Click on Tools, then Bundles, then FILEset Decrypt. On the line where it says source folder there's a small box on the end. Click it and from there go to your harddrive, users(you), flashtool, firmware, downloads and there you will find the firmware that you just downloaded. Click on it and that should unpack the firmware. Then select all the files to convert. That will place the converted files in the same location as the firmware. Don't bother with removing the .ta files. Do create the partition folder. See link below.
http://www.xperiablog.net/2018/01/2...mware-for-xperia-xz-premium-xz1-and-more/amp/
The above link will take you through all the above steps. You will lose user data. You can remove the USERDATA X Flash ALL and that should save your data but no guarantees.

bobsright said:
You have to select the location. Click on Tools, then Bundles, then FILEset Decrypt. On the line where it says source folder there's a small box on the end. Click it and from there go to your harddrive, users(you), flashtool, firmware, downloads and there you will find the firmware that you just downloaded. Click on it and that should unpack the firmware. Then select all the files to convert. That will place the converted files in the same location as the firmware. Don't bother with removing the .ta files. Do create the partition folder. See link below.
http://www.xperiablog.net/2018/01/2...mware-for-xperia-xz-premium-xz1-and-more/amp/
The above link will take you through all the above steps. You will lose user data. You can remove the USERDATA X Flash ALL and that should save your data but no guarantees.
Click to expand...
Click to collapse
The latets Xperifirm also extract right after downloading so the decrypt step is not needed.
I'm flashing a I write. I'll be dealing with the next part now:
Now use twrp to install the latest Magisk version(search online)
also have Magisk manager app(Play Store) on your phone
Once that's done and you've rebooted phone
open Magisk Manager and select the menu in upper left corner and go to Magisk Hide and if there's the option to hide whatever app that is detecting root and causing problems, select it and it should no longer detect root.
If the problem app is not shown then I don't know. I believe there is a Magisk Module that may be less app specific and hide Magisk from everything
TWRP has to be flashed or installed from store?

Was going to attach the file but had upload issues. What you want is twrp 3.3.1-0-maple.img. Once you have that put phone in fastboot mode ( volume up while plugging phone into computer) then go to the place you downloaded the above ( unzip it to a folder that also contains adb and fastboot unless you have that installed system wide). Open a powershell or cmd window inside that folder and type: fastboot boot twrp-3.3.1-0-maple.img. that'll open twrp on your phone in recovery. Then you can flash Magisk and that'll root your phone. I'm typing this from memory. I believe I have that right. If you want to install twrp on the phone itself umm, I believe you flash the .IMG file to recovery partition. You'll need to have both those files in your phone. Let me know if I got that right. If it doesn't work, no worries, just start over. These phones are hard to brick; believe me, I know.

bobsright said:
Was going to attach the file but had upload issues. What you want is twrp 3.3.1-0-maple.img. Once you have that put phone in fastboot mode ( volume up while plugging phone into computer) then go to the place you downloaded the above ( unzip it to a folder that also contains adb and fastboot unless you have that installed system wide). Open a powershell or cmd window inside that folder and type: fastboot boot twrp-3.3.1-0-maple.img. that'll open twrp on your phone in recovery. Then you can flash Magisk and that'll root your phone. I'm typing this from memory. I believe I have that right. If you want to install twrp on the phone itself umm, I believe you flash the .IMG file to recovery partition. You'll need to have both those files in your phone. Let me know if I got that right. If it doesn't work, no worries, just start over. These phones are hard to brick; believe me, I know.
Click to expand...
Click to collapse
I have downloaded the TWRP image and I have the android platform tools as well. Right now, my mobile is working with the latest ROM from Xperifirm and I'm not sure about root status. It was rooted before I did the firmware update. It is latest now and no app is complaining.
Current status:
- OEM Booltloader unlocked
- USB Debugging ON
Question:
- I need to know will if I'll lose all data on the phone?
- If I use the fastboot boot twrp-3.3.1-0-maple.img command, phone wil have TWRP as recovery and will be in this recovery mode? I need to copy Magisk (apk?) already on the phones hardrive so I can install from there?

Doomer D. Great said:
I have downloaded the TWRP image and I have the android platform tools as well. Right now, my mobile is working with the latest ROM from Xperifirm and I'm not sure about root status. It was rooted before I did the firmware update. It is latest now and no app is complaining.
Current status:
- OEM Booltloader unlocked
- USB Debugging ON
Question:
- I need to know will if I'll lose all data on the phone?
- If I use the fastboot boot twrp-3.3.1-0-maple.img command, phone wil have TWRP as recovery and will be in this recovery mode? I need to copy Magisk (apk?) already on the phones hardrive so I can install from there?
Click to expand...
Click to collapse
If you didn't lose data in upgrading the firmware you won't lose it installing Magisk. Using TWRP from your computer does not install it. It only puts you into recovery using TWRP as the menu. If you want to have it installed you need to flash the .img file to the recovery partition while in TWRP. All this does is eliminate the need to use a computer every time you want to use TWRP.
You more than likely lost root when flashing the new firmware. So Magisk apk is the manager app. You also need to have Magisk 20.4 as a zip file in your phone. When in TWRP select mount and make sure the location where the zip is is selected. Then go back and select install and then go to the location of the zip, select it and slide the slider and it will install. Go back to main menu and power off. People like to wipe and reboot, I find not wiping if you don't have to works for me along with powering off and then restarting the phone.

bobsright said:
If you didn't lose data in upgrading the firmware you won't lose it installing Magisk. Using TWRP from your computer does not install it. It only puts you into recovery using TWRP as the menu. If you want to have it installed you need to flash the .img file to the recovery partition while in TWRP. All this does is eliminate the need to use a computer every time you want to use TWRP.
You more than likely lost root when flashing the new firmware. So Magisk apk is the manager app. You also need to have Magisk 20.4 as a zip file in your phone. When in TWRP select mount and make sure the location where the zip is is selected. Then go back and select install and then go to the location of the zip, select it and slide the slider and it will install. Go back to main menu and power off. People like to wipe and reboot, I find not wiping if you don't have to works for me along with powering off and then restarting the phone.
Click to expand...
Click to collapse
Mission accomplished.
I did all this so that I can use Cheat engine to chat in some silly games plus a few simple ones I made with Unity. Turns out, Cheat Engine fails to show running apps to select from... what a trip...

Doomer D. Great said:
Mission accomplished.
I did all this so that I can use Cheat engine to chat in some silly games plus a few simple ones I made with Unity. Turns out, Cheat Engine fails to show running apps to select from... what a trip...
Click to expand...
Click to collapse
So Cheat Engine doesn't detect root with Magisk?

bobsright said:
So Cheat Engine doesn't detect root with Magisk?
Click to expand...
Click to collapse
Everything works perfectly. All apps working with root and Magisk is hiding root from required apps. Cheat Engine is working with Root. After that, the issue is with Cheat Engine. It is not working as expected. I see an emty Apps list and cannot fing the game I want to cheat in even when it is running. This is off topic as the thread is now complete. Just saying I didi all this for a dissapinting app.

Doomer D. Great said:
Everything works perfectly. All apps working with root and Magisk is hiding root from required apps. Cheat Engine is working with Root. After that, the issue is with Cheat Engine. It is not working as expected. I see an emty Apps list and cannot fing the game I want to cheat in even when it is running. This is off topic as the thread is now complete. Just saying I didi all this for a dissapinting app.
Click to expand...
Click to collapse
Oh well, at least you got it updated and working. Maybe it'll take some searching somewhere else to get that other stuff worked out.
Just a side note; I used to work for Sheikh Hamdan bin Rashid Al Maktoum at his Throughbred operation in Lexington.

Excuse me, does anyone know how to root xz premium docomo ubl no ??? Now on Android 9 Pie, please help.

I believe the Japan market version can't have the bootloader unlocked, thus, no root.