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.
Related
Hey there hope this is the right place for this ... Just want to report something that has happened. I am currently unable to use the G tablet stock vanilla TnT... any clue as to why this would happen? I dont really use it anyway however should this be resolved? and would it affect the tablet in the long run if not addressed? I use Launcher pro and the tablet forces itself to that when "home" force closes. I would like to try the TnT lite however am not confident about it.
Do i need to root the device before i hold the power button and vol +? to flash the new rom ( it bugs me that this is all i have to do to put in a custom rom. it seems to easy, unless it is that easy)
Will i lose all the files, PDF's, and documents that i have on it once i flash the new rom ?
As you can see im a noob to Android. Thanks for advice and guidance in advanced and patients.
Follow the instructions in the alternate gtab firmware post. It worked great for me. I would suggest installing cwm so you can back up your existing firmware.
My update would force close during download on the stock firmware. I finally got it to work by minimizing the pop up that displayed the progress. For some reason the screen would crash the download.
Your files should be there but you will lose all user settings and installed apps when you do the factory reset.
This is a common issue with stock, and TnT Lite. The user data seems to be very unstable once you upgrade to different firmware.
The "easiest" thing to do is just wipe the user data. However, if there is certain data you need to keep, I would recommend the excellent Titanium Backup. The only caveat is that the device has to be rooted, to use it.
roebeet said:
The only caveat is that the device has to be rooted, to use it.
Click to expand...
Click to collapse
And Z4root does this easily. Just install and click "root".
RyuFDAC01 said:
Hey there hope this is the right place for this ... Just want to report something that has happened. I am currently unable to use the G tablet stock vanilla TnT... any clue as to why this would happen? I dont really use it anyway however should this be resolved? and would it affect the tablet in the long run if not addressed? I use Launcher pro and the tablet forces itself to that when "home" force closes. I would like to try the TnT lite however am not confident about it.
Do i need to root the device before i hold the power button and vol +? to flash the new rom ( it bugs me that this is all i have to do to put in a custom rom. it seems to easy, unless it is that easy)
Will i lose all the files, PDF's, and documents that i have on it once i flash the new rom ?
As you can see im a noob to Android. Thanks for advice and guidance in advanced and patients.
Click to expand...
Click to collapse
Tntlite is that easy I was surprised. Too since rooting my HTC hero a year and a half ago was so much more hands on
Hey guys.... first off thanks for the advice it worked great it was easy to do... flashed TnT lite and was excited.... i attempted to pull an app from freewareloversDOTcom and was stuck in downloading status for some time even with a good wifi signal... This is where all hell broke loose ....the file i wanted never downloaded.... then the pic gallery forced closed then the launcher forced closed and had to shut down now now its in bootloop....I attempted to power and vol + but nothing happened in fact got a triangle !.... what is needed now.....
LOL at the entire situation this was my fear..... please if someone with extreme patients can list or point to a noob friendly thread on what i need to do
i have a microSD card can that be used read somewhere that i may need that.....
I thank you guys VERY VERY MUCH appreciate this
Hey guys.... first off thanks for the advice it worked great it was easy to do... flashed TnT lite and was excited.... i attempted to pull an app from freewareloversDOTcom and was stuck in downloading status for some time even with a good wifi signal... This is where all hell broke loose ....the file i wanted never downloaded.... then the pic gallery forced closed then the launcher forced closed and had to shut down now now its in bootloop....I attempted to power and vol + but nothing happened in fact got a triangle !.... what is needed now.....
LOL at the entire situation this was my fear..... please if someone with extreme patients can list or point to a noob friendly thread on what i need to do
i have a microSD card can that be used read somewhere that i may need that.....
Click to expand...
Click to collapse
I had a similar problem twice today (installed TnT Lite 2.02 and ran into boot loops). Here's how I recovered. Results may vary, so use at your own risk:
1. Download the vanilla restore from http://forum.tegratab.com/viewtopic.php?f=6&t=16 (this is just to get the recovery\console file unless you want to manually create it).
2. Download the updated stock TnT from http://forum.xda-developers.com/showpost.php?p=9362168&postcount=35
3. Extract the "recovery" folder from gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1.
4. In the recovery folder there is a file called "command" with no extension. Open this file with a text editor (eg. notepad) and edit the line so "SDCARD" says "SDCARD2" instead. Save it and ensure you do not add any extension. It should look like this:
--update_package=SDCARD2:/update.zip
5. Rename the "update-smb_a1002-2967-user.zip" from step 2 to "update.zip".
6. Copy the entire recovery folder with the edited "command" file from step 4 and the "update.zip" from step 5 to the root of your MicroSD card. It's important that the contents on the root of your MicroSD ends up with:
/update.zip
/recovery/command
7. Put the MicroSD in your gTablet.
8. Power on while holding the Volume Up button until you see a message regarding recovery.
9. You should see a graphic showing package box with a progress bar after a short time.
10. Wait until it completes and the unit will restart.
11. If all goes well, you should be back to stock TnT with the last OTA update.
If you are wondering why I just didn't use the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, it's because it didn't help me. I initially used the same general method above with the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, but my gTablet still continued to boot loop. After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Hope this helps. Good luck.
dcom222 said:
I had a similar problem twice today (installed TnT Lite 2.02 and ran into boot loops). Here's how I recovered. Results may vary, so use at your own risk:
1. Download the vanilla restore from http://forum.tegratab.com/viewtopic.php?f=6&t=16 (this is just to get the recover\console file unless you want to manually create it).
2. Download the updated stock TnT from http://forum.xda-developers.com/showpost.php?p=9362168&postcount=35
3. Extract the "recovery" folder from gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1.
4. In the recovery folder there is a file called "command" with no extension. Open this file with a text editor (eg. notepad) and edit the line so "SDCARD" says "SDCARD2" instead. Save it and ensure you do not add any extension. It should look like this:
--update_package=SDCARD2:/update.zip
5. Rename the "update-smb_a1002-2967-user.zip" from step 2 to "update.zip".
6. Copy the entire recovery folder with the edited "command" file from step 4 and the "update.zip" from step 5 to the root of your MicroSD card. It's important that the contents on the root of your MicroSD ends up with:
/update.zip
/recover/command
7. Put the MicroSD in your gTablet.
8. Power on while holding the Volume Up button until you see a message regarding recovery.
9. You should see a graphic showing package box with a progress bar after a short time.
10. Wait until it completes and the unit will restart.
11. If all goes well, you should be back to stock TnT with the last OTA update.
If you are wondering why I just didn't use the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, it's because it didn't help me. I initially used the same general method above with the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, but my gTablet still continued to boot loop. After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Hope this helps. Good luck.
Click to expand...
Click to collapse
Dude thank you so much for your effort in this !!!!! gonna try this as soon as i put my baby to sleep.... will let you know if this worked for me
dcom222 said:
I had a similar problem twice today (installed TnT Lite 2.02 and ran into boot loops). Here's how I recovered. Results may vary, so use at your own risk:
1. Download the vanilla restore from http://forum.tegratab.com/viewtopic.php?f=6&t=16 (this is just to get the recover\console file unless you want to manually create it).
2. Download the updated stock TnT from http://forum.xda-developers.com/showpost.php?p=9362168&postcount=35
3. Extract the "recovery" folder from gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1.
4. In the recovery folder there is a file called "command" with no extension. Open this file with a text editor (eg. notepad) and edit the line so "SDCARD" says "SDCARD2" instead. Save it and ensure you do not add any extension. It should look like this:
--update_package=SDCARD2:/update.zip
5. Rename the "update-smb_a1002-2967-user.zip" from step 2 to "update.zip".
6. Copy the entire recovery folder with the edited "command" file from step 4 and the "update.zip" from step 5 to the root of your MicroSD card. It's important that the contents on the root of your MicroSD ends up with:
/update.zip
/recover/command
7. Put the MicroSD in your gTablet.
8. Power on while holding the Volume Up button until you see a message regarding recovery.
9. You should see a graphic showing package box with a progress bar after a short time.
10. Wait until it completes and the unit will restart.
11. If all goes well, you should be back to stock TnT with the last OTA update.
If you are wondering why I just didn't use the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, it's because it didn't help me. I initially used the same general method above with the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, but my gTablet still continued to boot loop. After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Hope this helps. Good luck.
Click to expand...
Click to collapse
You mind if I steal these directions? It's more detailed than the one I wrote up on my TnT Lite post. I'd like to post it there (specifically the command file, as some people have issues understanding the "SDCARD2" change).
And thanks for posting your experiences to help the other users here!
roebeet said:
You mind if I steal these directions? It's more detailed than the one I wrote up on my TnT Lite post. I'd like to post it there (specifically the command file, as some people have issues understanding the "SDCARD2" change).
And thanks for posting your experiences to help the other users here!
Click to expand...
Click to collapse
Please do if they look to be correct. Hopefully we'll see confirmation that these instructions work.
I appreciate all your work on the gTablet!
dcom222 said:
Please do if they look to be correct. Hopefully we'll see confirmation that these instructions work.
I appreciate all your work on the gTablet!
Click to expand...
Click to collapse
Same here Roebeet thanks for your work...dcomm222 thanks again... So I tried to only install the TnTlite 2.0 from the microsd card, it read it, looked to have loaded it, and it went right into the bootloop again.... I really want TnT lite ......
so now i am going to try your method... fingers crossed
RyuFDAC01 said:
Same here Roebeet thanks for your work...dcomm222 thanks again... So I tried to only install the TnTlite 2.0 from the microsd card, it read it, looked to have loaded it, and it went right into the bootloop again.... I really want TnT lite ......
so now i am going to try your method... fingers crossed
Click to expand...
Click to collapse
I had no luck trying to re-flash to 2.0X once I got in the boot loop - I couldn't get past it no matter what until I went back to stock. Once I was back at stock I could re-flash to 2.0X from the internal SD. I'm still trying to figure out what's getting me in the boot loop - everything seems to work great for a while.
Good luck!
dcom222 said:
I had no luck trying to re-flash to 2.0X once I got in the boot loop - I couldn't get past it no matter what until I went back to stock. Once I was back at stock I could re-flash to 2.0X from the internal SD. I'm still trying to figure out what's getting me in the boot loop - everything seems to work great for a while.
Good luck!
Click to expand...
Click to collapse
GOT IT BACK!!!! geez man I was full on panic mode
have you flashed back to TnT lite back yet and how long does it last? Damn i am so tempted to go back im thinking it has something to do with what we attempted to load on the tablet ... i dont know just looking for a reason to Flash ....can this constant recovery flash do any damage to the tablet? I would like to try other Roms but dont want to mess my tablet up..
BTW i got this EUL when it rebooted especially sections 4.1 and 4.2 wtf!!! sorry about that but that is how i felt
Thanks again guys!!!!
RyuFDAC01 said:
GOT IT BACK!!!! geez man I was full on panic mode
have you flashed back to TnT lite back yet and how long does it last? Damn i am so tempted to go back im thinking it has something to do with what we attempted to load on the tablet ... i dont know just looking for a reason to Flash ....can this constant recovery flash do any damage to the tablet? I would like to try other Roms but dont want to mess my tablet up..
BTW i got this EUL when it rebooted especially sections 4.1 and 4.2 wtf!!! sorry about that but that is how i felt
Thanks again guys!!!!
Click to expand...
Click to collapse
If I remember correctly, the stock firmware with the OTA update will prompt you to accept a license and prompt to set the time, etc....
I just flashed the TnT 2.02 again. So far it seems OK, however it did the first 2 times I did it as well. I followed all of the instructions at "forum.androidcentral.com/showthread.php?p=442691#post442691" except I substituted using roeboot's TnT. Once I did it I had everything working (flash, market, etc...). Both times the boot loop happened when I tried to install or uninstall something, and both times were after a few hours of use. I tried a third time and almost instantly got into a boot loop, but I think I got ahead of myself in that try and did some things out of order. The good thing is that I was able to recover each time.
Out of curiosity, did your tablet come with a gray or green cloth to clean the screen? The reason I ask is that I thought I had seen somewhere that this might be an indication of a difference in gTablets.
The EULA shows up with a new stock firmware - and yeah 4.1 / 4.2 kinda bugged me too. I never selected "I Agree" - fark that.
As for the boot loops, it seems that we still can't pin it down - maybe it's just random, I don't know.
Hi,
I was stuck after bootlooping using Cyanmod, then flashing NVflash still didnt fix the issue, this fix did it for me. Thanks for getting me back up & running. I will give another shot at using cyanmod now that I have all the files needed to get me back.
BTW< I have a green cloth. What does that mean?
Thanks,
Rich
dcom222 said:
If I remember correctly, the stock firmware with the OTA update will prompt you to accept a license and prompt to set the time, etc....
Out of curiosity, did your tablet come with a gray or green cloth to clean the screen? The reason I ask is that I thought I had seen somewhere that this might be an indication of a difference in gTablets.
Click to expand...
Click to collapse
My tab came with a grey cloth... funny thing though I got mine on the second wave of shipments to sears... I NEVER had any issues with the time i just set it and it kept the time... I remembered that when these first came out that was a problem... i thought mine was diff because i never had any issues with time reseting itself... anyway Thanks again dude for your help hope i could play this forward to someone more noobier than me
Roebeet looking forward to your TnT lites...
dcom222 said:
After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Click to expand...
Click to collapse
I now have clockwork recovery installed... How do i copy the update.zip from external microsd to internal microsd... mounting sd-ext gives an error..
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
Error mounting SDEXT:!
Frustration levels are high with this device!!
Thanks!
a "me too" reboot problem
I was able to install TNT Lite 2.0, then 2.11. I got Clockwork Recovery installed as well.
The market would start, but if I did a search for obvious things like "Kindle", the market would give an error that it didn't exist in the market. Thinking it was the error situation described here:
http://forum.xda-developers.com/showthread.php?t=845175
I applied those instructions, and rebooted.
Upon reboot, it ended up in a continual reboot loop.
Trying to do the start with volume+power, it brings up Clockwork Recovery, and when told to wipe data/factory reset, it stays in the reboot loop. When told to apply sdcard's update.zip, it looks only at the one on the internal sdcard, which is for CWR, and goes back into the loop.
At that point I setup a microSD with the information from this post:
http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7
including changing the line from sdcard to sdcard2. Again it doesn't recognize that the internal sdcard2 is plugged in, and attempts to mount it with CWR (mount /sd-ext) yields the error:
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
Error mounting SDEXT:!
So, unfortunately I'm at an impasse, like the previous poster. I just bought the tablet a couple of days ago, so I'm far from expert at tweaking it into working.
Any suggestions on what to do, are greatly appreciated.
PS - Bought the gtablet from Office Depot, and received a green cloth.
Boot into clockwork recovery and go to advanced and format SD, use the 2gb and 512mb I believe, then flash TNT or another rom. That fixed my boot loop.
First let me introduce myself, my name is Sean Cullinan and I posted a very detailed set of instructions on my blog blendblog.net on how to take a stock GTablet and get it going with a custom ROM. I used Vegan for my instructions.
After the woot deal blew up a ton of traffic came to my site and there was some concern over using my instructions versus the ones here and also with the sources of the binaries I posted. I posted the binaries because I wanted to rename them with "number coding" to make them easier so that new users wouldn't install them in the wrong order.
Anyway, after talking with Roebeet and a few others I thought it would be good to post the instructions here as well. I wasn't trying to steal any of XDA Devs thunder, everything I learned I did through this site.
So here is the original blog post in it's entirety.. Note that I still pointed the links back to my server, you can find the same files linked from the devs at XDA if you don't "trust" me. Also, if you want to use TNT Lite 4.40 I posted a second tutorial to my blog, I kept it separate to keep things simple.
Please feel free to checkout my site as well if you find this useful,...and if enough people find this useful maybe this is "Sticky worthy?"
Verifying Installed ROM Version
The first thing you have to do is verify that you're GTablet is on ROM 3358 or lower before doing this procedure. If you have a newer ROM version on your device you cannot do this procedure at this time!
1) On the GTablet go to Settings->About Device
2) If the version is anything higher than 3588 STOP NOW! According to this thread it is easy to "softbrick" your device if you proceed. So again, STOP NOW! I hope to have instructions on how to get around this posted in the future.
Introduction
We bought a GTablet for work and our software partners also bought one to test the development we were doing on it. As such I had to write up instructions on how to flash the GTablet with the VEGAn ROM and a custom Kernel. I was told the instructions were very good so i decided to post them here. Disclaimer: First, flashing your tablet means you will lose any applications that you have installed previously or that came with the stock ROM. You will have to reinstall them. If you search around on XDA you will find other separate instructions on how to take backups if this is important. Second, please note that the developers at XDA Developers are not responsible for these instructions!! I put them together myself to help a vendor partner of ours whom I am developing software with. Many people have informed me that these instructions work great but as always with these things, you are doing something that is highly technical and something can go wrong...at which point you will have to figure out how to recover!
Installing Clockwork Mod Recovery
The first thing you have to do is install Clockwork Mod Recovery. The GTablet goes into “recovery” mode whenever you power up by holding the volume up key along with the power key. Clockwork Mod Recovery gives us a low level UI with which to work which the default “Recovery” mode does not do. To install Clockwork Mod Recovery do the following:
1) Attach the GTablet to your PC so you see it as a drive
2) Download and unzip the 1-cwmod_internal.zip file from the website on your PC.
3) Place the recovery folder and the update.zip file on the root of the disk drive that represents the GTablet on your PC from step 1. If there was already a recovery folder and update.zip you can delete them and replace them with this one.
4) Safely remove the GTablet
5) Power down the GTablet (hold power button and use the Power off option).
6) Hold the volume + key down while holding the power button. Release when you see “Detecting recovery key pressed” on the screen.
7) It will now install clockworkmod and the device will boot again.
Repartitioning GTablet storage
For some reason Viewsonic used an odd partition set when they shipped the GTablet. While repartitioning the storage wasn’t totally necessary it has been recommended on the forums so I did it. Here’s how:
1) Power down the GTablet
2) Boot into Clockwork Mod recovery by holding the Volume + key down while holding the power button. Release when you see “Detecting recovery key pressed” on the screen.
3) You will be presented with a menu, this is Clockwork Mod Recovery. To navigate the menu use the volume up and down keys. To select a menu option use the home key. To go back press the back key.
4) Navigate to Advanced->Partition SD Card (FYI, SD Card refers to internal storage, not the MicroSD card).
5) Choose 2048M for EXT size on the first screen
6) Choose 0M on the second screen.
7) You have now repartitioned the GTablet
Copying the ROM and Kernel files to the GTablet
Now that everything is formatted we have to copy the ROM files to the GTablet that we are going to use.
1) Navigate back to the root menu of Clockwork Mod by using the back key or by powering off and powering on with the Volume + key held down as above
2) Plug the GTablet into your PC
3) Choose mounts and storage->Mount USB storage. The Gtablet should now show up as a drive on your PC.
4) Create a directory on the drive called ROM’s.
5) Download and copy 2-gtab.VEGAn.1.00.beta5.1.user.final.zip from the website to the ROM’s directory. Note that this file is 88mb (rather large). DO NOT UNZIP, just copy
6) Download and copy 3-gtab.VEGAn.1.00.beta5.11.suppl.zip from the website to the ROM’s directory. DO NOT UNZIP, just copy
7) Download and copy 4-boot-cm_2632.32-xtra-vfpv3_fp-030711.zip from the website to the ROM’s directory. DO NOT UNZIP, just copy
8) You can now “safely remove hardware” from windows and select “Unmount” in Clockwork Mod. You can unplug the GTablet from your PC.
Installing the Vegan 5.1 ROM
Now we are ready to actually start installing stuff!
1) Navigate back to the root menu of Clockwork Mod by using the back key or by powering off and powering on with the Volume + key held down as above
2) Choose install zip from SD Card->choose zip file from sdcard
3) Navigate into the ROM’s directory and select 2-gtab.VEGAn.1.00.beta5.1.user.final.zip
4) When prompted choose “Yes- Install 2-gtab.VEGAn.1.00.beta5.1.user.final.zip”
5) Let the installer do its thing.
6) When installer completes go back to the root menu in clockwork mod.
7) Choose “wipe data/factory reset.” When prompted confirm that you want to wipe.
8) Choose “wipe cache partition”
9) Navigate to Advanced and choose “wipe davlik cache”
10) Navigate back to the root menu and choose reboot system now. The device should boot into Vegan 5.1. Let this happen.
Installing the Vegan 5.1 ROM supplement
There was a small update to Vegan 5.1 that was posted as a supplement that is installed exactly the same way that Vegan 5.1 was installed:
1) Power down the GTablet
2) Boot into Clockwork Mod recovery by holding the Volume + key down while holding the power button. Release when you see “Detecting recovery key pressed” on the screen.
3) Choose install zip from SD Card->choose zip file from sdcard
4) Navigate into the ROM’s directory and select 3-gtab.VEGAn.1.00.beta5.11.suppl.zip
5) When prompted choose “Yes- Install 3-gtab.VEGAn.1.00.beta5.11.suppl.zip”
6) Let the installer do its thing.
7) When installer completes go back to the root menu in clockwork mod.
8) Choose “wipe data/factory reset.” When prompted confirm that you want to wipe.
9) Choose “wipe cache partition”
10) Navigate to Advanced and choose “wipe davlik cache”
11) Navigate back to the root menu and choose reboot system now. The device should boot into Vegan 5.1 with the supplement. Let this happen.
Installing Pershoot’s kernel
Pershoot is a fantastic Android dev who has written superior Kernel's for several devices including the GTablet. You can check his site for the latest builds. This kernel fixes several more bugs in the default Kernal that comes with Vegan 5.1. It is installed the same way that you install the Vegan ROM/Supplement:
1) Power down the GTablet
2) Boot into Clockwork Mod recovery by holding the Volume + key down while holding the power button. Release when you see “Detecting recovery key pressed” on the screen.
3) Choose install zip from SD Card->choose zip file from sdcard
4) Navigate into the ROM’s directory and select 4-boot-cm_2632.32-xtra-vfpv3_fp-030711.zip
5) When prompted choose “Yes- Install 4-boot-cm_2632.32-xtra-vfpv3_fp-030711.zip”
6) Let the installer do its thing.
7) When installer completes go back to the root menu in clockwork mod.
8) Choose “wipe data/factory reset.” When prompted confirm that you want to wipe.
9) Choose “wipe cache partition”
10) Navigate to Advanced and choose “wipe davlik cache”
11) Navigate back to the root menu and choose reboot system now. The device should boot into Vegan 5.1 with the supplement and this kernel. Let this happen.
Last Steps
You now have Vegan 5.1 installed on your GTablet! What is left to do? The launcher that comes with Vegan is kind of weak, it doesn’t rotate to portrait so I chose to install Launcher Pro which is much nicer. You can get this in the Android Market which is built into this ROM. Launch the Android Market and you can either use an existing or create a new Google ID. Do a search for Launcher Pro. If you don’t see it you may need to “fix” the Android Market which is common when doing a ROM upgrade. Here is the procedure to fix it.
1) Navigate to the Android settings->Applications->Manage Applications
2) Choose the all tab
3) Select “Market” from the list
4) Press “Clear Cache”
5) Press “Force Stop”
6) Press the back button to navigate back to the list of applications
7) Select “Google Services Framework”
8) Press “Clear Data”
9) Press “Force Stop”
10) Exit the settings. Try to launch the market
11) You should receive an error, this is expected.
12) Power down the GTablet (I’ve been told not to use the reboot option instead powering down and using the power button to bring it back up).
13) Power on the GTablet
14) Once everything is loaded go back to the Market. If you get an error wait a minute.
15) Search for Launcher Pro and hopefully it is found. If not repeat this fix process again (I’ve had to do it twice sometimes).
Once you have Launcher Pro installed you can make it the default using the “Home Switcher” application. You can customize Launcher Pro quite a bit, it’s a nice launcher app.
Note You can safely delete the ROM’s directory after doing this if you desire to do so, although its sometimes handy to have it on there if you want to re-flash for some reason.
You should now have a pretty rock solid GTablet that gives you a very good, stock like Android experience.
Awsome Tutorial!,, Truly Awesome! Thank you for taking the time to write this. My Tab is currently OUT FOR DELIVERY. I can't wait to get it and try this! Thanks again.
I noticed on your website that you felt that the Archos 101 is a better device than the gTab. With the recent updates in ROMS and kernels do you still think the Archos device is superior?
What did you use for rooting? That is the one thing I see missing in your post.
Thanks for the comments and compliments!
I didn't use the term "rooting" but this is what you are doing when you install CWM and then flash your own ROM. So following my instructions "roots" the devices.
Here's a link to my article pr0cs is referring too. I wouldn't necessarily say that I thought the Archos was better, just different. My comparison was made with Vegan 5.1 so the review is still relevant. Now when/if Honeycomb gets running on the GTablet (which is far more likely than the Archos) it may change the equation a bit!
Sean
I've read other articles that specify rooting the device first then installing CWM, and I've seen articles like yours that don't mention getting root access, so thanks for that clarification.
And wonderful step-by-step guide.
Nice write up. I'll have to search the forum for information about this ROM.
Sent from Captivate, Cognition 4.1.1
Thanks for the step-by-step!
Just got my gtab last night.
Followed your instructions to the letter. Everything worked perfectly, thanks for your easy to use guide.
And thanks to all the Devs that made it possible. This tablet screams with a different ROM on it! My iPad toting friends are already jelly...
I just followed these instructions today from Sean's site, in order to upgrade my VEGAn 5.1.1 kernel to Clemsyn's v7 kernel.
It took me a bit to find Sean's blog location, so I am glad to see this here. I would encourage anyone who wants to mod their ROM and kernel revs to use this as a baseline.
I nominate this thread for a sticky.
Thanks OP! I just got my gtab today... someone mentioned in another forum that you should get nvflash in case you mess something up... is clockworkmod acting as a replacement for nvlflash here?
I know this is a stupid question but is it required to root the device before following any if these steps
Sent from my X10i using XDA Premium App
MFister said:
Thanks OP! I just got my gtab today... someone mentioned in another forum that you should get nvflash in case you mess something up... is clockworkmod acting as a replacement for nvlflash here?
Click to expand...
Click to collapse
ClockworkMod is another tool but not a replacement for nvflash. It would be wise to be comfortable with both.
sweetfish said:
I know this is a stupid question but is it required to root the device before following any if these steps
Sent from my X10i using XDA Premium App
Click to expand...
Click to collapse
Rooting isn't necessary at all whether you're modding or not. Most of the custom ROMs are pre-rooted for your convenience.
Great instructions. Been looking for an organized and easy-to-use guide for Vegan 5.1.x
Just got my G-Tab and waiting for it to finish charging.
Worked slick as a whistle. No problems whatsoever. I now have a REAL Android tablet. Thank you for putting together a very clear and thorough tutorial.
With a handle like "stiphy" and a post count of 69, you need to stop right there and enjoy life for a while!
nunjabusiness said:
With a handle like "stiphy" and a post count of 69, you need to stop right there and enjoy life for a while!
Click to expand...
Click to collapse
LOL...awesome post, oops, just screwed it up!
Glad the instructions are helpful!
Sean
Followed instructions and now my tablet is flying like a butterfly, thanks very much!
But I got a quick question,
Is it normal for my device to say:
Baseband version: Unknown
Also, every time I try to open 'status' in 'about device', I get a:
Sorry! The application Settings (process com.android.settings) has stopped unexpectedly. Please try again.
Is this normal as well?
You made this noobs day!!!
bro i have read and watched countless hours on how to do this...and it wasn't until i found this thread with my 100th google search during the past 2 wks that i felt confident enough to do this.
because of this thread, it was MAD easy!! again, mucho gracias.
on a side note...cant find launcher pro (or adw.launcher) in google markets. any idea why? suggestions?
studjethro said:
bro i have read and watched countless hours on how to do this...and it wasn't until i found this thread with my 100th google search during the past 2 wks that i felt confident enough to do this.
because of this thread, it was MAD easy!! again, mucho gracias.
on a side note...cant find launcher pro (or adw.launcher) in google markets. any idea why? suggestions?
Click to expand...
Click to collapse
Studjethro, try the market fix
+1 OP, great guide!
First of all, thank you so much for the concise and clear guide! I followed this exactly. The market fix needed titanium backup though.
Couple of issues:
1. The status check gives out error, does not work, and baseband is unknown - same as post #17
2. Calling using phone gives core dump :-( - I am assuming it should use google voice, but does not seem to work
Any ideas about these ? I have just started exploring. Will post if I find more issues.
Thanks again!
My apologies if this post is a dup, but I'm havin a hell of a time trying to find the proper steps to root the WiFi only XOOM i have hangin out next to me.
I am seeing a ton of posts about rooting the XOOM, with a good bit of them telling me different informationDated 27 April 2011)
http://forum.xda-developers.com/showthread.php?t=1010568&highlight=rooting+wifi&page=17 tells me to download the WiFi only image (Tiamat 1.3...), but then later tells me to download the Tiamat 1.4 images. [scribbi, my apologies for using your post as the example. But your post got me second guessing myself a little bit...(mostly cus I'm paranoid)]
I'm sure I am just second guessing myself over nothing, but just to be sure...
Is there a GOLDEN set of steps (or sticky), as of 27 APRIL 2011, that can give us (concerned rooters) the proper steps for rooting the WiFi only XOOM such that we can follow without minimal concern for the well-being of our tabs?
(I'm an embedded SW engineer, so I understand the repercussions of what I'm doing, which is why I'm to double checking the procedures before I attempt something that may brick my hardware)
Thanks for your time and mad props to everyone that was part of the effort to root this device. I wish I could code as well that they can.
I still do it the old fashioned way. I'm already unlocked so I just flash the boot image. With a clean system partition, you need to push a few drivers (.ko files) on plus "su" and the Superuser.apk. Superuser and su work together. And finally you need to create a new folder so that your real sdcard can be mounted. I think they changed the name from "sdcard2" to something new in 1.4.0.
Not exactly step by step but you can see which instructions that mirrors most.
New instructions involve CWM which I have not installed yet. I like to know what's done step by step as I have a Canadian system.img. I don't want that flashed over.
you could use the "one click" method found in the dev section. its really like a one click at a time, but goes slow so you can read and see what's going on. if your not comfy with adb I would suggest this method. then update the kernel with the kernel manager app.
jase33 said:
you could use the "one click" method found in the dev section. its really like a one click at a time, but goes slow so you can read and see what's going on. if your not comfy with adb I would suggest this method. then update the kernel with the kernel manager app.
Click to expand...
Click to collapse
I don't trust the "one click" methods. Me, I need to know how every part works together and what every step does. I'm more comfortable with using adb and fastboot manually than I am with someone's idea of user friendly. I'm also the kind of guy that would fix his own car rather than have a mechanic fix it for free.
I should take a look at it. The way you describe it, it almost sounds like a batch file.
Also, when I understand what's going on, I can apply the steps in different situations. For example, most of the instructions here are for a PC but I can do exactly the same things with my Mac Mini when my PC isn't convenient.
OK, let me propose one of the root method which is not required to flash any boot image but is required to flash ClockworkMod Recovery and to use the recovery for rooting.
Such method (i.e. using custom recovery) may work not only on WiFi US model (which I have), but also on other models (Verizon, WiFi Europe etc). But I tested it on WiFi US.
So the step by step are:
1. Install ClockworkMod Recovery v3.0.2.5 as described here:
http://forum.xda-developers.com/showthread.php?t=1038870
This actualy means that you need to unclock bootloader and flash ClockworkMod Recovery.
2. Download attached Root_Xoom.zip file and put it on SD card
3. Insert SD card into Xoom
4. Boot Xoom in the recovery mode
5. In ClockworkMod Recovery menu choose "install zip from sdcard" and "choose zip from sdcard" and install Root_Xoom.zip
6. Reboot Xoom
Hope you will have Root after that.
ok so since I'm not currently rooted it looks like this should work for me. Gonna give it a shot in a little white once I get me some courage juice...
Al936 said:
OK, let me propose one of the root method which is not required to flash any boot image but is required to flash ClockworkMod Recovery and to use the recovery for rooting.
Such method (i.e. using custom recovery) may work not only on WiFi US model (which I have), but also on other models (Verizon, WiFi Europe etc). But I tested it on WiFi US.
So the step by step are:
1. Install ClockworkMod Recovery v3.0.2.5 as described here:
http://forum.xda-developers.com/showthread.php?t=1038870
This actualy means that you need to unclock bootloader and flash ClockworkMod Recovery.
2. Download attached Root_Xoom.zip file and put it on SD card
3. Insert SD card into Xoom
4. Boot Xoom in the recovery mode
5. In ClockworkMod Recovery menu choose "install zip from sdcard" and "choose zip from sdcard" and install Root_Xoom.zip
6. Reboot Xoom
Hope you will have Root after that.
Click to expand...
Click to collapse
Other than rooting what else does this particular file do? Ovrclock, usb hosting, sd access??
Thanks
fabian29906 said:
Other than rooting what else does this particular file do? Ovrclock, usb hosting, sd access??
Click to expand...
Click to collapse
This is for rooting only (as OP requested). It is just to push su binary and superuser.apk into system partition. Nothing else.
after that, get kernel manager and install 1.3.2 for oc, sdcard etc.... 1.4.0 isn't stable is it?
Yes, if you need oc, sdcard etc..., you can flash the kernel you like. It can be done after or before kernel flashing.
Do you have to have an SD card to CWM/root your Xoom?
Yes, you need SD card. CWM installs file from SD card to make root
Updated 14-Dec-2011: I'm posting an updated recovery, "20111213" (I compiled it yesterday) below. I'm not going to bother cleaning up this entire post with updated information, as I'm just too tired right now. Please read the post, then read the "Changes" section towards the bottom... then download the update (if you want.) Probably this weekend some time, I'm going to be consolidating the posts for all 3 models of this device into a single post with three download links. (I'm trying to get them all in sync with each other.)
**** 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 T869 (tmobile galaxy tab 7 plus) tablet.
WHAT THIS DOES:
Installed from recovery, this .zip will first ensure that it's running on the Samsung/TMobile SGH-T869. If you have a different model, don't waste your time downloading it. It won't work. I do NOT have this tablet to test with, and a special thanks to shadejinx for doing the testing. That being said, he tells me that the backup and restore both work okay. However, there is an issue with rebooting back into recovery (see Post Installation notes and Issues.) If you want to try this, 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.
So, once it knows that it's working on the proper type of tablet, this package will make a backup copy of your existing recovery image, and place it in your internal storage with the name starting with "recovery_backup" and ending with the version of the recovery package you installed. For example, recovery_backup_20111206.img.
Next, a new version of the clockwork mod recovery is installed.
Then, the script will look for and delete any existing clockworkMod recovery backups that you have sitting around. Why? Because I'm re-using the script I wrote for the GT-P6210 tab... read that thread if it matters. Once my CWM-based recovery is installed, overwriting it with the same or newer versions won't delete the backups anymore.
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.
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 "t869_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.)
3. Select the file you placed on your storage card (starts with "t869_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
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/showpost.php?p=20074586&postcount=14
Update: According to shadejinx, this doesn't work for the SGH-T869. However, there's an alternative way, but you must have adb installed: Connect your tablet to the PC you have adb installed on, and power down the tablet. (A full power off - not just standby.) You'll notice that your tablet really isn't fully powered down, as there's a battery icon smack in the middle of the screen. It's in a "low power mode", and "adb" can still talk to it. Use adb to send the following command: "adb reboot recovery". You'll end up in recovery.
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 "t689_factory_recovery.img"
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 20111213:
* 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...
* Issues with getting into recovery are resolved. (after this update, you shouldn't need to use adb while the tablet is powered down.)
Here's the link for the recovery/root .zip (for the tmobile SGH-689)
version 20111213: http://www.mediafire.com/download.php?oro674o2881kw54
old versions:
version 20111206: http://www.mediafire.com/download.php?07ucaimq8qs6q05
Take care
Gary
uploaded and available. (message is to mark the thread as unread and as a place-holder for future notes.)
Your donation note is cool, man.
Just flashed update. It works fine I have root everything works the same installed superuser from market. Great work now all we need is a nice ICS ROM and voodoo
Sent from my SGH-T869 using XDA App
I wonder if tmobile would let me borrow one of these for a couple days so I can test some updates to the recovery.
"Hello, welcome to T-Mobile. Can I help you?"
"Yes, I'd like to quietly sit over there and attach my notebook computer to one of your demo tablets for about an hour to test voiding the warranty by flashing in low-level tools that, among other things, will allow anyone to bypass all the silly locks you people put on these devices. Oh, and I'm not a tmobile customer (and probably never will be.) Okay?"
heh
CSR: sure, go right ahead. Could you root it and install a custom ROM while your at it.. we've been getting tired of looking at this same old spoon fed sammy touchwiz and samsung apps nobody uses. Overclock the snot out of it.
just kidding, back on topic..
@garyd9 I'll get the updated recovery stuff tested tonight.
Updated and a new link posted in the OP.
Thanks to shadejinx for testing.
Changes for 20111213:
* 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...
* Issues with getting into recovery are resolved. (after this update, you shouldn't need to use adb while the tablet is powered down.)
garyd9 did this work blind and it worked perfectly the first time... I am very impressed. Anyone who reads this needs hit the thanks button on the OP.
garyd9 said:
* 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.
Click to expand...
Click to collapse
Where have you seen this?
rxxt said:
Where have you seen this?
Click to expand...
Click to collapse
I used the magic "search" function in XDA. It's a really cool feature of the site that lets you press a button, type a few letters, and find things.
Even if you aren't capable of using that function (and quite a few people are search-impaired for some reason), or if you might be searching for the incorrect term (I've done that myself a few times) you can always search manually. That involves opening threads and reading through them (not just the first post!)
I know that if I were looking for a firmware image, the DEV subforum thread marked with "Official FIRMWARES" would catch my attention, and I'm sure I'd find something useful if I spent a minute scanning through the thread that's less than 30 posts long. (That's a hint, by the way. I absolutely refuse to provide a direct link.)
Good hunting!
Gary
Sry, it was exactly the search function there do that I found this thread, but now I can see that it is too 'Galaxy Tab Plus', it was only 'Galaxy Tab' that Iam looking for, therefore the misplaced question..
(first the original reply)
rxxt said:
Wow, is it really true .. You have really savedmy day, damn well you tell me about the search option, otherwise I never havefound it, I can not thank you enough, what would we do without people likeyou..
Click to expand...
Click to collapse
Alas, 'tis true that some folk could never get along without those of us who point out the obvious.
(and now the current edited version)
rxxt said:
Sry, it was exactly the search function there do that I found this thread, but now I can see that it is too 'Galaxy Tab Plus', it was only 'Galaxy Tab' that Iam looking for, therefore the misplaced question..
Click to expand...
Click to collapse
Thank you for making my point.
edit: Please don't take my sarcasm personally. It's how I keep sane.
Take care
Gary
With the release of ICS, and seeing that others have taken over carrying the torch for updated and more modern versions of CWM Recovery, I'm no longer going to be supporting this release.
I'll leave the thread intact, but request that it be locked.
Oh, and I am still around, but I'm giving my Galaxy Tab 7.0 Plus to my wife. The stock firmware is actually very good for her, and she doesn't demand the amount of control over a tablet that I want.
Take care
Gary
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