Database Develop

[ROOTING] The M7 Exploit + Newbie Guide

To be honest, I'm a nice guy, but when threads get filled with utter "OMG, How do I root?" posts, I get pissed off. I don't mean to backseat moderate or anything, I just really get fed up sometimes. Hence, I've broken out the hardcore side of myself, and I present:
Coburn's (mostly) failproof rootmeplz kthxbai tutorial, featuring the awesome m7 exploit.
YOU CANNOT USE THIS ROOT GUIDE TO INSTALL ANDROID 2.0.x/2.1/2.x AT THIS MOMENT IN TIME. PLEASE DO NOT ASK IF YOU CAN INSTALL ANDROID 2.x USING ROOT, AT THIS STAGE IT'S A BIG FAT NO! THANK YOU FOR YOUR ATTENTION!!
Alright.
Easy to understand, plain english guide
Download the ZIP file attached to this post. Extract the files to a safe location - perhaps C:\Tattoo ?
Now, you'll need adb for windows. You can get it from my website's server here: ADB for windows.
Make sure your device is in USB Debug Mode (Settings > Applications > Development). This is ESSENTIAL!
Extract all the files in the adb4win zip file to your C:\Tattoo folder.
Now, go to Command Prompt. In XP, it's under System Tools in Accessories. In Vista/7, it'll be under accessories.
Do the following at the command line:
C:\Users\Coburn> cd C:\Tattoo
This will change your working directory from C:\Users\Coburn (or silimar) to C:\Tattoo .
Now, at the command line, do this:
C:\Tattoo> adb-windows shell "mkdir /data/local/bin" (with the quotes!).
This makes a directory on the Tattoo under /data/local, called bin. If you get a error (like mkdir failed, file/folder exists), this is fine! Don't sweat it.
Now, run this command:
C:\Tattoo> adb-windows push m7 /data/local/bin/m7
...and wait until finish.
Run this:
C:\Tattoo> adb-windows shell "cd /data/local/bin && chmod 755 ./m7" (with the quotes!)
This allows you to run the sucker.
Now, the fun part. Run this:
C:\Tattoo> adb-windows shell
This will dump you at a "$" shell. do the following:
C:\Tattoo> adb-windows shell
$ cd /data/local/bin
$ while ./m7 ; do : ; done
...lotsa text will flow down your screen. This is normal. Sometimes the exploit causes adb to freeze up, I don't know. I think it may be due to the exploit. It worked on my mac fine though...
Soon, you'll be greeted with this:
#
This is the root prompt! If you get stuff like this:
# usage: reboot ...
usage: reboot ....
usage: reboot ...
Just keep your cool, press enter and the # will say "Boo" again. This is due the exploit spawning reboots to gain the shell.
Then, do these commands from this thread's first post:
-bm- and the hax0rs crew said:
You did it, you should be root now!
Let's set some variables:
Code:
export LD_LIBRARY_PATH=/system/lib
export PATH=/system/bin
[...] check if ur root:
Code:
id
You should get something like this:
Code:
# id
uid=0(root) gid=1000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
uid=0(root) is important.
Click to expand...
Click to collapse
When you get this:
C:\Tattoo> adb-windows shell
$ cd /data/local/bin
$ while ./m7 ; do : ; done
[... lotsa pasta ...]
#
You can do anything then! Look at /system, /data, etc etc. You're broken free, my friend, and you'll forever be free. Until you press that exit button. you didn't. You didn't press that exit button? lolwut u did? Grrrrrrr!!!
EDIT: Added Guide to remount partitions. It's below.
Now you need to install su. Exit your root shell (via CTRL+C) (NO, Coburn, are you serious? ME LOSE ROOT SHELL?! ) and download this su.zip and extract it to C:\Tattoo. DO NOT EXIT THE COMMAND PROMPT WINDOW.
Meanwhile, back at the ranch, in your command prompt window, do this:
C:\Tattoo> adb-windows push su /data/local/bin/su
Then break out a shell...
C:\Tattoo> adb-windows shell
at the $ prompt, enter:
$ chmod 755 /data/local/bin/su
$ cd /data/local/bin/
..run the exploit again via "while 'true' ; do ./m7 ; done" to get root again then enter ...
# chown root.root /data/local/bin/su
# chmod 4755 /data/local/bin/su
# mount -o rw,remount /dev/block/mtdblock5 /data
# mount -o rw,remount /dev/block/mtdblock3 /system (This line allows you to play around with files on the system partition!)
After that, you can exit out of the root shell, and try a normal shell and this:
$ /data/local/bin/su
...which should make you get a nice # prompt. (Sometimes it doesn't, for me it got su: permission denied, wtf?)
(End SU Part of guide)
Tested on Windows 7. Also works on a phone terminal emulator too!
Keep your cool peeps - I do this for fun, I'm not a fulltime android dev. I am an addict though.
Happy rootin my friends.
Cheers,
Tattoo Hacker Coburn.
Greets fly out to the geeks that hacked it originally - without you, I'd have got a nexus one.
Thanks for marsdroid for correcting an error. Kudos to you, bro!
"ANDROID - It's a virus. In a Good Way. Once it's in your system, you can't get rid of it."

You should also add the "su" part in order to get root easier after the first time. Otherwise you have to do the exploit every time you want #

You could also add an explanation on how to remount the partitions without nosuid, so that a suid su can work.

mainfram3 said:
You could also add an explanation on how to remount the partitions without nosuid, so that a suid su can work.
Click to expand...
Click to collapse
Noted. Will do.
LordGiotto said:
You should also add the "su" part in order to get root easier after the first time. Otherwise you have to do the exploit every time you want #
Click to expand...
Click to collapse
Heh, yeah. Might add that up too.

Coburn64.
Thanks Man.
Nice Thread.

Thank you Coburn

svprm said:
Coburn64.
Thanks Man.
Nice Thread.
Click to expand...
Click to collapse
Thanks bro for your thanks.

I'm very glad you did that work, I'm kind of busy but I will update my statusposting and link to your HowTo!
Thats great community work.
[ROOTING] The M7 Exploit + Newbie Guide
Easy to understand, plain english guide
Click to expand...
Click to collapse
I apologize for my english, it's not my native language and I tried my best. ;-)
Keep up your work!
-bm-

-bm- said:
I'm very glad you did that work, I'm kind of busy but I will update my statusposting and link to your HowTo!
Thats great community work.
I apologize for my english, it's not my native language and I tried my best. ;-)
Keep up your work!
-bm-
Click to expand...
Click to collapse
You're welcome. I actually wanted this thread to help your thread, I wanted to spawn a m7 exploit thread to keep the original thread (which is based on the classic m6 exploit) clean of "How do I root with m7" and such.
Keep up the good work too, bm!

Thanks Coburn, so m6 is useless..
adb shell rm /data/local/bin/m6?

thx for the work , and corrections ! deleted the ealyer post

?
When i get # , and type:
# chown root.root /data/local/bin/su
i get :
chown root.root /data/local/bin/su
chown: not found
#
What i'm doing wrong /??

liderzre said:
When i get # , and type:
# chown root.root /data/local/bin/su
i get :
chown root.root /data/local/bin/su
chown: not found
#
What i'm doing wrong /??
Click to expand...
Click to collapse
type
export LD_LIBRARY_PATH=/system/lib
export PATH=/system/bin

rooted
Ty. Guide is not 100% for noobs. (ME).

Problem copying files to system partition after successfull rooting
Hi
The device was rooted successfully (from the first time using m7)
But I have very strange problem.
I try to update some files in the /system (updating fonts in /system/fonts).
I successfully run following command to remount system with rw permissions
/system/bin/mount -o rw,remount /dev/block/mtdblock3 /system
But when I try to copy files to /system/fonts I get "not enough memory" error.
If I run "df" command it shows that /system has 14% free before write attempt
But if I run "df" command after the write attempt I see that there is no free space.
It looks like there is some protection mechanism that prevents copying files to /system partition.
Does any one has an idea how to solve it?
Thanks

ronyrad said:
Hi
The device was rooted successfully (from the first time using m7)
But I have very strange problem.
I try to update some files in the /system (updating fonts in /system/fonts).
I successfully run following command to remount system with rw permissions
/system/bin/mount -o rw,remount /dev/block/mtdblock3 /system
But when I try to copy files to /system/fonts I get "not enough memory" error.
If I run "df" command it shows that /system has 14% free before write attempt
But if I run "df" command after the write attempt I see that there is no free space.
It looks like there is some protection mechanism that prevents copying files to /system partition.
Does any one has an idea how to solve it?
Thanks
Click to expand...
Click to collapse
The problem is well known an jet we have got no explanation. It looks like an additional security system build in by HTC. That is what also prevents us from flashing Custom ROMS at the moment. Development goes on here: http://forum.xda-developers.com/showthread.php?t=631540&page=18 but there is no solution or explanation until now.
-bm-

Could it be that it seems to be that the driver (yaffs) is possibly trying to copy /system into memory, and then reflash the partition all at once (to prevent NAND/NOR tear and wear)?

this guide is in error and will for sure not work ...
you should post probberly ...specially now when things is working....
there is no reason do do a NONSENCE guide .....
thx for the work thoe
Click to expand...
Click to collapse
Excuse me, but it was tested working. I do not post false or misleading information, so please don't accuse me of posting something that won't work. It does work. If you have troubles, you're not following it correctly. Start again and work one step at a time.

Coburn64 said:
Excuse me, but it was tested working. I do not post false or misleading information, so please don't accuse me of posting something that won't work. It does work. If you have troubles, you're not following it correctly. Start again and work one step at a time.
Click to expand...
Click to collapse
don't worry for such baseless allegations coburn.... u r doing a great job. keep up this good work bro.... thanks a lot for this wonderful presentation...
waiting for ur custom ROM.....

Coburn64 u are missing a ; in the 2. while
and i dont expect the newbies to sit back and wait for the "BUUH"..
but im sure someone will....
thx again
EDIT Coburn64 fixed it

[GUIDE] Steps to root stocked Nexus One android without flashing(unlocked bootloader)

Disclaimer 1 : I tried to look for something like this but I did not found it. Then I tried to achieve it. Sorry if they are well known steps
This guide allows to root a Nexus One with unlocked bootloader with NO need to flash recovery
USE THAT INFORMATION AT YOUR RISK!!
Updated: Added a line to work with Gingerbread
That steps are for Ubuntu. If you are any interested windows user, please let me know.
Prerequisites:
Unlocked bootloader
adb working properly
1. Download fastboot
Code:
wget --referer=http://developer.htc.com/adp.html http://dl4.htc.com/RomCode/ADP/fastboot.zip
unzip fastboot.zip
chmod u+x fastboot
rm fastboot.zip
2. Obtain busybox (anyone have any direct link?) - NOT GOING TO FLASH CM, JUST GETTING busybox from a trusted place
Code:
wget http://download.cyanogenmod.com/get/update-cm-7.0.0-N1-signed.zip
unzip update-cm-7.0.0-N1-signed.zip system/xbin/busybox
rm update-cm-7.0.0-N1-signed.zip
3. Download su
-- UPDATE: that link broken, you have to donwload it from Google Play
Code:
wget http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
unzip su-2.3.6.1-ef-signed.zip system/app/Superuser.apk system/bin/su
rm su-2.3.6.1-ef-signed.zip
4. Download recovery-RA - NOT GOING TO FLASH IT, DON'T WORRY!!!
Code:
wget -O recovery-RA-passion-v2.2.1.img http://files.androidspin.com/files/amon_ra/RECOVERY/recovery-RA-passion-v2.2.1.img
md5sum recovery-RA-passion-v2.2.1.img
echo ... Validate md5sum is 3def709ab1c9e051a92a1c8b1504a36a
5. Reboot to bootloader - JUST BOOTING WITH, NO FLASHING
Code:
adb devices
adb wait-for-device
adb reboot-bootloader
fastboot boot recovery-RA-passion-v2.2.1.img
echo ... Waiting for recovery image load
while [ -z `adb shell pwd 2> /dev/null` ]
do
sleep 1
done
6. Root it!
Code:
adb shell mount /system
adb push system/xbin/busybox /system/bin/busybox
adb shell chmod 4755 /system/bin/busybox
adb push system/bin/su /system/bin/su
adb shell chmod 4755 /system/bin/su
adb push system/app/Superuser.apk /system/app/Superuser.apk
adb shell chmod 4755 /system/app/Superuser.apk
7. Reboot and enjoy rooting
Code:
adb shell reboot

Will this work on stock Gingerbread?

If you are running Nexus One with Gingerbread, as I understand, it can work. I've not tried, you can try.... at your risk ;-)

Helleqn said:
Will this work on stock Gingerbread?
Click to expand...
Click to collapse
If you have an unlocked bootloader, yes, it will work. If you have an unlocked bootloader, you can install pretty much anything you want, whenever you want...
Sent from my Nexus One using XDA Premium App

Helleqn said:
Will this work on stock Gingerbread?
Click to expand...
Click to collapse
I've added a adb command (mount /system) to work with Gingerbread. It works on mine.

It also works on 2.3.4

Yep. Worked great for me. But with all due respect, it seemed a little fishy to me that your directions have users pull busybox from Cyanogenmod but then have them pull su and Superuser.apk from a random file on a Dropbox account especially since both files are available in the already trusted Cyanogenmod download that was used for busybox. And even more so because the Superuser.apk file using your instructions is a larger file than the one included with Cyanogenmod. So I only used the files from CM and it worked like a charm.
Not accusing you or anything. I'm just pointing that out.

The easier way is to do step 5, then flash the su zip from step 3, and you're pretty much done. You can install busybox through the Market app...

Don't worry for the link, I toke it from the original post for that su release:
http://forum.xda-developers.com/showthread.php?t=682828
I agree it's enough with CM but I intend to get the last version... may be it's not the best option...
Thanks for your comments.

[UTIL] SkitzBackup

The attached ZIP includes scripts for Windows and Linux to backup your Galaxy Tab.
Linux users will need to install 7zip
Code:
sudo apt-get install p7zip
May also work on OSX but you're on your own with 7zip
You will need adb access to your tab whichever platform you use.
All you need to do to run it is extract the attached archive and run
Windows
Code:
skitzbackup.cmd
Linux / OSX
Code:
chmod a+x <folder where you extracted it>/skitzbackup/skitzbackup.sh
cd <folder where you extracted it>/skitzbackup
./skitzbackup.sh
The script will pull the following partitions and pack them in a 7zip archive for safe keeping:
efs
recovery
boot
system
radio
cache
misc
Before you ask, I have no idea what the 'misc' partition is. Haven't had time to explore that yet
I have NOT tested flashing these back as yet, except for boot and recovery so you use this entirely at your own risk.
DOWNLOAD HERE
View attachment skitzbackup.zip
Enjoy!

Code:
alias del=rm
mkdir skitzbackup
cd skitzbackup
adb shell su -c "dd if=/dev/block/mmcblk0p1 of=/sdcard/efs.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p2 of=/sdcard/recovery.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p3 of=/sdcard/boot.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p5 of=/sdcard/cache.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p6 of=/sdcard/misc.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/radio.img bs=4096"
adb pull /sdcard/efs.img
adb pull /sdcard/recovery.img
adb pull /sdcard/boot.img
adb pull /sdcard/system.img
adb pull /sdcard/cache.img
adb pull /sdcard/misc.img
adb pull /sdcard/radio.img
adb shell rm /sdcard/efs.img
adb shell rm /sdcard/recovery.img
adb shell rm /sdcard/boot.img
adb shell rm /sdcard/system.img
adb shell rm /sdcard/cache.img
adb shell rm /sdcard/misc.img
adb shell rm /sdcard/radio.img
7z a skitzbackup.7z *.img
del *.img

Could this be used to backup apps and app data before unlocking bootloader? I can't see a /data partition

working perfectly!You're great

djmasque said:
Could this be used to backup apps and app data before unlocking bootloader? I can't see a /data partition
Click to expand...
Click to collapse
No. Unfortunately, using this method to backup needs to write to the 'sdcard' which is what you want to back up.
Writing a script to back up data is a bit tricky since you can't reference it as a drive in windows and you can't know, for sure what the mount point will be in linux.
My main aim with the first version was to write a script which would work on either Windows or Linux, which it does. I might do seperate scripts to do a data backup.

bcmobile said:
No. Unfortunately, using this method to backup needs to write to the 'sdcard' which is what you want to back up.
Writing a script to back up data is a bit tricky since you can't reference it as a drive in windows and you can't know, for sure what the mount point will be in linux.
My main aim with the first version was to write a script which would work on either Windows or Linux, which it does. I might do seperate scripts to do a data backup.
Click to expand...
Click to collapse
Okay, good work nonetheless

Looks a lot like rotobackup, hehe.

Chainfire said:
Looks a lot like rotobackup, hehe.
Click to expand...
Click to collapse
Yes, it is based on rotobackup method, but compresses and cleans up too
Sent from my GT-P7100 using XDA Premium App

bcmobile said:
Yes, it is based on rotobackup method, but compresses and cleans up too
Sent from my GT-P7100 using XDA Premium App
Click to expand...
Click to collapse
Whats needed now is a kind of automated restore

bcmobile said:
You will need adb access to your tab whichever platform you use.
All you need to do to run it is extract the attached archive and run
Click to expand...
Click to collapse
Sorry for the noob question but how do i do this true windows?

Will this work for me?
Hi bcmobile,
This looks excellent.
I'm currently running a P7100 (10.1v) with ISI-Galaxy 1.2.5v (HC3.2) but my baseband/modem is still P7100BUKE2.
I would like to get the GSM working (for sending USSD commands) but I would need to flash my modem, and I would like to backup the modem before I flash it with the P7500 modem.bin, if something goes wrong, I can always go back to the old one.
In your script, is radio.img the modem.bin?
Also is the "/dev/block/" always the same on all the different versions of the tablet? (in other words if I have a 10.1v will this backup my modem).
Thanks so much. You help is much appreciated.

seraphimserapis said:
Whats needed now is a kind of automated restore
Click to expand...
Click to collapse
/!\ IN THEORY /!\ you'd just have to copy the .img files back to the tab and switch the command line arguments for dd. (e.g. dd if=/path/to/file.img of=/path/to/directory)

soo i know this is kind of old but does this work for any device? if so what am i doing wrong? its stuck on deamon started successfully...

[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?

Question Mounting system R/W

Hi,
did anybody successfully mount system R/W?
I tried https://forum.xda-developers.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/
but it did not work.
Regards,
Hyper

I used https://forum.xda-developers.com/t/...ake-partitions-rw-in-super-partition.4120963/
for stock rom.

NisseGurra said:
I used https://forum.xda-developers.com/t/...ake-partitions-rw-in-super-partition.4120963/
for stock rom.
Click to expand...
Click to collapse
Just forgot, I also tried this one. How did you do it?
I could not find super.sin.
Also when trying to unpack the super image, the Tools says, it would not be a proper super image :-/

You need root and usb debugging
Place the superrepack.arm64_pie in your adb folder and then open an cmd shell:
adb push superrepack.arm64_pie /data/local/tmp
adb shell
su
cd /data/local/tmp
mv superrepack.arm64_pie superrepack
chmod 755 superrepack
stop
Then i used for a-active:
./superrepack /dev/block/bootdevice/by-name/super system_a
./superrepack /dev/block/bootdevice/by-name/super system_ext_a
./superrepack /dev/block/bootdevice/by-name/super product_a
sync
reboot

Can i ask why you want to mount system as RW?

morpheus302 said:
Can i ask why you want to mount system as RW?
Click to expand...
Click to collapse
Without a proper debloating it is not possible to get MicroG running without issues :-/

NisseGurra said:
You need root and usb debugging
Place the superrepack.arm64_pie in your adb folder and then open an cmd shell:
adb push superrepack.arm64_pie /data/local/tmp
adb shell
su
cd /data/local/tmp
mv superrepack.arm64_pie superrepack
chmod 755 superrepack
stop
Then i used for a-active:
./superrepack /dev/block/bootdevice/by-name/super system_a
./superrepack /dev/block/bootdevice/by-name/super system_ext_a
./superrepack /dev/block/bootdevice/by-name/super product_a
sync
reboot
Click to expand...
Click to collapse
Thank you! Gonna try this again.
//EDIT
Unfortunately after reboot I have ramdump. This never happpend before
I exceuted the scripts until all errors were gone.