Hi, I got a new phone recently, as the name implies it's a CC Core-m5, I would like to root this device but unfortunately there isn't anything on internet and the guys working at CC doesn't want to give me the firmware so that I can patch the boot using magisk.
Can someone help please ?
If someone manage to get temporary root access (even if it can't remount partitions) can he post how he managed to do it ? That way we could build our own TWRP image
Temporary root access is easy to realize: simply put a suitable su binary into Android's filesystem and make it executable:
Code:
adb devices
adb push <FULL-PATH-OF-SU-BINARY-ON-PC> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
xXx yYy said:
Temporary root access is easy to realize: simply put a suitable su binary into Android's filesystem and make it executable:
Code:
adb devices
adb push <FULL-PATH-OF-SU-BINARY-ON-PC> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
Click to expand...
Click to collapse
Thanks a lot, Im gonna try that, I thought of that technic but wasn't sure if it was possible
Hmm, look like this isn't possible anymore, or Im doing it wrong. Im using lineageOS 18.1 su binary, when executing it threw the shell I get the error code 255. Weird
Using the SU binaries you provided in an other thread I get the error code 1. Nothing more
xXx yYy said:
Temporary root access is easy to realize: simply put a suitable su binary into Android's filesystem and make it executable:
Code:
adb devices
adb push <FULL-PATH-OF-SU-BINARY-ON-PC> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
Click to expand...
Click to collapse
xXx yYy said:
Temporary root access is easy to realize: simply put a suitable su binary into Android's filesystem and make it executable:
Code:
adb devices
adb push <FULL-PATH-OF-SU-BINARY-ON-PC> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
Click to expand...
Click to collapse
You won't get root access this way, as root access is allowed for binaries in root partition.
As you can't write this partition <=> you can't put any binary on it.
idem-bis-repetita
As seen in this thread https://forum.xda-developers.com/t/rooting-crosscall-core-m5.4359409/ there is a way to get temporary root access.
@xXx yYy Any further ideas ? Thanks btw
Might be resolved once we get more informations on dirty-cred, as it may affect the android kernel too.
Bricked my phone lol, no working recovery
Related
I recently received my Transformer back after RMA-ing it for a non functioning screen. Of course, even though the problem lied with the hardware, they still unrooted and reinstalled stock firmware on it. Everything on it works, except for the USB cable that seems to be either not working, or because they installed all my apps and settings back on the tablet, something's wrong. This is a problem when it comes to rooting it again. What I'm trying to do is run the commands through the Terminal Emulator, but here is what happens:
Code:
[email protected]: /sdcard $ adb start-server
* Daemon not running, starting it on port 5038 *
* Daemon started successfully *
[email protected]: /sdcard $ adb connect localhost:5038
connected to localhost:5038
[email protected]: /sdcard $ adb push su /data/local/tmp
error: device not found
So my question is, is it even possible to do this? If not, is there another way to do it?
Thanks in advanced for any help!
adb is the android debugging bridge what it does is changes your shell from your computer to your device so you do not need to run anything that refers to adb from your device
Hmm, run Wolf's exploit but remove 'adb' from all the commands, pretend you're already in the shell. (Because you are)
Thing O Doom said:
Hmm, run Wolf's exploit but remove 'adb' from all the commands, pretend you're already in the shell. (Because you are)
Click to expand...
Click to collapse
Yeah, I've tried that too.
Code:
/system/bin/sh: push: not found
aldude999 said:
Yeah, I've tried that too.
Code:
/system/bin/sh: push: not found
Click to expand...
Click to collapse
push is an adb command not a terminal command
mrevankyle said:
push is an adb command not a terminal command
Click to expand...
Click to collapse
I understand that.
I've been trying mv with no luck:
Code:
mv /sdcard/su /data/local/tmp
failed on '/sdcard/su' - Cross-device link
Download a Recovery.zip you want, and then extract the file called 'recoveryblob' out of it. (I highly recommend Rouge XM touch)
Place it on the root of your internal storage /sdcard/.
Run this:
Code:
mv /data/local/tmp /data/local/tmp.bak
ln -s /dev/block/mmcblk0p4 /data/local/tmp
exit
reboot the tab, get back in, run this:
Code:
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
reboot again, then you see a blue bar if it worked.
Then you can access CWM recovery that you just flashed with dd, and use that to install the Superuser or SuperSU .zip
Thing O Doom said:
Download a Recovery.zip you want, and then extract the file called 'recoveryblob' out of it. (I highly recommend Rouge XM touch)
Place it on the root of your internal storage /sdcard/.
Run this:
Code:
mv /data/local/tmp /data/local/tmp.bak
ln -s /dev/block/mmcblk0p4 /data/local/tmp
exit
reboot the tab, get back in, run this:
Code:
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
reboot again, then you see a blue bar if it worked.
Then you can access CWM recovery that you just flashed with dd, and use that to install the Superuser or SuperSU .zip
Click to expand...
Click to collapse
Code:
mv /data/local/tmp /data/local/tmp.bak
failed on '/data/local/tmp' - Permission denied
EDIT: Also, I've tried chmod, and I get an Operation not permitted error.
This is a TF101 correct? What stock firmware is it running?
You need to get USB working again.
Thing O Doom said:
This is a TF101 correct? What stock firmware is it running?
You need to get USB working again.
Click to expand...
Click to collapse
Yes It's running completely up to date (unfortunately) 9.2.1.24.
aldude999 said:
Yeah, I've tried that too.
Code:
/system/bin/sh: push: not found
Click to expand...
Click to collapse
It might help to understand what is going on. In this case, adb push su /data/tmp becomes "cp su /data/tmp/" if you are running from the terminal. You'll need stronger linux-fu.
You might also need a few extra /'s at the end of *some* of your commands.
sent from my transformer
gee one said:
It might help to understand what is going on. In this case, adb push su /data/tmp becomes "cp su /data/tmp/" if you are running from the terminal. You'll need stronger linux-fu.
You might also need a few extra /'s at the end of *some* of your commands.
sent from my transformer
Click to expand...
Click to collapse
Yeah, I gotcha, but the only command I have that comes close to cp is mv, and all the commands are very strictly limited.
Hi, I'm having trouble choosing the right section, anyway..
After more than a year i managed to correctly install ADB drivers, because before i installed Google driver, when i noticed i must install Motorola driver , the removing of previous one did not successful done, so the Motorola one did not installed well, by manually removing files it succeed.
But now another annoying not previewed issue, i need to exchange a file in /system/etc both in my tablet and my Motorola moto C tel. , it needs to remount system part. in r/w but to do this need to restart adb as root but with 'adb root' this is the answer:
adbd cannot run as root in production builds
my system is 7.0, what can i do?
You can install a temporary root to run shell-commmands what require root-rights like mount in ADB:
Code:
adb devices
adb push <FULL-PATH-TO-SU-BINARY-ON-PC> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
adb shell "/data/local/tmp/su -c 'mount -o rw,remount,rw /system'"
I have two questions, i don't find any su command available in the net.
I don't understand how it is possible to have to do all these hard maneuvers with a debug tool, i think it might be simpler.. why there's a command remount or root if it doesn't work?
hello i have my device SM A202F ANDROID 11 so i tried to root it but not working i have tried with kingroot ADB and Odin to flash twrp but not works if someone have the file to root it please share it thx
Every Android OS is rooted if a single binary called su is presnt in the Android ecosystem.
You at any time can add this binary by means of ADB
Code:
adb devices
adb push <LOCATION-OF-SU-BINARY-ON-COMPUTER> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
The matching SU-binary you extract from su-ARM.zip what you can download from
here.
jwoegerbauer said:
Every Android OS is rooted if a single binary called su is presnt in the Android ecosystem.
You at any time can add this binary by means of ADB
Code:
adb devices
adb push <LOCATION-OF-SU-BINARY-ON-COMPUTER> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
The matching SU-binary you extract from su-ARM.zip what you can download from
here.
Click to expand...
Click to collapse
am i undesrstand i have unlocked the bootloader but can you make a video about abd push i dont understand
The novel CAT S22 Flip was released in September, and is pretty much the only of its kind. It actually has an unlocked bootloader, and I was excited to try to root it. However, there's no version of TWRP designed specifically for it! Having never rooted anything before, does anyone know my options in this case to get TWRP for this phone? (Or another method of root I'm not aware of would also be fine.) Thanks!
Shoitah said:
The novel CAT S22 Flip was released in September, and is pretty much the only of its kind. It actually has an unlocked bootloader, and I was excited to try to root it. However, there's no version of TWRP designed specifically for it! Having never rooted anything before, does anyone know my options in this case to get TWRP for this phone? (Or another method of root I'm not aware of would also be fine.) Thanks!
Click to expand...
Click to collapse
Hey. I'm in the same boat. I need to add su binary but looks like the only way to do it is with TWRP. Have you succeeded? I keep trying to find a way to do it, so far no luck.
TWRP isn't needed at all to push ( suitable ) SU binary onto Android's filesystem: you achieve this by means of ADB, too
jwoegerbauer said:
TWRP isn't needed at all to push ( suitable ) SU binary onto Android's filesystem: you achieve this by means of ADB, too
Click to expand...
Click to collapse
Sweet!!! How does it look like?
I just tried adb sideload <file.zip> while in recovery mode and i'm getting this
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
When check adb devices its shows that device is unauthorized. But it's only unauthorized in recovery mode.
Actually looks like I have a problem with recovery mode. Instead I'm getting "No command" screen. It's not even getting into recovery
To perform a ADB Sideload - what is used to flash a Stock ROM - phone must get booted into Sideload mode at 1st
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP>
adb reboot
Oh cool. Didn't know that I could reboot stratight to sideload and bypass initial recovery menu. Thank you!
As for my previous issue with "No command" error on recovery boot, I managed to resolve it. When It's gets to "No command" screen, you need to hold Power + Volume Down just long enough to tap Volume Up. And then recovery menu will appear. So Press Power + Volume Down and then tap Volume Up.
When I tried to sideload su binary with
Code:
adb sideload <file.zip>
On the mobile screen i'm getting this error
Code:
E:failed to verify whole-file signature. Update package verification took 0.5 s ( result 1)
E:Signature verification failed
E: error: 21
Looks like recovery not allowing to install unsigned packages. Is there a way around it? Do I need to source another su binary or there is a way to sign it?
Ok. I think I'm getting closer to the core issue. I thought that I rooted the device, but I only unlocked the bootloader. So device is not rooted. As per original thread topic, looks like there is still no TWRP yet and boot.img is not accessible to modify. Tried to get boot.img directly from the device, but getting - permission denied.
Any other walkarounds i should try?
SU binary isn't a signed package. It's a ~110KB file you have to push onto Android OS, preferred to /data/local/tmp directory and afterwards have to make it executable.
I've downloaded Chainfire SuperSu Zip packages, unpacked it and got a su file from arm64 folder. As you mentioned, su file is 108.5KB =)
I've pushed it to /data/local/tmp and made it executable
Code:
S22FLIP:/ $ ls -la /data/local/tmp
total 114
drwxrwxrwx 2 shell shell 3488 2022-12-22 09:36 .
drwxr-x--x 4 root root 3488 1970-01-01 12:15 ..
-rwxrwxrwx 1 shell shell 108496 2008-02-29 03:33 su
Maybe I'm missing something, I still get
Code:
S22FLIP:/ $ su
/system/bin/sh: su: inaccessible or not found
You must tell Android where the SU binary is located
Code:
cd /data/local/tmp & su
or
Code:
/data/local/tmp/su
jwoegerbauer said:
You must tell Android where the SU binary is located
Code:
cd /data/local/tmp & su
or
Code:
/data/local/tmp/su
Click to expand...
Click to collapse
Hi. I am trying to root the phone. I tried with QFIL to get the boot.img file with no luck.... I am trying now with su. I put the su binary where you said and execute it.
Now what should I do? If you can help me, I will be grateful
IMO you can't root a phone ( a conglomerat of hardware pieces ) but only enable Android OS to run system commands as root ( will say with elevated rights if those are required ) by means of su.
Knowing this you would open a terminal window in Android and type out
Code:
<FULLPATH-TO-SU-BINARY-HERE>/su -c "<SHELL-COMMAND-THAT-REQUIRES-ELEVATED-RIGHTS-HERE>"
Example:
Code:
/data/local/tmp/su -c "mount -o remount,rw -t auto /system"
jwoegerbauer said:
IMO you can't root a phone ( a conglomerat of hardware pieces ) but only enable Android OS to run system commands as root ( will say with elevated rights if those are required ) by means of su.
Knowing this you would open a terminal window in Android and type out
Code:
<FULLPATH-TO-SU-BINARY-HERE>/su -c "<SHELL-COMMAND-THAT-REQUIRES-ELEVATED-RIGHTS-HERE>"
Example:
Code:
/data/local/tmp/su -c "mount -o remount,rw -t auto /system"
Click to expand...
Click to collapse
Doesn't work. It looks like the su binary doesn't grant system commands root
I really don't know what to do......
C:\Users\HieAnh>adb root
restarting adbd as root
C:\Users\HieAnh>adb remount
Not running as root. Try "adb root" first.
Click to expand...
Click to collapse
after i do :"adb root" to cmd,
then i get :"restarting adbd as root"
next i do :"adb remount"
but i get :"Not running as root. Try "adb root" first."
a big question for this problem
my phone is rooted, switch ro.secure=0, ro.debuggle=1
pls help me
What response do you get when you type su in shell?
ze7zez said:
What response do you get when you type su in shell?
Click to expand...
Click to collapse
i get :
C:\Users\HieAnh>adb shell
gracerlte:/ $ su
gracerlte:/ #
Click to expand...
Click to collapse
The ADB driver does not care at all whether phone's Android is rooted or not. As you correctly stated one have to run adb root for ADB to gain root access device's Android.
I don't want to examine why adb root in your case doesn't work.
Anyways the following should be a workaround:
Code:
adb devices
adb shell "su -c 'mount -o remount,rw /system'"
...
...
jwoegerbauer said:
The ADB driver does not care at all whether phone's Android is rooted or not. As you correctly stated one have to run adb root for ADB to gain root access device's Android.
I don't want to examine why adb root in your case doesn't work.
Anyways the following should be a workaround:
Code:
adb devices
adb shell "su -c 'mount -o remount,rw /system'"
...
...
Click to expand...
Click to collapse
hmm, i just run
adb pull /data/data
Click to expand...
Click to collapse
but i get
/data/data/: 0 files pulled, 0 skipped.
Click to expand...
Click to collapse
why ?
You have to mount /data partitton as RW.