Develop Bugs

[ROOT] Easy Root 4.1 With VRoot ( Update software 01/11)

{
"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"
}
Greetings to Friends
A few days ago in xperiablog
Root was introduced to the Xperia Z1
http://www.xperiablog.net/2013/09/11/xperia-z1-gets-root/
I 've tested the same time I realized that the Xperia SL
This software can be easily routed
get to share with your friends
Although is very easy
But I will give a simple video tutorial
First, the software VRoot Download the attachment to this post
Or from the manufacturer's site
http://www.mgyun.com/vroot
1 - Install drivers for your phone
2 - Activate the option in your phone Enabled usb debugging
Settings / Developer options
3 - After opening the software and USB cable to connect your phone
4 - When was your phone program
Right click the first option
As shown
Your phone will then reboot
And successful Root the message on the screen
This method will work on most Sony devices
If it is successful, then reboot the phone, the application icon will appear in Root
Note : The root of the problem
SuperSU flash files from the recovery menu, select
Thanks
Amir

Thank you!!
This is brilliant, Genius, Easy, Hassle Free, worked on my Acro S like a charm!!!!

Cool. Anyone taken it apart yet, I want to know how they do it!

My Xperia S already rooted but I wanted to see if it works for my "Smart S14" (Chinese Android) I was surprised cuz it really worked.

it works on stock .96 Xperia S fw?

cikoxda said:
it works on stock .96 Xperia S fw?
Click to expand...
Click to collapse
Yes easily
Sony on all devices I 've even tried Samsung or HTC

Thanks mate.It worked easyly.But one Question.The Superuser App is written in mandarin or Corean language.Is it possible to change the Apps Language to English?
Or could i easyly uninstall it an replace it with an other Superuser App from Marketplace?
Thanks and regards.

quentin.0160 said:
Thanks mate.It worked easyly.But one Question.The Superuser App is written in mandarin or Corean language.Is it possible to change the Apps Language to English?
Or could i easyly uninstall it an replace it with an other Superuser App from Marketplace?
Thanks and regards.
Click to expand...
Click to collapse
+1

I guess u can always install another superuser app. I prefer Super SU btw.

Great this seems to work with my XS , FW - 6.2.B.1.96 , thanks

RazorMC said:
I guess u can always install another superuser app. I prefer Super SU btw.
Click to expand...
Click to collapse
Yes, but how do we uninstall the chinese superuser - app?
(I only deactivated it for now)
Thanks,
Bernd
Sent from my LT26i using xda app-developers app

Hi @ all
System apps like this Cineese SU App can be uninstalled with "root App Deleter".Found on market.You need root permissions too.

just install super su and update the binaries.. them it will promp to unistall the other ones.. it worked for me..

It works, but I have a small issue: I can't remove the Superuser application the rooting kit provides. I install SuperSu, it prompts me to update the binaries, I do, and it tells me "installation successful", but it doesn't ask me to remove the other superuser applications. So I am stuck with the Chinese/Korean Superuser application. Any thoughts on this?

alex.sg said:
It works, but I have a small issue: I can't remove the Superuser application the rooting kit provides. I install SuperSu, it prompts me to update the binaries, I do, and it tells me "installation successful", but it doesn't ask me to remove the other superuser applications. So I am stuck with the Chinese/Korean Superuser application. Any thoughts on this?
Click to expand...
Click to collapse
1.Root with VRoot
2.Install Superuser or Supersu and update binares
3.Unroot with VRoot click in ROOT button on this page:
4.reset xs
It's work

debriuman said:
1.Root with VRoot
2.Install Superuser or Supersu and update binares
3.Unroot with VRoot click in ROOT button on this page:
4.reset xs
It's work
Click to expand...
Click to collapse
Thank you! It worked!

alex.sg said:
It works, but I have a small issue: I can't remove the Superuser application the rooting kit provides. I install SuperSu, it prompts me to update the binaries, I do, and it tells me "installation successful", but it doesn't ask me to remove the other superuser applications. So I am stuck with the Chinese/Korean Superuser application. Any thoughts on this?
Click to expand...
Click to collapse
File added Super SU
The root of the problem
SuperSU flash files from the recovery menu, select

Xperia acro S .96 FW
Hi. I'm currently trying this one but VRoot is taking a long time recognizing my phone. Any idea guys why?

Tried it on a chinese tablet Nextway F8X which nothing else could root, and that worker like BOSS!!! BRAVO!!!

Just wonder how it works... Somebody can explain that? I'm not so optimistic to tools like this.
Tap Tap Tapatalk - Sony Xperia S [4.1.2]

[Q] Language Changes on Restart of Samsung Galaxy Grand

Hi,
I have installed the new GENNXT ROM J4.
Whenever my phone reboots it has a different language (Not English)
Please help me to fix this permanently.
One more problem that am facing is my phone beeps randomly anytime..

akifdadan said:
Hi,
I have installed the new GENNXT ROM J4.
Whenever my phone reboots it has a different language (Not English)
Please help me to fix this permanently.
One more problem that am facing is my phone beeps randomly anytime..
Click to expand...
Click to collapse
hello, the problem supersu remove updates from the store and put the version 1.65 I solved so

tonimontoia said:
hello, the problem supersu remove updates from the store and put the version 1.65 I solved so
Click to expand...
Click to collapse
Didnt understand.. can u please be a little descriptive ..?
Thanks for replying...

akifdadan said:
Didnt understand.. can u please be a little descriptive ..?
Thanks for replying...
Click to expand...
Click to collapse
the problem is supersu, remove the new version and forgive version 165

akifdadan said:
Didnt understand.. can u please be a little descriptive ..?
Thanks for replying...
Click to expand...
Click to collapse
Go to Aplication Manager, select the App SuperSU, and Unistall updates. That should bring you back to the older version. Just make sure you don't have Auto Update turned on from Google Play. Otherwise, it is going to update it back to new version.

hunter0389 said:
Go to Aplication Manager, select the App SuperSU, and Unistall updates. That should bring you back to the older version. Just make sure you don't have Auto Update turned on from Google Play. Otherwise, it is going to update it back to new version.
Click to expand...
Click to collapse
Reverted the updates and rebooted my phone..
Still boots into some other language..
Unable to uninstall SuperSu 1.69
Any way possible to uninstall super su so that i can install supersu 1.65 ?

akifdadan said:
Reverted the updates and rebooted my phone..
Still boots into some other language..
Unable to uninstall SuperSu 1.69
Any way possible to uninstall super su so that i can install supersu 1.65 ?
Click to expand...
Click to collapse
According to ChainFire (He is the developer) on Google+, it will be fix on the next update. So, I would just wait if you can't uninstall the current version.
"Language changing every boot on some firmwares
This issue is found and fixed in the next update. Took a few hours to locate this one ...
OTA survival breaking OTA update 4.3 --> 4.4"
Also fixed in the next update

I have the same problem on 4.2.2 rooted stock rom. Always reverts to russian after reboot. I am in France. Very bothering.
Sent from my GT-I9082 using xda app-developers app

The update just went live guys. The language problem is fixed

GXGOW said:
The update just went live guys. The language problem is fixed
Click to expand...
Click to collapse
It still says version 1.69 in the Play Store. After the update, the first reboot changed the language back to Portuguese. On the second reboot, the language seems to stick

Looks updated to me. It seems those bugs are fixed.
{
"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"
}
Sent from my GT-I8190 using Tapatalk

You're right. When I checked Google Play earlier it was still version 1.69. Just checked it under Application manager, it does say 1.75. All is well. Thanks.

hunter0389 said:
You're right. When I checked Google Play earlier it was still version 1.69. Just checked it under Application manager, it does say 1.75. All is well. Thanks.
Click to expand...
Click to collapse
In Google added an updated version of Super Su 1.75 and now when you restart the language does not change

Android pay

I tried setting up android pay, but can't seem to get it to work. I've tried using root cloak and no device check, but whatever I do, I can't get it to work.
{
"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"
}

It's not going to if you're rooted. Check the following link (and subsequent forum post):
http://www.xda-developers.com/googl...-with-root-and-android-pay-in-the-xda-forums/
I'm sure someone will find a work around, but for now you have to do one or the other.

Did you change your DPI? That apparently was my problem.

fr4nk1yn said:
Did you change your DPI? That apparently was my problem.
Click to expand...
Click to collapse
It also doesn't work if you are rooted.

geoff5093 said:
It also doesn't work if you are rooted.
Click to expand...
Click to collapse
Indeed. But reports are saying you can temporarily unroot and it'll activate. My G4 isn't rooted and it wouldn't go through with a DPI change.

fr4nk1yn said:
Indeed. But reports are saying you can temporarily unroot and it'll activate. My G4 isn't rooted and it wouldn't go through with a DPI change.
Click to expand...
Click to collapse
I've heard mixed things. It's not just adding a card - some people I've heard say that transactions fail if the phone is rooting at the time of purchase even if they got it through the card adding process. Others, I've seen saying that the temporary unroot trick worked.

DarkWolf747 said:
I've heard mixed things. It's not just adding a card - some people I've heard say that transactions fail if the phone is rooting at the time of purchase even if they got it through the card adding process. Others, I've seen saying that the temporary unroot trick worked.
Click to expand...
Click to collapse
I was finally able to add a card, I had to add Google Play Services to Root Cloak. I haven't tested it yet but so far so good at least.

larrydp said:
I was finally able to add a card, I had to add Google Play Services to Root Cloak. I haven't tested it yet but so far so good at least.
Click to expand...
Click to collapse
It seems to have worked. You are awesome!
Sent from my VS986 using Tapatalk

I got it to work by disabling Superuser. Once I did that, I could add the card and then enable Superuser again. No problems using Android Pay once Superuser was enabled after getting the card added.

thanks i got it going on my g4 wish i can ha e it working on my g3

You have to rootcloak both Android Pay and Google Play Services.

I tried that on my g3. No go. To let you know im on 4.4.2 on my g3

I finally got it to work with my rooted G4, but I had to rely on Xposed and Rootcloak.
1. Set DPI to the default (640). Unfortunately, Android Pay won't work on anything other than stock DPI. (I went back to stock DPI, but use the App Settings (xposed) app to set my individual apps back to 540) Reboot.
2. Open RootCloak (xposed), and add both Google Pay Services and Android Pay to the block list.
3. Open SuperSu and go to settings. Uncheck "Enable SuperSu". This will take a minute or so to run, but it is reversible (you won't lose root).
4. Clear data for Google Play Services and Android Pay. You will have to set up some of your account info again, and let it re-sync.
5. Open Android Pay and add all your cards. This must be done before re-enabling root.
6. When complete, go back to SuperSu, and re-enable root. Reboot.
These are the steps that worked for me, but YMMV.

I was able to get it working with the exact same steps except I skipped #4 and things turned out fine.
Verified by using the phone to pay at Walgreens.
---Paul
billybob275 said:
I finally got it to work with my rooted G4, but I had to rely on Xposed and Rootcloak.
1. Set DPI to the default (640). Unfortunately, Android Pay won't work on anything other than stock DPI. (I went back to stock DPI, but use the App Settings (xposed) app to set my individual apps back to 540) Reboot.
2. Open RootCloak (xposed), and add both Google Pay Services and Android Pay to the block list.
3. Open SuperSu and go to settings. Uncheck "Enable SuperSu". This will take a minute or so to run, but it is reversible (you won't lose root).
4. Clear data for Google Play Services and Android Pay. You will have to set up some of your account info again, and let it re-sync.
5. Open Android Pay and add all your cards. This must be done before re-enabling root.
6. When complete, go back to SuperSu, and re-enable root. Reboot.
These are the steps that worked for me, but YMMV.
Click to expand...
Click to collapse

Stock Oreo Rom Debloater Script

STOCK OREO ROM DEBLOATER SCRIPT.​
{
"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"
}
The Following apps/services will be removed if you Flash this zip file:
These apps can be easily installed through playstore if you want few of them specifically
#Apps
Google Drive
Google Duo
DTV Player
FM Radio
Gmail
Google Hindi Keyboard
Google Pinyin Keyboard
GuideMe (Moto Help)
Hangouts
Japanese Keyboard
Korean Keyboard
LiveWallpapersPicker
Google Maps
Messages
Google Music
Photos
Sim Toolkit
Talkback
Google Videos
Wallpapers
YouTube
Zhuyin Keyboard
#Priv-apps
AudioFX ( Equalizer )
Emergency Info
Velvet ( Google )

Can you choose the applications that you want to remove?
Or All those that are in the list will be deleted

For what purpose this zip file is used

skacit said:
For what purpose this zip file is used
Click to expand...
Click to collapse
It removes the apps stated above that ships with the rom

does this work on a locked bootloader?

masivb said:
does this work on a locked bootloader?
Click to expand...
Click to collapse
No, cause you need Root access and that's not possible without unlocked bootloader.

al3al3al3jandr0 said:
Can you choose the applications that you want to remove?
Or All those that are in the list will be deleted
Click to expand...
Click to collapse
Apparently you can modify the list in the zip file.

Removed others apps
imonkeys said:
Apparently you can modify the list in the zip file.
Click to expand...
Click to collapse
The following applications can also be removed:
- App Widget
- File Manager
- 1st Prip
- 2 Prip
- Republic Wireless
Or affect the system?

al3al3al3jandr0 said:
The following applications can also be removed:
- App Widget
- File Manager
- 1st Prip
- 2 Prip
- Republic Wireless
Or affect the system?
Click to expand...
Click to collapse
Yeah those can be removed too.
but they are in a different folder i.e oem/apps & oem/priv-apps
i tried several ways but didn't find a way to incorporate it in the script. for now the best way to delete them is through root explorer.
again, i dont have any idea about coding. i just edited the zip file to be compatible with our device.
if someone could find a way to do it then i can surely add that too

Great contribution
ganeshkmr21 said:
Yeah those can be removed too.
but they are in a different folder i.e oem/apps & oem/priv-apps
i tried several ways but didn't find a way to incorporate it in the script. for now the best way to delete them is through root explorer.
again, i dont have any idea about coding. i just edited the zip file to be compatible with our device.
if someone could find a way to do it then i can surely add that too
Click to expand...
Click to collapse
Amazing, thank you and good work

Hello, this can be done without root, but with unlocked bootloader and TWRP? ElementalX Kernel installed.
Thanks!!

3Rick99 said:
Hello, this can be done without root, but with unlocked bootloader and TWRP? ElementalX Kernel installed.
Thanks!!
Click to expand...
Click to collapse
Yes it can be

Not working
Hi, when I flash the script in TWRP and reboot nothing happens. All the apps are still present. Please Help.
Thank You

The zip package works yes, I used it today on my Moto G4 with stock rom, it worked perfectly. Something that I do not recommend removing is Republic Wireless, in case you remove it will give you an error in the applications option in the settings, the maximum you should do is to freeze it using the titanium backup or some other program that does the same.

Does it work with Current Oreo Soak Test? (OPJ28.108)

xSamukaBRx said:
Does it work with Current Oreo Soak Test? (OPJ28.108)
Click to expand...
Click to collapse
It should still work with 8.1 stock rom, because package names should still be the same. Better backup your system with TWRP before you flash the debloater, just to be safe.

thorin0815 said:
It should still work with 8.1 stock rom, because package names should still be the same. Better backup your system with TWRP before you flash the debloater, just to be safe.
Click to expand...
Click to collapse
I already flashed aroma 8.1 gapps. But thanks for answering

It works on Oreo :good:

Thanks it worked on Latest SOAK 8.1
is there any way to uninstall Stock Phone App and install latest Google Phone app ?

Wtf after i flashed the script im not able to record video from any app ???

Should a custom kernel fix this?

I recently got the Pixel 3 XL, and was working to get it setup. However, I am going to wait to activate it until I know that I can successfully pass the SafetyNet Check and use Android Pay.
I have quite a few apps so I wanted to transfer a lot of them via Titanium Backup. I successfully installed Magisk, flashed the patched boot.img file, verified I was rooted, and installed all of my apps via Titanium Backup---from one of my other devices.
Then I re-flashed the original boot.img file to partition A & B and verified that I was no longer rooted.
However, my Device shows up as NOT CERTIFIED in Google Play. I totally expected this, since my bootloader is definitely unlocked.
Question #1: When developers start releasing custom kernels, will this issue probably be resolved? I don't care about root, beyond restoring my apps, but Android Pay is highly utilized.
Question #2: Has anyone unlocked your bootloader and still had their device show up as CERTIFIED, with Android Pay working as expected?

Unlocked and still certified. I assume it's because I haven't modified the system partition by only using systemless mods in magisk
Sent from my Pixel 3 XL using Tapatalk

Pic
{
"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"
}
Sent from my Pixel 3 XL using Tapatalk

If you've installed overlays, they reside in system/app, and thus you have modified system.
You're certified because Magisk hide is doing its job in relation to SafetyNet.
superchilpil said:
Unlocked and still certified. I assume it's because I haven't modified the system partition by only using systemless mods in magisk
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Sent from my Pixel 3 XL using Tapatalk

diesteldorf said:
I recently got the Pixel 3 XL, and was working to get it setup. However, I am going to wait to activate it until I know that I can successfully pass the SafetyNet Check and use Android Pay.
I have quite a few apps so I wanted to transfer a lot of them via Titanium Backup. I successfully installed Magisk, flashed the patched boot.img file, verified I was rooted, and installed all of my apps via Titanium Backup---from one of my other devices.
Then I re-flashed the original boot.img file to partition A & B and verified that I was no longer rooted.
However, my Device shows up as NOT CERTIFIED in Google Play. I totally expected this, since my bootloader is definitely unlocked.
Question #1: When developers start releasing custom kernels, will this issue probably be resolved? I don't care about root, beyond restoring my apps, but Android Pay is highly utilized.
Question #2: Has anyone unlocked your bootloader and still had their device show up as CERTIFIED, with Android Pay working as expected?
Click to expand...
Click to collapse
I'm bootloader unlocked, rooted, running a Substratum theme and Android Pay works fine plus my device is certified in Google Play.
You have to use Magisk hide on the apps that don't work with root. As far as your device showing up as not certified, use Magisk hide on Google Play store then reboot, then clear the storage and cache on the play store, reboot again and it will show up as device certified.

These are the apps I use Magisk hide on and everything on my Pixel 3 XL works like it's not rooted.

diesteldorf said:
I recently got the Pixel 3 XL, and was working to get it setup. However, I am going to wait to activate it until I know that I can successfully pass the SafetyNet Check and use Android Pay.
I have quite a few apps so I wanted to transfer a lot of them via Titanium Backup. I successfully installed Magisk, flashed the patched boot.img file, verified I was rooted, and installed all of my apps via Titanium Backup---from one of my other devices.
Then I re-flashed the original boot.img file to partition A & B and verified that I was no longer rooted.
However, my Device shows up as NOT CERTIFIED in Google Play. I totally expected this, since my bootloader is definitely unlocked.
Question #1: When developers start releasing custom kernels, will this issue probably be resolved? I don't care about root, beyond restoring my apps, but Android Pay is highly utilized.
Question #2: Has anyone unlocked your bootloader and still had their device show up as CERTIFIED, with Android Pay working as expected?
Click to expand...
Click to collapse
Just clear data in the play store. Thats all it needs....

micmars said:
If you've installed overlays, they reside in system/app, and thus you have modified system.
You're certified because Magisk hide is doing its job in relation to SafetyNet.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Overlays are in the vendor partition not system.
Back on my Pixel C when we didn't have twrp I would unpack the vendor partition and place the overlays.
NVM I guess OMS has changed since I last used it
Sent from my Pixel 3 XL using Tapatalk

No, not on Pie.
superchilpil said:
Overlays are in the vendor partition not system.
Back on my Pixel C when we didn't have twrp I would unpack the vendor partition and place the overlays.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Sent from my Pixel 3 XL using Tapatalk

elreydenj said:
Just clear data in the play store. Thats all it needs....
Click to expand...
Click to collapse
That fixed mine from saying that it was not certified. Thanks!