Develop Bugs

ADB: Permission denied...no matter what i do!!!

OK...I'm beginning to think that rooting is not for me!!!! Getting a bit frustrated!!!
OK, so I installed SDK on my pc (Win XP Ver 2002 SP3), and I cannot get it recognize the device.
I tried the guide for dummies here on XDA, and I follow all the indications, server starts up, I can kill it too....but every time I try to run it I get:
"error: device cannot be found"
The line that I am writing is as follows:
Code:
c:\android-sdk-windows\tools>adb shell
and I get the error above.
When I try to see if devices are connected, and Use this:
Code:
c:\android-sdk-windows\tools>adb devices
I get:
"List of Devices attached", but there is no list!!!!!
But I can see the SDCARD from my computer....I can access the files...
Maybe I can try to pull instead of push, but I'm not sure how that would be written (line wise), not if will work.
BTW...I have never done anything like this on android....very new to this!!!!
umm.. HELP!!!
OK changed pc's,....on this one it does recognize the device, but does not allow me to push anything.....when i try:
Code:
adb push su /sdcard/su
I get adb: permissions denied
------
I tried su +, and that got me to the # prompt. So I tried typing
Code:
# adb push su /sdcard/su
and I get adb: not found???
Running out of options here!
...
Thanks!

I think you are mounting the sdcard. You don't want to do that. Just connect your phone to the computer and run ADB. Don't click "USB Connected. Select to copy files to/from your computer" on your phone.

funkeee said:
I think you are mounting the sdcard. You don't want to do that. Just connect your phone to the computer and run ADB. Don't click "USB Connected. Select to copy files to/from your computer" on your phone.
Click to expand...
Click to collapse
Funkeeeeeee thank you for the reply.
OK...I am not getting an option when I connect to the pc..on the one I get it, I shose do nothing. I have also disabled mass storage on the device once loaded, adn I get the same error. Here is some of the code that I get thorught the PC's terminal:
C:\>cd android-sdk-windows\tools
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT09YR200737 device
C:\android-sdk-windows\tools>adb shell
$ adb push su /sdcard/su
adb push su /sdcard/su
adb: permission denied
$ adb kill-server
adb kill-server
adb: permission denied
$
Click to expand...
Click to collapse
Notice that once I get the initial permission denied, the terminal seems to get locked up on that no matter what I type....see above...
Anything else to try??? AM I missing something here?

That's fine. There are a few things I can suggest for you to try..
First, I want you to enable USB debugging on your phone by going to Settings > Applications > Development and check that first option.
Then connect the phonoe, but don't use 'adb shell' before pushing files. It should look like this:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Funkz>cd c:\g2
c:\g2>adb pull /system/build.prop
501 KB/s (3596 bytes in 0.007s)
c:\g2>
Click to expand...
Click to collapse
If you are trying to run it from within adb shell, it will spit back 'adb: not found.' That should do fix it for you.
If it does not, go to Control Panel > System > Advanced > Environment Variables. Then click on Path and Edit, then ";C:\android-sdk-windows\tools\" at the very end and try again.
By the way, you don't have to run adb from the installation directory. After adding the path I just mentioned, you should be able to run it from anywhere.

funkeee said:
That's fine. There are a few things I can suggest for you to try..
First, I want you to enable USB debugging on your phone by going to Settings > Applications > Development and check that first option.
Then connect the phonoe, but don't use 'adb shell' before pushing files. It should look like this:
If you are trying to run it from within adb shell, it will spit back 'adb: not found.' That should do fix it for you.
If it does not, go to Control Panel > System > Advanced > Environment Variables. Then click on Path and Edit, then ";C:\android-sdk-windows\tools\" at the very end and try again.
By the way, you don't have to run adb from the installation directory. After adding the path I just mentioned, you should be able to run it from anywhere.
Click to expand...
Click to collapse
Thanks.....I finally can run it without having to type the entire path!!!! That was great help!!!
AS for the permission denied.....still having that issue! The one thing I didn't understand was when you changed the path to >g2.....what do you mean???? path to be g2?
Thanks again for the help!
Just a note...I am trying to do this post OTA, which I downloaded, never got the push...Would having the OTA have any effect on this? DO I need to consider reverting to stock and trying from there? If so how? run recovery?
Dude thanks for the help!

did you try typing SU? IMO you cant tamper with ADB Shell if you dont have su access so try typing down SU to ask for permission.

Alright first things first. ADB requires special drivers to work. Which is probably why it didn't work on the original PC. If you download the PDANet client on the PC that you need to do adb it will install the necessary drivers and you can uninstall the program without losing the drivers.
Another ADB requirement is to enable USB Debugging. MENU>Settings>Applications>Development and check the USB Debugging Box.
I don't know about anyone else but with my phone will automount the card. It is recommended to pull down the notification bar and make sure that your SD card isn't mounted.
You need to navigate your command prompt to whatever folder you keep ADB.exe for me
Code:
C:\Users\etnie>cd C:\Users\etnie\Downloads\G2\Android\tools
for me this returns
Code:
C:\Users\etnie\Downloads\G2\Android\tools>
to confirm this
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb devices
I won't post all the code but it should start the daemon successfully and list your device.
to be able to push files to your phone they also need to be in the same folder as the ADB.exe ie the tools folder. of course you can push it from any folder if you type the full path
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb push C:\Users\etnie\Downloads\G2\bootanimation.zip /data/local
the above code would push the bootanimation.zip from my G2 folder located in my Downloads folder to /data/local on the phone. changing the boot screen animation when you turn on the phone. I actually have the BIOS one. Because I am huge nerd lol. Moving on...
I think I covered everything necessary....If you are still having problems either PM me or reply here.

Thanks guys for the replays...here are some comments...
Acid_Wir3 said:
did you try typing SU? IMO you cant tamper with ADB Shell if you dont have su access so try typing down SU to ask for permission.
Click to expand...
Click to collapse
I have tried SU, and it does grant access, BUT!!!! so here is what happens...
I get to .....\tools> adb shell ... then i get.... the $ prompt. At this point I type $su .... then my prompt changes from $ to #. I understand that it should be $ # In any case once I get to # it says adb: not found code looks like this:
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\carlos>cd\
C:\>adb shell
$ su
su
# adb push su /sdcard/su
adb push su /sdcard/su
adb: not found
#
BTW, the path has been predfined to C:\android-sdk-windows\tools\
Not sure how to navigate from #prompt
RuncaProfundus said:
1Alright first things first. ADB requires special drivers to work. Which is probably why it didn't work on the original PC. If you download the PDANet client on the PC that you need to do adb it will install the necessary drivers and you can uninstall the program without losing the drivers.
2Another ADB requirement is to enable USB Debugging. MENU>Settings>Applications>Development and check the USB Debugging Box.
3I don't know about anyone else but with my phone will automount the card. It is recommended to pull down the notification bar and make sure that your SD card isn't mounted.
4 You need to navigate your command prompt to whatever folder you keep ADB.exe for me
Code:
C:\Users\etnie>cd C:\Users\etnie\Downloads\G2\Android\tools
for me this returns
Code:
C:\Users\etnie\Downloads\G2\Android\tools>
to confirm this
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb devices
I won't post all the code but it should start the daemon successfully and list your device.
to be able to push files to your phone they also need to be in the same folder as the ADB.exe ie the tools folder. of course you can push it from any folder if you type the full path
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb push C:\Users\etnie\Downloads\G2\bootanimation.zip /data/local
the above code would push the bootanimation.zip from my G2 folder located in my Downloads folder to /data/local on the phone. changing the boot screen animation when you turn on the phone. I actually have the BIOS one. Because I am huge nerd lol. Moving on...
I think I covered everything necessary....If you are still having problems either PM me or reply here.
Click to expand...
Click to collapse
Runca thanks for the detailed reply....going in order here:
1 - I did and I still have pdanet isntalled
2 - it's been like that since the first day I got the phone.
3 - How do I ensure??? you are talking about from the phone....I should turn off USB Storage? Will try this one.
UPDATE: tried unmounting and re running without success....
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\carlos>cd\
C:\>adb shell
$ adb push su /sdcard/su
adb push su /sdcard/su
adb: permission denied
$
4 - It's pretty much what I have. Other that I'm not running su before doing so......
Any thoughts?

Crey23 said:
AS for the permission denied.....still having that issue! The one thing I didn't understand was when you changed the path to >g2.....what do you mean???? path to be g2?
Click to expand...
Click to collapse
The "g2> " bit is just his command prompt. He's changed directory to one called "g2" on his phone but that's nothing to do with how adb works etc (just that if he pushes or pulls files then that'll be the current directory on the PC for that).

Crey23 said:
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\carlos>cd\
C:\>adb shell
$ su
su
# adb push su /sdcard/su
adb push su /sdcard/su
adb: not found
#
Click to expand...
Click to collapse
Those "adb push" commands should be done from your PC's command prompt, not from within an Android shell prompt on your phone.
"adb shell" starts a command shell on the phone. Which is fine for doing some stuff. But "adb" commands won't work because now you're issuing them to your phone, not your PC.

steviewevie said:
Those "adb push" commands should be done from your PC's command prompt, not from within an Android shell prompt on your phone.
"adb shell" starts a command shell on the phone. Which is fine for doing some stuff. But "adb" commands won't work because now you're issuing them to your phone, not your PC.
Click to expand...
Click to collapse
Thanks Steve.....that makes a lot of sense, and in part why i am a bit lost here....but knowing that....how can I get to "push" things to my phone?

Don't run the adb shell command. That takes you into the phone's prompt. Any commands you run from adb shell with $ or # are run within the phone. You want to run adb push from command prompt. Look at my previous post. It should look like:
C:/>adb push ...
not
#adb push...
Sent from my HTC Vision using XDA App

Funkeee,x thank you I will try that as soon as I can.
funkeee said:
Don't run the adb shell command. That takes you into the phone's prompt. Any commands you run from adb shell with $ or # are run within the phone. You want to run adb push from command prompt. Look at my previous post. It should look like:
C:/>adb push ...
not
#adb push...
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Sent from my T-Mobile G2 using XDA App

Finally progress
Guys thank you for your help!!!!!
I was finally able to push all the files to the phone. Now my problem has changed..., still dealing with Permission denied....when executing rage I get a buch of errors, please see image:
Code:
$ $su
# /data/local/tmp/rage
I get this.....
{
"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"
}
I then figured that since I was temp rooted through Visionary r10, that was the reason for the errors above. I then proceeded to reboot without temp-rooting.
When I come up to the terminal I get:
Code:
export PATH=/data/local/bin:$PATH
$ $su
su: permission denied
$
SO if I understand this correctly, I need NOT be temp-rooted in order to run rage, but if I'm not temp-rooted, I don't have permissions to get to execute rage....there a chicken and egg story here somewhere! lol
Can I use a hybrid of the visionary temp root and perm root in that post?

From what I recall you need to uninstall visionary and reboot prior to using the rage method.
Sent from my HTC Vision using XDA App

Thanks funkeee...I will try in the morning.
But part of the problem is that without visionary I cannot get su access to run any of this. I'll backup VIS r10 before removing, and try again.
I post my results...goodnight and thanks!
funkeee said:
From what I recall you need to uninstall visionary and reboot prior to using the rage method.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Sent from my T-Mobile G2 using XDA App

I looked at the rage instructions and the prompt is misleading. You may forgetting to use chmod to change permssions. I've put my version of the instructions (just the start).
Uninstall visionary, reboot and from command prompt on your pc, navigate to the folder where you have these files and run:
c:/> adb push su /sdcard/su
c:/> adb push Superuser.apk /sdcard/Superuser.apk
c:/> adb push rage /data/local/tmp/rage
c:/> adb push busybox /data/local/tmp/busybox
c:/> adb push root /data/local/tmp/root
c:/> adb shell chmod 0755 /data/local/tmp/*
Don't forget the last entry, which changes the permissions.
Then on your phone, open terminal and put in:
$ /data/local/tmp/rage
It will say Forked Childs...
Then Menu > Reset Term. It will close, then launch terminal again, it will force close and then launch it again and you will have rage root.
If you get to there, you're in good shape. You can then follow those instructions to to push hboot and wpthis. Be careful with the dd command and be sure you have it exactly right. There are no do-overs with 'dd'.
http://forum.xda-developers.com/showthread.php?t=834228

Thanks man I will try it shortly.

funkeee said:
I looked at the rage instructions and the prompt is misleading. You may forgetting to use chmod to change permssions. I've put my version of the instructions (just the start).
Uninstall visionary, reboot and from command prompt on your pc, navigate to the folder where you have these files and run:
c:/> adb push su /sdcard/su
c:/> adb push Superuser.apk /sdcard/Superuser.apk
c:/> adb push rage /data/local/tmp/rage
c:/> adb push busybox /data/local/tmp/busybox
c:/> adb push root /data/local/tmp/root
c:/> adb shell chmod 0755 /data/local/tmp/*
Don't forget the last entry, which changes the permissions.
Click to expand...
Click to collapse
Up to here I am fine.
funkeee said:
Then on your phone, open terminal and put in:
$ /data/local/tmp/rage
It will say Forked Childs...
Then Menu > Reset Term. It will close, then launch terminal again, it will force close and then launch it again and you will have rage root.
If you get to there, you're in good shape. You can then follow those instructions to to push hboot and wpthis. Be careful with the dd command and be sure you have it exactly right. There are no do-overs with 'dd'.
http://forum.xda-developers.com/showthread.php?t=834228
Click to expand...
Click to collapse
But is with this part that I have issues with......
I uninstalled VISONary as suggested, and I got the same result as before.....error, error, error.....permission denied! Basically without visionary and su I cannot get access to the run rage. I gave me this error:
Code:
$ /data/local/tmp/rage
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
mount: Operation not permitted
mkdir failed for /system/xbin, Read-only file system
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
Unable to chmod /system/xbin/busybox: no such file or directory
/data/local/tmp/rage: /data/local/tmp/busybox: not found
cp: Permission denied
cp: Permission denied
Unable to chmod /system/xbin/su: no such file or directory
Mount: Operation not permitted
$
SO as i interpret this as I dont have the rights or permission to run the rage script. What puzzles me is the fact the it cannot "mount" the sdcard...after running this, I cannot take a picture (screenshot) bcs it does not recognize the sdcard. I have to Reboot.
Any ideas?
Thanks!

Crey23 said:
Up to here I am fine.
But is with this part that I have issues with......
Code:
$ /data/local/tmp/rage
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
mount: Operation not permitted
mkdir failed for /system/xbin, Read-only file system
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
Unable to chmod /system/xbin/busybox: no such file or directory
/data/local/tmp/rage: /data/local/tmp/busybox: not found
cp: Permission denied
cp: Permission denied
Unable to chmod /system/xbin/su: no such file or directory
Mount: Operation not permitted
$
Click to expand...
Click to collapse
I think there's something majorly wrong here. Funny, I saw someone else with a similar problem recently. It looks like when you're running "rage" it's actually running the "root" script that you use at a later stage, and not "rage" at all. Double check what you've got, I think "rage" is a binary and not a script. Are you sure you didn't push "root" to "rage" ?

[Q] Rooting Problem Please Help

so i have adb setup and have it adb.exe in the gfree folder so when i go to command prompt im permission denied after
su
cd /data/local
chmod 777 gfree
./gfree -f
sync
Click to expand...
Click to collapse
what am i doing wrong
heres a pic
{
"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"
}
after cd /data/local it says permission denied what do i do?

zbrah said:
so i have adb setup and have it adb.exe in the gfree folder so when i go to command prompt im permission denied after
what am i doing wrong
heres a pic
after cd /data/local it says permission denied what do i do?
Click to expand...
Click to collapse
are you working from this page? http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
why are you cd'ing to data/local? what's in that folder? in the other thread you said you had your files in gfree_02??

http://forum.xda-developers.com/showthread.php?t=855764
im using this method

why would you cd to data/local? you need to put files there, not pull files from there...

martonikaj said:
why would you cd to data/local? you need to put files there, not pull files from there...
Click to expand...
Click to collapse
what should i do then
what commands do i do thanks for the help i appreciate it

On your computer's terminal/command line, navigate to where the gfree file is, and then...
Code:
adb push gfree /data/local
adb shell
This copies gfree to your phone, then puts you in your phone's terminal. Then do this:
Code:
su
cd /data/local
chmod 777 gfree
./gfree -f
sync
Click to expand...
Click to collapse
thats what is says on this thread http://forum.xda-developers.com/showthread.php?t=855764

zbrah said:
thats what is says on this thread http://forum.xda-developers.com/showthread.php?t=855764
Click to expand...
Click to collapse
Aren't you supposed to be running the commands:
Code:
su
cd /data/local
chmod 777 gfree
./gfree -f
sync
In terminal emulator on your phone? from what I remember this is the way I did it. Could be mistaken by the wording though... I just remember using ADB to push all the files then just running terminal emulator on my phone instead of running a shell. Worth a try if you can't get ADB shell to work properly.

zbrah said:
so i have adb setup and have it adb.exe in the gfree folder so when i go to command prompt im permission denied after
what am i doing wrong
heres a pic
after cd /data/local it says permission denied what do i do?
Click to expand...
Click to collapse
From the look of this you still have a $ sign this means you dont have root permission, it should be a # sign after typing su in adb shell . Looks like your temp root didn't work or your not allowing root user permission on your phone right after typing su in adb shell.

The guide you are trying to use specifically says "So we're assuming you've permarooted already and usb debugging is on" but from the thread title, it sounds like you are trying to get permanent root. The guide does not work if you don't already have root.
You should probably use the guide in the Wiki linked to earlier.

The problem is the very first command you type into the command prompt on your phone, i.e. "su", is giving you "permission denied". So as others have said, you are not getting root permissions. If you have rooted previously then the "Superuser" app pops up and asks for permissions the first time you try "su", check it's not coming up with a box on your phone which you're failing to see (then it times out after a few seconds and says "permission denied").

Full HTC Desire HD (sense 3.0/android 2.3.5) guide to root, S-OFF/Sim Unlock

I have moved this post to the Desire HD Android Development section (http://forum.xda-developers.com/showthread.php?t=2221039) if a mod wants to delete this thread, that would be great.
I probably won't ever update this.
THIS GUIDE IS MAINLY this guide (http://tau.shadowchild.nl/attn1/?cat=6) SIMPLIFIED TO SOME EXTENT. with parts that werent included in the guide added to the guide and resources added to the ace-tools folder that would have to be downloaded separately.
PREFACE:
Download this and unzip it somewhere (reccommend C:\ root folder): http://www.multiupload.nl/MXW371YT87
Full HTC Desire HD guide to root, S-OFF/Sim Unlock
1. Unlock the bootloader at http://htcdev.com/bootloader/
2. Copy your Unlock_code.bin file that you got in the email to the ace-tools folder.
3. Download rooted stock rom: http://www.multiupload.nl/20T9R21IGY
(link to rom thread: http://forum.xda-developers.com/showthread.php?t=1382235&highlight=rooted+stock )
copy the ROM zip file to your SD card.
4. Install recovery image:
Open cmd and type:
• cd <the directory of the ace-tools folder> (eg cd C:\ace-tools)
Ensure your phone is connected to your PC and then boot into bootloader, then navigate to fastboot.
In cmd:
• fastboot recovery1.img
5. boot into recovery through bootloader and Install the ROM you placed on the SD card, (via install zip fileselect the rom zip)
6. Reboot the phone, ensure the rom is working fine and you have root access you can test this by turning on usb debugging then:
• Adb shell
• Su
You should see the $ turn into a #. If this happens, congrats you have root access.
Then type this:
• Exit
Then again:
• Exit
Then:
• Adb push boot.img /data/local/tmp
• adb shell dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
• adb pull /data/local/tmp/boot.img
• adb push goldcard /data/local/tmp
• adb shell chmod 775 /data/local/tmp/goldcard
• adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid
take note of the string of numbers and letters that appear.
then:
• adb shell /data/local/tmp/goldcard -c <string of numbers and letters should go here> -o /data/local /tmp/goldcard.img
• adb shell dd if=/data/local/tmp/goldcard.img of=/dev/block/mmcblk1
• adb push misc_version /data/local/tmp
• adb shell chmod 775 /data/local/tmp/misc_version
• adb shell /data/local/tmp/misc_version -s 1.11.111.1
7. If this is all fine boot into bootloader again.
From bootloader go to fastboot.
Go back to the cmd window on your PC from earlier, type in:
• Fastboot oem lock
Then type:
• fastboot oem rebootRUU
• fastboot flash zip firmware.zip
• fastboot reboot-bootloader
unlock the bootloader again using the Unlock_code.bin you got from HTC:
• fastboot flash unlocktoken Unlock_code.bin
then flash boot.img in ace-tools folder:
• fastboot flash boot boot.img
next:
• fastboot flash recovery recovery.img
8. boot to recovery again then:
• adb push gfree /tmp/
• adb shell chmod 775 /tmp/gfree
• adb shell /tmp/gfree -f
reboot to bootloader and you should see it says S-OFF at the top of the screen, if It does congrats your done.
VICTORY:
{
"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"
}
help me out if you feel like it by signing up to dropbox with my refferal link:
Always have your stuff when you need it with @Dropbox. Sign up for free! http://db.tt/G8qfL77X

"Couldn't mount SD card" rooting Nexus 7 (2013)

Hi,
I have been trying to root a Nexus 7, and I always end up having the problem that the recovery cannot mount the sdcard. I have wiped the entire device several times and tried installing different google stock images: marshmallow (6.0.1 MMB29O and MMB29Q) and lollipop (5.1.1 LMY48T). I tried installing Cyanogenmod, but couldn't install it without access to the sdcard from the recovery. I also tried different recovery methods.
This is the bootloader loading screen
{
"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"
}
The stock recovery function failing to mount:
Team Win Recovery:
And ClockworkMod Recovery:
I also tried other versions of those recovery tools, but with the same result. I have no problem accessing the SD card from the Android OS, and accessing the device in USB mode was not a problem either.
It would be great if someone knew what the problem is. I have been searching, but couldn't find anything that helped.
Thanks for the help.

Aitor86 said:
I have no problem accessing the SD card from the Android OS
Click to expand...
Click to collapse
Android works fine but recovery does not? Unusual.
Please boot TWRP, run the following and post the log file:
Code:
adb shell blkid > data.txt
adb shell cat proc/partitions >> data.txt
adb shell head /sys/block/mmcblk0/device/* >> data.txt
adb shell dmesg >> data.txt
adb shell cat /tmp/recovery.log >> data.txt

k23m said:
Android works fine but recovery does not? Unusual.
Please boot TWRP, run the following and post the log file:
Code:
adb shell blkid > data.txt
adb shell cat proc/partitions >> data.txt
adb shell head /sys/block/mmcblk0/device/* >> data.txt
adb shell dmesg >> data.txt
adb shell cat /tmp/recovery.log >> data.txt
Click to expand...
Click to collapse
Hi, thanks for the help. This is the output of that code:
pastebin.com/fP5q3DPE

Aitor86 said:
Hi, thanks for the help. This is the output of that code: pastebin.com/fP5q3DPE
Click to expand...
Click to collapse
Hi mate, you wrote "I have no problem accessing the SD card from the Android OS" but the reality is "a few weeks ago I had no problem" - correct?
Your log:
Code:
mmc0: unrecognised EXT_CSD revision 7
mmc0: error -22 whilst initialising MMC card
Try the latest TWRP first, OK?

k23m said:
Hi mate, you wrote "I have no problem accessing the SD card from the Android OS" but the reality is "a few weeks ago I had no problem" - correct?
Your log:
Code:
mmc0: unrecognised EXT_CSD revision 7
mmc0: error -22 whilst initialising MMC card
Try the latest TWRP first, OK?
Click to expand...
Click to collapse
I have no idea what the problem was, but using the latest TWRP (3.0) did the trick. The sdcard is visible, and I can access any file I want from there.
Just to answer your question, the SD card was still accessible from the Android OS, so summing up, the only recovery tool that worked was the latest version of TWRP.
Thanks for the help!!!! I thought I was using the appropriate version, and I had spent more time than I would admit trying to get this working.

Hi
Sent from my iPhone using Tapatalk

Working viper4a with easy steps.

STEP 1: Root the phone with the link provided in the op7t forum.Now you have magisk.
STEP 2: Install the SE LINUX SWITCH APP link: https://labs.xda-developers.com/store/app/com.ibuprophen.selinux
STEP 3: change selinux to permissive. now to go settings-battery optimisation-change the selinux app to not optimised.turn off googleplay protect.
STEP 4:now all you need is a modded stock recovery. download it from here. link: https://drive.google.com/file/d/1S-1Np5CFx9z98Ntp8vUTWFU1ksqIeBSN/view
STEP 5:now go to fastboot and flash the stock modded recovery. CODE: fastboot flash recovery RECOVERYNAME.zip now you have adb enabled stock recovery.
STEP 6:now boot to stock recovery while connected to pc and type adb devices in cmd. it should go to adb. if yes proceed to next step.
STEP 7:now install viper4fx from magisk. phone will reboot. go into viper4a app and install drivers. it will go to fastboot ofcourse.
STEP 8: boot to recovery from fastboot. then just type in the following commands/
1. adb shell
2. cd data
3. cd adb
4. cd modules
5. cd ViPER4AndroidFX
6. rm post-fs-data.sh
7. exit
STEP 8: phone will now boot. again go to viper4a app and install drivers and repeat step 8 again.
VOILA now you have viper fully working on our beloved op7t.
NOTE: disable bluetooth absolute volume for bluetooth to work in v4a.
Dont try installing viper in 10.3.1. you will be stuck in fastboot. so instead download 10.3.0 fastboot image and flash it. then follow the above steps and update the phone by the following.
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- In Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot. Root, viper and all the magisk modules will be retained. Give a thumbsup

Anyone tried this?

VIZT said:
Anyone tried this?
Click to expand...
Click to collapse
perfectly working in mine.
{
"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"
}

why do i need always to set os to permissive?

Snake.s9 said:
why do i need always to set os to permissive?
Click to expand...
Click to collapse
Permissive sets SELinux to behave in a different way than Enforcing(default), which is required for V4A to work.
As far as technical details, I have no idea.

Permissive is dangerous.

Batfink33 said:
Permissive is dangerous.
Click to expand...
Click to collapse
Why ? Explain more please

Snake.s9 said:
Why ? Explain more please
Click to expand...
Click to collapse
Leaves the kernel open to any malicious apps that want to take control of your phone.

Snake.s9 said:
why do i need always to set os to permissive?
Click to expand...
Click to collapse
permissive mode allows some features to run on some instances which are not allowed in enforcing mode. like for example debugging.

Apparently its not meant for me to have viper. Modded recovery won't even work.

i tired it says no such file or directory on rm command
had to load app and install driver first

shorty1993 said:
Apparently its not meant for me to have viper. Modded recovery won't even work.
Click to expand...
Click to collapse
not working in the sense? not able to flash or adb isnt responding?

chwads2k8 said:
i tired it says no such file or directory on rm command
had to load app and install driver first
Click to expand...
Click to collapse
yes. postfs file will be generated only after installing the app. it is necessary to remove it for the phone to boot and for viper to work aswell.

I got to step five say
C:\adb>adb shell
error: device not found

AboNaya said:
I got to step five say
C:\adb>adb shell
error: device not found
Click to expand...
Click to collapse
Why would you type adb shell in fastboot?
Read the instructions again
Sent from my OnePlus7TPro using XDA Labs

Lossyx said:
Why would you type adb shell in fastboot?
Read the instructions again
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
C:\Users\MY>adb shell
OnePlus7T:/ $ cd data
cd data
OnePlus7T:/data $ cd adb
cd adb
/system/bin/sh: cd: /data/adb: Permission denied
Thank you very much for responding to me. I have taken the steps back to step 8 and the phone, of course, does not start the problem now, it is as follows What is the solution to overcoming this problem, please, I am a fan of this program and after moving to OnePlus SevenT I could not run it for more than ten to twenty attempts

AboNaya said:
C:\Users\MY>adb shell
OnePlus7T:/ $ cd data
cd data
OnePlus7T:/data $ cd adb
cd adb
/system/bin/sh: cd: /data/adb: Permission denied
Thank you very much for responding to me. I have taken the steps back to step 8 and the phone, of course, does not start the problem now, it is as follows What is the solution to overcoming this problem, please, I am a fan of this program and after moving to OnePlus SevenT I could not run it for more than ten to twenty attempts
Click to expand...
Click to collapse
Ah.
After typing adb shell and your prompt shows:
OnePlus7T:/ $
type: su <press enter>
Prompt should now look like this:
OnePlus7T:/ #
Now you have root access and can cd into /data/adb/.

not working
adb shell
# cd data
cd data
# cd adb
cd adb
/system/bin/sh: cd: /data/adb: No such file or directory
what to do now?

grandpajiver said:
Ah.
After typing adb shell and your prompt shows:
OnePlus7T:/ $
type: su <press enter>
Prompt should now look like this:
OnePlus7T:/ #
Now you have root access and can cd into /data/adb/.
Click to expand...
Click to collapse
C:\adb>adb shell
# su
su
/system/bin/sh: su: inaccessible or not found
#

AboNaya said:
C:\adb>adb shell
# su
su
/system/bin/sh: su: inaccessible or not found
#
Click to expand...
Click to collapse
Don't type su, just adb shell and proceed
Sent from my OnePlus7TPro using XDA Labs