I rooted my kindle fire using kindle fire utility 0.9.6 (after the rooting superuser wasn't installed on my kindle), downloaded twrp, flashed hashcode jelly bean ROM from this link
http://forum.xda-developers.com/showthread.php?t=1766829
and then flashed Superuser-3.1.3-x86-signed.zip which I downloaded from this link
http://androidsu.com/superuser/
but superuser won't work, when I check the root explorer in ES file explorer it tells me that this feature can't work on ur phone
Please I'm really dying out here
Someone Help Pleeeeeeeeeeeeeeeeeease !!!!!
You need the su binary installed as well. But with that being said, why don't you just install the Superuser.apk?
[Edit:] It's late and I'm not paying attention for some reason. Custom ROMs come pre-rooted and you have Jelly Bean installed. Perhaps there's a problem with ES File Explorer?
soupmagnet said:
You need the su binary installed as well. But with that being said, why don't you just install the Superuser.apk?
Click to expand...
Click to collapse
Thank you for replying so fast
how can I install su binary? and about the superuser.apk isn't that what i flashed into my device i have a superuser icon on my desktop but it just won't add any apps to its list.
Thanks again
At the Superuser website, there are three zip files. One is Superuser, one is the su binary, and the other should be both. Not that it matters at this point.
soupmagnet said:
At the Superuser website, there are three zip files. One is Superuser, one is the su binary, and the other should be both. Not that it matters at this point.
Click to expand...
Click to collapse
what do you mean by not that it matters at this point?
can't I just download the zip and flash it?
soupmagnet said:
You need the su binary installed as well. But with that being said, why don't you just install the Superuser.apk?
[Edit:] It's late and I'm not paying attention for some reason. Custom ROMs come pre-rooted and you have Jelly Bean installed. Perhaps there's a problem with ES File Explorer?
Click to expand...
Click to collapse
Maybe you missed this
soupmagnet said:
Maybe you missed this
Click to expand...
Click to collapse
I tried another app called copy paste it and when I try to use it this message appears:
"Your Phone does not appear to be rooted or has not been given root privileges. to use this application please provide root privileges to this applications"
what should I do?
[Edit] ok now i know my device is certainly not rooted i tried orbot, market enabler and market unlocker they all dispatch the same message your device isn't rooted.
can anyone tell me how to root it?
Scarfacew said:
I tried another app called copy paste it and when I try to use it this message appears:
"Your Phone does not appear to be rooted or has not been given root privileges. to use this application please provide root privileges to this applications"
what should I do?
[Edit] ok now i know my device is certainly not rooted i tried orbot, market enabler and market unlocker they all dispatch the same message your device isn't rooted.
can anyone tell me how to root it?
Click to expand...
Click to collapse
I too used the KFU to supposedly root my KF, but when I tried to install Titanium Backup, it gave me the same error message saying that my phone did not have root privileges... I wonder if there is something not installing correctly when using KFU...
"Root" consists of the su binary, which the system uses to give the user root permissions, and Superuser.apk, which keeps a database of what programs you allow to have those permissions. With "su" only, you will still have root permission, but only at the level of command line interface and your apps will not be allowed root permissions. Superuser.apk by itself is worthless. Custom ROMS come pre-rooted so the need to re-root is usually unnecessary unless something happens to one of the above mentioned programs. The only way to be sure if/which one is missing is in recovery via the command line because custom recovery will provide temporary root access.
Code:
adb shell ls /system/xbin
...look for su
Code:
adb shell ls /system/app
...look for Superuser.apk
Superuser can be installed from within the ROM using the .apk (at least in earlier versions it was possible), or in recovery using the command line or by flashing the signed .zip from the superuser website . The su binary can only be installed while in recovery.
Of course it all can be fixed by re-flashing your custom ROM.
It may also be necessary to rename the check-rooted executable, but only if you're running the stock Amazon software.
I think that pretty much covers it.
soupmagnet said:
"Root" consists of the su binary, which the system uses to give the user root permissions, and Superuser.apk, which keeps a database of what programs you allow to have those permissions. With "su" only, you will still have root permission, but only at the level of command line interface and your apps will not be allowed root permissions. Superuser.apk by itself is worthless. Custom ROMS come pre-rooted so the need to re-root is usually unnecessary unless something happens to one of the above mentioned programs. The only way to be sure if/which one is missing is in recovery via the command line because custom recovery will provide temporary root access.
Code:
adb shell ls /system/xbin
...look for su
Code:
adb shell ls /system/app
...look for Superuser.apk
Superuser can be installed from within the ROM using the .apk (at least in earlier versions it was possible), or in recovery using the command line or by flashing the signed .zip from the superuser website . The su binary can only be installed while in recovery.
Of course it all can be fixed by re-flashing your custom ROM.
It may also be necessary to rename the check-rooted executable, but only if you're running the stock Amazon software.
I think that pretty much covers it.
Click to expand...
Click to collapse
Ok now things are getting worse I tried to turn the wifi on and it didn't work, I tried to reboot and power off the tablet but it just won't work
{Edit} I want to know that by re-flashing the ROM is there a guarantee that those problems won't happen again.
One more thing is that I deleted the ROM from my kindle I can't transfer it from my laptop because the kindle hasn't been recognized after the jelly bean and I can't downloaded because wifi isn't working so what should I do
Thanks in advance
Scarfacew said:
Ok now things are getting worse I tried to turn the wifi on and it didn't work, I tried to reboot and power off the tablet but it just won't work
I want to know that by re-flashing the ROM is there a guarantee that those problems won't happen again.
Thanks in advance
Click to expand...
Click to collapse
There are never any guarantees when it comes to computers and system software, but the LIKELINESS is very high that the problem will be fixed.
soupmagnet said:
There are never any guarantees when it comes to computers and system software, but the LIKELINESS is very high that the problem will be fixed.
Click to expand...
Click to collapse
One more thing is that I deleted the ROM from my kindle I can't transfer it from my laptop because the kindle hasn't been recognized since I flashed the jelly bean and I can't downloaded because wifi isn't working so what should I do
Thanks in advance
Boot into recovery and "mount" your sdcard to USB. The computer should still recognize it.
soupmagnet said:
Boot into recovery and "mount" your sdcard to USB. The computer should still recognize it.
Click to expand...
Click to collapse
I re-flashed the Rom, wifi is working so I dl ES file explorer and checked Root explorer, but when superuser request popped, I clicked allow but it didn't work it gave me the same message, the new thing is that superuser app added es file explorer to its list but I still can't copy apps in the app/system file.
I know I bored you to death and I'm really thankful for ur help but I really need the root.
Scarfacew said:
I re-flashed the Rom, wifi is working so I dl ES file explorer and checked Root explorer, but when superuser request popped, I clicked allow but it didn't work it gave me the same message, the new thing is that superuser app added es file explorer to its list but I still can't copy apps in the app/system file.
I know I bored you to death and I'm really thankful for ur help but I really need the root.
Click to expand...
Click to collapse
Ok, well try a different ROM. If the problem persists then we can try to think of something.
I flashed the Alien droid ROM it's working fine till now but I need to know how to install an arabic keyboard please
Thanks
Ok, I have a dumb question, but from where do you run the DOS commands from? (ie. what directory?)..
c:\KFU?
Right-click on your KFU folder and select properties to find the folder's path. It may be different depending on wherever you've installed it.
soupmagnet said:
Right-click on your KFU folder and select properties to find the folder's path. It may be different depending on wherever you've installed it.
Click to expand...
Click to collapse
Thanks. but not sure i understand.
Here is what I'm attempting to do.. using the root method described here: http://forum.xda-developers.com/showthread.php?t=1638452 under "Getting to fastboot mode" there are a series of command line examples that seem to start with adb.... (ex. adb shell chmod 755 /data/local/tmp/fbmode).
Under Rooting the stock software, the first step command line is "adb shell mount system"
my question is from where do I start (directory) so that when I enter these commands they work?
Or are you saying that I need to fun all these from the KFU directory? (or KFU/tools) or some other directory..
I appreciate the help and feedback..
:h my::
Wherever adb is...Right-click on that folder to find it's path so you can "cd" or change directories to it. Alternatively, you can Shift + Right-click on that folder and select something like "Open command window here".
Related
I followed all the steps from the Wiki: (http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD).
Now the problem is when I go to verify the root. On the Wiki, where it says run "su' in computer ADB shell, I get access denied. When I run "./gfree_verify" in computer ADB shell, I get
Error: Could not open modem device; /dev/****
Error: Verify could not initialize device
But in my apps on the G2 I see an icon for superuser permissions. So did the root take or not?
Thanks for any help, new to Android.
Go in to terminal on your phone and type SU
After pressing enter if it says permissions denied, you have no root, if a Su message pops up click allow... that means you have root
Edit: I think you have no root
MacaronyMax said:
Go in to terminal on your phone and type SU
After pressing enter if it says permissions denied, you have no root, if a Su message pops up click allow... that means you have root
Edit: I think you have no root
Click to expand...
Click to collapse
After typing Su in the terminal on the phone, I get a message pop that says either allow or deny. I click allow and it gives me root permission.
Then it`s OK!
After reboot/or try again,open terminal emulator on your phone and type "su".
If you get a superuser prompt, you have root!
After "su" you should see a line with "#".
Ganii said:
Then it`s OK!
After reboot/or try again,open terminal emulator on your phone and type "su".
If you get a superuser prompt, you have root!
After "su" you should see a line with "#".
Click to expand...
Click to collapse
After a reboot (two actually) after I enter su into terminal I dont get the popup anymore asking allow or deny. I get "#." I actually went through the whole rooting Wiki steps again, to root the phone (just cause I wasn't sure if I was rooted). Same results, the gfree-verfiy doesnt work and neither does the "older" method. But I get "#" after entering su in terminal on G2.
I also installed Rom Manager, I clicked Flash ClockworkMod Recovery and then chose Backup Current ROM. It asked for superuser permissions and I allowed it. It rebooted the phone and went to a ClockworkMod Recovery screen where I selected reboot device. Does this mean I backed up my current Tmobile ROM?
Another question, is it okay to delete the files I had to push to /data/local to root? How would I delete them?
I want to really thank you guys for all the help.
boost3d23 said:
After a reboot (two actually) after I enter su into terminal I dont get the popup anymore asking allow or deny. I get "#." I actually went through the whole rooting Wiki steps again, to root the phone (just cause I wasn't sure if I was rooted). Same results, the gfree-verfiy doesnt work and neither does the "older" method. But I get "#" after entering su in terminal on G2.
I also installed Rom Manager, I clicked Flash ClockworkMod Recovery and then chose Backup Current ROM. It asked for superuser permissions and I allowed it. It rebooted the phone and went to a ClockworkMod Recovery screen where I selected reboot device. Does this mean I backed up my current Tmobile ROM?
Another question, is it okay to delete the files I had to push to /data/local to root? How would I delete them?
I want to really thank you guys for all the help.
Click to expand...
Click to collapse
# sign means your rooted or have su access.
Go under manage and restore backups in rom manager, you should have a copy of the rom you just backed up. Unless you renamed the back up its probably a date.
Its ok to delete the files you pushed to data/local use a file manager like root explorer.
Sent from my HTC Vision using XDA App
After a reboot (two actually) after I enter su into terminal I dont get the popup anymore asking allow or deny. I get "#." I actually went through the whole rooting Wiki steps again. Same results, the gfree-verfiy doesnt work and neither does the "older" method. But I get "#" after entering su in terminal on G2.
Click to expand...
Click to collapse
You get "#" then it`s right,the app don`t ask you again about allow or deny!
About gfree-verify,I don`t know.Maybe something wrong with Script
or you have done something wrong with the commands!
I also installed Rom Manager, I clicked Flash ClockworkMod Recovery and then chose Backup Current ROM. It asked for superuser permissions and I allowed it. It rebooted the phone and went to a ClockworkMod Recovery screen where I selected reboot device. Does this mean I backed up my current Tmobile ROM?
Click to expand...
Click to collapse
If you choose "Backup ROM" you phone boot into Recovery,then you have
to choose "backup/restore option to backup you current ROM.
Otherwise you don`t have a backup
Again thanks guys.
Now i downloaded Astro and ES file Managers but I cant find the files. Do I need specifically need root manager? Im guessing the ones I downloaded cant access root files.
boost3d23 said:
Again thanks guys.
Now i downloaded Astro and ES file Managers but I cant find the files. Do I need specifically need root manager? Im guessing the ones I downloaded cant access root files.
Click to expand...
Click to collapse
I use Root Explorer or SUFBS (Super User File Manager and Terminal).
boost3d23 said:
Now i downloaded Astro and ES file Managers but I cant find the files. Do I need specifically need root manager? Im guessing the ones I downloaded cant access root files.
Click to expand...
Click to collapse
You should really have posted up in the existing thread about gfree on this, or otherwise in the Q&A forum
But anyway, yes, those file managers don't handle root. Well, ES does have an option to do so, but it doesn't work on the Vision. So you'll need a root-capable file manager, as joemm said.
On the backup, that sounds a bit odd, but you'll know that it's doing a backup because it'll take a while. You'll get a different screen where it shows you it's backup up the main phone partitions, and even which file is being backed up. When it's done, make sure you copy this backup somewhere else, like your PC (i.e. so you don't just have a single copy, in case something happens to it - e.g. corrupt SD card).
Thanks to everyone who provided insight. I had the same problem and was worried about bricking my phone, but this worked and I'm happily rooted!
Phone: Incredible 2, running Android 2.3.3 Stock Verizon ROM
S-OFF and Rooted : using revolutionary 0.4pre4
HBoot: 6.13.1002
Recovery: Revolutionary CWM 4.0.1.4
I'm having ROOT Access/SU problems. I need access to some files in the root/System/ directory and am unable to get r/w.
I s-off/rooted my Incredible 2 using the instructions on this tutorial http://forum.xda-developers.com/showthread.php?t=1219246 (The How To Root DInc2) and the instructions on the revolutionary.io website. (Essentially: Get S-Off via revolutionary> flash recovery CWM> flash su.2.3.6.3-efgh)
The revolutionary s-off process was successful and I got s-off.
I flashed Superuser su.2.3.6.3-efgh-signed.zip and seem to have Root. The binaries are upto date according to the app.
I have Titanium Backup, Root Check, BusyBox Installer installed. I had to install Busybox. All these apps run properly. I can wipe, backup, and install system app data via Titanium Backup. Root Check says I have root access and the correct Busybox location.
The Problem
I installed Root Explorer today and I am successfuly able to change from R/O to R/W and back on the root directory and on the SDCard. But when I go to the System directory I cannot change from R/O to R/W.
Tryed to connect to the Inc2 from my PC (winXP) via ADB. ADB Devices command shows my device. When in ADB Shell the default profile is $. When I type in SU I get back the message "SU: permission denied" I do not get a prompt from Superuser on the phone to give access.
(To see if the problem was in the steps I was doing I tried this on my rooted Incredible 1 and in Root Explorer I was successfully able to remount the System directory from R/O to R/W and back. But the same problem with ADB I have on both Inc1 and Inc2. (Inc1 was s-off/rooted with Unrevoked3/Unrevoked Forever, with su.2.3.6.1-ef-signed.zip.)
I'm not sure what went wrong where, since some of the root access is working. Any suggestions? Help?
Thanks,
that happen to me before. and the only way to change the r/o to r/w is going back to stock,if you have a stock back up rom you have to run that one,and then you can install the rom you want,and the you can change with root explorer s/o to r/w.if you dont have a stock back up you have to install the PG32IMG,and then you have to go to revolutionary and install the recovery.dont forget to turn off the fast boot.if you dont know how to do that,setting,power,and then uncheck the fast boot to off.
I dont think your binaries are up to date.
Try installing SuperUser 3.0 and report back - with updated binaries. The binaries should show at least verison 3.
I had issues to with the Root access that came with revolutionary and this worked for me.
You are on the right path though.
I'd like to try and avoid flashing the original Verizon ROM back on the phone. I'll leave that for last resort. There is stuff that I've done to the phone that I would rather not have to go through to do again.
In Superuser I tap on the 'check for binary updates', the respone after checking is that the 'su is up to date'. The version that I'm currently using su.2.3.6.3-efgh-signed.zip the files are modified in 2008 and 2011. So it seems to be upto date.
Is there a place I can download the latest version of Superuser 3.0?
The version of Superuser3.0 that I was able to find, when I open the zip file, shows all the files last modifed in 2008.
You wont have to flash back.
Follow my advice and install the new SuperUser on the market. It is 3.0.
Once in the application go to update binaries and update anyway.
Reboot and let us know how it works.
Those 2.3.6.3 binaries didnt work for me either. Now im fine after following my own advice.
Oh - and also - check to make sure that you have allowed specific permission for the application you are having issues with - within SuperUser.
You will be pleased to see that the new SuperUser can automatically grant Root to all of your apps...dangerous, but speeds things up.
@tinkbtrar. Thanks!
Ugrading to the latest Superuser 3.0 and updating the binaries did help! Still some problems, but making progress.
I can connect via adb shell and get SU privileges. # shows up! I think I now have r/w privilege on /system. Not sure, but I think I do. (I'm still learning adb shell and linux commands)
But I still cannot get Root Explorer on the phone to work properly. Same problem as before. I can get r/o and r/w on the root directory, but cannot get r/w on the System directory. The button turns green, but the nothing changes.
I can live with getting SU privileges in adb shell, but it would really be nice to get r/w on System in RootExplorer.
gunnyp said:
@tinkbtrar. Thanks!
Ugrading to the latest Superuser 3.0 and updating the binaries did help! Still some problems, but making progress.
I can connect via adb shell and get SU privileges. # shows up! I think I now have r/w privilege on /system. Not sure, but I think I do. (I'm still learning adb shell and linux commands)
But I still cannot get Root Explorer on the phone to work properly. Same problem as before. I can get r/o and r/w on the root directory, but cannot get r/w on the System directory. The button turns green, but the nothing changes.
I can live with getting SU privileges in adb shell, but it would really be nice to get r/w on System in RootExplorer.
Click to expand...
Click to collapse
Be sure to click thanks if you haven't already. Lol.
Try wiping data...force closing and uninstalling root explorer (thru manage applications...not CWR).
Should take care of it. And because you are rooted you should have full access to filesystem via adb already.
Sent from my Xoom using xda premium
try mount -t ext3 -o remount,rw /dev/block/mmcblk0p25 /system with adb. thatll remount /system as readwrite
Sent from my Incredible 2 using XDA App
@tincbtrar, gave you the thumps-up!
No go with Root Explorer yet.
I wiped data from CWM, uninstalled, and reinstalled Root Explorer, but still could not get r/w on the System directory using Rootexplorer.
Anyone, any ideas/suggestions?
gunnyp said:
@tincbtrar, gave you the thumps-up!
No go with Root Explorer yet.
I wiped data from CWM, uninstalled, and reinstalled Root Explorer, but still could not get r/w on the System directory using Rootexplorer.
Anyone, any ideas/suggestions?
Click to expand...
Click to collapse
trust me you will have to do what i said before in the second post...
gunnyp said:
@tincbtrar, gave you the thumps-up!
No go with Root Explorer yet.
I wiped data from CWM, uninstalled, and reinstalled Root Explorer, but still could not get r/w on the System directory using Rootexplorer.
Anyone, any ideas/suggestions?
Click to expand...
Click to collapse
You paid for Root Explorer. It doesn't work for you. I'd be bugging the developer since it's clearly not doing the job.
@android-incredible
yes, i looking more and more like i may have to flash my rom backup that i made right after s-off. let's see, since i can get su in adb shell i can get done what i need to so reflashing is not utmost urgent.
i'm not sure it's rootexplorer since i've not seen other posts with similar issue. if the flash of the rom backup does not do it, that may then point to rootexplorer. lets see...
Ok so my one x is on stock jb "rooted" now but im having a problem with su only seemingly picking up half of the requests apps send to it. the rootchecker app says the su/superuser dirs are there but it says there is no root.
It was working before the OTA and i still have some apps working fine that need root but others aren't getting allowed and theres no prompt for them, but if i remove the apps that are allowed root and reinstall they get prompted by su for auth or deny as normal.
I cant delete the su files in esfileexplorer as it just gives me an error, i cant select RW on the system dir as it gives root error but i can browse the root dir.
I want to remove su completely and reroot but none of the unroot apps i have found will work (probably because of JB) and i don't know the fastboot commands to remove what i need to remove.
Anyone have any ideas?
TheAngelus said:
Ok so my one x is on stock jb "rooted" now but im having a problem with su only seemingly picking up half of the requests apps send to it. the rootchecker app says the su/superuser dirs are there but it says there is no root.
It was working before the OTA and i still have some apps working fine that need root but others aren't getting allowed and theres no prompt for them, but if i remove the apps that are allowed root and reinstall they get prompted by su for auth or deny as normal.
I cant delete the su files in esfileexplorer as it just gives me an error, i cant select RW on the system dir as it gives root error but i can browse the root dir.
I want to remove su completely and reroot but none of the unroot apps i have found will work (probably because of JB) and i don't know the fastboot commands to remove what i need to remove.
Anyone have any ideas?
Click to expand...
Click to collapse
reroot via recovery mode, have you ever think of that ?
or try to use adb command to delete the old superuser file / replace the old superuser file with the working one
Reboot into recovery (turn on whilst holding Volume - [down])
adb uninstall superuser.apk (or whatever its named on your device)
Download new SuperUser
adb install SuperUserNew.apk (Or whatever the file name of the new one is)
Goodluck
Thanks Wilks3y, ive tried the uninstall command but i get this error:
/sbin/sh: pm: not found
The apk in the system/app folder is called superuser.apk
TheAngelus said:
Thanks Wilks3y, ive tried the uninstall command but i get this error:
/sbin/sh: pm: not found
The apk in the system/app folder is called superuser.apk
Click to expand...
Click to collapse
what is the name of the superuser that you have downloaded ? (the new one, not the old one at system/app/)
if it's the same name "superuser.apk" then the command is "adb install superuser.apk"
or go to recovery mode and apply flashable zip to replace the superuser files
download this one http://download.chainfire.eu/298/SuperSU/CWM-SuperSU-v0.99.zip
put in your sdcard
go to recovery
apply this supersu package
more information -> http://forum.xda-developers.com/showthread.php?t=1538053
Yeh thanks its working now after reflashing the cwm superuser.
So I usually use the toolkit to root, in fact I have been for many versions now.
However with the installation of 4.2.1 I haven't been able to root at all. I use the toolkit in the same way but it simply doesn't root the phone.
So today I tried the manual way. I downloaded and installed SDK tools from google navigated to the adb folder and went through the commands. Everything seemed to go okay apart from when I typed adb shell chmod 06755 /system/bin/su. The command window did nothing.
I carried on and typed adb shell chmod 06755 /system/app/Superuser.apk, when it said "bad command" or something similar.
Rebooted the phone, no root... still.
However the Superuser app is there. So:
1) How do I delete the superuser app, bearing in mind it has system permissions. I'd like to simply start again.
2) I don't have CW recovery installed and would prefer not to bother with it if I can.
3) Just to confirm, when I root the phone, does that allow me to delete files in the /system/app folder?
4) Following this guide on rooting manually. Is that all alright?
5) In a couple of sentences, can someone explain rooting to me? From what I understood, rooting simply opens up the phone to allow access to everywhere, where you can copy and delete files, or apks.
6) If 5 is true, when following the rooting guide (4), which command am I actually telling the system to run as root? Is it simply the "root" command?
7) If 6 is true, how come when I re-boot, the phone won't let me delete things from the system/app folder?
Thanks for any help.
1) stop using a toolkit, and no you didnt root the manual way.
2) download this: http://forum.xda-developers.com/showthread.php?t=1538053 - its supersu, superuser is unreliable on 4.2+
3) fastboot flash a recovery
4) flash the supersu.zip
5) done.
Sorry, I should have explained the Su app is SuperSU.
Just gave it another go using a manual toolkit but still no root access. I also now have an su.apk, superuser.apk (SuperSU) and a su file. Need to delete them all.
What do you mean by "fastboot flash a recovery"? You mean flash a new recovery centre like CW?
Don't these superuser apps just manage app permissions? They don't actually enable the root access do they?
Thanks
anotherxdauser said:
Sorry, I should have explained the Su app is SuperSU.
Just gave it another go using a manual toolkit but still no root access. I also now have an su.apk, superuser.apk (SuperSU) and a su file. Need to delete them all.
What do you mean by "fastboot flash a recovery"? You mean flash a new recovery centre like CW?
Thanks
Click to expand...
Click to collapse
follow this: http://forum.xda-developers.com/showthread.php?t=1529058
Quick Q...
If I flash a 4.2.1 system.img to the phone, it will replace what exactly?
I'm thinking this might be a way to get rid of the root apps which are protected and allow me to update to 4.2.2, THEN look at manually rooting.
anotherxdauser said:
Quick Q...
If I flash a 4.2.1 system.img to the phone, it will replace what exactly?
I'm thinking this might be a way to get rid of the root apps which are protected and allow me to update to 4.2.2, THEN look at manually rooting.
Click to expand...
Click to collapse
it replaces anything in /system... basically the OS.
I have been able to root my Kindle and want to get the store working.
I think I need to copy the Google Services Framework APK to the /system/app directory.
I am using ES File Explorer version 1.6.2.5.
My Kindle is version 6.3.2.
When I try to copy the file from the SD card to the /system/app directory it says unable to copy.
Thanks in advance for the help
Did you mount system as read/write?
I'm afraid I don't know what that means. I used KFU 0.9.6 to root the device. I had installed ES file explorer before I did the rooting. Does explorer need to be read/write, or is that an option for KFU? Is it an option I can change or do I have to re-install something?
robvia said:
I'm afraid I don't know what that means. I used KFU 0.9.6 to root the device. I had installed ES file explorer before I did the rooting. Does explorer need to be read/write, or is that an option for KFU? Is it an option I can change or do I have to re-install something?
Click to expand...
Click to collapse
ES File Explorer should have the option to do so, but I don't use it so I couldn't say for sure. If you can't figure it out, I'm sure someone around here will be able to help.
I found the Root settings in ES F E and checked the option for Root Explorer. It gave me a message that test fails option not allowed on your phone. Not sure if that is what I should be looking for or not.
robvia said:
I found the Root settings in ES F E and checked the option for Root Explorer. It gave me a message that test fails option not allowed on your phone. Not sure if that is what I should be looking for or not.
Click to expand...
Click to collapse
Do you have an ADB connection?
The Mount File System option is greyed out.
Below that it says Mount/ , /system as writable.
Does that have to be installed after the rooting is done?
Is there another file explorer option that is better?
Should I uninstall and re-install ES?
ES is on the Kindle. I have copied the APK to the kindle and to the SDcard directory. When I am connected to the computer, my computer only has access to the sdcard directory. I can't even see the /system folder.
ES can see the folder, but can't write to it.
robvia said:
ES is on the Kindle. I have copied the APK to the kindle and to the SDcard directory. When I am connected to the computer, my computer only has access to the sdcard directory. I can't even see the /system folder.
ES can see the folder, but can't write to it.
Click to expand...
Click to collapse
You still didn't answer my question. Do you have a connection with ADB? You were able to root it weren't you? You must have had an ADB connection at some point.
Sorry, Since I was trying to copy the file with out the device connected to the computer, I didn't think it mattered.
When connected to the computer, in device manager, it's Android Composite ADB Interface.
The Kindle shows up as a drive in Windows Explorer. At one point when I was doing the root, it did not show up as a drive.
If I can copy from my computer to the /system directory, that would be great, but since i don't have access to that through the computer, I was copying from the download directory on the Kindle to the /system directory on the Kindle.
robvia said:
Sorry, Since I was trying to copy the file with out the device connected to the computer, I didn't think it mattered.
When connected to the computer, in device manager, it's Android Composite ADB Interface.
The Kindle shows up as a drive in Windows Explorer. At one point when I was doing the root, it did not show up as a drive.
If I can copy from my computer to the /system directory, that would be great, but since i don't have access to that through the computer, I was copying from the download directory on the Kindle to the /system directory on the Kindle.
Click to expand...
Click to collapse
You say you used the KFU to root...do you still have it available? Run it and see if it shows ADB ONLINE.
Yes, the ADB status is online when I run KFU. I also ran Super One Click and it said your device apears to be rooted.
I also installed the app, mount /system (rw/ro).
when I select mount rw, it says the system dir remounted with r/w permission.
robvia said:
Yes, the ADB status is online when I run KFU. I also ran Super One Click and it said your device apears to be rooted.
I also installed the app, mount /system (rw/ro).
when I select mount rw, it says the system dir remounted with r/w permission.
Click to expand...
Click to collapse
Soooo...problem solved, right?
I wish it were that easy. Even though it says it's mounted in r/w mode, I can't get it to copy. Should I try and root it again? Could I have done something wrong? I used KFU and did root with superuser. Should I use Super One Click and unroot then try to root again? I don't remember any options for me to select wrong. Is there a PC tool that alllows you to copy directly to the /system directory? I really thought I was past the hard part. Thanks again for all the help.
Okay, since you have KFU and you have connection with ADB, press Shift then Right-click on the KFU "tools" folder and select "Open command window here". At the command prompt that opens up enter the following (omitting the comments in red, of course) ;
Code:
$ adb push /local/path/to/GoogleServicesFramework.apk /sdcard/ [COLOR=Red]<-- Replace "/local/path/to/..." with the location of GoogleServicesFramework.apk on your computer
[/COLOR]
$ adb shell
$ su [COLOR=Red]<-- If you receive an error here, you need to re-root
[/COLOR]~ # mount -o remount,rw ext4 /system [COLOR=Red]
[/COLOR]~ # mv /sdcard/GoogleServicesFramework.apk /system/app/GoogleServicesFramework.apk
~ # chmod 644 /system/app/GoogleServicesFramework.apk
~ # pm install -r /system/app/GoogleServicesFramework.apk
do the same for AccountAndSyncSettings and GoogleLoginService, reboot, then do the same for Vending.apk (I'm assuming you are trying to install the Market, right?)
Ok. I think I might see the issue. When I rooted the Kindle I did not have the apk copied to the device. It looks like there is a move command that copies the APK file from the SDcard to /sysstem/app folder. I think I need to put the apk in the proper place on the device and then un-root and then try and root it again.
Yes I am tyring to get the market running.
So you are saying there are 3 files that need to be copies? I have the file com.android.vending_3.8.15.apk, but I do not have AccountAndSyncSettings.
The more I read your reply, I'm less sure of myself. Before I root with KFU (or maybe super one click) do I need to have files copied to the Kindle? I guess I would have expected KFU to have these files, but OK if not included. Does KFU attempt to copy the framework file to the proper directory? If so, where does the files need to exist before starting?
I think your instructions here are a command line version of what I am trying to do with ES File Explorer. Is that true?
robvia said:
Ok. I think I might see the issue. When I rooted the Kindle I did not have the apk copied to the device. It looks like there is a move command that copies the APK file from the SDcard to /sysstem/app folder. I think I need to put the apk in the proper place on the device and then un-root and then try and root it again.
Yes I am tyring to get the market running.
So you are saying there are 3 files that need to be copies? I have the file com.android.vending_3.8.15.apk, but I do not have AccountAndSyncSettings.
The more I read your reply, I'm less sure of myself. Before I root with KFU (or maybe super one click) do I need to have files copied to the Kindle? I guess I would have expected KFU to have these files, but OK if not included. Does KFU attempt to copy the framework file to the proper directory? If so, where does the files need to exist before starting?
I think your instructions here are a command line version of what I am trying to do with ES File Explorer. Is that true?
Click to expand...
Click to collapse
You need AccountAndSyncSettings. Are you using a tutorial for this? If so, which, one?
And yes, it is the command line version of what you're trying to accomplish with ES. It will give you more control and you'll be less likely to screw up.
Sure is rooted?
I recently back to stock firm to can check battery issues. I was using JB Hashcode very happy so far and was thinking go back again, but a short pass by the stock firmware was a really bad idea because got an update on the air (6.3.2) and lose my rooted status. I've used KFU again with no luck. Root explorer, droidwall says that i'm not rooted... So sad. Any ideas?
chocaru said:
I recently back to stock firm to can check battery issues. I was using JB Hashcode very happy so far and was thinking go back again, but a short pass by the stock firmware was a really bad idea because got an update on the air (6.3.2) and lose my rooted status. I've used KFU again with no luck. Root explorer, droidwall says that i'm not rooted... So sad. Any ideas?
Click to expand...
Click to collapse
What does this have to do with the topic at hand?
Sorry for not getting back earlier. My weekend included getting hit by a deer. Really messed all my plans up.
I used the instructions here http://forum.xda-developers.com/showthread.php?t=1399889.
These screenshots show an option to install Google Apps, but I don't see that option when I run it. I guess I'm a little confused. Are there different instructions I should be following?