I did a backup with the TRWP recovery but I can't find the directory "TWRP" in the sd card, neither in the explorer nor in the pc when connecting. However, the directory is there if I look from the recovery.
diegodm said:
I did a backup with the TRWP recovery but I can't find the directory "TWRP" in the sd card, neither in the explorer nor in the pc when connecting. However, the directory is there if I look from the recovery.
Click to expand...
Click to collapse
Do you see it in adb shell? Or did you try do adb pull it?
k-kuchen said:
Do you see it in adb shell? Or did you try do adb pull it?
Click to expand...
Click to collapse
I see it in the adb shell, but cannot access to it, "Permission denied". I can't adb pull it, it says that the remote object doesn't exist.
Are you doing that while in TWRP or in Android? Your problem might be related to SELinux contexts.
_that said:
Are you doing that while in TWRP or in Android? Your problem might be related to SELinux contexts.
Click to expand...
Click to collapse
I was doing it in Android, but now in TWRP i've been able to adb pull it.
Is there any reason I should be worried about that SELinux thing?
Are you using the latest version of TWRP from here: http://forum.xda-developers.com/showthread.php?p=57672469 ?
lost101 said:
Are you using the latest version of TWRP from here: http://forum.xda-developers.com/showthread.php?p=57672469 ?
Click to expand...
Click to collapse
No, I'm using the 2.8.6.0 downloaded from the TWRP site. Should I use the GPE version from your link? (I have GPE firmware flashed)
diegodm said:
No, I'm using the 2.8.6.0 downloaded from the TWRP site. Should I use the GPE version from your link? (I have GPE firmware flashed)
Click to expand...
Click to collapse
Yeah, try that.
lost101 said:
Yeah, try that.
Click to expand...
Click to collapse
Wow, I had no idea that a recovery could be so beautiful Well, now I've done a backup and I can see it perfectly in my PC. Thanks!
Related
So, I updated to 2.3.4 today, and after a rebbot into recovery, CWM was gone.
No problem, I tought, and used fastboot to flash it back.
fastboot went OK, but when I tried to use CWM from recovery, I got stucked at the "stock" recovery (android with a exclamation mark). Is anyone else facing this?
Click to expand...
Click to collapse
NVM this first part, solved that.
Also, I can´t get adb to work, tried pushing some files and got permission denied; abd remount gave me a "remount failed: Operation not permitted" error.
Yeah, having the same problem here. The 'remount failed..' error is because the update patched our boot.img and now they are no longer 'insecure.' I think I might fix it so we all can have root again. I've also had better luck when running a shell script and physically moving apps, etc to the places i want them...then have to chmod, etc...freaking sucks.
If you need any help with some workarounds shoot me a message..also have some personal scripts that get everything going
du5t3r said:
Yeah, having the same problem here. The 'remount failed..' error is because the update patched our boot.img and now they are no longer 'insecure.' I think I might fix it so we all can have root again. I've also had better luck when running a shell script and physically moving apps, etc to the places i want them...then have to chmod, etc...freaking sucks.
If you need any help with some workarounds shoot me a message..also have some personal scripts that get everything going
Click to expand...
Click to collapse
Thanks, I spent a long time yesterday trying to solve this.
Finally, I gave up and installed Root Explorer. Let me know if you have any progress with this.
Use RootExplorer after flash to rename the recovery.sh to recovery-no.sh its found in the ETC folder.
Try choosing erase recovery in the rom managers settings then flash.
kaizxclusive said:
Use RootExplorer after flash to rename the recovery.sh to recovery-no.sh its found in the ETC folder.
Try choosing erase recovery in the rom managers settings then flash.
Click to expand...
Click to collapse
Hmm, I found a install-recovery.sh, is that one?
I am not using rom manager...
gasparzim said:
Hmm, I found a install-recovery.sh, is that one?
I am not using rom manager...
Click to expand...
Click to collapse
yes, just rename it to something like install-recovery.sh.old
Bajo76 said:
yes, just rename it to something like install-recovery.sh.old
Click to expand...
Click to collapse
Thanks, looks like it´s working now.
Hey
I have a tf101g with prime and CWM but i want to unroot it back to factory.
I tried the one click unroot method but the bat closes and no menu option ever turns up. What options do i have here ?
thefollower said:
Hey
I have a tf101g with prime and CWM but i want to unroot it back to factory.
I tried the one click unroot method but the bat closes and no menu option ever turns up. What options do i have here ?
Click to expand...
Click to collapse
Download the stock firmware (WW or US). Unzip it once (it will still be a zip).
Place said file where you can flash with your recovery.
Flash stock firmware with CWM.
Reboot.
frederuco said:
Download the stock firmware (WW or US). Unzip it once (it will still be a zip).
Place said file where you can flash with your recovery.
Flash stock firmware with CWM.
Reboot.
Click to expand...
Click to collapse
I can't. I click choose zip from sdcard, and i get E:Can't mount /sdcard/
thefollower said:
I can't. I click choose zip from sdcard, and i get E:Can't mount /sdcard/
Click to expand...
Click to collapse
What version of CWM are you on and how did you install it?
I am assuming you mustve used ROM Manager to update it...See here: http://forum.xda-developers.com/showthread.php?t=1671598
You should use PERI to push a working recovery and then flash it using that.
frederuco said:
What version of CWM are you on and how did you install it?
I am assuming you mustve used ROM Manager to update it...See here: http://forum.xda-developers.com/showthread.php?t=1671598
You should use PERI to push a working recovery and then flash it using that.
Click to expand...
Click to collapse
Well i ran rom manager but it did work (as in it did update). I'm on version v6.0.1.3 ?
thefollower said:
Well i ran rom manager but it did work (as in it did update). I'm on version v6.0.1.3 ?
Click to expand...
Click to collapse
Also (my edit was not working)
I'm on android 3.2 which i think is not ICS operating system right?
thefollower said:
Well i ran rom manager but it did work (as in it did update). I'm on version v6.0.1.3 ?
Click to expand...
Click to collapse
thefollower said:
Also (my edit was not working)
I'm on android 3.2 which i think is not ICS operating system right?
Click to expand...
Click to collapse
Yes, 3.2 is Honeycomb. I am not sure if Wolf's Exploit works on Honeycomb or not, but I would give PERI a try (linked in my previous post).
frederuco said:
Yes, 3.2 is Honeycomb. I am not sure if Wolf's Exploit works on Honeycomb or not, but I would give PERI a try (linked in my previous post).
Click to expand...
Click to collapse
Ok i tried it, didn't work my tablet is asking for a password which i've never set =/ Won't let me passed it either. Tried and failed about 20 times to guess one and it doesnt give me an option to change my password.
Have i bricked it ? =/
thefollower said:
Ok i tried it, didn't work my tablet is asking for a password which i've never set =/ Won't let me passed it either. Tried and failed about 20 times to guess one and it doesnt give me an option to change my password.
Have i bricked it ? =/
Click to expand...
Click to collapse
Is this the password for the Android OS, or is it an encryption password?
If it is an encryption password before the Android login, you will need to do a format data (wipe the entire /data/ partition including /data/media/ a.k.a. /sdcard/). If your internal memory was encrypted then it would make sense why CWM cannot mount the /sdcard/.
Can you install zips from the microSD with your recovery? If so you could try flashing another recovery zip file and see if that works. You could also try to use adb to install another recovery when you are in CWM.
frederuco said:
Is this the password for the Android OS, or is it an encryption password?
If it is an encryption password before the Android login, you will need to do a format data (wipe the entire /data/ partition including /data/media/ a.k.a. /sdcard/). If your internal memory was encrypted then it would make sense why CWM cannot mount the /sdcard/.
Can you install zips from the microSD with your recovery? If so you could try flashing another recovery zip file and see if that works. You could also try to use adb to install another recovery when you are in CWM.
Click to expand...
Click to collapse
I have sinced fixed it, i re-ran the .bat file and did it again seems to solve it ^_^ Thanks!
thefollower said:
I have sinced fixed it, i re-ran the .bat file and did it again seems to solve it ^_^ Thanks!
Click to expand...
Click to collapse
Sweet
Hey!
i just rooted my phone by this way : http://www.modaco.com/topic/366771-root-your-moto-g-option-1-superboot/
and it works!
but now i need to install a custom recovery so i can install custom rom too!
how could i ? " i tried to use rom manager but he shows me that my device is not supported officially by CWR
any help ?
Pir4t3 said:
Hey!
i just rooted my phone by this way : http://www.modaco.com/topic/366771-root-your-moto-g-option-1-superboot/
and it works!
but now i need to install a custom recovery so i can install custom rom too!
how could i ? " i tried to use rom manager but he shows me that my device is not supported officially by CWR
any help ?
Click to expand...
Click to collapse
ok solved!
but i got another problem
i can't mount usb storage at the recovery mode!
i flashed CWM And TW .. and the same
how can i solve it ?
Pir4t3 said:
ok solved!
but i got another problem
i can't mount usb storage at the recovery mode!
i flashed CWM And TW .. and the same
how can i solve it ?
Click to expand...
Click to collapse
What do you mean by usb storage? You can flash your rom by sideloading it under your recovery.
adb sideload rom-name.zip
1pilo said:
What do you mean by usb storage? You can flash your rom by sideloading it under your recovery.
adb sideload rom-name.zip
Click to expand...
Click to collapse
when u open the recovery go to mount then mount usb storage
it makes ur pc read your phone so you can transfer some files
i used it many times in my old phone " Nexus s "
and I'm using mac so i don't this command will work
Pir4t3 said:
when u open the recovery go to mount then mount usb storage
it makes ur pc read your phone so you can transfer some files
i used it many times in my old phone " Nexus s "
and I'm using mac so i don't this command will work
Click to expand...
Click to collapse
I'm also using a mac. if your downloading the sdk from google u go to sdk/platform-tools and theres the adb file.
Next you need to place the rom file in the same folder
then you need to go to your recovery under install from sideload
and then in your terminal
./adb sideload rom-name.zip
after transfering from mac it gets installed directly
1pilo said:
I'm also using a mac. if your downloading the sdk from google u go to sdk/platform-tools and theres the adb file.
Next you need to place the rom file in the same folder
then you need to go to your recovery under install from sideload
and then in your terminal
./adb sideload rom-name.zip
after transfering from mac it gets installed directly
Click to expand...
Click to collapse
Thanks!
so if i want to transfer a file without installing it " if it zip too "
coz i want to try it .. but i just wanna try that it works without installing a rom
is it possible ?
and again thanks!
Pir4t3 said:
Thanks!
so if i want to transfer a file without installing it " if it zip too "
coz i want to try it .. but i just wanna try that it works without installing a rom
is it possible ?
and again thanks!
Click to expand...
Click to collapse
that should be tricky trying a rom without installing it.
The only solution I know would be doing a backup before. Then installing it and then restoring the backup.
There should be some other recovery where u can manage your roms. but I cant remember.
1pilo said:
that should be tricky trying a rom without installing it.
The only solution I know would be doing a backup before. Then installing it and then restoring the backup.
There should be some other recovery where u can manage your roms. but I cant remember.
Click to expand...
Click to collapse
i tried CMW and TW .. same thing happened!
i just wanna say Thank you again
Help i've accidentally deleted my backup OS on my nexus 5. i am using CWM. i was trying to put android L on my nexus 5 and it couldnt install. so i went back to the recovery mode in attempt to restore my device to the backup i made. i couldnt find the backup on my sd card...weird. so i am stuck. trying to find a way to get my device back.
AHMEDNATOR said:
Help i've accidentally deleted my backup OS on my nexus 5. i am using CWM. i was trying to put android L on my nexus 5 and it couldnt install. so i went back to the recovery mode in attempt to restore my device to the backup i made. i couldnt find the backup on my sd card...weird. so i am stuck. trying to find a way to get my device back.
Click to expand...
Click to collapse
If your backup got deleted then it is lost forever. Flash cwm again then flash the rom you used before L
You should keep a copy of the backup off your device. Maybe third time will be the charm.
http://forum.xda-developers.com/showthread.php?t=2750414
Wakamatsu said:
You should keep a copy of the backup off your device. Maybe third time will be the charm.
http://forum.xda-developers.com/showthread.php?t=2750414
Click to expand...
Click to collapse
i kept a copy of it but when i went back to try and restore with that copy. i didnt see it any more. the bad luck i get with android phones
bitdomo said:
If your backup got deleted then it is lost forever. Flash cwm again then flash the rom you used before L
Click to expand...
Click to collapse
how to flash it again if i have no way to get back in my device?
AHMEDNATOR said:
how to flash it again if i have no way to get back in my device?
Click to expand...
Click to collapse
What do you mean by "get back in my device"? You cant turn it on?
bitdomo said:
What do you mean by "get back in my device"? You cant turn it on?
Click to expand...
Click to collapse
scratch that. i can turn it off and back on. i tried adb sideload but i cant seem to be able to push a rom on the nexus.
AHMEDNATOR said:
scratch that. i can turn it off and back on. i tried adb sideload but i cant seem to be able to push a rom on the nexus.
Click to expand...
Click to collapse
Have you flashed cwm?
bitdomo said:
Have you flashed cwm?
Click to expand...
Click to collapse
yeah i have CWM installed
AHMEDNATOR said:
yeah i have CWM installed
Click to expand...
Click to collapse
What is the command you use to push the rom?
bitdomo said:
What is the command you use to push the rom?
Click to expand...
Click to collapse
the rom i downloaded is called something hammerhead. i renamed it to Rom.zip . when i am in my command prompt. i type "adb push Rom.zip" or when i do the sideload, i do "adb sideload Rom.zip"
AHMEDNATOR said:
the rom i downloaded is called something hammerhead. i renamed it to Rom.zip . when i am in my command prompt. i type "adb push Rom.zip" or when i do the sideload, i do "adb sideload Rom.zip"
Click to expand...
Click to collapse
There is the problem. You didnt tell where to push the zip.
Use this:
adb push rom.zip /data/media/0
after that you should see the rom.zip on the internal storage
bitdomo said:
There is the problem. You didnt tell where to push the zip.
Use this:
adb push rom.zip /data/media/0
after that you should see the rom.zip on the internal storage
Click to expand...
Click to collapse
alright, let me give it a try.
bitdomo said:
There is the problem. You didnt tell where to push the zip.
Use this:
adb push rom.zip /data/media/0
after that you should see the rom.zip on the internal storage
Click to expand...
Click to collapse
it says "error: cloased"
AHMEDNATOR said:
it says "error: cloased"
Click to expand...
Click to collapse
running
adb devices
command showes you any output?
bitdomo said:
running
adb devices
command showes you any output?
Click to expand...
Click to collapse
yeah, it shows some numbers and letters which i assume is my device and next to it, it says "sideload"
AHMEDNATOR said:
yeah, it shows some numbers and letters which i assume is my device and next to it, it says "sideload"
Click to expand...
Click to collapse
Then use
adb sideload rom.zip
command
bitdomo said:
Then use
adb sideload rom.zip
command
Click to expand...
Click to collapse
i get a bunch of stuff and commands come up in the command prompt. i ll try to take a picture for you
bitdomo said:
Then use
adb sideload rom.zip
command
Click to expand...
Click to collapse
there it is
If you don't have path variables set up make sure your rom.zip is in the platform-tools folder of the sdk.
NM. Looks like you do have path variables set up. That second longer error in you screen shot is because you put a space after rom. The first looks like it can't read it because your typing the name wrong. Remember it's case sensitive so Rom.zip and rom.zip are two different things.
Did any if you try installing OTA from TWRP?
I'm tempted to but seeing as it's installed block by block stuff could go wrong when you've modified /system, /vendor and/or /product...
ante0 said:
Did any if you try installing OTA from TWRP?
I'm tempted to but seeing as it's installed block by block stuff could go wrong when you've modified /system, /vendor and/or /product...
Click to expand...
Click to collapse
i have tried but can't get thru..keeps getting error.
Sent from my Mate 9 using XDA Labs
eddmecha said:
i have tried but can't get thru..keeps getting error.
Sent from my Mate 9 using XDA Labs
Click to expand...
Click to collapse
Did you try editing the updater-script?
I was trying to make a flashable zip, found this python script (sdat2img) but doesn't work with OTA :/
Well then, its probably using "huawei-only" commands.
ante0 said:
Did you try editing the updater-script?
I was trying to make a flashable zip, found this python script (sdat2img) but doesn't work with OTA :/
Well then, its probably using "huawei-only" commands.
Click to expand...
Click to collapse
hmm never tried edit the script.
Maybe someone have to try sideload like OnePlus.
Enable sideload in twrp and in adb type: adb sidload update.zip
And use latest Google adb not minimal adb https://developer.android.com/studio/releases/platform-tools.html
Tried, but no success.
Tried with fastboot - same result.
Must have kernel sources and build new TWRP.
Until then - patiently waiting