Database Develop

Cannot get root after unlocking and installing custom recovery!!!

I have tried every toolkit and manually pushing it and flashing it from recovery and no go. With TWRP it says failed. with CWM it says it installed. But when I reboot and try and run a app that requires root, it says that I do not have root.
Stock Tmo 4.4.2 ROM, S-On, Unlocked
What am I doing wrong?

What file are you flashing with TWRP for root?
sent from my mobile device

I have tried multiple SU.zips as well as Superuser-3.1.3-arm-signed.zip. Is there a different one I should be using?
SaHiLzZ said:
What file are you flashing with TWRP for root?
sent from my mobile device
Click to expand...
Click to collapse

http://forum.xda-developers.com/showthread.php?t=1538053
Flash this in twrp
sent from my mobile device

I downloaded the UPDATE-SuperSU-v1.93.zip and pushed it to the phone and booted into TWRP and chose install and browsed to the sdcard and clicked on the zip file and it says:
Error FLashing zip /sdcard/UPDATE-SuperSU-v1.93
Updating Partition details
E: Unable to mount ./cache'
E: Unable to mount '/data'
E: Unable to mount internal storage
Failed
SaHiLzZ said:
http://forum.xda-developers.com/showthread.php?t=1538053
Flash this in twrp
sent from my mobile device
Click to expand...
Click to collapse

Huh.. Interesting. Perhaps mount data partition from advanced? Not sure right now
sent from my mobile device

I think I fixed it. I updated TWRP to 2.6.3.3 and it did not say fail when I flashed it. Unfortunately Google is re-installing 100 apps and I have to wait for something to be installed that needs root.
I will report back soon.
SaHiLzZ said:
Huh.. Interesting. Perhaps mount data partition from advanced? Not sure right now
sent from my mobile device
Click to expand...
Click to collapse

It worked!
Thanks for pointing me in the right direction!

Awesome

Wierd TWRP Error

So after some messing around today with one of the cm12 builds, everytime I try to do anything in twrp I get the error "E: Unable to stat ' /data/power_supply_logger/power_supply_info.bin' " and i have no idea how to solve it. The only effect it seems to have is it makes restoring and backing up data fail at the last second (although as far as I can tell all of the data makes it). The error is always right after "updating partition details". I've tried reflashing 2 or three different versions of twrp (2.7.1.1, 2.6.3.1, and 2.8.1) as well as restoring stock vzw firmware through rsd lite as well as the gpe rom to no avail. Any help would be greatly appreciated.
Also, when flashing cm12, i get "mount: failed to mount /dev/block/platform/msm_sdcc. 1/by-name/userdata at /data: Device or resource busy"

StATicxTW0T said:
So after some messing around today with one of the cm12 builds, everytime I try to do anything in twrp I get the error "E: Unable to stat ' /data/power_supply_logger/power_supply_info.bin' " and i have no idea how to solve it. The only effect it seems to have is it makes restoring and backing up data fail at the last second (although as far as I can tell all of the data makes it). The error is always right after "updating partition details". I've tried reflashing 2 or three different versions of twrp (2.7.1.1, 2.6.3.1, and 2.8.1) as well as restoring stock vzw firmware through rsd lite as well as the gpe rom to no avail. Any help would be greatly appreciated.
Also, when flashing cm12, i get "mount: failed to mount /dev/block/platform/msm_sdcc. 1/by-name/userdata at /data: Device or resource busy"
Click to expand...
Click to collapse
I have the same problem with my moto g falcon XT1032.
Wen I try to flash CM 12 he gives the same error.

BinBug said:
I have the same problem with my moto g falcon XT1032.
Wen I try to flash CM 12 he gives the same error.
Click to expand...
Click to collapse
The first error or the second? I've narrowed the first down to a missing file in my data folder. Unfortunately rsd'ing doesn't help. If anyone'd be willing to upload it for me that'd be awesome. It's the bin file in /data/power_supply_logger/

The first error or the second error
StATicxTW0T said:
The first error or the second? I've narrowed the first down to a missing file in my data folder. Unfortunately rsd'ing doesn't help. If anyone'd be willing to upload it for me that'd be awesome. It's the bin file in /data/power_supply_logger/
Click to expand...
Click to collapse
Wen I try to flash te ROM he give me this:
Code:
Installing 'data/media/0/sideload.zip" ...
Checking for MD5 file ...
Skipping MD3 check : no MD5 file found
mont: failed to mount /dev/block/platform.msm_sdcc.1/by-name/userdata at /data: devices or resource busy
unmount of /data failed (-1): Devices or resource busy
E: Error Exexuting updater binary in zip ' /data/media/0/sideload.zip"
You say that i most change the bin file in /data/power_supply_logger/, but how?
link to rom that i use : CM12 for flacon

BinBug said:
Wen I try to flash te ROM he give me this:
Code:
Installing 'data/media/0/sideload.zip" ...
Checking for MD5 file ...
Skipping MD3 check : no MD5 file found
mont: failed to mount /dev/block/platform.msm_sdcc.1/by-name/userdata at /data: devices or resource busy
unmount of /data failed (-1): Devices or resource busy
E: Error Exexuting updater binary in zip ' /data/media/0/sideload.zip"
You say that i most change the bin file in /data/power_supply_logger/, but how?
link to rom that i use : CM12 for flacon
Click to expand...
Click to collapse
That error is caused by the version of TWRP you are using. Something about different versions and different updater scripts. Some have had sucess with 2.8.1, some with 2.6.3.1 and some with 2.7.1.1. You will need to try all three until you find the one that works for you. Do not touch the power supply file, that's whats causing my first error. Somehow it got deleted, and restoring to complete stock does not replace it, thats why i need someone to upload theirs.

failed to mount /data (Invalid argument)

Hi,
I just installed Huawei P9 [ROM][6.0] fRomFuture - NewWorld V2 and the phone boots and works fine, but I cant update Su binary because of this error in TWRP ( I have unlocked bootloader and root):
failed to mount /data (Invalid argument)

Just clear the notification on each restart, don't try and update the SU Binary. It's a known issue
See the rom's thread
And re the TWRP issue, are you using the latest one from @paulobrien? 3.0.2.0 RC3?

colthekid said:
Just clear the notification on each restart, don't try and update the SU Binary. It's a known issue
See the rom's thread
And re the TWRP issue, are you using the latest one from @paulobrien? 3.0.2.0 RC3?
Click to expand...
Click to collapse
Thank you, nope I was using the one from SRK TOOL. Do you know how to install TWRP via Paul, its a img file (i'll have a hunt for his copy)

In twrp, go install, choose install image, choose file, select partition recovery and done
Other method with pc-fastboot command -> fastboot flash recovery blabla.img this method need root with stock rom. Custom roms already rooted so dont worry

Milamber said:
Thank you, nope I was using the one from SRK TOOL. Do you know how to install TWRP via Paul, its a img file (i'll have a hunt for his copy)
Click to expand...
Click to collapse
Don't know if the Tool is using the latest version. Paul's is here ... http://forum.xda-developers.com/p9/development/wip-twrp-support-t3372331 still has some issues backing up, but best we have at the mo.
you can either flash as @master' suggests or via adb
adb reboot-bootloader
fastboot flash recovery twrp-3.0.2-0-eva-modaco-rc3.img
fastboot reboot
edit: beaten to it! :highfive:

colthekid said:
Don't know if the Tool is using the latest version. Paul's is here ... http://forum.xda-developers.com/p9/development/wip-twrp-support-t3372331 still has some issues backing up, but best we have at the mo.
you can either flash as @master' suggests or via adb
adb reboot-bootloader
fastboot flash recovery twrp-3.0.2-0-eva-modaco-rc3.img
fastboot reboot
edit: beaten to it! :highfive:
Click to expand...
Click to collapse
Thanks to both of you from Australia!

Hi. when I try backup system ihad message : "createTarFork () process ended with error :255"
What`s wrong?
Last messages from log
I:addFile '/data/hw_init/system/emui' including root: 0
==> set selinux context: ubject_r:system_data_file:s0
I:addFile '/data/hw_init/system/emui/base' including root: 0
I:Error adding file '/data/hw_init/system/emui/base' to '/external_sd/TWRP/BACKUPS/MWS0216C19000719/2017-03-15--12-38-32//data.f2fs.win'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/MWS0216C19000719/2017-03-15--12-38-32/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup
Click to expand...
Click to collapse
ok. I changed SD card ,formated it in phone and did backup by TWRP-3.0.2-0-eva. Now I think all done good. Last question is what about this red alert at the end of log?
Unmounting main partitions...
Failed to unmount '/system' (Device or resource busy)
Click to expand...
Click to collapse

Bricked phone

Hello,
First of all, my version was l19c185b385
I wanted to install marshmallow instead of nougat because of Xposed. Anyway, I didn't want to use rollback package (I didn't know that I can't install marshmallow like that) so, I just opened TWRP and then I removed everything even the system. Now, I can't install MM it always gives me the error "sparse flash write failure" in fastboot; however, when I installed b385 it finished the installation. In addition, I can't install anything for MM like recovery and twrp.
At the moment I can access only to trwp, fastboot, erecovery and dload (although it never works for me :crying
PS: I have tried to install rollback package via dload but it said it isn't compatible and stopped at 5%

IDontKnowAnythingAtAll said:
Hello,
First of all, my version was l19c185b385
I wanted to install marshmallow instead of nougat because of Xposed. Anyway, I didn't want to use rollback package (I didn't know that I can't install marshmallow like that) so, I just opened TWRP and then I removed everything even the system. Now, I can't install MM it always gives me the error "sparse flash write failure" in fastboot; however, when I installed b385 it finished the installation. In addition, I can't install anything for MM like recovery and twrp.
At the moment I can access only to trwp, fastboot, erecovery and dload (although it never works for me :crying
PS: I have tried to install rollback package via dload but it said it isn't compatible and stopped at 5%
Click to expand...
Click to collapse
Well done. Well done.
Try to flash firmware as zip file via twrp.
Are you able to mount/unmount /system in twrp?

xtcislove said:
Well done. Well done.
Try to flash firmware as zip file via twrp.
Are you able to mount/unmount /system in twrp?
Click to expand...
Click to collapse
yes I can mount system, I can't flash the firmware as zip because i don't have it i mean the update.zip can't be flashed in twrp

IDontKnowAnythingAtAll said:
yes I can mount system, I can't flash the firmware as zip because i don't have it i mean the update.zip can't be flashed in twrp
Click to expand...
Click to collapse
Come on... You risking your phone here, why don't you do some research before you mess things up?
The zip file with the update. App in it (firmware) is flashable with twrp
Huawei Firmware finder app in play store and you are fine

xtcislove said:
Come on... You risking your phone here, why don't you do some research before you mess things up?
The zip file with the update. App in it (firmware) is flashable with twrp
Huawei Firmware finder app in play store and you are fine
Click to expand...
Click to collapse
I thought you can't flash a system.zip without meta-inf
Anyway I have flashed it and it didn't work
I have also download another copy of the system, and yet nothing changed
Edit: the errors are
32K crc checked failure
E: unknown command [error]
E: unknown command [error]
update_huawei_pkg_from_ota_zip: update package from zip failed
updater process ended with error: 7
error installing zip file '/sdcard/update.zip'
updating partition details
failed to mount '/vendor' (invalid argument)
failed to mount '/product' (invalid argument)
failed to mount '/version' (invalid argument)
...done

okay, i have managed to fully fix my phone thanks to you , but now i need to rollback can you teach me how? idk why but dload method always fail

IDontKnowAnythingAtAll said:
okay, i have managed to fully fix my phone thanks to you , but now i need to rollback can you teach me how? idk why but dload method always fail
Click to expand...
Click to collapse
Look for a dload folder on your internal storage, there could be another folder something with "hw" in the name but i dont know anymore what i like to say there are maybe leftovers from an OTA or something like this just delete any folder with zip files in it.
Maybe you have the wrong Rollback package.
The Rollback package from the second link in my signature works on EVAL09 and EVAL19.

Need help with Rooting Moto G(6)

I have installed TWRP, in recovery when im trying to install dm_verity file i'm getting error - "unable to find boot block location". can someone help how to flash it

VineelKumar said:
I have installed TWRP, in recovery when im trying to install dm_verity file i'm getting error - "unable to find boot block location". can someone help how to flash it
Click to expand...
Click to collapse
You have to format data using the type "yes" to continue method. Then use twrp's menus to reboot back into recovery. Mount /system and /vendor in twrp then flash it. If you still have a problem, then try the 5/21/19 release of the disabler.

@Spaceminer No, that's nonsense! Data is mounted correctly and is fully unencrypted. See screenshot where you can read "Updating partition details... done" There's NO error message.
That's the first thing...
Second, there's no need to mount sth manually, the script itself will do this if necessary!
@VineelKumar Download the dm-verity-disabler.zip by Zackptg5 from
https://zackptg5.com/android.php#disverfe
This will work with your device.

WoKoschekk said:
@Spaceminer No, that's nonsense! Data is mounted correctly and is fully unencrypted. See screenshot where you can read "Updating partition details... done" There's NO error message.
That's the first thing...
Second, there's no need to mount sth manually, the script itself will do this if necessary!
@VineelKumar Download the dm-verity-disabler.zip by Zackptg5 from
https://zackptg5.com/android.php#disverfe
This will work with your device.
Click to expand...
Click to collapse
It doesn't show data as mounted. It shows the external sdcard as being mounted. And there is an error, twrp is giving error 1, and the disabler is also showing an error saying it can't find the boot block location. This means twrp isn't able to modify block devices or mount them properly. What I told him to do will fix the problem. The script doesn't mount anything correctly if twrp is not able to run the script... I know what I'm talking about. I wouldn't steer the guy wrong.
Edit: I'm definitely correct. What I said is actually mentioned in the official twrp thread for this device. It says; "If you format data (Not just factory reset) after decrypting you must reboot into recovery and format again." - direct quote from the instructions, under notes.

I flashed the same .zip with /data, /system and /vendor mounted properly and ran into the same error... (see screenshot)
To mount a device block it's not neccessary to have /data mounted.
The .zip is incompatible with Moto g6 - that's all!

WoKoschekk said:
@Spaceminer No, that's nonsense! Data is mounted correctly and is fully unencrypted. See screenshot where you can read "Updating partition details... done" There's NO error message.
That's the first thing...
Second, there's no need to mount sth manually, the script itself will do this if necessary!
@VineelKumar Download the dm-verity-disabler.zip by Zackptg5 from
https://zackptg5.com/android.php#disverfe
This will work with your device.
Click to expand...
Click to collapse
Thanks it worked fine. But for some reason the mobile was struck in boot loop(just warning message on screen saying, you have unlocked bootloader for couple of seconds and then same thing appears again), any idea how to fix it ?

VineelKumar said:
...any idea how to fix it ?
Click to expand...
Click to collapse
Yes, do it manually. The disabler.zip does two things on your device.
1.) remove dm-verity
2.) disable forceencryption of /data
The magisk.zip also removes dm-verity within the installation process. So you don't need the disabler.zip for this.
To remove forceencryption you have to follow a few simple steps which are given in my instruction below:
preparation:
You have to be on the latest stock firmware with TWRP installed and nothing else.
Boot into TWRP and format /data (do not wipe it! you must use format). Then reboot directly into TWRP!!
Now let's start to remove forceencryption.
1.) place the attached .tar.gz file in your internal storage (/sdcard)
2.) mount /vendor in the options menu and open TWRP's terminal command under advanced settings
3.) type in (or copy it from here)
Code:
tar -xvzf /sdcard/fstab.tar.gz
4.) at next boot your device will be unencrypted
Now don't reboot your device and stay in TWRP to install the magisk.zip v19.3!! That's important to flash v19.3 instead of the latest v20.3 otherwise it causes a bootloop!! I don't know why it does but you can later update Magisk without any problems through the Magisk Manager.
Magisk will now remove the dm-verity during the installation process. That's a part of the installation script of Magisk.
When the installation of Magisk has finished you can boot your device into system. Maybe it reboots one time but don't care. Also the bootanimation will take some time due to unencryption of /data. That's quite normal.

WoKoschekk said:
Yes, do it manually. The disabler.zip does two things on your device.
1.) remove dm-verity
2.) disable forceencryption of /data
...
the installation of Magisk has finished you can boot your device into system. Maybe it reboots one time but don't care. Also the bootanimation will take some time due to unencryption of /data. That's quite normal.
Click to expand...
Click to collapse
I appreciate your patience, WoKoschekk. I for one appreciate the guide and insight into the reason root must be achieved this way. I was using 20.3 and 18 the whole time. I was successful with your instructions the first time. It became stuck on boot after the initia reboot, so I pushed fstab and magisk again and it was fine. I remember that on one phone, encryption wasn't a problem if you had your pin or password. Could it be the same here provided there was no fingerprint assigned (might be the original pixel)? I'm guessing this TWRP can't decrypt? Just curious, because N/A balogna.

I'm glad to hear that!
TWRP for Moto g6 can't decrypt your data. That's the reason why you must disable forceencryption to use TWRP.

WoKoschekk said:
Code:
tar -xvzf /sdcard/fstab.tar.gz
Click to expand...
Click to collapse
I don't have a SD card, so I put the file into the TWRP folder. I then used,
Code:
tar -xvzf data/media/TWRP/fstab.tar.gz
Was that the right location?

/data/media/0 = /sdcard
/external_sd = external SD in SD-card slot

WoKoschekk said:
/data/media/0 = /sdcard
/external_sd = external SD in SD-card slot
Click to expand...
Click to collapse
Ok, I see now. Anyway all updated and rooted with your instructions, thanks.