Hi, I want ClockworkMod Recovery to run some commands when it boots. This can be done by placing a file named extendedcommand in /cache/recovery/.
My problem is, I cannot put extendedcommand in /cache/recovery/ via adb push without root.
Is there a way around this? I'm basically creating a root installer, hence why I cannot have root in the first place.
Is it possible to get ClockworkMod Recovery to check for extendedcommand in the SD card or another folder when I can push via adb push?
Thanks.
Related
I've been trying to root my Samsung Galaxy Tab 10.1 WiFi but keep running into the same error.
I push'd the root zip file package into /sdcard via ADB. I can see this file when I browse the directory with a file manager.
The problem is I can't install the zip via the stock recovery because it won't mount sdcard. I get the following error when I select "install zip": unknown volume for path [/sdcard]
Anyone have any ideas? I'm on a Mac with no Windows machine around, so it seems my options are pretty limited.
Does anyone know of a way to manually flash clockworkmod without root? It doesn't look like there's any other way to install the root zip in the stock recovery. Am I just screwed?
So it seems that my HTC ONE has no OS installed, I am able to get to the HTC logo and thats it. I reboot into bootloader and are able to install CWM and TWRP but no luck installing ARHD rom via adb sideload method, it just fails. Any hints on how to install a rom either stock or otherwise? i have a cwm backup of my stock rom rooted odex on my computer but it is not a flashable zip. Any help will be greatly appreciated. Thanks in advance.
(i have a mac if that matters)
if you aren't back on cwm flash that recovery.
boot to it
push your backup to the phone with ./adb push /foldername/* /sdcard/clockworkmod/backup might be backups, I can't remember, but you can check with adb shell
./adb shell
cd /sdcard/clockworkmod
ls (that is a lowercase L)
that should give you a directory listing.
after you've successfully pushed the backup reboot to recovery again and restore it.
This should do the trick
gunnyman said:
if you aren't back on cwm flash that recovery.
boot to it
push your backup to the phone with ./adb push /foldername/* /sdcard/clockworkmod/backup might be backups, I can't remember, but you can check with adb shell
./adb shell
cd /sdcard/clockworkmod
ls (that is a lowercase L)
that should give you a directory listing.
after you've successfully pushed the backup reboot to recovery again and restore it.
This should do the trick
Click to expand...
Click to collapse
I am in the same situation. Can not get my phone to roboot. I have a rom to push but I dont know how to use ADB commands. I can get to command prompt but them I am totally lost. Can you give me a quick step by step?
adb push filename /sdcard
gunnyman said:
if you aren't back on cwm flash that recovery.
boot to it
push your backup to the phone with ./adb push /foldername/* /sdcard/clockworkmod/backup might be backups, I can't remember, but you can check with adb shell
./adb shell
cd /sdcard/clockworkmod
ls (that is a lowercase L)
that should give you a directory listing.
after you've successfully pushed the backup reboot to recovery again and restore it.
This should do the trick
Click to expand...
Click to collapse
Hy gunnyman, when I push the folder to the sd card it always decompresses and send the individual files to the system not the full backup folder so i can select it from the backups menu. this is the command I used ./adb push may6.zip /sdcard/clockworkmod/backup
I also pushed the decompressed files to the sd card since it looks like it instals all files needed for os to work with the following command ./adb push may6.zip /sdcard
I reboot system but still stuck on HTC logo.
May6 is the name of my backup and when i use the ls command it has a .zip to the end.
So can you let me know how to sent the complete folder to the phone to be placed on the backup folder and thus be able to be selected under the cwm menu? Thank you so much
Unzip it. Send entire folder uncompressed
You don't restore a backup the same way you flash a rom. It's a separate menu option in recovery
gunnyman said:
Unzip it. Send entire folder uncompressed
You don't restore a backup the same way you flash a rom. It's a separate menu option in recovery
Click to expand...
Click to collapse
yes its unzipped. took off the .zip name and sent it to the backup folder and it still sends the uncompressed files. Once I go to restore from backup folder I get a -System/ and -Meta-INF/ files and no file with -May6/ or something like that. So i try to restore from -system/ but it says md5 sum dont match.
Any ideas?
No, I don't sorry
my device intex cloud m6 1gb ram 8gb rom is not rooting.Please tell how to root
How to root Intex Cloud M6 8gb and 16gb smartphones.
Hello there,
This query was posted a long time ago by you and i am not sure if you have found the solution or not. But as far as i am aware, it is pretty hard to root this device. It runs on a Spreadtrum chipset sc7731. However, recently i figured out how to root this device.
It seems like that the device's default.prop file comes with a configuration :
Code:
ro.secure=1
which makes it impossible to root this device with absolutely any rooting software out there including the one-click apps.
To be able to root this device, the only efficient way is to replace the stock recovery with a custom one, deleting the default su binary file inside the /system/xbin folder as well as in the /system/bin folder, installing the SuperSU.zip file and finally by installing the Kingroot apk which will ultimately root the device.
I personally prefer the TWRP but there is no official release out there for this device. So, i ported a custom recovery for it in my spare time ( It may appear somewhat ridiculous but i had nothing more interesting to do so i changed the layout :silly
I have attached the recovery file below.
After you have downloaded the recovery as well as the SuperSU.zip, here are the steps to root it:-
Download the minimal adb fastboot for windows. You may google it, its available easily. (It turns out it may be the only tool that may work effectively in case your device is not getting recognized by any other adb.)
Rename the recovery as twrp and place it inside the Minimal adb and fastboot folder.
Connect the device via a USB cable and make sure adb debugging is on inside the developer options.
Now open the Minimal adb and fastboot tool and type the following commands inside the prompt:-
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery twrp.img
fastboot reboot
Type the commands in the exact sequence. Your device will boot normally. Now, time to checkout the recovery. Type the following command inside the prompt.
Code:
adb reboot recovery
In a few seconds, you will have the custom twrp booted in front of you. Now, open the Mount tab inside the recovery and check the system option within it.
Head back to the recovery homescreen and open the Advanced tab which is followed by opening the File Manager tab.
Inside the file manager, follow the path to the pre-existing su binary file, i.e /system/xbin and delete it. Do the same with the su file present on /system/bin.
Now, head back to the recovery home ,open Install tab and select the SuperSU.zip wherever you placed it and swipe to confirm the installation.
Reboot system. (It will probably boot without the logo so don't worry if it does.)
Now Google the Kingroot.apk, download it and install it. Give it a run, it will probably fail.
So get rid of the other superuser app i.e, SuperSU app via the option present inside it, i.e "Cleanup to install other superuser app" or something like that.
After a few seconds, it will disappear from the device and probably the same might happen with the Kingroot app.
Reboot the device.
Re-install the Kingroot app and run it again.
Congrats! You just rooted your device. Go ahead and check the root via an app like Rootchecker.
Here is the custom recovery file: -
HTML:
https://adarshkushwah.github.io/Custom-recovery-for-Intex-Cloud-M6-8gb-and-16gb/
If you have any query regarding this, do let me know. :good:
(I would be glad if you or anyone who finds this post useful would thank me) Cheers!
Im trying to flash a file from twrp but the files simply don't appear in it. It appear only when I access it through the computer.
Anyway, how to change that ?
maybe because the file is not a flashable zip? With TWRP you can flash flashable zip or img files for partitions.. Also, be sure to access the /sdcard from the TWRP file manager when you tap Install. If it's and External SD you could have to mount it before..
EDIT:
Last but not least, if you are sure the zip is flashable you could use sideload.. From TWRP go to Advanced / Sideload and start sideload.. Open a command prompt into your PC and with the device attached to it use
Code:
adb sideload G:/whatever/the/file/is/into/your/PC/file.zip
Naturally you need adb
brainvision said:
maybe because the file is not a flashable zip? With TWRP you can flash flashable zip or img files for partitions.. Also, be sure to access the /sdcard from the TWRP file manager when you tap Install. If it's and External SD you could have to mount it before..
EDIT:
Last but not least, if you are sure the zip is flashable you could use sideload.. From TWRP go to Advanced / Sideload and start sideload.. Open a command prompt into your PC and with the device attached to it use
Code:
adb sideload G:/whatever/the/file/is/into/your/PC/file.zip
Naturally you need adb
Click to expand...
Click to collapse
It says "failed". Despite that, even if it was an image, shouldn't I see the file at least ? There's an option in twrp which I can choose between zip and images...
The file is the XposedInstaller_3.0_alpha4.apk, xposed-v86-sdk23-arm.zip.asc and eu.chain.fire.supersu_v2.78-278_Android-2.1.apk
No one is a zip as you can see..
Liooh said:
The file is the XposedInstaller_3.0_alpha4.apk, xposed-v86-sdk23-arm.zip.asc and eu.chain.fire.supersu_v2.78-278_Android-2.1.apk
Click to expand...
Click to collapse
You should download zip file instead of the asc file if you want to flash the xposed framework.the apk files you have to install it on the phone and you don't have to flash it on the recovery
Hello there,
First-off, i would like to thank the Chainfire for the SuperSU files and the Kingroot for making the rooting process easier.
As far as i am aware, it is pretty hard to root this device. It runs on a Spreadtrum chipset sc7731. However, recently i figured out how to root this device.
->> REQUIREMENTS:
1. Minimal adb and fastboot tool.
2. Kingroot app.
3. As usual, a working brain.
->> METHOD:
It seems like that the device's default.prop file comes with a configuration :
Code:
ro.secure=1
which makes it impossible to root this device with absolutely any rooting software out there including the one-click apps.
To be able to root this device, the only efficient way is to replace the stock recovery with a custom one, deleting the default su binary file inside the /system/xbin folder as well as in the /system/bin folder, installing the SuperSU.zip file and finally by installing the Kingroot apk which will ultimately root the device.
I personally prefer the TWRP but there is no official release out there for this device. So, i ported a custom recovery for it in my spare time ( It may appear somewhat ridiculous but i had nothing more interesting to do so i changed the layout :silly
I have attached the recovery file below as well as the SuperSU.zip files below.
After you have downloaded the recovery as well as the SuperSU.zip, here are the steps to root it:-
Download the minimal adb fastboot for windows. You may google it, its available easily. (It turns out it may be the only tool that may work effectively in case your device is not getting recognized by any other adb.)
Rename the recovery as twrp and place it inside the Minimal adb and fastboot folder.
Connect the device via a USB cable and make sure adb debugging is on inside the developer options.
Now open the Minimal adb and fastboot tool and type the following commands inside the prompt:-
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery twrp.img
fastboot reboot
Type the commands in the exact sequence. Your device will boot normally. Now, time to checkout the recovery. Type the following command inside the prompt
.
Code:
adb reboot recovery
In a few seconds, you will have the custom twrp booted in front of you. Now, open the Mount tab inside the recovery and check the system option within it.
Head back to the recovery homescreen and open the Advanced tab which is followed by opening the File Manager tab.
Inside the file manager, follow the path to the pre-existing su binary file, i.e /system/xbin and delete it. Do the same with the su file present on /system/bin.
Now, head back to the recovery home ,open Install tab and select the SuperSU.zip wherever you placed it and swipe to confirm the installation.
Reboot system. (It will probably boot without the logo so don't worry if it does.)
Now Google the Kingroot.apk, download it and install it. Give it a run, it will probably fail.
So get rid of the other superuser app i.e, SuperSU app via the option present inside it, i.e "Cleanup to install other superuser app" or something like that.
After a few seconds, it will disappear from the device and probably the same might happen with the Kingroot app.
Reboot the device.
Re-install the Kingroot app and run it again.
Congrats! You just rooted your device. Go ahead and check the root via an app like Rootchecker.
The custom recovery file has been attached and happens to be in the .zip format so kindly extract the recovery from it.
If you have any query regarding this, do let me know. :v
(I would be glad if you or anyone who finds this post useful would thank me) Cheers!