Related
First let me say thanks to all of you, I purchased my wife what was out of the box a useless machine. Then before I had an sd card out of desperation I used the tnt lite and flashed off onboard storage. all went fine.
Today I see there has been a few updates so I installed a microsd (16gb ) and attempted to do it correctly using the CW mod install guide. I mounted the card and used Es FE to extract the cwmod to root /sdcard folder then I powered down and did the volume +/power. I seen the prompts it looked like it went through. then i booted back into os and used esfe to delete them out of root booted down and it shows the prompts then a yellow exclamation and just goes back into OS no matter what I have tried. I tried several times.
I dont want to mod the unit anymore without the recommended recovery methods could someone guide me a bit why I cant get cwmod to load?
thanks
bump for attention
if you are using the internal sdcard.....SDCARD:
/sdcard/update.zip
/sdcard/recovery/command
"command" must have this line in it
--update_package=SDCARD:/update.zip
OR external sdcard.......SDCARD2
/sdcard2/update.zip
/sdcard2/recovery/command
"command" must have this line in it
--update_package=SDCARD2:/update.zip
CHECK THE COMMAND FILE. If you are booting with Power/Vol+ and its not going to the clockwork menu then clockwork is not installed. Installing any Viewsonic updates will erase cwm recovery
This'll make it do the recovery
sgilbert said:
First let me say thanks to all of you, I purchased my wife what was out of the box a useless machine. Then before I had an sd card out of desperation I used the tnt lite and flashed off onboard storage. all went fine.
I powered down and did the volume +/power. I seen the prompts it looked like it went through. then i booted back into os and used esfe to delete them out of root booted down and it shows the prompts then a yellow exclamation and just goes back into OS no matter what I have tried. I tried several times.
Click to expand...
Click to collapse
I had the same scenario and it was due to the editor I was uing to make the recover/command file. Just delete what is in the recover/command folder, and unzip the file in the following link, and copy the file in the command folder to the SD. It WILL work with the next effort of install with the vol+ and power button function (sys recovery?) I got it to work, thanks to Robeet's Explanation....
The File is what I extracted from the original plain vanilla file that Robeet had referenced to on this forum. I only took the recovery/command part of the package.
Here is the link:
http://hotfile.com/dl/92124038/c519e7c/recovery_sdcard.zip.html
Good Luck!
Hey all, just wanted to give a quick rundown. I shared this on Slickdeals earlier and someone recommended I throw it over here so that it might help anyone. My Coworker got his gTablet yesterday (from the Woot deal in March) and I had the chance to play with it/flash a custom ROM.
First about the stock ROM. His had angry birds and flash preinstalled, there were some funny directories setup on the internal storage which included a few apps (angry birds and flash amoungst them). I suspect they did some funny business at the factory with our units, but it did not in ~ANY~ way appear to be used/returned etc. The directories I remember were "Master", which I believe had apps and ... Oh hell it's too long now, something else. Anyways it didn't appear to be anything other than new is my point.
Next, the screen. It was definitely a TN panel and did have some odd viewing angles, and while not ideal it was certainly not anything that was preventing one person from enjoying it, vertical or horizontal. It was difficult for others to gather around and see videos well, so if that is a large concern for you then be concerned I suppose.
The stock ROM. It came with 1.1-3381 (or whatever the 33 was). It really does suck. They disable the menu button in most locations with the stock ROM, and it was slow/sluggish just like everyone has been saying.
Now I hope this crash course is of some help to anyone with their new toy. First to check your ROM version, you can go tab the Gears icon at the side of the screen, then choose About in the left menu. In here you'll find the rom version (should be something like 1.1-3389, 1.1-3588 or 1.2-something). Here's what I did to get his updated. Get familiar with XDA, it'll be a great friend and resource.
1.) I loaded the 1.1-3588 stock recovery, an upgrade from the 1.1-3389 recovery. It was possible to do this by going to this page (don't forget to thank Roebeet for putting all of this together), downloading the "3588 Recovery Pack v1.0".
2.) Unzip the 3588 Recovery Pack v1.0 then connect your tablet to your PC and enable USB mode (when you plug it in, you'll need to click the Yellow/Orange circle in the upper-right, then choose to enable USB tethering). Copy the "recovery" folder, and the update.zip to the root (what opens when you double-click the tablet drive) of the tablet internal memory (Probably D: or F: ).
3.) After the files copy to the tablet, turn off USB tethering, then turn off the tablet. You'll be restarting it in Recovery, which will automatically load the new recovery.
4.) To start the tablet in recovery, have the tablet turned off, then press and hold the power button and volume + button. You'll see a small message in the upper-left to indicate that it is starting in recovery. You can release the buttons now.
5.) After the update finishes installing the tablet will automatically reboot to Android once again, with the ugly Tap And Tap interface. This is OK, you're two steps from fixing it.
6.) Turn on USB tethering again, then open the tablet folder and delete the recovery folder and update.zip.
7.) Go back to this page, and once again thank Roebeet, and download "clockworkmod .8 bekit". Once downloaded, unzip it, then copy the recovery and update.zip to the root of the internal memory again. Turn off the tablet.
8.) Start the tablet in Recovery again by holding power button and Volume + at the same time. Once again you'll see a message in the upper-left and you can release. It'll do its thing and reboot to Android when it completes.
9.) After you get into Android again, start USB Tethering then delete the recovery folder and update.zip.
10.) At this point you can load what ROM you want (within limits, BE SURE TO READ THE ROM THREADS FIRST). I installed Vanilla AOSP Gingerbread ROM. Go download the file from that thread, then place it into the root of your tablet internal memory. Be sure to thank kornyone for their work. Also be sure to download the "gapps" available on this page as well, for you will have to install it to have the Android Market, GMail, etc.
11.) To install it, turn off the tablet, reboot into Recovery (Power button & Volume + at the same time..). You'll now be in Clockworkmod, a custom recovery. You can navigate the custom recovery by using the volume rocker to go up and down, the power button to go back a menu, and the Home soft key to press enter.
To properly install a ROM you should always first clear the data/system/cache. It's been a while since I've used clockworkmod, but I believe the option you are looking for is Factory Data Reset, choose Yes on the next screen. Then delete cache just to be sure.
Now you can go to "Install ZIP from sdcard", then "Choose zip" or something akin to it. Navigate to the file you copied, and tell it to install. Wait a short while and you should see that it successfully installed. Now just press the power key a few times to get back to the main menu and then choose to Reboot (whatever the top option is).
Enjoy your Gingerbread Android.
A few app recommendations: I use LauncherPro. It's available in the Android market and it's a "Home" replacement. Try it out, it's smooth and it has a bunch of extra widget if you purchase the program (1.99). Also check out Dolphin Browser HD. The last word of advice I can give is to get familiar with Long Press, it's basically right-click in Android. To do a long press just hold down on an icon or a blank area and see what happens.
A round of thanks go out to Roebeet and kornyone for putting the files used together, and a special thanks for the excellent documentation Roebeet. If I've left anyone out or placed this post in the wrong section please let me know and I'll get it fixed.
newbie question
I load the clockworkmod recovery and nothing changes. How do I get the clockwork mod to work? I already have my gTablet rooted. Now just trying to get to where I can load a custom ROM.
Thanks
apboswell said:
I load the clockworkmod recovery and nothing changes. How do I get the clockwork mod to work? I already have my gTablet rooted. Now just trying to get to where I can load a custom ROM.
Thanks
Click to expand...
Click to collapse
If you have flashed clockwork properly then to power on your device hold the volume up key as press the power button. This will load the recovery kernel and the clockworkmod, from which you can backup your device and install custom roms.
Just wanted to posted a quick update -- Two of the tablets that people at my workplace ordered suffered an odd corruption of the internal memory. The symptoms were random app's force closing, then upon trying to reboot the device it simply boot loops (the OS screen displays, then flips back to Viewsonic -> Load screen, repeat endlessly). Got them booted into recovery and tried to load data to which it reported the data partition could not be loaded due to the block being inaccessible. After a quick search the solution to this problem if you encounter it is:
1.) Boot into clockworkmod .08 by holding the power button and volume + button until you see the Recovery key press detected in upper-left.
2.) Go to advanced using the volume buttons, then press the home key to enter the advanced menu.
3.) In here go to Partition SD Card and select 2048, then 0. Wait a few minutes and the data partition will be ready to go again.
At this point I went ahead and did formatted the following partition through the mount menu: boot, system, data, cache. Afterwards I loaded the ROM again and everything appears to be working well.
Hope this helps anyone else who gets this random error.
Good post! Thanks!
The SD repartitioning is a very common fix here, in XDA. Usually it's what we try if you have weird FC's or file corruption and a re-flash or data wipe doesn't fix things. I've had to do that at least twice on my own device, over the last 3 months or so.
Also, keep in mind that the 3588 Recovery Pack is designed with a rooted ROM in mind (it lets you flip back and forth between clockworkmod and standard recovery via a script that can run off the GTablet or via adb)
**** USE AT YOUR OWN RISK ****
The following is posted so that I may share what I've done. It was done by me and for me. If you use it for you, then you take responsibility for whatever happens. This could, potentially, cause problems. It certainly will void your warranty (though it's pretty easy to undo this with no obvious signs.)
Install ClockworkMod Recovery and roots your P6210 tablet.
DO NOT ATTEMPT TO RESTORE ANY CWM BACKUP MADE WITH ANY OTHER VERSION/REVISION. IT WILL BREAK THINGS. THIS VERSION IS NOT BACKWARDS COMPATIBLE. JUST START WITH FRESH BACKUPS AND BE HAPPY.
WHAT THIS DOES:
Installed from recovery, this .zip will first ensure that it's running on the Samsung GT-P6210. If you have a different model, don't waste your time downloading it. It won't work. I have a P6210 to test with. I don't have any other 7 plus tab, so I can't test any other 7 plus tab, and therefore won't even act like it might work. If you want to try it anyway, you should have the knowledge to repair whatever you break - in which case you'll also have the knowledge to unpack this zip file and do things the manual way.
(starting with 20111210, a backup of the recovery is no longer made. I feel this is no longer needed as there is a confirmed working ODIN package people can use to restore their tablets with.)
Next, a new version of the clockwork mod recovery is installed.
(starting with 20111210, old backups are no longer purged. If you are upgrading from my original CWM recovery (previous to Dec 9th), please manually delete old clockwork recovery backups, as they are NOT VALID and will destroy your normal boot operation if you attempt to restore with a proper/current version of this recovery.)
Finally, the tab will be rooted. This only involves copying a tiny file (called 'su') to the system. In order for most android apps to make use of that, however, another application must be first installed. (See "Finishing SuperUser installation" below.) I considered putting that "SuperUser" application as part of this package, but it's really very easy to get it from the market.
INSTRUCTIONS:
Put the installation zip file on your tablet's external SD card. If you don't have an external SD card, you won't be able to install this. MicroSD cards are cheap. If you have a tablet that costs 399 USD, you can afford to spend a few extra dollars/euros/pesos/whatever on a microSD card. Just get one. Not only is it required for installing this from the factory recovery, but it makes a great place to back things up to. A nice 16GB card is suggested. 32GB is better. You'll need AT LEAST 1GB for this recovery. If you have a previous version of CWM already in-place, you won't need the storage card.
You can download the .zip file directly to your tablet and then possibly use the built in "My files" applet to move it to extStorages/SdCard, or you could download it to your computer and use "adb" to push the file to /mnt/sdcard/extStorages/SdCard, or you should be able to get it there with "Kies." If you have the proper adapter, you could also attach the microSD card directly to your computer and just copy it there. It doesn't matter HOW you get it on the card, as long as it's on the card.
After the zip file is on your microSD card, and the microSD card is inside (and recognized by) your tablet, then you need to...
Boot into recovery mode.
If the recovery version banner is "CWM-based Recovery v5.x.x.x", then you already have a version of CWM installed and should skip ahead to the proper section. If the banner is "Android system recovery (3e)", then you have the factory recovery and should continue with...
Installing from factory (3e) recovery:
Use the volume up/down buttons to move the highlight up and down, and the power button to select the highlighted option.
1. Select "apply update from external storage"
2. Select the file you placed on your storage card (starts with "p6210_CWMR".)
3. Sit back and watch it run. Read the information that is being sent to the screen. If there's an error, it'll display some message. If it works, it'll display a message starting with the word "Done!"
4. Select "reboot system now."
You now have a CWM-based recovery installed, and your tablet is rooted.
Please skip ahead to "Finishing SuperUser installation"
---------------------------------------------
Installing from CWM-based Recovery
Use the volume up/down buttons to move the highlight up and down, and the power button to select the highlighted option.
1. Select "Install zip from sdcard"
2. Select "choose zip from internal sdcard" (which will actually point to the external card.) (If you are upgrading and chose not to put the .zip on the external microSD card, you might need to select "choose zip from sdcard" instead.)
3. Select the file you placed on your storage card (starts with "p6210_CWMR".)
4. Select "Yes - Install (whatever filename you selected)"
5. Sit back and watch it run. Read the information that is being sent to the screen. If there's an error, it'll display some message. If it works, it'll display a message starting with the word "Done!"
6. Select "+++++ Go Back +++++"
7. Select "reboot system now."
---------------------------------------------
Finishing SuperUser installation
Install the SuperUser application directly from the android market:
https://market.android.com/details?id=com.noshufou.android.su
....
Post-installation Notes and Issues
It's a known issue with the version of CWM used in this recovery that the "internal sdcard" actually references the built in storage on the tablet. So, if you want to back up to your microSD card, choose "backup to internal sdcard". I'm retaining this issue to stay "compatible" with other CWM recoveries of the same version number. (won't fix)
The .zip package displays an incorrect version identifier/date when version 20111209 is being installed. (It's shows a banner with the date of 06-Dec) (cosmetic)
This recovery is NOT compatible with firmware updates via Kies (and perhaps not via other samsung official methods.) In order to perform a firmware update, I suggest the following procedure: First, perform a CWM Recovery backup, then use the ODIN package found elsewhere to restore this tablet to a factory state. Let Kies upgrade the tablet to whatever version it wants (give it a few tries in case multiple upgrades are needed.) Then re-install this recovery, and perform an "advanced restore" (or "advanced restore from internal sdcard if you made the backup using the similar option.) From there, restore "data." That will leave the entire firmware update in place. (boot is the normal boot kernel; system is what people like to call a ROM here, but is the samsung pre-installed apps; and data contains the applications you install and all your data.) Then "go back", wipe the cache partition, advanced, and wipe the dalvik partition. HOWEVER, please note that I have no way to know if any given samsung firmware update is "compatible" with this restore unless I've tried it myself. It's compatible with everything released up to the date of this note (10-Dec-2011), but I can't predict the future.
Donation?
I don't take donations. If you have spare money (I don't), please donate it to the Salvation Army, Red Cross, or just find a homeless person on the street and give them something. My favorite charity is the Shriner's Hospital for Children. (yes, I am.) If you'd like to thank me, there's a button at the bottom of this post dedicated to that. If you don't want to thank me, that's okay too.
Changes for 20120107:
Brought the recovery kernel up to date with the normal boot kernel. The only impact should be that if you keep crashing any time you boot normally (and before you are able to perform any action), you can now boot into recovery to _hopefully_ be able to retrieve the /proc/last_kmsg as a diagnostic tool.
Reduced the size of the .zip quite a bit.
Changes for 20111210:
* A backup of the existing recovery image is no longer being made. I feel this is no longer needed, as an ODIN package is now confirmed to be working that people can use to restore their tablets to a factory state.
* Old clockworkmod recovery backups are no longer being deleted when installing this. If you are installing this or newer from my CWM recovery previous to Dec 9th, 2011, please manually delete all those old backups. If you attempt to restore them, please be prepared to download ODIN and a factory ODIN image, as you'll need it in order to get your tablet working again. You've been warned...
* The issue that was causing backups to the tablet's built-in storage to fail has been corrected.
Changes for 20111209:
* Issues with getting into recovery are resolved.
* a backup of the recovery is only made if there is no sign of a previous version of this same recovery in place
Credits
Most obviously, Koush for his wonderful clockworkmod recovery. It's the basis of this entire project. Entropy512 for pointing me in the proper direction on a couple of things, pershoot mods to CWM for the Galaxy Tab 10.1 that I ported over to this one (due to the different partition structure of honeycomb devices.)
Links are below...
Take care
Gary
thanks gary, how might we be able to tell if this will be kosher with 3g version? do we need to --dump all pit via heimdall to ensure all partitions match up,etc? Thank you for your speedy work.
chrisrotolo said:
thanks gary, how might we be able to tell if this will be kosher with 3g version? do we need to --dump all pit via heimdall to ensure all partitions match up,etc? Thank you for your speedy work.
Click to expand...
Click to collapse
It's not kosher at all. I didn't wash my hands before compiling it, and had bacon bits on my salad for lunch. Sorry.
Thanks Gary. I have been watching your progress for about a week and you are like a put-bull. Amazing. u da man!!!
Pit bulls would be shamed as wussies. Many great devs possibly have a touch of Asperger's syndrome (with MUCH better socialization skills!) which, with tasks like this, is a benefit! At the very least just plain tenacious! lol
Thanks Gary. I've learned a lot just following along reading the discourse between you and others like Entropy. Appreciate it.
garyd9 said:
It's not kosher at all. I didn't wash my hands before compiling it, and had bacon bits on my salad for lunch. Sorry.
Click to expand...
Click to collapse
ahhh , close enough. anyways what could we do to find out without actually flashing this to possible incorrect partition??
chrisrotolo said:
ahhh , close enough. anyways what could we do to find out without actually flashing this to possible incorrect partition??
Click to expand...
Click to collapse
Which "3g" model do you have? The tmobile one or the international one?
I'm trying to narrow down which is the GT-P6200 and which is the SGH-T869!
I'm working with someone via PM and email to get the information needed for the SGH-T869, and I think it'll be pretty easy to get a recovery together for it, but other people will have to test and validate. I think this is the tmobile version...
international p6200
Soft Brick(kinda Sorta - well not really). Using defult 3e recovery. Tab would boot up, but would not go into recovery at all. Nada Nada. Thought it might have been some leftovers from other stuff I have been trying, so I odin3'd the factory image, did a wipe all and tried it again. Same difference. The only thing I could really think of was maybe I had a corrupted download.
funny thing is that it would boot up into the OS. Just not into recovery. will keep trying as I really want a way to make nandroid backups.
otamctech said:
Tab would boot up, but would not go into recovery at all.
Click to expand...
Click to collapse
No need to ODIN... that's why the package creates that backup recovery image. However, you said it's booting normally, correct? If so, it's not broken or bricked (and I experience the exact same thing.)
For some odd reason (that I haven't been able to figure out), after I flash a non-stock recovery, its very difficult to get the tab into recovery mode. Some times I get it instantly, and some times I have to try several times in a row. Are you using adb? If so, it might be easier. Power off the tab, plug it into your computer, and eventually the tab goes into a "low power mode" where you see the battery gauge but nothing else. From there (again, assuming you have adb installed/working), you can just run "adb reboot recovery" That usually gets me into recovery. 90% of the time.
If not, just try again. If you see the samsung animation starting, press/hold the power button to turn it off again, then press/hold volume up again... etc. It's a PITA, and a major annoyance of mine.
Two things about it make it REALLY annoying for me. First, I'm using samsung's own kernel for this... but I'm just repacking the initramfs portion of it. Second, if you put the factory recovery back, it's easy to get into recovery again.
chrisrotolo said:
international p6200
Click to expand...
Click to collapse
I'll get to that one eventually. I'm commited to do the tmobile one next, and I REALLY need to concentrate on my full-time job (the one that pays me a salary) which only leaves me a couple hours each day.
take care
Gary
absoultely, take your time. Is there a certain battery percentage requirement to get into either stock or CWM recovery say 50% or 60% minimum? we had this issue on dell streak 7. Let me know if I can help with partition layout or anything for p6200. thanks.
chrisrotolo said:
absoultely, take your time. Is there a certain battery percentage requirement to get into either stock or CWM recovery say 50% or 60% minimum? we had this issue on dell streak 7. Let me know if I can help with partition layout or anything for p6200. thanks.
Click to expand...
Click to collapse
No hard requirement I'm sure - but flashing at below 50% is just a stupid reckless risk, plain and simple as that.
If you are having issues getting into recovery after flashing this...
Here's a procedure I've come up with that has allowed me to get into this recovery 9 out of 10 attempts (and it doesn't require any special connections to a computer.) Please read all the steps before starting so you're prepared for what comes next. It'd really be annoying to have recovery finally pop up, but you weren't paying attention so the tablet turned off.
power off the tablet
Throughout this entire process the volume UP switch should be held and not released. This is the side of the volume switch closest to the power button. Once you see your recovery screen, you can release the volume switch (and any other button you might be holding at that time.)
Press/hold Volume Up (constant)
Press the power button, hold it down for 2-3 seconds, and release it.
You'll see the Samsung logo screen for a few seconds...
Instead of the expected recovery screen, you might see the samsung boot animation with music. If so, immediately (without releasing volume up), press and hold (and keep holding) the power button. Don't let it go this time.
The tablet will appear to power off after holding the power button for a few seconds, and then will power back on a second or two later.
(you're still holding that power button, right? how about volume up? Good.) Again, you'll see the samsung logo screen for a few seconds...
Instead of the boot animation, recovery should pop up this time. Release the power button as soon as it does or you'll just turn the tab back off again. You should also release the volume UP at this point.
(If you've flashed my recovery, please try this. If it doesn't work, please take the effort to reply to this post so I can know what people other than myself are experiencing.)
Take care
Gary
updated OP with:
Post-installation Notes and Issues
I'm aware that after flashing this, it is difficult to get back into recovery. I'm not sure WHY, but it's fairly consistantly a pain in the rear. However, I have found that following the steps in the following post seems to work (at least for me) 9 out of 10 times. (I was distracted on the 10th try, so not sure if it worked or not): http://forum.xda-developers.com/show...6&postcount=14
Remember above I mentioned that when this package installs, it creates a backup of the old recovery? Well, it does that no matter what recovery was in place. So, if you install this package with a factory recovery, that backup will be of the factory recovery (which is probably what you want.) If you install this package a second time when you already have the CWM Recovery installed, you'll overwrite that factory recovery backup with a backup of the CWM recovery (which makes no sense.) I'd strongly suggest that after you FIRST install this package, you make a copy of that backup recovery image file (and full filename is displayed when it's created), and stick that copy someplace safe. Perhaps just rename it and copy it to your SDcard or computer. A good name might be "p6210_factory_recovery.img"
The Tab 10.1 could be difficult to get into recovery too.
Usually, the following works for me:
Press and hold VolUp
Press and hold Power until the screen turns on (this is slightly different from your instructions)
Release Power but keep holding VolUp until Recovery shows
__________________
somebody9 said:
I was wondering if anyone knows what needs to be deleted in order to get rid of that pesky pop up menu you get by pressing on the Chevron/Arrow in the middle of the bar.
Click to expand...
Click to collapse
Please start a new thread for a new topic. Try to keep this one isolated to the CWM recovery.
garyd9 said:
Please start a new thread for a new topic. Try to keep this one isolated to the CWM recovery.
Click to expand...
Click to collapse
Sorry about that. Post removed.
Garys method of booting into recovery works fine. I'm just going to post it in linear format.
1. Press the power button and select Power Off
2. Press the volume up button (closest to power button) and do not release until the recovery screen is displayed
3. Press (do not hold) the power button
4. The static Galaxy 7.0 Tab Plus screen will display (possibly twice)
5. When the animated Samsung screen displays, press and hold the power button
6. The static Galaxy 7.0 Tab Plus screen will display
7. Release all buttons when the recovery screen displays.
This works every time for me
Hi guys, this is the first post i upload and want to take the occasion to greet you all.
In these days i bought a Samsung Infuse 4G...i really like this phone but want to be able to use it with some special features such as connecting various USB devices to the phone and other juicy stuff.
I read that the builtin ROM is not capable of such this thing, and Ice Cream Sandwitch, witch should allow to do that, is not available for this smartphone model. At least not officially.
My choice fell upon CM7 LinuxBozo ROM ( http://forum.xda-developers.com/showthread.php?t=1311960 ).
I rooted my device. I'm sure of that because i am able to use the root explorer with root privileges and the root menu shows up among my applications.
I then followed the instructions here ( http://forum.xda-developers.com/showthread.php?t=1107881 ) in order to install the ClockWorkMod Flashing Menu but I am not sure whether anything went allright or not as, after trying both the methods shown on the guide, nothing happened (in the first case, the automatic install through ROM Manager seems to work, a message appears on the screen confirming anything went smooth but when i reboot i see the normal reboot menu, no advanced menu nor CWM menu; in the second case i tried to manually load the CWM menu by placing the update file in the SD and renaming it to update.zip, the update gets stuck somewhere saying something about a bad or wrong signature, tried it a few times and with different CWM update versions but nothing to do).
I then stumbled into a workaround to fix that issue by an even more manual procedure ( http://www.youtube.com/watch?v=PkMo8rBehHg&feature=related ) basically consisting in copying the "recovery" executable from the CWM update archive to the directory /system/bin and of course chmodding it to rwxr-xr-x and chowning it to the root.
Now the CWM screen appears but, as i attempt to flash the CM7 ROM, the flashing gets stuck at "Finding update package". I read here ( http://forum.xda-developers.com/showthread.php?t=821499 ) that it could happen sometimes and it's just a matter of trying and trying again... I tried at least ten times up to now but it keeps getting stuck...maybe it's not my case.
Hope someone will help me out...i really need that USB reading feature. Thank you.
baareem said:
Hi guys, this is the first post i upload and want to take the occasion to greet you all.
In these days i bought a Samsung Infuse 4G...i really like this phone but want to be able to use it with some special features such as connecting various USB devices to the phone and other juicy stuff.
I read that the builtin ROM is not capable of such this thing, and Ice Cream Sandwitch, witch should allow to do that, is not available for this smartphone model. At least not officially.
My choice fell upon CM7 LinuxBozo ROM ( http://forum.xda-developers.com/showthread.php?t=1311960 ).
I rooted my device. I'm sure of that because i am able to use the root explorer with root privileges and the root menu shows up among my applications.
I then followed the instructions here ( http://forum.xda-developers.com/showthread.php?t=1107881 ) in order to install the ClockWorkMod Flashing Menu but I am not sure whether anything went allright or not as, after trying both the methods shown on the guide, nothing happened (in the first case, the automatic install through ROM Manager seems to work, a message appears on the screen confirming anything went smooth but when i reboot i see the normal reboot menu, no advanced menu nor CWM menu; in the second case i tried to manually load the CWM menu by placing the update file in the SD and renaming it to update.zip, the update gets stuck somewhere saying something about a bad or wrong signature, tried it a few times and with different CWM update versions but nothing to do).
I then stumbled into a workaround to fix that issue by an even more manual procedure ( http://www.youtube.com/watch?v=PkMo8rBehHg&feature=related ) basically consisting in copying the "recovery" executable from the CWM update archive to the directory /system/bin and of course chmodding it to rwxr-xr-x and chowning it to the root.
Now the CWM screen appears but, as i attempt to flash the CM7 ROM, the flashing gets stuck at "Finding update package". I read here ( http://forum.xda-developers.com/showthread.php?t=821499 ) that it could happen sometimes and it's just a matter of trying and trying again... I tried at least ten times up to now but it keeps getting stuck...maybe it's not my case.
Hope someone will help me out...i really need that USB reading feature. Thank you.
Click to expand...
Click to collapse
what color is your cwm screen?
this may be a simpler way of gettin cwm:
http://forum.xda-developers.com/showthread.php?t=1220090
specifically, the CWM instructions set.
I see that the instructions you suggested me would mean to start the process almost from scratch. I will do that as soon as i finish studying the nazis for my school report .
And maybe after getting the next answer from you
The boot screen is green text on black backgroud.
Holding audio and power buttons for 10 seconds doesn't prompt me to the red boot screen if it was what you meant and if I read the instructions provided well (witch i didn't as i have no time now)... don't get me wrong. Just trying to provide you as more information as possible.
baareem said:
I see that the instructions you suggested me would mean to start the process almost from scratch. I will do that as soon as i finish studying the nazis for my school report .
And maybe after getting the next answer from you
The boot screen is green text on black backgroud.
Holding audio and power buttons for 10 seconds doesn't prompt me to the red boot screen if it was what you meant and if I read the instructions provided well (witch i didn't as i have no time now)... don't get me wrong. Just trying to provide you as more information as possible.
Click to expand...
Click to collapse
if you still have root, download from market
sgs kernel flasher and the flash the gingerbread kernel to give you RED recovery and flash the rom of your choice after a factory reset and usual wipes
Cool... i'm now running CM7 !
Here is what i missed for anyone who would have the same problem in the future (you can find the download links here: http://forum.xda-developers.com/showthread.php?t=1220090 ):
CWM Installation Instructions:
1) You must be rooted.
2) If you have a /Voodoo folder on your internal SD card, delete it and reboot.
3) If you're already running a custom ROM with Voodoo lagfix FULLY enabled, you can skip to step 7.
4) Download CWM-community-kernel-v8.zip if you're on Froyo or CWM-infused-v2.0.1-kernel.zip if you're on Gingerbread and place it on your internal SD card.
5) Install SGS Kernel Flasher from the Market.
6) Open SGS Kernel Flasher, select choose kernel, select the file you downloaded, and select flash kernel. Your phone will reboot and begin to enable Voodoo lagfix. Let it do that and boot all the way up. It will take a while (5-10 minutes) because it's converting all partitions to ext4.
7) Download update-infused-v2.X.X-full.zip and place it on your internal SD card.
8) Power off your phone.
9) With the phone powered off, hold both volume keys and the power button for about 10 seconds and then release. This should boot you into RED CWM.
10) Select "install zip from sdcard" and select update-infused-v2.X.X-full.zip.
11) Once that finishes, select "wipe data/factory reset".
12) Select "reboot system now".
13) Do NOT restore system data with Titanium Backup. Do NOT restore ALL apps with data. If you absolutely must restore something with Titanium Backup, only restore MISSING apps with data.
Click to expand...
Click to collapse
Now just another question: i noticed different errors when running the market and other old built-in apps... I just need to reinstall gapps right?
yeah, that is why it's stickeyed.
you just had to read/search them.
market wise, there's a market fix
or you can also factory reset and wipe cache and dalvik in cwm
Thanks. You helped me solving this and now anything works fine. Have a good day.
Thread (NOT) SOLVED.
--------
(Edited after realizing gapps still don't show up as installation didn't really worked)
baareem said:
Thanks. You helped me solving this and now anything works fine. Have a good day.
Thread SOLVED.
Click to expand...
Click to collapse
np. take it easy, bro.
I was too quick saying it worked.
The Infuse just booted up but nothing changed. I then tried to do the zip installing through rom manager again but invane.
When trying with the manual install it promts me with this error:
E: Can't open /emmc/gapps-gb-xxxxxxx-signed.zip
(bad)
Installation aborted.
Click to expand...
Click to collapse
I tried different versions of gapps including the one suggested in the CM wiki but with no luck. I guess the problem is somewhere else.
PS: now i see the blue on black bootscreen as in order to install gapps with rom manager i was asked to reinstall CWM trough it...
baareem said:
I was too quick saying it worked.
The Infuse just booted up but nothing changed. I then tried to do the zip installing through rom manager again but invane.
When trying with the manual install it promts me with this error:
I tried different versions of gapps including the one suggested in the CM wiki but with no luck. I guess the problem is somewhere else.
PS: now i see the blue on black bootscreen as in order to install gapps with rom manager i was asked to reinstall CWM trough it...
Click to expand...
Click to collapse
what version of ROM were you running when you tried this?
Stock FRoyo?
Cyanogenmod 7 ... exactly this version : http://forum.xda-developers.com/showthread.php?t=1311960
Kernel version is 2.6.35.7 , android v 2.3.7.
The old, OOB version i had was froyo 2.2.6 if i well remember.
baareem said:
Cyanogenmod 7 ... exactly this version : http://forum.xda-developers.com/showthread.php?t=1311960
Kernel version is 2.6.35.7 , android v 2.3.7.
The old, OOB version i had was froyo 2.2.6 if i well remember.
Click to expand...
Click to collapse
I haven't played with CM7, it's not an infuse based rom.
I recall some installation issues with it.
I remember an unsuccess reboot intially and pull battery thing..not sure.
If you're looking to install another rom, odin back to stock and start over.
check out my sig line for some useful links
Okay, so I am rather new to Rooting and Development. I had a couple issues and questions I need addresses for the Sidekick 4g.
First, I am having a problem getting the CWM recovery to work. I have already Rooted my phone via the SuperOneClick app. When I replace the recovery file in system/bin, with the update.zip on the root of my SD card, I flash the CWM recovery from ROM manager. When I reset my device holding Vol -, +, and power key, it still brings me to the Blue colored Samsung Recovery. WTF?
Second, I am a photoshop-head, and I wanted to customize my device. I have already located the 78 PNG files that compose the power-off video animation and altered them to create my own power-off sequence. But I am trying to locate the image file for the T-Mobile Sidekick 4g Samsung screen that comes on when you initially power-on the device.
also, when I replaced the PNG files for the power-off animation, it plays a bit more slowly when powering off. I believe this is because the PNG files I replaced the originals with must me larger in file size. The dimensions and resolution are still the same. anybody know a good way to reduce PNG file size? this one isnt as important I could prob. figure that out on my own with a little trial-and-error.
BUT I NEED THIS CWM WORKING! HELP!
1st ever post on here
In the blue recovery it should say something like install zip. You have to click that an install the update.zip file on your SD card.
wissing737 said:
1st ever post on here
In the blue recovery it should say something like install zip. You have to click that an install the update.zip file on your SD card.
Click to expand...
Click to collapse
for some reason on the blue recovery I dont have that option? just re-install packages, clear cache, reboot, etc. no install from zip option. I thought that option was only available on the red recovery, which is why im trying to get that one. I replaced the recovery file in system/bin already multiple times and still no luck.
youngzae said:
for some reason on the blue recovery I dont have that option? just re-install packages, clear cache, reboot, etc. no install from zip option. I thought that option was only available on the red recovery, which is why im trying to get that one. I replaced the recovery file in system/bin already multiple times and still no luck.
Click to expand...
Click to collapse
I thought there was a option in stock recovery that said install update from SD card and then it would install the one you put on the SD card and then it would bring you in too the custom recovery.
Actually im pretty sure you have to click reinstall packages and that will bring you into it.
wissing737 said:
I thought there was a option in stock recovery that said install update from SD card and then it would install the one you put on the SD card and then it would bring you in too the custom recovery.
Actually im pretty sure you have to click reinstall packages and that will bring you into it.
Click to expand...
Click to collapse
you may be right. but when I try to re-intsall packes it gives me an error message. ill replace the recovery again, replace the update.zip, and give it another try then see what it does...
wissing737 said:
I thought there was a option in stock recovery that said install update from SD card and then it would install the one you put on the SD card and then it would bring you in too the custom recovery.
Actually im pretty sure you have to click reinstall packages and that will bring you into it.
Click to expand...
Click to collapse
WOW this is like the 10th time I tried it and it actually worked this time! thanx for telling me to do the same crap i did already lol it finally worked
youngzae said:
WOW this is like the 10th time I tried it and it actually worked this time! thanx for telling me to do the same crap i did already lol it finally worked
Click to expand...
Click to collapse
hahah no problem, i dont think i can help you with your other problems though ,but good luck.