Remote wipe does not work - Samsung Captivate Glide

When I try to issue a wipe command using Cerberus or Android Lost it does not work. The phone shuts down as it's supposed to but then CWM recovery displays and it shows the error: "E: Invalid command argument".
If I go to the Privacy menu and choose Factory Data Reset it works correctly. After shutting down it shows the picture with the box and robot, then it reboots and it has been wiped. It also works if I use CWM Recovery to start the wipe.
I first had the problem with Osimood. I then tried INC3PTiON and also went back to stock using the method from the Development sticky.
Is this something to do with CWM? Can I try a different version of CWM? In Recovery it shows CWM-based Recovery v5.0.2.7.

Could you please try remote wipe on your Glide and see if it works?
If you do a CWM backup before you wipe you can just restore the backup to get back to normal.
You could use Cerberus, AndroidLost or LookOut. Anything that allows you to remote wipe your phone.

Related

[Q] Problem with ClockworkMod Recovery

Problem with ClockworkMod Recovery
I was trying to install MIUI ROM but after performing a data wipe I got an
E: unknown volme for path [sd/ext]
Back Menu Button Disabled
Davik Cache wiped
message.
I'm now not able to use any of the options in the first clockwork mod recovery screen even though I can freely move throughout them. Whenever I choose one the background remains but nothing happens.
Any ideas on how to fix this? I'm afraid to reboot since I have no ROM installed.
take the battery out, put it back in then power on holding the volume down button then get back in recovery wipe again then flash again

recovery loop problem

I now cannot get into an operating system. The device loads FFF 1.4a says "booting" goes blank for a little while then comes back to the 1.4a screen and says "booting" again and loads up TWRP. This is how I got to this point:
I recently decided to go from an older CM7 rom to a new jb one.
Because I had an older version of FFF and had a CWM recovery, I downloaded the new version of FFF (1.4a) and the newest version of TWRP (2.2.0) (flashable zip file) as well as the new jellybean rom and jb gapps. I checked all md5s prior to doing anything.
I booted into recovery and created a backup in CWM. I then cleared cache and Davlic cache and installed FFF 1.4a. I then rebooted to CM7. After loading CM7, I rebooted into recovery, cleared cache and davlic cache and installed TWRP 2.2.0. I then rebooted into CM7, rebooted into recovery. I then cleared cache, davlic cache, factory reset, and wiped system. I then installed CM10 and jb gapps and attempted to reboot to system, but have not ever been able to get there.
I have tried installing the CM7 rom I had before, no difference, CM9 rom, no difference. I tried to use a recovery file I had, still no good.
Adb does not seem to behaving properly as well. I can't seem to be able to get the device into fastboot mode for one. In TWRP I can see the device as the following:
4B8E000600000001 recovery
when I try to change the bootmode, this is how it behaves:
adb shell
~ # <-[6n idme bootmode 4002
/sbin/sh: idme: not found
KFU also seems to not be much help at changing the bootmode. I have tried older version as sited elsewhere (0.9, 0.3), but these fair no better.
Also, In my haste and desire to get this working I thought,"maybe there is some conflict with the sd card", so I wiped that only to realize while wiping that I never backed up my recovery files, "doh!".
Also, I have full battery.
I am a noob, so I could have done anything wrong. Any help would be appreciated.
When you get to the bootloader screen select boot normal in the boot menu by quickly depressing your power button a few times if it does not boot normal then flash the bootloader again in recovery http://forum.xda-developers.com/showthread.php?t=1632375 also you will have to mount your sdcard in twrp to do so make sure there are no checks in the boxes of system and data then mount transfer 1.4a bootloader a new ROM and gapps then unmount flash bootloader reboot it get back to twrp wipe factory reset wipe cache wipe dalvik wipe system flash ROM flash gapps select reboot if prompted select system see where your at after that
http://forum.xda-developers.com/showpost.php?p=29186989&postcount=157
Thanks
Thepooch said:
When you get to the bootloader screen select boot normal in the boot menu by quickly depressing your power button a few times if it does not boot normal then flash the bootloader again in recovery http://forum.xda-developers.com/showthread.php?t=1632375 also you will have to mount your sdcard in twrp to do so make sure there are no checks in the boxes of system and data then mount transfer 1.4a bootloader a new ROM and gapps then unmount flash bootloader reboot it get back to twrp wipe factory reset wipe cache wipe dalvik wipe system flash ROM flash gapps select reboot if prompted select system see where your at after that
Click to expand...
Click to collapse
Thanks, I will try this when I get a chance.
Thanks
kinfauns said:
http://forum.xda-developers.com/showpost.php?p=29186989&postcount=157
Click to expand...
Click to collapse
Thanks for this as well, did not see this information anywhere else.
fixed
Yep, it was a bad FFF flash. All good now. Thanks for the help.

[Q] Phone won't restore

I had paranoid android installed on my phone running 4.1.2 and it kept crashing sometimes so I decided to go back to cm-10 which i used before but didn't prefer it. I did the exact same things I did last time but this time my phone would just stay at the cm-10 logo and never turn on. I had backup for paranoid android created before i flashed the cm-10 and so I tried restoring but it wouldn't work it my phone would turn off in middle of the restore. I tried that a few times and I just tried to retore the ORIGINAL 4.0 before i rooted my phone and it stopped in middle for that too and my phone just turned off. Idk what to do can anyone PLEASE HELP?? :crying:
I tried factory reset & clear data partition open it would also freeze in middle and turn off.
Also it says this at the bottom when i go to CWM recovery
E:can't open /cache/recovery/log
E:can't open /cache/recovery/log
E:can't open /cache/recovery/log/last_log
E:can't open /cache/recovery/log/last_log
PLEASE HELP ME CAN'T DO ANYTHING WITH THIS PHONE RIGHT NOW :crying:
You should try and redownload the ROM and place it at the root of your sdcard
I normally do...
Wipe Data/Factory reset
Wipe cache partition
install zip from sdcard
go to Advanced
Wipe dalvik cache
Wipe battery status
Fix permissions (just incase)
Reboot Device
wait about usually 3-8 minutes depends on the ROM. if it's longer then that then your stuck in a boot loop
this is all on done on CWMR v6.0.1.5
aplastar said:
You should try and redownload the ROM and place it at the root of your sdcard
I normally do...
Wipe Data/Factory reset
Wipe cache partition
install zip from sdcard
go to Advanced
Wipe dalvik cache
Wipe battery status
Fix permissions (just incase)
Reboot Device
wait about usually 3-8 minutes depends on the ROM. if it's longer then that then your stuck in a boot loop
this is all on done on CWMR v6.0.1.5
Click to expand...
Click to collapse
It wouldn't let me. That's the problem, anything I tried to do in recovery mode it would freeze and then turn off. And now it doesn't even go to recovery mode anymore! It just stays black the whole time. any help?
Last time I had this problem, I had to revert to stock using Odin and download mode.. works great now. It's a big hassle, but it is good to do a full reset every now and then. Then again, had so many problems with cwm that now I'm a twrp only man. That might help too.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

[Q] CWM v6.0.4.3 N7100 problem in supporting Stock 4.3 ROM restoration

I have an International version of Note 2 (N7100) rooted with CWM recovery 6.0.4.3 (touch) installed.
In order to analyze the wakelock problem (most of the time, the CPU is at 200Mhz rather than deep sleep when it is not used. Also "battery info" tells me the battery was mostly used by "Android OS"), I have to factory reset the device and flash to the stock 4.3 ROM. I monitored the newly setup phone for a day before I rooted it and install CWM recovery 6.0.4.3 for full system backup.
Happily used the phone for a week. After my son played with it for an afternoon, the wakelock problem comes back. Not sure what settings did he changed or apps he installed. So I go ahead backup the current rom and restore the phone from the previous backups.
Here was what I have done:
1. Boot into Clockworkmod recovery
2. Clear all partition / factory reset
3. Select Backup and restore.
4. Select the backup directory that I want to restore from (the one without wakelock problem)
5. Wait for the restoration process to finish
6. System reboots.
After system rebooted, it kept popping up "unfortunately com.google.process.gapps has stopped". The device was not usable, because the message will pop up again once I click OK to dismiss it. I then tried the following, but none of them works.
1. Restore from different backups
2. Enable "download service" from application manager. (It was not disabled)
3. Reset all apps settings from "Application manager" (menu)
Trying option 2 and 3 was a pain as the popup messages was blocking the screen, I have to be really quick to dismiss the message box and touch on the command.
BTW, the CWM recovery touch was installed from Odin, not from ROM manager. I experience the following problems:
1. Issue with "backup current ROM" command from "ROM manager". It cannot find /ex_sdcard when it goes to recovery.
2. It cannot find dalvik partition to wipe.
3. Backup to zip command does not work. It does backup the files and at the end it said the backup file is in /storage/sdcard/clockworkmod/image.zip. But I cannot find the zip file any where, including the external sd card.
Here is what I did to restore my phone to previous state with stock ROM:
1. Use Odin to flash the stock rom (samsung 4.3 for N7100), which will restore the stock recovery instead of the CWM recovery.
2. Reboot the device.
3. Use Odin to flash CWM recovery.
4. Reboot the device.
5. Go into recovery and restore only the /data partition.
6. Wipe /cache.
7. Reboot the device
8. Boot back to recovery and root the device.
Now I have the phone at my previous state.
Does it mean CWM recovery will not work with stock ROMs ? or I did something wrong.
Also, I still have not find out what was the cause for the wakelock problem in "Android OS". I have two backups where one has the problem and one does not. I have tried untar them and compare them with WinMerge, but there were a lots of files to go through.
fatice said:
I have an International version of Note 2 (N7100) rooted with CWM recovery 6.0.4.3 (touch) installed.
In order to analyze the wakelock problem (most of the time, the CPU is at 200Mhz rather than deep sleep when it is not used. Also "battery info" tells me the battery was mostly used by "Android OS"), I have to factory reset the device and flash to the stock 4.3 ROM. I monitored the newly setup phone for a day before I rooted it and install CWM recovery 6.0.4.3 for full system backup.
Happily used the phone for a week. After my son played with it for an afternoon, the wakelock problem comes back. Not sure what settings did he changed or apps he installed. So I go ahead backup the current rom and restore the phone from the previous backups.
Here was what I have done:
1. Boot into Clockworkmod recovery
2. Clear all partition / factory reset
3. Select Backup and restore.
4. Select the backup directory that I want to restore from (the one without wakelock problem)
5. Wait for the restoration process to finish
6. System reboots.
After system rebooted, it kept popping up "unfortunately com.google.process.gapps has stopped". The device was not usable, because the message will pop up again once I click OK to dismiss it. I then tried the following, but none of them works.
1. Restore from different backups
2. Enable "download service" from application manager. (It was not disabled)
3. Reset all apps settings from "Application manager" (menu)
Trying option 2 and 3 was a pain as the popup messages was blocking the screen, I have to be really quick to dismiss the message box and touch on the command.
BTW, the CWM recovery touch was installed from Odin, not from ROM manager. I experience the following problems:
1. Issue with "backup current ROM" command from "ROM manager". It cannot find /ex_sdcard when it goes to recovery.
2. It cannot find dalvik partition to wipe.
3. Backup to zip command does not work. It does backup the files and at the end it said the backup file is in /storage/sdcard/clockworkmod/image.zip. But I cannot find the zip file any where, including the external sd card.
Here is what I did to restore my phone to previous state with stock ROM:
1. Use Odin to flash the stock rom (samsung 4.3 for N7100), which will restore the stock recovery instead of the CWM recovery.
2. Reboot the device.
3. Use Odin to flash CWM recovery.
4. Reboot the device.
5. Go into recovery and restore only the /data partition.
6. Wipe /cache.
7. Reboot the device
8. Boot back to recovery and root the device.
Now I have the phone at my previous state.
Does it mean CWM recovery will not work with stock ROMs ? or I did something wrong.
Also, I still have not find out what was the cause for the wakelock problem in "Android OS". I have two backups where one has the problem and one does not. I have tried untar them and compare them with WinMerge, but there were a lots of files to go through.
Click to expand...
Click to collapse
I did not find the problem with restoration using CWM, but did find out what causes the wakelock: "Automatic call recorder Pro".
Disable the auto start function and battery drains is back to 1% per hour during standby.
fatice said:
I have an International version of Note 2 (N7100) rooted with CWM recovery 6.0.4.3 (touch) installed.
In order to analyze the wakelock problem (most of the time, the CPU is at 200Mhz rather than deep sleep when it is not used. Also "battery info" tells me the battery was mostly used by "Android OS"), I have to factory reset the device and flash to the stock 4.3 ROM. I monitored the newly setup phone for a day before I rooted it and install CWM recovery 6.0.4.3 for full system backup.
Happily used the phone for a week. After my son played with it for an afternoon, the wakelock problem comes back. Not sure what settings did he changed or apps he installed. So I go ahead backup the current rom and restore the phone from the previous backups.
Here was what I have done:
1. Boot into Clockworkmod recovery
2. Clear all partition / factory reset
3. Select Backup and restore.
4. Select the backup directory that I want to restore from (the one without wakelock problem)
5. Wait for the restoration process to finish
6. System reboots.
After system rebooted, it kept popping up "unfortunately com.google.process.gapps has stopped". The device was not usable, because the message will pop up again once I click OK to dismiss it. I then tried the following, but none of them works.
1. Restore from different backups
2. Enable "download service" from application manager. (It was not disabled)
3. Reset all apps settings from "Application manager" (menu)
Trying option 2 and 3 was a pain as the popup messages was blocking the screen, I have to be really quick to dismiss the message box and touch on the command.
BTW, the CWM recovery touch was installed from Odin, not from ROM manager. I experience the following problems:
1. Issue with "backup current ROM" command from "ROM manager". It cannot find /ex_sdcard when it goes to recovery.
2. It cannot find dalvik partition to wipe.
3. Backup to zip command does not work. It does backup the files and at the end it said the backup file is in /storage/sdcard/clockworkmod/image.zip. But I cannot find the zip file any where, including the external sd card.
Here is what I did to restore my phone to previous state with stock ROM:
1. Use Odin to flash the stock rom (samsung 4.3 for N7100), which will restore the stock recovery instead of the CWM recovery.
2. Reboot the device.
3. Use Odin to flash CWM recovery.
4. Reboot the device.
5. Go into recovery and restore only the /data partition.
6. Wipe /cache.
7. Reboot the device
8. Boot back to recovery and root the device.
Now I have the phone at my previous state.
Does it mean CWM recovery will not work with stock ROMs ? or I did something wrong.
Also, I still have not find out what was the cause for the wakelock problem in "Android OS". I have two backups where one has the problem and one does not. I have tried untar them and compare them with WinMerge, but there were a lots of files to go through.
Click to expand...
Click to collapse
I have to say, I did encounter the replication of the same exact problem. It kept popping up "unfortunately com.google.process.gapps has stopped". I was using the same CWM recovery 6.0.4.3 for my N7100 using stock android 4.3.
Try to do so many things but fail to get rid of the pop up. At the end, I ended up having to flash rom using Odin.
Anyway, I think, there's some bug with CWM recovery 6.0.4.3 that caused the error to happen. I managed to use TRWP 2.6.3.1 without any problem to restore after that.
Regards,
Had exactly same problem, i downgraded cwm from 6.0.4.6 to 6.0.4.4 by using odin
Than restore works fine no problems with services.
Note 3 sm-n900w8
warlab said:
Had exactly same problem, i downgraded cwm from 6.0.4.6 to 6.0.4.4 by using odin
Than restore works fine no problems with services.
Note 3 sm-n900w8
Click to expand...
Click to collapse
Hi.
How did you downgraded CWM using odin? I am stuck in the same problem.
Khizer Jalal
khizerjalal said:
Hi.
How did you downgraded CWM using odin? I am stuck in the same problem.
Khizer Jalal
Click to expand...
Click to collapse
Download image and overwrite existing one
Now i see that i have entered the rooting world in it's darkest time
I had the exact same problem of yours with CWM 6.0.4.3 and and the exact same problem with titanium backup(when i restore APP DATA for almost all apps they crash and keep popping messages). so there was no restore feature for me for long time
BUT TB restoring of App data is fixed when i updated TB to latest version and the CWM nandroid after-restore problem is fixed when yesterday i upgraded to philz 6.46.3, the restored ROM works flawlessly.
Now I think(not sure) what was going on is related to something called "FIX Permissions" or in other words when we restore system + data things get messed up that each app can't find it's own DATA folder causing it to crash. CWM and titanium backup didn't use to fix that mess but now they do so these problems won't occur anymore.

Samsung galxay Tab 3 Lite 7.0 Stuck at TWRP Recovery...

I was exploring the TWRP recovery installed on my tablet and tried to create backup which failed. Then i went to the mount menu and selected data and system. Then into the reboot menu i selected Firstly Recovey, then download, then system, then power off and every option restarted into twrp recovry and i cant start my tablet normally... I tried factory reset and data wiping cache and dalvik wiping but nothing helped. What should i do now ???:crying:
The twrp version is 2.7.0.1
BrickHead69 said:
I was exploring the TWRP recovery installed on my tablet and tried to create backup which failed. Then i went to the mount menu and selected data and system. Then into the reboot menu i selected Firstly Recovey, then download, then system, then power off and every option restarted into twrp recovry and i cant start my tablet normally... I tried factory reset and data wiping cache and dalvik wiping but nothing helped. What should i do now ???:crying:
The twrp version is 2.7.0.1
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56526161&postcount=144

Categories

Resources