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
So, I wanted to delete my google account in the first place. I found this tutorial with video. It says:
Basically this was done on a rooted phone. We used the program called Root Explorer and navigated to /system/framework. Make sure that is mounted r/w and not r/o (read write vs read only). Rename framework-res.apk > framework-res.apk.bak. You might get an error after this (force close). Just go ahead and force close it. Immediately rename it back to framework-res.apk. Reboot and you're done. Enter your new main Google account.
Click to expand...
Click to collapse
I rooted the phone using the Galaxy S II Root Guide on this forum. I put the XWKDD_insecure.tar on my phone, succesfully. After reboot i rooted the the phone using SuperOneClick. Everything went fine, it asked me if i wanted BusyBox > clicked 'Yes'.
I rebooted my phone, left it in USB Debugging (you never know what happens). I launched the application Root Explorer (v2.14.2) > some message asked me if i allowed the app acces to my root > clicked yes.
So, Root Explorer launched, i navigated to /system/framework and clicked "mount R/W" (read/write). I renamed framework-res.apk to framework-res.apk.bak. TROUBLE STARTS HERE
All kind of processes started to crash and asked me to do forced close the tutorial says this can happen, so i force closed. But the errors kept popping up, and i kept clicking force close. In the end there were 3(i guess) processes which continiously kept crashing one-after-another.
The proces system crashed also, so the creen was black. I was able to slide the top bar (system tray?), the icon of my advanced task killer was there so I tried to launch that but it crashed too. So I gave up, and long pressed the powerbutton.
Big trouble
I tried to reboot, the samsung galaxy s II launch image appeared. That's it.. nothing left. After a lovely cursing-session i put on the KE2 original kernel. (again, just like the root guide says) Rebooted but it's still stuck at the launch image.
Kernel version:
2.6.35.7-I910XWKE2-CL187606
[email protected] #2
I've got this phone handed by the mailman 24hours ago, and i really really want to get this fixed. Whoever helps me to get my phone working again will get a reward, I'm really desperate.
Anymore information needed? Leave a reply plz
Just go into download mode and flash again with whatever rom you want (FULL ROM not just kernel). Should be fine I would think as /system is not essential (well, for to use it as a phone/pda yes) but not for flashing again. Should be fine then.
Although i'm new to the flashing stuff, i understand what you mean. I'm going to find a full rom and download it to my phone, and be back asap
Thanks already!
Phone works again
deanwray, if you have an paypal accoun you may PM your details to me. As i've said:
Whoever helps me to get my phone working again will get a reward, I'm really desperate.
Click to expand...
Click to collapse
I guess answering my question was almost easier then picking your nose still i want to thank you
I do have a paypal account, but to anyone who would want paying for simple advice, I would have little respect for and even less so for myself, just press the thanks button in xda, im more glad that your sorted than nething else
Sent from my GT-I9100 using XDA Premium App
Understood, i already pressed the thanks button.
@Admins: If needed, this topic may be closed now.
I too did rename framework-res.apk and bricked my Kindle fire; need help
I too did the same dumb thing.
I already rooted my kindle fire, downloaded android market I loggedin using a google account. After that I was unable to change the google account. Browsed web and I saw the post of the video. I followed the instructions in the video.
steps followed: using root explorer, went to /system/framework and renamed framework-res.apk and and after I completed the renaming, the device crashed (or I clicked something; hence crashed?) and stuck in blank carrousel page.
So, I rebooted and all I get now if boot logo of 'Kindle fire'. It doesnt go any forward.
I connected to PC and I am able to see the device in ADB. But no root access in shell. So, any adb command I give I get back errors like: no permission; read-only folder, etc.
When I use the Kindle fire utility v0.9.3 and try to do temp root or root, I get
Error type 2 android.util.AndroidException: Can't connect to activity manager; is the system running?
adbd cannot run as root in production builds
PC detects the device as 'Android Composite ADB interface'. But cant do anything in adb. I can push files to /data/local/tmp folder. Thats about it.
when I do
adb shell mv /system/framework/framework-res.apk.bak /system/framework/framework-res.apk
I get:
failed on '/system/framework/framework-res.apk.bak' - Read-only file system
Can someone help rename this file back to original framework-res.apk?
Thank you very much;
I know some international versions of the S7 have the data toggle in their drag down. Obviously AT&T HAS to remove it to inconvenience their customers......
How do we go about putting it back in? Would it be something like it was on the S5? (see here - http://forum.xda-developers.com/showthread.php?t=2721550)
Currently at work, but I'll be taking a look at this once I'm home.
---
edit - looks like I've found something from a German forum!! http://www.android-hilfe.de/thema/r...ixperience-s7-port-stable-v3-1.759967/page-33
I'm testing this now, hopefully my phone reboots
edit 2 - failure. Maybe someone else can see where I went wrong?
*DISCLOSURE - only follow the below if you are comfortable with messing up your phone. I will not be reliable for your damaged phone, if something does go wrong*
Based on the thread I found in German above, you have to edit "sysui_qs_tiles". For some reason, SQLite Editor cannot find that file, but Settings Database Editor(SDE) by 4A does.
Once SDE has been installed, head to secure, and scroll down until you see "sysui_qs_tiles"(see attached screenshot). When you click to edit it, you'll get a permissions error.
To stop the permissions error, plug phone into computer, open where your ADB is installed, then open an Administrator command prompt there. (start-> type "cmd" -> right click and select administrator, then type "cd c:\adb", or where your ADB is stored) You should do "adb devices" and then see your devices. If you do, paste this "adb shell pm grant by4a.setedit android.permission.WRITE_SECURE_SETTINGS". The next time you click on "sysui_qs_tiles", you'll be able to edit it.
The German thread says to reference this:
Wifi,Location,SilentMode,RotationLock,Bluetooth,MobileData,PowerSaving,AirplaneMode,DormantMode,Flashlight,UltraPowerSaving,WifiHotspot,PersonalMode,AllShareCast,Sync,Aod,SFinder,ScreenCapture
Click to expand...
Click to collapse
I tried inserting MobileData, but when I restart, there is no new MobileData tile (the MobileData addition stays in the "sysui_qs_tiles" though).
Any thoughts?
edit 3 - tried it one more time, and I added the screenshot tile!! Looks promising, but we would need to find the name for the mobiledata tile.
Delete
I am on PK1 and after flashing engboot i didnt like the way my phone ran so I flashed AP file of PK1 and now suddenly I have data toggle. I never even rooted with engboot or did any other adjustments to try and get the toggle.
I rooted my tablet by using king root but I don't know what to do for android. Can someone tell me how to do that. I'm in the latest version and using windows computer
Practically said:
I rooted my tablet by using king root but I don't know what to do for android. Can someone tell me how to do that. I'm in the latest version and using windows computer
Click to expand...
Click to collapse
Wait - I responded to a PM and directed you to the appropriate thread. Please check your mail and proceed accordingly. The HDX forums have a wealth of information that should allow you to unlock your device and install a custom ROM with minimal effort.
Thanks for answer @Davey126 I red your mail but I still have some questions. I bought this tablet yesterday and this is my very first Android experience. I got how to root and unlock my device but I don't know the rest I mean is there any thread for very beginners ?
Practically said:
Thanks for answer @Davey126 I red your mail but I still have some questions. I bought this tablet yesterday and this is my very first Android experience. I got how to root and unlock my device but I don't know the rest I mean is there any thread for very beginners ?
Click to expand...
Click to collapse
If your device is currently unlocked you should be able to launch a custom recovery environment called TWRP. That's where most device maintenance is performed such as installing different versions of 'android' otherwise known as custom ROMs. Try this:
- power off device
- press and hold <power>+<vol-up> until Kindle Fire logo appears
- immediatlely release power button followed by volume 1-2 seconds later
- wait a few more seconds for next screen to appear
- what happens?
To exit recovery mode long press power until device shuts off. A short press will start the device normally.
Your response will determine next steps. If TWRP is present you're just a few steps away from installing a custom ROM. If stock Amazon recovery appears (just two options) then there is more work to be done.
Davey126 said:
If your device is currently unlocked you should be able to launch a custom recovery environment called TWRP. That's where most device maintenance is performed such as installing different versions of 'android' otherwise known as custom ROMs. Try this:
- power off device
- press and hold <power>+<vol-up> until Kindle Fire logo appears
- immediatlely release power button followed by volume 1-2 seconds later
- wait a few more seconds for next screen to appear
- what happens?
To exit recovery mode long press power until device shuts off. A short press will start the device normally.
Your response will determine next steps. If TWRP is present you're just a few steps away from installing a custom ROM. If stock Amazon recovery appears (just two options) then there is more work to be done.
Click to expand...
Click to collapse
I dont get this mean
Run:
Code:
adb shell
su
dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot
how can i run this
Practically said:
I dont get this mean
Run:
Code:
adb shell
su
dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot
how can i run this
Click to expand...
Click to collapse
I'm stuck at waiting for any device screen and there is fastboot text on my tablet
Practically said:
I dont get this mean
Run:
Code:
adb shell
su
dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot
how can i run this
Click to expand...
Click to collapse
In Windows Dos prompt
Practically said:
I'm stuck at waiting for any device screen and there is fastboot text on my tablet
Click to expand...
Click to collapse
Your driver not installed properly. Pls just follow my thread tips.
@kkcheong sorry for bother you just to clarify my situation. I rooted my tablet and spent 8 hours yesterday to unlock it but couldn't. First of all code_generator.bat works fine it creates unlock.code file. however When i apply the unlock bat I got an error on my tablet screen which says unlock code is not correct. Can you help me about what to do by explaining to very very very noob person. Another issue is i cant copy the 2 files to root folder i tried es browser and root browser.
1. I think your ADB driver not properly install. Check your Hardware Device in your windows for ADB. If no such ADB in your Hardware means you have install ADB properly
2. You cannot copy to root? You maybe need to enable R/W with root explorer or es explorer root.
Practically said:
@kkcheong sorry for bother you just to clarify my situation. I rooted my tablet and spent 8 hours yesterday to unlock it but couldn't. First of all code_generator.bat works fine it creates unlock.code file. however When i apply the unlock bat I got an error on my tablet screen which says unlock code is not correct. Can you help me about what to do by explaining to very very very noob person. Another issue is i cant copy the 2 files to root folder i tried es browser and root browser.
Click to expand...
Click to collapse
Practically said:
@kkcheong sorry for bother you just to clarify my situation. I rooted my tablet and spent 8 hours yesterday to unlock it but couldn't. First of all code_generator.bat works fine it creates unlock.code file. however When i apply the unlock bat I got an error on my tablet screen which says unlock code is not correct. Can you help me about what to do by explaining to very very very noob person. Another issue is i cant copy the 2 files to root folder i tried es browser and root browser.
Click to expand...
Click to collapse
Suspect vulnerable bootloader (and cubed TWRP) have not been installed as outlined in step #2 of the unlock thread OP.
I can transfer the two file to root folder. Now what should I do. Sorry for long questions but I have limited opportunity for using a computer since I don't have. I use friend of mine's. I want to make sure I got every step correctly. In the post I can do generate code thing. I successfully generate unlock.code file but the whe I write adb shell in cmd I got error something like adb is not recognised. Do you have any idea of any script file that do these things automatically.
So
Step 1 Done
Two files was copied to root folder
But stuck at code thing. Btw I don't have any driver issue since I can enable fastboot and get Unock code is wrong error
Practically said:
I can transfer the two file to root folder. Now what should I do. Sorry for long questions but I have limited opportunity for using a computer since I don't have. I use friend of mine's. I want to make sure I got every step correctly. In the post I can do generate code thing. I successfully generate unlock.code file but the whe I write adb shell in cmd I got error something like adb is not recognised. Do you have any idea of any script file that do these things automatically.
So
Step 1 Done
Two files was copied to root folder
But stuck at code thing. Btw I don't have any driver issue since I can enable fastboot and get Unock code is wrong error
Click to expand...
Click to collapse
You need to access the device via adb to issue the commands listed in step #2 of the unlock post:
- boot into FireOS and unlock device
- enable USB debugging from the FireOS settings menu (Google if you need help finding it)
- tether device; you may get an authorization prompt on device (look for it)
- there may be a notification indicating device is connected in 'charge mode'; switch it to 'file transfer' also known as 'MTP'
- open a Windows command prompt and navigate to folder where adb/fastboot commands live
- issue commands referenced in above post
If the host you are using does have (or you can't find) adb/fastboot installing the following package may be beneficial: https://forum.xda-developers.com/showpost.php?p=42407269&postcount=1