Related
Root your ICS/JB phone S2 + Samsung + not Samsung phones - No more waiting for custom kernels
This topic provides universal root methods to bypass the use of custom kernels. I took the time to write it as I was tired from waiting for a Dev to publish a custom kernel for the last firmware released.
I will try here to reference most threads and ways to root your phone. Some methods will let you root as soon as you get the new ROM, no more waiting for some dev to release a kernel for you.
I will not list here custom kernels that come with root, you can find them in other threads.
As a general rule, do not forget to take extra precautions when you flash anything: ALWAYS DO A NANDROID BACKUP IN CWM
Method 1 - Recommended
Push superuser + Busybox (Now v1.20.2 from Linus Yang) in recovery
{
"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"
}
Now, on the i9100 and some other phones (N7000...), you can flash the attached signed zip files in stock recovery, no more need to CWM.
A BIG BIG THANK YOU TO Chainfire for his support that made it possible and to Entropy512 who pushed me to look for a fix
Attached is the CWM Recovery 4.x non touch version, confirmed safe for wiping. It will not superbrick your phone
>>>>>> Now it is even getting greater with attached Clockworkmod v6.0.1.2 !!!! <<<<<<
>>>>>> Also probably safe from brickbug <<<<<<
Pros
Universal and will probably work on any ICS phone, if you have a CWM image. No longer wait for a modded kernel
On the i9100 and some other phones (N7000...), you can now even root from the stock recovery, no need to the cwm image
No PC needed, only an android device and the zip files that you download to your sd card
Fully reversible unroot without PC needed
No Yellow Triangle (Only for phones with a zip CWM image)
No custom counter increased (Only for phones with a zip CWM image)
Only copies superuser +/- busybox, nothing else is touched, neither /data nor the kernel
No brick risk while flashing cwm even if things go wrong as it will be always overwritten by stock recovery after a reboot
Click to expand...
Click to collapse
Cons
None since I switched to the CWM4 and CWM6 recoveries (no more superbrick risks under 4.0.4 ICS kernels, only CWM5.x was affected)
Click to expand...
Click to collapse
Special notes about busybox
The zip files attached in this post install busybox only in /system/xbin. I do not put any symlink in /system/bin
If you previously installed other versions of busybox, I advise to run Busybox Uninstaller v1.0 zip in the thread dedicated to it here: http://forum.xda-developers.com/showthread.php?t=1853419
It will clean any orphan symlink that could be left from a previous install. After that, install busybox from any of the attached files in this post
The uninstaller in this post, only removes busybox package from /system/xbin. I do not delete any package put in bin, as it is assumed it was put there by another program, not my script. It will not remove any symlink either. So, run the Busybox Uninstaller v1.0 for that
Click to expand...
Click to collapse
This method was first inspired from Rachmat3 thread here and Chainfire script here (do not forget to thank them). I modified it to work in stock recovery, enhanced script, include Chainfire superSU last version + BusyBox last binary. I also keep a ChainsDD superuser version.
Instructions
For phones affected by the superbrick bug (i9100, N7000) and that has a stock recovery accepting update.zip files (most phones with a temporary cwm.zip file at Clockworkmod site:
You can flash the attached files directly in stock recovery 3e, no need to cwm:
Download the root file:
- Root_SuperSU.0.96.Only-signed.zip for Chainfire SuperSU (the one that comes with CF_Root) without busybox.- Root_SuperSU.0.96-FreeSpace.zip for Chainfire SuperSU without busybox (use only if you have issues with previous one, usually for phones having a /system partition with 0 free space).- Root_SuperSU.0.96-Busybox.1.20.2-S2-signed.zip to install superSU + busybox v1.20.2 from Linus Yang.- Root_Superuser_3.1.3_Busybox_1.20.2-Update1-signed.zip if you prefer the classic ChainsDD superuser + Busybox from Linus Yang.- Root_Busybox_1.20.2_Only_XXX.zip to install only Busybox from Linus Yang.
I advise Chainfire SuperSU for 2 reasons: it lets you unroot from within superSU application and it lets you migrate to ChainsDD superuser if you like later
.
Copy the Root_XXX.zip file you downloaded to externalsd card
Boot into stock recovery (volume up+home+power), and select "apply update from external storage". Now select the Root_XXX.zip file downloaded above and you are rooted
To unroot, do the above steps and replace the file Root_XXX.zip by the attached Unroot_SuperUser-Busybox-Uninstaller-Update2-signed.zip. It will delete superuser, su and busybox packages.
For a complete removal of busybox, look here at my Busybox Uninstaller which will remove ALL busybox symlinks (over 600 files depending on installers used before):
http://forum.xda-developers.com/showthread.php?t=1853419
To get temporary cwm (to make nandroid backups...) or if stock recovery gives you a signature error, follow the next more universal steps.
Click to expand...
Click to collapse
.
.
For most (if not all?) ICS phones having a CWM image at Clockworkmod site:
Download attached cwm-touch-6.0.x.x-i9100.zip for the i9100 Galaxy S2. This is the touch version but it also works with volume up/down keys and power button to select menu.
CWM6 is now thought to be probably safe for wipe, no superbrick risks under ICS 4.0.4: read more here
I also attached the cwm6 non touch version and the recovery-clockwork-4.0.1.5-galaxys2.zip. CWM4 is also confirmed to be safe for wipe by Entropy512 Recognized Developer
For other phones, download the cwm image from here http://clockworkmod.com/rommanager
.
Put the previously downloaded cwm-touch-6.0.x.x-i9100.zip file on your external sd card
Download the attached root file you want as per instructions above
I advise Chainfire SuperSU for 2 reasons: it lets you unroot from within superSU application and it lets you migrate to ChainsDD superuser if you like later
Copy the Root_XXX.zip file you downloaded to internal or external sd card
Boot into stock recovery (volume up+home+power), and select "apply update from external storage". Now select the cwm-touch-6.x.x.x-i9100.zip file you copied in previous step (this step gives a temporary flash that will disappear after reboot)
You get CWM recovery interface (this custom recovery is temporary, not permanent)
Inside CWM, select "install zip from sdcard". Then, select "choose zip from sdcard". Now, scroll down to the "Root_XXX.zip" file and hit power button to install it.
It will add SuperSU or Superuser last version apk to system/app, last superuser binary (su) to system/xbin and busybox last version to system/xbin, all with correct file permissions.
Reboot and you get permanent root + busybox installed on your stock kernel.
To unroot, do the above steps and replace the file Root_XXX.zip by the attached Unroot_SuperUser-Busybox-Uninstaller-Update2-signed.zip. It will delete superuser, su and busybox packages.
For a complete removal of busybox, look here at my Busybox Uninstaller which will remove ALL busybox symlinks (over 600 files depending on installers used before):
http://forum.xda-developers.com/showthread.php?t=1853419
Click to expand...
Click to collapse
Fix common issues: You end with both ChainsDD and Chainfire superuser and SuperSU
Also another symptom is having constantly superuser asking for updates from market.
Some people are getting duplicates from previous root methods using ChainsDD superuser instead of Chainfire superSU or vice versa when they come from SuperSU and switch to superuser.
Also, this can happen when you updated let's say to a future Chainfire SuperSU v1.0 and later you use one of my outdated scripts (with version 0.94 for example).
The cause is that I do not delete anything from /data/app. I can add it, it is not an issue, but till these brick things are fixed, I chose not to do it.
The solution is very easy:
Just uninstall from stock application manager all superuser applications. The /system/app application will stay as system applications cannot be removed normally in application manager
After that, just update your superuser application from market. Updates are put in /data/app and original copy will stay in /system/app.
Click to expand...
Click to collapse
Method 2
CF_Root + stock kernel + [optional] Mobile Odin Free version
Here, you use an older CF_Root kernel, and flash your newer stock kernel
First, get a CF_Root kernel from CF_Root thread here http://forum.xda-developers.com/showthread.php?t=1103399. Just get the nearest one to your ROM. You can download any ICS kernel, it will do the job for the root only purpose
Flash the CF_Root kernel with odin
Now, flash again your stock kernel with odin. You can get a stock kernel from lyriquidperfection thread http://forum.xda-developers.com/showthread.php?t=1619525
Do not forget to thank / donate to him
No stock kernels for you? use Mobile Odin free version (see below)
After flashing the stock kernel, root will usually stay and you will be reverted back to your stock recovery instead of CWM recovery
Click to expand...
Click to collapse
Method 3
Insecure Kernels + SuperOneClick + [optional] Mobile Odin Free
Not tested by me. You get superuser instead of Chainfire superSU + an older busybox
First, get an insecure kernel from here http://forum.xda-developers.com/showthread.php?t=1619525
Do not forget to thank/donate lyriquidperfection
No insecure kernel for your ROM? Just try a kernel from same ICS version, it usually works fine for rooting
Flash the insecure kernel with odin
Download SuperOneClick v2.3.3 from here http://shortfuse.org/?p=193 and look at this thread for an overview: http://forum.xda-developers.com/showthread.php?t=803682
Put your phone on USB debugging mode (System Settings / Developer Options)
Launch SuperOneClick and root using auto or psneuter method. Do not use the ZergRush Exploit as it is meant for older exploited GB versions
Now, flash again your stock kernel with odin. You can get a stock kernel from lyriquidperfection thread http://forum.xda-developers.com/showthread.php?t=1619525
Do not forget to thank / donate to him
No stock kernel for your ROM? Use Mobile Odin Free version (see below)
Click to expand...
Click to collapse
Method 4
Insecure Kernels + S2 Root - For SAMSUNG Devices
The tool and all instructions are on lyriquidperfection thread:
http://forum.xda-developers.com/showthread.php?t=1125414
It will do the same as in method 3, but using a newer and better supported tool than SuperOneClick
You have to flash an insecure kernel, root with S2Root and flash again your stock kernel
It roots using Chainfire SuperSU and busybox 1.20.1 at time of posting
Author is a recognized developer and offers great support
You are still depending on author to release a custom kernel for all your new ROMs
Click to expand...
Click to collapse
Mobile Odin Free version
Flash your stock kernel from complete ROM file
Now that Intratech stopped releasing stock kernels in his thread, rooting using methods 2 and 3 can be a problem. In fact, you will not be able to flash your newer original stock kernel after rooting with insecure or cf_root older kernel. You can look in above lyriquidperfection thread for a stock kernel to flash in odin. But, if you do not like to wait for him to release a kernel, you can get Mobile Odin Free version
Download Mobile Odin Free version from here http://forum.xda-developers.com/showthread.php?t=1347899
Do not forget to thank donate to Chainfire
From your stock tar.md5 ROM file, extract the zimage file (your stock kernel)
Put zimage file on external sd card
Run Mobile Odin and specify the zimage file in kernel box like in this image:
Flash, you get your stock kernel and root is normally left
Click to expand...
Click to collapse
Mobile Odin Pro (Payed) version
Root + Flash - You should consider buying it.
With this method, you will have SuperSU from chainfire (that can be updated from market) but no Busybox.
You can install busybox from market or from attached CWM_Root_Busybox_1.20.2_Only_(No_SuperSU)-S2-Update2-signed.zip file in this thread
Buy Mobile Odin Pro from market here https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro
If you want to flash a full new rom, put the tar file on the external_sd. Point all boxes to the ROM tar file. Enable EverRoot option like in image below. Flash
If you flashed your ROM using odin and only want to root, proceed like in Example 4 above to flash only the kernel (zimage file from your actual ROM). Enable EverRoot option and flash
Now, install BusyBox from market or flash my CWM_Root_Busybox_1.20.2_Only_(No_SuperSU)-S2-Update2-signed.zip file with cwm to get last busybox.
Click to expand...
Click to collapse
Chainfire - adbd Insecure app
Getting switchable insecure kernel WITH stock kernel
One of the advantages for some people in CF_Root kernel is the insecure mode. Now, you can have insecure kernel like behavior without flashing a custom kernel. There is a magic app for that, signed Chainfire.
Thread + free download link here:
http://forum.xda-developers.com/showthread.php?t=1687590
And you can buy it from market to support author:
https://play.google.com/store/apps/details?id=eu.chainfire.adbd
Instructions, quoted from chainfire
If you are running a stock (made by the phone manufacturer) kernel on your device, chances are adbd is running in "secure" mode, even if you are rooted. This app lets you run adbd in "insecure" mode, which gives you root access in "adb shell", allows access to system files and directories through "adb push/pull", and lets you run the "adb remount" command to make your /system partition writable.
Of course, your device must already be rooted for this to work. It may not work with "S-ON" devices and locked bootloaders.
This app does not make any permanent changes to your device - a reboot will undo any modification. That's why there is also the option to enable this feature at boot.
Note that if you have USB connected when the app activates or deactivates adbd root mode, you may need to unplug/replug the cable or run "adb kill-server" on your computer before adb will work again.
Click to expand...
Click to collapse
Feel free to comment or suggest enhancements
Big Thanks! Very usefull post.
Links seems down. Ive took it from Your post #382 in http://forum.xda-developers.com/showthread.php?t=1501719&page=39
Method #1 working very well with LPD kernel. Thanks Again.
Yes, sorry
It is a forum problem, hope it is fixed. I will update it as soon as it is fixed
While waiting for forum to fix my attachments, I edited post 1 with mediafire mirrors to the files
Sorry
nabuhonodozor said:
Big Thanks! Very usefull post.
Links seems down. Ive took it from Your post #382 in http://forum.xda-developers.com/showthread.php?t=1501719&page=39
Method #1 working very well with LPD kernel. Thanks Again.
Click to expand...
Click to collapse
Happy it helped
Hi, I always install new ics Sammy roms using Mobile Odin pro, but didn't know that busybox wasn't installed, so I need to know what is the point of installing it? What is the real use of busybox? I've been using my s2 rooted just with mobile Odin pro without any issue... Every root app that I need like titanium backup, root explorer, etc. Are working great, so I don't know what busybox is for...
Sorry for the dumb question and thanks in advance for the help!
Enviado desde mi GT-I9100 usando Tapatalk 2
Maybe you once installed a CF_Root or other kernel that comes with busybox
If you do not format /system, most system apps are kept, include busybox
Titanium backup uses its internal busybox version, not the /system one
Root explorer does not use busybox I think, but not sure
To know if it is installed or not, look for busybox file in /system/xbin or /system/bin
thanks ,hey can you also post way to change cf root's recovery (non touchable) to tuch recovery that would be really awesome :highfive:
apk_xiz said:
thanks ,hey can you also post way to change cf root's recovery (non touchable) to tuch recovery that would be really awesome :highfive:
Click to expand...
Click to collapse
This is not cf_root or a kernel, sorry
CWM from cf_root is proprietary coded by Chainfire
Phil3759 said:
This is not cf_root or a kernel, sorry
CWM from cf_root is proprietary coded by Chainfire
Click to expand...
Click to collapse
oh ok my bad
Phil3759 said:
Maybe you once installed a CF_Root or other kernel that comes with busybox
If you do not format /system, most system apps are kept, include busybox
Titanium backup uses its internal busybox version, not the /system one
Root explorer does not use busybox I think, but not sure
To know if it is installed or not, look for busybox file in /system/xbin or /system/bin
Click to expand...
Click to collapse
OK, thanks a lot for the help!
Enviado desde mi GT-I9100 usando Tapatalk 2
apk_xiz said:
oh ok my bad
Click to expand...
Click to collapse
Unless you frequently use cwm, there is really no need to use cf_root. Only really missing thing is insecure kernel to have adb access as root. I will edit post 1 for adding insecure behavior without flashing
Sent from my GT-I9100 using Tapatalk 2
Done,
I added a paragraph at the end with instructions to have adb shell root access like in insecure kernels
Updated first post with new SuperSU 0.93
If you already used this method, no need to flash again, just open superSU and update through market. After that, open app and it will update the su binary
i think guides belong in the general section
nice guide though
Forum attachments are fixed now
You can download again from forum, but I will keep mediafire mirrors
edit 2: fixed the 0kb download attachments corrupted uploads when forum was broken
Mobile Odin
Thanks for the great guide Phil. A couple of questions..
I have Mobile Odin Pro and I want CWM as well so i have to do this?
Flash new rom with superuser injected, cwm manager and everoot ticked.
Flash CWM with instructions from 1st method
Flash with CWM CWM_Busybox_Only_1.20.1.zip
thats it? I guess this emulates a CF-ROOT kernel right?
thanks again.
No, Chainfire CWM manager app will detect a CF_Root kernel and refuse to launch if another kernel is there
Only CF_Root has Chainfire CWM, a custom written CWM
Other kernels include custom CWM too, look for them
The CWM image here will give you all functions from the original CWM project, but you need to launch it from stock recovery. Just keep the zip on your external sd card, that's it, only more 2 clicks. At the end, you get all CWM functions
Phil3759 said:
No, Chainfire CWM manager app will detect a CF_Root kernel and refuse to launch if another kernel is there
Only CF_Root has Chainfire CWM, a custom written CWM
Other kernels include custom CWM too, look for them
The CWM image here will give you all functions from the original CWM project, but you need to launch it from stock recovery. Just keep the zip on your external sd card, that's it, only more 2 clicks. At the end, you get all CWM functions
Click to expand...
Click to collapse
I see. I won't tick cwm manager and install the original CWM.
Thanks bro.
borolo222 said:
I see. I won't tick cwm manager and install the original CWM.
Thanks bro.
Click to expand...
Click to collapse
In any case, you need CWM image for the method in post 1
From CWM, you flash root file
But on reboot, you will still have your original stock recovery. To launch CWM, you have to launch it from your stock recovery
Hi,
what started as an Idea seems to be working now. For once i wanted a phone that has warranty for more than two weeks (or at least a chance for warranty).
DISCLAIMER:
Do all of this at your own risk. Even though we will not be flashing a custom recovery, technically the warranty is lost the moment you root your phone.
None of the Tools is actually written by me, i just tinkered a bit and came up with this tutorial.
1. You will need
- Galaxy A3 (mine was an A300FU but i guess every one that can be rooted without flashing should do) on Lollipop (5.0.2).
- Minimal ADB or some other software that brings debugging drivers and adb.
- KingRoot 4.60+
- SuperSu-ME (from play Store or an older version is also fine) or any other way to go from the Kinguser Root Management to SuperSU
- Deodexed apks matching you phone model
- Flashfire Beta
- Xposed Installer, I used 3.0alpha4
- Xposed bridge for Samsung lollipop I used xposed-v75-sdk21-arm-arter97-snapdragon_requestConcurrentGC
2. If something goes wrong:
- Odin and a stock LOLLIPOP ROM for your device!
This is Important: Since we dont have a custom recovery, whenever something goes wrong the only rescue is going back to a stock rom and thereby wiping. If everything works in the first go there will be no wipe.
3. Rooting
First we need to root. Thanks to KingRoot thats very easy and just a matter of waiting. Install KingRoot (has to be 4.60+ for Lollipop), Click try to Root, wait for it, done. Know we need to get rid of the KingRoot stuff again and install SuperSU (FlashFire does not support KingUser but SuperSU) thats what we need SuperSU-ME for. There Will be some Left overs since KingRoot converts itself to a system app, you can remove this with Titanium Backup or a ROM Toolbox of you choice.
4. Deodexing
Next step is gonna be Deodexing. This one is a little Tricky without a Custom Recovery. Flashing the Deodex using FlashFire will leave you stuck at the Boot Logo.
Unpack the Flashable Deodex zip. you#ll find a META-INF and a system folder. Copy the system folder (or rename it, doesnt matter) to your SDcard or the phone memory using USB. At this point you can also copy the two Xposed files (zip+apk). Next we need USB Debugging. Install the minimal ADB, browse to the install location and start "adb devices" once (this will start the daemon). Now take your phone, browse to settings / phone info and tap the build number like 10 times (this gives you developers options) now go to settings / developers options and enable USB debugging.
Connect you phone via USB. This hould bring up a dialog granting your PC permission to connect. Click Yes.
Connect to the phone and request root using
Code:
adb shell
su
Now turn on the phones screen there should be a root request, allow it.
Next is the following commands, assuming the location of the extracted system folder is /storage/extSdCard/deodex_system
Code:
mount -o rw,remount /system
rm -Rf /system/app
rm -Rf /system/priv-app
rm -Rf /system/framework
cp -R /storage/extSdCard/deodex_system/* /system
chown -R root:root /system/app
chown -R root:root /system/priv-app
chown -R root:root /system/framework
chmod -R 755 /system/app
chmod -R 755 /system/priv-app
chmod -R 755 /system/framework
rm -Rf /data/dalvik-cache/*
reboot
This will replace all system apks with the deodexed ones, sets the right owner and permissions, clears the dalvik cache and reboots. Booting is gonna take a while and then you're enjoying you're rooted, deodexed stock ROM without flashing anything so far. So now about installing Xposed.
Don't be to slow with thus step. Deleting the three folders will make the phone go crazy and at some point reboot, you should be done by then.
Edit: I did this on a second device now, for some reason the remount did not work. In this case try disabling SElinux (http://forum.xda-developers.com/devdb/project/dl/?id=12178) and then remount.
5. Xposed
Install the XposedInstaller apk file like any other app, no need to start it yet. Next install FlashFire and launch it (granting root access) now select the Option "OTA or ZIP" in Flashfire and select the flashable Xposed zip you downloaded earlier. No further settings needed just hit Flash! The next reboot is again gonna take a while, but after that you can launch the Xposed Installer and start Installing Modules. We're done.
Whenever you do a factory reset (from the recovery), You need to root again using Kingroot, replace it with SuperSU and install Xposed again.
Once more, I did not develop any of the tools mentioned, all credits to their respective authors.
Cheers,
prometh
Edit: I did not try too many modules yet but Wanam for lollipop works just fine and that useless S Whatever bar is a thing of the past
Hi.
I already have a rooted Galaxy A3 (A300FU) and I have TWRP as my recovery so my warranty is already gone and I'm not too worried about that. However I have had no success at trying to deodex my rom to be able to install xposed.
Would it be possible to just flash the deodexed and the xposed zip from TWRP? And with regards to the deodexed zip would it matter if I flash it over the top of my current rom when I'm using a carrier rom rather than the BTU unlocked rom?
Squall88uk said:
Hi.
I already have a rooted Galaxy A3 (A300FU) and I have TWRP as my recovery so my warranty is already gone and I'm not too worried about that. However I have had no success at trying to deodex my rom to be able to install xposed.
Would it be possible to just flash the deodexed and the xposed zip from TWRP? And with regards to the deodexed zip would it matter if I flash it over the top of my current rom when I'm using a carrier rom rather than the BTU unlocked rom?
Click to expand...
Click to collapse
I think this would be a question for the deodex thread I linked but heres my 5 cents: The procedure in your case should be Flashing Deodex (eventually also gapps_replacement from that thread if you get Google Apps FCs) flashing Xposed, booting, installing the xposed installer. The Deodexed zip is meant to be flashed on top of your system. What I described is basically doing manually what the deodex zip file would do (deleting copying...). Since you have twrp already, I guess a system backup wouldn't hurt.
Many thanks for the help. I'll make a nandroid backup of system first just in case and then give it a go.
Thanks again.
Impossible with my SG A3 A300FU
Hello, I already have the root and TWRP installed, but if I try to type the command line with ADB it doesn't work and if I flash the zip, it doesn't work too. Any Idee ? With the first or the second method boot loop with the samsung logo !!
darwin345 said:
Hello, I already have the root and TWRP installed, but if I try to type the command line with ADB it doesn't work and if I flash the zip, it doesn't work too. Any Idee ? With the first or the second method boot loop with the samsung logo !!
Click to expand...
Click to collapse
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Great work prometh696 !!! I managed to get xposed on my A5 with knox 0x0 !!!
Some other steps I followed to get it for my A500FU; first I extracted my own system folders system/app/, system/framework/ & system/priv-app/ with root explorer to my ext SD card and then copied it to my computer.
On the computer I batch deodexed those folders with joeldroid's batch deodexer:
http://forum.xda-developers.com/and.../script-app-joeldroid-lollipop-batch-t2980857
Had some issues there as not every Java version seems to deliver the deodexed folders without errors; more details in that topic.
Then I followed your adb commands and installed xposed, and as you said, knox didn't change and is still 0x0 !!!
Thanks again !!!
---------- Post added at 01:30 PM ---------- Previous post was at 01:06 PM ----------
prometh696 said:
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Click to expand...
Click to collapse
The command lines are for copying the deodexed apks (so not in a zip). The zip is for xposed and is flashed by flashfire.
But as he already got TWRP (and thus knox 0x1) I see no use for him to use your method anyway
prometh696 said:
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Click to expand...
Click to collapse
When I type the first command line after this one "rm -Rf /system/priv-app" or this one "rm -Rf /system/framework" I don't know when exactly my phone reboot and bootloop on samsung logo (dynamic one) ???
My mobile restart before end of commands line
Hi,
your solution seems really good but my mobile (A300FU) is retarting before I typed all commands line.
Do you know a solution ?
Maybe cause I've no ExtSDcard and use the internal card ?
Thank you for your help !!
Regards
Virtua
update : I tried with trwp and made the necessary but the mobile does not boot.
This phone is a mess
It's the first time I can't do what I want with a phone. All posts seems to be a hoax. ;( ;(
Whenever you do a factory reset (from the recovery), You need to root again using Kingroot, replace it with SuperSU and install Xposed again.
Click to expand...
Click to collapse
This is actually incorrect unless root is systemless.
Root remains in system, and so does xposed. A factory reset does not touch the system partition.
You lose root after a reset because you need to reinstall superuser. If you make it a system app you won't lose root even after a reset.
The same with xposed just reinstall the apk.
Code:
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any doubts about rooting
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
{
"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"
}
There are lot of Guides Available for Rooting Grand 2. But I'm sharing this for the people who don't have a pc and want their phone rooted safe.
I have tried this several times, and I'm sure it is safe. Eventhough there is a chance of soft brick.
Note: This Guide is only for Samsung Galaxy Grand 2 SM-G7102 which is running on Kitkat 4.4.2 stock Rom. You can try on other devices on your own risk.
*--------------------------*
DOWNLOADS
For Method - 1
Kingroot
SuperSu-Me
For Method - 2
Flashify
Rashr (optional)
SuperSu v2.52 Beta
Recoveries
CWM by Mukulsoni
TWRP by Aapav
Philz Touch by Ali.filth
*--------------------------*
Method - 1
1. Download Kingroot App and Root your phone with it.
(Kingroot is not a safe app and it is highly vulnerable, Hackers can easily hack your phone when using Kingroot as superuser app. Eventhough with kingroot you can easily root your phone without pc)
Download Kingroot
Don't know how to root with Kingroot?
*Download and install the KingRoot app as you would do with any normal app.
"Launch the KingRoot app from the app drawer.
*A 'Try to Root' button will appear at the bottom of the screen. Just tap this button and let the rooting process complete.
*After the device is rooted, a success message will appear on the screen.
Done!
Click to expand...
Click to collapse
2. Reboot (important)
3. Download 'Supersu-me' App.
See this thread to know more
or Buy Pro Version
Buy or Google it [emoji14] it's against xda rules providing free download link for a premium app.
note: SuperSu-me Please App Developed by XDA Devolopers. They decided as a team to take on the challenge and come out with this script that will completely remove all of the KingRoot applications and put SuperSU on our device.
all credits goes to them.
4. Install SuperSu-Me.. open it, it will ask for root permission, Grant it.
5. Then press Blue Button
It will take a while. The app will automatically remove Kingroot file from our phone and replace Kingroot with supersu.
6. Reboot
Enjoy having root privileges
Note: if the Kingroot app still remains after all these steps, uninstall it manually.
In some cases, you may lose root privileges after using supersume. In such cases, open SuperSu(not Supersu-me) settings> full unroot. Then Repeat all the steps again.
After doing all these steps, you can use flashify app to flash custom Recoveries and other stuffs. But Read some guides before using these apps
Flashify : https://play.google.com/store/apps/details?id=com.cgollner.flashify
Rashr (An alternate app for flashing Recoveries and zip files as same as flashify) :-
Play store link : https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Note : These apps could brick your device if you use it wrong. so careful.
- RECOVERIES -
CWM
TWRP
Philz Touch
I personally recommend CWM for beginners.
*-------------------------------*
Method - 2
This method is more complicated
Note - I haven't tried this step on Grand 2 kitkat. But tried on several other devices. every time it worked. it should work on grand 2 stock firmware too.
1. Download Kingroot App and Root your phone with it.
2. Download Flashify from playstore
Link: https://play.google.com/store/apps/details?id=com.cgollner.flashify
3. Download a recovery (links are mentioned above)
*I recommend twrp for this method.
4. Download Supersu 2.52 flashable zip
link: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
5. Open flashify, it will ask for root permission. Grant it.
We can flash recovery with flashify using 2 methods. they are
(i) flashing Zip file method
(ii)flashing img file method
only try 2nd method if 1st fails
first we try (i) flashing Zip file method
'Boot Image, Recovery Image and Zip File' are the three main options you find in flashify.
Select Zip file option > choose a file > find Recovery.zip(recovery flashable zip file ) from the folder you downloaded and select it > Yup! (ofcourse Yup! is an option lol) > Copy First > Reboot.
if you have done all steps properly, it will automatically reboot to recovery and flash zip file which will replace the stock recovery.
some times Zip file method fails, in such case we can try (ii)flashing img file method.
first of all go to file manager and find the recovery zip file you downloaded, extract it. inside the extracted folder, you will find a file named recovery.img
open flashify > Recovery Image > Choose a file (browse and find recovery.img file you extracted and then select it) > Normal Android Way > Yup! > Reboot
Phone will reboot.
after recovery has flashed using flashify, open flashify again > touch the 3dot menu on the top right corner > select Reboot Recovery. phone will reboot to recovery. from there select Install zip and flash recovery.zip again (because recoveries that flashed through flashify are not at all stable, sometimes it fails to boot manually using power+volumeup key combinations. so you should flash recovery, from recovery using flashable zip file) see some guides how to flash zip file using recovery.
6. Reboot to Recovery
You can boot to recovery using power+volumeup key combinations.
OR
open flashify> 3dot menu > Reboot Recovery
7. Install Zip > BETA-SuperSU-v2.52.zip (supersu file you have dowloaded first)
it will take a while
Supersu Beta 2.52 version have scripts included to remove Kingroot automatically. Flashing BETA-SuperSU-v2.52.zip will automatically remove Kingroot and replaces with supersu
After flashing finished, reboot the phone and open Supersu. See whether it working properly. if no error message shown, You have rooted your phone successfully.
Post your doubts and comments here.
hit thanks button if helped.
Nice post but I am already use this thanx dear
Sent from my SM-G7102 using Tapatalk
JAMESAMEES said:
Nice post but I am already use this thanx dear
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
hit thanks button then ??
yub
JitDevHacker said:
hit thanks button then
Click to expand...
Click to collapse
you deserve it
digitman xxx said:
you deserve it
Click to expand...
Click to collapse
lol
you are distributing apk for a paid app,distributing cracked apk for paid apps is strictly prohibited on xda.
Requesting you to remove it asap.
neonkat said:
you are distributing apk for a paid app,distributing cracked apk for paid apps is strictly prohibited on xda.
Requesting you to remove it asap.
Click to expand...
Click to collapse
Removed
EDIT: Method 2 added to post #1
JitDevHacker said:
EDIT: Method 2 added to post #1
Click to expand...
Click to collapse
Rooting your device through king root is safe and easy one
aryalmuskan17 said:
Rooting your device through king root is safe and easy one
Click to expand...
Click to collapse
not safe,that makes your device vulnerable.
aryalmuskan17 said:
Rooting your device through king root is safe and easy one
Click to expand...
Click to collapse
Easy to Root without pc. but vulnerable. flash supersu v2.52 beta as long as possible after rooted with Kingroot.
neonkat said:
not safe,that makes your device vulnerable.
Click to expand...
Click to collapse
what is vulnerable??
aryalmuskan17 said:
what is vulnerable??
Click to expand...
Click to collapse
Kingroot is Vulnerable. you should replace Kingroot with supersu
JitDevHacker said:
Code:
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any doubts about rooting
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
There are lot of Guides Available for Rooting Grand 2. But I'm sharing this for the people who don't have a pc and want their phone rooted safe.
I have tried this several times, and I'm sure it is safe. Eventhough there is a chance of soft brick.
Note: This Guide is only for Samsung Galaxy Grand 2 SM-G7102 which is running on Kitkat 4.4.2 stock Rom. You can try on other devices on your own risk.
*--------------------------*
DOWNLOADS
For Method - 1
Kingroot
SuperSu-Me
For Method - 2
Flashify
Rashr (optional)
SuperSu v2.52 Beta
Recoveries
CWM by Mukulsoni
TWRP by Aapav
Philz Touch by Ali.filth
*--------------------------*
Method - 1
1. Download Kingroot App and Root your phone with it.
(Kingroot is not a safe app and it is highly vulnerable, Hackers can easily hack your phone when using Kingroot as superuser app. Eventhough with kingroot you can easily root your phone without pc)
Download Kingroot
2. Reboot (important)
3. Download 'Supersu-me' App.
See this thread to know more
or Buy Pro Version
Buy or Google it [emoji14] it's against xda rules providing free download link for a premium app.
note: SuperSu-me Please App Developed by XDA Devolopers. They decided as a team to take on the challenge and come out with this script that will completely remove all of the KingRoot applications and put SuperSU on our device.
all credits goes to them.
4. Install SuperSu-Me.. open it, it will ask for root permission, Grant it.
5. Then press Blue Button
It will take a while. The app will automatically remove Kingroot file from our phone and replace Kingroot with supersu.
6. Reboot
Enjoy having root privileges
Note: if the Kingroot app still remains after all these steps, uninstall it manually.
In some cases, you may lose root privileges after using supersume. In such cases, open SuperSu(not Supersu-me) settings> full unroot. Then Repeat all the steps again.
After doing all these steps, you can use flashify app to flash custom Recoveries and other stuffs. But Read some guides before using these apps
Flashify : https://play.google.com/store/apps/details?id=com.cgollner.flashify
Rashr (An alternate app for flashing Recoveries and zip files as same as flashify) :-
Play store link : https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Note : These apps could brick your device if you use it wrong. so careful.
- RECOVERIES -
CWM
TWRP
Philz Touch
I personally recommend CWM for beginners.
*-------------------------------*
Method - 2
This method is more complicated
Note - I haven't tried this step on Grand 2 kitkat. But tried on several other devices. every time it worked. it should work on grand 2 stock firmware too.
1. Download Kingroot App and Root your phone with it.
2. Download Flashify from playstore
Link: https://play.google.com/store/apps/details?id=com.cgollner.flashify
3. Download a recovery (links are mentioned above)
*I recommend twrp for this method.
4. Download Supersu 2.52 flashable zip
link: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
5. Open flashify, it will ask for root permission. Grant it.
We can flash recovery with flashify using 2 methods. they are
(i) flashing Zip file method
(ii)flashing img file method
only try 2nd method if 1st fails
first we try (i) flashing Zip file method
'Boot Image, Recovery Image and Zip File' are the three main options you find in flashify.
Select Zip file option > choose a file > find Recovery.zip(recovery flashable zip file ) from the folder you downloaded and select it > Yup! (ofcourse Yup! is an option lol) > Copy First > Reboot.
if you have done all steps properly, it will automatically reboot to recovery and flash zip file which will replace the stock recovery.
some times Zip file method fails, in such case we can try (ii)flashing img file method.
first of all go to file manager and find the recovery zip file you downloaded, extract it. inside the extracted folder, you will find a file named recovery.img
open flashify > Recovery Image > Choose a file (browse and find recovery.img file you extracted and then select it) > Normal Android Way > Yup! > Reboot
Phone will reboot.
after recovery has flashed using flashify, open flashify again > touch the 3dot menu on the top right corner > select Reboot Recovery. phone will reboot to recovery. from there select Install zip and flash recovery.zip again (because recoveries that flashed through flashify are not at all stable, sometimes it fails to boot manually using power+volumeup key combinations. so you should flash recovery, from recovery using flashable zip file) see some guides how to flash zip file using recovery.
6. Reboot to Recovery
You can boot to recovery using power+volumeup key combinations.
OR
open flashify> 3dot menu > Reboot Recovery
7. Install Zip > BETA-SuperSU-v2.52.zip (supersu file you have dowloaded first)
it will take a while
Supersu Beta 2.52 version have scripts included to remove Kingroot automatically. Flashing BETA-SuperSU-v2.52.zip will automatically remove Kingroot and replaces with supersu
After flashing finished, reboot the phone and open Supersu. See whether it working properly. if no error message shown, You have rooted your phone successfully.
Post your doubts and comments here.
hit thanks button if helped.
Click to expand...
Click to collapse
I have successfully Root. But run SuperSU to uninstall the failed kingroot
I installed 4.6.5 kingroot
Drthanh77 said:
I have successfully Root. But run SuperSU to uninstall the failed kingroot
I installed 4.6.5 kingroot
Click to expand...
Click to collapse
Try Method 2. Flash SuperSu v2.52 using recovery
@Drthanh77 Don't qoute post #1 please. but feel free to ask your doubts.
Sent from my SM-G7102 using Tapatalk
JitDevHacker said:
@Drthanh77 Don't qoute post #1 please. but feel free to ask your doubts.
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Thanks You verry much
despite a successful installation with SuperSU-v2.55.zip. But SuperSU-v2.55 remain inactive and not removed by Kingroot
Drthanh77 said:
Thanks You verry much
despite a successful installation with SuperSU-v2.55.zip. But SuperSU-v2.55 remain inactive and not removed by Kingroot
Click to expand...
Click to collapse
Use supersu-me
Sent from my SM-G7102 using Tapatalk
How
---------- Post added at 09:00 PM ---------- Previous post was at 08:58 PM ----------
I got a message to update su binary after I installed super sume, what could be wrong?
If u have problem with supersu. Delete and remove root from kingroot and then flash the supersu zip
Hello guys,
i've ended in here from another thread which is locked LINK
As the OP of the thread, i've tried several 1-CLICK root apps (both Android and PC) with no luck (Mine is also as gift from mobile carrier).
I have screenshot of "Version" sub-menu, from something called "Factory mode" also i can access the tablet via fastboot and adb (see attached pictures)
Any suggestions?
No one?
I root it using http://www.kingroot.net for PC. Enable. Developers option, then adb USB whatever it was... And should work.
Sent from my QC-703GN using Tapatalk
mefistoreyon said:
I root it using http://www.kingroot.net for PC. Enable. Developers option, then adb USB whatever it was... And should work.
Sent from my QC-703GN using Tapatalk
Click to expand...
Click to collapse
Well it doesn't. I can't tell why, cuz is in Chinese.
soadfan said:
Hello guys,
i've ended in here from another thread which is locked LINK
As the OP of the thread, i've tried several 1-CLICK root apps (both Android and PC) with no luck (Mine is also as gift from mobile carrier).
I have screenshot of "Version" sub-menu, from something called "Factory mode" also i can access the tablet via fastboot and adb (see attached pictures)
Any suggestions?
Click to expand...
Click to collapse
Ways to root:
KingRoot
Flash with Recovery supersu
Use Framaroot.
Mempler said:
Ways to root:
KingRoot
Flash with Recovery supersu
Use Framaroot.
Click to expand...
Click to collapse
Well... Kingroot worked yesterday. Idk is because i've downloaded latest version or that i've added it as device administrator (also disabled built-in app permission manager).
Now how to replace kingroot with super su? I tried both Super-sume and mrw v2.4 with no luck.
First flash TWRP with the TWRP manager then install root browser goto /system/app delete kinguser restart your phone goto recovery and flash the supersu update
Mempler said:
First flash TWRP with the TWRP manager then install root browser goto /system/app delete kinguser restart your phone goto recovery and flash the supersu update
Click to expand...
Click to collapse
Well...it isn't supported. Is there generic recovery that can be used on various devices based on...idk, chipset?
fyi
I've managed to do it. idk exactly how.
Tried again this mrw (v.2.4) in the root of the sdcard. i'm not running *.sh files from terminal emulator, but via root explorer's script executor.
This time i've mounted /system RW before starting the procedure (found this tip in a lenovo a5000 tutorial that i saved in the past. It can be done via terminal emulator or with app like root essentials).
This time looked like the script hanged, king root has stopped several times and finally "executing script" popup disappeared.
However tried to install SuperSU manual (because script failed)
Then SuperSU returned that kingroot is still present in the system and can try to uninstall it (last time this did unroot the tablet), but with /system mounted RW i decided to give it a try.
Well, now i have fully functional SuperSU and root.
Any TWRP for Umidigi One Pro that is able to read the /data partition ?
Edit:Solved
Ghost505 said:
Any TWRP for Umidigi One Pro that is able to read the /data partition ?
Edit:Solved
Click to expand...
Click to collapse
What was the solution? I didn't even know we had a twrp!
http://community.umidigi.com/forum.php?mod=viewthread&tid=2962&extra=page=1
https://forum.xda-developers.com/android/development/twrp-umidigi-z2-z2-special-edition-t3842866
Best twrp found here : http://community.umidigi.com/forum.php?mod=viewthread&tid=17560&extra=page=1
Hey, What is your device Android version?
Android 8.1
For those with Umidigi One / One Pro or Z2
0. Install twrp from first link
---
(second link)
1. now we need to edit the fstab file
because its a MTK device your fstab file looks like fstab.mt6763 or simliar
2. Download Mixplorer from XDA Thread. ( this root explorer is the best because it set permission automaticly.)
3. open mixplorer and browse to root/system/vendor/etc/fstab.mt6763..
4 open that file and search for ( should be line 15)
/dev/block/platform/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,errors=panic wait,check,quota,formattable,resize,forceencrypt=/dev/block/platform/bootdevice/by-name/metadata,
Click to expand...
Click to collapse
5. edit the file to this
/dev/block/platform/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,errors=panic wait,check,quota,formattable,resize,encryptable=/dev/block/platform/bootdevice/by-name/userdata,
Click to expand...
Click to collapse
6.save and turn off the phone
---
7. Wipe Data from device and enter in the phone again and no more encryption so twrp will be able to access the data partition.
Ghost505 said:
http://community.umidigi.com/forum.php?mod=viewthread&tid=2962&extra=page=1
https://forum.xda-developers.com/android/development/twrp-umidigi-z2-z2-special-edition-t3842866
Click to expand...
Click to collapse
Thanks for the info, I'll give it a shot soon.
There's no item when I go to root in Mixplorer
Ghost505 said:
Android 8.1
For those with Umidigi One / One Pro or Z2
0. Install twrp from first link
---
(second link)
1. now we need to edit the fstab file
because its a MTK device your fstab file looks like fstab.mt6763 or simliar
2. Download Mixplorer from XDA Thread. ( this root explorer is the best because it set permission automaticly.)
3. open mixplorer and browse to root/system/vendor/etc/fstab.mt6763..
4 open that file and search for ( should be line 15)
5. edit the file to this
6.save and turn off the phone
---
7. Wipe Data from device and enter in the phone again and no more encryption so twrp will be able to access the data partition.
Click to expand...
Click to collapse
Blackchancellor said:
There's no item when I go to root in Mixplorer
Click to expand...
Click to collapse
This means that Mixplorer does not have root permissions to access root folder. Install magisk and try again, if it still does not work and you have root installed, clear data&cache for mixplorer app.
But I can't root the phone. I've tried all, but when I enter twrp it mounting data partition always fails. And TWRP also always only starts the first time after it's been flashed. Next time I start in recovery mode, I just see "No command".
Ghost505 said:
This means that Mixplorer does not have root permissions to access root folder. Install magisk and try again, if it still does not work and you have root installed, clear data&cache for mixplorer app.
Click to expand...
Click to collapse
Blackchancellor said:
But I can't root the phone. I've tried all, but when I enter twrp it mounting data partition always fails. And TWRP also always only starts the first time after it's been flashed. Next time I start in recovery mode, I just see "No command".
Click to expand...
Click to collapse
it is odd on why the recovery partition is being changed to default, do you have root ?
root tutorial
Install magisk manager 6.0.1 apk
Get the boot..img from rom section last update and put it inside phone
Use magisk manager install button to modify boot.img
Extract it to pc and mount it on boot partition in flash tools and only select that partition and click download with phone off
twrp after that link
It didn't work. When I press "install" and select the rom in the file manager, it says "flashing" and then it disapears. Nothing changes
Ghost505 said:
it is odd on why the recovery partition is being changed to default, do you have root ?
root tutorial
Install magisk manager 6.0.1 apk
Get the boot..img from rom section last update and put it inside phone
Use magisk manager install button to modify boot.img
Extract it to pc and mount it on boot partition in flash tools and only select that partition and click download with phone off
twrp after that link
Click to expand...
Click to collapse
Blackchancellor said:
It didn't work. When I press "install" and select the rom in the file manager, it says "flashing" and then it disapears. Nothing changes
Click to expand...
Click to collapse
Try SP_Flash_Tool to root with magisk first
But my main question has always been: hiw to root? I can't mount data partition after flasing twrp so I can't access my files in recovery mode and I can't install magisk
Ghost505 said:
it is odd on why the recovery partition is being changed to default, do you have root ?
root tutorial
Install magisk manager 6.0.1 apk
Get the boot..img from rom section last update and put it inside phone
Use magisk manager install button to modify boot.img
Extract it to pc and mount it on boot partition in flash tools and only select that partition and click download with phone off
twrp after that link
Click to expand...
Click to collapse
Ghost505 said:
Try SP_Flash_Tool to root with magisk first
Click to expand...
Click to collapse
Blackchancellor said:
But my main question has always been: hiw to root? I can't mount data partition after flasing twrp so I can't access my files in recovery mode and I can't install magisk
Click to expand...
Click to collapse
You do not need twrp to root the device, all you need is the sp flash tool and the boot.img from the rom. Also the magisk manager application installed normally.
OK. Could you please help me by explaining step to step how to root using SPFT? Thanks in andvance
Ghost505 said:
You do not need twrp to root the device, all you need is the sp flash tool and the boot.img from the rom. Also the magisk manager application installed normally.
Click to expand...
Click to collapse
Blackchancellor said:
OK. Could you please help me by explaining step to step how to root using SPFT? Thanks in andvance
Click to expand...
Click to collapse
1. install magisk manager apk
2. place boot.img in the downloads folder in the phone
3. press install in magisk manager apk and choose patch boot
4. get the new boot.img file created by magisk manager 6.0.1 and put it in pc and flash it using sp flash tool in boot partition
in here is the boot.img look in it with winrar
Thanks, but where to get this boot.img? Is it from the extracted rom (.rar) files.
Ghost505 said:
You do not need twrp to root the device, all you need is the sp flash tool and the boot.img from the rom. Also the magisk manager application installed normally.
Click to expand...
Click to collapse
Ghost505 said:
1. install magisk manager apk
2. place boot.img in the downloads folder in the phone
3. press install in magisk manager apk and choose patch boot
4. get the new boot.img file created by magisk manager 6.0.1 and put it in pc and flash it using sp flash tool in boot partition
Click to expand...
Click to collapse
It worked. Thanks!
Ghost505 said:
1. install magisk manager apk
2. place boot.img in the downloads folder in the phone
3. press install in magisk manager apk and choose patch boot
4. get the new boot.img file created by magisk manager 6.0.1 and put it in pc and flash it using sp flash tool in boot partition
in here is the boot.img look in it with winrar
Click to expand...
Click to collapse
Phone is now rooted and TWRP installed, but I still can't mount data partition.
Go in ROOT /vendor/etc/fstab.mt6763 with MIXPLORER
Should be on line 15 I think
edit:
/dev/block/platform/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,errors=panic wait,check,quota,formattable,resize,forceencrypt=/dev/block/platform/bootdevice/by-name/metadata,
to:
/dev/block/platform/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,errors=panic wait,check,quota,formattable,resize,encryptable=/dev/block/platform/bootdevice/by-name/userdata,
save and restart phone and wipe data in twrp, everything will be erased, enter in phone after that and follow instructions like the first time you started the phone