Database Info

[GUIDE] Fool proof install for stock 4349 (1.1 to 1.2 upgrade path)

Fool proof way to install 4349:
The reason there are so many steps is that they are broken down so that each step is basically one menu action. Follow EVERY step. Yes there are easier ways, this way ensures that your tablet is absolutly stock and wiped of all traces of other roms.
What you need:
1. A g Tablet with CWM 0.8 recovery (doesn't matter what ROM)
2. A stock 3588 image renamed to 'stock3588update.zip' (http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3588-user.zip)
3. A stock 4349 image renamed to 'update.zip' (http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-4349-user.zip)
4. A folder called recovery with a file in it called COMMAND inside it with the following line of text:
Code:
--update_package=SDCARD:/update.zip
4. Calkulin's Format_all.zip (attached here: http://forum.xda-developers.com/showpost.php?p=11946224&postcount=1)
Step 1: Ensure there is nothing on your g tablet you want. NOTHING!
Step 2: Boot to CWM recovery with Pwr and Vol+
Step 3: Go to the "mounts and storage" menu
Step 4: Choose "mount USB storage"
Step 5: Confirm there is nothing you want to save on your SD card. If there is anything you want, save it now.
Step 6: "Unmount" and go back to the main CWM Recover Menu
Step 7: Choose "advanced"
Step 8: Choose "Partition SD Card"
Step 9: Choose 2048M for Ext size
Step 10: Choose 0M for swap size
Step 11: Watch it Partioning SD Card, then when complete once again mount USB storage as in steps 3/4
Step 12: Load onto the SD Card: Calkulin's_FORMAT_ALL.zip, stock3588update.zip, update.zip (this is the 4349 file), the recovery folder with the command file inside it. Your Sdcard should look like the attached screen grab.
Step 13: Unmount and return to main menu of CWM.
Step 14: Choose "install zip from sdcard" then "choose zip from sdcard" and select "Calkulin's_FORMAT_ALL.zip"
Step 15: Proceed with the install, once finish select "choose zip from sdcard" and select "stock3588update.zip"
Step 16: Once it completes, go to the CWM recovery main menu then power off with the power button.
Step 17: Boot up into recovery with PWR and Vol+. This will initiate the 4349 install using the stock recovery.
Step 18: Watch your tablet boot into a bone stock 4349 rom.
An optional starting point for this is to use nvflash (back to stock recovery or CWM recovery) to repartition everything first to make fully sure all partitions are as they should be.

Nice! Well laid out with clear steps. I 100% agree that the cleaner your device is, the more likely that the 4349 upgrade will succeed. On clean 3588 stock, I've had about a 90% success rate, at least (but I have had a few soft-bricks too).
Going to work on 3588 nvflash today - need to test it out as I think we all really need it, at this point.

Just one question for clairifacation.. on the command line of text. Should it have the have the apostrophy and the beginning and end or not?

LisaBham said:
Just one question for clairifacation.. on the command line of text. Should it have the have the apostrophy and the beginning and end or not?
Click to expand...
Click to collapse
No, corrected. Thanks.

Just to post a bit of an update:
It is pretty easy to get rooted with z4root. The permanent option works. Also, installing the amazon marketplace was no problem. I actually like this setup better than google market because it stores all the free apps you download as well as the paid ones.
Additionally, the google apps (download from here: http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps get the ones for tegra on CM6) from CM6 were easy to install with the standard recovery. Looks like this latest stock version is pretty decent overall.

ramerco said:
installing the amazon marketplace was no problem. I actually like this setup better than google market because it stores all the free apps you download as well as the paid ones.
Click to expand...
Click to collapse
The biggest problem with the Amazon Appstore for Android is that it has far, far fewer apps than the Google Android Market. A large majority of the applications that I require (indeed, what I bought the tablet to run in the first place) are only available through the Google Android Market.

Followed step by step and everything seemed to go well until I tried to restart after the upgrade....nothing but a black back-lit screen. Tried resetting/factory reset, tried clearing cache, nothing. Had to NVFlash back to 3588 and tried to see if there was an OTA update but it says I am up to date with 3588. Then tried to manually install the 4349 update.zip which appeared to go through but again, same black screen afterwards. Very frustrating.

tsg2513 said:
Followed step by step and everything seemed to go well until I tried to restart after the upgrade....nothing but a black back-lit screen. Tried resetting/factory reset, tried clearing cache, nothing. Had to NVFlash back to 3588 and tried to see if there was an OTA update but it says I am up to date with 3588. Then tried to manually install the 4349 update.zip which appeared to go through but again, same black screen afterwards. Very frustrating.
Click to expand...
Click to collapse
Sounds like you were stuck in apx mode. Lucky you were able to boot at all!

jason1332 said:
Sounds like you were stuck in apx mode. Lucky you were able to boot at all!
Click to expand...
Click to collapse
Could be, but I don't think so. I got through the 3 birds screen then the g-tablet screen before it went black so I don't think I was in apx. I guess I will just wait until VS pushes the OTA Update again.

Is there any way to change the boot animation in 4349?

ideaman said:
Is there any way to change the boot animation in 4349?
Click to expand...
Click to collapse
Boot animation is still stored in the same place (system/media) so existing methods for changing it should work fine.

Hi Gents,
Questions,
- Is this flash will void my warranty?
- If I'm running from stock 3855 Rom form VS, from what step I should begin with?
Thanks,
Charles

I'd like to make a formal request that this guide be stickied?
Many people have been wanting to flash the HC rom, and this is the best guide I've found (used it myself) to safely, and efficiently get to the 1.2 bootloader and stock recovery in update 4349.
It does not instruct anyone, or link to Roms on other forums, just provides them with the information to reach a foundation to where they can use 1.2 based bootloader roms. We can't ignore that it's an important catagory of users.

TJEvans said:
I'd like to make a formal request that this guide be stickied?
Many people have been wanting to flash the HC rom, and this is the best guide I've found (used it myself) to safely, and efficiently get to the 1.2 bootloader and stock recovery in update 4349
Click to expand...
Click to collapse
At that time this was a good way to do it. Now, you can NVFLASH 4349 in a few minutes. Then when you reboot wipe data/cache.

jcflman said:
At that time this was a good way to do it. Now, you can NVFLASH 4349 in a few minutes. Then when you reboot wipe data/cache.
Click to expand...
Click to collapse
regardless, there isn't a stickied guide on safely getting to 1.2 from out of the box setup...this is the most comprehensive one I've found for a brand new user that doesn't have any experience with nvflash (I still don't) or even flashing a rom. I've answered 2 questions today from people that basically just opened the box and were wondering how to get to 1.2 from stock. or wanted a link to a stock rom/recovery image. I haven't found any other posts that have a stock 3588 or stock 4349 files link in it. This post does, without even going into the roms available for the 1.2 bootloader.

Thanks ramerco. This is exactly what I've been looking for. I am still relatively new to the G-Tab and ROMS and need more details, which you have provided. I've been looking for "detailed" steps to get to 4349 along with 1.2 boot loader since I want to try roebeet's HC.

jcflman said:
At that time this was a good way to do it. Now, you can NVFLASH 4349 in a few minutes. Then when you reboot wipe data/cache.
Click to expand...
Click to collapse
I'd like ot bump this, and request again, that this post be stickied. More and more people are having issues when flashign from 1.1 to 1.2 roms, and THIS GUIDE is the SAFEST and MOST COMPREHENSIVE guide on how to go from 1.1 to 1.2.
Yes, it may be quicker to NVFlash as much as you possibly want, but I'll bet that if you found every post about a softbricked G-Tablet, the user was trying to NVFlash something...
It seems to me at this point, that developers are NVFlashing everything nowadays..that's fine, becuase most of them know how ot recover from it. Typical USERS, though, do not, and end up making their situation worse. WE NEED TO PREVENT PROBLEMS, so using standard recoveries, or CWM over NVFlash is the safest way to do it. I have no problem learning NVFlash to recover from a softbrick, but I'll be damned if learning it and using it CAUSES a softbrick becuase I have no idea what I'm doing.
PLEASE Sticky this thread, and clean up some other stickies that are no longer needed. For instance, Jerdog's "One and only Honeycomb" thread...not necessary anymore, since the reality he predicted wouldn't happen, has.

Wi-Fi
Who knows how to set up Wi-Fi on Linux.
Shall describe the step by step please.

how do you create file
I am really new at this. So how to you do this step?
4. A folder called recovery with a file in it called COMMAND inside it with the following line of text:
Code:
--update_package=SDCARD:/update.zip
What is the step-by-step process for this? I know how to create a folder, but I dont know how to create the file with the code. Can someone help me with this. Thanks I have Windows 7 if that matters.

novicexda said:
I am really new at this. So how to you do this step?
4. A folder called recovery with a file in it called COMMAND inside it with the following line of text:
Code:
--update_package=SDCARD:/update.zip
What is the step-by-step process for this? I know how to create a folder, but I dont know how to create the file with the code. Can someone help me with this. Thanks I have Windows 7 if that matters.
Click to expand...
Click to collapse
You might have a copy of the recovery folder with command file on your pc where you unzipped the cwmod_internal.zip unless you moved it to your G Tablet instead of copying. You could always unzip the cwmod_internal.zip file again to pull the recovery folder from it. Anyway, to answer your question...
To create a file just open the recovery folder you just created then right-click > new > text document. Put the code "--update_package=SDCARD:/update.zip" without the quotes & save the document as command. It shouldn't have a file extension like command.txt just command only.

[GT-P6210][CWMRecovery][ROOT] ClockworkMod Recovery and Root (07-Jan-2012)

**** 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

[Q] Infuse zip flashing stuck at "Finding update package"

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

How to Root and upgrade from ice cream sandwich to jelly bean??

Dear all,
I received an Asus Transformer Tf101 for Christmas, 16gb internal RAM,
OS 4.0.3 (ice cream). Can someone please guide me how to enable root and upgrade the os?
I tried to rooted with Sparkyroot but, kept getting " exploit not found". Please help!
Sent from my Transformer TF101 using xda app-developers app

Check to make sure the rooting method works with your device. Have you checked out the sticky threads here about it ? I remember that I tried three different ways of rooting (all from here) before it worked - I think it was a PC driver issue and a lack of support for one.
After that, you will need to install a custom recovery in order to flash from. I really like TWRP, and was advised to download "Goomanager" from the Play Store - from there you can go to the menu dots in the upper right and choose "Install OpenRecoveryScript" and it will install it. I also like the "Reboot2Recovery" app, although it's not as useful on a custom ROM that includes the feature, but is easier than holding down buttons just right for that first time.
After that, you can flash a ROM via that custom recovery you installed (on TWRP it is very user-friendly and very obvious what you need to do as long as you know what you need to "wipe" beforehand - all you need is to use the "Install" button and thereafter).
ROM+Kernel(optional)+GAPPS(Google proprietary apps) . You need to wipe both caches, /system and internal data. You could use Titanium Backup prior to this to backup apps and of course back up data to an external source. A Kernel is sort of an underlayer of the "OS" that works on a low level with the hardware. You can read about some of the available ones in the Development section and see why people are using them, what possible benefits they get, et cetera.

arabic support
do custom roms support foreign languages and fonts, i use to visit arabic web sites and arabic tweets, do CM10, AOSP or Teom eos support such fonts
Pennycake said:
Check to make sure the rooting method works with your device. Have you checked out the sticky threads here about it ? I remember that I tried three different ways of rooting (all from here) before it worked - I think it was a PC driver issue and a lack of support for one.
After that, you will need to install a custom recovery in order to flash from. I really like TWRP, and was advised to download "Goomanager" from the Play Store - from there you can go to the menu dots in the upper right and choose "Install OpenRecoveryScript" and it will install it. I also like the "Reboot2Recovery" app, although it's not as useful on a custom ROM that includes the feature, but is easier than holding down buttons just right for that first time.
After that, you can flash a ROM via that custom recovery you installed (on TWRP it is very user-friendly and very obvious what you need to do as long as you know what you need to "wipe" beforehand - all you need is to use the "Install" button and thereafter).
ROM+Kernel(optional)+GAPPS(Google proprietary apps) . You need to wipe both caches, /system and internal data. You could use Titanium Backup prior to this to backup apps and of course back up data to an external source. A Kernel is sort of an underlayer of the "OS" that works on a low level with the hardware. You can read about some of the available ones in the Development section and see why people are using them, what possible benefits they get, et cetera.
Click to expand...
Click to collapse

You should be fine with foreign languages as the custom rom is generally built on what Android uses, so if you can do it on stock than you should be fine on custom.
I use a different recovery than the above post, but if you follow his steps then you should be fine. You don't NEED a custom kernel to run JB per say, but it does give you a bit more power if you want to get into overclocking etc. Also, I try to stress, once you have custom recovery and are ready to flash whatever rom you chose, wipe everything. My first and only real panic was a bootloop from not wiping everything.

Like somebody mentioned above, make sure your device is compatible with each tool. Look at your serial number on the bottom of the tablet next to the usb port. Should see B60blahblah or B70blahblah, or maybe something higher (if it's newer).
I use a nice tool put together by whitekidney called EasyFlasher. It's an all in one package where you can root, install custom recovery, and install new firmware. Check this thread. It works very well for me, and is super easy.
whitekidney says:
Works for:
ANY TF101:
SBK1 (B10-B70)
SBK2 (B70,B80,B90++)
Some B70 models are SBK1, some newer B70 are SBK2, if you don't know which one you have, try both!
Click to expand...
Click to collapse
It's real easy to use. Put your tablet into apx mode by holding the power button and the volume up button. The screen will look like it's off but if you plug it into your Windows computer, you should hear the sound when a device is plugged it. Then it'll try to install the drivers for an apx device, or some MTP drivers, I believe. If they fail to install, download PDAnet and install it. This will correctly install your drivers. There's also another method of getting your drivers to install correctly. Here's a universal driver package that 1wayjonny put together. To clarify, only use PDAnet or the universal driver package if your drivers didn't install correctly when you plugged your transformer (which should be in apx mode) into your computer.
Now you can use EasyFlasher to install a custom recovery. I left it on the very first option, (a touch recovery, so you don't have to use your buttons to change your selection). During this process, EasyFlasher should first open up a command prompt (it might pop up behind your current programs running so you won't see it until you minimize everything except for EasyFlasher). The cmd prompt will ask you to overwrite some files on your device, just type a for "always" and let it do it's thing. It's really running NVflash which you should also get familiar with too.
After you have a custom recovery installed, flash your ROM of choice. Here's a nice JB 4.1 that I've tried out. Download that file, put it on a micro sd card, pop it in your transformer, and reboot into recovery by holding volume down and the power button. When it reboots, press volume up to enter your new custom recovery (like it should say on the screen). If you installed the same recovery that I recommended above (hopefully these are the correct steps, as I don't have my device in front of me), click on flash .zip, then click on from sd card. You should see the zip that you transferred from your computer, click on it, and it should install.
Once that's finished, reboot your transformer, let it load the new rom, either set it up or skip all the junk in the beginning. Once you're on the main home screen, remove your micro sd card and transfer the superuser zip that you can find inside the tools folder in EasyFlasher's directory (on your computer) to your sd card. Reboot into recovery, and now flash that super user zip the same way you flashed the rom.
Now you have a brand new, 4.1.2 JB rooted device!

Quick question, do i need to connect my asus eee transformer pad tf101 to my windows xp pc to root it? Or can i used my ibook g3. The reason i ask is because i keep getting an error about MTP error. I have search everywhere for this error and i cant find a solution.
Sent from my Transformer TF101 using xda app-developers app

jbusti75 said:
Quick question, do i need to connect my asus eee transformer pad tf101 to my windows xp pc to root it? Or can i used my ibook g3. The reason i ask is because i keep getting an error about MTP error. I have search everywhere for this error and i cant find a solution.
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
I am sure it can be done, but most of the tools (like EasyFlasher) use Windoze.
Even if you are getting an MTP error, it should not matter as you will be using the APX device. Just make sure you have the APX driver and update the unknown device that appears after you boot to APX mode.

[Q] How to get OTA

Hi,
I'm a Gnex user, there is a friend that has a Nexus S, when I saw it she was using GB 2.3.6!
I said, WTF! In know 4.1.2 is official on the Nexus S.
This is the info I was able of gathering:
kernel 2.6.35.7 gb5f63ef
[email protected] #1
GRK39F
How can I update it easily? with stock rom.
Best regards.

Your friend should go to settings and check for new system updates.
Sent from my Nexus S using xda app-developers app

devil188 said:
Your friend should go to settings and check for new system updates.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
yes, she did, but it says "there is no update available"
Thanks.

You could flash the new stock rom for her. But first, try this:
You can try forcing your device to ask for a free download slot:
1. Settings > Apps > All
2. Find Google Service Framework in the list, tap on it
3. First tap Clear Data, then Force Stop
After this procedure the last checked date under Settings > About Phone > System Update should have been reset to 1970 or so. Tap the Check now button there and see if the update notification pops up now.
Click to expand...
Click to collapse
Maybe this'll work, but I can't tell you that it works for 100%.
If it fails, you should definitely download the stock rom OR custom rom (like hellybean 4.2.2 w/ devil kernel) for her and flash it, but you have to unlock & root it for her first.
Hope I can help you out

Same issue!
Hello!
I too have the same problem. I recently got as a gift a I9020A, and before starting to use it as my main mobile I wanted to update it to a newer version of Android. It's current version is 2.3.6 Gingerbread and when I try to check for updates none will appear, I have also tried to clear data and force stop on Google Service Frameworks and then trying to update but once more it was useless. I've contacted Samsung Mobile's Help, they informed me that 2.3.6was the latest Android for I9020A, however I have seen that there are OTAs of the 4.1.2 released for my device.
This is my first android, I wouldn't know the benefits of updating the OS but I assume they are many, I have an iPad and I jailbroke it without updating the iOS and now if I update the iOS I'll lose the jailbreak and consequently all of the cracked apps, but I can't install apps that require a more current version of iOS, so I'm taking that experience to Android, don't ever want that to happen again.
I have already non-destructive rooted my device following this thread, but I don't know any much further than this, or even if the rooting I needed was the destructive one in order to apply the OTA. I saw this thread with the links for the OTA 4.1.1 but am not sure of the differences between IMM76M and IMM76D, so I don't know which to download..
I'll be glad to provide any other information needed. If anyone could help OP and me I'll be very grateful, give you a thank you and set the good word of you on the streets. "Street Rep +1" lol

Download the "sojua" one at this thread: http://forum.xda-developers.com/showthread.php?t=1932832
Then flash it (If you don't know how it works, just take a look at some tutorials!).

So I should install the sojua and not the OTA, right? The OTA would be only from the ics to jb?
And I don't know how to flash, by what I've read I have to use Clockworkmod Recovery? if so I think I can find tutorials easily, if not then please pinpoint me the right way, there is far too much information out there, I feel overwhelmed..

Anyone?

"sojua" from the thread IS the OTA version!
Also, I think you need this too: https://dl.dropbox.com/u/41124284/gapps-jb-20121223-signed.zip (Google Apps, for installing all the G-Apps)
To flash your device with CWM, you have to:
1. Install "ROM Manager" (@ Play Store, search for it)
1.1 Enter USB-Storage mode and copy the .zip file into your sdcard.
2. Open ROM Manager and install Clockwork Recovery (Simple)
3. Turn off your device after the installation has been finished.
4. HOLD Volume Up and the Power Button to enter Recovery Mode.
5. Select "RECOVERY" by using the volume button and press the Power Button to confirm.
6. After CWM has come up, select "backup and restore" first and backup your system. This may take a while.
7. Make a factory reset (at the main menu) // EVERYTHING will be wiped!
8. Go to "advance" and "wipe dalvik cache"
9. Main Menu > "install zip from sdcard" > select the zip you copied into the sdcard. (Select the OTA!)
10. Wait until finish
11. Repeat 9. , but now select the gapps zip.
12. Wait until finish
13. Main Menu > Reboot to system
You're done! If something bad happens, you can always restore by going into recovery mode and select "restore" in the "backup and restore" menu.

Thanks a lot, devil188, but unfortunately it still hasn't worked..
I get up to step 9-10 and then it will abort the update I don't know why. I've tried unzipping the Sojua tgz file, leaving only the tgz file, unzipping the tgz and zipping it into a .zip.. but it will always abort
Not sure how to proceed now

I will look for the file you need for flashing. Be patient actually, you could try to flash a custom rom, maybe you like those ones more
Sent from my Nexus S using xda app-developers app

Any news?

Try searching the stock rom in the forums or flash a custom rom (<better ), it's fast to find
Can't do it for you now because I'm not at home right now
Also, if you decide to flash a custom rom, then follow my little tutorial
Sent from my Nexus S using xda app-developers app

I can't post a link I have to a DroidViews tutorial, since I have less than 10 posts, but by what I understood it would replace the factory image from mine 2.3.6 to a 4.1.2. Is there any problem with that?
Moreover, what Custom Rom would you recommend?

I've managed to finally be able to upgrade my Nexus S to 4.1.2 following the DroidViews tutorial. Now I'm having battery issues lol.
Thank you very much for trying to help me