OK, where to start.
I guess first you should know I had, and my wife still has, a Nook Color and I started out early last year with CM7. I (briefly) dabbled with CM 9 before switching to CM 10 late last year. I understand the basics, but trying to follow along in some of these threads is difficult because they refer to each other but some stuff is outdated.
So first question is do I choose hybrid or regular? At some point in one of the threads, it seemed like hybrid offered more stabilty? I have a 32 GB SanDisk ultra micro sdcard if that helps.
Next, I know in general that you need the img file, the from and gapps, plus any updates, but I,m not sure which updates I actually need. If there is an update to the img file, you can only do 1, right?
I had it up once, but I think it went to sleep and.
I could never get anywhere again. So, can someone please point me in the right direction to the right files and procedure, please?
sflesch said:
OK, where to start.
I guess first you should know I had, and my wife still has, a Nook Color and I started out early last year with CM7. I (briefly) dabbled with CM 9 before switching to CM 10 late last year. I understand the basics, but trying to follow along in some of these threads is difficult because they refer to each other but some stuff is outdated.
So first question is do I choose hybrid or regular? At some point in one of the threads, it seemed like hybrid offered more stabilty? I have a 32 GB SanDisk ultra micro sdcard if that helps.
Next, I know in general that you need the img file, the from and gapps, plus any updates, but I,m not sure which updates I actually need. If there is an update to the img file, you can only do 1, right?
I had it up once, but I think it went to sleep and.
I could never get anywhere again. So, can someone please point me in the right direction to the right files and procedure, please?
Click to expand...
Click to collapse
I know I may be confusing you with this HD vs HD+ discussion. But the devices really are very similar. The instructions for each are very similar. You just have to be careful that you get the right files for the right device. If you want to understand Hybrid vs Original SD, read my HD+ Hybrid thread linked in my signature. I even have a paragraph on the HD Hybrid there and explain what you have to do different from the HD+ Hybrid instructions. They work the same, you just have to use the files for the HD (from his Hybrid thread). The biggest advantage of the Hybrid is you can boot back and forth between stock and CM without having to remove the SD.
And I believe on the image update zip for the HD Hybrid image, you just need the latest update, not all of them.
So if you want to use the HD Hybrid, use the HD Hybrid image, update it with the latest update zip, boot so it creates the partitions. Put the HD CM10.1 and gapps zips on internal media storage and flash them with the CWM using "install zip from SD/choose zip from internal memory" option. With the HD CM10.1 zip there is no need to use a converter zip like is necessary for the HD+. Otherwise they are installed the same way.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
I know I may be confusing you with this HD vs HD+ discussion. But the devices really are very similar. The instructions for each are very similar. You just have to be careful that you get the right files for the right device. If you want to understand Hybrid vs Original SD, read my HD+ Hybrid thread linked in my signature. I even have a paragraph on the HD Hybrid there and explain what you have to do different from the HD+ Hybrid instructions. They work the same, you just have to use the files for the HD (from his Hybrid thread). The biggest advantage of the Hybrid is you can boot back and forth between stock and CM without having to remove the SD.
And I believe on the image update zip for the HD Hybrid image, you just need the latest update, not all of them.
So if you want to use the HD Hybrid, use the HD image, update it with the latest update zip, boot so it creates the partitions. Put the HD CM10.1 and gapps zips on internal media storage and flash them with the CWM using "install zip from SD/choose zip from internal memory" option. With the HD CM10.1 zip there is no need to use a converter zip like is necessary for the HD+. Otherwise they are installed the same way.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
So,
1) Load sdcard-cwm-hummingbird-hybridv2.zip on the card (the image file inside that is) (winimage or other tool)
2) Drop the UImage file from update-20130221.zip on the sd card
3) Copy cm-10.1-20130430-UNOFFICIAL-hummingbird.zip and gapps-jb-20130301-signed.zip to the Nook
4) Boot with the sdcard and point to the two files in 3, wiping cache in between.
Do I need the NookHD-HDplus-stock-fix-vold-for-dual-boot-hybrid-swapped file? Should I install that before I reboot from #4? If not, how do I get back in to do a recovery to install it?
Am I missing anything? I did all that, but maybe I mixed up some files along the way.
sflesch said:
So,
1) Load sdcard-cwm-hummingbird-hybridv2.zip on the card (the image file inside that is) (winimage or other tool)
2) Drop the UImage file from update-20130221.zip on the sd card
3) Copy cm-10.1-20130430-UNOFFICIAL-hummingbird.zip and gapps-jb-20130301-signed.zip to the Nook
4) Boot with the sdcard and point to the two files in 3, wiping cache in between.
Do I need the NookHD-HDplus-stock-fix-vold-for-dual-boot-hybrid-swapped file? Should I install that before I reboot from #4? If not, how do I get back in to do a recovery to install it?
Am I missing anything? I did all that, but maybe I mixed up some files along the way.
Click to expand...
Click to collapse
Clarifications.
1. I don't like winimage. I have a link to win32diskimager in my Hybrid thread.
3. Copy zips to Nook internal memory. On stock that is called sdcard unless you previously used my swap zip.
4. When you boot the first time, it will take a few minutes to prepare the SD and will reboot once in that process, ending in CWM. Then flash the two zips. You do not need to wipe cache between the two.
You only need that vold fix file if you want to use that same SD to store your media files while running stock and you want them swapped. And yes, you can do it then.
To get back to CWM later, bokbokan has a slick cyanoboot boot menu to allow you to do that. Just hold the n key while it boots to enter the menu.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
Clarifications.
1. I don't like winimage. I have a link to win32diskimager in my Hybrid thread.
3. Copy zips to Nook internal memory. On stock that is called sdcard unless you previously used my swap zip.
4. When you boot the first time, it will take a few minutes to prepare the SD and will reboot once in that process, ending in CWM. Then flash the two zips. You do not need to wipe cache between the two.
You only need that vold fix file if you want to use that same SD to store your media files while running stock and you want them swapped. And yes, you can do it then.
To get back to CWM later, bokbokan has a slick cyanoboot boot menu to allow you to do that. Just hold the n key while it boots to enter the menu.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
I'm stuck with the CM boot animation just spinning around. That's one of the problems I've experienced so far. I think one time I force rebooted and I got to start - it even started downloading apps, but I left it for a short bit and came back to a blank screen.
sflesch said:
I'm stuck with the CM boot animation just spinning around. That's one of the problems I've experienced so far. I think one time I force rebooted and I got to start - it even started downloading apps, but I left it for a short bit and came back to a blank screen.
Click to expand...
Click to collapse
Boot to CWM and go to advanced menu and wipe dalvik cache. Then try rebooting to CM10.1.
And you said downloading apps, did you mean optimizing apps? If so that is the dalvik cache being built. And it needs to finish that.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
Boot to CWM and go to advanced menu and wipe dalvik cache. Then try rebooting to CM10.1.
And you said downloading apps, did you mean optimizing apps? If so that is the dalvik cache being built. And it needs to finish that.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
I guess I will try tomorrow. I try holding down the n but just get a blank screen after the initial B&n nook screen.
After I entered my Google account info., it started downloading all of my Google Apps from the Play Store.
sflesch said:
I guess I will try tomorrow. I try holding down the n but just get a blank screen after the initial B&n nook screen.
After I entered my Google account info., it started downloading all of my Google Apps from the Play Store.
Click to expand...
Click to collapse
You are holding it too soon. Wait for the cyanoboot logo to show. Also, with some versions of the HD hardware, the cyanoboot menu does not work.
So you got so far as Google play store working? And it was automatically installing apps? Maybe one of those is what borked it. Go to one of your other devices and turn off automatic app installation in your play store account settings. Then factory reset with CWM and reboot to set up play store again without automatic installation.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
You are holding it too soon. Wait for the cyanoboot logo to show. Also, with some versions of the HD hardware, the cyanoboot menu does not work.
So you got so far as Google play store working? And it was automatically installing apps? Maybe one of those is what borked it. Go to one of your other devices and turn off automatic app installation in your play store account settings. Then factory reset with CWM and reboot to set up play store again without automatic installation.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
I will try again tomorrow from scratch. It doesn't matter if I hold the n down or not, all I get is the nook screen, then it scrambles up top, then a black, back-lit screen.
Thanks for all the one-on-one help. I really appreciate it. I know this shouldn't be that hard, but I've tried and downloaded so much I think I just need to delete it all and start from scratch to make sure I haven't got anything wrong...
...as far as the Google apps, that was just one time, but if I actually get to the point of setting up my account again, I will go turn it of...
Thanks!
sflesch said:
I will try again tomorrow from scratch. It doesn't matter if I hold the n down or not, all I get is the nook screen, then it scrambles up top, then a black, back-lit screen.
Thanks for all the one-on-one help. I really appreciate it. I know this shouldn't be that hard, but I've tried and downloaded so much I think I just need to delete it all and start from scratch to make sure I haven't got anything wrong...
...as far as the Google apps, that was just one time, but if I actually get to the point of setting up my account again, I will go turn it of...
Thanks!
Click to expand...
Click to collapse
Sounds like you may have one of the devices that cyanoboot does not work on.
I would suggest when you start over do not install the gapps until later. That way you can isolate whether Play Store is causing the issue. Also when you start over, before you flash the CM10.1 zip, go to mounts and storage in CWM and format /system, /cache and /data. Then you will have a clean installation.
When you get CM10.1 working without gapps, go to settings, about tablet, and tap several times on the build number. That will activate developer options. Then go to developer options and check the advanced boot menu. Then when you hold the power button, the reboot option will show and then when you select that, there will be more options including a choice to boot to recovery.
Then when things are working right, you can boot to recovery and flash gapps and continue setup.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
Sounds like you may have one of the devices that cyanoboot does not work on.
I would suggest when you start over do not install the gapps until later. That way you can isolate whether Play Store is causing the issue. Also when you start over, before you flash the CM10.1 zip, go to mounts and storage in CWM and format /system, /cache and /data. Then you will have a clean installation.
When you get CM10.1 working without gapps, go to settings, about tablet, and tap several times on the build number. That will activate developer options. Then go to developer options and check the advanced boot menu. Then when you hold the power button, the reboot option will show and then when you select that, there will be more options including a choice to boot to recovery.
Then when things are working right, you can boot to recovery and flash gapps and continue setup.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
I wiped all caches each time and did not try to do gapps:
First run, Cyanogen boot logo loop. Waited 15 minutes. Powered off/on and nook scrambled screen followed by black backlit screen.
Second run, symlink: some symlinks failed
E:Error in /emmc/Roms/cm-10.1-20130502-UNOFFICIAL-hummingbird.zip
(Status 7)
Installation aborted.
Wiped everything and tried install again. CyanogenMod Animation loop.
I will see if I can try another card just for the heck of it.
I had damage protection on my Nook Color and decided to take care of it. The power button didn't work anymore and it was becoming a hassle. There are apps I can download in CM to shut down, but not in stock. This Nook was a "deal" from QVC, but I'm thinking if I had known better, I would have just dealt with the old one until CM advanced a little further for the HDs.
Of course if the Stock replacement Roms are any good, I suppose I could replace that and "break" it if I brick it.
As a side note, I read something about B&N allowing sideloads, except you still couldn't do other stores. Does that mean I can either sideload Titanium Backup into the B&N stock then restore my apps from another backup or load apps on the other nook, then transfer the apk to the B&N stock?
So, I switched from my SandDisk Ultra 32GB card to my regular Class 4 card and I have actually been able to boot into the OS twice now...will update more later.
I'm up and running right now in CM10.1! WOW! What performance compared to my Nook Color! After reading some of the other threads, I think it's gotta to be the ultra micro sd card that was the issue!
Sent from my Barnes & Noble Nook HD using xda app-developers app
Not even a thank you??
carlyle070 said:
Not even a thank you??
Click to expand...
Click to collapse
I did click on the "Thank You" buttons and say "Thanks" several times, for all the help and even though it ended up being my card, yes. Thank you, leapinlar.
I think I was waiting for a reply to my post that I got it up and running so I could say "Thanks", so thank you for the reminder!
Is that enough Thanks for ya?! :laugh:
So if I have one of the devices that Cyanoboot just does not work on then there's nothing I can do?
zalmann said:
So if I have one of the devices that Cyanoboot just does not work on then there's nothing I can do?
Click to expand...
Click to collapse
I'm not sure what you mean, nothing you can do. There is nothing you can do about the cyanoboot menu not working, but you can use the boot menu in CM10.1 to boot to CWM. That is if you get CM10.1 booting itself.
Sent from my Nook HD+ running CM10.1 on emmc.
Maybe if you shared what device you have, someone can help.
Sent from my Barnes & Noble Nook HD using xda app-developers app
zalmann said:
So if I have one of the devices that Cyanoboot just does not work on then there's nothing I can do?
Click to expand...
Click to collapse
If the Cyanoboot menu does not appear when using the Hybrid setup on the Nook; unfortunately there is nothing you can do to make it appear. However, you can still install and use CM10.1 perfectly fine. This isn't actually a major problem.
I had two Nook HDs, one worked perfectly with the Cyanoboot menu, whereas the other did not - using the same files for burning, installing etc. I believe it maybe some hardware difference. Regardless, you can still boot CM10.1 on both tablets, and they both perform the same.
The only difference is that there is no menu, but once in CM, you can select the option to boot into CWM upon a reboot (if you've enabled Developer Mode + Advanced Reboot). Another method is to hold the "n" key whilst they Cyanoboot menu appears; this may not work, and you will be displayed with a lighter black screen, which does and displays nothing. At this point, turn off your Nook and try again. If that still doesn't do it, hold the "n" button as soon as you see the fuzzy screen taking over the "nook" text. It'll work, tested last today.
Again, unfortunately there is nothing you can do to make the boot menu appear; but this is hardly a problem on a daily basis.
Related
Epic Unleashed 1.1! First DROID2 rom!
For all the bugs people reported, I thank you. This release should fix a bunch of those bugs!
UPDATE:If you are having problems follow the new instructions on how to install bellow.
Changelog:
MAJOR Bug fixes.
Screen turns off.
Keyboard works.
Wifi may work(untested)
Accelerometer works.
Missing anything...?
Thanks:
Thank you Brendan for testing this release for me while my phone takes a little "nap" lol.
Features:
Deodexed
Bloatware removed
Scripts
Build.prop mods
Not sure if everyone know's this, but all my releases come with a widget that looks just like the HTC Clock called Fancy Widgets.
Please report bugs to me as you find them. Best way to contact me is email me at [email protected] or my GTalk Matt4542.
How to install:Important!
You will need to download Koush's bootstrap application and bootstrap your recovery. Then you can boot into recovery via the same app or you can install via ROM Manager(by rebooting into recovery, not via install rom from sdcard). Once you boot into recovery do a FULL nandroid backup and then you go to mounts and storage and mount /system manually to avoid more issues. Install zip from sdcard and toggle signature verification to disable. Now you can install the zip from the sdcard. Once this is done, reboot.
Now after reading all that here is your download!
Download <--- Click Me
For the best support please join my IRC chat on Freenode. #epicrom
Thanks for using Epic the first DROID 2 rom! Say thanks if you like it
I am trying to buy a domain name to host my files. All I need is $15 dollars. You do not have to do this if you do not want to. It is just to help me out a little bit Please donate as little as $1 to my PayPal [email protected]. Thanks if you do!
NOTE: Updated September 7th, 2010. Added additional steps to the process. Reread to reapply the Epic Unleashed 1.1!
Please READ each direction CAREFULLY and BEFORE executing each step. I can not stress how many mistakes are made because someone did not READ the directions carefully. So... yeah, once again, READ THE DIRECTIONS CAREFULLY!
How to Apply EpicUnleashed 1.1
Credits: The ROM was created by Matt4542. Tutorial was written by me with some simple directions from Matt. You'll need to be rooted in order to run the Droid 2 Bootstrapper.
The fine print: Matt4542 and/or I (DarkOnion) can not be held responsible if you mess up. If you mess up, you mess up. That's why I wrote the .sbf recovery tutorial. Matt has also written one. More simple, but requires Linux.
Here we go.
1. Download Koush Bootstrap here.
http://koush.tandtgaming.com//motorola/droid2/Droid2Bootstrap.apk
2. Download Epic Unleashed 1.1!
http://www.epic.grrmode.com/Epic-Unleashed11Deodexed.zip
3. Move both files to the base of the SD Card. Best way to do this is to plug your phone into your computer and move it like that. Make sure you phone is in USB mass storage mode. To change it, pull down the notification blind, choose USB connection, and choose USB Mass storage. Now copy and paste the two files to the new removable drive that showed up in your My Computer. The Epic-Unleashed11Deodexed.zip needs to be at the base of the SD card, and not in any folders. After moving all the files over to the phone, change the connection type back to Charge Only. Notfication blind -> USB Connection -> Charge only.
4. Install Koush Droid 2 Bootstrapper. Using an app installer, Astro File Manager, or equivalent, navigate to your SD card. The folder in Astro File Manager will be called sdcard. Choose Droid2Bootstrap.apk and install it. Follow the directions.
5. Now that it is installed, open Droid 2 Bootstrapper located in your applications section menu. It'll probably ask you for Super User access, say yes.
6. Press Bootstrap Recovery. It'll probably ask you for Super User access, say yes.
7. Next, we want to back your system file up by making a system image. In the Droid2 Bootstrapper, which you are already in, choose Reboot Recovery. Your phone should restart and load up into the bootloader.You should see some green text with various options, and a little lower than the middle of the screen, it says ClockworkMod Recovery.
Notes for navigating through the system. You need to use the keyboard to navigate. "Enter" will select. "Del" will cancel/go back. and the arrows are movement.
8. Using your slide out keyboard, scroll down to backup and restore and press the enter key. It should take you to another window. Choose Backup. Let it runs it's course. After it is all said and done. Reboot your phone by choosing reboot system now. (I don't think the rebooting is necessary, but I am just going to do it be safe.)
9. After you are done rebooting, if you did this, go back to the Droid 2 Bootstrapper, and choose Reboot Recovery. It'll reboot, and you'll eventually be back at the screen with the green text.
10. Using your keyboard buttons, choose mount and storage. And then choose mount /system. After that, press del to go back to the main menu.
11. Using your keyboard buttons, choose install zip from sdcard.
12. You need to make sure signature verification is off. Choose toggle signature verification and make sure it is off. At the bottom, under ClockworkMod Recovery, it'll say whether or not signature verification is enabled or disabled. You want it to say that it is disabled.
13. Then choose install zip from sdcard. Choose Epic-Unleashed11Deodexed.zip. It'll ask to confirm. Scroll down to Yes, and press enter. You'll see some commands going and eventually say it is complete.
14. Now navigate back to the main menu by pressing "Del" on the keyboard. And restart your phone by choosing reboot system now. It'll reboot and that's it! You've added EpicUnleashed 1.1.
Note: Your first boot will take a little while, up to 10 minutes. PLEASE BE PATIENT. You know that you corrected updated if your start-up animation is different.
If you need to undo this thing, boot back up into bootloader using Droid 2 Bootstrapper -> Reboot Recovery -> Back Up and Restore (after the reboot) -> Restore.
If you like this tutorial or any other tutorial, please feel free to show your gratitude by sending me a few bucks my way. I am a poor college student always trying to make ends meet. It's just more than writing a tutorial. Troubleshooting, helping others when they get lost, constant updating and rewording to make the process more simple. All donations are greatly appreciated, no matter the amount. $1 USD is good for two taco's at Jack in the Box! Paypal: [email protected]
And please don't forget about Matt. Send some love his way, too. It takes time create this stuff, not to mention troubleshoot, fix, and update. Make sure you send some love his direction. He needs money for a domain name. Paypal him at: [email protected]
If anyone comes across and problems with instructions, please let me know. I am going to try to keep this thread updated and easy to use.
= = =
How to Root Droid 2
http://forum.xda-developers.com/showpost.php?p=7865824&postcount=164
How to SBF Recovery Droid 2
http://forum.xda-developers.com/showthread.php?t=770224
How to Flash Epic Unleashed 1.1 ROM (see post #2)
http://forum.xda-developers.com/showthread.php?t=776320
I have v1.0 installed now. When I go into bootstrap and try to install 1.1 my phone still reads rom v1.0...?
Sent from my DROID2 using Tapatalk
Same for me, I came from stock and it appears I am still stock (no weather widget, etc). I notice I did not move the .zip from my /downloads/ to the base sd card, I will try that when I have some time.
Sent from my DROID2 using XDA App
pulptastic said:
Same for me, I came from stock and it appears I am still stock (no weather widget, etc). I notice I did not move the .zip from my /downloads/ to the base sd card, I will try that when I have some time.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
I am working on the issue now.
heartlessmcfly said:
I have v1.0 installed now. When I go into bootstrap and try to install 1.1 my phone still reads rom v1.0...?
Sent from my DROID2 using Tapatalk
Click to expand...
Click to collapse
I am working on a fix for that.
Thank you for the quick response. I am very excited about roms on the d2! I will play around with it some more after dinner.
Sent from my DROID2 using XDA App
I came from stock and it appears I am still stock (no weather widget, etc). Nothing has changed.
Maybe you can put the launcher2.apk for 2.2 as the main homescreen. I downloaded it from the droid incredible forum on my phone and everything is working alot snappier on my end. Still using stock just looking and waiting until everything is figured on this rom.
Later....
Sent from my DROID2 using XDA App
pulptastic said:
Thank you for the quick response. I am very excited about roms on the d2! I will play around with it some more after dinner.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
As a test for now just try to install your recovery from ROM Manager and boot into recovery that way. It is untested but it is worth a shot.
trillside said:
Maybe you can put the launcher2.apk for 2.2 as the main homescreen. I downloaded it from the droid incredible forum on my phone and everything is working alot snappier on my end. Still using stock just looking and waiting until everything is figured on this rom.
Later....
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Actually all of the bugs have been ironed out. It is a problem with the recovery. It may affect you, may not. I would put the stock Froyo launcher but I am not going to risk screwing with blur and causing more problems now. I will do it in a later release.
ya i installed it, but i did it from my downloads folder, it took like 3 seconds and nothing is new lol, i will have to try from the root i guess.
th3drow said:
ya i installed it, but i did it from my downloads folder, it took like 3 seconds and nothing is new lol, i will have to try from the root i guess.
Click to expand...
Click to collapse
I tried this and still nothing is new...
I tried to install this rom using multiple ways:
Wiped phone
Normal install as instructions say
Wiping SDCARD
Could not see any changes.
I'm sort of a noob at this but is this going to improve the speed of the device
Antiapplekid said:
I'm sort of a noob at this but is this going to improve the speed of the device
Click to expand...
Click to collapse
Yes and no. It'll is suppose to help clean up some of the junk that is on the phone. Have you rooted yet, because if you haven't... you need to do that before you flash a fixed version.
Yep I have already rooted it but I am in the stage where it says to make sure that my signature check is disable mine is enable how do I get it disabled sorry for being such a noob lol i got 5th in the state of Minnesota for computer repair but I I haven't done this kinda of stuff before
Everyone who has had problems please read my updated instructions!
for those having problems installing epic 1.1 try going to mounts and storage in clockworkmod recovery and select -mount /system before installing update.zip. worked for me may work for u idk. it now shows epic under android version instead of 2.2...
JKASS5 said:
for those having problems installing epic 1.1 try going to mounts and storage in clockworkmod recovery and select -mount /system before installing update.zip. worked for me may work for u idk. it now shows epic under android version instead of 2.2...
Click to expand...
Click to collapse
Yup. It does work. Thank you to you sir, and thank you to Matt for walking me through the updating process. I have updated the tutorial to reflect the changes.
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.
Hi,
I got a GTablet for Christmas today and I seem to have had some bad luck with it...
When I first got the tablet, it wouldn't keep any of my settings (not the wifi connection, not the development settings, nothing).
I thought I could get around this by flashing a different image (I am a novice user, though I do have a very modded N1 -- except it's still stock, sort of).
So... I did not have a MicroSD card at all (it's Christmas, all the places are closed until Monday, and I did not anticipate any problems). Still, I was able to flash the image of TNT Lite...Sort of. I had no problems upon booting, with the familiar N1 X boot animation.
I could add things to the stock Android launcher included with TNT Lite, but not remove them (as soon as I sled the icon I wanted to remove over to the 'trashcan', it force-closed the launcher, but my icon was removed nonetheless).
I did have a slightly working Market (I had the half-star issue). I did not have Titanium Backup installed, so I attempted to restore a working Market by force-closing and clearing the data of the 'Google Services Framework' and 'Market' services... Didn't work, like I thought, so I then tried to sideload Titanium Backup.
There is where my big, big problem came up. As soon as I tried to load TB onto my GTablet, I had tons of Force-Closes (and the tablet sort-of half rebooted). So, I got them to go away and tried again. Same thing.
So, I gave up and vowed to try again tomorrow. Except, I might not be able to tomorrow... As soon as I turned the tablet off, all was A-Okay for the most part... Later, I thought I'd try a little earlier than tomorrow, so when I turned it on.... I didn't get any farther than the GTablet logo before I realized I was in an infinite boot loop.
Now, I'm stuck with a boot-looping GTablet and a not working Christmas present! Help, please.
EDIT @ 3:44AM (Dec 29, 2010)- [FIXED]
FIXED!
When you get an sdcard you can do a fresh install from the external sdcard.
Yeah, I know that.
I don't know if I'll be able to rescue it or not (like I said, I'm new to this, and I was under the impression that [Power]+[Volume-UP] meant 'load recovery mode' which would look like the one I use on my Nexus One).
Do you think I should try (if I can get out of the infini-boot) flashing to TNT Lite (the latest, I think 3.1.0.1 or something similar)?
I'm wary of flashing to that one again, since it seems to have some serious problems with my particular tablet (I searched and there were no similar problems to mine that I could find).
I don't know if I'll be able to sideload Titanium Backup, are there any alternatives to that in getting a working Market (I tried anything else I could think of, but nothing was ever able to sideload onto my Tablet, ever)?
Have you installed Clockworkmod recovery?
Read the main threads (tnt lite, vegan, installing gapps) and I believe you will find someone has had the same problems you have
Hi there! I got the MicroSD card today.
So, I was looking through the guide I had previously used (http://forum.xda-developers.com/showthread.php?t=842004) and now I'm going to try to install ClockWork Mod recovery .8 (the one they said works best here).
I will update this (or maybe make a new message if you don't mind, if I can't edit my posts) if I can successfully get it working.
EDIT @ 12:47AM (Dec 29, 2010)- [Downloading the recovery mod file]
I downloaded the 'gtab-cwm-v08.zip' file to my MicroSD card, and extracted the 'update.zip' and 'recovery' folders inside (I imagine that is correct).
Then, took it out of the computer and loaded it onto my GTablet. I turned it on and did the recovery combination with [Power]/[Volume-UP].
It gave the screen that said it was loading the image and then another screen (black with 'ANDROID' and some other text on the screen).
For just a second, an error-type screen flashed on the screen (big warning icon, not sure how to describe it, but there was no text nor a loading bar).
Then, it rebooted (and then again and again, so it's not fixed yet).
Not sure what I did wrong... <
EDIT @ 1:43AM (Same Day)- [Installing recovery/Fixing boot loop]
Successfully installed Clockwork Mod Recovery .8 after downloading a 'command' file from my ROM's .rar (I modified the file so that it'll say <load-info>sdcard2<load-info> instead of <load-info>sdcard<load-info>).
Repartitioned to 2048 and 0 for the memory settings.
EDIT @ 1:55AM (Same Day) [Boot loop fixed, now just trying to figure out what to do next]
Repartitioning to 2048 and 0 in the memory fixed the boot loop. Yes!
Now, I don't know exactly what to do next... This one is still in progress right now.
Sounds like you did it right. Where you got the Clockwork file may make a difference though. There are 2 of them out there. One is from a thread that has it setup to load from an external sdcard. The other from the internal. Quick way to see what you have is to open the command file inside the recovery folder and see if it says sdcard, or sdcard2. You want it to point at whatever method you are using to load it. Sdcard for internal, sdcard2 for an external card.
If you haven't tried it already, look at this.
After that just load the rom you want.
Beware though, you may have a strange model that won't work with that, some have been floating around..... Read the full thread too
This may also be useful to you: http://forum.xda-developers.com/showthread.php?t=842000
Now, I see why it did not work... Mine had no 'command' file AT ALL (in the 'recovery' folder)!
So, how can I make one?
By the way... To address your initial issue of being in a boot loop. Get clockwork installed. Once installed go to advanced, partition sdcard. Use 2048, and 0 for the swap. That will get rid of the boot loop.
XANAVirus said:
Now, I see why it did not work... Mine had no 'command' file AT ALL (in the 'recovery' folder)!
So, how can I make one?
Click to expand...
Click to collapse
You can find one in most any of the roms. The earlier TnT roms had them, others too...
They are all the same except for the sdcard, or sdcard2 thing I talked about so don't worry about finding a specific one.
So, when I install Clockwork, do I need to leave that MicroSD in there to run it everytime (not sure where it puts the files/etc)?
XANAVirus said:
So, when I install Clockwork, do I need to leave that MicroSD in there to run it everytime (not sure where it puts the files/etc)?
Click to expand...
Click to collapse
Nope. Once it is installed you don't need the sdcard anymore. Be sure to read my post a couple above this about fixing your boot loop.
Okay, as you wrote in the first page to reformat to 2048 and 0 (in that order), I just did that (as wrote in my edit )
What should I do next?
XANAVirus said:
Okay, as you wrote in the first page to reformat to 2048 and 0 (in that order), I just did that (as wrote in my edit )
What should I do next?
Click to expand...
Click to collapse
Reboot and see where you are... It should go back to where you were before you got the boot loop. The stuff on your internal sdcard will be gone though. So I hope there wasn't anything important there.
BTW, you can hit the back button on the side of your screen to go backwards in the clockwork menus.
Nothing important. I haven't even installed anything new or changed any new settings on my current ROM (that TNT-Lite).
I'm rebooting it right now as I type this.
EDIT @ 1:58AM (Same Day)-
Your steps fixed my boot looping problem. Thanks!
Now, I don't know what next to do. I don't have Titanium Backup installed (couldn't sideload it, I kept having problems).
I don't know if the Market is fixed yet.
Did it boot?
Sent from my VEGAn-TAB-v1.0.0b4 using Tapatalk
Yes, thanks!
Awesome! Now I would boot back into clockwork and make a backup. You can rename them from a file manager too so they make sense..
Sent from my VEGAn-TAB-v1.0.0b4 using Tapatalk
I don't ever use titanium to do the market fix. I just use it to backup apps.
Sent from my VEGAn-TAB-v1.0.0b4 using Tapatalk
Okay, I made the backup like you asked. So, now should I try to fix the Market?
Is there anything else that needs tweaking?
**** 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
**this was a very early guide and most of the files and methods referenced in it are long outdated, sounds crazy I know as the phone has barely been out, but i recommend finding more recent guides at this point. I wanted to leave this up for archival reasons though. As of 7-22 I am running dhackers CM10 build with great results. Just don't forget to set max cpu clock back down to 1500 mhz if you don't want it over locked out of the box **
As per the usual disclaimer....at your own risk, be aware of IMEI loss issues and whatnot...basically cover your own butt.....and enjoy.....
7-15 2:46pm **As of right now voice and SMS are not working on my phone while other people report they are working fine. While you can still play around and see just how amazingly fast CM is on this phone, YMMV. If it doesn't work you need to know how to go back to stock before trying this.
7-29 this guide is very old, it pre-dates kexec and is only here for historical purposes
For clarification: The question was asked if one is supposed to follow the original Team Epic Kexec kernel instructions or these steps and the answer is two fold. If your goal is to install the UNOFFICIAL CM9 built by Invisiblek (which is the purpose of this thread), then you follow the steps in THIS THREAD ONLY. There are a couple steps and a couple files linked to in the original Kexec page that will not allow you to install CM9. That page was made for those wanting to try out their Kexec Proof of Concept KERNEL, not install a ROM of any kind.
This thread makes some assumptions, such as you already have a working install of the Android SDK and ADB, you already have the drivers installed, you are using the original USB cable that came with your phone, you know how to move around DOS to get to the directory where you downloaded the files, etc.......those lower level tasks are for another thread.
To Try Our Proof-of-Concept Kernel <<<The base of these instructions was the Team Epic Kexec Kernel page seen at this link, Many Thanks to them
Thanks to Invisiblek for clarifying and helping me get steps just right.
The following is an adaptation of the CM Kexec kernel proof of concept with the changes in files and steps necessary to load the latest CM9 work in progress. Be advised I take no credit at all. This is the work of Team Epic and Invisiblek. I just put this together for myself and for others who would like to try it with one caveat. DATA doesn't work! Voice and SMS only....and maybe 1xRtt data.....so you will be relying on WiFi for data! You've been warned!
Also, I highly suggest you use a free MD5 Hash checking utility to verify the integrity of the files you are downloading. That is why the MD5 hash is provided, so you can be sure you didn't get the wrong file or a corrupt download that could cause a BRICK!
If you don't follow the directions carefully you can end up with a brick! Ask questions after reading the OP if you still aren't sure. I probably won't know the right answer for sure. You may have to wait on someone with more experience in this to answer your question.
DO NOT ACCEPT AN OTA UPDATE WHILE RUNNING THIS SETUP
1. Download the recovery.img (MD5: f1c01ad20e02751a73188f173eb412ca), which combines our source-based kernel with our previously released CWM v4.
2. Flash the recovery.img following these instructions, that is:
Code:
adb push recovery.img /sdcard/
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 bs=256k
sync
3. Reboot into recovery (using volume up, home power buttons), wipe data, install one of invisibleks CM9 roms>click here for all of his CM9 roms< which do not have boot.img integrated, then continue with the steps below:
4. Download these additional files:
(required download)boot.img (MD5: db058f4b15df0fa1b9ee04a5c17cf103), which is invisibleks custom boot.img
It would be good at this point to read ahead and determine where you will be loading the next file. Keep in mind if you are in stock recovery and choose to wipe data, this will wipe the internal memory.
if you plan to load onto internal memory download this file boot_emmc_boot_img.zip (MD5: 84a3f98c194f6dedc583dbc75ccc34c2)
or
if you plan to load onto sdcard (ext) memory download this file boot_sdcard_boot_img.zip (MD5: 88904d7e69d455ff88756b4d1ad79aac), which are applied in recovery to kexec (boot) the custom boot.img.
5. Place boot.img either on the internal SD card (the /sdcard/ folder), or on the external SD card (the /mnt/extSdCard/ folder).
The boot.img kernel boots directly out of one of these folders, it will not (and should not) be flashed to the device.
6. If you're using the internal SD card, place boot_emmc_boot_img.zip in /sdcard/ as well. If you're using the external SD card, place boot_sdcard_boot_img.zip in /mnt/extSdCard/.
7. Reboot into recovery.
8. If using the internal SD card, select "Install zip from sd card" and then "choose zip from internal sdcard", then "boot_emmc_boot_img.zip". Alternatively, if using the external SD card, select "choose zip from sdcard", then "boot_sdcard_boot_img.zip".
At this point, the device should reboot "in the middle" of applying the update, temporarily booting boot.img. If the update "completes" and returns to the CWM menu, kexec has failed or the wrong recovery was loaded in the beginning. Please check the locations of boot.img, and boot_emmc_boot_img.zip or boot_sdcard_boot_img.zip and verify recovery.img file used was the correct one, verify using an MD5 hash checker.
9. Once booted, the custom kernel can be confirmed by checking "Kernel version" in "Settings", "About device". It should report:
3.0.8-gdefeb6f
[email protected] #1
SMP PREEMPT Sun Jul 8 04:27:58 EDT
2012
10. To reboot into the stock kernel, select "Restart" from the Power menu, which will actually reboot into CWM recovery. Press the Power button to select "reboot system now" and leave recovery.
11. You cannot simply power on your phone with this setup! In order to power on your phone you will have to hold volume up, home and power to boot into recovery and load the zip file you chose at step 4 where you chose either internal or external memory, so either "boot_emmc_boot_img.zip" or "boot_sdcard_boot_img.zip". If you do accidentally boot up by just hitting power, no big deal, it will give you all sorts of force closes, simply pull battery and boot back up using the Vol up, Home, power method.
If anyone would like to suggest further clarification, please do. To get the stock Google apps such as Play Store get the package HERE and install in recovery
Alternatively a more condensed version of this install procedure has been posted by nbsdx and can be found HERE.
7-15 2:46pm **As of right now voice and SMS are not working on my phone while others are working fine. While you can still play around and see just how amazingly fast CM is on this phone, YMMV. If it doesn't work you need to know how to go back to stock before trying this.
If you want to return to bone stock, simply go to THIS THREAD to get STOCK ROM IMAGE and then put your phone into Odin Download mode by following THIS THREAD and be sure to flash it using the PDA button. It will take a while, probably 20 minutes or so, it will take forever to boot up the first time but you will be on bone stock like new.
Very informative. Would read again.
Sent from my Transformer Prime TF201
dual boot
Being that we have to use kexec anyhow, it would be nice (especially with the state of current cm9 rom) if we could fully dual boot so as to keep stock system and data for stock kernel.
Like here,
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html
I just installed successfully using the instructions in the OP so I can confirm it works correctly. Holy crap it's fast.
Anybody want to put up a video of how well it runs for us that aren't brave enough to put it on our own phones?
Sent from my SCH-I535 using xda premium
dakalter said:
Anybody want to put up a video of how well it runs for us that aren't brave enough to put it on our own phones?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I'll leave that part to someone who doesn't sound like a retarded redneck on video.
silasrye said:
I tried to install the vzw cm9 (with with invisiblek's boot.img put back into the zip) via this method exactly.
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html
fake cwr works, and everything went fine, but when i try to flash boot_cm9.zip i stay in cwr.
I am using the cwr from this post
http://forum.xda-developers.com/showthread.php?t=1773514
I had started with the twrp from that post, but it didn't recognize my internal sdcard.
So, I don't see why this shouldn't be a doable thing. But something probably needs to be redirected somewhere.
The good news is, I boot into my normal rom without problem.
Click to expand...
Click to collapse
If you follow the steps in this thread, including using these links for your files, it will work without a problem.
I can't comment on why other guides on other sites using other files don't work.....and not really sure how it applies to this thread. Lets try to keep it on topic. If you have issues with the dual booting instructions, you might start a new thread to address that or jump in irc.freednode.net/verizons3 and graciously ask the people for help
When you flash the the CM9 rom built by Invisiblek it will come back out to CWR menu. At that point in the process I realized I hadn't copied the boot.img file into the root of my sd card, so i left it on the CWR menu, popped out the sdcard, copied the boot.img file over (already had the boot_sdcard_boot.img file on the root of sdcard), and popped the sdcard back in, chose advanced->reboot recovery, then followed the steps in this guide, worked perfectly.
silasrye said:
I tried to install the vzw cm9 (with with invisiblek's boot.img put back into the zip) via this method exactly.
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html
fake cwr works, and everything went fine, but when i try to flash boot_cm9.zip i stay in cwr.
I am using the cwr from this post
http://forum.xda-developers.com/showthread.php?t=1773514
I had started with the twrp from that post, but it didn't recognize my internal sdcard.
So, I don't see why this shouldn't be a doable thing. But something probably needs to be redirected somewhere.
The good news is, I boot into my normal rom without problem.
Click to expand...
Click to collapse
You need to add one line to Invisiblek's updater-script that "flashes" the boot.img to the bootloader partition in the multi boot folder. Check out the sprint cm9 install for the line to add.
I have tested dual booting to work perfectly.
is the data not working due to the ril??
suzook said:
is the data not working due to the ril??
Click to expand...
Click to collapse
yes, will update OP once we have working 3G/4G data
as of right now my voice and SMS isn't working while others is.....trying to figure it out
I flashed back to stock, simply because I need to have voice and SMS working. I could deal without 3G/4G data for a little bit and use WiFi, but no SMS/Voice was a deal breaker on my phone. I have to be easily gotten in touch with for work and such. It was fun while it lasted.
Will these same instructions work for the CM10 build that is in the server list?
17akota said:
Will these same instructions work for the CM10 build that is in the server list?
Click to expand...
Click to collapse
No. Different files used, probably a different step or two also. I plan to edit this once CM10 builds are ready for public consumption. These instructions also don't include the automated kexec scripting work done recently that allows your device to cold boot into CM9.
Sent from my SCH-I535 using xda premium
neyenlives said:
No. Different files used, probably a different step or two also. I plan to edit this once CM10 builds are ready for public consumption. These instructions also don't include the automated kexec scripting work done recently that allows your device to cold boot into CM9.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I figured that.
Could you point me in the direction of the new Kexec? I read about it somewhere and would like to try it out.
17akota said:
I figured that.
Could you point me in the direction of the new Kexec? I read about it somewhere and would like to try it out.
Click to expand...
Click to collapse
irc.freenode.net #verizons3
Sent from my SCH-I535 using xda premium
i came from a thunderbolt, and know how different a RIL can be from phone to phone, so i ask this quite seriously...
How different is the RIL from the Gnex to the SGIII?
seang said:
i came from a thunderbolt, and know how different a RIL can be from phone to phone, so i ask this quite seriously...
How different is the RIL from the Gnex to the SGIII?
Click to expand...
Click to collapse
Completely different processors.
Is there anyway to get the TouchWiz Camera on CM9? I really like that camera app.
I tried just putting it in /system/app and changing the permissions to rw-r--r-- and rebooting and nothing
Then i tried just installing it like a normal apk and it failed.
I would love CM9 if i could just get the stock camera app too work.
BTW im using DHacker29's CM9 and its amazing. So much easier to install.
17akota said:
Is there anyway to get the TouchWiz Camera on CM9? I really like that camera app.
I tried just putting it in /system/app and changing the permissions to rw-r--r-- and rebooting and nothing
Then i tried just installing it like a normal apk and it failed.
I would love CM9 if i could just get the stock camera app too work.
BTW im using DHacker29's CM9 and its amazing. So much easier to install.
Click to expand...
Click to collapse
It probably requires touchwiz frame work. It will take significantly more work than just dropping in an apk
Sent from my SCH-I535 using xda premium
DHacker's CM10 is awesome!! I've been running it all day and Jelly Bean is really smooth on the S3.
http://www.droidhive.com/forums/index.php?/files/category/26-sgs3/
Check it out guys.