Database Users

[ROOT] Stock ICS Leak One-Click Root Tool

Hi all!
First off, I'm new to xda Developers so please excuse me if this is in the wrong forum! I thought I'd post information about a tool I wrote here which roots stock 4.0.3 leak on the A500, A501 and assumingly the A200 too. Its literally one click - just enable USB debugging. "ICS Root" also installs, optionally, FaceLock and Trebuchet (although FaceLock doesn't want to work. It lets you set it up though =P)
Since version 5.0.1 this also now works with the new 0.022.00 leak!
The full post is over at TegraOwners: http://forum.tegraowners.com/viewtopic.php?f=30&t=350
The only real system requirements are Windows (with .Net Framework 4) and an Iconia on the stock 4.0.3 leak. I hope somebody finds this useful its been tested by myself and a couple of TegraOwners users and it works well.
In terms of the technique used, it uses the great Jay Freeman's mempodroid exploit to gain root at which point it mounts /system rw and installs su, busybox and Superuser.apk so no real surprises there. Installing Trebuchet adds that apk to /system/app and installing FaceLock installs the apk to /system/app before installing the pittpatt folder to the flexrom (mounted as /system/vendor). I plan to open source it when all the requested features have been implemented and the code has been cleaned up.
Thanks!
~blackthund3r
EDIT 14/05/2012: ICS Root 7 is out enjoy!
Sent from my A500 using Tapatalk

cwm version?
why would it not work with cwm version?

With this tool does system remain writeable after rooting?

What about flashing CWM with acer recovery installer once rooted? I guess it would screw the bootloader...

lowsum said:
What about flashing CWM with acer recovery installer once rooted? I guess it would screw the bootloader...
Click to expand...
Click to collapse
If you are on the cwm with the HC boot loader it should work as Its Magic will be run..
if you are on the new boot loader as in the full non modded leak.. It will give you secure boot error ..
The new boot loader Blocks its magic.

Thanks
Hey this worked easy. I had to re-install USB drivers and make sure I had the latest from Google. Other then that, hit the button, wait about 1.5 minutes, and it rebooted! No problems thus far! Thanks Again!

JeanBubu said:
why would it not work with cwm version?
Click to expand...
Click to collapse
It would but the cwm one, afaik, is prerooted?
Sent from my A500 using Tapatalk

root doesnt work like its supposed to. i know its only half root due to the bootloader, but terminal emulator flat out says i'm not rooted after this despite sixasis working and titanium backup/root checker both saying i have root and busybox. i'm going to post this on TO as well for you incase you dont check here often.

nifterific said:
root doesnt work like its supposed to. i know its only half root due to the bootloader, but terminal emulator flat out says i'm not rooted after this despite sixasis working and titanium backup/root checker both saying i have root and busybox. i'm going to post this on TO as well for you incase you dont check here often.
Click to expand...
Click to collapse
That's storage cos terminal works for me and running su in an adb shell works great too.
Code:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ su
# exit
[email protected]:/ $ su
#
Sent from my A500 using Tapatalk

SteamBishop said:
Hey this worked easy. I had to re-install USB drivers and make sure I had the latest from Google. Other then that, hit the button, wait about 1.5 minutes, and it rebooted! No problems thus far! Thanks Again!
Click to expand...
Click to collapse
You're welcome and I'm glad it worked!
Sent from my A500 using Tapatalk

After reading the other post, I have found that I cannot write to the system directory from the device itself. The folder attributes indicate that it is set to write, however File Explorer HD will not let me. I have tried to create a folder in the /system and it will not accept the addition. The strange thing is that Root Check says it is rooted, File Explorer HD accepts putting it into Root Explore, but that is it. It is odd. I will try to reapply the Root to see if that makes a difference.

SteamBishop said:
After reading the other post, I have found that I cannot write to the system directory from the device itself. The folder attributes indicate that it is set to write, however File Explorer HD will not let me. I have tried to create a folder in the /system and it will not accept the addition. The strange thing is that Root Check says it is rooted, File Explorer HD accepts putting it into Root Explore, but that is it. It is odd. I will try to reapply the Root to see if that makes a difference.
Click to expand...
Click to collapse
Please, read the op before bringing this up. This method is for half root, its the only way possible right now on stock leak ics. There is a special script you need to use to mpunt system. You can find it in the stock leak thread, run it in terminal or use rom toolbox and set it as a script to run at boot because rebooting loses write privileges.

nifterific said:
Please, read the op before bringing this up. This method is for half root, its the only way possible right now on stock leak ics. There is a special script you need to use to mpunt system. You can find it in the stock leak thread, run it in terminal or use rom toolbox and set it as a script to run at boot because rebooting loses write privileges.
Click to expand...
Click to collapse
Sorry for offending you and whoever else it did. Thank you for pointing that script out in that post. My intent was to offer a second comment to your assessment..

nifterific said:
Please, read the op before bringing this up. This method is for half root, its the only way possible right now on stock leak ics. There is a special script you need to use to mpunt system. You can find it in the stock leak thread, run it in terminal or use rom toolbox and set it as a script to run at boot because rebooting loses write privileges.
Click to expand...
Click to collapse
I have a better script which I'll be releasing as an update to the root app this morning hopefully. It'll be a terminal command to remount rw.
Sent from my A500 using Tapatalk

New update out!!
blackthund3r said:
I have a better script which I'll be releasing as an update to the root app this morning hopefully. It'll be a terminal command to remount rw.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Version 3 came out this morning
It features some bug fixes as well as a completely new remount menu which mounts /system rw properly on the fly. Tested with a busybox installer app
Enjoy!

Thanks for your tool blackthund3r !
I tried it with the new leak from this morning and it doesn't seem to work anymore
Edit :
Just to be a little more specific, the app says the process was OK and state that the tablet is rooted but the tablet doesn't reboot by itseld and su is not installed. I tried to install su manually but it's unable to find a previous su package on the system.

paugustin said:
Thanks for your tool blackthund3r !
I tried it with the new leak from this morning and it doesn't seem to work anymore
Edit :
Just to be a little more specific, the app says the process was OK and state that the tablet is rooted but the tablet doesn't reboot by itseld and su is not installed. I tried to install su manually but it's unable to find a previous su package on the system.
Click to expand...
Click to collapse
ah okay it appears a completely new leak has been released. It is possible that the mempodroid exploit has been patched up. I'm gonna look into it soon. I can't much tonight - I have school work. I'll see what can be done and what the differences between leaks are.
Sent from my A500 using Tapatalk
EDIT: mempodroid hasn't been patched See ICS Root v3.1

Hi blackthund3r
Thanks for the update 3.1 but could you please fix the problem on your hosting website? clicking on this file send to an error warning.
The other files can be downloaded though.

can someone post a mirror to the 3.1 version? current link is not working.
can somebody also confirm, if i root with this tool, i will be able to reinstall my clockworkmod recovery through 'acer recovery installer' and flash any other cwm rom? or do i have to downgrade to honeycomb 3.01, install iconiaroot for honeycomb and then acer recovery installer?

Gersma,
I'll be able to answer to your question as soon as I'll be able to download this tool and test it.

Viper4Android S-ON/OFF Workaround

I have successfully created my own bypass to get viper4android to work. Always create a full backup before attempting =)
1. Download viper4android APK
2. Download Root Explorer from the playstore
3. Install Both Apps
4. Launch Root Explorer
5. In root explorer go to /system/lib/soundfx and copy the folder to /data/ (make a soundfx folder)
6. Also copy /system/etc/audio_effects.conf to the /data/soundfx/ folder
7. Using root explorers menu you can create a shortcut (symbolic link) make a shortcut of the /data/soundfx/ folder and a shortcut of the /data/soundfx/audio_effects.conf
8. Boot into TWRP
9.Mount the system partition
10. Rename /system/lib/soundfx to /system/lib/soundfx2
11. Copy soundfx shortcut create earlier to /system/lib/ it will look like a "file" to TWRP
12.Rename the /system/etc/audio_effects.conf to /system/etc/audio_effects.conf1
13. Copy the audio_effects shortcut into /system/etc/ (be sure its name matches the old exactly)
15. Reboot
16. Launch Viper and install driver
I haven't dealt with LPA yet (hasn't had an issue) nor have I done any other modifications at this time which are avail on the viper4android thread.
I was just thinking about symbolic links to get around this S-OFF/ON issue and it appears they work and technically as a workaround we could symbolically link everything in system to another location and access it all. This could easily be put into ROM builds now at least as well!
Build.Prop may be useful to move out via sym link as well

It's not a matter of being s-on or s-off.. It's a matter of having write protection removed then you can do all of that. S-off just allows you to flash any partition on the device.. (radio, hboot etc..) plus you can flash any ruu you want as long as you change to supercid
There is a kernel module in dev and it's working great on my device.

On M7 it seems to me that the S-OFF also disables write protection system on stock rom
Envoyé de mon HTC Butterfly s en utilisant Tapatalk

migascalp said:
On M7 it seems to me that the S-OFF also disables write protection system on stock rom
Envoyé de mon HTC Butterfly s en utilisant Tapatalk
Click to expand...
Click to collapse
But you don't need s-off to disable write protection. You just need a kernel with it disabled or the kernel module which flair posted in the development section. I'm using it and am able to write to the system fine and I'm s-on. The title of the thread should be something like "with write protection on" not s-on.

I just wanted to clarify that with S-OFF this module is useless

migascalp said:
I just wanted to clarify that with S-OFF this module is useless
Click to expand...
Click to collapse
You don't need to clarify that to me. I'm very well aware of that. My point was that for this topic you don't need s-off for this to work.. You just need write protection off. Whether that be with with s-off or with a module.. This working is not dependant on s-off.. It's dependant on write protection being off. That is my point.
Sent from my HTC One using Tapatalk

For anyone who wants the stock kernel with write protection off just use this JMZM8 Kernel and then just install busybox like regular and boom Viper4Android, literally made my M8 sound so much better (not that it wasn't already awesome)

worked with htc 816 running indian stock, which still has no s-off at the moment,
had to go to twrp recovery terminal command, to make the symbolic links or move directories....
viper4android made a lot of difference in this particular model.
the next thing would be to make viper4a a system app, since it tended to close and thus lower the volume, usually after some time.

helloicanseeu said:
worked with htc 816 running indian stock, which still has no s-off at the moment,
had to go to twrp recovery terminal command, to make the symbolic links or move directories....
viper4android made a lot of difference in this particular model.
the next thing would be to make viper4a a system app, since it tended to close and thus lower the volume, usually after some time.
Click to expand...
Click to collapse
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off

One-M8-Master said:
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off
Click to expand...
Click to collapse
will try to make it work .... meanwhile from what i gathered in a htc 816 facebook group, most indian pple buying this particular model seems to have no clue about making the most out of its audio properties ... the 816's true selling points were its larger 5.5 " size, great audio output, and relatively low cost compared with other htc flagship models.

One-M8-Master said:
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off
Click to expand...
Click to collapse
done ... went to twrp recovery,
moved "com.vipercn.viper4android_v2-1.apk" from ""/data/app" to "/system/priv-app"
moved "com.vipercn.viper4anddroid_v2-1/libV4AJniUtils.so" from to "/data/app-lib" to "/system/lib/"
should be working fine, havent extensively tested it out yet though,
reported as a system app, and viper driver is running.

I Can't Get data/soundfx Shortcut to Transfer to /System/lib
In the opening instructions, #11 says that we have to transfer the data/soundfx shortcut to /system/lib. Everytime I try it with TWRP it just says failed. If I try it with root browser,
it will say successful until the phone is rebooted. Any help would be appreciated. I am a newbie to these things.

BaltColts said:
In the opening instructions, #11 says that we have to transfer the data/soundfx shortcut to /system/lib. Everytime I try it with TWRP it just says failed. If I try it with root browser,
it will say successful until the phone is rebooted. Any help would be appreciated. I am a newbie to these things.
Click to expand...
Click to collapse
u need to install twrp recovery for htc 816.
get it from "TeamWin Projects" website.
after successfully installing twrp, boot into recovery mode, use twrp to move data/soundfx shortcut to /system/lib, etc...
hope u get to install viperfx successfully and make full blast of the great audio output of this big value music machine, makes a near perfect combo with my music angel cube speakers(as far as mine human ears tell me), anyone using this combo too?
later htc models based on mediatek chipsets seem to have horrible audio outputs ... maybe even iphone 6 and samsung note4 cant beat htc 816 where mp3 output is concerned
background: htc 816 doesnt has s-off, so its always s-on, which means if u try to write to the "/system" folder, the phone will trigger a reboot immediately, to prevent any modifications to the folder. root browser will not be able to write to /system folder, even if the phone has root access, due to this s-on protection. The only way to edit /system folder is to boot to twrp (in recovery mode).

blewis540 said:
I have successfully created my own bypass to get viper4android to work. Always create a full backup before attempting =)
1. Download viper4android APK
2. Download Root Explorer from the playstore
3. Install Both Apps
4. Launch Root Explorer
5. In root explorer go to /system/lib/soundfx and copy the folder to /data/ (make a soundfx folder)
6. Also copy /system/etc/audio_effects.conf to the /data/soundfx/ folder
7. Using root explorers menu you can create a shortcut (symbolic link) make a shortcut of the /data/soundfx/ folder and a shortcut of the /data/soundfx/audio_effects.conf
8. Boot into TWRP
9.Mount the system partition
10. Rename /system/lib/soundfx to /system/lib/soundfx2
11. Copy soundfx shortcut create earlier to /system/lib/ it will look like a "file" to TWRP
12.Rename the /system/etc/audio_effects.conf to /system/etc/audio_effects.conf1
13. Copy the audio_effects shortcut into /system/etc/ (be sure its name matches the old exactly)
15. Reboot
16. Launch Viper and install driver
I haven't dealt with LPA yet (hasn't had an issue) nor have I done any other modifications at this time which are avail on the viper4android thread.
I was just thinking about symbolic links to get around this S-OFF/ON issue and it appears they work and technically as a workaround we could symbolically link everything in system to another location and access it all. This could easily be put into ROM builds now at least as well!
Build.Prop may be useful to move out via sym link as well
Click to expand...
Click to collapse
Will this method work without busybox?
There is a very specific reason why I'd not like to use busybox, so this may end up being a very good solution for me.

fade2black101 said:
Will this method work without busybox?
There is a very specific reason why I'd not like to use busybox, so this may end up being a very good solution for me.
Click to expand...
Click to collapse
What's wrong with busybox? its a hidden process only used when an app like V4A calls for it, other then that it has no negative effect. why avoid it?
Besides this thread is disinfo, all this is not required to get V4A working, Go to this thread Here and follow instructions.

hi,
I have completed those steps, but the viper4android keeps asking me to install the driver.
I have tried also the steps from helloicanseeu. But still, not working.
please help me, because installing viper4android is never been this hard on my previous device. thank you.

i got stuck after flashing viper . stuck on htc logo then reboots back to recovery..

oulixeus said:
hi,
I have completed those steps, but the viper4android keeps asking me to install the driver.
I have tried also the steps from helloicanseeu. But still, not working.
please help me, because installing viper4android is never been this hard on my previous device. thank you.
Click to expand...
Click to collapse
Which phone u using? What stock rom? I was using stock indian on htc816.
---------- Post added at 09:12 PM ---------- Previous post was at 09:03 PM ----------
XskipperX said:
i got stuck after flashing viper . stuck on htc logo then reboots back to recovery..
Click to expand...
Click to collapse
U followed the steps by blewis?

Why it is so complicated..???.if s-on, unlock bootloader and flash a custom kernel (elementalx). In install options just choose to set SElinux permissive. Then, install driver for Viper and reboot. That is it. If s-off, start with kernel installation...
People are talking about that s-off gives full access to system partition - true but not correct. Unlocked bootloader gives write access to system folder, while s-off in addition allows to change partitions, bootloader, etc.
Sent from my HTC One M8 using XDA Free mobile app

uvt_novice said:
Why it is so complicated..???.if s-on, unlock bootloader and flash a custom kernel (elementalx). In install options just choose to set SElinux permissive. Then, install driver for Viper and reboot. That is it. If s-off, start with kernel installation...
People are talking about that s-off gives full access to system partition - true but not correct. Unlocked bootloader gives write access to system folder, while s-off in addition allows to change partitions, bootloader, etc.
Sent from my HTC One M8 using XDA Free mobile app
Click to expand...
Click to collapse
Welp, it's so complicated because NONE of the instructions seem to work for a huge number of us. I've tried like 5 "failsafe" methods but they just fail and fail.
ONE time I had it working and was all psyched, and then I restarted the phone at some point and that was the end of that. Never worked since.

SU not found

hi, 2months ago I root the device with cm-10.2.1-maguro all working as expected, till I liked to use voice recorder after recording stopped the app close, realize that has to do with root.
I couldnt find how to enable the app through superuser, so start to check for alternatives so I landed here
Code:
https://play.google.com/store/apps/details?id=eu.chainfire.supersu
no hope also with that, uninstalled. The problem :
through adb + eclipse I can browse the device folders when using adb root - OK
on device superuser still @ settings - OK
when on android terminal - and run the command su writes su not found!
then I red @ superSU GplayURL
Superuser access management runs through a so called "su binary". There can be only one of these at a time.
Click to expand...
Click to collapse
how I can restore the original cm-10.2.1-maguro su binary?

whokn0ws said:
hi, 2months ago I root the device with cm-10.2.1-maguro all working as expected, till I liked to use voice recorder after recording stopped the app close, realize that has to do with root.
I couldnt find how to enable the app through superuser, so start to check for alternatives so I landed here
Code:
https://play.google.com/store/apps/details?id=eu.chainfire.supersu
no hope also with that, uninstalled. The problem :
through adb + eclipse I can browse the device folders when using adb root - OK
on device superuser still @ settings - OK
when on android terminal - and run the command su writes su not found!
then I red @ superSU GplayURL
how I can restore the original cm-10.2.1-maguro su binary?
Click to expand...
Click to collapse
Have you tried installing a rooted ROM?
Sent from my Nexus 4 using Tapatalk

nada, just download the cm desktop + cm android and made the root, nothing else.. please, advise how I can fix it..

whokn0ws said:
nada, just download the cm desktop + cm android and made the root, nothing else.. please, advise how I can fix it..
Click to expand...
Click to collapse
What recovery do you have installed?
Sent from my Nexus 4 using Tapatalk

http://www.cyanogenmod.org/
from desktop navigate to http://get.cm (download app)
from mobile navigate to http://get.cm (download app)
mobile get rooted in ~15min
thanks

so I dont know anything else..

I used to have this issue (but I didn't realise I had lost root because of an app), so I just downloaded and reflashed SU and all was good.
Download and flash from recovery: http://download.chainfire.eu/282/SuperSU/

hmm tried I got :
- Mounting
- Removing old
- Extracting files
- Restoring files
- Settings Permissions
set_perm : some canges failed
E: Error in data/media/0/CWM-SuperSU-v0.98.zip
(Status 7)
Installation aborted
-- when tried sideload ^the same with :
E: Error in /tmp/update.zip
!?
@nicknc writes :
ClockworMod Recovery v6.0.4.7
[searching..searching..searching..]
the solution is to download the latest SuperSU zip aka
http://download.chainfire.eu/446/SuperSU/UPDATE-SuperSU-v1.99r3.zip
there isnot error7, installed rebooted su is there!.
the final Q, is how to enable an application to have root access (when SuperSU not prompt me) ?
Marvlesz thanks!

whokn0ws said:
the final Q, is how to enable an application to have root access (when SuperSU not prompt me) ?
Click to expand...
Click to collapse
When an app requests SU, you should be prompted. If you've set a default choice, you should be able to change that from the SU app. You should also be able to change previous choices from there as well.

basically the problem is :
1-voice recorder recording but no output
2-on built-in browser in any page has 'browse' to choose a file - the open dialog never opens! (aka facebook.com upload photo or imgur.com)
how I will resolve these? googlesearch=0%

[GUIDE] |ROOT + Tethering + MORE| Moto X ver. 4.4.4 for XT1060 and XT1058 (VZW/AT&T)

[GUIDE] |ROOT + Tethering + MORE| Moto X ver. 4.4.4 for XT1060 and XT1058 (VZW/AT&T)
Moto X Root for AT&T/VZW [KXA21.12-L1.26]
This is a rewrite of instructions found HERE by CrashXXL. This will get you PERMANENT[meaning it will not disappear after reboot, but will die if you reflash or upgrade, etc] root on your 4.4.4 AT&T/VZW [KXA21.12-L1.26] Moto X. This will NOT disable system write protection or unlock your bootloader, etc.
The following steps were used by me on Ubuntu 15.04 to root my XT1060 from Verizon:
0. Reinstall your stock rom from HERE you will want the firmware that matches your current 4.4.4 KXA21.12-L1.26 firmware. If you are unsure how to do this HERE is a guide. [NOTE: If you skip this step and you are on 4.4.4 from an OTA then you will be stuck on the M Logo and will have to do this step and all the other steps over]
1. Make sure you have the necessary applications:
Code:
sudo apt-get install android-tools-fastboot python python-serial unrar
2. Download your _Root_<Your phone carrier>_KXA21.12-L1.26_Stock.rar from HERE
3.
-- a) Extract the files
-- b) From the terminal cd into the directory of the extracted files.
-- c) Put your phone into fastboot mode [reboot holding the power and volume down button]
4. Type [NOTE/WARNING: This will softbrick your phone. Which is completely fine if the steps are all followed]:
Code:
sudo fastboot flash sbl2 sbl2.mbn
sudo fastboot reboot
Your phone will have a black screen, but will be in QCOM Emergency mode. You can type in lsusb to confirm this.
5. Type:
Code:
python qdloadRoot.py MPRG8960.bin -ptf _root/partitions.txt
This will take a good 5-15mins. Make sure you are plugged into power and this step is not interrupted. Once this is done your phone will reboot and start up and you will see that SuperSu is installed.
Congrats you have root
NOTE: Read on to the next posts for more info and resources.

Xposed Install
The original post can be found HERE by Sabissimo.
Assuming the above steps were followed and you now have root. Do the following:
1. Download THIS for AT&T XT1058 or THIS for VZW XT1060
2. Extract the file as in step 3 above
3. Run the same commands from step 4 above.
5. Type:
Code:
python qdloadXposed.py MPRG8960.bin -ptf _root/partitions.txt
Be patient for a few minutes. Your phone will reboot.
6. Install 2.6.1 or 2.7.1 of Xposed from their SITE and install as normal.
Congrats you now have root and Xposed that will survive reboots

Thanks to @Nicene Nerd he put together a nice set of scripts to make custom packages to add/remove packages from system images. Check it out here!
Make a tutorial how to pack new applications onto the system AdAway etc.
-- Tutorial to bake in new apps. Thanks Sabissimo. I might rewrite this in the future to make it easier. If anyone follows that guide and would like to write please let me know and we can share files here.

Flash the same way you do the above.
This is for the xt1060.
Here are a list of addition flashables after you have root/xposed
Download:
This will change your /system/etc/hosts file to point to /data/data/hosts. Change this setting in AdAway and be ad free
Adaway_hosts_Root_4.4.4_VZW_KXA21.12-L1.26.zip
This has the buildprop edited for entitlement bypass (tether check) and has all stagefright options set to false. This also has the CF.lumen driver installed (look on playstore great app):
CF.lumenPLUS_Root_4.4.4_VZW_KXA21.12-L1.26.zip

jahrule said:
3. Go further and make our own system images.
Click to expand...
Click to collapse
If you are interested in MoFo, I first need someone to help me make the "pre-rooted" image. It must be in ext4 format. I have an XT1060 Dev Ed that is rooted. According to maiko1,
maiko1 said:
Simplest way is to make the system block device readable by everyone (chmod 644), and then adb pull the block device to your computer.
For example on the turbo via adb shell as root:
Code:
# ls -l /dev/block/bootdevice/by-name
lrwxrwxrwx root root 1970-01-09 20:49 system -> /dev/block/mmcblk0p39
# chmod 644 /dev/block/mmcblk0p39
Then pull it with adb:
Code:
$ adb pull /dev/block/mmcblk0p39 system.img
Click to expand...
Click to collapse
I tried that but I get the error
remote object '/dev/block/mmcblk0p39' not a file or directory
Now, I am not your most experienced adb user so I may have been doing something wrong. What I did was start an adb shell while my XT1060 was running in Android. Then I typed:
su # ls -l /dev/block/bootdevice/by-name
lrwxrwxrwx root root 1970-01-09 20:49 system -> /dev/block/mmcblk0p39
then
# chmod 644 /dev/block/mmcblk0p39
But when I went to pull it I got that error above. I just noticed that SuperSu had silently denied root to the adb shell. Not sure how to stop that.
Also, if I can get this to work, then I could put AdAway, Busy Box, etc. on my XT1060 and pull the image and it should be flashable with mofo.

Finally
I will follow this guide and then post results! I wanna root in my XT058 from long time ago!

Alexdream said:
I will follow this guide and then post results! I wanna root in my XT058 from long time ago!
Click to expand...
Click to collapse
If you need help. Just ask, but it is quite simple.
Don't forget to hit thanks!

JulesJam said:
If you are interested in MoFo, I first need someone to help me make the "pre-rooted" image. It must be in ext4 format. I have an XT1060 Dev Ed that is rooted. According to maiko1,
I tried that but I get the error
remote object '/dev/block/mmcblk0p39' not a file or directory
Now, I am not your most experienced adb user so I may have been doing something wrong. What I did was start an adb shell while my XT1060 was running in Android. Then I typed:
su # ls -l /dev/block/bootdevice/by-name
lrwxrwxrwx root root 1970-01-09 20:49 system -> /dev/block/mmcblk0p39
then
# chmod 644 /dev/block/mmcblk0p39
But when I went to pull it I got that error above. I just noticed that SuperSu had silently denied root to the adb shell. Not sure how to stop that.
Also, if I can get this to work, then I could put AdAway, Busy Box, etc. on my XT1060 and pull the image and it should be flashable with mofo.
Click to expand...
Click to collapse
Looks like you are trying to dd from a partition that does not exist. We can take this offline as it is off topic from this thread.

jahrule said:
Looks like you are trying to dd from a partition that does not exist. We can take this offline as it is off topic from this thread.
Click to expand...
Click to collapse
/dev/block/mmcblk0p39 exists - I can see it in ES File Explorer.
Bottom line is this - I have an XT1060 Dev Ed unlocked and rooted and was trying to help those of you who have unlockable XT1060's to be able to use MoFo. I don't need it for my XT1060 and it looks like you all have another option, although I am not sure how good of an option it is.
If someone wants to enlist my help, I would be willing to help but the ball in your court.

Does anyone has succesfully rooted Moto X1060 (VZW) using this tutorial?

JoseLoarca97 said:
Does anyone has succesfully rooted Moto X1060 (VZW) using this tutorial?
Click to expand...
Click to collapse
Other than me? You can check the original thread. Many other people have done it there.

I can root successful my XT1058 following this guide. Thank you so much! Finally I have xposed and GravityBox.

Post 3 updated with guide to bake in new system applications!

Where should I get the files in step 1 of the root process?

abuttino said:
Where should I get the files in step 1 of the root process?
Click to expand...
Click to collapse
The links are all in post 1. The first step are the packages you need. In my case I was running Ubuntu. If you are running Windows. The you can check the linked original thread and try to do it like that.

I tried it the Windows way and everything went very smoothly. Thanks.
I just don't have the experience to run Ubuntu yet. Been running Windows since v3
Sent from my XT1060 using Tapatalk

Thx! @jahrule
Any chance we can modify it so it will work for the XT1052?

dagoban said:
Thx! @jahrule
Any chance we can modify it so it will work for the XT1052?
Click to expand...
Click to collapse
I think the xt1052 is Europe version and can have the bootloader unlocked. It is then trivia to root.

jahrule said:
I think the xt1052 is Europe version and can have the bootloader unlocked. It is then trivia to root.
Click to expand...
Click to collapse
Yep, 1052 is the Europe one. I have 2 lying around here, for one the BL is unlockable, but the other one has an error and the moto page says that device is not unlockable even thou its a xt1052.
So I would really appreciate something for the xt1052
Thx again!
And let me know if you need any files from the xt1052 partitions / sbfs

dagoban said:
Yep, 1052 is the Europe one. I have 2 lying around here, for one the BL is unlockable, but the other one has an error and the moto page says that device is not unlockable even thou its a xt1052.
So I would really appreciate something for the xt1052
Thx again!
And let me know if you need any files from the xt1052 partitions / sbfs
Click to expand...
Click to collapse
If it shows error try the US support site instead of the one in your country.. Worked for me

Root OP3T without unlocking bootloader - Automated App

ROOT w/o UNLOCKING BOOTLOADER:
Few of Qualcomm Devices have been found to have engineering mode software preinstalled on the device, which has root access. Using the same exploit root can be achieved in OP3, OP3T, OP5 and others, without unlocking the bootloader. Here is a full story: OnePlus Accidentally Pre-Installed an App that acts as a Backdoor to Root Access
The exploit was found by the user Elliot Alderson. An application has been promised by the author soon, to gain root access.
I have tested the method in OnePlus 3T and it works perfectly and passes SafetyNet check, furthermore you do not get DM-Verity error either.
Please follow the guide from here: OnePlus 3T Root w/o unlocking bootloader
Note: Do not modify system files though it won't let you, doing so will trigger Dm Verity.
Magisk Modules do not work, i,e you won't be able to use any modules.
Root and hide root works.
You will get system update but updating might kick you out of the root and you won't be able to gain access to root again.
It works on latest Oreo Beta, as you see in the screenshot.
Disclaimer: Follow the guide at your own risk, it is working fine for me, that in no way means it will work the same for you. Neither me nor the people envolved in this takes any responsibility. You and only you are responsible if anything goes wrong.
Note: I am not the developer or the person who found this exploit or root method. All credits go to them.
SCREENSHOTS ATTACHED
Update 1:
An app has been realsed by Oğuzhan Yiğit here is the link, the full credit goes to him for the same. Here is the link to the post:
Oneplus 3T Root Via App, further it installs SuperSU

This step is required every time you reboot:
adb shell
cd /data/magisk/
./magisk --mountimg xbin.img /system/xbin
magisk --post-fs
magisk --post-fs-data
magisk --service

I haven't tried doing the same, but theoretically, it shouldn't work.

[deleted]

casual_kikoo said:
...OnePlus 2...
Click to expand...
Click to collapse
That phone does not have dm-verity. That's why it works.
DOING THIS ON A ONEPLUS 3 OR NEWER WILL NOT WORK AND YOU WILL BRICK UNTIL YOU QUALCOMM UN-BRICK THE PHONE
Edit: I suggest deleting that and posting it in the OnePlus 2 section since someone will likely try it and brick.

SpasilliumNexus said:
That phone does not have dm-verity. That's why it works.
DOING THIS ON A ONEPLUS 3 OR NEWER WILL NOT WORK AND YOU WILL BRICK UNTIL YOU QUALCOMM UN-BRICK THE PHONE
Edit: I suggest deleting that and posting it in the OnePlus 2 section since someone will likely try it and brick.
Click to expand...
Click to collapse
Ok, as I thougth something else enter into account.
Thanks a lot !

As a newbie can u plz provide me the steps how to gain root access.?
Thanks in advance.

anuajayan said:
As a newbie can u plz provide me the steps how to gain root access.?
Thanks in advance.
Click to expand...
Click to collapse
Please do the necessary steps, I will assist you wherever you get stuck, you can also reach me at telegram on @apurvak

coolstoneapurva said:
Please do the necessary steps, I will assist you wherever you get stuck, you can also reach me at telegram on @apurvak
Click to expand...
Click to collapse
I don't know from where or how to start with? Please guide me accordingly..

replace hosts file
OK, so I decided to take advantage and replace my hosts file. I gain adb root, but then
Code:
@~/Downloads/oneplus[20:56:04]~: adb push hosts /system/etc/hosts
adb: error: failed to copy 'hosts' to '/system/etc/hosts': remote couldn't create file: Read-only file system
hosts: 0 files pushed. 73.3 MB/s (327680 bytes in 0.004s)
trying without success
Code:
@~/Downloads/oneplus[21:00:48]~: adb remount
remount failed
and from within
Code:
@~/Downloads/oneplus[21:00:51]~: adb shell
OnePlus3T:/ # id
uid=0(root) gid=0(root) groups=0(root),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats),3009(readproc) context=u:r:su:s0
OnePlus3T:/ # mount -o rw,remount /system
'/dev/block/dm-0' is read-only
What am I doing wrong or need to do to replace my hosts file, please?

mitkko said:
OK, so I decided to take advantage and replace my hosts file. I gain adb root, but then
trying without success
and from within
What am I doing wrong or need to do to replace my hosts file, please?
Click to expand...
Click to collapse
It's a good thing something is stopping you, because you shouldn't be modifying any file on the partitions. Again, dm-verity is enabled. You modifying any file directly will result in getting a corrupt error after a reboot. Use Magisk for systemless modifications.

Please write in first post if OTA will still work on next update. And if possible specify if this woks also on oxygen os open beta with Android Oreo.
That said, anyone know if possible to unlock bootloader state, without trigger the factory reset??

SpasilliumNexus said:
It's a good thing something is stopping you, because you shouldn't be modifying any file on the partitions. Again, dm-verity is enabled. You modifying any file directly will result in getting a corrupt error after a reboot. Use Magisk for systemless modifications.
Click to expand...
Click to collapse
How do I do that? Assume I have already introduced magisk to my phone.

mitkko said:
How do I do that? Assume I have already introduce magisk to my phone.
Click to expand...
Click to collapse
Isn't there a systemless host option for adblock in Magisk's settings? If so, turn it on, install AdAway, turn on systemless hosts in that, apply the adblock.

SpasilliumNexus said:
Isn't there a systemless host option for adblock in Magisk's settings? If so, turn it on, install AdAway, turn on systemless hosts in that, apply the adblock.
Click to expand...
Click to collapse
Never used it before. Is that persistent? I mean after reboot and magisk root gone will it persist? I don't need persistent root, I just want to patch hosts one time only if possible.

mitkko said:
Never used it before. Is that persistent? I mean after reboot and magisk root gone will it persist? I don't need persistent root, I just want to patch hosts one time only if possible.
Click to expand...
Click to collapse
It's not persistent. The last steps for root access in that guide needs to be done after every reboot, which is also needed for AdAway to apply the block. Applying the adblock after root doesn't need a reboot.
You're better off just doing the traditional unlock and root instead.
Hope that makes sense.

Deodexed and Patched EngineeringMode.apk for restore default Privilege
I played a little with Angela`s Root and wanted to restore the previous level of privilege. In the application there is a special button rollback changes, but it is Invisible
Code:
this.mPrivilege = this.findViewById(2131493042);
this.mPrivilege.setOnClickListener(((View$OnClickListener)this));
this.mPrivilege.setVisibility(4); //this.mPrivilege.setVisibility(View.INVISIBLE);
So I did the application deodex and patched the application, changing it to
Code:
this.mPrivilege.setVisibility(0); //this.mPrivilege.setVisibility(View.VISIBLE);
After that I changed the original application to patched
Code:
adb remount
adb push EngineeringMode_SIGNED_ALIGNED.apk /system/app/EngineeringMode/EngineeringMode.apk
And start them
Code:
adb shell am start -n com.android.engineeringmode/.qualcomm.DiagEnabled --es "code" "angela"
Result Screenshort:
After click on the button, the phone restarts and all privileges are restored

mitkko said:
OK, so I decided to take advantage and replace my hosts file. I gain adb root, but then
Code:
@~/Downloads/oneplus[20:56:04]~: adb push hosts /system/etc/hosts
adb: error: failed to copy 'hosts' to '/system/etc/hosts': remote couldn't create file: Read-only file system
hosts: 0 files pushed. 73.3 MB/s (327680 bytes in 0.004s)
trying without success
Code:
@~/Downloads/oneplus[21:00:48]~: adb remount
remount failed
and from within
Code:
@~/Downloads/oneplus[21:00:51]~: adb shell
OnePlus3T:/ # id
uid=0(root) gid=0(root) groups=0(root),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats),3009(readproc) context=u:r:su:s0
OnePlus3T:/ # mount -o rw,remount /system
'/dev/block/dm-0' is read-only
What am I doing wrong or need to do to replace my hosts file, please?
Click to expand...
Click to collapse
You shouldn't make any changes to system partion doing to will render you unable to boot, as dm verity is enabled.

andQlimax said:
Please write in first post if OTA will still work on next update. And if possible specify if this woks also on oxygen os open beta with Android Oreo.
That said, anyone know if possible to unlock bootloader state, without trigger the factory reset??
Click to expand...
Click to collapse
Yes it will work on next update as system files are intact, further it works on Beta Oreo as you can see the screenshot. I will further update the post with the same.

seems not working on Android 8 /OOS 5