Related
Here you go! Ripped straight from my article: How To: Remove AT&T From Captivate.
Instructions
WARNING: I am not responsible for any bricked, messed up, ruined devices. You modify your phone at your own risk. These processes are not necessarily safe for your Samsung Captivate or any other device.
Root the Samsung Captivate
First things first. You’ll need to root your device to continue with many of the modifications listed below. For our “How to Root the Samsung Captivate” guide, click here. It’s very very easy. Even a total noobie can do it! If you have questions, post a comment and we’ll get back to you A.S.A.P. Look below if you get the idea, check out our “How to Root the Samsung Captivate” guide if you don’t.
Download Update.zip
Plug in your Captivate to your computer. When the phone notifies you that the USB has been plugged in, scroll down your notifications bar and click on “USB connected: Select to copy files to/from your computer.”
Click “Mount”
Now, you’ll probably see a popup telling you a new USB drive has been inserted, open it up on your computer. In Windows, click “Open folder to view files.”
Drag Update.zip into the Captivate USB drive (on the top level… do not navigate into folders)
Turn off the Captivate (Power Off)
Hold down the Volume Up/Down rocker and the power button until you see some action. Your phone is now booting into recovery.
Use the volume down button to scroll down to “Reinstall packages”
Click the power button to select that option
Enable App Sideloading
AT&T has some weird reservations against app sideloading. That means, AT&T Android users can not use any apps not downloaded on the Android Market. Have no fear! You can remove this restriction easily. Check below for the basic instructions, or click to go to our “Enable Captivate App Sideloading” guide.
BusyBox Installed
Samsung Captivate with root
SQL Database Manager
We suggest trying the SQLite plugin for Firefox, you can find it here.
Turn on USB debugging: Settings >> Applications >> Development
Plug in your Samsung Captivate
Open up Command Prompt on your computer (Windows: start, search, type “cmd”, right click cmd, Run as Administrator)
Type in: cd _____PATH TO ANDROID SDK FOLDER______\tools
Example: cd C:\Users\USERNAME\Desktop\android-sdk-windows\tools
Type in: adb shell
Type in: su
Type in: cp /dbdata/databases/com.android.providers.settings/settings.db /sdcard/settings.db
Type in: cp /dbdata/databases/com.android.providers.settings/settings.db /sdcard/settings.db.backup
Type in: exit
Type in: exit
Type in: adb pull /sdcard/settings.db %userprofile%\desktop
Leave Command Prompt open
Open SQLite Manager in Firefox by pressing Tools >> SQLite Manager
Click “Database”
Then click “Connect Database”
Navigate to “settings.db” on your Desktop
Expand the tables
Click “Secure” on the panel
Scroll down to ID 6, “install_non_market_apps”
Double click it and change “value” from 0 to 1.
Close SQLite Manager
Go back to the command prompt window, type in: adb push %userprofile%\desktop\settings.db /sdcard
Type in: adb shell
Type in: su
Type in: cp /sdcard/settings.db /dbdata/databases/com.android.providers.settings
Type in: chmod 777 /dbdata/databases/com.android.providers.settings/settings.db
Type in: reboot
Disconnect your Captivate from your computer while your phone reboots.
Remove AT&T Bloatware Apps
Must have root and BusyBox installed before performing this process!
Open up Android Market and search/download “Titanium Backup”
Make sure your phone is not “Mounted” with USB
Open Titanium Backup
Press the Backup/Restore button
Click on each app and press un-install if you’d like to get rid of it. Do not delete apps off of this list, unless you know it is safe! This deletes these potentially forever… so be sure about things!
Delete-able:
AT&T Navigator
AT&T Radio
AT&T Maps
AT&T Music
AT&T Mobile Hotspots
Mobile Banking
Mobile Video
Where
YPmobile
AT&T FamilyMap
Mini Diary
MobiTV
Write and Go
Remove AT&T Market Restrictions
Market restrictions? What? You mean AT&T really censors what apps I can and cannot see on my Samsung Captivate? Yes they do. But, no problem. Android developer Andrea Baccega has developed an app called "Market Enabler" to remove the censorship by emulating the T-Mobile market on the Samsung Captivate as well as other devices. Instructions below if you've already got root access:
Download “Market Access” and install the latest version of the APK file on your Captivate.
Don't know how to install .apk files? Copy the file to your phone and then install "Apps Installer" or "Astro File Manager" from the market. It's easy! Just double click the .apk when you find it!
Close the Market down fully. If you were running the Market previously, reset the phone so it is not a running task. Or use a task killer and end the Market app.
Open up the Market Access application and go to "Backup value" in case you need to get back to the AT&T market
Then click "Providers" and find: "T-Mobile [US]"
Click and hold that option until it says "Emulate "T-Mobile" SIM?" -- click "Yes" there
You may have to Allow Market Access in Superuser Permissions
Click back to "Settings" click the checkbox next to "Emulate on boot"
All done. Now your Market is uncensored.
Remove AT&T and/or Samsung Logos on the Device
Not quite yet! Check back later. We are working with some chemistry-experts to see if we can dissolve those logos. Have you seen how sexy the Captivate is without logos? Click here to check out the video.
Credits
Big thanks to the XDA-Developers forum users for all their hard work on posting Captivate guides. User: nbs11 – bloatware removal. User: clubtech – market censorship removal application. User: blackjackboy – original root guide. User: kirbo20 – app sideloading.
Thank you for compiling all this in a FAQ WT fasion.
Sent from my AOSP on XDANDROID MSM using XDA App
got everything to work... except the Swoosh
Ok heres is what happened. I started on this whole guide and got hung up somewhere in the middle. I had to use Root Manager and SQLite Editor. Got everything but the AT&T Boot Swoosh sound off. I realize that this is not the exact post for the swoosh sound, but here goes. whenever im using the /sdcard command at the end of my command, it will say that this is a read only file system. it was writing to the sd card at one point, then somehow stopped. Any suggestions on how to fix this?
ThePatient said:
Ok heres is what happened. I started on this whole guide and got hung up somewhere in the middle. I had to use Root Manager and SQLite Editor. Got everything but the AT&T Boot Swoosh sound off. I realize that this is not the exact post for the swoosh sound, but here goes. whenever im using the /sdcard command at the end of my command, it will say that this is a read only file system. it was writing to the sd card at one point, then somehow stopped. Any suggestions on how to fix this?
Click to expand...
Click to collapse
you can either delete it from system/etc/PowerOn.wav
or you can install silent boot
http://www.androlib.com/android.application.com-antweb-silentboot-BnqC.aspx
Anyone try to remove the AT&T Address Book app yet?
I remember seeing this....and would be incredibly happy if this was possible!
kennethpenn said:
Not quite yet! Check back later. We are working with some chemistry-experts to see if we can dissolve those logos. Have you seen how sexy the Captivate is without logos? Click here to check out the video.
Credits
Click to expand...
Click to collapse
Great write up, still hoping we can remove that logo
decepticon said:
Great write up, still hoping we can remove that logo
Click to expand...
Click to collapse
Now only if I can remove the AT&T logo from the front of my phones screen at the top!
22 steps to enable sideloading, and you are still using a gui editor, this can be done in 8 steps shown here on xda-developers:
/showpost.php?p=7267391&postcount=1
Also, to remove the at&t/samsung boot animation you can delete (or rename) the file /system/media/bootsamsung.qmg however this leaves the at&t white "world phone" screen on longer and then a black screen for the rest of the boot process. Haven't found anything that will edit the .qmg file (which was used on the samsung moment and the galaxy spica as well), also placing a bootanimation.zip in this folder after removing the bootsamsung.qmg does not work(although it does on the samsung moment).
not sure how i'm still a new user and can't link websites when I've been a member since 2008...
shad0wf0x said:
22 steps to enable sideloading, and you are still using a gui editor, this can be done in 8 steps shown here on xda-developers:
/showpost.php?p=7267391&postcount=1
Also, to remove the at&t/samsung boot animation you can delete (or rename) the file /system/media/bootsamsung.qmg however this leaves the at&t white "world phone" screen on longer and then a black screen for the rest of the boot process. Haven't found anything that will edit the .qmg file (which was used on the samsung moment and the galaxy spica as well), also placing a bootanimation.zip in this folder after removing the bootsamsung.qmg does not work(although it does on the samsung moment).
not sure how i'm still a new user and can't link websites when I've been a member since 2008...
Click to expand...
Click to collapse
It's just very detailed. Takes like five minutes to do...
Nice job kenneth. If I were you id take a look at the guide I wrote on the subject in general. Nb added stuff and did edits. Feel free to use the info there to simplify your own guide.
Sent from my Samsung Captivate using XDA app
You didn't really explain how to uninstall the AT&T applications. How is this done?
raid0422 said:
You didn't really explain how to uninstall the AT&T applications. How is this done?
Click to expand...
Click to collapse
Open Titanium Backup
Press the Backup/Restore button
Click on each app and press un-install if you’d like to get rid of it. Do not delete apps off of this list, unless you know it is safe! This deletes these potentially forever… so be sure about things!
Delete-able:
AT&T Navigator
AT&T Radio
AT&T Maps
AT&T Music
AT&T Mobile Hotspots
Mobile Banking
Mobile Video
Where
YPmobile
AT&T FamilyMap
Mini Diary
MobiTV
Write and Go
Does this mean that Titanium Backup is what you use to uninstall software? I looked at the description of it and it just said it was for creating a backup image.
OK, yeah it is. I just used it to uninstall everything.
Yes Titanium Backup can be used. I've updated the post to make things clearer... thanks for your feedback!
Sent from my Samsung Captivate using XDA app
Here is the stock Galaxy S startup animation and sound to get rid of the AT&T antenna animation and swish sound.
Thanks to emclondon in the Galaxy S forums for the upload.
Cool.. I will definitely refer to this thread when I get my captivate
when I type su it gets me permission denied...any ideas?
raid0422 said:
OK, yeah it is. I just used it to uninstall everything.
Click to expand...
Click to collapse
How?
Instructions:
Open Titanium Backup
Press the Backup/Restore button
Click on each app and press un-install if you’d like to get rid of it
OK after Pressing Backup/Restore there are only 5 options in the list (apparently for backing up)
Accounts
Applications Widgets
Bluetooth Pairings
Country, Language, Time zone
Wi-Fi Access Points
Where are the applications listed to uninstall?
Hey Guys
So one of the biggest questions I have seen in the last couple weeks since the Rogers captivate was released is how to root. I figured I would write a nice tutorial for everyone to make it easier!
Method 1: SuperOneClick
This is the easiest way, however most people have not been able to achieve root using this. Try this first if no luck move to method 2. Instructions on how to root using SuperOneClick can be found here
Method 2: Manual Root using ADB and Terminal
This one takes more time and not as easy to do as you have to do everything manually. But haven't heard of any problems with it yet
Step 1: Install <PDANet> Drivers. Just download the file and install. Select Samsung drivers. No need to actually install PDAnet on the Captivate you just need the drivers from the install. Follow the instructions with the installer to properly install the drivers.
Step 2: Download <Andriod SDK>.
- Extract the Android SDK .Zip file to C:\AndroidSDK (this should name the new folder created AndroidSDK in the C directory.
- Go to your start menu and search cmd or click run and type in cmd to open command prompt
- Type the following into command prompt, hitting enter at the end of each line
cd C:\AndroidSKD\Tools
adb devices
- You should see a serial number pop up. This is the serial number of your phone. This means ADB is set up
Step 3: Download <RageagainsttheCage Rooting Files>
- Extract them to the c:\AndroidSDK\tools\ folder. HAS TO BE IN THIS FOLDER FOR THE FOLLOWING COMMANDS TO WORK
Step 4: Unplug phone if it is plugged in. Then, on the phone, go to Settings > Applications > Development and make sure USB Debugging is Checked ON.
Step 5: Plug phone back in to computer. Make sure SD are not mounted
Step 6: Reopen Command prompt if not open. In the command prompt enter the following, pressing enter at the end of each line
cd c:\androidsdk\tools\
adb devices
adb push Superuser.apk /sdcard/
adb push su /sdcard/
adb push rageagainstthecage-arm5.bin /data/local/tmp/
adb shell chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
Step 7: On the phone, go to Marketplace and download Terminal Emulator
Step 8: Leaving the phone plugged in, open the Terminal Emulator on the phone. Type the following, pressing enter at the end of each line
cd /data/local/tmp
./rageagainstthecage-arm5.bin
Step 9: WAIT. It will take a full minutes for the rage root to install. When finished you will see "Forked Childs". DO NOT DO ANYTHING TILL YOU SEE THIS. Terminal will allow you to type as it goes back to $ while it is installing BUUT DO NOT DO ANYTHING JUST WAIT(Cannot stress this enough)
Step 10: once "Forked Childs" appears, exit the Terminal App, and then reopen it. Instead of $ you should now see #. If not redo Step 7. Otherwise continue.
Step 11: Type the following hitting enter at the end
cat /proc/mounts
This should bring up a list (Easiest to view in landscape mode. Look for the following
/dev/block/XXXXXXXXXX /system YYYY ro 0 0 (the XXXXXXXXX part should be different depending on which device you have. The YYYY part will either be; ext2, ext3 or yaffs2 or something similar. )
My YYYY was rtf , not sure if it will be the same for everyone (though i assume it is)
Step 12: Now in the terminal window, using the info from above, enter the following, hitting enter at the end of each line (Be sure to enter spaces where needed as below)
mount -o rw,remount -t YYYY /dev/block/XXXXXXXXXX /system
cat /sdcard/Superuser.apk > /system/app/Superuser.apk
cat /sdcard/su > /system/bin/su
chmod 4755 /system/bin/su
mount -o ro,remount -t YYYY /dev/block/XXXXXXXXXX /system
exit
Step 13: Close terminal window if still open. Check your app drawer and, assuming everything was completed properly, you should see Superuser. If not redo Step 12, again watching for spaces and using the correct info from Step 11.
ACKNOWLEDGEMENTS
I, in no way shape or form, came up with the above method or tools. This method was modified from and composed from the method decribed over at Theunlockr.com for ease of use and to root the Captivate specifically. I big thanks go out to those guys!
ORINGAL LINK CAN BE FOUND HERE
WARNING
I am not responsible for any damage doone to the phone or its file system as a result of this tutorial. It is for educational purposes only. You have been warned!
THANK YOU!
No other method was working for me (not SuperOneClick, not these ADB instructions). Sure enough, using Terminal Emulator, I was able to get #. I wasn't able get this through adb, nor was I through SuperOneClick (infinite loop @ "mount" command).
I noticed a few things:
-When I compared filesizes from your provided Rage Root files, to the ones that were included in this thread (which also come with SuperOneClick—and which I was unable to get working), I noticed major differences. This gave me hope!, as I'd tried everything else that I knew how to prior to this point.
-My "XXXXXXXXXX" was actually only 4 characters: "stl6".
-My "YYYY" was only 3 characters ("rfs").
-SuperUser showed up on my applist without even requiring a reboot.
THANKS AGAIN
I shall now attempt to apply a lagfix; I will report back with results.
--Bah: no luck. RyanZA's OCLF V2.2+ returns error:
Could not mount /dev/block/mmcblk0p2 onto /dbdata/rfsdata: mount: No such file or directory
--OCLF V1+ returns error:
Could not create /data/linux.ex2 - dd: can't open '/data/linux.ex2': Permission denied
Uh-oh.
PhrProfess said:
THANK YOU!
No other method was working for me (not SuperOneClick, not ). Sure enough, using Terminal Emulator, I was able to get #. I wasn't able get this through adb, nor was I through SuperOneClick (infinite loop @ "mount" command).
I noticed a few things:
-When I compared filesizes from your provided Rage Root files, to the ones that were included in this thread[/url] (which also come with SuperOneClick—and which I was unable to get working), I noticed major differences. This gave me hope!, as I'd tried everything else that I knew how to prior to this point.
-My "XXXXXXXXXX" was actually only 4 characters: "stl6".
-My "YYYY" was only 3 characters ("rfs").
-SuperUser showed up on my applist without even requiring a reboot.
THANKS AGAIN
I shall now attempt to apply a lagfix; I will report back with results.
--Bah: no luck. RyanZA's OCLF V2.2+ returns error:
Could not mount /dev/block/mmcblk0p2 onto /dbdata/rfsdata: mount: No such file or directory
--OCLF V1+ returns error:
Could not create /data/linux.ex2 - dd: can't open '/data/linux.ex2': Permission denied
Uh-oh.
Click to expand...
Click to collapse
Yup same problem here. I was able to root it manually a few days ago, but have as of yet been unable to lag fix it.
Strange. After I rooted I had no problem using RyanZa's Lagfix. Your still using the stock rom after rooted correct?
deacfire said:
Strange. After I rooted I had no problem using RyanZa's Lagfix. Your still using the stock rom after rooted correct?
Click to expand...
Click to collapse
Correct. I've tested out quite a few apps from the market, though.
When I mount my device, I notice that there are some files on my internal SDCard:
-su
-Superuser.apk
-nv_data.bin
-busybox (why is this there, I uninstalled that)
-update.zip
...and some folders:
-layar
-twc-cache
-Android -» data -» com.cooliris.media
-Android -» data -» com.google.android.apps.maps
-svox
...These all have subdirectories.
Not knowing what a default internal SD directory ought to look like, I wonder: Could any of these be causing a conflict? I read that some said not to have any apps installed on the SDCard while trying to mess around (with ROMs, I think), so I tried removing what I could, and then rebooting (and some folders respawned), and reapplying the fix—no dice. I've since replaced all of the folders and the files.
Stock rom here as well.
Hrmm not quite sure why lag fix isn't working for you guys. Just a quick question, in RyanZa One Click, is "Un-Root Device" green?
I still have no problems applying RyanZa Lag Fix to my Captivate as I had to redo it last night after i switched back to the Rogers stock rom after testing Cog 2.2. My guess, and it is just a guess, is that the root never applied properly. Have you tried rerooting the device?
deacfire said:
Hrmm not quite sure why lag fix isn't working for you guys. Just a quick question, in RyanZa One Click, is "Un-Root Device" green?
I still have no problems applying RyanZa Lag Fix to my Captivate as I had to redo it last night after i switched back to the Rogers stock rom after testing Cog 2.2. My guess, and it is just a guess, is that the root never applied properly. Have you tried rerooting the device?
Click to expand...
Click to collapse
Thought I might give you some info as well since i've been messing with mine for about a week now. I was able to root the device, oneclick did not work originally for this and I used ADB method similar to what you had here. After this I went for the lag fix, everything was green like it was supposed to be, installed the ext2 tools no problem and then get the same error about unable to mount when applying lag fix.
At this point I used OCLF to unroot the device and it did, I then used the oneclick to re-root which it did this time, in terminal I can su properly and again all the tools are green in OCLF. Tried to lagfix and failed again so I started making some changes manually based on the error messages that were out put. Created the folder it was trying to mount to for instance and then set the permission to this to 777 that would allow world write access, this allowed it to create the new partition in ext2 but when mounting the loopback device it fails saying it doesn't exist (which it doesn't I looked) so while I did get a bit further the lag fix still fails. I would gladly apply the lag fix manually through the terminal if I knew everything that was being done to re-format the partitions for ext3 but I can't seem to find that info anywhere.
Next best thing I would guess is to install a stock rom from rogers from someone else and see if there are any differences, I'm guessing based on the devices in the /dev folder that there are more then one image on the devices some set up more similar to AT&T that the lag fix will work on.
mrprefect said:
Thought I might give you some info as well since i've been messing with mine for about a week now. I was able to root the device, oneclick did not work originally for this and I used ADB method similar to what you had here. After this I went for the lag fix, everything was green like it was supposed to be, installed the ext2 tools no problem and then get the same error about unable to mount when applying lag fix.
At this point I used OCLF to unroot the device and it did, I then used the oneclick to re-root which it did this time, in terminal I can su properly and again all the tools are green in OCLF. Tried to lagfix and failed again so I started making some changes manually based on the error messages that were out put. Created the folder it was trying to mount to for instance and then set the permission to this to 777 that would allow world write access, this allowed it to create the new partition in ext2 but when mounting the loopback device it fails saying it doesn't exist (which it doesn't I looked) so while I did get a bit further the lag fix still fails. I would gladly apply the lag fix manually through the terminal if I knew everything that was being done to re-format the partitions for ext3 but I can't seem to find that info anywhere.
Next best thing I would guess is to install a stock rom from rogers from someone else and see if there are any differences, I'm guessing based on the devices in the /dev folder that there are more then one image on the devices some set up more similar to AT&T that the lag fix will work on.
Click to expand...
Click to collapse
Try the stock rom in the main Rogers Captivate forum. It is one i used to go from Cog 2.2 back to stock and it applied the root and lag fix without a hitch. Give it a try and let us know!
deacfire said:
Try the stock rom in the main Rogers Captivate forum. It is one i used to go from Cog 2.2 back to stock and it applied the root and lag fix without a hitch. Give it a try and let us know!
Click to expand...
Click to collapse
Happen to have a link right to the forum? so many threads to search through...
I'm new to the whole android thing though I've been working with linux for years but its a bit of a learning curve coming from a blackberry.
also what are you using to flash your device?
I'm having the same problem. Let me know if you somehow fix it.
Sent from my SAMSUNG-SGH-I896 using XDA App
I was finally able to get my last night.
Turns out my first root attempt was a failure. I had to unroot via an update.zip method as i did not have the permissions to remove the files from terminal.
Once unrooted i then did the update.zip method for the I897, and modified the script to look for I896 instead. It worked flawlessley. I am now getting the pop-up asking for root permissions. I had never seen it work previously.
I was then able to install OCLF without any problems. (and it popped up asking for root)
I am now rooted and lag fixed. Previous quadrant score was at 860's and i pulled a 2285 last night after the OCLF.
Can you please tell us how to modify script and how to flash back to stock..I need to return my phone and superuse app wont go away after unrooting and factory reset
inningsdefeat500 said:
Can you please tell us how to modify script and how to flash back to stock..I need to return my phone and superuser app wont go away after unrooting and factory reset
Click to expand...
Click to collapse
Well i cannot help you flash back to stock as i don't quite know how to do that yet myself. But i can help you unroot, re-root, and lag fix.
I have found the files again and uploaded them to rapid share with the necessary modifications.
Download THIS FILE and once downloaded, rename it to update.zip Be careful not to name it update.zip.zip by accident.
Place the file into the root of your sdcard.
Shutdown the phone with the power button, or pull the battery out and put it back in.
Enter recovery mode:
While holding the volume up and volume down buttons press and hold the power button until you see the white text that says SGH-I896, then release the power button only.
When in recovery mode use the volume down key to highlight reinstall packages, then press the power button. It should say completed and reboot the phone.
Once the phone has rebooted, do the exact same thing again, only use THIS FILE instead. Dont forget to rename the file again!
Then install the OCLF from market. Install the EXT2 tools first. Then run the lag fix installer.
I assume you already know how to enter recovery mode, but this way someone else searching for a fix will have all the info at their disposal here.
EDIT!!!
Some mirrors for the files
For the UN-Root files go HERE
For the ROOT files go HERE
Hi all i am very lost here....i have tried for hours the last few days on how to root this i896 with the super one click method with no luck....anyways i was speaking to my brother earlier and he has done it with his bell vibrant no problem....anyways what i want to know is what is the purpose of rootindg the phone? I thought it was for downloading 3rd party apps or whats the purpose for superuser? The reason why i am asking is that i can download 3rd party apps already...i allow them on my application settings and download a app downloader and works fine? Im lost someone please help.
Sent from my SAMSUNG-SGH-I896 using XDA App
dandroid123 said:
Hi all i am very lost here....i have tried for hours the last few days on how to root this i896 with the super one click method with no luck....anyways i was speaking to my brother earlier and he has done it with his bell vibrant no problem....anyways what i want to know is what is the purpose of rootindg the phone? I thought it was for downloading 3rd party apps or whats the purpose for superuser? The reason why i am asking is that i can download 3rd party apps already...i allow them on my application settings and download a app downloader and works fine? Im lost someone please help.
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
Take a look here. It answered alot of my questions.
http://www.androidcentral.com/rooting-it-me-some-qa
Also, if you only follow the second half of my post above you should be able to root it as well.
Thanks deacfire! The one click wouldn't work for me but the second method did.
I am having a really annoying problem though. The superuser.apk that you included just gave me a black screen. So I updated it to this one: http://forum.xda-developers.com/showthread.php?t=682828&highlight=no+apps+in+list
Which is newer. But now it just says "no apps in list". Tried installing it from the zip, tried from the market no different.
I do have apps that require superuser: ROM Manager, Root Explorer, Adfree. They all work, also have titanium backup but its is telling me it needs root access.
How can I fix this, it is a major issue.
EDIT:Thanks impulser91!! That work and was SUPER easy! Should probably get posted in the original post.
when i copy update.zip into the /sdcard and then try hitting reinstall packages, it results in an error and aborts. any suggestions?
Nevermind....it worked MUAHAHAHAHAHAH LET THE FUN BEGIN!
Sweet, 2 users. Not bad for under 10 posts
I'm glad its working for others. I had one heck of a time finding the right combination of files and process's for the I896. I am an IT professional and it took me a few days of fumbling around all the I896 and I897 posts.
Anyways, glad to hear it worked, and i hope other people find it useful as well. I will keep the originals, so if the links go down someone just PM me and i will load them somewhere else.
impulser91 said:
Well i cannot help you flash back to stock as i don't quite know how to do that yet myself. But i can help you unroot, re-root, and lag fix.
I have found the files again and uploaded them to rapid share with the necessary modifications.
Download and once downloaded, rename it to update.zip Be careful not to name it update.zip.zip by accident.
Place the file into the root of your sdcard.
Shutdown the phone with the power button, or pull the battery out and put it back in.
Enter recovery mode:
While holding the volume up and volume down buttons press and hold the power button until you see the white text that says SGH-I896, then release the power button only.
When in recovery mode use the volume down key to highlight reinstall packages, then press the power button. It should say completed and reboot the phone.
Once the phone has rebooted, do the exact same thing again, only use THIS FILE instead. Dont forget to rename the file again!
Then install the OCLF from market. Install the EXT2 tools first. Then run the lag fix installer.
I assume you already know how to enter recovery mode, but this way someone else searching for a fix will have all the info at their disposal here.
Click to expand...
Click to collapse
I could just about kiss you.... but I won't
Thanks for the update files they worked like a charm. I had a similar issue where the device didn't seem to be properly rooted, though it didn't give me any issues with most things when applying the lagfix it would die.
applied both your unroot and then root and it worked flawlessly the first time, lagfix then ran with no issues and my quadrant scores are 2250 now.
Not sure what you did exactly, I've tried rooting from update.zip from oneclick and neither worked I ended up rooting with the ADB and though it seemed to work it apparently did not.
Thanks again
i have a rooted droid x running the version above. i am not interested in running custom roms, i just want root so i can run whatever apps i want to. after rooting i downloaded wireless tether and the free version of titanium backup. wireless tether is my only means of connecting my computer to the internet. i ran a complete backup after downloading titanium backup. just messing around one day i removed cardock and blockbuster from the phone. i have restored blockbuster but can not get cardock restored. my phone has downloaded the latest ota update and wants me to install it. from what i have read, i will need cardock restored. is this correct and if so how can i get it back? i am fairly good with a puter but new to android. i rooted using doroot for windows. all help is much appreciated.
maneddi said:
i have a rooted droid x running the version above. i am not interested in running custom roms, i just want root so i can run whatever apps i want to. after rooting i downloaded wireless tether and the free version of titanium backup. wireless tether is my only means of connecting my computer to the internet. i ran a complete backup after downloading titanium backup. just messing around one day i removed cardock and blockbuster from the phone. i have restored blockbuster but can not get cardock restored. my phone has downloaded the latest ota update and wants me to install it. from what i have read, i will need cardock restored. is this correct and if so how can i get it back? i am fairly good with a puter but new to android. i rooted using doroot for windows. all help is much appreciated.
Click to expand...
Click to collapse
2.3.15 is soooo yesterday
look into some deblured Rom's. Easier to get rid of the Crapware with a Rom than one at a time. that could cause other issue.
IMHO there are easier tools to root like 4Zroot.
Your heading in the correct direction keep on reading the threads and different sites.
please read my post again. i am not interested in roms.
Stock apks
www . chadhaney . com / droidXDefault / ( wont allow me to post links) but go there...
Let me know what happens... I'm in the same boat. No roms, just titanium back up and wireless tether ( which I never use ) Titanium Pro allows you to freeze apps so they dont run and you dont have to delete them.
P
According to droid x forums, if your rooted, and have all the original apk/apps on the phone you should be able to update to 2.3.34. Make sure that every setting is stock too. No frozen apps, etc... You will lose root. Then they recommend Z4root to re-root.
Successful install
I was running 2.3.15 rooted, no leak, installed 2.3.34 OTA with no problems.
I used Z4Root 1.3 to re-root my droid x. If you were previously rooted you should select the unroot option from Z4Root first. Phone will restart and then select permanent root. Should be good to go after that...
I did it the hard way... wish I had un-rooted first!
Thanks for helping eyepopper. I downloaded the apk file but it would not install. I assume I need to move it manually but don't know where it goes. The odex file opened when I selected it and looks like code. Not sure how to get it where I need it either. I am using astro for my files.
Sent from my DROIDX using XDA App
Are you using the phones browser? Try going the chad website thru the phones browser (I use dolphin browser) download it to the phone. Then run the apk thru the browser, go one step further and make sure that you checked off to allow other non market apps to run in applications. Astro app is the problem most likely.
i am using the stock browser but the page just reloads when i select the apk file and opens a window showing gibberish when i select the odex file. i have the 2 files on my sd card under titanium backup and was able to copy and paste them from /sd/titanium backup to /sd but i can't get them to copy and paste to the system folder or the framework folder. as soon as i leave /sd the paste function grays out. looks like your are the only one willing to help me and i am very grateful for it. i need to go on and get this done and be thru with it so i can enjoy the holidays. can you meet me in a chat somewhere and see if we can get this done? pm me ur info if you can. thanks again...
maneddi said:
hi, i was wondering if you could look at my post concerning updating to the latest ota. (it's in the general droid x section) i have the files but can't get them off my sd card onto the phone.
Click to expand...
Click to collapse
Ok you will need to connect your phone to your computer. Open a command prompt and type the following commands:
*make sure your phone's usb mode is Charge Only
1) type: Adb devices (make sure your phone gets listed as a device)
2) type: adb shell (press enter)
3) type: su (press enter)
4) type: mount -o rw,remount /dev/block/mtdblock 4 /system
I'm not sure where you have the cardock.apk on your sdcard, but this next step will require you to know the path to your .apk
5) type: cp /mnt/sdcard/<path to CarDock.apk> /system/app/CarDock/apk
if just on the sdcard then it would be "cp /mnt/sdcard/CarDock.apk /system/app/CarDock.apk
6) type: cd /system/app
7) type: chmod 644 CarDock.apk
8) type: exit
you may need to type exit one more time, but when you return to a normal command prompt, type the following:
adb reboot.
Make sure to take a backup before you do any of this, as if you mess anything up in /system your phone can wind up hosed....
Hope this helps. As a last resort, you could always take a backup of your phone, and then perform the 2.3.15 full sbf and restore the apps that way (make sure to perform a factory reset as well. Then you would be able to perform the OTA update and shouldn't have any problems.
Hope this helps! Lemme know if you need more help.
You can also refer to this link if you want more info...
http://androidforums.com/droid-x-al...w-reinstall-system-apps-_as_-system-apps.html
great post SysAdmin-X, thanks. i haven't used adb manually before but i know if your not careful 1 little missed space or wrong key stroke will mess you up so i opted to go with the post you provided a link for.
i downloaded root explorer and was able to move my files successfully from my sd card to the system apps folder but could not get them to show up afterwards in titanium backup. i figured since they were files i manually removed from tb they were prolly named wrong so to be right i went to this link and downloaded the entire zip. i was then able to place those 2 files in the /system/app folder and after rebooting they showed up in tb. finally...yea!!! ok, i remember reading somewhere they needed to be in the /system/framework folder as well. does anyone know if this is fact? if the update looks for them there and doesn't find them it won't install correctly or at all, so i'm told.
maneddi said:
great post SysAdmin-X, thanks. i haven't used adb manually before but i know if your not careful 1 little missed space or wrong key stroke will mess you up so i opted to go with the post you provided a link for.
i downloaded root explorer and was able to move my files successfully from my sd card to the system apps folder but could not get them to show up afterwards in titanium backup. i figured since they were files i manually removed from tb they were prolly named wrong so to be right i went to this link and downloaded the entire zip. i was then able to place those 2 files in the /system/app folder and after rebooting they showed up in tb. finally...yea!!! ok, i remember reading somewhere they needed to be in the /system/framework folder as well. does anyone know if this is fact? if the update looks for them there and doesn't find them it won't install correctly or at all, so i'm told.
Click to expand...
Click to collapse
possibly with Root Explorer tool you could change the permissions of the moved apps to rwrr.
this way you phone can see them and use them.
Kdinc is right about changing the permissions using root explorer. Make sure to set the as user: read and write, group: read, and other: read. Should look like this after: rw-r--r--
Sent from my DROIDX using XDA App
Hi,
If your like me and you have had some problems with android market on your Kindle Fire (yes,I got one for christmas and its already rooted ) by following a guide with Vending.apk and though you can browse the market, it is stuck on Starting Download, I have found a solution to the problem... All you need to do is get a new file:bit.ly/tlWjSn
This file is simply an updated version to the Vendor.apk other tutorials provide.
All you do is the following(presuming you have rooted, got root explorer and GO launcher):
1.Copy the file to kindle at an easy to access location.
2.Long-Hold the file and tap move.
3.Navigate to / then system then app.
4.Set it to R/W mount (top left)
5.Paste the file.
6.Set the permissions like all other files(tick first 2 in first row, first 1 in second row and first 1 in third row then tap ok)
7.Reboot the device
8.Go onto GO launcher and add it to the screen (tap the list thing bottom middle of the screen,then tap Add. then select Application followed by Market)
9.Done! Enjoy!
Not sure if I should start a new thread or not.
I'm rooted and have SU. I have confirmed this by running Titainium Backup.
Market stopped working after the latest Kindle update. After I re-rooted, I tried re-installing vender.apk, but it still crashes upon launching it. Also, I am running Go Launcher EX.
When I browse folders while connected to a computer (using Win7), the system folder is hidden.
I never installed Root Explorer on the Fire. Is there a way for me to download and install it directly, or will I need to side load it? I assume if it's in the Market I'll need to side load.
leebo said:
Not sure if I should start a new thread or not.
I'm rooted and have SU. I have confirmed this by running Titainium Backup.
Market stopped working after the latest Kindle update. After I re-rooted, I tried re-installing vender.apk, but it still crashes upon launching it. Also, I am running Go Launcher EX.
When I browse folders while connected to a computer (using Win7), the system folder is hidden.
I never installed Root Explorer on the Fire. Is there a way for me to download and install it directly, or will I need to side load it? I assume if it's in the Market I'll need to side load.
Click to expand...
Click to collapse
Unfortunately you will as far as I know, but for $3.99, it is VERY useful when rooting or installing app's. market.android.com/details?id=com.speedsoftware.rootexplorer&hl=en
Check it out. If you run into anymore problems feel free to PM me as it's easier
Hello guys, I have a little question related to market app that maybe has been already answered so I won't start a new thread.
I have my KF with 6.2.1 rooted and with the full android market installed (EX launcher and so on).
Usually the market works fine, but I always get errors ( process com.android.vending has stopped unexpectedly) and consequent force closes even if I can download stuff and apps. Basically, it happens whenever the market takes an action.
Is it a known issue or ir it "normal" ?
Thank you all in advance.
For me, I am having problems copying the Vending.apk to /system/app folder. I follow the steps in that tutorial but when I paste the.apk in the folder nothing happens. Help??
Got it rooted last night, and I'm using file expert since my cheap ass doesn't want to buy root explorer.
sengokubattosai said:
For me, I am having problems copying the Vending.apk to /system/app folder. I follow the steps in that tutorial but when I paste the.apk in the folder nothing happens. Help??
Got it rooted last night, and I'm using file expert since my cheap ass doesn't want to buy root explorer.
Click to expand...
Click to collapse
I'm afraid that without Root Explorer you can't change the /system/app folder permissions from R/O to R/W, therefore you can't paste anything in that folder.
Chiwaz said:
I'm afraid that without Root Explorer you can't change the /system/app folder permissions from R/O to R/W, therefore you can't paste anything in that folder.
Click to expand...
Click to collapse
File expert gives you that option too though.
if ur rooted but it wont paste or read and write in root explorer then ur su wasnt pushed properly in ur root process! When i rooted my kindle i deleted my old su and did the whole root process from scratch when i got the new root process. The whole thing went smooth and su showed up in apps when done but it wasnt totally rooted as i couldnt read or write in root explorer. Jcase told me that when the adb command for pushing the su wasnt done right thats what happens. he fixed it for me, great guy.
that was me though
THIS METHOD IS NO LONGER WORKS as of update version 2.0.5 and higher.
Please visit this thread instead for the current rooting method.
Posting in this thread will get you nowhere, let it RIP.
ANNOUNCEMENT:
If you have a new Nook HD/HD+ and want to root and get the GAPPS running, you should follow the guide at the All-in-One thread instead. That said, I won't copy all the information here to there, so you should continue to read on.
Let me start by saying that I didn't come up with the working root method. The original root instruction came from verygreen in this thread. And I am not a developer, I merely have a few linux background and even less so in the Android. I worked on this on my spare time by myself.
I merely take what was working, but unusable to make it usable. I found something that he is missed. This may actually be working on Nook HD (non-plus) also, but since I don't own one I can't say that it will.
Disclaimer:
If something gone wrong, it's all your fault. I take ZERO responsibility for what happen to your device, your life, your wife/husband, your kids, your unborn child and etc. You get the idea.
Background:
When I found out the root doesn't actually work past a reboot, I start looking what actually cause the Nook to be pissed and factory reset itself. Well, it seem that the /system and anything in there is basically coming from a /dev/block/mmcblk0p8 And if something got change, Nook get pissed and do a FULL FACTORY RESET(I'll explain in a moment). Well, at least I start investigated under that idea.
What I found:
What I found, or at least what I think I found is that, probably just adding file, or increase in the size(maybe there is a threshold for this), will cause it to do a full factory reset. What I also found is that there is a $PATH for /system/sbin but not pointing to anywhere. So I come up with the idea of making another ext4 file system in a file and loop mount it to /system/sbin I guess that work(very well). What I also found is that, there are two kind of factory resets. The one that you perform yourself, which is actually not a full factory reset and the one that Nook get pissed and do the full one.
A factory reset that you perform yourself, whether from the GUI or button combination will basically clean the partition /data while a full blown one will basically restore other partition such as /system
What is included:
basically a zip file, inside that zip file are 6 files.
boot_complete_hook.sh.bak this is basically a modified version of verygreen's
busybox & su are basically from his thread
superuser.apk well I found this one floating around and seem like a good idea to stick it in there (not even sure if it gonna work w/ Nook)
makeroot.bat this is basically what do most of the work. It's base on verygreen original rooting instruction.
sbin_mount This is basically an ext4 file system which have su and another version of busybox all setup nice and tidy for you all. This version of busybox is 1.20.2r2 which I grabbed from here.
Prerequisite:
ADB, it's your responsibility to have adb up and running, meaning not just have it install, but it can see your nook also.
leapinlar wrote a post to help you getting ADB to work here.
Now to get root:
all you have to do is unzip it and run makeroot.bat (obviously you run this in windows command prompt). Yub that's all. The batch file will do the rest, including reboot the nook and wait for it to reboot and stuff. Won't make a coffee for you though.
The manual and hard way:
well, I will only explain this in a summarize way. Basically this start with verygreen rooting method. It basically take advantage of the exploit and run /data/boot_complete_hook.sh which you adb push yourself(with correct permission) with root privilege. What you can run in there is basically up to your creativity. So obviously in this case, you mount the sbin_mount as an ext4 filesystem in the /system/sbin You can make this file yourself if you want to, in linux using dd and mkfs command. Basically using dd to create a file volume to the size you want and mkfs to format it to ext4. Mount it and start uploading stuff you want in there. You will have to correct all the file permission as well. Since all of this will be mounted to /system/sbin you should be aware what you gonna put in there. I guess I could make this thing 100MB, but for this specific purpose 10MB is enough. I my case, just the su and busybox and the symbolic links for the busybox. I'm doing this for the long term. I'm too lazy to point to busybox everytime I wanna do something.
What to do afterward:
Now that you have root, you can Enable Unknown Source to allow you to install app from within the device and install GAPPS. Follow the two guides below if you interested.
Enable Unknown Source: Again, I make an easy little tool for you here.
GAPPS: here.
Did I missed something:
Well, as I said I'm no coder so if I didn't do a clean job, you can refine it. If I didn't document or give proper credit, then I guess I missed that. Sorry about that, again I'm no coder and never done this. And finally:
If this thing work for you, feel free to hit that "THANKS" button. I spent many hours trying to come up with this solution.
FAQ:
Q: My so and so application when attempting to have root access get freeze up, or superuser doesn't work?
A: Well, I'm not sure if this is dued to how the Nook side-loading work or not, but it seem for some reason superuser won't start by itself. So you have to start it manually the first time.
Q: I type in "adb root" and I can't get in as root, it doesn't work?
A: yes it does, it's just not working with adb root. You can get in via "adb shell" once you get in, type in "su" and you can see that you now should have root access.
Thank you so much! This works perfectly. Survives reboot.
here's the Linux version.
Thanks someone0 for getting this started.
Haven't fully tested the linux version, but it loads and starts up, so should work.
extract, and open up terminal and navigate to the dir you extracted to, and type
./makeroot.sh and then enter.
This sounds like a good idea initially.
It is true that the B&N does not just check for /system/xbin/su directly like they did in the past.
This time they check for something else and I just had no time to look into it more deeply to find out what is it they are actually checking for. I plan to figure this out on Friday when I am back home.
Also wanted to tell you that having Linux background is a great thing when tinkering with Android (at a low level, anyway). I don't have much Android background to speak of as well.
This works really well, and thanks to Someone (and mad props too) for getting persistent root working on this.
I may be being very naive, but my suspicion on the reboot is around the manifest file that's present at root.
It seems to be generated by the boot process and it might provide a quick and dirty list of what's permitted on the device to check. With persistent root, lots of investigation becomes a lot less painful. I expect that by end of day we'll have install unsigned running.
Early in my experimenting with the HD+, I noted:
- some versions of the Google Services Framework can be installed via adb
- when I launched the native calendar app after installing gsf, it wanted to sync to a google account, and was able to add the google account
- one version of the Play store installed and launched as far as throwing the 'you must accept the terms of service' before crashing
What BN most likely does is calculating the hash value (or digest, if you prefer) of certain system files that they think shouldn't be tampered with, then during reboot, the values of these files must match, or they will do a factory reset.
The key point is to find out where they do these checks and fool the check.
This sound simple but it depends on how they implement it. If they use binary decisions (like if the hash_value == calculated), then it is easy to get around. If not (e.g. using white box algorithm to hide keys), then it get more complicated.
excellent and very elegant solution. Kudos!
I'm heading out to work, and if you think your theory is right, try poking around with it. Now that your have root, you can try to dd those bootloading partitions out to user area and upload them out to PC and inspect them.
looking at the vold.fstab
Code:
xloader -> /dev/block/mmcblk0p1
bootloader -> /dev/block/mmcblk0p2
recovery -> /dev/block/mmcblk0p3
boot -> /dev/block/mmcblk0p4
rom -> /dev/block/mmcblk0p5
bootdata -> /dev/block/mmcblk0p6
factory -> /dev/block/mmcblk0p7
system -> /dev/block/mmcblk0p8
cache -> /dev/block/mmcblk0p9
userdata -> /dev/block/mmcblk0p10
Be extra careful when touching those partition if you not sure, don't touch them. But making a block copy of them and taking them out should be relatively easy and safe. Obviously you gonna need a Linux box to do this. I setup a VM on one of my PC last night because I need to get a ext4 partition and put all the goodies in there.
krylon360 said:
here's the Linux version.
Thanks someone0 for getting this started.
Haven't fully tested the linux version, but it loads and starts up, so should work.
extract, and open up terminal and navigate to the dir you extracted to, and type
./makeroot.sh and then enter.
Click to expand...
Click to collapse
Just wonder why do use a zip file for the linux version? Wouldn't this kinda messup the permission when compress/uncompress? meaning, makeroot.sh may not have the proper permission when unzip. Please double check.
someone0 said:
Just wonder why do use a zip file for the linux version? Wouldn't this kinda messup the permission when compress/uncompress? meaning, makeroot.sh may not have the proper permission when unzip. Please double check.
Click to expand...
Click to collapse
works just fine.
I chmod a+x'd the script before putting it into the zip.
heh, yeah, it works. Forgot I had my touchpad pluged in and it rebooted it....
whoops.
thanks for posting the location of the /recovery partition. I want to put a copy of htat on ice to prevent BN from undoing any of my work in a future update - I may want some of the fixes they have, but I want to be able to roll them back if needed.
Someone0 are you around can you pm me, Your root works, I installed nook color tools ver .02 in system/app folder and was able to see it in my sideloaded launcher, was able to uncheck/check install non market apps which sets the setting for US to be able to install .apk files from the nook itself, ONLY ISSUE is since I put that file in the system/app folder and the nook didnt like it I got stuck in a bootloop and get to start this process all over again! (nook resetted to ground zero)
maybe we temporary can leave it there get us the permission to install non market apps then remove the file and we will be ok or maybe stuck in another bootloop.
---------- Post added at 09:20 PM ---------- Previous post was at 08:52 PM ----------
GOT IT WORKING NOW:
1. Once rooted, get a file manager with root support and enable read/write permission to /system
2. temporary copy nook tools ver .02 .apk to the system/app folder
3. have a sideloaded launcher and check the app drawer youll see nook tools, run it, first screen uncheck and check the install non market apps box couple of times make sure its checked afterwards
4. have a test .apk to run the BN installer on and see you can now install .apks from the NOOK HD and HD+
5. remove the nook tools.apk file from the system/app folder and quit your file explorer which should reset everything for the system folder back to the way it orginally is!
6. reboot, if you reboot successfully with no boot loop 8 times, your GOLDEN FOR NOW! once again load up a file manager go select an .apk file and see you can now install it! Next step is trying to get amazon market working! then google somehow, but for google you need files in system/app folder permanently!
7. YOU CAN NOW SUCCESSFULLY DOWNLOAD .APK FILES through web, email, any other app and install through the NOOK HD or HD+ BN installer for .apk files. Watch what you install, if it gets put into /system or /system/app folder DREADED BOOT LOOP which resets everything! AMAZON MARKET WORKS!!!! and apps from there install fine to the BUILT IN MEMORY.
** Hopefully amazon market dont install stuff to the system/app folder and if it does hopefully you do not get the dreaded boot loops where you got to start this whole process over again so be forwarned!!! you will loose all data on NOOK HD and HD+ if u get stuck in the bootloops! BACKUP STUFF before messing with root and this kind of thing! DEVELOPMENT!
Aside from moving the actual apk to /system/app/ temporary (since you only do it once), putting a symbolic link there may work also without creating a reset loop. But can't you just side load the apk and run it in other folder?
someone0 said:
Aside from moving the actual apk to /system/app/ temporary (since you only do it once), putting a symbolic link there may work also without creating a reset loop. But can't you just side load the apk and run it in other folder?
Click to expand...
Click to collapse
when you sidelaod it OR install or have it installed to another folder or ran from another folder it cant modify the setting to allow non market apps to install!!
has to be in the /system/app folder THEN RAN from app drawer then you can set the setting uncheck and check box quit program and for now YOU HAVE to remove the .apk from the system/app folder and then you can reboot and the setting sticks! I GOT AMAZON MARKET INSTALLED right now installing apps! NOW WE GOT A KINDLE ladys and gentleman!
Amazon apk installs in internal memory. Apps downloaded from Amazon get installed in internal memory. You can then move them to SD card or leave them in internal memory. System apps are provided in the ROMs by the developers or vendors. ALWAYS back up before making system changes.. Now rooted - use Titanium Backup. System/app should be static throughout ROM lifecycle unless modified by user.
skyhawk21 said:
7. YOU CAN NOW SUCCESSFULLY DOWNLOAD .APK FILES through web, email, any other app and install through the NOOK HD or HD+ BN installer for .apk files. Watch what you install, if it gets put into /system or /system/app folder DREADED BOOT LOOP which resets everything! AMAZON MARKET WORKS!!!! and apps from there install fine to the BUILT IN MEMORY.
** Hopefully amazon market dont install stuff to the system/app folder and if it does hopefully you do not get the dreaded boot loops where you got to start this whole process over again so be forwarned!!! you will loose all data on NOOK HD and HD+ if u get stuck in the bootloops! BACKUP STUFF before messing with root and this kind of thing! DEVELOPMENT!
Click to expand...
Click to collapse
This is why I put the /system back to ro, at least that is what I think I did.
Amazon Store working on ROOTED Nook HD
Proof of Concept:
http://youtu.be/wCyd730L74Y
skyhawk21 said:
Proof of Concept:
http://youtu.be/wCyd730L74Y
Click to expand...
Click to collapse
LOL, your internet is slow. Could have cut the video time by 1/2 if not 2/3 if you switch to faster ISP.
skyhawk21 said:
Someone0 are you around can you pm me, Your root works, I installed nook color tools ver .02 in system/app folder
Click to expand...
Click to collapse
What exactly did you install? I cannot find "nook color tools" in Google Play or on APKTOP. Thanks for your hard work!
NEVERMIND! I found the thread that has the link for the app: http://forum.xda-developers.com/showthread.php?t=868366 Thanks again.
does this root method work on Nook HD+2.0.2?
if not how I can downgrade to 2.0.0?