Database Info

[Q] flash insecure boot image from CWM?

Is there a way to flash an insecure boot image from CWM recovery?
I rooted my transformer with nachoroot, and installed CWM with the one-click recovery installer. None of these methods unlocked the boot loader, obviously, so I can't use adb remount and friends.
I have a B70 tf101, with the .21 firmware if that helps.

I think you need to flash an insecure boot.img.
There are a few few threads kicking around in the dev section that explain this. rebound821 posted an excellent thread. I think this is exactly what moshi and brk's root tools do via nvflash.
In a nutshell:
1) extract your boot.img from your TF
2) unpack the boot.img to the kernel and ramdisk
3) unpack the ramdisk
4) edit default.prop to set ro.secure=0
5) re-assemble in reverse order
6) zip and flash

gee one said:
I think you need to flash an insecure boot.img.
There are a few few threads kicking around in the dev section that explain this. rebound821 posted an excellent thread. I think this is exactly what moshi and brk's root tools do via nvflash.
In a nutshell:
1) extract your boot.img from your TF
2) unpack the boot.img to the kernel and ramdisk
3) unpack the ramdisk
4) edit default.prop to set ro.secure=0
5) re-assemble in reverse order
6) zip and flash
Click to expand...
Click to collapse
thanks for the reply, but I was asking if after I've done that I could flash the boot img with CWM? I've heard that nvflash doesn't work on B70 transformers.
Sent from my HTC Vision using Tapatalk

Yup, in step 6, you would zip it up and flash it via cwm.

pm sent!!!

perquisitor_omnia said:
Is there a way to flash an insecure boot image from CWM recovery?
I rooted my transformer with nachoroot, and installed CWM with the one-click recovery installer. None of these methods unlocked the boot loader, obviously, so I can't use adb remount and friends.
I have a B70 tf101, with the .21 firmware if that helps.
Click to expand...
Click to collapse
If you have root you can do adb remount.
Start a shell in adb and use su to get root. Now you can remount.
I assume this is about remount /system

gls9 said:
If you have root you can do adb remount.
Start a shell in adb and use su to get root. Now you can remount.
I assume this is about remount /system
Click to expand...
Click to collapse
Yeah, but even if I remount /system using adb shell I can still can't do "adb push" to /system so I assume I need to set ro.secure=0 in the bootloader for this to work.

perquisitor_omnia said:
Yeah, but even if I remount /system using adb shell I can still can't do "adb push" to /system so I assume I need to set ro.secure=0 in the bootloader for this to work.
Click to expand...
Click to collapse
I dont know because I don't use adb much.
But why not do this from terminal emulator and just copy the file from sdcard ?
(or with adb shell)
Something like this:
su
mount -o remount,rw /system
cat [source] > [destination]

gls9 said:
I dont know because I don't use adb much.
But why not do this from terminal emulator and just copy the file from sdcard ?
(or with adb shell)
Something like this:
su
mount -o remount,rw /system
cat [source] > [destination]
Click to expand...
Click to collapse
Thats what I am doing at the moment, but it is annoying to have to stage all files to /data/local or /sdcard before copying files to /system from the tablet, when it is much easier to do
$ adb push <file> /system/
from the host computer. Anyway, if I make a insecure bootloader for my tablet that can be flashed from the recovery, I'll post it here as it might be useful to other people in my position.

I've got an insecure boot.img from the US 8.6.5.21 firmware if anyone is interested. It's just the boot in a zip file.

Maybe I'm misunderstanding, but I thought that any image you flashed with CWM recovery was using an insecure boot.img, unless flashing back stock recovery. Anyway, for adb push or adb pull for that matter to work you have to install Asus sync software and USB drivers under Windows and if in Linux, you can search xda for the thread that explains how to get adb working. Once you've got that and root you can adb push and adb pull all day long til you run out of space.

sidneyk said:
Maybe I'm misunderstanding, but I thought that any image you flashed with CWM recovery was using an insecure boot.img, unless flashing back stock recovery. Anyway, for adb push or adb pull for that matter to work you have to install Asus sync software and USB drivers under Windows and if in Linux, you can search xda for the thread that explains how to get adb working. Once you've got that and root you can adb push and adb pull all day long til you run out of space.
Click to expand...
Click to collapse
I have adb working properly (I use it with my G2 all the time), and I use linux.
But for some reason, with my Asus Transformer, when I do
Code:
$ adb remount
I get a 'permission denied' error.
Even if I remount /system rw from the shell, I still get 'permission denied' when trying to use 'adb push' to any directory besides /data/local or /sdcard on the tablet. Is this a bug with the recovery I flashed? or is this because the bootloader hasn't had ro.secure=0 set?
Sent from my Transformer TF101 using Tapatalk

Are you trying this in recovery or under the normal system? Try it under both.
sent from my transformer

I'm trying under the normal system, I will try under recovery when I get access to my desktop.
Sent from my Transformer TF101 using Tapatalk

OK, how about some testing:
from your PC:
adb version
adb shell grep secure /default.prop (or adb shell getprop ro.secure)
This will check your adb version and also see if your ro.secure flag is set.
I tested 'adb remount' and it worked as intended. I'm on adb version 1.0.29 with ro.secure=0.
Also, the recovery ramdisk has it's own default.prop and ro.secure flag, so these can actually be set independantly, but I think you would notice it immediately if recovery wasn't insecure.

Code:
$ adb version
Android Debug Bridge version 1.0.29
$ adb -s shell getprop ro.secure
1
so that would be the problem. can I set the ro.secure property in build.prop?

perquisitor_omnia said:
I have adb working properly (I use it with my G2 all the time), and I use linux.
But for some reason, with my Asus Transformer, when I do
Code:
$ adb remount
I get a 'permission denied' error.
Even if I remount /system rw from the shell, I still get 'permission denied' when trying to use 'adb push' to any directory besides /data/local or /sdcard on the tablet. Is this a bug with the recovery I flashed? or is this because the bootloader hasn't had ro.secure=0 set?
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
I am familiar with errors kind of like this from Mac OS, dunno if it applies here but you might try repairing permissions from CWM. I have fund that quite a lot of ROMs do not have correct permissions set.
Cheers!
-M
Xda member since 2007

perquisitor_omnia said:
Code:
$ adb version
Android Debug Bridge version 1.0.29
$ adb -s shell getprop ro.secure
1
so that would be the problem. can I set the ro.secure property in build.prop?
Click to expand...
Click to collapse
Yeah, that would cause the issues. Not sure how to fix it, but some ideas:
1) flash an insecure boot.img via cwm
2) use the staging partition to flash a boot.img/blob
3) ???

I finally used the SBK detect tool, my B70 has a nvflashable firmware, so I will pull the boot loader with nvflash and make it insecure that way.
Sent from my HTC Vision using Tapatalk

1.55.531.3 rom?

Hello all.
I looked and can't find but is there a rooted 1.55.531.3 rom for the device anywhere.
Rooted the phone tried the ICS from sensation and kinda want to go back but not unroot.

I could send you my recovery if you have the ability to flash
rooted 1.55.531.3 with clockwork recovery and SU

M9x3mos said:
Hello all.
I looked and can't find but is there a rooted 1.55.531.3 rom for the device anywhere.
Rooted the phone tried the ICS from sensation and kinda want to go back but not unroot.
Click to expand...
Click to collapse
yeah, what you are looking for doesn't exist at the moment. i too thought about making a nandroid of the the new ROM for people to flash, but since the new setup comes with a new radio, new kernel, new HBOOT, etc., i'm not sure how it would fly if someone just flashed the nandroid?

Hboot n radio would be the only thing missing... Kernels sits in recovery....
rooted 1.55.531.3 with clockwork recovery and SU

I know I made a flashable package out of the Google Talk apk file, and either did or meant to make some out of the other apps in it - I'm not sure which thread it's in.
I can check later and link it. Not sure what else anyone did with it, if wifi calling wasn't pulled forward from it I'll have a package for that sometime soon anyway.
I also never did get a chance to check what the gps changes were I remember being in it.
Edit:
Link to Gtalk flashable zip package from that update.
Sent from my Bulletproof_Doubleshot using xda premium

nlarge said:
I could send you my recovery if you have the ability to flash
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
Do you have the stock rom for 1.55.531.3 that I can flash on my mt4gs? I would really appreciate it

http://forum.xda-developers.com/showthread.php?t=1484679
http://forum.xda-developers.com/showthread.php?t=1433805

It would be flashed as if restoring a nandroid. I would flash the above link. If you really want it I can send it
rooted 1.55.531.3 with clockwork recovery and SU

Thanks. Okay, this is where I am:
Unlocked bootloader with htcdev
s-on
hboot 1.45.0013
software 1.55.531.3
Would like to achieve root so that I can flash custom roms/use titanium backup. From what I can tell, nlarge was able to accomplish this. (http://forum.xda-developers.com/showthread.php?t=1474933&page=6). However, couldn't post on that thread because I have less than 10 posts....sorry.
Cannot use temproot (FR3VO) method because says needs s-off and/or adb mount issue:
An error occurred while running the exploit (-1) (errno: 22)
c:\Android>adb wait-for-device
c:\Android>adb remount
remount failed: Operation not permitted
c:\Android>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
c:\Android>adb shell mount -oremount,suid /dev/block/mmcblk0p23 /data
mount: Operation not permitted
c:\Android>adb shell mkdir /vendor/bin
mkdir failed for /vendor/bin, Read-only file system
c:\Android>adb shell chown root.shell /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb shell chmod 755 /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb push ./sqlite3 /vendor/bin
cannot stat './sqlite3': No such file or directory
c:\Android>adb push ./su /vendor/bin
cannot stat './su': No such file or directory
c:\Android>adb push ./busybox /vendor/bin
cannot stat './busybox': No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/su
Unable to chmod /vendor/bin/su: No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/busybox
Unable to chmod /vendor/bin/busybox: No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/sqlite3
Unable to chmod /vendor/bin/sqlite3: No such file or directory
c:\Android>adb shell chmod 6555 /vendor/bin/su
Unable to chmod /vendor/bin/su: No such file or directory
c:\Android>adb shell chmod 4555 /vendor/bin/busybox
Unable to chmod /vendor/bin/busybox: No such file or directory
c:\Android>adb shell chmod 755 /vendor/bin/sqlite3
Unable to chmod /vendor/bin/sqlite3: No such file or directory
c:\Android>adb shell busybox --install -s /vendor/bin
busybox: permission denied
c:\Android>adb shell sync
c:\Android>adb shell chmod 6555 /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb install ./Superuser.apk
can't find './Superuser.apk' to install
c:\Android>pause
Press any key to continue . . .​
So, I understand, permission denied/operation not permitted, I assume because I don't have root.
When I look at superuser, it says "su binary voutdated" and when I tap to check for updates, automatic update fails and error message "su was not updated. A zip file (su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary.
Can't boot into recovery mode, phone just sits on mytouch 4g slide screen. Again, I assume because no root. Same thing happens if I try to factory reset, just stays on the mytouch 4g slide screen.
Anyone have any suggestions? I am going crazy trying to get this phone to work. I would really appreciate the help!

Flash clock work recovery... I think I linked it somewhere... Or Google will help
rooted 1.55.531.3 with clockwork recovery and SU

Now find yourself a nice recovery image (CWM), boot phone into fastboot mode, "fastboot flash recovery recovery.img".
When this is done you will have a free and open recovery image, and can use that to write/install the su binary and apk (either with flashable zip or through adb shell, either will work).
rooted 1.55.531.3 with clockwork recovery and SU

nlarge said:
Now find yourself a nice recovery image (CWM), boot phone into fastboot mode, "fastboot flash recovery recovery.img".
When this is done you will have a free and open recovery image, and can use that to write/install the su binary and apk (either with flashable zip or through adb shell, either will work).
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
Have tried flashing new and old versions of cwr and the earlier links from blue with no luck. Trying to do it manually through the computer with fastboot, results in 'waiting for device' message. All drivers installed, usb debug, have tried charge only/mount as disk drive options. Neither work. Have tried flashing manually by converting .img to .zip without compression and flashing through phone. No error message but nothing changes.
Cannot use cwm to flash because not error message says not rooted. Not sure what else to do. BTW, you guys are awesome for helping me out Thanks!

Put your phone in fastboot. Pull battery, hold down and power then try again
rooted 1.55.531.3 with clockwork recovery and SU

How to fastboot flash recovery
Return to Contents Page - doubleshot Developers Reference
Boltinghouse said:
Have tried flashing new and old versions of cwr and the earlier links from blue with no luck. Trying to do it manually through the computer with fastboot, results in 'waiting for device' message. All drivers installed, usb debug, have tried charge only/mount as disk drive options. Neither work. Have tried flashing manually by converting .img to .zip without compression and flashing through phone. No error message but nothing changes.
Cannot use cwm to flash because not error message says not rooted. Not sure what else to do. BTW, you guys are awesome for helping me out Thanks!
Click to expand...
Click to collapse
(hah, thanked but meant to hit quote)
What you need to do is go here: http://clockworkmod.com/rommanager
Scroll down the list and find the recovery for our device (5.0.2.7 for the myTouch 4G Slide) - download this.
Put it in the same folder as 'fastboot.exe' on your computer. Rename it to recovery.img
On your phone, turn off 'fastboot' in power options.
Power off the phone.
Now, give it a minute to power off - then hold the volume down button and press power.
Now it will boot up to the hboot menu. The list presented will have you highlighted on the word 'fastboot' - press power to choose this.
Now you are presented with the fastboot menu. It should say fastboot with a red highlight around it near the top.
At this time you should plug the USB cord from your computer into the phone. It will update to say fastboot USB in red highlight now.
-okay-
We have the phone booted up in fastboot, attached to the computer, and ready to work with.
Open up your command prompt, and navigate to the folder where you have the fastboot command. This is the same folder that you have the new clockworkmod recovery.img in from before.
In your terminal now type:
Code:
fastboot devices
This will come back with your device, serial number, and show you it is connected and ready to go. (if it is not something is wrong)
Now type:
Code:
fastboot flash recovery recovery.img
Let's break this down:
fastboot = activates the fastboot.exe command, and says that what's typed next uses the definitions in that fastboot.exe file.
flash = command that says write to
recovery = destination (name of partition) being written to
recovery.img = file written to previously defined location.
----
Since you have the new clockworkmod recovery file in the same folder as fastboot.exe, and you renamed it to recovery.img, then the previously shown command will overwrite your stock recovery with the new image you are providing it.
At this point you should have clockworkmod recovery in place of your stock recovery when you boot the device to hboot menu and select recovery.
Let us know if you have any other problems.

Good explanation blue.... It sounded like he knew what he was doing, hence my quick correction...
Hate typing a lot out from phone!
rooted 1.55.531.3 with clockwork recovery and SU

OMG! Thats awesome. FINALLY ROOTED!!!!! yay! So happy. Thank you guys so much. nlarge and blue, you two are the best!
Thanks again
~Brandi~

Oops... Sorry I called you a he...LOL... Most of us nerds are guys
We help where we can
Boltinghouse said:
OMG! Thats awesome. FINALLY ROOTED!!!!! yay! So happy. Thank you guys so much. nlarge and blue, you two are the best!
Thanks again
~Brandi~
Click to expand...
Click to collapse
rooted 1.55.531.3 with clockwork recovery and SU

nlarge said:
Oops... Sorry I called you a he...LOL... Most of us nerds are guys
We help where we can
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
It's all good, I know being a chick I'm in the minority here. Either way, thank you so much.

So it looks like both nlarge and boltinghouse rooted s-on phones. Is there any reason not to go ahead and root that way? Is there any reason you need/want s-off?

it depends on what you want to do with your phone...
If you just want to be able to make recovery and flash ROMS than you dont need s-off
If you want to play with other stuff(radios and mounts) then you need s-off.
I personally like doing things to my phone so I would like to get to s-off. I am ok with it for now, but S-off will give me the full control I want.
qwerty3656 said:
So it looks like both nlarge and boltinghouse rooted s-on phones. Is there any reason not to go ahead and root that way? Is there any reason you need/want s-off?
Click to expand...
Click to collapse

HTC One X Root Assistance

Hey guys. I just got my HOX and have been trying to root it. The software update keeps popping up and I keep refusing, so no worries there. I've got 1.85 right now and have been attempting the methods found here and here, but they just aren't working. I'd prefer to use the manual method. Someone willing to help a guy get started with all this would be the greatest person ever, just saying!

blinkbomber said:
Hey guys. I just got my HOX and have been trying to root it. The software update keeps popping up and I keep refusing, so no worries there. I've got 1.85 right now and have been attempting the methods found here and here, but they just aren't working. I'd prefer to use the manual method. Someone willing to help a guy get started with all this would be the greatest person ever, just saying!
Click to expand...
Click to collapse
check pm

beaups said:
check pm
Click to expand...
Click to collapse
Could you help me too X( ? I got my HOX last night at 8pm; I traded my rooted S2 Skyrocket for it.
Been looking for the past day through forums and google. It's so different from Samsung's phones, but a nice change indeed.
I'm on 1.85 and tried those two methods also. I'm not very familiar with ADB. From reading all night and this morning, I believe I root, unlock bootloader, flash recovery, flash custom roms?

smartnphone said:
Could you help me too X( ? I got my HOX last night at 8pm; I traded my rooted S2 Skyrocket for it.
Been looking for the past day through forums and google. It's so different from Samsung's phones, but a nice change indeed.
I'm on 1.85 and tried those two methods also. I'm not very familiar with ADB. From reading all night and this morning, I believe I root, unlock bootloader, flash recovery, flash custom roms?
Click to expand...
Click to collapse
Follow the instructions in this link http://forum.xda-developers.com/showthread.php?p=30741993
Sent from my HTC One X using xda premium

abhipati said:
Follow the instructions in this link http://forum.xda-developers.com/showthread.php?p=30741993
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks. I used this for ADB http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
I remember using it for my S2, but I don't quite understand the directions for the http://forum.xda-developers.com/showthread.php?t=1709296 method. Could you dumb it down for this HOX noob?

smartnphone said:
Thanks. I used this for ADB http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
I remember using it for my S2, but I don't quite understand the directions for the http://forum.xda-developers.com/showthread.php?t=1709296 method. Could you dumb it down for this HOX noob?
Click to expand...
Click to collapse
I'll try to help! all of the following is my interpretation of the rooting method described here: http://forum.xda-developers.com/showthread.php?t=1709296
What you need:
HOX on ATT 1.85
su binary from http://dl.dropbox.com/u/don'tusemeimabadsubinary
EDIT: The su binary above has issues. Use this one instead: http://dl.dropbox.com/u/9060692/su
Make sure HTC sync is NOT RUNNING (down in system tray)
Make sure phone is set to "charge only" and usb debugging is enabled!
Download correct su file (assuming you don't have a problem with this step )
Put su in same directory as ADB. Get to adb command prompt and cd into that directory
Quote from Butters619: cd means change directory. It is a windows command prompt command. So you would type "cd C:\adb" if that was where your adb folder was. Folder and directory can be used interchangeably, although directory is more "correct". We only say folder because GUIs use folders to represent directories.
NEW - pull sim card
NEW - do factory reset
NEW - when reset is complete, do not replace sim, do NOT connect to wifi. Go through setup, go to settings, enable USB debugging. When that's done:
Enter these commands in adb:
adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
(If you get file doesn't exist after the FIRST command don't worry - they may not be there)
Now, on the phone, go to settings and check for software update. It will tell you you need to connect to network. Now, replace the SIM OR connect to wifi. Have it check for software update again. When it's done, do NOT click "yes" or "ok" on the phone. Simply:
Enter these commands in adb:
adb shell ls -l /data/local.prop
IF AND ONLY IF you get "file not exists" or anything like that then set your phone's date 2 days ahead and reboot the phone and start over. If you get file info, you're golden. Proceed...
Enter these commands into adb:
adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"
Reboot via adb by entering this command: adb reboot
After phones reboots
Enter these commands in adb:
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
You should be rooted.

A cool username said:
I'll try to help! all of the following is my interpretation of the rooting method described here: http://forum.xda-developers.com/showthread.php?t=1709296
What you need:
HOX on ATT 1.85
su binary from http://dl.dropbox.com/u/don'tusemeimabadsubinary
EDIT: The su binary above has issues. Use this one instead: http://dl.dropbox.com/u/9060692/su
Make sure HTC sync is NOT RUNNING (down in system tray)
Make sure phone is set to "charge only" and usb debugging is enabled!
Download correct su file (assuming you don't have a problem with this step )
Put su in same directory as ADB. Get to adb command prompt and cd into that directory
Quote from Butters619: cd means change directory. It is a windows command prompt command. So you would type "cd C:\adb" if that was where your adb folder was. Folder and directory can be used interchangeably, although directory is more "correct". We only say folder because GUIs use folders to represent directories.
NEW - pull sim card
NEW - do factory reset
NEW - when reset is complete, do not replace sim, do NOT connect to wifi. Go through setup, go to settings, enable USB debugging. When that's done:
Enter these commands in adb:
adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
(If you get file doesn't exist after the FIRST command don't worry - they may not be there)
Now, on the phone, go to settings and check for software update. It will tell you you need to connect to network. Now, replace the SIM OR connect to wifi. Have it check for software update again. When it's done, do NOT click "yes" or "ok" on the phone. Simply:
Enter these commands in adb:
adb shell ls -l /data/local.prop
IF AND ONLY IF you get "file not exists" or anything like that then set your phone's date 2 days ahead and reboot the phone and start over. If you get file info, you're golden. Proceed...
Enter these commands into adb:
adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"
Reboot via adb by entering this command: adb reboot
After phones reboots
Enter these commands in adb:
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
You should be rooted.
Click to expand...
Click to collapse
Thanks. Yeah i've been trying it alld ay but it can't find where my SU is. it's in the same location as the ADB stuff i believe C:\android-sdk-windows. Seem like some of the senior members are willing to go through teamviewer to help the ones who can't do it. I'll try asking them :/

Sorry I couldn't be of any help, but please let me know if/how you get this to work just in case this happens to me when I get my one x.
Sent from my Touch Pro 2 using xda app-developers app
---------- Post added at 08:22 PM ---------- Previous post was at 08:18 PM ----------
blinkbomber said:
Hey guys. I just got my HOX and have been trying to root it. The software update keeps popping up and I keep refusing, so no worries there. I've got 1.85 right now and have been attempting the methods found here and here, but they just aren't working. I'd prefer to use the manual method. Someone willing to help a guy get started with all this would be the greatest person ever, just saying!
Click to expand...
Click to collapse
I wonder if the one who actually started this thread got his/her phone to work...???
Sent from my Touch Pro 2 using xda app-developers app

Someone think they can help me root the phone? I'm on 1.85 and I believe I finally got adb to recognize my device but after that I don't think I'm doing it right
Sent from my SGH-I777 using XDA Premium App

I have bricked my phone I think please help.

Hello I have a HOX from att with the 1.85 software number.
I attempted to use this method to root my phone. http://forum.xda-developers.com/showthread.php?t=1709296
I proceeded with the instructions as followed and was sucessfully able to run these commands:
adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb reboot
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
adb shell ls -l /data/local.prop
adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"
Now it's time to reboot
adb reboot
After phones reboots
adb remount
The command prompt indicated a successful remount. (At this point on the phone only the notification bar was working and nothing else was on the screen and right now that is where my phone is stuck, but i proceeded on)
I entered this command adb push su /system/xbin/su
and recieved a error
failed to copy 'su' to '/system/xbin/su': Read-only file system
At this point I did not know what to do I proceeded to reboot and then remount again.
Now I am stuck with just the notification bar responding and the settings not opening.
I am hoping anyone can help me also please PM me. I would appreciate any help with my situation.
If possible could someone g chat with me as typing and waiting for replies is taking to long.
Sorry if I come off as needy but the possiblity of losing the phone I recently bought is scaring me

sunny342 said:
Hello I have a HOX from att with the 1.85 software number.
I attempted to use this method to root my phone. http://forum.xda-developers.com/showthread.php?t=1709296
I proceeded with the instructions as followed and was sucessfully able to run these commands:
adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb reboot
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
adb shell ls -l /data/local.prop
adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"
Now it's time to reboot
adb reboot
After phones reboots
adb remount
The command prompt indicated a successful remount. (At this point on the phone only the notification bar was working and nothing else was on the screen and right now that is where my phone is stuck, but i proceeded on)
I entered this command adb push su /system/xbin/su
and recieved a error
failed to copy 'su' to '/system/xbin/su': Read-only file system
At this point I did not know what to do I proceeded to reboot and then remount again.
Now I am stuck with just the notification bar responding and the settings not opening.
I am hoping anyone can help me also please PM me. I would appreciate any help with my situation.
If possible could someone g chat with me as typing and waiting for replies is taking to long.
Sorry if I come off as needy but the possiblity of losing the phone I recently bought is scaring me
Click to expand...
Click to collapse
I ended up just turning off the phone and then opening hboot and doing a factory reset. It got me back to stock so at least I can use my phone

sunny342 said:
I ended up just turning off the phone and then opening hboot and doing a factory reset. It got me back to stock so at least I can use my phone
Click to expand...
Click to collapse
When you try and mount your phone, since you factory reset through Hboot, you'll need to reformat your SD card because you corrupted it. Just some information for you.

Factory reset in bootloader, plug it in to comp, bring up "my computer" on your computer. Right click removable storage and choose "format"
Sent from my One X using Tapatalk 2

Can this phone be rooted on Nougat?! Conflicting Information!!

I keep getting conflicting information on this device.
Can it be rooted on Nougat? Is a root being developed? Or has the G5 been abandoned?

I too am waiting to hear.
Sent from my LG-H830 using Tapatalk

You can use the dirtycow exploit. This doesn't really root your phone, it allows you to flash twrp and boot you into twrp so you can flash supersu

Dirtycow worked for me on Nougat 7.0, It will run like charm if u do ur steps correctly (Dnt forget to unlock fastboot oem) I was getting an error cuz or that 😂Rookie mistake.

Xperienced Noob said:
I keep getting conflicting information on this device.
Can it be rooted on Nougat? Is a root being developed? Or has the G5 been abandoned?
Click to expand...
Click to collapse
Any luck with this?

http://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-running-30a-nougat-t3524322
Here's a link to a new way to root the G5. I used the dirty cow exploit, that worked for me, it was pretty easy.

An alternate method that worked great for my h830 was to LGUP the twrped 10D tot, then use that TWRP to flash autoprime's 20A Nougat zip. After booting up once into unrooted 20A, i powered off and did factory reset (volume down with power button released for just a second at the LG logo) and entered TWRP to flash the latest SuperSU zip. Upon reboot into 20A, it maintained root and has been withstanding my assaults on system apps for about a week now.
=>>update: still rooted and TWRPd, flashed the NSS kernel, almost a month later and no problems!

Skyline GTR78 said:
http://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-running-30a-nougat-t3524322
Here's a link to a new way to root the G5. I used the dirty cow exploit, that worked for me, it was pretty easy.
Click to expand...
Click to collapse
Did not work for me. Stuck on no command when rebooting to recovery...

RicardoSal24 said:
You can use the dirtycow exploit. This doesn't really root your phone, it allows you to flash twrp and boot you into twrp so you can flash supersu
Click to expand...
Click to collapse
mxmagia said:
Dirtycow worked for me on Nougat 7.0, It will run like charm if u do ur steps correctly (Dnt forget to unlock fastboot oem) I was getting an error cuz or that Rookie mistake.
Click to expand...
Click to collapse
I saw that page, i seem to have lost it and can not find it using search, any link to that page would be helpful.
Thanks

warriorvibhu said:
I saw that page, i seem to have lost it and can not find it using search, any link to that page would be helpful.
Thanks
Click to expand...
Click to collapse
I'll get you the link to download it, Im not at home right now, once I get there I'll send it to you.
EDITED: Credits to @godfather123189
This is what you need, if you need some help PM me
Download all the files from here:
https:// build.nethunter. com/android-tools/dirtycow/arm64/ (Erase the spaces, I cant post links)
and follow these instructions:
**pushing files**
adb push dirtycow /data/local/tmp
adb push recowvery-applypatch /data/local/tmp
adb push recowvery-app_process64 /data/local/tmp
adb push recowvery-run-as /data/local/tmp
adb push twrp.img /sdcard/twrp.img
**end pushing files**
1) adb shell
2) cd /data/local/tmp
3) chmod 0777 *
4) ./dirtycow /system/bin/applypatch recowvery-applypatch
"<wait for completion>"
5) ./dirtycow /system/bin/app_process64 recowvery-app_process64
"<wait for completion, your phone will look like it's crashing>"
6) exit
7) adb logcat -s recowvery
"<wait for it to tell you it was successful>"
8) CTRL+C
9) adb shell reboot recovery
"<wait for phone to boot up again, your recovery will be reflashed to stock>"
10) adb shell
11) getenforce
"<it should say Permissive, adjust source and build for your device!>"
12) cd /data/local/tmp
13) ./dirtycow /system/bin/run-as recowvery-run-as
14) run-as exec ./recowvery-applypatch boot
"<wait for it to flash your boot image this time>"
15) run-as su
16) dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery

Yes, it can be.
Checkout my guide I just made: https://forum.xda-developers.com/lg-g5/how-to/guide-root-stock-n-using-jcadduonos-t3529093

Dumboguy03 said:
Did not work for me. Stuck on no command when rebooting to recovery...
Click to expand...
Click to collapse
Download link for dirty cow......
https://build.nethunter.com/android-...irtycow/arm64/
and follow these instructions:
**pushing files**
adb push dirtycow /data/local/tmp
adb push recowvery-applypatch /data/local/tmp
adb push recowvery-app_process64 /data/local/tmp
adb push recowvery-run-as /data/local/tmp
adb push twrp.img /sdcard/twrp.img
**end pushing files**
1) adb shell
2) cd /data/local/tmp
3) chmod 0777 *
4) ./dirtycow /system/bin/applypatch recowvery-applypatch
"<wait for completion>"
5) ./dirtycow /system/bin/app_process64 recowvery-app_process64
"<wait for completion, your phone will look like it's crashing>"
6) exit
7) adb logcat -s recowvery
"<wait for it to tell you it was successful>"
8) CTRL+C
9) adb shell reboot recovery
"<wait for phone to boot up again, your recovery will be reflashed to stock>"
10) adb shell
11) getenforce
"<it should say Permissive, adjust source and build for your device!>"
12) cd /data/local/tmp
13) ./dirtycow /system/bin/run-as recowvery-run-as
14) run-as exec ./recowvery-applypatch boot
"<wait for it to flash your boot image this time>"
15) run-as su
16) dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery
You can copy and paste everything into cmd window to make it easier.

Does this unlock bootloader?
Sent from my LG-H830 using Tapatalk

<quote>Download link for dirty cow......
https://build.nethunter.com/android-...irtycow/arm64/</quote>
Link 404's @Skyline GTR78

Dumboguy03 said:
<quote>Download link for dirty cow......
https://build.nethunter.com/android-...irtycow/arm64/</quote>
Link 404's @Skyline GTR78
Click to expand...
Click to collapse
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Try this

mxmagia said:
I'll get you the link to download it, Im not at home right now, once I get there I'll send it to you.
EDITED: Credits to @godfather123189
This is what you need, if you need some help PM me
Click to expand...
Click to collapse
Thanks this worked esp coz it gave me the confidence, I used this and another step by step LG V20 instructions to install TWRP and achieve root on LG G5.
Here is the link:
http://android.wonderhowto.com/how-to/root-your-t-mobile-lg-v20-using-dirty-cow-0175329/

​
Skyline GTR78 said:
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Try this
Click to expand...
Click to collapse
Thanks. I had found it, and it worked. Kinda. I have twrp installed, and I'm assuming root, but there's nothing there. Through file explorer and terminal everything is gone. Including external sd I loaded RR on with a working phone. Not good. Idk where to even go from here
Edit; Can read external sd and install packages, but "reboot system" just takes me back into TWRP. The install seems to go well (result was [1.00000]) and system is no longer blank. But can't boot into it. A little closer tho
Edit 2: If you get stuck in a boot loop to TWRP, use these commands (provided by @z28james):
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/fota
All good now!

Looks like I can't delete my reply. I had a problem after rooting and I had either misread the instructions to get into recovery or they were typed wrong where I was looking. I finally found a site that gave the correct procedure: vol down+power then at LG screen release power while still holding vol down then hold power again with vol down. I was able to flash a rom at that point.

could you give me a hand if i pm you?

edit: replied in wrong thread. sorry