Database Develop

can anybody help me with this command line

this used to work when i did on my mytouch
cd /data/app-private/
ls
cp */sdcard
when i enter the command on my nexus i get error
cp: cant stat '*': no such file or directory
can some body please tell me how properly write the comand for a nexus one

What exactly are you trying to accomplish with the command? Are you trying to copy everything from /data/app-private/ onto your microSDHC card? If so, I would just (as root), do:
cp /data/app-private/* /sdcard
Make sure that you su to root before issuing the command, or you will get a permission denied error.

doesnt work either

What are you trying to do?
Can you link the place where you originally saw this command?

napoleontheruler said:
cd /data/app-private/
ls
cp */sdcard
Click to expand...
Click to collapse
so from the command and the errors you get using your and nathanzachary's version it looks like
a) your missing a space between * and /
b) you need root access to read anything in /data
perhaps you can tell us what the output of the "ls" is and maybe exchange that with an "ls -al" ? that would show us the access rights. please just copy the whole session.

FloOGB said:
so from the command and the errors you get using your and nathanzachary's version it looks like
a) your missing a space between * and /
b) you need root access to read anything in /data
perhaps you can tell us what the output of the "ls" is and maybe exchange that with an "ls -al" ? that would show us the access rights. please just copy the whole session.
Click to expand...
Click to collapse
i know about the space typo. "ls" shows all of the protected apps on your device. this command line would basically let you save any protected app to the devices sdcard. in a nut shell paid apps for free but it wont work on my nexus. can anyone figure out what the command line should be for a nexus.
i am running cm 5.0.5.3 if it helps any

"ls" is the same as "dir" in windows. it just lists the content of the directory you changed into with "cd". thats why we need to see the complete output of your console session. that includes your input, the output and the error messages. this is the reason i wanted to see an "ls -al" to see the access rights of that directory. if you dont want us to see the aps than please cut out the names, but leave all dots
this is up till know a purley "linux" problem, we just need the right data.
EDIT: and do an "id" please, just after the ls -al, copy that output as well.

FloOGB said:
"ls" is the same as "dir" in windows. it just lists the content of the directory you changed into with "cd". thats why we need to see the complete output of your console session. that includes your input, the output and the error messages. this is the reason i wanted to see an "ls -al" to see the access rights of that directory. if you dont want us to see the aps than please cut out the names, but leave all dots
this is up till know a purley "linux" problem, we just need the right data.
EDIT: and do an "id" please, just after the ls -al, copy that output as well.
Click to expand...
Click to collapse
drwxrwx--x 1 system system 2048 Mar 22 21:51
drwxrwx--x 1 system system 2048 Mar 25 18:04
i dont know if that will help

FloOGB said:
we need to see the complete output of your console session
Click to expand...
Click to collapse
something like
Code:
* daemon not running. starting it now *
* daemon started successfully *
# bash
bash-4.1# id
uid=0(root) gid=0(root)
bash-4.1# cd /data/app-private/
bash-4.1# ls -al
drwxrwx--x 1 system system 2048 Apr 1 07:29 .
drwxrwx--x 1 system system 2048 Mar 20 14:33 ..
-rw-r----- 1 system app_68 92139 Feb 28 11:10 *****.apk
-rw-r----- 1 system app_64 44784 Apr 1 07:29 *****.apk
bash-4.1# cp * /sdcard
bash-4.1# exit
exit
# exit
I just want to see which user you are on the shell and if the access rights match. Because if you are not root you don't even have list rights on that directory, which causes the "cant stat *" message
Did you root you N1? How do you access the shell? ADB? SSH? App? This is getting pointless

FloOGB said:
This is getting pointless
Click to expand...
Click to collapse
that's a little harsh on him...
he is having problems. be understanding. everyone has to start somewhere.
but, flo is correct, we need more detail on how you're commanding, and you'll definitely need root access

FloOGB said:
something like
Code:
* daemon not running. starting it now *
* daemon started successfully *
# bash
bash-4.1# id
uid=0(root) gid=0(root)
bash-4.1# cd /data/app-private/
bash-4.1# ls -al
drwxrwx--x 1 system system 2048 Apr 1 07:29 .
drwxrwx--x 1 system system 2048 Mar 20 14:33 ..
-rw-r----- 1 system app_68 92139 Feb 28 11:10 *****.apk
-rw-r----- 1 system app_64 44784 Apr 1 07:29 *****.apk
bash-4.1# cp * /sdcard
bash-4.1# exit
exit
# exit
I just want to see which user you are on the shell and if the access rights match. Because if you are not root you don't even have list rights on that directory, which causes the "cant stat *" message
Did you root you N1? How do you access the shell? ADB? SSH? App? This is getting pointless
Click to expand...
Click to collapse
ok first of all how would it be possible to run cm 5.0.5.3 witch i posted my n1 is currently running if i didnt have root. i am using this coomand as i have been through better terminal emulator. if you would be so kind as to give me the exact command lines to get the output info you want i will gladly do so. besides what is the point of terminal emulator, adb, or fastboot without root.

napoleontheruler said:
ok first of all how would it be possible to run cm 5.0.5.3 witch i posted my n1 is currently running if i didnt have root. i am using this coomand as i have been through better terminal emulator. if you would be so kind as to give me the exact command lines to get the output info you want i will gladly do so. besides what is the point of terminal emulator, adb, or fastboot without root.
Click to expand...
Click to collapse
* daemon not running. starting it now *
* daemon started successfully *
# bash
bash-4.1# id
uid=0(root) gid=0(root)
bash-4.1# cd /data/app-private/
bash-4.1# ls -al
drwxrwx--x 1 system system 2048 Apr 1 07:29 .
drwxrwx--x 1 system system 2048 Mar 20 14:33 ..
-rw-r----- 1 system app_68 92139 Feb 28 11:10 *****.apk
-rw-r----- 1 system app_64 44784 Apr 1 07:29 *****.apk
bash-4.1# cp * /sdcard
bash-4.1# exit
exit
# exit
Click to expand...
Click to collapse
1) adb shell
2) bash
3) id
4) cd /data/app-private/
5) ls -al
6) cp * /sdcard
Basically anything after bash-4.1# is a command.

napoleontheruler said:
if you would be so kind as to give me the exact command lines to get the output info you want i will gladly do so.
Click to expand...
Click to collapse
I did? Multiple times?
FloOGB said:
perhaps you can tell us what the output of the "ls" is and maybe exchange that with an "ls -al" ? that would show us the access rights. please just copy the whole session.
Click to expand...
Click to collapse
FloOGB said:
EDIT: and do an "id" please, just after the ls -al, copy that output as well.
Click to expand...
Click to collapse
Thats the reason why i got a bit frustrated, sorry. archangelugp posted the command sequence.

archangelugp said:
1) adb shell
2) bash
3) id
4) cd /data/app-private/
5) ls -al
6) cp * /sdcard
Basically anything after bash-4.1# is a command.
Click to expand...
Click to collapse
do i run in terminal emulator or adb connect

napoleontheruler said:
do i run in terminal emulator or adb connect
Click to expand...
Click to collapse
Whichever method you use you'll have to use the su command to get root access first.
Connect your phone to your computer via USB cable, and make sure USB debugging is enabled on your phone (Settings > Applications > Development)
Enter adb shell to fire up Debug Bridge and enter shell mode
Enter su to become superuser
Enter cat /data/app-private/filename.apk > /sdcard/filename.apk to copy the file to the SD card.
exit
exit
Click to expand...
Click to collapse
I didn't want to reinvent the wheel so I pasted this from here. Both methods are shown.

wind0zer said:
Whichever method you use you'll have to use the su command to get root access first.
I didn't want to reinvent the wheel so I pasted this from here. Both methods are shown.
Click to expand...
Click to collapse
i was talking about what command line to find the output info and if i should run that though terminal emulator or adb.the link is were i got the command line from. so r u telling me that the termial emulator method will not work on the nexus.

Yes you can use the terminal in the phone to back up your paid apps.
Which part of the steps (in the link) do you not understand?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk

Why so troublesome.
By using below two apps, you can simply copy out your purchase & install apps:
- Root Explorer
- Titanium Backup

Yeah, my guess was that he isn't logged in as root, thats why I need the output of "id".
I think it doesn't matter how you access the phone, trough a terminal emulator on the phone or though adb.
Just write us down the uid and gid value from "id", that should be little enough text to copy manually
for example, write down the red part:
bash-4.1# id
uid=0(root) gid=0(root)

4.2.2 Link

http://android.clients.google.com/packages/data/ota/google_mako/de8b8d101614.signed-occam-JDQ39-from-JOP40D.de8b8d10.zip

Patching radio is just the modem drivers, most of the time there is a new one with every update release.
If they're going to disable LTE via radio/modem then that can easily be replaced by a previous or modified version but if its baked into the actual coding then thats another story.

UZ7 said:
Patching radio is just the modem drivers, most of the time there is a new one with every update release.
If they're going to disable LTE via radio/modem then that can easily be replaced by a previous or modified version but if its baked into the actual coding then thats another story.
Click to expand...
Click to collapse
Thanks. Fixed.

I'm not on ATT but with 4.2.2 changing to LTE only immediately reverts to WCDMA preferred..

There is indeed a new baseband. Phone Info shows that all the various LTE modes are still there though. Can someone on ATT or someone in Canada test to see whether LTE is still working?
---------- Post added at 04:57 PM ---------- Previous post was at 04:50 PM ----------
El Daddy said:
I'm not on ATT but with 4.2.2 changing to LTE only immediately reverts to WCDMA preferred..
Click to expand...
Click to collapse
If you select all the other LTE modes (LTE/GSM auto), it stays selected.

bioyuki said:
There is indeed a new baseband. Phone Info shows that all the various LTE modes are still there though. Can someone on ATT or someone in Canada test to see whether LTE is still working?
---------- Post added at 04:57 PM ---------- Previous post was at 04:50 PM ----------
If you select all the other LTE modes (LTE/GSM auto), it stays selected.
Click to expand...
Click to collapse
upload baseband only please

zephiK said:
upload baseband only please
Click to expand...
Click to collapse
Link me to a how-to and I'll be happy to do it for you

bioyuki said:
Link me to a how-to and I'll be happy to do it for you
Click to expand...
Click to collapse
$ adb shell
# == inside adb shell ==
$ su
# dd bs=256 count=49153 if=/dev/block/platform/omap/omap_hsmmc.0/by-name/radio of=/sdcard/radio.img
49153+0 records in
49153+0 records out
12583168 bytes transferred in 11.365 secs (1107185 bytes/sec)
# exit
$ exit
# == adb shell exited ==
$ adb pull /sdcard/radio.img .
# done
(do those through ADB... or you can manually type it in terminal emulator)
when you type exit exit..... (and you didnt do it through ADB) just go to your /sdcard/ and upload the radio.img and include md5 hash please

zephiK said:
$ adb shell
# == inside adb shell ==
$ su
# dd bs=256 count=49153 if=/dev/block/platform/omap/omap_hsmmc.0/by-name/radio of=/sdcard/radio.img
49153+0 records in
49153+0 records out
12583168 bytes transferred in 11.365 secs (1107185 bytes/sec)
# exit
$ exit
# == adb shell exited ==
$ adb pull /sdcard/radio.img .
# done
(do those through ADB... or you can manually type it in terminal emulator)
when you type exit exit..... (and you didnt do it through ADB) just go to your /sdcard/ and upload the radio.img and include md5 hash please
Click to expand...
Click to collapse
On it

zephiK said:
$ adb shell
# == inside adb shell ==
$ su
# dd bs=256 count=49153 if=/dev/block/platform/omap/omap_hsmmc.0/by-name/radio of=/sdcard/radio.img
49153+0 records in
49153+0 records out
12583168 bytes transferred in 11.365 secs (1107185 bytes/sec)
# exit
$ exit
# == adb shell exited ==
$ adb pull /sdcard/radio.img .
# done
(do those through ADB... or you can manually type it in terminal emulator)
when you type exit exit..... (and you didnt do it through ADB) just go to your /sdcard/ and upload the radio.img and include md5 hash please
Click to expand...
Click to collapse
Umm thats for a omap device it looks like. I don't think that will work.

winner00 said:
Umm thats for a omap device it looks like. I don't think that will work.
Click to expand...
Click to collapse
Yeah, not working. I found a tool to grab the radio but it works for Windows only. Anyone else?

winner00 said:
Umm thats for a omap device it looks like. I don't think that will work.
Click to expand...
Click to collapse
really? worked on my Nexus S (same exact instructions) which was a hummingbird processor. hmmm, probably because they played around with the partitioning system in 4.2.x

bioyuki said:
There is indeed a new baseband. Phone Info shows that all the various LTE modes are still there though. Can someone on ATT or someone in Canada test to see whether LTE is still working?
Click to expand...
Click to collapse
LTE no longer works on 4.2.2
bioyuki said:
If you select all the other LTE modes (LTE/GSM auto), it stays selected.
Click to expand...
Click to collapse
It stays selected, but once you exit the menu, it reverts back to WCDMA preferred.

efrant said:
LTE no longer works on 4.2.2
It stays selected, but once you exit the menu, it reverts back to WCDMA preferred.
Click to expand...
Click to collapse
Whaaaat?
Can anybody else confirm please

This thread beat you by a few minutes
http://forum.xda-developers.com/showthread.php?t=2147137
Closed

Guide to go straight to TWRP 2.7.0.0

My new phone shipped with 12B and my first attempt to TWRP it failed resulting in very odd behavior in recovery mode (black screen and if connected to a PC with usb, I would get dozens of drive letters showing up). I recovered stock (11A) following the excellent guide here on xda (http://forum.xda-developers.com/showthread.php?t=2432476) and figured out a slightly different way to install TWRP 2.7.0.0 directly than anything I've read on xda (granted I've not read every post of every forum on the topic so I apologize if this exists somewhere already).
I've only tested this on a vs980 LG G2 as this is the only phone I have available to me.
Prerequisites:
You will need adb working, have a rooted phone. (see the first post of this forum)
Download TWRP 2.7.0.0 (http://teamw.in/project/twrp2/197)
Expand the TWRP 2.7.0.0 zip (expanded it into the folder twrp2)
adb push twrp2\tmp\loki\loki_flash /data/local/tmp/loki_flash
adb push twrp2\tmp\loki\loki_patch /data/local/tmp/loki_patch
adb push twrp2\recovery.img /data/local/tmp/recovery.img
adb shell (make sure you are at the root # prompt, otherwise su)
cd /data/local/tmp
chmod 777 loki_flash
chmod 777 loki_patch
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img (stop if you see errors)
./loki_patch recovery ./aboot.img ./recovery.img ./recovery.lok (stop if you see errors)
./loki_flash recovery ./recovery.lok (stop if you see errors)
exit
adb reboot recovery

Followed your steps all the way to step 11, and got error message 'Unsupported aboot image.' This is on rooted 12B stock firmware.
[email protected]:/data/local/tmp # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboo
t of=/data/local/tmp/aboot.img
rm/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img <
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.083 secs (12633445 bytes/sec)
[email protected]:/data/local/tmp # ll
ll
-rw------- root root 1048576 2014-04-24 00:43 aboot.img
-rwxrwxrwx root root 67020 2008-02-29 02:33 loki_flash
-rwxrwxrwx root root 67688 2008-02-29 02:33 loki_patch
-rw-rw-rw- root root 8828928 2008-02-29 02:33 recovery.img
[email protected]:/data/local/tmp # ./loki_patch recovery ./aboot.img ./recovery.img ./recovery.lok
aboot.img ./recovery.img ./recovery.lok <
[+] loki_patch v2.1
[-] Unsupported aboot image.

Same Issue
I had the same issue, that's why I went back to 11a stock, then forward to root/twrp/rom and now flashed the 12b radio. There appears to be something with the aboot.img in the 12b stock that loki doesn't like/doesn't support.
zw6233 said:
Followed your steps all the way to step 11, and got error message 'Unsupported aboot image.' This is on rooted 12B stock firmware.
[email protected]:/data/local/tmp # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboo
t of=/data/local/tmp/aboot.img
rm/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img <
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.083 secs (12633445 bytes/sec)
[email protected]:/data/local/tmp # ll
ll
-rw------- root root 1048576 2014-04-24 00:43 aboot.img
-rwxrwxrwx root root 67020 2008-02-29 02:33 loki_flash
-rwxrwxrwx root root 67688 2008-02-29 02:33 loki_patch
-rw-rw-rw- root root 8828928 2008-02-29 02:33 recovery.img
[email protected]:/data/local/tmp # ./loki_patch recovery ./aboot.img ./recovery.img ./recovery.lok
aboot.img ./recovery.img ./recovery.lok <
[+] loki_patch v2.1
[-] Unsupported aboot image.
Click to expand...
Click to collapse

I guess I'm curious, why go to all that trouble? I used flashify to install 2.7 and it worked just fine.

idrift said:
I guess I'm curious, why go to all that trouble? I used flashify to install 2.7 and it worked just fine.
Click to expand...
Click to collapse
Some just prefer using ADB. Especially those coming from Nexus devices where Fastboot is available. Doing it this way usually ensures the recovery will push successfully. Unless of course you mistype a command. Although I've personally never had a hiccup with Flashify, I've seen some who have.

idrift said:
I guess I'm curious, why go to all that trouble? I used flashify to install 2.7 and it worked just fine.
Click to expand...
Click to collapse
I just tried flashify and I reboot into stock recovery...?
Sent from my VS980 4G using Tapatalk

0331 said:
I just tried flashify and I reboot into stock recovery...?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Depends on what you are trying to do. If you are trying to load a custom recovery you need
You can back up your current kernel and recovery first with flashify which is never a bad idea.
Then you would need to flash TWRP if that is what you are trying to do. I flashed a zip as that's
the format TWRP was in for me. It replaces your stock recovery then. Warranty gone....
Make sure this is what you want to do. As previously posted some have had problems doing this.
For me it worked flawlessly. Do at your own risk.

[Q] recovery problem

I have unlocked my bootloader, installed TWRP and then i`ve get a TWRP bootloop. Tried to install CWM and now i have dual recovery. Is this normal? Does anyone had this issue?

Calanderia said:
I have unlocked my bootloader, installed TWRP and then i`ve get a TWRP bootloop. Tried to install CWM and now i have dual recovery. Is this normal? Does anyone had this issue?
Click to expand...
Click to collapse
Go into twrp. Go to advanced. Go to command terminal. Press the arrow in the bottom right. Enter these commands
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Then hit enter
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Then hit enter and reboot
Sent from my VS980 4G using XDA Free mobile app

NBreunig3 said:
Go into twrp. Go to advanced. Go to command terminal. Press the arrow in the bottom right. Enter these commands
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Then hit enter
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Then hit enter and reboot
Sent from my VS980 4G using XDA Free mobile app
Click to expand...
Click to collapse
Thx, i`ll try tomorrow cause this happend on HTC One of a friend. On my m7 worked fine.
What actualy this commands do? What did he did wrong that make the phone fall into that bootloop?

Calanderia said:
Thx, i`ll try tomorrow cause this happend on HTC One of a friend. On my m7 worked fine.
What actualy this commands do? What did he did wrong that make the phone fall into that bootloop?
Click to expand...
Click to collapse
Ok. Honestly I don't know what the commands do but it worked for me. He most likely got in a bootloop because he tried to install an ota update while rooted
Sent from my VS980 4G using XDA Free mobile app

NBreunig3 said:
Go into twrp. Go to advanced. Go to command terminal. Press the arrow in the bottom right. Enter these commands
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Then hit enter
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Then hit enter and reboot
Click to expand...
Click to collapse
As far as I know:
/dev/zero returns null chararters or 0 if you prefer (0x00)
so:
if = input file (source)
/dev/zero = 0
of = output file (destination)
so the command means: write 0 over data contained in /fota and /misc partitions, in other therm, it will destroy data of these both partitions!
And from my understanding, this is not a good idea! I don't even know if /fota partition exist on the M7.
@Calanderia
make sure the recovery image you are using is compatible for your phone variant
check MD5 of the image before flashing
You should really try to reflash the recovery and then erase cache
Code:
fastboot flash recovery recovery.img
fastboot erase-cache
fastboot reboot-bootloader
Then try to boot the recovery again.
---------- Post added at 07:38 PM ---------- Previous post was at 07:36 PM ----------
NBreunig3 said:
Ok. Honestly I don't know what the commands do
Click to expand...
Click to collapse
dd commands can be very dangerous, if you don't know what they are doing, then don't use these and more important, don't suggest someone else to execute these.
@nkk71 could you please take a look at this thread and give your opinion on commands at post #2? thanks

alray said:
As far as I know:
/dev/zero returns null chararters or 0 if you prefer (0x00)
so:
if = input file (source)
/dev/zero = 0
of = output file (destination)
so the command means: write 0 over data contained in /fota and /misc partitions, in other therm, it will destroy data of these both partitions!
And from my understanding, this is not a good idea! I don't even know if /fota partition exist on the M7.
@Calanderia
make sure the recovery image you are using is compatible for your phone variant
check MD5 of the image before flashing
You should really try to reflash the recovery and then erase cache
Code:
fastboot flash recovery recovery.img
fastboot erase-cache
fastboot reboot-bootloader
Then try to boot the recovery again.
---------- Post added at 07:38 PM ---------- Previous post was at 07:36 PM ----------
dd commands can be very dangerous, if you don't know what they are doing, then don't use these and more important, don't suggest someone else to execute these.
@nkk71 could you please take a look at this thread and give your opinion on commands at post #2? thanks
Click to expand...
Click to collapse
What phone and carrier are you using?
Sent from my VS980 4G using XDA Free mobile app

NBreunig3 said:
What phone and carrier are you using?
Sent from my VS980 4G using XDA Free mobile app
Click to expand...
Click to collapse
well this is the Htc one M7 forum, so I guess the OP use the M7 Also said at post #3

hi @alray
quite right, those commands will null out the specified partitions (it's actually one of the ideas I had for the active cmndline overflow error), so
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc[
wouldn't cause any harm (of course it will wipe the version-main etc, minor issue), but
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
is probably not going to achieve anything, cause that doesn't exist as far as I can tell.
Here's my "by-name" listing for an m7_ul:
Code:
adsp -> /dev/block/mmcblk0p16
boot -> /dev/block/mmcblk0p33
cache -> /dev/block/mmcblk0p36
cdma -> /dev/block/mmcblk0p28
control -> /dev/block/mmcblk0p25
devlog -> /dev/block/mmcblk0p22
dsps -> /dev/block/mmcblk0p15
extra -> /dev/block/mmcblk0p27
local -> /dev/block/mmcblk0p26
misc -> /dev/block/mmcblk0p19
modem -> /dev/block/mmcblk0p20
pdata -> /dev/block/mmcblk0p24
radio -> /dev/block/mmcblk0p17
recovery -> /dev/block/mmcblk0p34
reserve -> /dev/block/mmcblk0p18
system -> /dev/block/mmcblk0p35
userdata -> /dev/block/mmcblk0p37
so no fota (firmware over the air) partition there. Oh and remember that the "by-name" support was only implemented as of TWRP 2.7.<something> (can't remember when), so earlier recoveries won't do any of the above commands.
At OP, fastboot erase cache should solve your problem, and if you're saying you have both recoveries installed, then you probably flashed one of them to the kernel partition
fastboot flash boot <name of recovery>.img
as opposed to the recovery partition
fastboot flash recovery <name of recovery>.img

nkk71 said:
hi @alray
quite right, those commands will null out the specified partitions (it's actually one of the ideas I had for the active cmndline overflow error), so
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc[
wouldn't cause any harm (of course it will wipe the version-main etc, minor issue), but
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
is probably not going to achieve anything, cause that doesn't exist as far as I can tell.
Here's my "by-name" listing for an m7_ul:
Code:
adsp -> /dev/block/mmcblk0p16
boot -> /dev/block/mmcblk0p33
cache -> /dev/block/mmcblk0p36
cdma -> /dev/block/mmcblk0p28
control -> /dev/block/mmcblk0p25
devlog -> /dev/block/mmcblk0p22
dsps -> /dev/block/mmcblk0p15
extra -> /dev/block/mmcblk0p27
local -> /dev/block/mmcblk0p26
misc -> /dev/block/mmcblk0p19
modem -> /dev/block/mmcblk0p20
pdata -> /dev/block/mmcblk0p24
radio -> /dev/block/mmcblk0p17
recovery -> /dev/block/mmcblk0p34
reserve -> /dev/block/mmcblk0p18
system -> /dev/block/mmcblk0p35
userdata -> /dev/block/mmcblk0p37
so no fota (firmware over the air) partition there. Oh and remember that the "by-name" support was only implemented as of TWRP 2.7.<something> (can't remember when), so earlier recoveries won't do any of the above commands.
At OP, fastboot erase cache should solve your problem, and if you're saying you have both recoveries installed, then you probably flashed one of them to the kernel partition
fastboot flash boot <name of recovery>.img
as opposed to the recovery partition
fastboot flash recovery <name of recovery>.img
Click to expand...
Click to collapse
thanks for the clarification! Nicely explained, as usual :good:

[Guide] Remove magisk modules without TWRP!

First of all, this was all made possible by s3axel
Now on to the tutorial:
Flash s3axel's stock recovery with adb enabled (Tutorial in post)
Now you have that, boot into the recovery and put in your security method (pattern, pin, etc)
Now open CMD and type "adb shell"
To find a specific module
type "ls -Ral data/adb/modules"
Now to remove the magisk module
type "rm -r data/adb/modules/module_name"
(module_name is the name of the module)
I'll be sure to try and help with any questions in the comments so don't be shy to ask

Don't you have to cd to a path before executing the remove command?
EDIT:
You have to cd to data/adb/modules and then run the rm -r command. It worked perfectly! Now I can actually try different modules. Thanks!
Sent from my OnePlus7TPro using XDA Labs

Lossyx said:
Don't you have to cd to a path before executing the remove command?
EDIT:
You have to cd to data/adb/modules and then run the rm -r command. It worked perfectly! Now I can actually try different modules. Thanks!
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Sorry forgot that yeah, thanks for the heads up. I edited the post

HolyChickenGuy said:
First of all, this was all made possible by s3axel
type "rm -r data/adb/modules/module_name"
Click to expand...
Click to collapse
Remembers me of how to shoot yourself in the foot with bash...
Code:
$ ls
foot.c foot.h foot.o toe.c toe.o
$ rm * .o
rm:.o no such file or directory
$ ls
$
Always be carefull when using "rm -r" or "rm -rf". :laugh:

thank you very much for you post, really helped me

I followed this guide but didn't succeed!
When imputing the command "ls -ral /data/adb/modules" I get the message that there is not that file or directory...
Inputing "ls -ral /data/adb" I find that there are 2 directorys under /adb: "system" and "root", but no "modules"
I'm stuck here. please help me

salomaoa said:
I followed this guide but didn't succeed!
When imputing the command "ls -ral /data/adb/modules" I get the message that there is not that file or directory...
Inputing "ls -ral /data/adb" I find that there are 2 directorys under /adb: "system" and "root", but no "modules"
I'm stuck here. please help me
Click to expand...
Click to collapse
I think you can use "cd file_name" to enter file
"cd .." to back
You can type "ls" to show any file
And you go in the file and type "rm -r *" to remove all file and folder

ricky886 said:
I think you can use "cd file_name" to enter file
"cd .." to back
You can type "ls" to show any file
And you go in the file and type "rm -r *" to remove all file and folder
Click to expand...
Click to collapse
I was hoping you could guide me? I want to delete lock.ogg and unlock.ogg in system/product/media/ui folder and copy new ones. BTW, I have got the adb enabled img of 10.0.8...

adeelsmatrix said:
I was hoping you could guide me? I want to delete lock.ogg and unlock.ogg in system/product/media/ui folder and copy new ones. BTW, I have got the adb enabled img of 10.0.8...
Click to expand...
Click to collapse
You'll have to use magisk for that.
System is permanent read only in Android 10
Sent from my OnePlus7TPro using XDA Labs

adeelsmatrix said:
I was hoping you could guide me? I want to delete lock.ogg and unlock.ogg in system/product/media/ui folder and copy new ones. BTW, I have got the adb enabled img of 10.0.8...
Click to expand...
Click to collapse
You can try this to remove that two files
Adb shell
CD system/product/media/ui
Rm lock.ogg
Rm unlock.ogg

ricky886 said:
You can try this to remove that two files
Adb shell
CD system/product/media/ui
Rm lock.ogg
Rm unlock.ogg
Click to expand...
Click to collapse
Thanks for the reply bro, Actually I need to overwrite these two files with the files of same names. So how to put new files with the same names. PEACE...

adeelsmatrix said:
Thanks for the reply bro, Actually I need to overwrite these two files with the files of same names. So how to put new files with the same names. PEACE...
Click to expand...
Click to collapse
Check this
https://adbshell.com/commands
I think you can use cp(copy) or mv(move) commands

Lossyx said:
You'll have to use magisk for that.
System is permanent read only in Android 10
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
How magisk could help in this regard. Is there any specific module...?
---------- Post added at 07:23 AM ---------- Previous post was at 07:22 AM ----------
ricky886 said:
Check this
https://adbshell.com/commands
I think you can use cp(copy) or mv(move) commands
Click to expand...
Click to collapse
Thanks, I'll try this...

ricky886 said:
Check this
https://adbshell.com/commands
I think you can use cp(copy) or mv(move) commands
Click to expand...
Click to collapse
I can enter into systems but adb shell is displaying only three directories/folders (bin, etc and lib64). I can't get into system/product/media/audio/ui folder. Any suggestions....?
As I know off you can't mount system rw in Android 10 for now...

salomaoa said:
I followed this guide but didn't succeed!
When imputing the command "ls -ral /data/adb/modules" I get the message that there is not that file or directory...
Inputing "ls -ral /data/adb" I find that there are 2 directorys under /adb: "system" and "root", but no "modules"
I'm stuck here. please help me
Click to expand...
Click to collapse
I am stuck here as well, "ls -ral /data/adb" tells me no such file or directory.
"ls -ral /data" only returns
# ls -Ral data
data:
total 0
drwxr-xr-x 2 root root 40 2019-12-25 01:32 .
drwxr-xr-x 28 root root 1100 1970-03-14 14:38 ..
I installed a Magisk module and Now im stuck in boot animation. Have no way of uninstalling at the moment. Please let me know if you have a solution

thanks for this guide !!

c19932 said:
I am stuck here as well, "ls -ral /data/adb" tells me no such file or directory.
"ls -ral /data" only returns
# ls -Ral data
data:
total 0
drwxr-xr-x 2 root root 40 2019-12-25 01:32 .
drwxr-xr-x 28 root root 1100 1970-03-14 14:38 ..
I installed a Magisk module and Now im stuck in boot animation. Have no way of uninstalling at the moment. Please let me know if you have a solution
Click to expand...
Click to collapse
Looks like you forgot the "/" infront of data so unless you are already in the root directory it is listing the contents of the directory "data" that is in your current location which it looks like doesn't exist.
Either run
# ls -Ral /data
or
# cd /
# ls -Ral data
Hope that helps ya out.
Stay Kung Flu Free
Later

Thanks for this helpful guide,
Just an FYI for my 10.0.7AA i reboot into recovery but i cannot decrypt, however I could use those commands and helped me remove the modules.
However, the phone is still not booting, does it have anything to do with the recovery pushed? Do I need to then go place the stock recovery back?
Or has it got something else wrong?
Thanks again.

Another way with a computer running adb:
If adb debugging is enabled:
"adb wait-for-device shell magisk --remove-modules"
If not, flash the stock boot.img, enable USB debugging, flash the magisk_patched_boot.img and then run the command.
It will remove all modules even if your SystemUI crashes. If you are stuck before adb commands can be issued, the OT's tutorial will do.

Macusercom said:
Another way with a computer running adb:
If adb debugging is enabled:
"adb wait-for-device shell magisk --remove-modules"
If not, flash the stock boot.img, enable USB debugging, flash the magisk_patched_boot.img and then run the command.
It will remove all modules even if your SystemUI crashes. If you are stuck before adb commands can be issued, the OT's tutorial will do.
Click to expand...
Click to collapse
Thanks, good to know!
So only prerequisite is that ADB/USB debugging is enabled and it works for both Magisk and Xposed modules?