Database Users

Step by Step for Rooting Rogers Captivate (I896)

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

[Q] Root after OTA

Has anyone gotten their fascinate rooted after the OTA Update? I uses to use z4Root but.this is no longer working. It goes rhough the steps but none of the root apps can get super uswr access. I prefer one touch as I dont feel comfotable typing in all the commads for it to be hooked up to the pc

Dirrk's EZ Root v0.2
I was able to edit the START_ROOT.bat file in Dirrk's EZ Root v0.2 so the it would pause for 120 seconds instead of 60 seconds after the first phone reboot. Then, after the reboot, unplug the USB from the phone and reconnect it. I'm not sure if this will work for everyone, but it worked for me.

Roblovesbox said:
Has anyone gotten their fascinate rooted after the OTA Update? I uses to use z4Root but.this is no longer working. It goes rhough the steps but none of the root apps can get super uswr access. I prefer one touch as I dont feel comfotable typing in all the commads for it to be hooked up to the pc
Click to expand...
Click to collapse
there is a 1 click guide on i believe android central that is very easy. all you do is plug in your phone to a cpu download the .zip and open a file, then leave your phone alone for about 5 minutes and its done. it worked for me when z4 failed.. that was the first time i used anything other than z4 and was a little concerned but it was as easy as z4.. if not easier seeing as that z4 caused my phone to lock up a few times while it was in the process
EDIT: Here is the link.. you will need to register at android central to get the file but its very easy.
http://forum.androidcentral.com/fascinate-roms-hacks/33899-how-root.html

Powell730 said:
there is a 1 click guide on i believe android central that is very easy. all you do is plug in your phone to a cpu download the .zip and open a file, then leave your phone alone for about 5 minutes and its done. it worked for me when z4 failed.. that was the first time i used anything other than z4 and was a little concerned but it was as easy as z4.. if not easier seeing as that z4 caused my phone to lock up a few times while it was in the process
EDIT: Here is the link.. you will need to register at android central to get the file but its very easy.
Click to expand...
Click to collapse
This worked! I did do two things as it would error in the beginning. I changed the pause time in the file on the reboot to 120 seconds instead of the 60 as suggested in one post and I had to unplug my usb cable and plug it back in after the first reboot. Easy none the less, thank you!

Okay...it wont let me edit cause im a newb. The root worked or so I thought but now when I run Titanium backup it says it cant acquire root access. Any Ideas on this anyone?

Roblovesbox said:
Okay...it wont let me edit cause im a newb. The root worked or so I thought but now when I run Titanium backup it says it cant acquire root access. Any Ideas on this anyone?
Click to expand...
Click to collapse
Check and see if you have the Superuser app in your apps list. If not, download it from the Market, and then see if your apps that require root access work or not.

Yes I have the super user APP. The apps are just saying they aren't getting root access. They are in the list as well.

http://forum.xda-developers.com/showthread.php?t=803682
this worked for me, i used it last night

I was working on this last night. Z4root installs su to system/bin, while the 2nd root method installs to system/xbin. The ota changed the file permissions for su, but left the file in tact. That's why the one click mod will say your rooted (it sees the su file), but apps won't have root access.
I had to go old school and chmod the su file in system/bin rebooted and got root access again.
For anyone that used a one click root method like z4 root, and still hasn't done the ota update un root the phone first!
On the road but I will post instructions on how I re-rooted in a few hours as well as the specific files needed.
*actually from what I recall, any files needed are included in the one click root mentioned above.
Sent from my SCH-I500 using XDA App
**Follow instructions in this post http://forum.androidcentral.com/526222-post739.html
except, when you get to the portion that says
cd /system/xbin , replace that with cd /system/bin
(I believe only z4root users that did not unroot need to change this, or anyone who has su copied to their /bin directory without the root.)
everything is exactly the same... It's much better linking the post than copying the info again.

My phone w/ OTA dl09 is rooted successful by using Fascinateforums method.
Sent from my SCH-I500 using XDA App

Cannot for the life of me get system r/w permissions

I've been running cm7 nightlies and now stable 7.0 for some time now. I have the new radio, ladios' kernel, and the sdcard read fix flashed.
I installed super manager and successfully deleted some of the stock cm7 media off my phone last week. Today, I came across the new GPS.conf files and wanted to try them.
Super manager couldn't switch the system to r/w despite saying "ok"
When I try to delete or write in the system with EStrongs file explorer, ghost commander, or android mate, they all give strange errors. The deleted files disappear but reappear after reboot. If I try to paste a file in system/etc I only get an error.
Superuser is successfully allowing permissions. I have the latest busybox. I have r/w enabled in each file manager.
I even tried an adb push test which first said "system is r/o only". The next try was "successful" but didn't do anything.
I'm still new with adb so I probably did something wrong. I typed in that r/w command, mount now shows: /dev/block/mtdblock3 on /system type yaffs2 (rw,relatime)
I can't figure out what changed and what I need to do to get r/w permissions. My only theory is that i had uninstalled and reinstalled super manager earlier and that somehow messed with my permissions.

You cannot permanently modify the system partition while the phone is booted into Android. The only way is to use adb while the phone is in recovery mode. Any changes you make while the phone is booted will be lost after a reboot.
Go check on those media files you thought you deleted. I bet you'll find they are still there.

Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...

jamus28 said:
Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...
Click to expand...
Click to collapse
You don't need to sign them on the aria
Sent from my Liberty using XDA App

jamus28 said:
Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Click to expand...
Click to collapse
Those programs will work on some phones but not the Aria.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...
Click to expand...
Click to collapse
It really is as simple as adding or removing a few files from the zip file if you want to modify it.

[Q] Crash after root and renaming framworks-res.apk

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;

[how-to]Fix android market if it isn't working

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