Database Develop

AIO ZV 8 rooter/CVM NOT WORKING.

I've followed EVERY GAWDAMN suggestion/guide/direction listed, and ZV8 refused to root/CWM for me.
Here's what the AIO says:
Root and Recovery for ZV8
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Mounting Device
remount failed: Operation not permitted
Pushing Root Permissions
Unable to chmod /system/bin/su: No such file or directory
3720 KB/s (5345280 bytes in 1.403s)
Unable to chmod /system/xbin/busybox: Read-only file system
--install: applet not found
Installing CWM Recovery
/dev/block/mmcblk0p14: cannot open for write: Permission denied
Remove Trash
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
rm failed for /data/local.prop, No such file or directory
CWM Recovery!!!
Just a note for MT. I wish the process were a bit more visible, as I've had to manually push things with adb before on rooting attempts.
I've spent 3 days trying to get this piece of sh!t rooted, and I'm tired of it.
I've followed EVERY DIRECTION/GUIDE/INSTRUCTION to the T, and still nothing, so a hearty STFU if all you can offer is a "Did you follow the directions?"

On the "Regain Root after update" post there is talk of using a terminal emulator to make the root stick on V8. The only thing that worked for me is the post at the top of page 7 (or 8?) that has about 8 steps. If you haven't already tried it.
Sent from my BROKEN OUT VS910

antiwesley said:
I've followed EVERY GAWDAMN suggestion/guide/direction listed, and ZV8 refused to root/CWM for me.
Here's what the AIO says:
Root and Recovery for ZV8
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Mounting Device
remount failed: Operation not permitted
Pushing Root Permissions
Unable to chmod /system/bin/su: No such file or directory
3720 KB/s (5345280 bytes in 1.403s)
Unable to chmod /system/xbin/busybox: Read-only file system
--install: applet not found
Installing CWM Recovery
/dev/block/mmcblk0p14: cannot open for write: Permission denied
Remove Trash
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
rm failed for /data/local.prop, No such file or directory
CWM Recovery!!!
Just a note for MT. I wish the process were a bit more visible, as I've had to manually push things with adb before on rooting attempts.
I've spent 3 days trying to get this piece of sh!t rooted, and I'm tired of it.
I've followed EVERY DIRECTION/GUIDE/INSTRUCTION to the T, and still nothing, so a hearty STFU if all you can offer is a "Did you follow the directions?"
Click to expand...
Click to collapse
Try booting into CWM the old-fashioned way (hold down button and power). When I went through all the steps, everything looked liked it failed and all I had was an unrooted ZV8. Even Root Checker said I was unrooted. But then I tried to manually boot into CWM, and it worked! I flashed the new rom, and superuser came with it! Might as well give it a try. There's the possibility that you end up wiping data if you don't actually have CWM, but it sounds like you don't really care at this point...

I went through 2 days of hell to get root. There are so many things to try but I think the one thing that worked for me was that after you root the stock V7 is to run titanium backup. When I ran it it said it had to change su access or something and then I rebooted and did this in a terminal program
su<enter>
echo 'ro.kernel.qemu=1' > /data/local.prop<enter>
but also made sure by then doing this:
cat /data/local.prop
if you don't see exactly the ro.kernel.qemu=1 redo it. I was surprised that I had it wrong but for some reason the terminal app missed characters sometimes.
-Keith

What a maroon.
Sent from my VS910 4G using Tapatalk

$ su
su
su: permission denied
$ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
cannot create /data/local.prop: permission denied
$

If you are able to have cwm breakout is rooted.
Sent from my Galaxy Nexus using xda premium

Thanks!
Thanks Antiwesley!
I had tried a few different times to get this working, your post below finally got it for me:
"LGNPST to ZV7.
Using AIO 1 LG Revo AIO, Root ZV7 ONLY.
Install "Rom Manager" (thanks to slimzim for this one)
Manually create local.prop as seen elsewhere in a few other versions of this kind of thing.
LGNPST to ZV8.
In a command prompt, 'adb remount'
'adb push su /system/bin/su'
'adb push superuser.apk /system/bin/superuser.apk'
'adb push busybox /system/bin/busybox'
Use AIO 2 to install CWM. It will error on a couple of things, don't panic. (one is an applet failure in the rooting process and the other are rm failures.) DO NOT USE OPTION #1! Only use Option #2!
Reboot.
Use Rom Manager's "Reboot Recovery" option and it boots straight into CWM.
(I had zero success using the hardware (power/down button) to boot into CWM.
Apply Broken Out 1.1
Back up while you're in CWM.
Reboot.
Enjoy ZV8."
The only thing I did differently was OTA to ZV8 rather than LGNPST. Also when I ran option two of AIO 2 I didn't get any errors.
The whole process took right around an hour.
Thanks again!
FYI I would have posted this in the dev section in the Regain Root thread but am lacking the posts to do so.

stinkyjak said:
$ su
su
su: permission denied
$ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
cannot create /data/local.prop: permission denied
$
Click to expand...
Click to collapse
koda1789 said:
Thanks Antiwesley!
I had tried a few different times to get this working, your post below finally got it for me:
"LGNPST to ZV7.
Using AIO 1 LG Revo AIO, Root ZV7 ONLY.
Install "Rom Manager" (thanks to slimzim for this one)
Manually create local.prop as seen elsewhere in a few other versions of this kind of thing.
LGNPST to ZV8.
In a command prompt, 'adb remount'
'adb push su /system/bin/su'
'adb push superuser.apk /system/bin/superuser.apk'
'adb push busybox /system/bin/busybox'
Use AIO 2 to install CWM. It will error on a couple of things, don't panic. (one is an applet failure in the rooting process and the other are rm failures.) DO NOT USE OPTION #1! Only use Option #2!
Reboot.
Use Rom Manager's "Reboot Recovery" option and it boots straight into CWM.
(I had zero success using the hardware (power/down button) to boot into CWM.
Apply Broken Out 1.1
Back up while you're in CWM.
Reboot.
Enjoy ZV8."
The only thing I did differently was OTA to ZV8 rather than LGNPST. Also when I ran option two of AIO 2 I didn't get any errors.
The whole process took right around an hour.
Thanks again!
FYI I would have posted this in the dev section in the Regain Root thread but am lacking the posts to do so.
Click to expand...
Click to collapse
I am having the problem Stinkjak is having. No matter how I try and copy the .prop into the /data folder. I get a message that says java.io.filenotfoundexception:/data/local.prop (permission denied). Can anyone crack this error?

Plumbert said:
I am having the problem Stinkjak is having. No matter how I try and copy the .prop into the /data folder. I get a message that says java.io.filenotfoundexception:/data/local.prop (permission denied). Can anyone crack this error?
Click to expand...
Click to collapse
Are you already on stock ZV7 and rooted? Use Root Explorer and go to /data and create new file, name it local.prop. Open in text editor, enter ro.kernel.qemu=1 then save it. If you can't do that in Root Explorer then you aren't rooted.

[DEV][TOOL] Generic SBK dumper [Source included]

Generic Nvidia Tegra Secure Boot Key Dumper, v0.4
**************************************
YOU MUST GET ROOT BEFORE PROCESSING!!!
This is a temp memory only fix, after you reboot your phone, everything will restore to it's original status. So it WILL NOT brick your phone at all!
**************************************
I am not sure it work for your devices or not, because I only get a SU660 device!
So , you must knew that P880 use a Secure Boot Key to encrypt its nflash communication, if you don't know the SBK, you can't use nvflash backup/restore your partitions.
I found that in the linux kernel, there is some protection that block the user try to read out SBK when the phone in "odm_production" status. So I designed a little software try to patch the phone RAM to bypass the protection.
This is a kernel patcher which will remove the protection when trying to read /sys/firmware/fuse/secure_boot_key
The dumper will patch the kernel in memory, and let you show the secure_boot_key.
Hope it work for all tegra devices.
Usage:
1. adb push dumpSBK /data/local/
2. adb shell
su
chmod 0777 /data/local/dumpSBK
/data/local/dumpSBK
After that, you can
4. cat /sys/firmware/fuse/secure_boot_key
dumpSBK will search the first 1MB physical address(which kernel will be there), and try to patch it.
Usage: dumpSBK [star_mem_addr in KB]
for example: dumpSBK 32
which will search the 32KB~1MB physical memory.
2012/12/31:
re-compile it with -static switch, so it can run on all android platform.
update instructions.
2013/01/01:
modify the program, and let you select which memory range to patch.
usage: dumpSBK [start_memory_addr] [end_memory_addr]
for example: dumpSBK 1 1024
which will search 1MB ~ 1024MB memory and try to patch the kernel.
2013/01/01:
v0.3 add more error detection in the file.
2013/01/06:
v0.4 wil search the first 1MB physical memory, you can specify the start_address , for example dumpSBK 32
and update the search pattern , it will fit for more compiler options.
2013/01/07:
Secure_Boot_Key Dumper for tegra2/tegra3 v0.1
1. adb push ss.ko /sdcard/
2. adb shell
su
cd /sdcard/
insmod ss.ko
dmesg
3. at the end of dmesg, you should see the secure_boot_key.....
2013/01/08:
v0.2 dump all known fuses.....

If you get a error:
Kernel patching failed! Abort....
that means your device kernel has a differnt tegra source code, or compiled with a different compiler........
Please let me know which kernel source code and compiler / compile switch it used.

marsgod said:
If you get a error:
Kernel patching failed! Abort....
that means your device kernel has a differnt tegra source code, or compiled with a different compiler........
Please let me know which kernel source code and compiler / compile switch it used.
Click to expand...
Click to collapse
will it hard brick the phone???

razerblade17 said:
will it hard brick the phone???
Click to expand...
Click to collapse
Do you want to try and find out? I certainly don't.
I like my phone and don't want to end up with an expensive paperweight instead :banghead:

SimonTS said:
Do you want to try and find out? I certainly don't.
I like my phone and don't want to end up with an expensive paperweight instead :banghead:
Click to expand...
Click to collapse
i'd have tried if i didnt sell mine
plus this wont brick the device
nothing can since bootloader's lock so u practically cant mess up anything that matters for booting up

The Troll said:
i'd have tried if i didnt sell mine
plus this wont brick the device
nothing can since bootloader's lock so u practically cant mess up anything that matters for booting up
Click to expand...
Click to collapse
Yep, i think Troll isn't trolling us i would try it out ,but i'm waitin' for my LG, factory reset via recovery bricked it.

This is a temp memory only fix, after you reboot your phone, everything will restore to it's original status. So it WILL NOT brick your phone at all!
The patcher will patch a single byte in your phone RAM, it will not modify any bit in your NAND Flash.

C:\adb>adb shell chmod 0777 /data/local/dumpSBK
Unable to chmod /data/local/dumpSBK: Operation not permitted
I got this

Here is a log of what happened, after I ran the program on my 4X with 10H F/W:
[email protected]:/data/local # /data/local/dumpSBK
/data/local/dumpSBK
[1] + Stopped (signal) /data/local/dumpSBK
[email protected]:/data/local # cat /sys/firmware/fuse/secure_boot_key
cat /sys/firmware/fuse/secure_boot_key
[1] + Segmentation fault /data/local/dumpSBK
Click to expand...
Click to collapse

^ You guys have rooted phone and debugging turned on? maybe that's why these errors.

phone rooted, recheked with root checker.
I have debuging mode one.
But i cant push files to /data/local/
C:\o4xr>adb push dumpSBK /data/local/
push: dumpSBK/Readme.txt -> /data/local/Readme.txt
failed to copy 'dumpSBK/Readme.txt' to '/data/local/Readme.txt': Permission deni
ed
Click to expand...
Click to collapse
So i put those files there with es file explorer and try to run second comand:
C:\o4xr>adb shell chmod 0777 /data/local/dumpSBK
Unable to chmod /data/local/dumpSBK: Operation not permitted
Click to expand...
Click to collapse
Who can explain why?

s7ar73r said:
phone rooted, recheked with root checker.
I have debuging mode one.
But i cant push files to /data/local/
So i put those files there with es file explorer and try to run second comand:
Who can explain why?
Click to expand...
Click to collapse
uhmm
as i seem to recall, the hello world rooting method *only known method* turns on access to that location..
thats where superuser and binaries are added
so if im correct u'd be able to push it if u follow the rooting method and adding the commands to the root.bat *or whatever its name it* that we run in pc by using notepad or anything..
so it should reroot and push ur desired file as well
*again, dun remember, been months but im sure hello world/backuptest thingy will be useful*

k1337Ultra said:
Here is a log of what happened, after I ran the program on my 4X with 10H F/W:
Click to expand...
Click to collapse
I get the this,too.
the v1 patch did not completely work.

The Troll said:
uhmm
as i seem to recall, the hello world rooting method *only known method* turns on access to that location..
thats where superuser and binaries are added
so if im correct u'd be able to push it if u follow the rooting method and adding the commands to the root.bat *or whatever its name it* that we run in pc by using notepad or anything..
so it should reroot and push ur desired file as well
*again, dun remember, been months but im sure hello world/backuptest thingy will be useful*
Click to expand...
Click to collapse
Its not the only known method... but now I don't have time, even to think... I just woke up and came to the computer.
You need to think widder
Gonna back to sleep :angel:

k1337Ultra said:
Here is a log of what happened, after I ran the program on my 4X with 10H F/W:
Click to expand...
Click to collapse
En.... I think it is due to I compiled the dumpSBK with 4.1.2 android, so it will not work on a ICS rom... I will check it later...

s7ar73r said:
C:\adb>adb shell chmod 0777 /data/local/dumpSBK
Unable to chmod /data/local/dumpSBK: Operation not permitted
I got this
Click to expand...
Click to collapse
You MUST root your device.
then type
adb root
to get the adb rooted work.
Of couse, you must have your device USB debug ON.

please do all the steps the right way , starting with the OP instruction you the right way.
OP is assuming we got a "unsecure" booted device, which we have not exactly due to the locked bootloader.
so its pointless to write "root" instruction froms adb when the device is in secure mode. OP is now told and should update the instructions, thank you.
ignore all the "adb shell" instruction and log into the device with "adb shell" once only.
in that shell which is opened execute the "su", so you get a root # prompt.
then run instructions given and skip all "adb shell" infront.
thats it, good luck.
edit:
adb remount,adb root and running root commands only work on unsecure devices , we got ro.secure=1 here and adb not allowed to run root commands

i think it's better toroot Your 4X with Dexter http://forum.xda-developers.com/showpost.php?p=30574547&postcount=85 because it doesn't have any issues, for me with 1st root method for example titanium backup wasn't working.
@marsgod, yep - we don't have 4.1.2 but 4.0.3, but u can leave this version because we'll get 4.1.2 in january

k1337Ultra said:
Here is a log of what happened, after I ran the program on my 4X with 10H F/W:
Click to expand...
Click to collapse
[email protected]:/data/local # /data/local/dumpSBK
/data/local/dumpSBK
[1] + Stopped (signal) /data/local/dumpSBK
[email protected]:/data/local # cat /sys/firmware/fuse/secure_boot_key
cat /sys/firmware/fuse/secure_boot_key
[1] + Segmentation fault /data/local/dumpSBK
i have same result . segmentation fault
whats wrong?

bullghost said:
[email protected]:/data/local # /data/local/dumpSBK
/data/local/dumpSBK
[1] + Stopped (signal) /data/local/dumpSBK
[email protected]:/data/local # cat /sys/firmware/fuse/secure_boot_key
cat /sys/firmware/fuse/secure_boot_key
[1] + Segmentation fault /data/local/dumpSBK
i have same result . segmentation fault
whats wrong?
Click to expand...
Click to collapse
after adb shell type su, u should have [email protected], not [email protected]
@edit so... anyone tested it in right way?

[SCRIPT] DROID 4 Utility XT894 Jellybean -- Windows + Mac + Linux (All In One!)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is ONLY for the DROID 4 XT894. Do NOT use this on anything else!
DROID 4 Utility XT894Jellybean
Use a Download Manager such as "Orbit Download Manager" for best downloading results.
Mirrors:
Dev-Host
Batakang
Filesize: 497 MB (521,766,988 bytes)
MD5: B8E86DDCC3C59571E7AB086BE13BD89D
- Windows Instructions
Extract .zip to its own folder on the Desktop.
Install the required drivers. The folder with the drivers is called "Drivers [WINDOWS ONLY]" and is included in the Utility folder.
Double click the ".bat" file. This will be called "WindowsUtility.bat" the image is just for reference.
- Mac & Linux Instructions
Extract the .zip to any folder you like, the /Downloads/ or /Desktop/ folder should work just fine.
Open a Terminal window. (On Mac: Applications > Utilities > Terminal)
Learn your 'sudo' password. This is almost always your Admin password on a Mac computer. On Linux you should already know what this is, its yours account password if your account is an admin as well.
Type the following code into the Terminal Windows, places where it says ***DRAG HERE*** are telling you to simply drag the folder there. For example: cd ***DRAG FOLDER HERE*** then press 'Enter' after each line.
Code:
cd ***DRAG UNZIPPED UTILITY FOLDER HERE***
chmod +x ./LinuxMacUtility.sh
bash ./LinuxMacUtility.sh
You will be asked for your sudo password at least once in the Utility process, so make sure you followed the instructions to learn it.
Functions of the DROID 4 Utility XT894 Jellybean:
Code:
1 Flash Official Jellybean Firmware (Wipe Data)
2 Flash Official Jellybean Firmware (No Data Wipe)
3 Razr Blade: Motorola Droid Razr 4.1 Root Exploit by djrbliss
4 Install Safestrap 3 App by Hashcode.
Number 1 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official Jellybean firmware to your device and will wipe data.
Number 2 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official Jellybean firmware to your device and will NOT wipe data.
Number 3 Explained -- This is Dan Rosenberg's DROID RAZR 4.1 Jellybean exploit called 'RAZR Blade'. This option requires your phone to be booted normally, with USB Debugging enabled. (This is working on the DROID 4 as well.)
Number 4 Explained -- This option requires your phone to be booted normally, with USB Debugging enabled. It will install Hashcode's App for Safestrap 3.11.
Remember, do not run this utility unless your phone is at 100% battery OR you have bought yourself one of Team Black Hat's Factory-Style Programming Adapters.
Thanks to Hashcode for Safestrap and Djrbliss for RAZR_Blade!

Yes! You are a champion, mattlgroff!
Sent from my DROID4 using xda app-developers app

Root failing.
Hello,
First and foremost I'd like to thank you for this utility. 4.1 flashed without a hitch! Unfortunately, I am unable to get the root to work. I've attached the text from where it started to error.
The root is failing here, after phase 2. Any ideas?:
/system/bin/sh: can't create /data/data/com.motorola.contextual.fw/files/DataCle
arJarDex.jar: Permission denied
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase three (this will take a minute)...
failed on '/data/logger' - Permission denied
mkdir failed for /data/logger, File exists
Unable to chmod /data/logger: Operation not permitted
link failed File exists
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase four...
3559 KB/s (543080 bytes in 0.149s)
3597 KB/s (1867568 bytes in 0.507s)
3144 KB/s (476557 bytes in 0.148s)
2308 KB/s (63838 bytes in 0.027s)
[*] Cleaning up...
/system/bin/sh: su: not found
/system/bin/sh: can't create /data/data/com.motorola.contextual.fw/files/DataCle
arJarDex.jar: Permission denied
[*] Rebooting...
[*] Exploit complete!
Thanks in advance for your assistance.

Thanks a lot, i could unbrick my phone thank to this tool.

korngames said:
Hello,
First and foremost I'd like to thank you for this utility. 4.1 flashed without a hitch! Unfortunately, I am unable to get the root to work. I've attached the text from where it started to error.
The root is failing here, after phase 2. Any ideas?:
/system/bin/sh: can't create /data/data/com.motorola.contextual.fw/files/DataCle
arJarDex.jar: Permission denied
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase three (this will take a minute)...
failed on '/data/logger' - Permission denied
mkdir failed for /data/logger, File exists
Unable to chmod /data/logger: Operation not permitted
link failed File exists
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase four...
3559 KB/s (543080 bytes in 0.149s)
3597 KB/s (1867568 bytes in 0.507s)
3144 KB/s (476557 bytes in 0.148s)
2308 KB/s (63838 bytes in 0.027s)
[*] Cleaning up...
/system/bin/sh: su: not found
/system/bin/sh: can't create /data/data/com.motorola.contextual.fw/files/DataCle
arJarDex.jar: Permission denied
[*] Rebooting...
[*] Exploit complete!
Thanks in advance for your assistance.
Click to expand...
Click to collapse
Try wiping and trying again. I was just told by a user on DroidRzr that it worked on the D4 OTA.
Sent from my Galaxy Nexus using Tapatalk 2

When I try this on my Droid 4 with the latest OTA JB update from Verizon, the terminal gets stuck at "waiting for device". This has happened previously when I tried to use the ICS Utility when my phone still had ICS. I've tried on several Windows PC's and none have seemed to recognized my device even with the latest Motorola drivers installed (when I went to install the drivers included in the JB Utility, I was alerted I already had newer versions). I have USB debugging enabled on my device. Am I missing something or doing something wrong?

Do you set your USB option from mass storage to MTP?
Sent from my DROID4 using xda app-developers app

I'm getting findstr.exe is not a valid win32 application... Running windows XP

i noticed the root method used with this utility uses a different superuser
when i used this and tried to use either the verizon tether or wifi tether for root users it wouldn't work because of the su used. But when i downloaded and used a different razor root script that installed supersu everything works great
just a fyi
i used this for rooting
http://vulnfactory.org/public/razr_blade.zip
also using this there is no need to put your device in mtp mode

dbreezy187 said:
Do you set your USB option from mass storage to MTP?
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
My USB connection is and has been set to MTP. Is that what it should be set as, or is it supposed to be set to one of the other two options?

Does this work root on the verizon droid 4? tryin to help my friend get his tether back.

When I used it on ICS that was my issue.... as far as I know yes MTP... are you using the same USB cable each time... have you checked device manager to unsure your phone is connected properly... ... ... yes this will root...
Sent from my DROID4 using xda app-developers app

dbreezy187 said:
When I used it on ICS that was my issue.... as far as I know yes MTP... are you using the same USB cable each time... have you checked device manager to unsure your phone is connected properly... ... ... yes this will root...
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
How do I check "device manager"? I'm reading some stuff that leads me to believe Motorola is quite strict about the use of their cables. Some say you may need an actual Motorola branded cable to get the device to connect. Where can I get an official Motorola micro USB cord?

Thanks for the root suggestion. Worked great and Verizon tether started up with no problems.
ovelayer said:
i noticed the root method used with this utility uses a different superuser
when i used this and tried to use either the verizon tether or wifi tether for root users it wouldn't work because of the su used. But when i downloaded and used a different razor root script that installed supersu everything works great
just a fyi
i used this for rooting
http://vulnfactory.org/public/razr_blade.zip
also using this there is no need to put your device in mtp mode
Click to expand...
Click to collapse

chewy74 said:
Thanks for the root suggestion. Worked great and Verizon tether started up with no problems.
Click to expand...
Click to collapse
no problem glad it helped

i've updated to the ota and have tried to root using this method on both camera and mtp, then wiped and tried again. still no root. phase one fails. used two different usb's, uninstalled and reinstalled drivers twice. whats goin on?

you reinstalled drivers, but did you check device manager to see the pc seeing phone correct (as a adb device)
Sent from my Clear using xda premium

how do i actually open device manager. i see no application after i install it

windows device manager
start>control panel>hardware & sound> device manager
if driver is not correct, may look like
if correct should look like

I have root back! Thank you!

Navibar 3 -5 -7 buttons mod - android 5.0 air3g, air 2

Like in description
Navibar 3 -5 -7 buttons mod - android 5.0
air3g, air 2​
If you have my rom Lolipop ( mirek190 ) just plug USB and choose proper option.
On other rom make sure you have root and USB debugging on.
3 buttons navigation bar​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5 buttons navigation bar​
7 buttons navigation bar​
air 3g
https://drive.google.com/open?id=0B8BF9-TGlz-FY2tWZUVZa05FU00
air 2
https://drive.google.com/open?id=0B8BF9-TGlz-FTEhvUTl2clE3Z3M
Ps - NOT RUN IT AS ADMINISTRATOR !

Hi mirek.
Can you add systemui.apk with a clock in its original position with 3 buttons?

Nope - center clock stays in the center like buttons

delete

Great job Mirek!

Hi, can you do this for the Air III? Do you need the stock SystemUI.apk?
EDIT:
I found this post www[dot]tsochen[dot]com/blog/post/15 and nearly the same intructions works for Air III M5C5. But the status_bar_*xml fix as not needed. This is the diff of navigation_bar.xml for 3 buttons
gist[dot]github[dot]com/kazuoteramoto/c0730bb27d0fb8dc6332

The system cannot find the path specified
Hi,
I'm getting the message: "The system cannot find the path specified."
I booted to mirek's rom, plugged the tablet to my laptop and ran the bat file. It was in debugging mode also.
Am I doing it wrong? Any help plz?

Wow, thanks, teramoto--this is fantastic! I just modded the SystemUI.apk on my device based on the tsochen link you provided, and your diff. I didn't want the screenshot and volume +/- buttons, but I did want to keep the menu button. So I just modded as indicated, and left the @id/menu entries untouched. The result is a nicely centered, four button variant.
EDIT: Somebody requested that I post my modded SystemUI.apk for a 4-button nav bar for the Air 3/III 32GB (M5C5). At the link below, I have done this, but also included 3- and 5-button versions, as well as the original 7-button SystemUI.apk version from the M5C5 v1.04 stock rom. The various SystemUI.apk files are obviously named by an explicit filename extension as you'll see when you download the archive. Also, let me reiterate--these are specifically for an Air 3/III 32GB (M5C5) tablet. Make sure that file ownership/permission is set correctly on installation else you will run into errors with the UI, and you will have to go in via adb root for manual fixing. Finally, and most importantly, note that credit for this goes to teramoto and the tsochen blog posting he pointed out above, which I just followed to do this, and also to mirek190 for starting this thread, and for helping out so many X98 Air users. Here's the link:
https://mega.nz/#!Hw0jRKBJ!0omuxVQXFHjzdbMV1bg6yvBhtMT570-gBhnkKxw2A4o

irfaan92 said:
Hi,
I'm getting the message: "The system cannot find the path specified."
I booted to mirek's rom, plugged the tablet to my laptop and ran the bat file. It was in debugging mode also.
Am I doing it wrong? Any help plz?
Click to expand...
Click to collapse
Facing the same problem...

irfaan92 said:
Hi,
I'm getting the message: "The system cannot find the path specified."
I booted to mirek's rom, plugged the tablet to my laptop and ran the bat file. It was in debugging mode also.
Am I doing it wrong? Any help plz?
Click to expand...
Click to collapse
Have you installed drivers ?

It worked actually.... I had been running it as admin when i shouldn't be...
But thanks for the reply mirek... Keep up the good work

irfaan92 said:
It worked actually.... I had been running it as admin when i shouldn't be...
But thanks for the reply mirek... Keep up the good work
Click to expand...
Click to collapse
I did the same as you for whole day....thanks anyway.

irfaan92 said:
It worked actually.... I had been running it as admin when i shouldn't be...
But thanks for the reply mirek... Keep up the good work
Click to expand...
Click to collapse
Thanks for a clue - 1st post updated .

verbage said:
Make sure that file ownership/permission is set correctly on installation else you will run into errors with the UI, and you will have to go in via adb root for manual fixing.
Click to expand...
Click to collapse
Someone asked for some more details about how to "go in via adb root for manual fixing". The question did not provide a lot of details except that the person copied over the file, renamed it, and then the navbar disappeared. So I am assuming that the SystemUI.apk file is correctly named and in the right place on the filesystem, but there is an issue of file ownership/permissions that needs to be fixed manually. If you are in that situation, or the UI is in an endless FC loop because of the same issue, here is what to do.
First, you'll need a working adb (Android Debug Bridge) install. If you don't have one already, the simplest thing to do is to just use the core adb files that mirek190 provides in either one of his ~2MB button mod archives linked at the start of this thread. In particular, I am talking about the "data" directory that has the five exe/dll files. Anyway, extract that, and then open a DOS command window in that directory. To quickly open up a command window, shift-right click on a blank part of the Explorer window, and choose the "Open command window here" option.
Now plug in your tablet, and give the following six commands in the command window you opened:
adb root [this initializes adb in root mode]
adb shell [this spawns an actual adb shell so you'll see the command prompt change]
mount -o rw,remount /system [this makes the /system partition writeable so you can make changes]
cd /system/priv-app/SystemUI [this changes to the right directory to avoid loooonnnngggg command lines]
chown root.root SystemUI.apk && chmod 644 SystemUI.apk [this manually specifies the correct file ownership and permissions]
exit [this gets you back out of the adb shell]
Note again that the above six commands are what is needed if the issue is just one of file ownership and permissions, and the modded SystemUI.apk is already correctly named and in the right spot. It is also the barebones version of a manual fix--before you give any commands, you might want to do some exploration to make sure my assumptions in the previous sentence are correct... For example, if your SystemUI.apk file is incorrectly named, you'll have to fix that first (i.e. "mv INCORRECTLYNAMEDFILE SystemUI.apk"). And before exiting out of the adb shell, you might want to restart the UI on the tablet just to make sure things are working correctly in case you need more triage via adb.
Hope this helps!

verbage said:
Someone asked for some more details about how to "go in via adb root for manual fixing". The question did not provide a lot of details except that the person copied over the file, renamed it, and then the navbar disappeared. So I am assuming that the SystemUI.apk file is correctly named and in the right place on the filesystem, but there is an issue of file ownership/permissions that needs to be fixed manually. If you are in that situation, or the UI is in an endless FC loop because of the same issue, here is what to do.
First, you'll need a working adb (Android Debug Bridge) install. If you don't have one already, the simplest thing to do is to just use the core adb files that mirek190 provides in either one of his ~2MB button mod archives linked at the start of this thread. In particular, I am talking about the "data" directory that has the five exe/dll files. Anyway, extract that, and then open a DOS command window in that directory. To quickly open up a command window, shift-right click on a blank part of the Explorer window, and choose the "Open command window here" option.
Now plug in your tablet, and give the following six commands in the command window you opened:
adb root [this initializes adb in root mode]
adb shell [this spawns an actual adb shell so you'll see the command prompt change]
mount -o rw,remount /system [this makes the /system partition writeable so you can make changes]
cd /system/priv-app/SystemUI [this changes to the right directory to avoid loooonnnngggg command lines]
chown root.root SystemUI.apk && chmod 644 SystemUI.apk [this manually specifies the correct file ownership and permissions]
exit [this gets you back out of the adb shell]
Note again that the above six commands are what is needed if the issue is just one of file ownership and permissions, and the modded SystemUI.apk is already correctly named and in the right spot. It is also the barebones version of a manual fix--before you give any commands, you might want to do some exploration to make sure my assumptions in the previous sentence are correct... For example, if your SystemUI.apk file is incorrectly named, you'll have to fix that first (i.e. "mv INCORRECTLYNAMEDFILE SystemUI.apk"). And before exiting out of the adb shell, you might want to restart the UI on the tablet just to make sure things are working correctly in case you need more triage via adb.
Hope this helps!
Click to expand...
Click to collapse
Hi. first let me thank you for your effort.
I tried your solution but I'm still without the buttons and notification bar.
Code:
D:\@SUPPORT\TECLAST_X98\x98air3g-buttons-mod\data>adb root
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
D:\@SUPPORT\TECLAST_X98\x98air3g-buttons-mod\data>adb shell
[email protected]_m5c5:/ # mount -o rw,remount /system
mount -o rw,remount /system
[email protected]_m5c5:/ # cd /system/priv-app/SystemUI
cd /system/priv-app/SystemUI
[email protected]_m5c5:/system/priv-app/SystemUI # ls
ls
SystemUI.apk
x86
[email protected]_m5c5:/system/priv-app/SystemUI # ls -l SystemUI.apk
ls -l SystemUI.apk
-rw-r--r-- root root 3572757 2016-01-13 01:11 SystemUI.apk
[email protected]_m5c5:/system/priv-app/SystemUI # chown root.root SystemUI.apk && chmod 644 SystemUI.apk
chown root.root SystemUI.apk && chmod 644 SystemUI.apk
<
[email protected]_m5c5:/system/priv-app/SystemUI # ls -l SystemUI.apk
ls -l SystemUI.apk
-rw-r--r-- root root 3572757 2016-01-13 01:11 SystemUI.apk
[email protected]_m5c5:/system/priv-app/SystemUI #
Am I doing something wrong? Any other idea? Or can I put the original file back?
Thanks for any help with this
EDIT: I forgot to mention that I'm using now the sikke1's GoogleNow custom rom. That might be the reason?

wepecko said:
I tried your solution but I'm still without the buttons and notification bar...Am I doing something wrong? Any other idea? Or can I put the original file back?...EDIT: I forgot to mention that I'm using now the sikke1's GoogleNow custom rom. That might be the reason?
Click to expand...
Click to collapse
Hmmm, from your ls -l command, it appears that the file ownership and permission were already set correctly, and so there was no need to give the chown/chmod commands again, but doing so didn't hurt, and only confirmed things.
My M5C5 is also on sikke1's rom--I started with mirek190's v6.1 slim version for the Air 2/II even though I have an Air 3/III, and it worked pretty good except for some hiccups. And so that is why I ended up on sikke1's debloated M5C5 rom, too.
Have you rebooted? You may be nervous to do so, understandably, but adb is enabled by default in the sikke1 rom so even if the graphical UI does not pop up, you can still do manual triage via adb.
---------- Post added at 07:19 PM ---------- Previous post was at 06:53 PM ----------
One thought for the future--if you are going to do this manually, you should stage it appropriately to hopefully avoid issues. For example, copy the original to a backup with the -p option to preserve file properties while still leaving the in-use original completely intact (i.e. "cp -p SystemUI.apk SystemUI.apk.ORIGINAL)". Then copy your modded apk file(s) into the same directory, and make sure file ownership/permissions are set as per above. Then do another cp -p to replace the in-use original with the modded apk.
Here's my listing for the directory to show you what I mean. I have the original apk plus the 3-, 4-, and 5-button modded apks all in the same directory with the correct ownership/permissions set. I can quickly change to any config, for example, the 3-button config, with a single cp -p command, i.e. "cp -p SystemUI.apk.MODDED-3-BUTTON SystemUI.apk". And there is no downtime/hiccup because one file is immediately replaced by the other, and the ownership/permissions are already correctly set.
Code:
[email protected]_m5c5:/system/priv-app/SystemUI # ls -la
ls -la
-rw-r--r-- root root 3572761 2015-12-31 00:54 SystemUI.apk
-rw-r--r-- root root 3572757 2016-01-03 16:43 SystemUI.apk.MODDED-3-BUTTON
-rw-r--r-- root root 3572761 2015-12-31 00:54 SystemUI.apk.MODDED-4-BUTTON
-rw-r--r-- root root 3572764 2016-01-03 16:43 SystemUI.apk.MODDED-5-BUTTON
-rw-r--r-- root root 3604448 2015-12-31 00:21 SystemUI.apk.ORIGINAL
drwxr-xr-x root root 2015-08-26 23:06 x86
[email protected]_m5c5:/system/priv-app/SystemUI #
Again, since you have confirmed everything, I would suggest rebooting if you have not done that. As I said, even if the graphical UI does not come up, you can still get into adb for repairs. At the very worst, you might have to reflash the rom.
I'm not sure why you have had hiccups, but these modded apks are directly from the stock SystemUI.apk of a v1.04 M5C5 rom. I have the modded navigation_bar.xml files, and I can send those or just diffs vs. the original so you can see the few lines that I changed. But you'll see they are just like described by teramoto and the tsochen blog he pointed out.

Thanks verbage. I understand your backup procedure and admit it was a mistake to rewrite the file directly.
However im still trying to find solution to this. I did restart ofcourse, several times, but it didnt help at all. It was late yesterday so i didn't have much time to try different scenarios. Anyway tonight im going to try to update the file with 4 and 5 buttons versions and will see if I'll have any luck.
One more idea: would it be possible that the reason of this not working is that it might be in conflict with xposed apk already installed?
Sent from my XT890 using Tapatalk

wepecko said:
Anyway tonight im going to try to update the file with 4 and 5 buttons versions and will see if I'll have any luck... One more idea: would it be possible that the reason of this not working is that it might be in conflict with xposed apk already installed?Sent from my XT890 using Tapatalk
Click to expand...
Click to collapse
Hmmm, sorry to hear you are still having a problem. The 3-, 4-, and 5-button versions all work perfectly on my Air 3/III using sikke1's debloated M5C5 rom, and since you have the same device, any of the versions should also work for you.
Certainly, the 7-button stock original should work, too, and that is also included in the archive I posted.
Whether there may be a conflict with the xposed framework you have installed, I don't know as I do not have xposed installed on my Air 3/III.
Anyway, good luck with fix, and we'll wait to hear more.

I tried again from the start and everything is working perfect now. Tested succesfully all versions of SystemUI file.
I have no explanation on the troubles during the first try though. I did everything the same way as yesterday.
:victory:

wepecko said:
I tried again from the start and everything is working perfect now. Tested succesfully all versions of SystemUI file.
I have no explanation on the troubles during the first try though. I did everything the same way as yesterday.
:victory:
Click to expand...
Click to collapse
Great, glad to hear you have it working!

General [SOLVED] Can't copy Titanium Backup files to PC!!!

How can i copy TitaniumBackup folder to PC?
With my others Galaxy phones i always could copy through MTP but with my G998B/DS i can't.
I've used all the methods i found on the internet, such as:
Copy through MTP;
Compress TitaniumBackup's folder into a .zip file;
And through the ADB command
Code:
adb pull "/sdcard/TitaniumBackup" "D:\BACKUP"
Through MTP and compressing the folder i only get the .PROPERTIES files and through ADB i get this error message:
adb: error: failed to copy '/sdcard/TitaniumBackup/com.google.android.apps.photos-20210403-172138.tar.gz' to 'D:\BACKUP\TitaniumBackup\com.google.android.apps.photos-20210403-172138.tar.gz': remote open failed: Permission denied
If anyone can help me I would appreciate it.
SOLUTION: I entered in TWRP and i've been able to copy the folder.​

anyone know how to resolve this? i don't have TWRP so i can't use that work around.

fizmixa said:
anyone know how to resolve this? i don't have TWRP so i can't use that work around.
Click to expand...
Click to collapse
Do you get the same error as below?
MasterHack10 said:
adb: error: failed to copy '/sdcard/TitaniumBackup/com.google.android.apps.photos-20210403-172138.tar.gz' to 'D:\BACKUP\TitaniumBackup\com.google.android.apps.photos-20210403-172138.tar.gz': remote open failed: Permission denied
Click to expand...
Click to collapse
Maybe the "Permission denied" error is triggered by windows itself since you try to copy into the root of drive D. Maybe running your terminal (e.g. PowerShell) as admin will resolve your issue.
Else, @fizmixa , you could still manually boot (but not flash) twrp using fastboot, if your device isn't a Samsung device (I don't know if you can achieve this with Samsung).

Same here...Still couldn't find a solution.

I had the same problem. Looks like it's permission related. I fixed the problem by booting into TWRP -> Advanced -> File Manager, navigating to /sdcard/TitaniumBackup, clicking the blue folder with the tick and then selecting the chmod755 option.
@fizmixa, try and download Terminal Emulator for Android from the Play store and run:
Code:
chmod 755 /sdcard/TitaniumBackup/

It is about owner permission. Tar.gz files has a different owner from .properties. I don't have TWRP recovery because I use Android Emulator. How can I solve this problem?

Same issue here. Is this an Android 11 issue?

I'm struggling with the same issue .. No TWRP with me yet. So any clue how to get these files out of the device ?

JazonX said:
I'm struggling with the same issue .. No TWRP with me yet. So any clue how to get these files out of the device ?
Click to expand...
Click to collapse
They're protected due to security changes in newer versions of Android. I had the same issue on my last device, unable to pull /sdcard/android or /sdcard/TitaniumBackup using ADB for example.
You can try the SmartSwitch Windows app to take a backup of your phone?
Just a word of warning, I used SmartSwitch yesterday and although the backup was successful the call log backup zip was corrupt and couldn't be restored.

skymera said:
They're protected due to security changes in newer versions of Android. I had the same issue on my last device, unable to pull /sdcard/android or /sdcard/TitaniumBackup using ADB for example.
You can try the SmartSwitch Windows app to take a backup of your phone?
Just a word of warning, I used SmartSwitch yesterday and although the backup was successful the call log backup zip was corrupt and couldn't be restored.
Click to expand...
Click to collapse
Hey, I just managed to sort it out.
Go to Titanium Backup, Preferences, Backup location - and click the below selected option;
Select the external backup storage option, and allow access to it.
It was weird how this caused the PC copying / internal copying to fail .. This sorted the problem for good.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

JazonX said:
Hey, I just managed to sort it out.
Go to Titanium Backup, Preferences, Backup location - and click the below selected option;
Select the external backup storage option, and allow access to it.
It was weird how this caused the PC copying / internal copying to fail .. This sorted the problem for good.
Click to expand...
Click to collapse
I'm not rooting my S21U but this is good to know for the future, tks.

I'm also having this problem with Android 11 on Pixel 5a, adb: error: failed to copy ...: remote open failed: Permission denied
There isn't a TWRP for this device yet so I can't try that solution. I tried JazonX's idea but it hasn't helped. The problem seems to be that the tar.gz files are owned by media_rw user instead of u0_a252 like the other files. I tried using 'adb shell', "su -" and then "chmod 755 /sdcard/TitaniumBackup/" but it doesn't actually change any of the permissions. Also tried commands such as "chown u0_a252 *.tar.gz" but it doesn't actually change anything. I tried to write to TB support too but no response yet. Any other ideas?

Aha! I found a solution! use "adb shell" then "su -" then navigate to "cd /data/media/0/TitaniumBackup". Now commands like "chown u0_a252 *" actually work and I was able to get full backup of /sdcard/TitaniumBackup with "adb pull". Crazy Android file system!

scarlion said:
Aha! I found a solution! use "adb shell" then "su -" then navigate to "cd /data/media/0/TitaniumBackup". Now commands like "chown u0_a252 *" actually work and I was able to get full backup of /sdcard/TitaniumBackup with "adb pull". Crazy Android file system!
Click to expand...
Click to collapse
Wow! It worked for me! Thanks very much

scarlion said:
Aha! I found a solution! use "adb shell" then "su -" then navigate to "cd /data/media/0/TitaniumBackup". Now commands like "chown u0_a252 *" actually work and I was able to get full backup of /sdcard/TitaniumBackup with "adb pull". Crazy Android file system!
Click to expand...
Click to collapse
Did you do this via windows command prompt or within a terminal program on the android device?
As I can't seem to get it to work on Windows CMD
Code:
C:\platform-tools>adb shell
redfin:/ $ su -
redfin:/ # cd /storage/emulated/0/TitaniumBackup
1|redfin:/storage/emulated/0/TitaniumBackup # chown u0_a252 *
redfin:/storage/emulated/0/TitaniumBackup # adb pull "/storage/emulated/0/TitaniumBackup" "D:\Temp"
: adb: inaccessible or not found
127|redfin:/storage/emulated/0/TitaniumBackup # adb pull /storage/emulated/0/TitaniumBackup
: adb: inaccessible or not found
127|redfin:/storage/emulated/0/TitaniumBackup #

pennywaltz said:
Code:
redfin:/storage/emulated/0/TitaniumBackup # adb pull "/storage/emulated/0/TitaniumBackup" "D:\Temp"
: adb: inaccessible or not found
127|redfin:/storage/emulated/0/TitaniumBackup # adb pull /storage/emulated/0/TitaniumBackup
: adb: inaccessible or not found
127|redfin:/storage/emulated/0/TitaniumBackup #
Click to expand...
Click to collapse
I think you have to exit the "adb shell" for further adb commands to work, as "adb" is in your C:\platform-tools directory

scarlion said:
I think you have to exit the "adb shell" for further adb commands to work, as "adb" is in your C:\platform-tools directory
Click to expand...
Click to collapse
I'm having the same problem on my Pixel 5 ("redfin"). It has nothing to do with adb. Without adb running at all, I can go to a terminal emulator on the device and run the following commands ...
Code:
redfin:/ $ su -
redfin:/ # cd /sdcard/TitaniumBackup
redfin:/sdcard/TitaniumBackup # chown u0_a362 *
No error is reported. However, after doing this, all the files previously owned by rw_media are still owned by rw_media. In other words, for those files, the chown command is effectively a no-op, even after an su to root.
Google strikes again with its "We think we're much smarter than you, and we're going to 'protect' you from yourself, whether you like it or not!" attitude.

HippoMan said:
Google strikes again with its "We think we're much smarter than you, and we're going to 'protect' you from yourself, whether you like it or not!" attitude.
Click to expand...
Click to collapse
I know right, it's pretty annoying... but even with root, I think you have to specifically modify the data from the /data/media/0 directory instead, i.e.:
redfin:/ $ su -
redfin:/ # cd /data/media/0/TitaniumBackup
redfin:/data/media/0/TitaniumBackup # chown u0_a362 *
Does that work?

scarlion said:
I know right, it's pretty annoying... but even with root, I think you have to specifically modify the data from the /data/media/0 directory instead, i.e.:
redfin:/ $ su -
redfin:/ # cd /data/media/0/TitaniumBackup
redfin:/data/media/0/TitaniumBackup # chown u0_a362 *
Does that work?
Click to expand...
Click to collapse
Yep, that worked for me! Thanks! It seems they have put some stupid userland file system which mirrors files from /data:
/dev/fuse on /storage/emulated type fuse (rw,lazytime,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other)