Database Info

2.3.4: CWM 3.0.0.5 problems

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.

[GT-P6200][CWMRecovery][ROOT]ClockworkMod Recovery and Root

****** USE AT YOUR OWN RISK *******
This is NOT SUPPORTED SOFTWARE. This is purely for my amusement and entertainment. I'm making it available to download for those who might like to examine my work, but if you install it, you are on your own. I can't even test this myself. (I don't have a GT-P6200.)
Seriously - this has not been tested enough for me to be happy with it, and I'm unable to test it myself. Please read the thread for the GT-P6210 for instructions, known issues, warnings, etc.
If you do decide to install this anyway, please let me know how it works out for you. If no one is using it, I WILL NOT MAINTAIN IT AND WILL DROP IT.
If people do start using it, and the reports are that everything is working okay, then it'll get merged into what I'm already doing with the other two 7 plus models (meaning it'll get updated as needed when they do.)
Again, PLEASE READ the thread for the 6210 for everything you need to know: http://forum.xda-developers.com/showthread.php?t=1379532
..and here's a link for a CWM recovery.
Link: http://www.mediafire.com/download.php?do5jkna3dpas1tq
Take care
Gary

Hi! I'm a placeholder.

garyd9 said:
Hi! I'm a placeholder.
Click to expand...
Click to collapse
Hi, Placeholder. I'm a placeholder, too. Good meeting you here.

Pm'ed you. went straight in CWM, looks nice. able to make a full backup and md5. fails to restore in the middle of restoring /data
also getting UDIDs are inconsistent , fixing permission is supposed to take care of this.
and Im pretty much factory reset after reboot.
EDIT: appears as if Location cache map app by remy in market I had set to block wifi and cell caches. restoring a backup in CWM got permissions error, trestoring /data fails and Im left with pretty much a factory reset. went back to market and reinstalled suspicious app, installed and still says caches blocked removed app, rebooted, made back up and successful restore! woo hoo! Thank You Gary!
Note: should we make a note for 7+ CWM users beware blocked location caches, or re-write recovery to take care of this, and/or email the app dev?
anyways, pretty excited. Thanks so much Gary.

Anyone else want to help test the CWM Recovery for this tablet? (GT-P6200 only)
The current tester has had mixed results, but it _may_ have been the result of a third party app causing problems. I'd like to get someone else to test in addition to ensure there aren't any other issues.
In order to test, I need someone who has "adb" installed on their PC, is comfortable with linux commands, already knows how to use adb for commands such as "adb shell, adb push, and adb pull", doesn't mind using ODIN to restore their tablet to a factory state if it soft-bricks, and already knows how to use ODIN and CWM Recovery.
As a side-note; the third party app that MIGHT have been causing the problem is "Location Cache" by "remydemy." I don't use this app myself, but apparently it has some function to block the google/android location caches and it appears to do that by messing with the permissions on the files... which is somehow causing an error when the recovery tries to clean the /data directory in order to restore.
Thanks
Gary

link posted for testing.

thanks again gary loving it.

when I select wipe dalvik cache in CWM options it says dalvik cache wiped awfully fast. and after reboot and removing some bloatware.apks there are still loads of .dex files in /data/dalvik-cache including bloat that i removed.
So i just used root ecplorer to delete entire contents of folder. : )
is this not linked properly or CWM issue, or is this normal function?
thanks so much for your help.

chrisrotolo said:
when I select wipe dalvik cache in CWM options it says dalvik cache wiped awfully fast. and after reboot and removing some bloatware.apks there are still loads of .dex files in /data/dalvik-cache including bloat that i removed.
Click to expand...
Click to collapse
I'll look into it. Please try this alternative to test that function: Boot your phone normally, and then reboot into recovery. Using the recovery menu, mount the /data partition. Then use 'adb shell' to shell into the device and manually look in the /data/dalvik-cache directory. Then "cd /" and from within recovery choose the advanced->wipe dalvik-cache. Then look in /data/dalvik-cache directory again to see if it did what it should have done.
It's possible, based on the ordering of your above description, that the dalvik cache rebuilt after you wiped it (during the reboot) but before you removed your bloatware.
Take care
Gary

thank you. Gary tried not to get Banned OK? we need you buddy. lol

chrisrotolo said:
thank you. Gary tried not to get Banned OK? we need you buddy. lol
Click to expand...
Click to collapse
Where you able to run those tests yet?
thanks
Gary

not as of yet, sometime today though.
---------- Post added at 03:13 PM ---------- Previous post was at 02:23 PM ----------
so yeah, you must be right. dalvik-cache was full with /data mounted. cd / then wiped dalvik from CWM, which finishes in a split second; a list (ls) shows no dalvik-cache folder after wiping, completly gone.
Answers my question.
One other issue I ran into, that you're may be aware of is somehow I disabled the power button in CWM, it said something about back button disabled. I think I had to hold power for 10 sec. to reset device.
Thanks.

chrisrotolo said:
...somehow I disabled the power button in CWM, it said something about back button disabled.
Click to expand...
Click to collapse
That one I'm not sure of and really can't help much with. No 'power' button means you can't select anything which would really be annoying.

it works great! instant root and cwm within 2 minutes! i highly recommend gary's method than the other one. i also don't seem to lose root access by clearing ram memory. SWEET.

Not working:
- format internal sd-card
- update CSC
- installing pre-apps
how to remove CWMRecovery and install stock recovery?

lvsw said:
Not working:
- format internal sd-card
- update CSC
- installing pre-apps
how to remove CWMRecovery and install stock recovery?
Click to expand...
Click to collapse
formatting the internal SDCard isn't going to happen with this version of CWM (that's designed for GB.) Honeycomb devices don't have a seperate /sdcard partition to format. Formatting the "internal sdcard" can be done from within the settings menu via a factory reset.
The other two items aren't broken - they simply don't exist in CWM recovery, and probably never will... Is having the pre-loaded samsgung sample video and music files repushed to your device over and over actually more important to you than the ability to do a nandroid backup? Do you even know what the CSC is that isn't being updated?
Have you bothered to seach around BEFORE installing this? Have you bothered to search around AFTER installing it to find out how to restore to factory?
I'm NOT going to answer your specific question on the basis that it's been answered already and I honestly feel that a user of XDA needs to have the ability to SEARCH before posting.
Take care
Gary

worked like a charm...backup and restore works perfectly...
thanks gary !!!

Hey Gary-
Question -
Is it possible to get ROM manager to recognize the recovery flashed here? I'd like to flash the new version of CWM, which claims to fix the internal SD card problem, but when I install ROM Manager it doesn't recognize that I have CWM flashed.
I could just flash a new recovery from ROM Manager, but I don't want to screw anything up.
Thanks!
Sent from my Galaxy Tab Plus using Tapatalk

jeffcavicchi said:
Is it possible to get ROM manager to recognize the recovery flashed here? I'd like to flash the new version of CWM, which claims to fix the internal SD card problem, but when I install ROM Manager it doesn't recognize that I have CWM flashed.
Click to expand...
Click to collapse
This recovery is CWM Based - it is not an official ROM Manager supported recovery. I have no idea what "internal SD card problem" you are referring to, as I had internal sd card issues resolved with this CWM-based recovery before I posted it (there's only a single version for the P6200.)
I'd actually advise against using the "ROM Manager" program on this device. It's not a supported device, and things can go terribly wrong when messing with recovery and firmware partitions that aren't explicitly supported.
Take care
Gary

garyd9 said:
This recovery is CWM Based - it is not an official ROM Manager supported recovery. I have no idea what "internal SD card problem" you are referring to, as I had internal sd card issues resolved with this CWM-based recovery before I posted it (there's only a single version for the P6200.)
I'd actually advise against using the "ROM Manager" program on this device. It's not a supported device, and things can go terribly wrong when messing with recovery and firmware partitions that aren't explicitly supported.
Take care
Gary
Click to expand...
Click to collapse
Got it - sort of what I figured.
Am I wrong that Recovery still sees the external SD card as an internal SD card? I thought the last time I flashed a zip (boot animation) Recovery showed it as being on the internal card, even though it was actually on the external card. I could be wrong, though - and I don't have the device in front of me to check.
Not a big deal either way - thanks for the response, and your hard work!
*Edit*
Just realized I posted this in the wrong thread like an idiot - I have a P6210. guess that's what happens when you start posting things bc (before coffee).

[RESOLVED] Flashing Custom Rom Results In Noob Hiccup, No Backup and Can't SD Mount

Hey guys, unfortunately my first post here will be under messy circumstances but I've managed to mess my phone up pretty bad.
I have an AT&T HTC One X. I'm running on Windows 7 64bit, all drivers updated, permissions set, etc. etc.
I was supposed to be flashing Cyanogenmod 10 when I ran into an error in that was in the actual zip file. Prior to installing TWRP I had Clockwork mod installed. I flashed TWRP onto my phone & have been using that since.
My noob hiccup was instead of deleting just the zip file I managed to wipe the entire sd card, backups included (I'm an idiot, I know).
Now I don't have an os and cannot run in debugging mode in order to get adb to function properly. When I adb I cannot access /system/ nor /sdcard/. I can only access /data/ & of course installing CM10 through that directory has resulted in more fails.
Please tell me there's a way to salvage this. Thanks in advance...

Notorio said:
Hey guys, unfortunately my first post here will be under messy circumstances but I've managed to mess my phone up pretty bad.
I have an AT&T HTC One X. I'm running on Windows 7 64bit, all drivers updated, permissions set, etc. etc.
I was supposed to be flashing Cyanogenmod 10 when I ran into an error in that was in the actual zip file. Prior to installing TWRP I had Clockwork mod installed. I flashed TWRP onto my phone & have been using that since.
My noob hiccup was instead of deleting just the zip file I managed to wipe the entire sd card, backups included (I'm an idiot, I know).
Now I don't have an os and cannot run in debugging mode in order to get adb to function properly. When I adb I cannot access /system/ nor /sdcard/. I can only access /data/ & of course installing CM10 through that directory has resulted in more fails.
Please tell me there's a way to salvage this. Thanks in advance...
Click to expand...
Click to collapse
I would just relock downloader through fastboot and run the ruu and go again...u can't mount through recovery?

omario8484 said:
I would just relock downloader through fastboot and run the ruu and go again...u can't mount through recovery?
Click to expand...
Click to collapse
Well I just fixed the sd card issue but now for whatever reason /system won't mount. do i need to install superuser first or something?

copy rom to sdcard and flash

DvineLord said:
copy rom to sdcard and flash
Click to expand...
Click to collapse
Tried 5 times now, same error every time:
E:Unable to mount '/system' (tw mount)
Error flashing zip '/sdcard/cm10_endeavoru-ota-eng-noeri-019'
*Shrugs, sorry for being a pain. Not sure what's left after this...

wrong phone this is the evita forum. you dont have a endeavoru.

DvineLord said:
wrong phone this is the evita forum. you dont have a endeavoru.
Click to expand...
Click to collapse
Ah, I was flashing the rom for the global one x not xl *facepalms
Thanks, it seems to be in working order now...

Notorio said:
Ah, I was flashing the rom for the global one x not xl *facepalms
Thanks, it seems to be in working order now...
Click to expand...
Click to collapse
Stick to ROMs in this specific (AT&T One X) forum, and you won't go wrong again (at least not in that way).
Or check out my Index thread to see the ROMs in an organized list: http://forum.xda-developers.com/showthread.php?t=1671237

CM can't delete files??

I have root enabled. I always have. This bug has plagued me for many versions through many reinstalls, for months.
Go into file manager > try to delete a folder > it fails, says you need root enabled. It's not just in the stock CM file manager, even Root Explorer fails.
I can explore the storage via Windows and delete the folder, but my device still shows it exists and can still access the files it contains.
WTF. Help!

Can anyone comment on this? I can't delete files because it demands root, even though I have root. It's been like this for months, through complete wipes and resets, through different versions of CM.
Even when I delete files using Windows, they still exist and are visible to apps and in CM File Manager.

Still a problem, but a workaround is to delete via TWRP recovery. Wish someone could explain why this is happening. It has something to do with CM, it's never been a problem on any other ROMs, but it's consistently been a problem on a range of CM ROMs.

.psd said:
Still a problem, but a workaround is to delete via TWRP recovery. Wish someone could explain why this is happening. It has something to do with CM, it's never been a problem on any other ROMs, but it's consistently been a problem on a range of CM ROMs.
Click to expand...
Click to collapse
Since you state it is a CM ROM and this phone runs on CM out of the box, I highly doubt it is a CM only problem. Any ROM you flash, except for OmniROM and derivatives uses CM commits. They may not be CM-based, but they share a lot.
Seems more like a faulty partition to me.
Can you tell us what happens if you remove the files using ADB? Either through your Windows PC or using Terminal Emulator.
That should work.
I'd advise you to format your storage partition, and see what happens after that.
If it doesn't work, I'd still advise you to format your storage partition
You know what they say: the simplest solutions are the best!

TiVON said:
Since you state it is a CM ROM and this phone runs on CM out of the box, I highly doubt it is a CM only problem. Any ROM you flash, except for OmniROM and derivatives uses CM commits. They may not be CM-based, but they share a lot.
Seems more like a faulty partition to me.
Can you tell us what happens if you remove the files using ADB? Either through your Windows PC or using Terminal Emulator.
That should work.
I'd advise you to format your storage partition, and see what happens after that.
If it doesn't work, I'd still advise you to format your storage partition
You know what they say: the simplest solutions are the best!
Click to expand...
Click to collapse
Well, as far as I know I format the storage partition every time I flash a new ROM (all of which have been CM nightlies or else CM11s or 12s), because I use TWRP and wipe everything listed in the wipe menu, twice.
But I do use TWRP, and that uses ADB right? It was successful deleting files.

Persist partition permissions and owners

Hi everyone. Got a bootloop, so had to format the persist partition. I made a backup of it with adb before formatting, but forgot to save permissions/owners of every file.
Could anyone just make an "ls -l" in all folders of /persist? Thank you.
P.S. I'd appreciate if anyone makes a full image backup of /dev/block/platform/msm_sdcc.1/by-name/persist
To make it, just do a dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/sdcard/persist.img and post the file on any file hosting.

Slavon-93 said:
Hi everyone. Got a bootloop, so had to format the persist partition. I made a backup of it with adb before formatting, but forgot to save permissions/owners of every file.
Could anyone just make an "ls -l" in all folders of /persist? Thank you.
P.S. I'd appreciate if anyone makes a full image backup of /dev/block/platform/msm_sdcc.1/by-name/persist
To make it, just do a dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/sdcard/persist.img and post the file on any file hosting.
Click to expand...
Click to collapse
Why don't you just try doing a factory reset after bootloop?
Anyways,here's the file that you were asking for-
https://drive.google.com/file/d/0BxysuRdzsJeWNi02b0NmSUVwbE0/view?usp=drivesdk

Mr.Ak said:
Why don't you just try doing a factory reset after bootloop?
Anyways,here's the file that you were asking for-
https://drive.google.com/file/d/0BxysuRdzsJeWNi02b0NmSUVwbE0/view?usp=drivesdk
Click to expand...
Click to collapse
Because it was a bootloop just right after a flashed the ROM on a completely clean factory reset device. Now I understand that it was a problem with the ROM, that's why I made a backup. And your image will help me know if I miss any files in this partition and know their permissions.

Slavon-93 said:
Because it was a bootloop just right after a flashed the ROM on a completely clean factory reset device. Now I understand that it was a problem with the ROM, that's why I made a backup. And your image will help me know if I miss any files in this partition and know their permissions.
Click to expand...
Click to collapse
Which ROM?

Mr.Ak said:
Which ROM?
Click to expand...
Click to collapse
hyperUnicorns. For some reason any build I try to install since the end of June gives me reboots. I thought it was some incompatibility with Multirom 33e and MIUI, but after I flashed the full Cyanogen package, nothing changed, that led me to google and some posts, saying it can be a damage of persist partition.

Slavon-93 said:
hyperUnicorns. For some reason any build I try to install since the end of June gives me reboots. I thought it was some incompatibility with Multirom 33e and MIUI, but after I flashed the full Cyanogen package, nothing changed, that led me to google and some posts, saying it can be a damage of persist partition.
Click to expand...
Click to collapse
That rom worked fine for me..maybe it doesn't support multi-rom.
I think you should ask on the rom's thread.