DISCLAIMER : You attempt the following at your own risk !
I'm not responsible if your phone blows up, bricks, you travel back in time or go bald or something!
Background :
I have the MT2-L05 Mate 2 from China.
When I received my Mate 2 last Thursday, the phone was on 4.2.2
After much hunting and downloading and flashing of ROMS, I managed to finally update to 4.4.2 KitKat.
Great ! I was happy. But I didn't have root access.
After trying and failing to use the various bootloader unlock tools on these forums, I Emailed Huawei, and politely asked them if I could have the 16 digit code for my Mate 2. An hour later an Email arrived with my bootloader unlock code, so I fastbooted, used the code and unlocked the Bootloader.....Cool ! Thanks Huawei, great customer service.
I then went to root my phone, and here the problems started. I tried at least 20 different Root tools, both via phone and over the pc, but no joy.
Nothing worked ! Vroot, Kingoroot, Towelroot, srs root, root genius 1.8.7, etc they all failed.
I was at the point of giving up, when I found a Chinese version of rootgenius 2.0.1.3......I ran it via pc........and Success ! I was finally rooted.
Supersu was installed, the binaries updated fine and all was good with the world. I tried wakelock detector first ( Yeah, I know, I REALLY need more battery life from the Mate 2 ! ), and Supersu asked for permission and it worked no problem.
I then tried to install adaway, and then I ran into problems, I was unable to edit my hosts file....ummm...odd. OK, then I tried to install xposed......Impossible to install.
I then read on these forums to edit build.prop and change a simple setting to get xposed running.......ok, no problem, yet when I edited my build.prop file, it would NEVER EVER save the edits. Weird? what's going on?.......after much searching and much reading I finally found the problem.................
Root Genius 2.0.1.3 :
http://www.shuame.com/root/
The Problem :
The 4.4.2 update adds a file to your System folder called :
set_immutable.list
this file contains :
Code:
/system/bin
/system/build.prop
/system/etc
/system/fonts
/system/framework
/system/isp.bin
/system/lib
/system/ons.bin
/system/usr
/system/vendor
/system/xbin
/system/app/HwLauncher6.apk
/system/app/HwLauncher6.odex
/system/app/systemUI.apk
/system/app/systemUI.odex
Any location listed above is IMPOSSIBE to mount as rw. Every file explorer or emulator you try will tell you it is rw, but it's not.
It's locked down completely...................and it's REALLY annoying.
This is why I could never edit my build.prop or Install Adaway etc..................
But I found a solution...... ( I think ! )..........
The Solution :
I spent the afternoon at work using google translate to find a fix for my problem and found a post from a guy called :
**** wire His Royal Highness Prince czx ( I cannot post the first 4 letters as it will probably be banned....It must be a Google translate error but it made me laugh ! )
His guide never worked for me until I made a few edits and added STEP 4. Then I got it to work.
The Solution :
1, First Root your Phone ( I suggest trying Root Genius 2.0.1.3 from my first post )
2, install busybox (I suggest BusyBox ( Stericson ) as I couldn't get this to work with the Jrummy BusyBox installer )
3, Install Rom Toolbox Pro ( I know it's payware and I tried other programs, but this is the only one that worked for me. I had already purchased ages ago. The free version may contain the following tools too, but I genuinely don't know )
4, open Scripter from Rom Toolbox pro and click " Mount System R/W "
5, open Terminal Emulator from Rom Toolbox Pro
Type: su then press enter
Type: mount -o rw, remount / system then press enter
Type: cd system then press enter
Type: chattr -R -i * then press enter
(On step 5 there is a space between remount forward slash and system and also between i and *)
6, Leave Terminal Emulator open, Hit your Home Button
7, then delete the file :system / set_immutable.list with Root Explorer. Other File managers with root access may work, I haven't tried
If you can not delete it, the above steps haven't worked, I can only suggest you try from step 4 after rebooting your phone.
If you are successful and manage to delete the set_immutable.list file then reboot your phone.
Job Done !
You now have full Root Access.
This has been tested by myself on my MT2-L05, it should work on ALL China Variants and presumably on the US MT2-L03 if this file is included in a 4.4.2 update, but I obviously cannot guarantee this.
I'm also curious as to whether anyone thinks this has left my phone open to exploits by the deleting this file....? Remember, if I have done something stupid by doing this, then so will you if you follow the above!
All I know is Xposed has installed perfectly after finally being able to edit my build.prop file and Adaway is running like a charm.
Feedback very welcome.
4L0M said:
The Solution :
Snip
5, open Terminal Emulator from Rom Toolbox Pro
Type: su then press enter
Type: mount -o rw, remount / system then press enter
Type: cd system then press enter
Type: chattr -R -i * then press enter
(On step 5 there is a space between remount forward slash and system and also between i and *)
Snip
Click to expand...
Click to collapse
I followed your guide, the part I bolded didn't seem to work for me, but after a few attempts I just kept going with the rest of the guide and I was still able to delete the file at the end of the day Thank you so much! I always felt like the root I had with 4.2 was kind of a pseudo root since I was limited by my root access, this is exactly what I needed!
I manage to get root and delete that file. Hooray and thanks! But after editing the build.prop, I still can't get xposed to install. I keep getting this error on the install screen.
scpion said:
I manage to get root and delete that file. Hooray and thanks! But after editing the build.prop, I still can't get xposed to install. I keep getting this error on the install screen.
Click to expand...
Click to collapse
Install xposed 2.5.1, it's the safest option for now and you will not get this error message.
I haven't tried too many xposed apps yet, but wanam works if you want circle battery etc
Experimental features of Greenify work too.
Gravity box Kitkat will not run properly for me.. I suggest you do not attempt to install it at the moment.
Let me know if you find anymore cool xposed modules to try!
4L0M said:
Install xposed 2.5.1, it's the safest option for now and you will not get this error message.
I haven't tried too many xposed apps yet, but wanam works if you want circle battery etc
Experimental features of Greenify work too.
Gravity box Kitkat will not run properly for me.. I suggest you do not attempt to install it at the moment.
Let me know if you find anymore cool xposed modules to try!
Click to expand...
Click to collapse
Thanks dude. Btw does your device support Google search by swiping up from home?
scpion said:
I manage to get root and delete that file. Hooray and thanks! But after editing the build.prop, I still can't get xposed to install. I keep getting this error on the install screen.
Click to expand...
Click to collapse
Same issue for me
janrck said:
Same issue for me
Click to expand...
Click to collapse
Install xposed 2.5.1, it's the safest option for now and you will not get this error message.
Cool xposed apps for 2.5.1 :
wanam kit : adds circle battery, expanded notifications, 4-way reboot menu etc etc
Android L Navbar : adds Android L navbar and Android L shapes Navbar
Both work flawlessly for me and have NEVER crashed once.
Hi, I followed your steps but in the step 5, when i type this : mount -o rw, remount / system it doesnt work.
4L0M said:
DISCLAIMER : You attempt the following at your own risk !
Nothing worked ! Vroot, Kingoroot, Towelroot, srs root, root genius 1.8.7, etc they all failed.
I was at the point of giving up, when I found a Chinese version of rootgenius 2.0.1.3......I ran it via pc........and Success ! I was finally rooted.
Supersu was installed, the binaries updated fine
I then tried to install adaway, and then I ran into problems, I was unable to edit my hosts file....ummm...odd. OK, then I tried to install xposed......Impossible to install.
Click to expand...
Click to collapse
I then read on these forums to edit build.prop and change a simple setting to get xposed running.......ok, no problem, yet when I edited my build.prop file, it would NEVER EVER save the edits. Weird? what's going on?.......after much searching and much reading I finally found the problem.................
/QUOTE]
How was SU installed if you had no rw privs?
vroot, kingroot, kingoroot, kinguser, srs root and rootgenius were created for a select few... it was a side effect of massive social engineering via the internet that they'd leak to so many others who weren't the target.
magicpromise said:
I then read on these forums to edit build.prop and change a simple setting to get xposed running.......ok, no problem, yet when I edited my build.prop file, it would NEVER EVER save the edits. Weird? what's going on?.......after much searching and much reading I finally found the problem.................
/QUOTE]
How was SU installed if you had no rw privs?
vroot, kingroot, kingoroot, kinguser, srs root and rootgenius were created for a select few... it was a side effect of massive social engineering via the internet that they'd leak to so many others who weren't the target.
Click to expand...
Click to collapse
I'm guessing because I could write rw to system folder. Set-immutable-list blocks folders inside system folder, not the basic system folder itself. ie/ system/xbin or system/etc they are blocked. /system on its own isn't.
4L0M said:
I'm guessing because I could write rw to system folder. Set-immutable-list blocks folders inside system folder, not the basic system folder itself. ie/ system/xbin or system/etc they are blocked. /system on its own isn't.
Click to expand...
Click to collapse
yes, and the instructions worked great.
i made a script with it in totalrom and set it to load on boot along with total rom itself to keep a strangle hold on the permissions.
magicpromise said:
yes, and the instructions worked great.
i made a script with it in totalrom and set it to load on boot along with total rom itself to keep a strangle hold on the permissions.
Click to expand...
Click to collapse
Can you please upload the script you made?
You'll make things easy for me, 'cause commands in terminal don't seem to work in my case.
Thank's !
Related
Thanks goes to #TeamWin for Temp Root
This is For Windows only, if you wish to make it work for linux or mac help your self...
Remember, This is still a Temp Root & any Changes made will be Rest back to stock on a Reboot
It's stable & works 100%
I Personally have not lost Root with this new Method
Q. I thought RW was Fixed?
A. Caused by Deleting an apk / file that was already deleted. Journaling shows it still there!
Keep Track of what you delete, as trying to delete something off system that you alread di hangs the /system into RO state.
Before Using!!HTC Sync Must be Turned OFF
Put the Phone into Charge Mode only ( Not Disk Drive )
USB Debugging Must be Turned on
What's Fixed:
Revamped due to new Method:
~ Superuser Apps now Function
~ If you Lose Root, all you have to do is Open terminal & type SU then type fixit! > No More Rebooting & running the exploit again for R/W on system to get Root back in place
~ Fixed R/O Bug!!
~ R/W is now Forced
~ /system is fully editable now! until reboot that is.
~ Busybox is installed to /vendor/bin
~ hex Edited libext4
~ hex edited libfuse.so
~~ This is the Last Update due to it working & Stable ~~
Download for RW HTC Sensation 4G:
````````````````````````````````````````````````````````````````````````````````````````````
Download for RW HTC Evo 3D:
````````````````````````````````````````````````````````````````````````````````````````````
Download for RW HTC Flyer 16GB/32GB:
````````````````````````````````````````````````````````````````````````````````````````````
Download for RW HTC Evo View:
Q. Is this permanent?
A. no, it's a temp root method..
Q. Will I lose SU Access at some point while running the OS?
A. You might, but open terminal & type fixit to get root back!.
Q. What about apps that need a reboot to use superuser?
A. Use Fast Reboot form the market for app that need a reboot..
Q. Can I push & remove items to system & will it work?
A. Yes, but all changes are reset on a reboot.
Once Downloaded, Unzip & double click on the Run_ME_fre3vo_Root.bat File & Enjoy long lasting Root!
OLD NEWS:
Everyone knows that currently with any temp root, you still lose links to the SU Binary & Busybox links, it's just a matter of time before it happens!!
So after digging around somewhat I found an over sight that HTC might use later for system updates via /vendor/bin, who knows at this point though... Anyways, after amount of time the SU Binary along with busybox links if be in system/bin or /system/xbin gets deleted / removed..
Now, what I did was enable the $Path to /vendor/bin which is in the Sensation export PATH..
Any Calls made from this point either be SU or Busybox don't get deleted nor touched from any App requesting the SU Binary!! I've tested this with alot of apps & the Root sticks in place..
Other than Reboot, it might as well be a Perma-Temp-Root!!
Downloading now!!! Can't wait to test it!
***EDIT***
Rooted perfectly, opened and closed Titanium Backup several times with no force closes or loss of su, Barnacle is perfect, Wireless tether is granted su but the kernel doesn't support it, screenshot gained su also but the screenshots were smeared colors. Drocap2 takes perfect screenies though. Gonna try a few more root apps before bed and play some more when I wake up to verify it lasts.
going to try this now!
Ran the script and no root
script stays on
daemon started successfully :/
eugene373 said:
Thanks goes to #TeamWin for Temp Root!!!
Everyone knows that currently with any temp root, you still lose links to the SU Binary & Busybox links, it's just a matter of time before it happens!!
So after digging around somewhat I found an over sight that HTC might use later for system updates via /vendor/bin, who knows at this point though... Anyways, after amount of time the SU Binary along with busybox links if be in system/bin or /system/xbin gets deleted / removed..
Now, what I did was enable the $Path to /vendor/bin which is in the Sensation & Evo 3D export PATH..
Any Calls made from this point either be SU or Busybox don't get deleted nor touched from any App requesting the SU Binary!! I've tested this with alot of apps & the Root sticks in place..
Other than Reboot, it might as well be a Perma-Temp-Root!!
This is For Windows only, if you wish to make it work for linux or mac help your self...
If you have trouble with the Superuser.apk, uninstall first & reboot then run the .bat file again..
What is installed?
Busybox w/ symlinks
Superuser.apk
SU Binary
Fre3vo
sqlite3
What's Removed?
slackerradio.apk
TMOUS_Navigator.apk
Transfer-pyramid-8.30.0.26-S30.apk
Protips.apk
IdleScreen_Stock.apk
HtcTipWidget.apk
com.htc.TrendsWidget.apk
com.mobitv.client.tmobiletvhd.apk
FusionStockWidget.apk
Stock.apk
So without further ado, the link!
http://www.multiupload.com/LBEYIFVD58
Once Downloaded, Unzip & double click on the Run_ME_fre3vo_Root.bat File & Enjoy long lasting Root!
Last edited by Eugene373; Today at 05:51 AM.
Click to expand...
Click to collapse
Is there any chance u can edit the script or tell me how to edit it so it doesn't remove anything. Thanks.
perfect works great!!! Managed to restore TB! Will try out wifi tethering right now and other su required apps! Thank you! <3
I guess I don't understand.
How is removing anything from /system/app gonna stick?
This worked perfect for me. No problems with it. Wifi tether won't work for me, but barnacle tether works perfectly. Drocap2 is taking perfect screen shots for me as well, where as before the images would be all distorted and what not.
Made some changes to the .bat since I don't necessarily want to disable all of that yet, but it works, this is the longest superuser has worked for me so far on the EVO 3D.
k2buckley said:
This worked perfect for me. No problems with it. Wifi tether won't work for me, but barnacle tether works perfectly. Drocap2 is taking perfect screen shots for me as well, where as before the images would be all distorted and what not.
Click to expand...
Click to collapse
How'd you get Barnacle to work?
EDIT:
Sorry my tablet doesn't read Ad-Hoc >_>
Is anybody able to root the E3D with this method? I tried twice and it failed both times. I will do again by restart my pc and E3D.
urcboss07 said:
Is anybody able to root the E3D with this method? I tried twice and it failed both times. I will do again by restart my pc and E3D.
Click to expand...
Click to collapse
Yeah....First try.
nabbed said:
I guess I don't understand.
How is removing anything from /system/app gonna stick?
Click to expand...
Click to collapse
It won't stick, but after you reboot you run the batch program again and the apps are removed again until your next reboot.
hockeyfamily737 said:
It won't stick, but after you reboot you run the batch program again and the apps are removed again until your next reboot.
Click to expand...
Click to collapse
So, it will not stick as said, right?
Tiffany84 said:
Is there any chance u can edit the script or tell me how to edit it so it doesn't remove anything. Thanks.
Click to expand...
Click to collapse
a .bat file is just a text document that is executed in command prompt. If you are familiar with cmd just open the file in notepad, delete any commands you don't want executed, save.
urcboss07 said:
So, it will not stick as said, right?
Click to expand...
Click to collapse
Not through a full reboot....no you will have to run the batch file again (even says so in the OP). However, the other root methods would crash periodically even without a reboot or would last but not give you access to the majority of your root apps. This is the closest yet to a feasible root solution.
mine doesnt get past daemon started successfully i have usb debugging on
so if i downloaded and installed some apps that require root,
and i reboot, what happens to them ?
they will work after running the bat file again ?
or they will have to be installed again to work properly ?
thanks !
EDIT: i haven't done my due diligence (searching and reading)
but it's 5 am so i'll ask ...
what works for screen capture and for wireless tethering ?
lowetax said:
so if i downloaded and installed some apps that require root,
and i reboot, what happens to them ?
they will work after running the bat file again ?
or they will have to be installed again to work properly ?
thanks !
Click to expand...
Click to collapse
They will work after running the .bat file again. You shouldn't need to uninstall and reinstall them. Super User may need to be uninstalled before running the .bat file again, if it gives you any force closes.
Sent from my PG86100 using XDA App
Since removing ads from browser and apps was one of the main reasons to root my DX I decided to make this tutorial. Problem is you can't just install AdAway (link) and run it because after a reboot you'll have to do it again. This method is keeping the ads away even after a reboot. Remember that you'll have to update AdAway-hosts files regularly.
All credits go to Yasir Javed Ansari. I only finetuned the method he described a little bit. Because his post is somewhere in another thread it seemed right to make a tutorial for it in the themes and apps section.
First of all you'll need a properly rooted DX with superuser 3.1.3 installed. See here for a zip to install superuser and busybox or here to download a pre-rooted 1.18 stock deodexed rom with superuser and busybux installed provided by infernal77. I'm using this rom on my DX and removed a lot of bloatware with Aroma (link) right after flashing the rom. Credits go to merovig for sharing info about flashable superuser/busybox-zip and Aroma and of course to infernal77 for providing his deodexed stock rom. Although it seems that this method shouldn't be necessary when using a deodexed rom I couldn't get it to work without using the command lines, so I decided to share it anyway.
In settings - power, uncheck 'fast boot'.
Install AdAway from Play Store. Run AdAway (don't download hosts files yet) and go to settings - preferences. Check 'allow redirections' and under 'target hosts file' select '/data/data/hosts'.
Reboot to recovery and then mount /system and mount /data.
While in recovery-mode connect the device to a PC and open a command prompt.
Type:
adb shell
cd system/etc
rm hosts
ln -s /data/data/hosts hosts
Disconnect the device from PC and reboot.
Now you can run AdAway: download files and apply ad blocking.
Done!
Nice one, added to Index.
@op, Good job.
Although my tutorial was word by word the same, apart from maybe few spelling mistakes. ;p
Above is required for Stock Rom which is rooted.
On custom and rooted Rom , you don't need to perform above steps as system is write permitted so running ad away normally works fine.
Regards
Yasir
Sent from my HTC Desire X
Hehe I know, the only thing I added was the /etc
Problem is that when I install for example infernals rooted stock deodexed rom, and then I install AdAway and hosts files, they don't survive a reboot. When I redirect the hosts file to /data/data/hosts AdAway states it can't create the symlink. That's why I still use your method even on a pre-rooted rom.
nightcrow said:
Hehe I know, the only thing I added was the /etc
Problem is that when I install for example infernals rooted stock deodexed rom, and then I install AdAway and hosts files, they don't survive a reboot. When I redirect the hosts file to /data/data/hosts AdAway states it can't create the symlink. That's why I still use your method even on a pre-rooted rom.
Click to expand...
Click to collapse
This symlink method(not mine) is present in ad away FAQs. So credit to the app team.
Sent from my HTC Desire X
Nice guide, first time I'm adfree, even after a reboot
did anyone get it working on desire x... mine still shows ads in apps...
I don't know, after all I'm an amateur, but the problem nightcrow described about how stuff goes back to stock after a reboot is something that happens a lot with the DX's - same thing with the bloatware. I had to remove the bloat apps from a rom.zip and flash that to avoid the problem. Seems to me there is some kind of security built in that goes beyond the norm. Otherwise I don't see why apps like Titanium work to remove apps (even after reboot) for example on most other phones, but not the DX.
Meherzad, I followed the instructions posted by nightcrow and it works for me ... try again, reboot and open an app you know normally has ads to check if it works.
Failed first time (forgot to uncheck fast boot:banghead. Reinstalled and did everything again, now works flawlesly.
ok.. working great......
nightcrow said:
Since removing ads from browser and apps was one of the main reasons to root my DX I decided to make this tutorial. Problem is you can't just install AdAway (link) and run it because after a reboot you'll have to do it again. This method is keeping the ads away even after a reboot. Remember that you'll have to update AdAway-hosts files regularly.
All credits go to Yasir Javed Ansari. I only finetuned the method he described a little bit. Because his post is somewhere in another thread it seemed right to make a tutorial for it in the themes and apps section.
First of all you'll need a properly rooted DX with superuser 3.1.3 installed. See here for a zip to install superuser and busybox or here to download a pre-rooted 1.18 stock deodexed rom with superuser and busybux installed provided by infernal77. I'm using this rom on my DX and removed a lot of bloatware with Aroma (link) right after flashing the rom. Credits go to merovig for sharing info about flashable superuser/busybox-zip and Aroma and of course to infernal77 for providing his deodexed stock rom. Although it seems that this method shouldn't be necessary when using a deodexed rom I couldn't get it to work without using the command lines, so I decided to share it anyway.
In settings - power, uncheck 'fast boot'.
Install AdAway from Play Store. Run AdAway (don't download hosts files yet) and go to settings - preferences. Check 'allow redirections' and under 'target hosts file' select '/data/data/hosts'.
Reboot to recovery and then mount /system and mount /data.
While in recovery-mode connect the device to a PC and open a command prompt.
Type:
adb shell
cd system/etc
rm hosts
ln -s /data/data/hosts hosts
Disconnect the device from PC and reboot.
Now you can run AdAway: download files and apply ad blocking.
Done!
Click to expand...
Click to collapse
have no idea how to write in command prompt
umo4u said:
have no idea how to write in command prompt
Click to expand...
Click to collapse
Windows button+R>Type cmd>enter
It doesn´t works for me...It may wont work because i have superuser v3.2?
Might be but I'm not sure. I'm on 3.1.3 and it works fine. Although getting ADB to work in twrp recovery is a bit of a struggle for now.
What exactly doesn't work for you?
nightcrow said:
Might be but I'm not sure. I'm on 3.1.3 and it works fine. Although getting ADB to work in twrp recovery is a bit of a struggle for now.
What exactly doesn't work for you?
Click to expand...
Click to collapse
you can do same in advanced-> execute command (or maybe shell - do not remember the exact naming)
adb was not working for me, too.
nightcrow said:
Might be but I'm not sure. I'm on 3.1.3 and it works fine. Although getting ADB to work in twrp recovery is a bit of a struggle for now.
What exactly doesn't work for you?
Click to expand...
Click to collapse
Why do you need ADB when you have TERMINAL in twrp. Just wondering
Anyhow, ADB will be fixed soon
Thanks for the tutorial works great with Superuser 3.2. Just to clarify something, should I leave "fast boot" mode off now?
Michael
michpan said:
Thanks for the tutorial works great with Superuser 3.2. Just to clarify something, should I leave "fast boot" mode off now?
Michael
Click to expand...
Click to collapse
I think you can turn it on.
If you'll not access recovery... when you need recovery, turn fast boot off...
Sent from my hTC branded muffin
Since this information was buried in the other thread I am posting it here for visibility:
This will work only on CWM flashable zip stock (because you need CWM to flash the zip, obviously):
- Flash this first:
http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip
- Then flash this:
http://d-h.st/X1A
Click to expand...
Click to collapse
Now, people are wondering if it's possible to root from OTA/kdz update (like we originally rooted stock JB). In theory it should be. Basically what I did with this root fix is I've added one line to one of init scripts (which all run with root permissions). This line is starting the install-recovery.sh script (which is provided with SuperSU zip package). With KK it's not enough to just drop su binary to /system/xbin - you also have to start daemon (as root). Whatever rooting method you are trying to use has to add a line to one of startup scripts which starts the SuperSU script. If one such method is found please post here, I will also update the OP.
Varcain said:
Since this information was buried in the other thread I am posting it here for visibility:
Now, people are wondering if it's possible to root from OTA/kdz update (like we originally rooted stock JB). In theory it should be. Basically what I did with this root fix is I've added one line to one of init scripts (which all run with root permissions). This line is starting the install-recovery.sh script (which is provided with SuperSU zip package). With KK it's not enough to just drop su binary to /system/xbin - you also have to start daemon (as root). Whatever rooting method you are trying to use has to add a line to one of startup scripts which starts the SuperSU script. If one such method is found please post here, I will also update the OP.
Click to expand...
Click to collapse
Is there any way I can root the phone if i already upgraded to KitKat, but I don't have CWM ?
I'm guessing that RootKeeper does not work?
help
dSERiES said:
I'm guessing that RootKeeper does not work?
Click to expand...
Click to collapse
:cyclops:
whether we should try this guide with other sd card
[GUIDE] [ROOT] Root your LG Mini L40/L70/L90/G2
"update.zip"
looks positive
or try a Varcain "kk_root.zip"
consider and report
or for us, and there are many of us, the OTA upgrade, no root and CWM
pozz
I want to know if this method will work to me( I am using 4.4.2 OpenEu v20b.)
Изпратено от моят LG-D605 използвайки XDA-FORUM, благодарение на appyet.com
hepy
or loss from the root 4.4.2.sa ota update
working with this method, at least for me
I just installed TowelRoot V 2
and without a reboot got root
Then I installed the Super 1.9.4 (any little problems)
and got root .....
very happy
http://forum.xda-developers.com/showthread.php?t=2784416
[ROOT][EXPLOIT][APK]Root Your Phone[LG and other supported]
Originally Posted by giperborey View Post
So. I got it Thanks to all!
1) Download and install TowelRoot.
2) Varcain's patch
Add string "/system/etc/install-recovery.sh &" to the end of /system/etc/init.engdo.post_boot.sh
or just simply replace it by Varcain edited version
this file.
It's neccessary to get root after each boot.
NOTE!!! YOU MUST SAVE ORIGINAL PERMISSIONS TO THAT FILE (rw-, r--, r--)
3) Delete last string "/system/etc/install-recovery-2.sh" from the /system/etc/install-recovery.sh
NOTE!!! YOU MUST SAVE ORIGINAL PERMISSIONS TO THAT FILE (rwx, r-x, r-x)
Congratulation! You get rooted phone
IMPORTANT NOTE:
When I did it the first time, I tried to install SuperSU 2.0 from the Market. He did not want to upgrade properly. Finally I got a soft-broken phone and repaired it by kdz firmware flasher. I'm not sure that the reason of soft-brick was SuperSU, but without it root works fine.
since I'm not a programmer, I would ask Varcain and opportunity that we end up CWM,
so that we enjoy the OTA UPDATE CM11, PA Rom 4.4.3 .......
Get the conversation
skakavac65 said:
or loss from the root 4.4.2.sa ota update
working with this method, at least for me
I just installed TowelRoot V 2
and without a reboot got root
Then I installed the Super 1.9.4 (any little problems)
and got root .....
very happy
http://forum.xda-developers.com/showthread.php?t=2784416
[ROOT][EXPLOIT][APK]Root Your Phone[LG and other supported]
Originally Posted by giperborey View Post
So. I got it Thanks to all!
1) Download and install TowelRoot.
2) Varcain's patch
Add string "/system/etc/install-recovery.sh &" to the end of /system/etc/init.engdo.post_boot.sh
or just simply replace it by Varcain edited version
this file.
It's neccessary to get root after each boot.
NOTE!!! YOU MUST SAVE ORIGINAL PERMISSIONS TO THAT FILE (rw-, r--, r--)
3) Delete last string "/system/etc/install-recovery-2.sh" from the /system/etc/install-recovery.sh
NOTE!!! YOU MUST SAVE ORIGINAL PERMISSIONS TO THAT FILE (rwx, r-x, r-x)
Congratulation! You get rooted phone
IMPORTANT NOTE:
When I did it the first time, I tried to install SuperSU 2.0 from the Market. He did not want to upgrade properly. Finally I got a soft-broken phone and repaired it by kdz firmware flasher. I'm not sure that the reason of soft-brick was SuperSU, but without it root works fine.
since I'm not a programmer, I would ask Varcain and opportunity that we end up CWM,
so that we enjoy the OTA UPDATE CM11, PA Rom 4.4.3 .......
Get the conversation
Click to expand...
Click to collapse
But this is only temporary root. After restart of phone you must run this root again
help
Varcain said:
Since this information was buried in the other thread I am posting it here for visibility:
Now, people are wondering if it's possible to root from OTA/kdz update (like we originally rooted stock JB). In theory it should be. Basically what I did with this root fix is I've added one line to one of init scripts (which all run with root permissions). This line is starting the install-recovery.sh script (which is provided with SuperSU zip package). With KK it's not enough to just drop su binary to /system/xbin - you also have to start daemon (as root). Whatever rooting method you are trying to use has to add a line to one of startup scripts which starts the SuperSU script. If one such method is found please post here, I will also update the OP.
Click to expand...
Click to collapse
Hello.Thanks for the tutorial.I cant put the recovery mode as i dont know how to do it exactly.I know that i have to press the power button and volume up.If you help me i will be grateful.Thanks
Hi Varcain
Please could you update "varcain_rootfix.zip" for SuperSU v 2.01?
With the current "rootfix" does not work, and still wants to install SU binary.
Thanks for your work.
Sorry bad English.
Root Stock Recovery 4.4.2
Hello people,
After many attempts,
it seems that these instructions
definitely the easiest to root lg d 605, the OTA upgrade to 4.4.2.
A big thank you lioko27
Android.com.pl
Root Stock Recovery 4.4.2
Welcome.
Modification is used to zrotowania v20 firmware preloaded or OTA update for the PC (KDZ, Software LG)
This method does not allow upload custom recowery Cwm-fault is either with the powers or the installation file Cwm-work in progress
needs
* soft v20
* stock recovery
installation
charge applications:
- Towelroot (gives you temporary root)
https://towelroot.com/
Rom Toolbox Lite (or other manager with root privileges)
https://play.google.com/store/apps/d....toolbox&hl=pl
w / the apps you install on your phone, run Towelroot and click on the banner "make it ra 1 n"
charge pack zip
https://drive.google.com/file/d/0B1t...it?usp=sharing
move it through the USB cable or a memory card reader
run rom toolbox, click the root browser and copy the root file location v2.zip dp "cache" on your phone,
we leave the rot browser to the main menu click "scripter"-reboot recovery-run script-do
the phone will start in recovery, select apply update from the cache and select the copied package,
after the installation is completed, restart the phone and look forward to root.
The procedure is simple and Root after restart everything is OK
Now is already high time for CWM ....
Help Varcain....
and other developers ....
When I see what kind of support are second LG devices,
I was angry a lot.
Just look at what support has LG 9 and all will be clear.
The other devices that do not speak ....: (
Sorry for my english, going over translater,
greeting
I hope CWM soon ...: Kiklop:
hey I updated to v2.01 supersu
link
http://forum.android.com.pl/f1211/root-stock-recovery-4-4-2-a-439890/
I have seen a way for cwm to kitkat in a polish forum.
Instructions:
You must have adb.
1 Extract the zip on PC
2 Connect your phone to a PC with USB debugging enabled
3 Open the folder and press "shift" and the right mouse button
4 Select "Open command window here"
Follow the commands now:1 adb push aboot.img / data / local / tmp
2 adb shell
3 su
4 dd if = / data / local / tmp / aboot.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
5 exit
6 exit
7 adb push loki_flash / data / local / tmp
8 adb push recovery.img / data / local / tmp
9 adb shell
10 su
11 cd / data / local / tmp
12 chmod 777 loki_flash
13 ./loki_flash recovery recovery.img
14 reboot recovery
After your phone will reboot in cwm mode.When i did it rebooted automatically with an error:HW reset was detected.Dont worry just press the turn on button for 20 sec and the phone will reboot without giving that error again.
Big thanks to szymel00 a user of a polish android forum.
The link for the zip: (http://d-h.st/2kk)
Tested without any virus.
I didn't have to flash anything
I used the app KingRoot(not in appstore). It just rooted and it was just done. Later that day it rooted jelly bean version as well.
PS! You have to allow unknown sources when running apk-s from outside play store.
-------THIS GUIDE IS NO LONGER NEEDED------
If your on a rootable version follow the guide and instructions to install a pre rooted Firmware, with Rbox's custom recovery.
This I supposed was good to use to have SuperSU before we had any type of recovery.
-----UPDATED V3-----NEW DOWNLOAD LINKS-----
*PLEASE READ THROUGH THE FULL GUIDE BEFORE STARTING.*
FIRE STICK Replace King/o Root with SuperSU v3.
Thanks @joojoobee666 for his suggestions on layout of the guide to try make it more understandable to folk and also to incorporate a step into the script to make it a little easier still.
First off i am not responsible for your device, if you want to wait for a custom recovery (if one is even being made) that is your choice. Ive spent 2 days trying all possible ways to accomplish this and made it as easy as i could for you.
REMEMBER GUYS, the process for this to work is root with KINGOROOT - reboot-root with KINGROOT - reboot - run the commands - uninstall KINGOROOT. Failing to follow the order of the steps could soft brick you.
Prerequisites
Fire Stick
Fire OS 5.0.5 (if your on anything other than 5.0.5 use my other guide to downgrade to 5.0.5 here:
http://forum.xda-developers.com/fire-tv/development/fire-tv-stick-downgrade-firestarter-3-2-t3399298 ) dont forget to block updates again.
An understanding that 2 separate root programs are used in this guide KINGO ROOT and KING ROOT.
Installation Procedure :
You must follow these steps exactly as they are here, any deviation from this could cause you to brick (which is undo able so dont worry too much)
If you are not already rooted you need to root with KINGO ROOT. Once rooted reboot your Fire Stick. download it from here :
https://root-apk.kingoapp.com/kingoroot-download.htm
Your now able to follow the guide after you Root with KINGO ROOT.
Procedure
1.) Download the rar file containing the scripts and APKS:
http://www.filedropper.com/firestickroot_2
http://s000.tinyupload.com/?file_id=73723140467469181970
http://www.megafileupload.com/7nfv/firestickroot.rar
2.) Extract the file pack in the rar to /sdcard on your Fire Stick, PLEASE DOUBLE CHECK THIS. YOU NEED TO HAVE THE FOLDER STRUCTURE CORRECT OR IT COULD CAUSE PROBLEMS. YOU SHOULD HAVE /SDCARD/FIRESTICKROOT/CONTENTS . Inside the firestickroot folder you will see KING ROOT, install this and open it. Grant any permissions to it and let it take over root. When its finished, reboot your Fire Stick.
3.) Open an ADB Shell connection to the device. You should now see a prompt like this:
[email protected]:/ $
4.) Run the "su" command and choose "Allow" when prompted by KINGROOT on the screen. If successful, you should now see the following in the terminal:
[email protected]:/ $ su
[email protected]:/ #
5.) Run the following command:
sh /sdcard/firestickroot/root.sh
if successful you should see something similar to this
[email protected]:/ # sh /sdcard/firestickroot/root.sh
-----------------------------------------
-----------------------------------------
---FireStick SuperSU Tool by Sconnyuk----
Thanks to Mr.W0lf for the original script
------Thanks @Chainfire for SuperSU -----
--------Swap KingRoot for SuperSU--------
-----------------------------------------
-----------------------------------------
/system/bin/am[8]: app_process: not found
/system/bin/pm[6]: app_process: not found
/system/bin/am[8]: app_process: not found
/system/bin/pm[6]: app_process: not found
rm: /system/app/Kinguser.apk: No such file or directory
/system/bin/am[8]: app_process: not found
/system/bin/pm[6]: app_process: not found
chattr: stat /system/bin/ddexe: No such file or directory
rm: /system/bin/ddexe: No such file or directory
chattr: stat /system/usr/iku/isu: No such file or directory
rm: /system/usr/iku: No such file or directory
rm: /dev/reportroot: No such file or directory
rm: /system/app/Kinguser: No such file or directory
rm: /data/data-lib/king: No such file or directory
----------------INSTALLING SU BINARIES--------------------
cp: /system/xbin/su: Text file busy
mkdir failed for /system/bin/.ext, File exists
ln: /system/bin/install-recovery.sh: File exists
cp: /system/bin/mksh: No such file or directory
pkg: /sdcard/firestickroot/superuser.apk
Success
-----------Your Welcome--------------
6.) Run the SuperSU application, go to settings and un-check Enable Superuser then re-check it.
7.) Reboot the device (either hold play and select or run "reboot" from the ADB Shell prompt)
8.) Open ADB Shell once again and run "su". This time you should see the SuperSU prompt asking to allow the ADB Shell process to run as root.
9.) Uninstall KINGOROOT
10.) If you have any reminents of KING ROOT installed uninstall them, if it wont let you uninstall, re-install KING ROOT but DONT OPEN IT! then you can uninstall it.
IF YOU RUN INTO SOFTBRICK ISSUE (stuck at fire tv logo)
Make sure you have ADB drivers properly installed in your windows pc/laptop.
connect a genuine usb lead to the firestick/pc.
download the windows version of KINGO ROOT and install it.
open KINGO ROOT on the pc with Fire Stick connected up to pc and tv.
wait for the button to pop up and click root.
if you dont see AFTV or get enable debugging in the KINGO ROOT program on pc/laptop please unplug the stick from usb and replug it back in.
if this still wont work restart the pc/laptop or try another pc/laptop.
you should after clicking root boot back up into your homescreen, if it doesnt boot back into your homescreen automatically, wait around 5 minutes and unplug usb and re-plug it again.
Thumbs up if ive helped
If anyone can make use of another app from chainfire, Flashfire, as it now will work with chainfires Su binaries installed. The app allows for backup/flash all partitions/install zips etc. Im not sure if its fully working or maybe an older version might?
Anyway ill leave that for anyone who might want to test that app out.
*IMPORTANT*
If you still cant seem to manage this, delete he associated KINGOROOTS SUPERUSER manually, then right after you have installed KINGROOT and rebooted navigate to /system/xbin and delete the file daemonsu. When the script finishes run it a second time, if you dont get chainfires SuperSU installed manually install it. This is included in the script to carry out this task but seems it wont work for everyone.
sconnyuk said:
be back soon with re-written guide v2 that is much simpler.
Click to expand...
Click to collapse
:good: i went out and bought the device for this process. was going to pull the trigger on the long complicated route. can you throw together a twrp image for us as well?
asafegous said:
:good: i went out and bought the device for this process. was going to pull the trigger on the long complicated route. can you throw together a twrp image for us as well?
Click to expand...
Click to collapse
Ive re done the guide made it much simpler, spent 2 days on it trying all ways to brick my device in the process and could not brick it no matter how hard i screwed up.
This newer guide should work 1st time if followed correctly, and you will be shot of Kingo/o Root.
Im real sorry but to make a custom recovery is a little beyond me.
sconnyuk said:
*Update*
I am not responsible for your device, if you want to wait for a custom recovery (if one is even being made) that is your choice. Ive spent 2 days trying all possible ways to accomplish this and made it as easy as i could for you.
The guide has been re done again by myself as it was far too long and although there was zero chance of bricking (with the use of Kingo Roots windows tool) ive put v2 together which is much simpler and all in a single script you will have no chance of any brick, with success the first attempt
This guide is for Fire Stick 5.0.5, you need root access with KingRoot, so if your rooted with Kingo Root please update your root app with the KingRoot apk in this pack, it will take over your Kingo Root and use King User.
Please note, you must root originally with Kingo Root, restart then Re-root with KingRoot then restart again, if not you will find that after a restart you will get unrooted.
Also be aware, if you have followed this through and still after a restart you are unrooted navigate to /root/system/xbin and delete the file daemonsu, then try again.
Download the pack here : http://s000.tinyupload.com/?file_id=02940258229221060594
Extract it in your Fire Sticks /sdcard directory.
You should have a folder in your Fire Sticks /sdcard directory called firestickroot.
Ive noticed myself that if im at the standard fire tv stick launcher sometimes king/o root fails to grant permissions so for the next step be aware and maybe have firestarter/app starter launcher loaded up.
Connect your Pc/Laptop/terminal to your fire stick and type the following commands. (grant permissions to all)
su
sh /sdcard/firestickroot/root.sh
Thats it, the script will remove KING ROOT and all associated files and install su binary and SuperSU apk.
Once you restart make sure you are using ChainFires SuperSu and uninstall Kingo Roots stuff.
Thumbs up if ive helped
Click to expand...
Click to collapse
II
@sconnyuk, could you pls add another d/l mirror? Thx
dave157 said:
@sconnyuk, could you pls add another d/l mirror? Thx
Click to expand...
Click to collapse
I certainly will when I get home later.
This is not working for me here. Here's the log:
Code:
-----------------------------------------
-----------------------------------------
---FireStick SuperSU Tool by Sconnyuk----
Thanks to Mr.W0lf for the original script
------Thanks @Chainfire for SuperSU -----
--------Swap KingRoot for SuperSU--------
-----------------------------------------
-----------------------------------------
Success
Success
rm: /system/app/Kinguser.apk: is a directory
rm: /system/app/Kinguser: No such file or directory
Failure [DELETE_FAILED_INTERNAL_ERROR]
/sdcard/firestickroot/root.sh[34]: can't create /system/xbin/daemonsu: Text file busy
rm: /data/data/com.kingroot.RushRoot: No such file or directory
rm: /data/data/com.kingroot.kinguser: No such file or directory
rm: /data/data/com.kingroot.master: No such file or directory
chattr: stat /system/bin/ddexe: No such file or directory
rm: /system/bin/ddexe: No such file or directory
chattr: stat /system/usr/iku/isu: No such file or directory
rm: /system/usr/iku: No such file or directory
rm: /dev/reportroot: No such file or directory
rm: /system/app/Kinguser: No such file or directory
rm: /data/data-lib/king: No such file or directory
----------------INSTALLING SU BINARIES--------------------
mkdir failed for /system/bin/.ext, File exists
ln: /system/bin/install-recovery.sh: File exists
cp: /system/bin/mksh: No such file or directory
pkg: /sdcard/firestickroot/superuser.apk
Failure [INSTALL_FAILED_DUPLICATE_PERMISSION perm=android.permission.ACCESS_SUPERUSER pkg=com.kingouser.com]
-----------Your Welcome--------------
I removed the com.kingouser.com package manually and was able to install the Superuser APK but when I run Superuser, it says the SU binaries are not installed. I've reinstalled KingRoot for now but this script is NOT bullet proof. I'm not sure exactly what state this is leaving me in but root seems to be working again after reinstalling KingRoot. Should I be completely removing KingoRoot BEFORE running this script? If so, the instuctions hould mention it. As of now, I'm afraid to do so for fear of bricking this thing. Any thoughts?
joojoobee666 said:
This is not working for me here. Here's the log:
Code:
-----------------------------------------
-----------------------------------------
---FireStick SuperSU Tool by Sconnyuk----
Thanks to Mr.W0lf for the original script
------Thanks @Chainfire for SuperSU -----
--------Swap KingRoot for SuperSU--------
-----------------------------------------
-----------------------------------------
Success
Success
rm: /system/app/Kinguser.apk: is a directory
rm: /system/app/Kinguser: No such file or directory
Failure [DELETE_FAILED_INTERNAL_ERROR]
/sdcard/firestickroot/root.sh[34]: can't create /system/xbin/daemonsu: Text file busy
rm: /data/data/com.kingroot.RushRoot: No such file or directory
rm: /data/data/com.kingroot.kinguser: No such file or directory
rm: /data/data/com.kingroot.master: No such file or directory
chattr: stat /system/bin/ddexe: No such file or directory
rm: /system/bin/ddexe: No such file or directory
chattr: stat /system/usr/iku/isu: No such file or directory
rm: /system/usr/iku: No such file or directory
rm: /dev/reportroot: No such file or directory
rm: /system/app/Kinguser: No such file or directory
rm: /data/data-lib/king: No such file or directory
----------------INSTALLING SU BINARIES--------------------
mkdir failed for /system/bin/.ext, File exists
ln: /system/bin/install-recovery.sh: File exists
cp: /system/bin/mksh: No such file or directory
pkg: /sdcard/firestickroot/superuser.apk
Failure [INSTALL_FAILED_DUPLICATE_PERMISSION perm=android.permission.ACCESS_SUPERUSER pkg=com.kingouser.com]
-----------Your Welcome--------------
I removed the com.kingouser.com package manually and was able to install the Superuser APK but when I run Superuser, it says the SU binaries are not installed. I've reinstalled KingRoot for now but this script is NOT bullet proof. I'm not sure exactly what state this is leaving me in but root seems to be working again after reinstalling KingRoot. Should I be completely removing KingoRoot BEFORE running this script? If so, the instuctions hould mention it. As of now, I'm afraid to do so for fear of bricking this thing. Any thoughts?
Click to expand...
Click to collapse
As the guide says if you have problems navigate to /system/xbin and delete daemonsu
First make sure you are rooted with KINGO ROOT - reboot
Second install the KING ROOT apk in the pack you downloaded and placed in /sdcard. let it take over root and should install its own King User apk. - reboot
Third step :
su
sh /sdcard/firestickroot/root.sh
The script is no way bulletproof but it works, if anyone would like to moddify it to better suit Fire Stick that would be great. As for bricking, i understand that nothing is 100 percent fail proof as in root etc but the way this script is set out ive tested it for 2 days uninstalling root re installing king/go in different combinations and could not brick my stick, i got a few restarts but that was all. The v1 guide i did had higher chance of bricking (trust me i tested the crap out of it) and everytime my stick failed to boot i plugged it into my laptop and ran either kingo or king root windows versions and it re rooted and got me back up and running, everytime.
I tried all different combinations to try brick and not be able to bring it back but always did.
The v2 guide here what your using i couldnt get my stick to brick once.
sconnyuk said:
As the guide says if you have problems navigate to /system/xbin and delete daemonsu
First make sure you are rooted with KINGO ROOT - reboot
Second install the KING ROOT apk in the pack you downloaded and placed in /sdcard. let it take over root and should install its own King User apk. - reboot
Third step :
su
sh /sdcard/firestickroot/root.sh
The script is no way bulletproof but it works, if anyone would like to moddify it to better suit Fire Stick that would be great. As for bricking, i understand that nothing is 100 percent fail proof as in root etc but the way this script is set out ive tested it for 2 days uninstalling root re installing king/go in different combinations and could not brick my stick, i got a few restarts but that was all. The v1 guide i did had higher chance of bricking (trust me i tested the crap out of it) and everytime my stick failed to boot i plugged it into my laptop and ran either kingo or king root windows versions and it re rooted and got me back up and running, everytime.
I tried all different combinations to try brick and not be able to bring it back but always did.
The v2 guide here what your using i couldnt get my stick to brick once.
Click to expand...
Click to collapse
I initially WAS rooted with Kingo, re-rooted with King and rebooted, then ran script. But it FAILED to complete so I didn't try the removal of deamonsu since it never completed. Is that going to fix the error I received when installed Superuser.apk? That error seems to be unrelated to the leftover daemonsu as it's in regards to a conflict with packages installed from KingoRoot. Review of the scripts shows that they in NO WAY remove that application (com.kingouser.com) so I imagine I will end up in the same spot....If I get there. I'm currently stuck on "fireTVstick" logo after trying to Re-Root with Kingo as you suggested. I don't think this looks very good...
joojoobee666 said:
I initially WAS rooted with Kingo, re-rooted with King and rebooted, then ran script. But it FAILED to complete so I didn't try the removal of deamonsu since it never completed. Is that going to fix the error I received when installed Superuser.apk? That error seems to be unrelated to the leftover daemonsu as it's in regards to a conflict with packages installed from KingoRoot. Review of the scripts shows that they in NO WAY remove that application (com.kingouser.com) so I imagine I will end up in the same spot....If I get there. I'm currently stuck on "fireTVstick" logo after trying to Re-Root with Kingo as you suggested. I don't think this looks very good...
Click to expand...
Click to collapse
OK, run the windows version of KingoRoot on your pc/laptop. if it fails first time unplug usb then plug it back in and it should root you and get you back up and running.
Its failing to complete because the daemonsu file is there. Delete it and the script will finish and uninstall KingRoot.
Nowhere in the guide says you must install SuperSU apk, the script does this for you. All you should be left with when it completes is KingoRoot and a newly installed SuperSU apk v2.01
sconnyuk said:
OK, run the windows version of KingoRoot on your pc/laptop. if it fails first time unplug usb then plug it back in and it should root you and get you back up and running.
Its failing to complete because the daemonsu file is there. Delete it and the script will finish and uninstall KingRoot.
Click to expand...
Click to collapse
Thanks. Will give all that a go here and let you know.:good:
joojoobee666 said:
Thanks. Will give all that a go here and let you know.:good:
Click to expand...
Click to collapse
Definitely want to know if everyone is having success, i did not make the scripts used here, i just slightly modified them and merged more instructions.
Everytime i run the script it works and if it wasnt for the fail safe of Windows Kingo Root i would not of put the guide up.
sconnyuk said:
Definitely want to know if everyone is having success, i did not make the scripts used here, i just slightly modified them and merged more instructions.
Everytime i run the script it works and if it wasnt for the fail safe of Windows Kingo Root i would not of put the guide up.
Click to expand...
Click to collapse
Hmm...I'm not having any luck with the KingoRoot windows app. It's not even getting to the point where it can fail. "Connecting...Please enable USB Debugging mode" is where it's getting stuck. If I remove the fire stick and plug it back in, nothing happens in the program. It still just sits at that screen. I can adb into it but I do not get root (of course). Should I maybe relflash the 5.0.5 update.bin I have sitting on the SD card (if possible)?
joojoobee666 said:
Hmm...I'm not having any luck with the KingoRoot windows app. It's not even getting to the point where it can fail. "Connecting...Please enable USB Debugging mode" is where it's getting stuck. If I remove the fire stick and plug it back in, nothing happens in the program. It still just sits at that screen. I can adb into it but I do not get root (of course). Should I maybe relflash the 5.0.5 update.bin I have sitting on the SD card (if possible)?
Click to expand...
Click to collapse
Just restart the KingoRoot app and plug unplug firetick and plug it back in, it will eventually detect it.
If not, run kingroot windows tool if that works then ok, if not dont close it open kingoroot up and then try, you will get it detected it happened to me a few times when i did v1 guide
sconnyuk said:
Just restart the KingoRoot app and plug unplug firetick and plug it back in, it will eventually detect it.
Click to expand...
Click to collapse
I think I've done all that over 10 times, same thing keeps happening. The one thing I have gotten twice is a window titles "Notification" that explains that I will need to allow debugging on the device for the app. Obviously, I cannot do that. It eventually goes away on its own then hangs at the aforementioned screen again. Any other suggestions?
joojoobee666 said:
I think I've done all that over 10 times, same thing keeps happening. The one thing I have gotten twice is a window titles "Notification" that explains that I will need to allow debugging on the device for the app. Obviously, I cannot do that. It eventually goes away on its own then hangs at the aforementioned screen again. Any other suggestions?
Click to expand...
Click to collapse
restart your pc/laptop try another usb port ? did you try KINGROOT windows app then if that goes ok fine, if not dont close it open KINGO ROOT windows app and try it then, like i said i had this a few times when i did the v1 guide but everytime i got it back up again.
sconnyuk said:
restart your pc/laptop try another usb port ? did you try KINGROOT windows app then if that goes ok fine, if not dont close it open KINGO ROOT windows app and try it then, like i said i had this a few times when i did the v1 guide but everytime i got it back up again.
Click to expand...
Click to collapse
I was just in the middle of installing the KingRoot app. I ran it and it said it was successful. Should I just reboot now? (side note, there is not daemonsu in /system/bin currently)
joojoobee666 said:
I was just in the middle of installing the KingRoot app. I ran it and it said it was successful. Should I just reboot now?
Click to expand...
Click to collapse
If it wont start up in a few minutes yes just unplug and plug it back in.
Like i said, i would not of put guide up if there wasnt the failsafe methods of KING/O for windows in place.
sconnyuk said:
If it wont start up in a few minutes yes just unplug and plug it back in.
Like i said, i would not of put guide up if there wasnt the failsafe methods of KING/O for windows in place.
Click to expand...
Click to collapse
That was the only reason I decided to go for it. However, It's still stuck on the fireTV Stick logo...after multiple reboots
joojoobee666 said:
That was the only reason I decided to go for it. However, It's still stuck on the fireTV Stick logo...after multiple reboots
Click to expand...
Click to collapse
Let it sit there a while, will probably go to optimising screen.
If it wont re root it with Kingo/king on pc and dont restart after, just let it sit and it should go to optimising screen.
I have lenovo vibe shot and I have updated it with Android 6.0.1, rooted it with SuperSU 2.78
and installed systemless xposed framework on it all of the things are going well but
recently I tried to change the boot animation and I realized that I dont and I cant have writing access
to /system and any of its sub folders (i want to replace a couple of MP4 files inside /system/media
no matter if I use mount commands from adb from PC or any other app in my mobile, write access will not be given
for example ES File explorer says it is read only, when I click on write and click OK, it will show no error, but going to
same setting again it shows read only selected again
similar is the case with Root Browser
I think it is due to systemless root
But is there any way I can get write acccess to /system/media ???
plz help
usman400 said:
I have lenovo vibe shot and I have updated it with Android 6.0.1, rooted it with SuperSU 2.78
and installed systemless xposed framework on it all of the things are going well but
recently I tried to change the boot animation and I realized that I dont and I cant have writing access
to /system and any of its sub folders (i want to replace a couple of MP4 files inside /system/media
no matter if I use mount commands from adb from PC or any other app in my mobile, write access will not be given
for example ES File explorer says it is read only, when I click on write and click OK, it will show no error, but going to
same setting again it shows read only selected again
similar is the case with Root Browser
I think it is due to systemless root
But is there any way I can get write acccess to /system/media ???
plz help
Click to expand...
Click to collapse
Root properly
I did it twice using TWRP I flashed Super SU 2.78 2 times, it never showed any error
and went fine
Plz tell me a little more if you mean something else by root properly
Any app that needs root access is working perfectly fine except for this permission
setting issue on /system