Hello,
i need help, i have an old android system (2.3.4) that i would like root. (3months that I try)
the kingroot application (3.5) allows me to get root rights (which allows me to have adb shell su # OK, if I install it) but this app installs too much unpleasant things... i would like to do otherwise with your help.
I have an update file "update.zip" that can load automatically at startup.
is it possible to modify the update.zip to get root rights (supersu)?
and if so, can you help me?
for information, this is the android system of "recon live mod" (no touch, but I can use "asm java apps" to simulate the touch on laptop)
thank you!
Perhaps Yes?!
dededede said:
Hello,
i need help, i have an old android system (2.3.4) that i would like root. (3months that I try)
the kingroot application (3.5) allows me to get root rights (which allows me to have adb shell su # OK, if I install it) but this app installs too much unpleasant things... i would like to do otherwise with your help.
I have an update file "update.zip" that can load automatically at startup. >>>>file here<<<<
is it possible to modify the update.zip to get root rights (supersu)?
and if so, can you help me?
for information, this is the android system of "recon live mod" (no touch, but I can use "asm java apps" to simulate the touch on laptop)
thank you!
Click to expand...
Click to collapse
Kingroot is a Chinese App that pushed it's Function from Managing root To Advertising and Stuff.So,There is an app Called Kingroot to supersu that allows you to Gain root access.Alternatively you can Flash a Custom recovery and flash Supersu Throug it(After unrooting from kingroot ofcourse)Or try other oneclick root soloutions.But Out of Curiousity what are you doing with that Old Android.I thought they were Dead.What are You hiding bro?You gonna Hack CIA with that Lethal Programming.
Sent from my SM-N9005 using Tapatalk
lol
is the "recon mod live HUD" of "reconinstrument" bought and abandoned by "intel" .. ( thx intel )
the "fastboot" is unreachable, and I have only 150MB of disponnible (not enough for a custom recovery?)
kingroot is the only one to work but I do not want to use it ...
so I'm looking for another way to get root and supersu
dededede said:
lol
is the "recon mod live HUD" of "reconinstrument" bought and abandoned by "intel" .. ( thx intel )
the "fastboot" is unreachable, and I have only 150MB of disponnible (not enough for a custom recovery?)
kingroot is the only one to work but I do not want to use it ...
so I'm looking for another way to get root and supersu
Click to expand...
Click to collapse
So Use "Kingroot to SuperSu"Script zip or apk from xda.
Sent from my SM-N9005 using Tapatalk
I already tried but I had a lot of errors.
it was also impossible for me to update the binary (no internet connection on the device)
Last Resort.
dededede said:
j'ai déjà essayer mais j'avais beaucoup de remontées d'erreur.
il m'était également impossible de mettre a jour le binary (pas de connexion internet sur l'appareil)
Click to expand...
Click to collapse
Buddy Your Device is too old.Either Flash a Recovery.Generally it replaces your already present recovery and Doesn't Cause much pain.
Sent from my SM-N9005 using Tapatalk
there is no recovery at all .... yes it is really old
(go see on the web "recon mod live")
dededede said:
Hello,
i need help, i have an old android system (2.3.4) that i would like root. (3months that I try)
the kingroot application (3.5) allows me to get root rights (which allows me to have adb shell su # OK, if I install it) but this app installs too much unpleasant things... i would like to do otherwise with your help.
I have an update file "update.zip" that can load automatically at startup.>>>>file here<<<<
is it possible to modify the update.zip to get root rights (supersu)?
and if so, can you help me?
for information, this is the android system of "recon live mod" (no touch, but I can use "asm java apps" to simulate the touch on laptop)
thank you!
Click to expand...
Click to collapse
Hi. The easiest way to root your Android is through TWRP... I don't know if your device is supported but take a look. https://www.xda-developers.com/how-to-install-twrp/
agatgamez said:
Hi. The easiest way to root your Android is through TWRP... I don't know if your device is supported but take a look. https://www.xda-developers.com/how-to-install-twrp/
Click to expand...
Click to collapse
Hello,
thank you for your answer, but as I said above, I can not use fastboot because the terminal does not support fastboot.
no fastboot --> no TWRP
I found the solution, I used a tool "unlockroot23" which was no longer available on XDA (which I recovered with "web.archive.org")
it installs root 10x faster than kingroot and cleaner.
I re-share the links, if you can serve someone.
>>link unlockroot23<<
Thank you all for your help
dededede said:
I found the solution, I used a tool "unlockroot23" which was no longer available on XDA (which I recovered with "web.archive.org")
it installs root 10x faster than kingroot and cleaner.
I re-share the links, if you can serve someone.
>>link unlockroot23<<
Thank you all for your help
Click to expand...
Click to collapse
I did my best, always happy to help
Related
So there are two populair methods of rooting the galaxy s3:
- The Samsung galaxy s3 toolkit
- Chainfire's CF-ROOT
My questions are as follows:
What are the technical differences between the two rooting methods?
Do the methods have any drawbacks? (cf-root for example is incompatible with rommanager)
disclaimer:
I am not interested in what you think is the best method, I want to know the technical differences between the two methods used.
I know that the toolkit itself is not a rooting method, it does however include 4 different methods you can use, I am referring to those.
The toolkit uses cfroot I think. Not sure if it's as up to date as the latest cfroot via Odin. They both work well enough. There is no other method I know of. And I haven't had any drawbacks.
That's all I can say really
Sent from my GT-I9300 using xda premium
Also The toolkit uses Odin too. It has other options and clear instructions. Drivers. Modems etc so this would be the best option for an casual user.
Latest cfroot via Odin is probably your best option if u know what your doing
But it's up to you mate, it doesn't really need analyzing so deeply...
Sent from my GT-I9300 using xda premium
slking1989 said:
But it's up to you mate, it doesn't really need analyzing so deeply...
Click to expand...
Click to collapse
Well it is personal but I like to know or at least have a general idea of what I am doing to my phone. So yes it does
Tnx for the reply
Anyone else who can give me some more insight?
Unfortunately I don't have an answer for you, but I also am interested in the answer to your question..
I think certain methods of rooting use SuperSU (is this the CF one?) and then another method uses Superuser. I think both install busybox (that seems to be the same?)
In my experience, using the Superuser.apk app was faster than SuperSU..
I don't even have the Busybox app installed (but I am sure my phone has busybox, so this also confuses me??)
CF root gets the job done in 20-25 seconds. It installs superSU, busybox and cwm recovery. I would allways recommend rooting with CF Root over the Toolkit.
But that`s my opinion off course
gee2012 said:
CF root gets the job done in 20-25 seconds. It installs superSU, busybox and cwm recovery. I would allways recommend rooting with CF Root over the Toolkit.
But that`s my opinion off course
Click to expand...
Click to collapse
Yes go with the CFroot if u just want to root ur phone.
Sent from my GT-I9300 using Tapatalk 2
'K, I'll bite. I'm not going to give an overall recommendation - at the end of day, they both install an APK and put a new binary in /system/xbin.
Note: I used CF-Root to root my phone. When I talk about how the the toolkit does what it does, I'm basing my words on this image. I've seen the things in that image before, even though I haven't used the toolkit. This also means that my toolkit observations may not be entirely accurate but it's a batch script, anyway; you can just read through it and find out how it works. I'm also primarily a Windows user, but I used to use GNU/Linux quite a bit to write programs for a phone that I once had.
Rooting is, when broken down, the installation of a "su" binary installed to /system/xbin, that is owned by root and carries the setuid flag. This flag is important as the Linux kernel will then run the process whenever it's invoked as the person who owns it, root. This process can then, in turn, start other programs and they inherit the user ID (something like this - I'm taking my time reading TLPI...) so they are then running as root. There's also a "manager" app (Superuser or SuperSU) that will be installed; this app is talked to by the su binary (through the Android Binder AFAIK, though Superuser's source is available so if you really wanted to find out you could read that) to see, for example, if the program that is invoking "su" is allowed to do so. CF-Root installs the SuperSU apk to /system/app, which means that it survives factory resets. The toolkit, from a quick look at the Superuser ZIP in its folder and its batch file, also installs the Superuser apk to /system/app. When sideloading apps or installing from the Google Play Store, they usually get installed to /data/app.
Not all "su" implementations for Android need a manager app, I've seen implementations where su does not place restrictions on who is allowed to run it; uid=0 for everyone without discrimination! (Yes, that also includes you, Super Smilies Pack 3000 with boob smilies) Thankfully, neither the toolkit nor CF-Root do this. I lie a little. Superuser's su binary will automatically reject any request to become root if the Superuser.apk is not installed but SuperSU's su binary will automatically accept all requests to become root if the SuperSU apk is not installed. Personally, I prefer SuperSU's behaviour as there have been too many times with my old phones where I'd have to sign into Google Play after wiping /data just to install the Superuser APK when all I wanted was to run a simple command.
ext* filesystems along with other *NIX filesystems have the concept of file permissions, a concept shared by other *NIX filesystems. In order to actually place this su binary owned by root into a folder owned by root, you need to be root. (Actually, the folder is also owned by the shell group so a user which is a member of that group could do it too, but they wouldn't be able to set the all-important setuid flag as they're not the user root [perhaps a member of group root could do it but I don't know]) Usually, exploits in other programs running/can run as root or in the kernel are searched for so that you can temporarily root in order to install the su binary correctly. The GSIII (with the exception of Verizon's) has an unlocked bootloader, though, so programmers don't need to search for any of these: it's able to flash unofficial, unsigned recoveries and kernels.
CF-Root does this:
* it flashes a new CWM-based recovery in the recovery partition of the phone. If you've seen the stock Android recovery, you'll know that it just can't match the features of CWM. The important thing about CWM is that it runs as root, just like the stock recovery, but it also lets you place any file anywhere on the phone without requiring that the the ZIP file containing the files are not signed with a Samsung private key. Remember what I said about file permissions?
* there's also a param.bin file. I don't know anything about this file, but I suspect it's flashed to get the phone to boot up into recovery mode the next time it's started so that CWM runs before anything else
* it also flashes the cache partition (I'm not sure whether it overwrites or appends as I don't know how [and probably never will] know how ODIN works with two ZIP files: SuperSU, which contains the su binary, the SuperSU apk and a script that is run by CWM to set the required permissions on the su binary among other things, and the CWM app which lets you tell the recovery what actions you want it to perform in Android without having to navigate through the awkward interface of CWM itself. While I don't know how to do this myself, CWM recovery can be told to automatically run commands from an external source. I'm not talking about random websites on the Internet, but (I think) through files that have to be placed somewhere by root. This is what apps like the CWM app and ROM Manager do. This is also what CF-Root does to tell the recovery that the next time it's booted that it should install both the CWM ZIP and SuperSU ZIP. That's it in the case of CF-Root: you now have a phone with the two files required for root access, and a CWM recovery and an app to control it.
The toolkit:
(I only talk about the "insecure boot" options as I imagine the recovery option does something similar to the above and do remember that I haven't used the toolkit to root my phone so some assumptions are made. I also assume you know what ADB is as I won't be explaining it)
* it gets you to flash a kernel image with a patched adbd that runs as root, so adb on your computer, in turn, is able to place files anywhere on the phone's /. File permissions make it so you can't just place adbd in its expected place (/sbin) as any user and /sbin is also mounted on a ramdisk part of the flashable kernel image so it would be replaced on the next reboot, anyway.
* When the phone is running again with the new kernel, it then tells adb (now running as root) to push the Superuser APK and the su binary into their rightful place and sets the correct permisions on the su binary so that it runs as root
* if you've told it to install busybox, busybox is pushed and a bunch of symlinks for all the applets that BusyBox supports are set up
CF-Root installs, naturally, Chainfire's SuperSu whereas the toolkit installs Superuser. I much prefer SuperSU (and I bought a pro license for Superuser long before I did for SuperSu). Superuser's interface is much better than SuperSU's and it's also open-source but I find that SuperSU works much quicker for me (Root Explorer actually popped up a message on my sister's freshly-flashed Xperia Arc S saying that Superuser can be slow if Superuser hasn't granted it root access quick enough - I've never encountered that on my Huawei U8800pro with SuperSU which has pretty much the same specs as the Xperia) and it can also log the commands an app is running as root if you're suspicious of an application.
You'll notice that ADB still runs as a normal user with CF-Root. You can use Chainfire's adbd Insecure app which will replace /sbin/adbd everytime the phone is started with his patched adbd which always runs as root, or you can just flash one of the many kernels available that already include a patched /sbin/adbd.
CF-Root also does not install BusyBox. You can grab one of the installers from the Play Store but what I do personally is kang a CM9 nightly build for the I9300 and take the META-INF folder and the /system/xbin/busybox binary and strip out most of the lines in the update-script leaving only the lines that mount, extract and create the symlinks for busybox and place the result in a new ZIP which is then flashed with CWM.
Your "cf-root for example is incompatible with rommanager" gripe is easily solved - just flash another recovery. CF-Root just packages a CWM Recovery, an app to control CWM and SuperSU. CF-Root itself is not a resident component, but the recovery and SuperSU etc. are, if that makes sense.
qwerty12 said:
A long story with a lot of interesting and valuable information
Click to expand...
Click to collapse
Tnx! This is precisely what I have been looking for! A lot of the information I already found in seperate pieces but this made it click in my head. I used cf-root to root the phone and am currently deciding if I want to work with the included tools and cwm recovery or flash CWM touch
I got a busybox installer from the market and it works like a charm (Well Titanium backup seems to do its job anyway).
I must say I think was over analyzing this a bit since I owned a HTC desire before this phone where rooting has a lot more risks involved and a lot more steps.
The only advantage i can see to using toolkit is it will get updated quicker and it has loads of other options. If you just want to Root and flash a Rom cf root is way to go
Sent from my GT-I9300 using xda app-developers app
creesch said:
Tnx! This is precisely what I have been looking for! A lot of the information I already found in seperate pieces but this made it click in my head. I used cf-root to root the phone and am currently deciding if I want to work with the included tools and cwm recovery or flash CWM touch
Click to expand...
Click to collapse
Glad it helped
I must say I think was over analyzing this a bit since I owned a HTC desire before this phone where rooting has a lot more risks involved and a lot more steps.
Click to expand...
Click to collapse
Yeah, HTC's locked bootloaders and the S-ON/S-OFF rubbish is one of the reasons I decided to skip the One X and go for the Galaxy S3.
creesch said:
I must say I think was over analyzing this a bit since I owned a HTC desire before this phone where rooting has a lot more risks involved and a lot more steps.
Click to expand...
Click to collapse
Its fair to say that unlike many people on this forum you did your research. Searched.. and asked a valid question. Whereas the majority of people just ask questions without being bothered to figure it out themselves. So thanks. Over analyzing? Maybe a little... but its better than flashing any old thing like many other have done and continue to do. Big thanks to qwerty who has filled me in on some useful info also.
Sent from my GT-I9300 using xda premium
You should have thanked him tho maaan
Sent from my GT-I9300 using xda premium
creesch said:
Tnx! This is precisely what I have been looking for! A lot of the information I already found in seperate pieces but this made it click in my head. I used cf-root to root the phone and am currently deciding if I want to work with the included tools and cwm recovery or flash CWM touch
I got a busybox installer from the market and it works like a charm (Well Titanium backup seems to do its job anyway).
I must say I think was over analyzing this a bit since I owned a HTC desire before this phone where rooting has a lot more risks involved and a lot more steps.
Click to expand...
Click to collapse
Stick with 5.x.x.x recovery, touch(6.x.x.x) has some instability issues afaik
Sent from my GT-I9300 using xda premium
slaphead20 said:
Stick with 5.x.x.x recovery, touch(6.x.x.x) has some instability issues afaik
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Alright well since it was only the touch aspect that made me consider it i'll leave it just like it is
Hey guys
Hey guys i have the internationa galaxy s3 running 4.1.2, i haven't done anything to my phone yet and im about to root it is the boot loader unlcoked and if not how do i unlock it :good:, could someone please help me:crying::crying: and give me clear instructions and links please :fingers-crossed: thanks you so much,
BTw i know this is the wrong thread but i cant find the right one, thanks alot guys
regards nick
how to root lenovo A390 : Bối rối:
and how to install data on sdcard 2
(I use google translate : P )
vuongbaoremix said:
how to root lenovo A390 : Bối rối:
and how to install data on sdcard 2
(I use google translate : P )
Click to expand...
Click to collapse
upup
up.. hope somebody will make a rooting tutorial for this phone.. and also a jb custom rom.. thanks in advance
Please help guys, Me too
Sent from my Lenovo A390_ROW using xda app-developers app
rezashamdani said:
Please help guys, Me too
Sent from my Lenovo A390_ROW using xda app-developers app
Click to expand...
Click to collapse
See my post here on how to root the A390
http://forum.xda-developers.com/showpost.php?p=43938398&postcount=4
no way to get a390 rooted
hi! i'm trying to root and setup a recovery on this phone but i cannot do it...
tried with no luck:
- scoutdriver73's method: sp flash tool hint me that it can download only a full image
- root with recovery method: script doesn't recognize when i confirm on smartphone for the reset, same for root option in mtk droid tools
- this guide http://forum.xda-developers.com/showthread.php?t=2332783 for extract boot.img and recovery.img and fix root permission with mtk droid tool, i get this error: 0 [main] gzip 4324 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer when i load my recovery.img on mtk tool.
i noticed there is a size difference between TWRP img i downloaded from web (5640Kb) and the one i extrated directly from phone (6144kb)
any suggest?
thanks
(LATE REPLY) This is how I rooted my a390
I noticed the post is 10 months ago, but I'm replying right now because there may be other users hunting for root solutions for this device.
How to root your Lenovo a390:
1. Download Framaroot: http://forum.xda-developers.com/showthread.php?t=2130276
Framaroot is an Android app created by XDA user alephzain. It allows you to root your device directly from your Android device-please click on link above to view full compatibility list. Download and Install this app. If it says "Installation blocked", go to your phone's Settings>Security and tick the "Unknown Sources" box. (Believe me, there are n00bs )
2. Open Framaroot. For the a390, there is only one exploit-Boromir, since it's a Mediatek powered device. Select Boromir.
3. Now you see two buttons: Install Superuser and Install SuperSU. You need to select only one of them. Framaroot will then root your device and install Superuser/SuperSU. (Superuser/SuperSU are apps which control root operations on your device ie. ensure no app uses root features without your permission-it is a MUST.)
The choice is up to you, but I'd recommend Superuser since it's like the Industry standard of rooted Android phones.
4. Reboot your phone. You'll find Superuser installed. Open it, swipe from left to right to access Superuser settings. The su binary is outdated and it'll appear in a red font. Tap it to update su binary.
This is proof enough that your phone is rooted, but if you really need to see, here's one more step.
5. Install Root checker from Google Play Store: https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck
Run this app, and if your phone is rooted, Superuser will come up automatically asking you whether Root Checker should be granted permission- press Yes and root Checker will deliver the result.
That's it-congratulations, you've rooted your a390 without any pain. Now you can flash a recovery, install Busybox, overclock your phone, get rid of the dumb apps Lenovo has included with the a390.... Enjoy! :laugh:
Hi to the community...
I need root acces for my new POV_TAB-p1325 !
All my attemps to get root failed!
this tablet use RKBatchTool.exe when usb connected to load *.img firmware updates! (for exemple: TAB-P1325_V1.0_20140503.img,which is the latest firmware update)
maybe the solution could be creating an unsecured *.img including recovery mode, superuser etc ?!
could anyone help to make such *.img file ?
best regards
alansan2013
the tab-p1325 tablet run under JB 4.1.1
pov root check
Hi, sorry but did you check if you already had root access before trying with tools? Recently most of these are Chinese clones and come with root privileges out of the box.
vsanto88 said:
Hi, sorry but did you check if you already had root access before trying with tools? Recently most of these are Chinese clones and come with root privileges out of the box.
Click to expand...
Click to collapse
Hi,
I'm sure it's not rooted because when I run titaniumbackup, it says that it have no root access !
regards
alansan2013 said:
Hi,
I'm sure it's not rooted because when I run titaniumbackup, it says that it have no root access !
regards
Click to expand...
Click to collapse
Just exhausting all possibilities here so bear wit me. . Try installing super Su or other Su binaries from the play store. Install a root checker app from the play store as well and then try it.
vsanto88 said:
Just exhausting all possibilities here so bear wit me. . Try installing super Su or other Su binaries from the play store. Install a root checker app from the play store as well and then try it.
Click to expand...
Click to collapse
all done, but no pre-root !
Hi.
I know this is a realy old topic, but still on position 1 @ googlesearch for "POV_TAB-P1325 root".
My POV_TAB-P1325 is now rooted. Maybe it works with other Devices which have a "RK30 Device" driver in the Windows Device Manager.
Here is the link:
www(dot)slatedroid(dot)com(slash)topic(slash)88850-rooting-rk3188-tablets(slash)
Happy rooting
P.S. Remove (dot) and (slash) with the real signs in the link cause of "To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
WARNING: For 20b and up (it means V20d also! ) DOWNLOAD this and make steps from 2. and optionally from 2. to 6
check this site for updates of root-making app
------------------------
1. Download and put it on your phone: https://drive.google.com/file/d/0BwDGitcriVSbcVR3X0UtY1Y3WGs/view?usp=sharing
2. Run the app - click START ROOT (you must have internet connection). AND WAIT.
this steps are optional
3. Download and extract MRW folder to your phone memory. https://drive.google.com/file/d/0BwDGitcriVSbMjQ0N3NlcGYwTXM/view?usp=sharing
4. Download from Google Play Terminal Emulator
5. Disconnect the phone from the USB port - IMPORTANT. Without it changes will not succeed !!!
6. Open Terminal Emulator app and enter this lines:
Code:
Su (enter)
sh /sdcard/mrw/root.sh
This will start a script that will remove Kingroot and replace to SuperSu, then automatically direct you to update the binary files. After this procedure, restart your phone and enjoy the ROOT, SuperSU on L
------------------------
Thanks for tutorial: original thread
------------------------
#
It works, thank you very much
WYPIERDAALAAC said:
1. Download and put it on your phone: https://drive.google.com/file/d/0BwDGitcriVSbcVR3X0UtY1Y3WGs/view?usp=sharing
2. Run the app - click START ROOT (you must have internet connection).
3. Now you have to install SuperUser from Google Play and download binaries.
4. Turn on your phone.
5. Download and extract MRW folder to your phone memory. https://drive.google.com/file/d/0BwDGitcriVSbMjQ0N3NlcGYwTXM/view?usp=sharing
6. Download from Google Play Terminal Emulator
7. Disconnect the phone from the USB port - IMPORTANT. Without it changes will not succeed !!!
8. Open Terminal Emulator app and enter this lines:
Code:
Su (enter)
sh /sdcard/mrw/root.sh
This will start a script that will remove Kingroot and replace to SuperSu, then automatically direct you to update the binary files. After this procedure, restart your phone and enjoy the ROOT, SuperSU on L
BIG THANKS FOR THIS TUTORIAL
Click to expand...
Click to collapse
I will never test it. I don't trust a root app which need internet connection. For what does it need internet? Sending something to someone? I do not trust it. If you say it works, post some screenshots of working titanium backup, betterbatterystats or other apps
I tried another method for other LG Lollipop firmwares, but not working (but at least it works via ADB and download mode, with no internet connection needed -.-)
I just installed the Kingroot app and clicked "START ROOT" and it worked perfectly, i don't even did the rest of the tutorial...
I attached a screenshot of greenify with auto hibernation active (you need root for that, sorry for the Portuguese language)!
Big thanks!
Andrewbons said:
I will never test it. I don't trust a root app which need internet connection. For what does it need internet? Sending something to someone? I do not trust it. If you say it works, post some screenshots of working titanium backup, betterbatterystats or other apps
I tried another method for other LG Lollipop firmwares, but not working (but at least it works via ADB and download mode, with no internet connection needed -.-)
Click to expand...
Click to collapse
But it works maybe this update their binaries by the web, i honestly dont care do a "risk" or leave it
WYPIERDAALAAC said:
But it works maybe this update their binaries by the web, i honestly dont care do a "risk" or leave it
Click to expand...
Click to collapse
"Do a risk or leave it", wise words. I gave it a try because of XDA translated it into english (but it's still a suspicious app -.-). Now, any idea on how to use SuperSU instead of KingUser? I want remove everything without installing anything else from shell
Andrewbons said:
"Do a risk or leave it", wise words. I gave it a try because of XDA translated it into english (but it's still a suspicious app -.-). Now, any idea on how to use SuperSU instead of KingUser? I want remove everything without installing anything else from shell
Click to expand...
Click to collapse
I meant 'Risk it or leave it'. You are so grouchy today (or always?). You will use this app only once so just do it.
Andrewbons said:
"Do a risk or leave it", wise words. I gave it a try because of XDA translated it into english (but it's still a suspicious app -.-). Now, any idea on how to use SuperSU instead of KingUser? I want remove everything without installing anything else from shell
Click to expand...
Click to collapse
If you're so damn wise just inspect scripts that are used from mrw folder and see if it has something suspicious.
binary update faild
using d618
any other method to root with supersu ?
didar2 said:
binary update faild
using d618
any other method to root with supersu ?
Click to expand...
Click to collapse
same here using d620
I do it like this:
1. Use KingRoot to root.
2. Install SuperSU and Terminal.
3. Open Terminal and type: su then sh /sdcard/mrw/root.sh
4. SuperSU will open automatically and will ask for binary, accept it and you are done
sheraz777 said:
same here using d620
Click to expand...
Click to collapse
use last version of supersu (v2.49 - BETA) it has improved Kingroot removal :good:
Just to make clear to everybody, you don't need to install supersu from Play Store you already have it in mrw folder, and when you start root.sh script it will automaticaly install it from folder. I did it a couple of times in the last few days with no problem.
good to know. now just use KingRoot and type command in terminal.
maybe now nobody will have problems with it
didar2 said:
use last version of supersu (v2.49 - BETA) it has improved Kingroot removal :good:
Click to expand...
Click to collapse
thank you so much... it worked like a charm...
now waiting for twrp for lollipop..
sheraz777 said:
thank you so much... it worked like a charm...
now waiting for twrp for lollipop..
Click to expand...
Click to collapse
Twrp and patched aboot is already out...
Sent from my LG-D620 using XDA Free mobile app
steffenbakke said:
Twrp and patched aboot is already out...
Sent from my LG-D620 using XDA Free mobile app
Click to expand...
Click to collapse
thanks man,,,, patched and flash twrp from flashify
i rooted version d620r poland but when i removed some apps of bloatware like g+ hangouts etc then my apps were crashing and lag the phone....
i flashed then the portugal version for d620r but root fails on it
peplosfc said:
i rooted version d620r poland but when i removed some apps of bloatware like g+ hangouts etc then my apps were crashing and lag the phone....
i flashed then the portugal version for d620r but root fails on it
Click to expand...
Click to collapse
that's weird, bcoz i uninstalled bloatware and no problems at all. probably you deleted not that folder
i got rom from D620 (without LTE) and phone D620R (with LTE) and i don't really care for LTE for now so i got no problems, everything works fine.
SuperSU says update binary failed. Its some another root method or somebody knows where can be a problem?
I have d620r.
Hi!
Haven't found anywhere answer about rooting... Is it possible to root his device?
PeeHoo said:
Hi!
Haven't found anywhere answer about rooting... Is it possible to root his device?
Click to expand...
Click to collapse
KingRoot can do it, but I would have difficulties to recommend that "shady" software. It is possible to remove KingRoot and install SuperSU with help of Super-Sumo pro which will cost you some money and still rather tricky process with no guarantee KingRoot is completely gone (it is very aggressive kind of software and pretty hostile to any alternative su solutions). Think twice before going this way.
It would be great if someone could help to make TWRP for this device. It is the same chip as in Moto G 2015 and Huawei provided some Open Source code. I just have no time at all now to work on that.
It is also probably readable to inject su directly to update file. There are tools that can extract partition's img files from update file and mount them, but after that we need to put it back into original file and make it work with EMUI original recovery.
Waiting too