Database Info

[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).

[GUIDE]How to load CM9 on GSIII

**this was a very early guide and most of the files and methods referenced in it are long outdated, sounds crazy I know as the phone has barely been out, but i recommend finding more recent guides at this point. I wanted to leave this up for archival reasons though. As of 7-22 I am running dhackers CM10 build with great results. Just don't forget to set max cpu clock back down to 1500 mhz if you don't want it over locked out of the box **
As per the usual disclaimer....at your own risk, be aware of IMEI loss issues and whatnot...basically cover your own butt.....and enjoy.....
7-15 2:46pm **As of right now voice and SMS are not working on my phone while other people report they are working fine. While you can still play around and see just how amazingly fast CM is on this phone, YMMV. If it doesn't work you need to know how to go back to stock before trying this.
7-29 this guide is very old, it pre-dates kexec and is only here for historical purposes
For clarification: The question was asked if one is supposed to follow the original Team Epic Kexec kernel instructions or these steps and the answer is two fold. If your goal is to install the UNOFFICIAL CM9 built by Invisiblek (which is the purpose of this thread), then you follow the steps in THIS THREAD ONLY. There are a couple steps and a couple files linked to in the original Kexec page that will not allow you to install CM9. That page was made for those wanting to try out their Kexec Proof of Concept KERNEL, not install a ROM of any kind.
This thread makes some assumptions, such as you already have a working install of the Android SDK and ADB, you already have the drivers installed, you are using the original USB cable that came with your phone, you know how to move around DOS to get to the directory where you downloaded the files, etc.......those lower level tasks are for another thread.
To Try Our Proof-of-Concept Kernel <<<The base of these instructions was the Team Epic Kexec Kernel page seen at this link, Many Thanks to them
Thanks to Invisiblek for clarifying and helping me get steps just right.
The following is an adaptation of the CM Kexec kernel proof of concept with the changes in files and steps necessary to load the latest CM9 work in progress. Be advised I take no credit at all. This is the work of Team Epic and Invisiblek. I just put this together for myself and for others who would like to try it with one caveat. DATA doesn't work! Voice and SMS only....and maybe 1xRtt data.....so you will be relying on WiFi for data! You've been warned!
Also, I highly suggest you use a free MD5 Hash checking utility to verify the integrity of the files you are downloading. That is why the MD5 hash is provided, so you can be sure you didn't get the wrong file or a corrupt download that could cause a BRICK!
If you don't follow the directions carefully you can end up with a brick! Ask questions after reading the OP if you still aren't sure. I probably won't know the right answer for sure. You may have to wait on someone with more experience in this to answer your question.
DO NOT ACCEPT AN OTA UPDATE WHILE RUNNING THIS SETUP
1. Download the recovery.img (MD5: f1c01ad20e02751a73188f173eb412ca), which combines our source-based kernel with our previously released CWM v4.
2. Flash the recovery.img following these instructions, that is:
Code:
adb push recovery.img /sdcard/
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 bs=256k
sync
3. Reboot into recovery (using volume up, home power buttons), wipe data, install one of invisibleks CM9 roms>click here for all of his CM9 roms< which do not have boot.img integrated, then continue with the steps below:
4. Download these additional files:
(required download)boot.img (MD5: db058f4b15df0fa1b9ee04a5c17cf103), which is invisibleks custom boot.img
It would be good at this point to read ahead and determine where you will be loading the next file. Keep in mind if you are in stock recovery and choose to wipe data, this will wipe the internal memory.
if you plan to load onto internal memory download this file boot_emmc_boot_img.zip (MD5: 84a3f98c194f6dedc583dbc75ccc34c2)
or
if you plan to load onto sdcard (ext) memory download this file boot_sdcard_boot_img.zip (MD5: 88904d7e69d455ff88756b4d1ad79aac), which are applied in recovery to kexec (boot) the custom boot.img.
5. Place boot.img either on the internal SD card (the /sdcard/ folder), or on the external SD card (the /mnt/extSdCard/ folder).
The boot.img kernel boots directly out of one of these folders, it will not (and should not) be flashed to the device.
6. If you're using the internal SD card, place boot_emmc_boot_img.zip in /sdcard/ as well. If you're using the external SD card, place boot_sdcard_boot_img.zip in /mnt/extSdCard/.
7. Reboot into recovery.
8. If using the internal SD card, select "Install zip from sd card" and then "choose zip from internal sdcard", then "boot_emmc_boot_img.zip". Alternatively, if using the external SD card, select "choose zip from sdcard", then "boot_sdcard_boot_img.zip".
At this point, the device should reboot "in the middle" of applying the update, temporarily booting boot.img. If the update "completes" and returns to the CWM menu, kexec has failed or the wrong recovery was loaded in the beginning. Please check the locations of boot.img, and boot_emmc_boot_img.zip or boot_sdcard_boot_img.zip and verify recovery.img file used was the correct one, verify using an MD5 hash checker.
9. Once booted, the custom kernel can be confirmed by checking "Kernel version" in "Settings", "About device". It should report:
3.0.8-gdefeb6f
[email protected] #1
SMP PREEMPT Sun Jul 8 04:27:58 EDT
2012
10. To reboot into the stock kernel, select "Restart" from the Power menu, which will actually reboot into CWM recovery. Press the Power button to select "reboot system now" and leave recovery.
11. You cannot simply power on your phone with this setup! In order to power on your phone you will have to hold volume up, home and power to boot into recovery and load the zip file you chose at step 4 where you chose either internal or external memory, so either "boot_emmc_boot_img.zip" or "boot_sdcard_boot_img.zip". If you do accidentally boot up by just hitting power, no big deal, it will give you all sorts of force closes, simply pull battery and boot back up using the Vol up, Home, power method.
If anyone would like to suggest further clarification, please do. To get the stock Google apps such as Play Store get the package HERE and install in recovery
Alternatively a more condensed version of this install procedure has been posted by nbsdx and can be found HERE.
7-15 2:46pm **As of right now voice and SMS are not working on my phone while others are working fine. While you can still play around and see just how amazingly fast CM is on this phone, YMMV. If it doesn't work you need to know how to go back to stock before trying this.
If you want to return to bone stock, simply go to THIS THREAD to get STOCK ROM IMAGE and then put your phone into Odin Download mode by following THIS THREAD and be sure to flash it using the PDA button. It will take a while, probably 20 minutes or so, it will take forever to boot up the first time but you will be on bone stock like new.

Very informative. Would read again.
Sent from my Transformer Prime TF201

dual boot
Being that we have to use kexec anyhow, it would be nice (especially with the state of current cm9 rom) if we could fully dual boot so as to keep stock system and data for stock kernel.
Like here,
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html

I just installed successfully using the instructions in the OP so I can confirm it works correctly. Holy crap it's fast.

Anybody want to put up a video of how well it runs for us that aren't brave enough to put it on our own phones?
Sent from my SCH-I535 using xda premium

dakalter said:
Anybody want to put up a video of how well it runs for us that aren't brave enough to put it on our own phones?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I'll leave that part to someone who doesn't sound like a retarded redneck on video.

silasrye said:
I tried to install the vzw cm9 (with with invisiblek's boot.img put back into the zip) via this method exactly.
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html
fake cwr works, and everything went fine, but when i try to flash boot_cm9.zip i stay in cwr.
I am using the cwr from this post
http://forum.xda-developers.com/showthread.php?t=1773514
I had started with the twrp from that post, but it didn't recognize my internal sdcard.
So, I don't see why this shouldn't be a doable thing. But something probably needs to be redirected somewhere.
The good news is, I boot into my normal rom without problem.
Click to expand...
Click to collapse
If you follow the steps in this thread, including using these links for your files, it will work without a problem.
I can't comment on why other guides on other sites using other files don't work.....and not really sure how it applies to this thread. Lets try to keep it on topic. If you have issues with the dual booting instructions, you might start a new thread to address that or jump in irc.freednode.net/verizons3 and graciously ask the people for help
When you flash the the CM9 rom built by Invisiblek it will come back out to CWR menu. At that point in the process I realized I hadn't copied the boot.img file into the root of my sd card, so i left it on the CWR menu, popped out the sdcard, copied the boot.img file over (already had the boot_sdcard_boot.img file on the root of sdcard), and popped the sdcard back in, chose advanced->reboot recovery, then followed the steps in this guide, worked perfectly.

silasrye said:
I tried to install the vzw cm9 (with with invisiblek's boot.img put back into the zip) via this method exactly.
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html
fake cwr works, and everything went fine, but when i try to flash boot_cm9.zip i stay in cwr.
I am using the cwr from this post
http://forum.xda-developers.com/showthread.php?t=1773514
I had started with the twrp from that post, but it didn't recognize my internal sdcard.
So, I don't see why this shouldn't be a doable thing. But something probably needs to be redirected somewhere.
The good news is, I boot into my normal rom without problem.
Click to expand...
Click to collapse
You need to add one line to Invisiblek's updater-script that "flashes" the boot.img to the bootloader partition in the multi boot folder. Check out the sprint cm9 install for the line to add.
I have tested dual booting to work perfectly.

is the data not working due to the ril??

suzook said:
is the data not working due to the ril??
Click to expand...
Click to collapse
yes, will update OP once we have working 3G/4G data
as of right now my voice and SMS isn't working while others is.....trying to figure it out

I flashed back to stock, simply because I need to have voice and SMS working. I could deal without 3G/4G data for a little bit and use WiFi, but no SMS/Voice was a deal breaker on my phone. I have to be easily gotten in touch with for work and such. It was fun while it lasted.

Will these same instructions work for the CM10 build that is in the server list?

17akota said:
Will these same instructions work for the CM10 build that is in the server list?
Click to expand...
Click to collapse
No. Different files used, probably a different step or two also. I plan to edit this once CM10 builds are ready for public consumption. These instructions also don't include the automated kexec scripting work done recently that allows your device to cold boot into CM9.
Sent from my SCH-I535 using xda premium

neyenlives said:
No. Different files used, probably a different step or two also. I plan to edit this once CM10 builds are ready for public consumption. These instructions also don't include the automated kexec scripting work done recently that allows your device to cold boot into CM9.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I figured that.
Could you point me in the direction of the new Kexec? I read about it somewhere and would like to try it out.

17akota said:
I figured that.
Could you point me in the direction of the new Kexec? I read about it somewhere and would like to try it out.
Click to expand...
Click to collapse
irc.freenode.net #verizons3
Sent from my SCH-I535 using xda premium

i came from a thunderbolt, and know how different a RIL can be from phone to phone, so i ask this quite seriously...
How different is the RIL from the Gnex to the SGIII?

seang said:
i came from a thunderbolt, and know how different a RIL can be from phone to phone, so i ask this quite seriously...
How different is the RIL from the Gnex to the SGIII?
Click to expand...
Click to collapse
Completely different processors.

Is there anyway to get the TouchWiz Camera on CM9? I really like that camera app.
I tried just putting it in /system/app and changing the permissions to rw-r--r-- and rebooting and nothing
Then i tried just installing it like a normal apk and it failed.
I would love CM9 if i could just get the stock camera app too work.
BTW im using DHacker29's CM9 and its amazing. So much easier to install.

17akota said:
Is there anyway to get the TouchWiz Camera on CM9? I really like that camera app.
I tried just putting it in /system/app and changing the permissions to rw-r--r-- and rebooting and nothing
Then i tried just installing it like a normal apk and it failed.
I would love CM9 if i could just get the stock camera app too work.
BTW im using DHacker29's CM9 and its amazing. So much easier to install.
Click to expand...
Click to collapse
It probably requires touchwiz frame work. It will take significantly more work than just dropping in an apk
Sent from my SCH-I535 using xda premium

DHacker's CM10 is awesome!! I've been running it all day and Jelly Bean is really smooth on the S3.
http://www.droidhive.com/forums/index.php?/files/category/26-sgs3/
Check it out guys.

[Q] Startup error - installed wrong script

To whom ever can help out, I have a Galaxy Tab 2 7.0, and cannot seem to get my problem resolved by myself. I have somehow inadvertently managed to install an update.zip that had or had no relations to this particular OS of this particular model of android.
My problem is that I wanted to be able to, migrate my apps to the external SdCard or extSdCard, and I think I used an update.zip designed for the cellphone HTC Evo 4g. Not realizing that I will be later unable to use the restore feature from a previous backup I had made using CWM 6.0.1.0 to recover from my inadvertent mistake (not to comfortable making a backup, and thinking I can restore properly anymore, like I can on my cellphone that I am spoiled with).
Silly of me to think I could use an update.zip designed for another type of device such as the HTC Evo 4g, but… (anyway my bad what was I thinking…?). The update.zip, by the way is "dtapps2sd-2.7.5.2-signed", like I mentioned this is clearly designed for the HTC Evo 4g, and not for the Samsung GT2 7.0.
The problem I experience now is not complete lose of my GT2 7.0 device I can still install and change out OS through the CWM-Recovery and install apps through the Android Market. I do however experience the inability to check my Storage properties under my Settings profile. When I attempt to click on this link it pauses for a second as if it wants to open up and perform its normal function, then reports an error "Unfortunately, Settings has stopped". Now at this point this is where I would have to mention another issue similar to this one, and that is at startup. When I first start the device up and it runs through its process of startup configuration. It will then report a list of programs that are prevented from running properly it as follows;
Unfortunately, the process android.process.media has stopped.
Unfortunately, My Files has stopped.
Unfortunately, Factory Test has stopped.
Unfortunately, MTP has stopped.
Now my question is, how is-it possible to resolve this issue. I have tried to complete a fresh install of the OS, CWM-Recovery, and also attempted to wipe everything possible that the recovery will allow, but I am not expecting much, as I cannot even get the backup and restore feature to work efficiently enough to provide me with what I need it to do…
I have provided this post with a download of the update.zip I used as well as the version of the OS I have provided my Samsung GT2 7.0. If anyone can shine some insight on what direction I should attempt to do to resolve this issue I would be more that interested to take a look at what I could use to correct this error of mine…
-Samsung GT2 7.0 - OS (Use the Download link above the Rosewell signature)
http://forum.xda-developers.com/showthread.php?t=1784318
-dtapps2sd-2.7.5.2-signed
http://www.mediafire.com/?7jpc5oudzt6o76p
I might be comfortable to ADB Shell into my device to make changes, or if one was able provide me an update.zip/script that would be great. Also is there a better recovery out there than the ClockWorkRecovery.

Better recovery so you may try twrp or so
Try install a fresh firmware preferably with a pit file from odin pc
Sent from my GT-I9300 using xda app-developers app

Mohamedselim said:
Better recovery so you may try twrp or so
Try install a fresh firmware preferably with a pit file from odin pc
Click to expand...
Click to collapse
Mohamedselim, Thanks...
Will look into this..., any links by the way in regards to the "fresh firmware with a pit file"...?

Have you tried downloading and flashing a full Odin tar file to restore your device to stock?

imnuts said:
Have you tried downloading and flashing a full Odin tar file to restore your device to stock?
Click to expand...
Click to collapse
Yeap...!, I have tried this already, have had no promising results...

This is the only compatible version of a .pit file...;
http://forum.xda-developers.com/showthread.php?t=1642744
Can anyone provide me another one for the GT-p3113...?

Just checking in..., and wondering if anyone has a solution for this...?

Factory reset in stock recovery. So Odin a stock Rom and before u install anything custom, do a factory reset in recovery after u Odin back to stock. Then flash away.
I imagine you have alrdy tried a factory reset using a custom recovery.

WAIT!!! You don't have to factory reset, just reboot into CWM recovery ang go to mounts and storage>wipe internal storage. Confirm and reboot. You will lose anything on the sdcard but your apps will stay.

RomsWell said:
Factory reset in stock recovery. So Odin a stock Rom and before u install anything custom, do a factory reset in recovery after u Odin back to stock. Then flash away.
I imagine you have alrdy tried a factory reset using a custom recovery.
Click to expand...
Click to collapse
MultipleMonomials said:
WAIT!!! You don't have to factory reset, just reboot into CWM recovery ang go to mounts and storage>wipe internal storage. Confirm and reboot. You will lose anything on the sdcard but your apps will stay.
Click to expand...
Click to collapse
1. I am all over the Factory resets, and wipes.
2. Already tried Stock Rom(s).
3. I believe my problem is a bootloader, or partitioning script. (As this denies me access from inside settings>storage where I can view my allocated size, and Restore to Factory button. In addition in CWM, I am not allowed to mount/sdcard(internal), extSdCard is ok though. Also, I cannot plug Tab via USB to check contains on Internal or External sdcard, but I can remove the External to transfer data from it via sdcard slot on PC...)
Maybe you can recommend a good Stock Rom, so I can give that ago...
I was in the process last night, and could not get a good connection with Heimdall or Odin. I am now looking into driver issues, so...

Ok, so I was successful in taking RomsWell and MultipleMonomials advice, and was able to return my device back to "Normal" state, including "Stock Recovery". But I still have the original problem as in my request I asked in my first post...
I do however experience the inability to check my Storage properties under my Settings profile. When I attempt to click on this link it pauses for a second as if it wants to open up and perform its normal function, then reports an error "Unfortunately, Settings has stopped". Now at this point this is where I would have to mention another issue similar to this one, and that is at startup. When I first start the device up and it runs through its process of startup configuration. It will then report a list of programs that are prevented from running properly it as follows;
Unfortunately, the process android.process.media has stopped.
Unfortunately, My Files has stopped.
Unfortunately, Factory Test has stopped.
Unfortunately, MTP has stopped.
Click to expand...
Click to collapse
I think now, if I cannot get a sizable remedy..., is just to try and send it in Samsung so they can take a look at it...
Any suggestions...?
FYI; I have also tried connecting to Kies, but due to the inability to posses a "MTP" (Media Transfer Protocol), is the reason I cannot connect to my SdCard & extSdCard. I can "PTP" (Picture Transfer Protocol) into it, using "adb shell", but not using "MTP"...
So I do not know how much "MTP" has to do with this relationship of the other three items that I mentioned in my bullet list in my quote, but...
Anyway, I don't know what I am trying to say, but thank you two, for getting me this far...!

grassy-sneakers said:
1. I am all over the Factory resets, and wipes.
2. Already tried Stock Rom(s).
3. I believe my problem is a bootloader, or partitioning script. (As this denies me access from inside settings>storage where I can view my allocated size, and Restore to Factory button. In addition in CWM, I am not allowed to mount/sdcard(internal), extSdCard is ok though. Also, I cannot plug Tab via USB to check contains on Internal or External sdcard, but I can remove the External to transfer data from it via sdcard slot on PC...)
Maybe you can recommend a good Stock Rom, so I can give that ago...
I was in the process last night, and could not get a good connection with Heimdall or Odin. I am now looking into driver issues, so...
Click to expand...
Click to collapse
Did you try formatting internal storage in CWM?

MultipleMonomials said:
Did you try formatting internal storage in CWM?
Click to expand...
Click to collapse
I am not quite confident on how much this will work. As I have tried this multiple times to wipe "Wipe Factory/Data", "Wipe Cache", including all the partitions under the "Advance" section found in CWM Recovery. Even using TWRP Recovery.
Per this post; I just attempted to flash a "Stock Rom", but not before doing a factory/data, cache wipe using "Stock Recovery", including after a successful install...
No luck, the same problem still exist as above...

Ok, this was all just the rudest experience I put my self threw. As I have an HTC Evo 4g - cellphone and have become comfortable with installing ROM's, Kernels, and Updates.zips, as well as, other modification. All threw the Recovery designed for this particular device, and don't get me wrong there has been a couple of times. Maybe more than a couple, more like a few times I have installed incompatible downloads I find in the XDA forums. Which makes this screw up, difficult form me to know that as long as you can get into a Download/Bootloader or a modified Recovery designed for a particular device that was successful flashed correctly. Well the screw up are easily redeemed/recoverable.
So, to make a long story short. After having called Samsung Customer Care (the 1-800-SAMSUNG) number, it seems to have been a External SdCard getting in my way from having been real short from sending my Tab off to the repair department (where ever it is...). I in fact already had it in an envelope, all I needed was an address to send it to. Anyway the nice person on the other side of the phone requested that I remove my External SdCard, and confirm that I was able to get into my "Storage" tab under my settings. Well after success getting this option back, I then made the suggestion that maybe my Eternal SdCard is corrupt or incorrectly formatted. She then agreed maybe this is the case. After ending the phone call. I quickly restarted my Tab, again only to find out that I was no longer receiving the error messages like mentioned above, which is great, because after multiple flashes of "Stock Roms w/Stock Recovery", and forcing myself to believe that it was a system install error. It in fact the External SdCard in place preventing me from throwing my Tab against the wall / in the mail to Samsung Repair Center...
"Man what an ordeal...!!!"
Thanks to all that helped with the suggestions, as to what direction I most defiantly tried.
I am now in the process, since I am living back in Stock mode. To receive an OTA (Over The Air) Update, and am still in the process of seeing if this thing still possess any residual silent errors...
I will keep you posted.
If not, well it off to happy rooting for me...!!!

That is it, my problem is resolved. Damnedest thing this problem of mine, it seems the only thing I screwed up was the micro SdCard. to the point it was the cause of all the error I received when I started up the device, as well as when I attempted to access my storage through me settings options...!!!
Now re-rooted, and a happy camper, Cheers...!

Malata Zpad T2

After searching for ages, I stumbled upon a solution for my tablet. Although all GTab ROMS work in the Zpad, I haven't been able to use the full 1GB RAM present in my Zpad.
So Finally today I stumbled upon a solution posted in slatedroid by Micky.
Instead of flashing the Viewsonic ROM to start with, we need to flash this ROM instead.
After you download the ROM from the link above, search for the TeamDRH CWM 5.5.0.4 and download. Extract the RAR file and replace the recovery.img in the folder with the TeamDRH CWM, cuz the one in the ROM is too old and doesn't support the latest ROMs.
[Note: If you want a larger system partition, follow this.
Open the file flash.cfg and find this no. 209715200 and replace it with this no.419430400
Now when you flash this ROM, you will get a system partition of 400MB.
If you use this method, you don't need to delete any system files after install from the ROM.]
Reboot the tab to CWM and wipe data/factory reset and wipe dalvik cache. Twice.
Shutdown and reboot to APX mode and connect to PC
NV Flash the ROM, let it boot and then shutdown.
Now to flash Jelly Bean.
Download Smoother Bean by nobe1976
Then boot the tablet to CWM
Again wipe data/factory reset and wipe dalvik cache. Twice just to be sure.
Flash the Smoother Bean zip file
Do not wipe data/factory reset or wipe dalvik cache this time.
Just reboot
Let it boot and run for a few minutes.
[Optional: Now install an app from play store to delete system apps and also a keyboard, Swipe or as such.
Open the system app remover and uninstall Gmail and AOSP Keyboard.
A few more apps can also be uninstalled, such as wallpapers, DSP Manager, Music FX, but not all.
Before deleting the AOKP Keyboard, you can copy it from the system folder if you want the stock keyboard. LatinIME.apk file.
(This does not apply if you modify the flash.cfg for larger system partition)
We need to uninstall these apps cuz after flashing with the above ROM, the system partition is only 209MB, so after flashing JB, we get around 5-6 MB free in the system partition. After uninstalling the apps, we get around 34 MB free.]
Hats off to nobe1976. He is able to develop a JB ROM that can be installed in a 200 MB system partition.
Well after everything, I hope whoever tried this in their MALATA Zpad is able to see full 1GB RAM, or around 850 MB approx.
[After this succesfull experiment, I would like to request a developer to kindly help us modify the system partition of the above ROM to 350 MB or more if possible.
Its a small request from us Zpad users.
(Note: From the help of all the users, I have been able to increase the system partitiom to 400MB)]
If anyone could help, I will be gratefull, we all will be very gratefull.
This is really pushing the limit.
Edit: Now you can use 1GB RAM present in your tablet and all the space available in the flash memory.
Note: This method can be used in all variants of the Zpad which has 1GB RAM and 16GB ROM.
Note: This tablet is sold by different names all over the world. The one I use is HCL AP10-A1

kank_fraud said:
Well after everything, I hope whoever tried this in their MALATA Zpad is able to see full 1GB RAM, or around 850 MB approx.
Click to expand...
Click to collapse
Can you post the 3 .txt files produced by these commands (reboot the tablet first)?:
Code:
$ [B]su -c dmesg > /mnt/sdcard/dmesg.txt[/B]
$ [B]cp /proc/meminfo /mnt/sdcard/meminfo.txt[/B]
$ [B]free > /mnt/sdcard/free.txt[/B]

After this succesfull experiment, I would like to request a developer to kindly help us modify the system partition of the above ROM to 350 MB or more if possible.
Click to expand...
Click to collapse
Though @rajeevvp is the best person on xda to give you solution that is more logical on this, I will tell you quick and dirty way to do this, which I have adopted.
1> download stock zpad rom if you don't have it already "ftp://112.5.164.225/tablePC/T2_nvflash_mp_3g(WCDMA)_20110824.rar"
2> unzip it, delete recovery.img from unzipped directory, copy part9.img from DRH nvflash which is used for prep 350M system partition to this directory, rename it to recovery.img
3> edit "android_fastboot_full_i_malata.cfg” change "size" of partition id 11 (which is a system partition)
Make sure you do not give any arbitrary size here; calculate it with the formula @rajeevvp posted here "http://forum.xda-developers.com/showpost.php?p=22138304&postcount=14"
4>now nvfalsh your tablet in apx mode with download.bat, now format /data /system /cache and flash whichever rom you want on top.
memory/partition config is supplied to kernel through CMDLINE parameter, so even if you nvflash tab with above procedure, its not necessary that default memory/partition sizes are maintained created by above prcoess, Team DRH boot.img has a blank CMDLINE. That is the reason
Above process will work on most of the ROM, which is using TeamDRH boot.img.
(more technical explaination stright from one of the posts of @rajeevvp "When the bootloader runs, it reads PT (partition 3) and constructs a command line telling the kernel what the partition layout is on the onboard NAND flash. Normally, the bootloader will pass this command line to the kernel as part of the boot-up process. However, if the bootloader sees that the boot.img already contains a default command line then that will take precedence")

I replaced the recovery image in the ROM as instructed in the first post but before flashing I edited the flash.cfg file to change the APP partition (id=11) size to 262144000 (250MB). I then followed the steps above but after flashing Smoother Bean it would always restart in recovery. I found I had to partition the internal SD to 4096/0 and then reload the rom and flash again. I now have a ZPad with a 250MB system partition and a total RAM of 871124 bytes. Thanks very much as it seems much faster now. Note I didn't have to remove any system apps in the process.

I replaced the recovery image in the ROM as instructed in the first post but before flashing I edited the flash.cfg file to change the APP partition (id=11) size to 262144000 (250MB). I then followed the steps above but after flashing Smoother Bean it would always restart in recovery. I found I had to partition the internal SD to 4096/0 and then reload the rom and flash again. I now have a ZPad with a 250MB system partition and a total RAM of 871124 bytes. Thanks very much as it seems much faster now. Note I didn't have to remove any system apps in the process.
Click to expand...
Click to collapse
glad to hear that it worked, BTW you will have to change /system size to minimum 350MB if you plan to use TeamDRH rom in future (hopefully with camera working)

I'll have a try later.Thanks So much.

Thank You all for the help.
I have already replaced the stock recovery CWM to 5.5 from the first flash.
Well I have tried to modify the system partition to 512 MB(536870912) in the flash.cfg and it failed. So I tried 400MB(419430400) and it worked.
It shows 419 MB in Titanium Backup
I am happy with it.
Its way better then before.
Thanks evryone
Problem solved

If anyone has formated or resized the internal memory resently, please try the maximum possible size for the system partition.
I tried 512MB but it didn't work. Maybe 490MB might work.
According to my knowledge, Android should support atleast upto 999MB for any partition.
Is it cuz of our tab or is it cuz of the architecture.
And if anyone knows, is it possible to create a larger internal partition.
As in 8GB or if possible the whole internal memory.
CWM doesn't allow more than 4GB internal space.

kank_fraud said:
I have already replaced the stock recovery CWM to 5.5 from the first flash.
Well I have tried to modify the system partition to 512 MB(536870912) in the flash.cfg and it failed. So I tried 400MB(419430400) and it worked.
Click to expand...
Click to collapse
Well this was expected result, /system partion resides on NAND flash chip (with is only 512MB) and not on SDcard.
Read this "http://raywaldo.com/2011/07/format-the-gtab/" and this "http://forum.xda-developers.com/showpost.php?p=15558724&postcount=12"
Also you need to bare in mind that other partitions also use 512MB nand flash as per explanation in above threads.
so if you take a close look at falsh.cfg file in nvflash directory you will understand that size allocation is sequential ("allocation_policy=sequential") and system partition (11) which is last to allocate the space, so you need to calculate it accordingly if you want to utilize all remaining space from NAND flash chip.

Well I cant open the page "http://raywaldo.com/2011/07/format-the-gtab/".
So according to this info I have hit the limit. I am already using 489MB of the 512MB flash. And as always, cuz of our storage manufactures, we get only 490MB in a 512MB chip.
What I wonder is why Malata and Viewsonic did not utilise the full NAND space available in the first place.
Is it used for something else.
I mean even the 350MB prep for Viewsonic GTab uses 350MB instead of 400MB.
It is so easy to to utilise and partition the NAND, then why not use the full available space.
What is the empty space used for!???
Or is it just a waste!!!

hi all,
tks for the useful informations above..but since my poor tech knowledge, its possible to produce a flashable rom for all T2 user with the max 490MB flash?
thanks in advance!
FG

fanguru said:
hi all,
tks for the useful informations above..but since my poor tech knowledge, its possible to produce a flashable rom for all T2 user with the max 490MB flash?
thanks in advance!
FG
Click to expand...
Click to collapse
Its already there.
Goto the first post and download the ROM
Extract the RAR file and find the file flash.cfg, right click and edit
Search this no. 209715200, it should be in the last 5-6 lines.
Delete the whole no. and type this no. 419430400
Save the file and close it.
Start your tablet in APX Mode and flash your tablet using download.bat.
Now you are using the full flash memory available.
You loose a few hundred kilobytes but thats it.
You cant use the whole flash memory as system partition.
There are additional partitions for the bootloader, recovery, logo, etc. which take up 89MB approx.
So 400MB is what you will get for system partition.
I would suggest flash as less as possible. Flash memory can written only a few hundred times. If it reaches the limit, then our tablet is dead.
Flash only major updates or if your ROM gives problem

rajeevvp said:
Can you post the 3 .txt files produced by these commands (reboot the tablet first)?:
Code:
$ [B]dmesg > /mnt/sdcard/dmesg.txt[/B]
$ [B]cp /proc/meminfo > /mnt/sdcard/meminfo.txt[/B]
$ [B]free > /mnt/sdcard/free.txt[/B]
Click to expand...
Click to collapse
Well I am very sorry for such a late reply. :angel:
I missed your post as I was out of station.
After I came back there were already solutions posted by a couple of users. :victory:
Well today while updating my original post, I noticed ur first reply. :silly:
Well thank you for your reply.
And thanks to all the ppl who provided for the solutions to our ZPad.
I guess the problems are solved for now.
:highfive: :highfive: :highfive: :good:

kank_fraud said:
Its already there.
Goto the first post and download the ROM
Extract the RAR file and find the file flash.cfg, right click and edit
Search this no. 209715200, it should be in the last 5-6 lines.
Delete the whole no. and type this no. 419430400
Save the file and close it.
Start your tablet in APX Mode and flash your tablet using download.bat.
Now you are using the full flash memory available.
You loose a few hundred kilobytes but thats it.
You cant use the whole flash memory as system partition.
There are additional partitions for the bootloader, recovery, logo, etc. which take up 89MB approx.
So 400MB is what you will get for system partition.
I would suggest flash as less as possible. Flash memory can written only a few hundred times. If it reaches the limit, then our tablet is dead.
Flash only major updates or if your ROM gives problem
Click to expand...
Click to collapse
Thank You kank_fraud,
i do these steps, and it works!
after, i've tried to flash "Smoother Bean " but tab continues to reboot i nrecovery mode. I've tried also to partition 4096 like suggested above, but same results.
So, the onlyu one rom working is the first?
ty again!:good:
FG

kank_fraud said:
I guess the problems are solved for now.
Click to expand...
Click to collapse
I'd still like the output of those commands--for my own edification.

fanguru said:
Thank You kank_fraud,
i do these steps, and it works!
after, i've tried to flash "Smoother Bean " but tab continues to reboot i nrecovery mode. I've tried also to partition 4096 like suggested above, but same results.
So, the onlyu one rom working is the first?
ty again!:good:
FG
Click to expand...
Click to collapse
Well for Me it worked the first time itself.
Why don't u try giv it a few more couple of times. :laugh:
BTW, are you using the Malata Zpad or Viewsonic Gtab
If you are using Gtab, try TeamDRH method but modify the size of the partition.
If u are using Zpad, try again.
Clear cache and reset before installing.
Try previous older ROMs and gradually update to newer ones.
Reset and wipe before each update.
As I didn't get any problems, so I can't say whats wrong with your installation.
And very sorry for the late reply.
I have exams.
But my tablet is very stable after this.
Everything is running smooth, even HD games.
Goodluck :fingers-crossed::fingers-crossed::fingers-crossed:

rajeevvp said:
I'd still like the output of those commands--for my own edification.
Click to expand...
Click to collapse
I tried it in terminal emulator, but it says 'Operation not permitted'

kank_fraud said:
I tried it in terminal emulator, but it says 'Operation not permitted'
Click to expand...
Click to collapse
same here.

kank_fraud said:
I tried it in terminal emulator, but it says 'Operation not permitted'
Click to expand...
Click to collapse
Fixed commands. Try them again.

I seem to have everything running and it seems really fast, the only problem I have is that the home button (hardware and soft) does not work!
I've tried installing a different home app, tried home switcher and I get asked when the tablet boots as to which home app to use, but still the buttons don't work (back and recent apps work).
Any ideas???

CWM v5.0.2.0 E:Bad boot message "recovery"?

hello friends. have p509, 2.2 froyo, have rooted z4root, have cwm v5.0.2.0 installed. when I boot to recovery, I get the CWM menu, but no functionality - I can browse the top menu, but select any item and it misfires: [I get the logo].
The error msg is simply E:Bad boot message, "recovery"
the handset functions ok - boots fine, no issues that I can see.
Should I just overwrite this with a different recovery like amonRA or TWRP or should I flash the same cwm again?
Does CWM have a problem running from a 34GB SD Card? I searched my error and did not find on exact handset but on another and this was the implication, and a patch was offered for that handset, so I don't know if that is relevant here.
thanks for your guidance
c

cognus said:
hello friends. have p509, 2.2 froyo, have rooted z4root, have cwm v5.0.2.0 installed. when I boot to recovery, I get the CWM menu, but no functionality - I can browse the top menu, but select any item and it misfires: [I get the logo].
The error msg is simply E:Bad boot message, "recovery"
the handset functions ok - boots fine, no issues that I can see.
Should I just overwrite this with a different recovery like amonRA or TWRP or should I flash the same cwm again?
Does CWM have a problem running from a 34GB SD Card? I searched my error and did not find on exact handset but on another and this was the implication, and a patch was offered for that handset, so I don't know if that is relevant here.
thanks for your guidance
c
Click to expand...
Click to collapse
CWM 5.0.2.0 is buggy. I'd recommend changing to another recovery. I use a touch version on my P509, but it will only allow installation of P500 ROMs. There is a work-around for this tho. In the ROM is a file -> META-INF/com/google/android/updater-script. There is an 'assert' statement at the top of that script that can be edited to specify P509, or it can be removed all together. Of course, you can also use OOne ROM Editor to trim the ROM and remove the assert statement automatically.

The error message
E:Bad boot message, " recovery"
Click to expand...
Click to collapse
can be safely ignored. You'll get that every time you boot into recovery.

That error message means you dont have SD-ext. Ignore it.
Re-flash the recovery, cwm 5.0.2.0 is stable. Have you re-map your your hardware buttons?
If no.. try other keys.. menu button is to select.. when you see logo use power button.
Recovery is not related to your sd card size. 32GB is max our phone can support!!

FINALLY found a way to nuke CWM. I reloaded it a half dozen times but always the same outcome - zombie. thankfully did not brick.
finally found a GOOD correct instruction about flashing new recovery via LGMDP, added the partition file to the folder with Amon/thunderg and successfully got that one loaded. I can't count how many 'guides', tuts, steps, suggestions I read that never once mentioned the need for the partition.mbn file.
thanks for your responses, however.
rr0yy said:
That error message means you dont have SD-ext. Ignore it.
Re-flash the recovery, cwm 5.0.2.0 is stable. Have you re-map your your hardware buttons?
If no.. try other keys.. menu button is to select.. when you see logo use power button.
Recovery is not related to your sd card size. 32GB is max our phone can support!!
Click to expand...
Click to collapse

cognus said:
FINALLY found a way to nuke CWM. I reloaded it a half dozen times but always the same outcome - zombie. thankfully did not brick.
finally found a GOOD correct instruction about flashing new recovery via LGMDP, added the partition file to the folder with Amon/thunderg and successfully got that one loaded. I can't count how many 'guides', tuts, steps, suggestions I read that never once mentioned the need for the partition.mbn file.
thanks for your responses, however.
Click to expand...
Click to collapse
Glad you got it worked out. Requiring the partition.mbn is not a normal procedure around here. That's why it was never mentioned. I've flashed countless recoveries on the P509 which is identical to the P500 and then also on the P506. Apparently somehow your partition tables got screwed up.

wish I understood that better. I had the same issue with two different sd cards employed - everything else about the handset/rom etc all worked swell. never an issue... just the doggone CWM. I did notice on the small 2gb card that the optimus never would illuminate the Format option - I wiped it and wanted the handset to format but no option allowed. formatted it then with sdformat [win7].
the 32gb sandisk had been my main squeeze for a couple years on the p509

cognus said:
wish I understood that better. I had the same issue with two different sd cards employed - everything else about the handset/rom etc all worked swell. never an issue... just the doggone CWM. I did notice on the small 2gb card that the optimus never would illuminate the Format option - I wiped it and wanted the handset to format but no option allowed. formatted it then with sdformat [win7].
the 32gb sandisk had been my main squeeze for a couple years on the p509
Click to expand...
Click to collapse
Windows doesn't handle partitioning correctly for Linux file systems. Try this tool instead. I've never used it, although I do have it installed. It does come highly recommended.