[Q] System software version 6.3_user_4019920 root possible? - Kindle Fire Q&A, Help & Troubleshooting

Hi all,
I have a kindle fire with system version 6.3_user_4019920.
I used Kindle Fire Utility 0.9.5, installed TWRP, FFF and Permanent Root with Superuser (option 2).
I did NOT installed Google Apps/Go Luncher EX though!
Everything went just fine with no errors at all.
I installed ProxyDroid 2.6.2 and that tells me that I am not root. I checked also to see if the device is rooted installing Root Checker app and that tells me also: "Sorry, you don't have root access"
Any help would be appreciated!
Regards,

osceoladad said:
Hi all,
I have a kindle fire with system version 6.3_user_4019920.
I used Kindle Fire Utility 0.9.5, installed TWRP, FFF and Permanent Root with Superuser (option 2).
I did NOT installed Google Apps/Go Luncher EX though!
Everything went just fine with no errors at all.
I installed ProxyDroid 2.6.2 and that tells me that I am not root. I checked also to see if the device is rooted installing Root Checker app and that tells me also: "Sorry, you don't have root access"
Any help would be appreciated!
Regards,
Click to expand...
Click to collapse
I have this problem too, KFU doesn't seem to copy su binary to /system/xbin, so just do it your self from adb (su binary located in the "files" folder inside KFU), then set permission to it as 06755, finally open install Superuser.apk.
Reboot into recovery mode
adb shell mount system
adb push ..\files\su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb install ..\files\Superuser.apk

Thank you.
I did all steps, but at the last command (adb install ..\files\Superuser.apk) I got the following error:
/sbin/sh: pm: not found

osceoladad said:
Thank you.
I did all steps, but at the last command (adb install ..\files\Superuser.apk) I got the following error:
/sbin/sh: pm: not found
Click to expand...
Click to collapse
You must boot out of recovery and back into the system before executing the adb install command.

kinfauns said:
You must boot out of recovery and back into the system before executing the adb install command.
Click to expand...
Click to collapse
Thanks,
I saw that KFU was showing 5000 status mode. So, I did: "fastboot oem idme bootmode 4000" I got an OKAY on the PC screen and now the Kindle Fire is stucked at the logo (I cannot even power it off). I disconnected and reconnected but know even the computer is not recognizing it.
Any other suggestions?

osceoladad said:
Thanks,
I saw that KFU was showing 5000 status mode. So, I did: "fastboot oem idme bootmode 4000" I got an OKAY on the PC screen and now the Kindle Fire is stucked at the logo (I cannot even power it off). I disconnected and reconnected but know even the computer is not recognizing it.
Any other suggestions?
Click to expand...
Click to collapse
That only changes the bootmode. You need to actually tell it to reboot.
Code:
fastboot reboot
Maybe you want to read the first few posts of this link...
http://forum.xda-developers.com/showthread.php?t=1552547
It will help you understand what you are doing rather than just typing commands.

kinfauns said:
That only changes the bootmode. You need to actually tell it to reboot.
Code:
fastboot reboot
Maybe you want to read the first few posts of this link...
http://forum.xda-developers.com/showthread.php?t=1552547
It will help you understand what you are doing rather than just typing commands.
Click to expand...
Click to collapse
That is exactly the article from were I have the command. Unfortunetly because the kindle is now stucked at the logo (cannot turn it off) even if I issue fastboot reboot is waiting for a device that is not recognized.

osceoladad said:
That is exactly the article from were I have the command. Unfortunetly because the kindle is now stucked at the logo (cannot turn it off) even if I issue fastboot reboot is waiting for a device that is not recognized.
Click to expand...
Click to collapse
Hold the power button until it shuts off. Then restart.

First what is the charge level on your battery that can happen from your battery being flat also maybe try powering it off by holding the power button for 20 seconds till it does completely power down some say to reinstall your drivers but I can't imagine why how and where they could have changed considering how far you have gotten

It worked and I was able to finishe the rooting also.
Thanks for all guys who replied, wasted their time and helped me out!
I needed all this because of a Europe trip and I run a Squid proxy here in US that I want to use it for netflix. Hopefully ProxyDruid will help me out.
Best,

I'm having a similar problem. I used KFU 0.9.6 and installed permanent root and twrp. I've even flashed the latest jandycane ROM. It's super stable and have had no problems except that I can't run apps that require root. The root checker says I don't have root. I tried running the above adm commands but with no luck. Any help is appreciated.
Sent from my Amazon Kindle Fire using Tapatalk 2

mcqueena9845 said:
I'm having a similar problem. I used KFU 0.9.6 and installed permanent root and twrp. I've even flashed the latest jandycane ROM. It's super stable and have had no problems except that I can't run apps that require root. The root checker says I don't have root. I tried running the above adm commands but with no luck. Any help is appreciated.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Enter the following command and post the results:
adb shell ls /system/xbin | grep '\bsu\b'; echo $?
Click to expand...
Click to collapse

soupmagnet said:
Enter the following command and post the results:
Click to expand...
Click to collapse
I'm not on mac or linux so the grep command fails. The output of
Code:
adb shell ls /system/xbin/su
is
Code:
/system/xbin/su
---------- Post added at 04:39 PM ---------- Previous post was at 03:57 PM ----------
I ran the utility again. Now /system/xbin/su is a symbolic link to /system/bin/su. The output of
Code:
adb shell ls -al /system/xbin/su
is
Code:
lrwxrwxrwx root root 2012-10-10 16:29 su -> /system/bin/su
and the output of
Code:
adb shell ls -al /system/xbin/su
is
Code:
-rwsr-sr-x root root 173934 2008-08-01 08:00 su

Sorry, it's easy for me to forget about you windows users
Do you have terminal emulator?
See if the "su" command is successful.

soupmagnet said:
Sorry, it's easy for me to forget about you windows users
Do you have terminal emulator?
See if the "su" command is successful.
Click to expand...
Click to collapse
Code:
/system/bin/sh: /system/bin/su: not executable: magic 7F45

Apparently your su binary is corrupt. Use adb shell to remove it and then adb push a new version to your /system/xbin folder. Afterwards (adb shell) chown and chmod to give it the proper ownership/permissions and try again.
I'm assuming you already know how to do this.
---------- Post added at 05:06 PM ---------- Previous post was at 04:59 PM ----------
Upon further inspection, it seems as though you installed the wrong su binary. There are two available; x86 and ARM. You need ARM.

Thanks for the help. I pushed a new su file. Now it says permission denied. What should the permissions be set to? I tried 06755 as above but no luck.
Sent from my PC36100 using Tapatalk 2

Code:
adb shell
chown 0.0 /system/xbin/su
chmod 755 /system/xbin/su
Then try su in terminal emulator

Still getting permission denied.
Sent from my Amazon Kindle Fire using Tapatalk 2

mcqueena9845 said:
Still getting permission denied.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Sorry, I told you wrong.
Code:
adb shell chmod 06775 /system/xbin/su

Related

[Root][Bootloader] BurritoRoot3 - The whole enchilada. Easy root edition

For 6.3 see http://forum.xda-developers.com/showthread.php?p=24129239
Please do not reupload/redistribute BurritoRoot2/BurritoRoot3, instead link directly to my hosting. I own the server, it will no go away any time soon. This allows me to update it if a bug is found.
BurritoRoot3 is not opensource, it is free, but it is not free to distribute. Please do not redistribute it.
Tested on 6.2, 6.2.1 and 6.2.2
Disclaimer:
BurritoRoot3 may void your warranty. While it was tested, over and over, a chance of data loss or hardware damage always exists. If something bad happens due to your use of BurritoRoot3, well it is your fault not our's, don't blame any of us.
Wine/Coffee/Device Funding:
To donate to jcase of TeamAndIRC for BurritoRoot go here:
http://forum.xda-developers.com/donatetome.php?u=2376614
To donate to pokey900 for the FireFireFire Bootloader go here:
http://forum.xda-developers.com/donatetome.php?u=466725
Download:
http://download.cunninglogic.com/BurritoRoot3.apk
BurritoRoot3 is an all in one package, to root and install the custom bootlaoder, FireFireFire, onto the KindleFire.
Instructions are pretty plain and simple, however you will have to get adb working on your own (if you have written, or know of adb guides for the Kindle Fire please PM me to list them here).
ADB GUIDES
MAC GUIDE: http://forum.xda-developers.com/showthread.php?t=1443071
WINDOWS GUIDE: http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
LINUX GUIDE: http://forum.xda-developers.com/showthread.php?p=22067293
What it does:
Gains root, installs superuser, installs su and installs the FireFireFire bootloader.
At this time, we do not have permission to distribute any recovery, once one is available for our use, we will add auto flashing of recovery.
How to use:
adb shell chmod 777 /data/local/tmp
Run app, follow directions given by the app.
Usage example :
[email protected]:~$ adb shell chmod 777 /data/local/tmp <---- This one is important, it may not create BurritoRoot3.bin if this is not done
[email protected]:~$ adb install BurritoRoot3.apk
4897 KB/s (1151520 bytes in 0.229s)
pkg: /data/local/tmp/BurritoRoot3.apk
Success
<go open the app now>
[email protected]:~$ adb shell /data/local/tmp/BurritoRoot3.bin --root
BurritoRoot3 Installer 0.1 by TeamAndIRC
#########################################################################
Usage: BurritoRoot3.bin <parameter>
--root - Restart adbD as root, and install Superuser app
--install - Install su
#########################################################################
Gaining root...
Installing Superuser APP, if it erros as already exists, please ignore the error.
pkg: /data/data/net.andirc.burritoroot3/bin/Superuser.apk
Success
Restarting adbD as root...
Please run adb shell /data/local/tmp/BurritoRoot3.bin --install
[email protected]:~$ adb shell /data/local/tmp/BurritoRoot3.bin --install
BurritoRoot3 Installer 0.1 by TeamAndIRC
#########################################################################
Usage: BurritoRoot3.bin <parameter>
--root - Restart adbD as root, and install Superuser app
--install - Install su
#########################################################################
BurritoRoot3 kroot 0.1 - TeamAndIRC
Remounting /system...
Cleaning up, ignore any errors
rm failed for /system/xbin/su, No such file or directory
rm failed for /system/bin/su, No such file or directory
Installing su...
Remounting /system..
Root installed
Starting: Intent { act=android.intent.action.MAIN cmp=net.andirc.burritoroot3/.FireFireFire }
Please check your Kindle's screen
[email protected]:~$
If you already have root, and want to safely install the FireFireFire bootloader, you can use the app, just install, open/close the app then
adb shell am start -a android.intent.action.MAIN -n net.andirc.burritoroot3/net.andirc.burritoroot3.FireFireFire
To install the CWR recovery by DoomLord after gaining root:
Download it, and push it to your Kindle
adb push <filename> /data/local/recovery.img
adb shell dd if=/data/local/recovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
Would you support the archos G9 devices
jutley said:
Would you support the archos G9 devices
Click to expand...
Click to collapse
Doesn't archos sign or lock system?
I love you Devs so much. I just got a Kindle today, but as I watched the video your Kindle shows up under Other Devices as if it didn't install the device driver. Mine is installed under portable devices. Can I just update that one or is there a debug mode for the Kindle that I'm missing?
Thanks for all you do!
---------- Post added at 10:06 AM ---------- Previous post was at 09:55 AM ----------
CharlieBoy808 said:
I love you Devs so much. I just got a Kindle today, but as I watched the video your Kindle shows up under Other Devices as if it didn't install the device driver. Mine is installed under portable devices. Can I just update that one or is there a debug mode for the Kindle that I'm missing?
Thanks for all you do!
Click to expand...
Click to collapse
LoL Nevermind I think I know why mine isn't there... I've already installed ADB from before. I shall continue on and see what happens :-D
I'm currently running Ubuntu 11.10(Without access to a windows computer to do so.) And after following the steps within the BurritoRoot I get error: insufficient permissions for device when entering adb root. I've rebooted my kindle and laptop as well as changed usb ports.
I've set it up so that it's acknowledged within /.android. Am I perhaps missing something sdk wise? The usb configuration install for extras within it says Linux isn't compatible. But any insight into this would be appreciated I'm not new to Android or adb for that matter. Things seem to be done differently for the Kindle is all.
Thanks guys.
AproSamurai said:
I'm currently running Ubuntu 11.10(Without access to a windows computer to do so.) And after following the steps within the BurritoRoot I get error: insufficient permissions for device when entering adb root. I've rebooted my kindle and laptop as well as changed usb ports.
I've set it up so that it's acknowledged within /.android. Am I perhaps missing something sdk wise? The usb configuration install for extras within it says Linux isn't compatible. But any insight into this would be appreciated I'm not new to Android or adb for that matter. Things seem to be done differently for the Kindle is all.
Thanks guys.
Click to expand...
Click to collapse
adb kill-server
sudo -s
adb devices
should see it now
Quit following me around jcase
Unheard said:
Quit following me around jcase
Click to expand...
Click to collapse
Hah Where you been?
I can not get ADB to recognize the device for the life of me.
I know I have the drivers installed the Fire is recognized as "android composite adb interface" under the Android Phone category in Device manager. But I can not get adb to see it.
"Adb kill-server"
"adb devices"
and it shows no devices attached. Ive done a factory reset on the tablet just to see (knowing it wouldn't make a difference)
Im running Windows XP
if someone could help me out.
notsointeresting said:
I can not get ADB to recognize the device for the life of me.
I know I have the drivers installed the Fire is recognized as "android composite adb interface" under the Android Phone category in Device manager. But I can not get adb to see it.
"Adb kill-server"
"adb devices"
and it shows no devices attached. Ive done a factory reset on the tablet just to see (knowing it wouldn't make a difference)
Im running Windows XP
if someone could help me out.
Click to expand...
Click to collapse
I'm sure its related to windows' drivers but I have no clue. Sorry
jcase said:
adb kill-server
sudo -s
adb devices
should see it now
Click to expand...
Click to collapse
Thanks man, I knew I must have failed to do something. It's much appreciated.
Dis this last night and it worked fine. Thanks!
I did have a few minor stumbles though. It seems the newest version of the software changed the name of the superuser app but the guide still uses the old name in the install command. Once I realized this I just changed the name in the command and it went right in.
Also for some reason I couldn't select the text in the adb box on the web page so I had to enter the commands by hand. No big deal but I would have felt more secure if the commands were in simple text so I could have copy/paste them in.
Like I said though everything worked and I have the market installed now. Thanks for the hard work!
I'm having some trouble with mine...I am trying to follow the video instructions to the link but it shows downloading a .android folder and extracting it to my user name on desktop but there is no such link. I have downloaded SDK and installed google usb drivers as well. I have 6.2.1 firmware and downloaded kindleroot_androidpolice.apk and placed on my kindle and I also downloaded superuser-2. I am not able to install the driver to the fire either. I go to my computer, manage, device manager, kindle, update driver software, browse my computer, etc. I have no INF file to choose under my .android folder.
Any help would be appreciated
My sd card is showing up as unmounted and not sure how to remount it. I sent adb remount and it didn't work. Any help would be appreciated.
Fee454 said:
I'm having some trouble with mine...I am trying to follow the video instructions to the link but it shows downloading a .android folder and extracting it to my user name on desktop but there is no such link. I have downloaded SDK and installed google usb drivers as well. I have 6.2.1 firmware and downloaded kindleroot_androidpolice.apk and placed on my kindle and I also downloaded superuser-2. I am not able to install the driver to the fire either. I go to my computer, manage, device manager, kindle, update driver software, browse my computer, etc. I have no INF file to choose under my .android folder.
Any help would be appreciated
Click to expand...
Click to collapse
would suggest to use this:
http://forum.xda-developers.com/showthread.php?t=1399889
[/COLOR]
b63 said:
would suggest to use this:
http://forum.xda-developers.com/showthread.php?t=1399889
Click to expand...
Click to collapse
This tool will attempt to install the correct Drivers for the Kindle Fire.
It will also perform the setup required for adb_usb.ini in .android for you.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
Press any key to continue . . .
I tried to install the drivers for the kindle but i receive the above message
---------- Post added at 09:56 PM ---------- Previous post was at 09:07 PM ----------
My issue is it cannot find my device...where can I find the kindleADB.zip I keep hearing about?
did you do install_drivers.bat first ?
take a look:
http://forum.xda-developers.com/showpost.php?p=20698002&postcount=283
that should correct the path issue
You should get the same files from the android Sdi. Good luck.
Jcase, I know that you said the unroot button did not work, but is there a method of unrooting?
b63 said:
did you do install_drivers.bat first ?
take a look:
http://forum.xda-developers.com/showpost.php?p=20698002&postcount=283
that should correct the path issue
Click to expand...
Click to collapse
Yes thank you. Moving it to the same as the run.bat seemed to have worked as it shows online now when running the Kindle Fire Utility. I switched it to fast boot but now seems to have been frozen at the kindle fire logo for quite some time now. I heard you have to switch to fastbook to install TWRP first before rooting?
I am not sure if I should attempt to somehow reboot this as it seems to be stuck at the boot up screen
wrong - switch back to normal boot and use the utility

[Q] fb mode: premission denied in KFU 0.9.5

im try to root my Fire v6.3 with KFU v0.9.5. The drivers are installed corrected and my ADB status - online and Boot status - 4000. But when i try and root with option 2(or use any option actually) i see /local/data/fbmode: permission denied
Can anyone tell me what my issue is?
thanks guys.
Change the permissions of fbmode. In command prompt, navigate to the KFU folder that contains adb.exe and enter...
adb shell chmod 775 /data/local/fbmode
...and try again
Sent from my Amazon Kindle Fire using xda premium
i tried that and i'm still getting permission denied. I've been messing about with this for a few days now. I just copied and pasted what you told me to type. I actually tried "adb shell chmod 755 /data/local/fbmode" i saw that on another website. Still no working!
Any other tips?
thanks
[Edit:] I changed my mind
Instead, try rooting manually. Without KFU.
http://forum.xda-developers.com/showthread.php?p=24124828
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
[Edit:] I changed my mind
Instead, try rooting manually. Without KFU.
http://forum.xda-developers.com/showthread.php?p=24124828
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
i just finished trying that and got permission denied on this line "adb shell /data/local/fbmode". I'm quickly exhausting all options. I've tried on 2 pc's, one running xp and one running windows 7 and get to the same stage!
Did you "adb root" and "adb remount" to mount system as read/write?
Sent from my Amazon Kindle Fire using xda premium
i managed to get it rooted manaully using /tmp/ in the comand lines as below.
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
Came across it on a thread on here. Thank for you help man

PLEASE HELP! Kindle Fire stuck in infinite bootloop after adb reboot

Hi,
I recently got a new Kindle fire and tried to root it.
I followed the instructions given in this post.
http://forum.xda-developers.com/showthread.php?t=1568340
However, my kindle fire seems to be stuck in an infinite boot loop after first step itself.
Here are the step I followed (I am using Windows 7 32bit).
1. Installed android sdk.
2. Updated the Kindle driver to install "android abd composite interface"
3. Downloaded all the required files in the platform-tools folder
Required files:
fbmode.zip - http://forum.xda-developers.com/show....php?t=1414832
twrp2 - http://teamw.in/project/twrp2/79
su - http://dl.dropbox.com/u/8699733/kindlefire/su
firefirefirefire http://forum.xda-developers.com/show....php?t=1369405
fastboot + adb for your OS of choice.
4. Followed following commands:
unzip fbmode.zip
adb push fbmode /data/local/fbmode
adb shell chmod 755 /data/local/fbmode
adb shell /data/local/fbmode
adb reboot
5. After this, my kindle fire seems to have stuck in an infinite boot loop.
- It starts up only when a USB cable is connected.
- Power light is orange and not green
- It starts up Kindle Fire logo comes up, then shuts down again
- My computer is not detecting any device, probably because KF is in an infinite boot loop
- When I run adb devices -- no devices show up
- When I run fastboot command [fastboot -i 0x1949 flash bootloader .....] it says "waiting for devices"
- When I remove the USB cable from KF, It doesn't powers on (even after long pressing the power button).
- I tried many things posted on different forums on two laptops (Windows 7 32 bit as well as 64 bit) and using different USB cables but nothing worked.
- Only thing I haven't tried is Factory cable as I don't have it and don't have money to buy it.
PLEASE HELP!!
http://forum.xda-developers.com/showthread.php?t=1623244
Superuser not working
Thanks for the help with the charging issue Kinfauns!!!
I charged my kindle fire using stock charger and finally rooted it.
However, I am still not able to install android market on my KF.
After rooting Kindle (followed all the steps given in the thread), I installed Superuser.apk.
Then to install android market, I installed root explorer and downloaded Kindle Fire android market zip file. (followed instructions from one of the NAT3MIL's video on youtube).
First step is to install googleServicesFramework.apk file, which I did.
The next step is to move market.apk file to system/apps folder. However, when I tried doing that, I got a warning:
"Your phone doesn't appear to be rooted. This is requires in order to change or delete protected files such as this ......"
I don't understand why is it saying so as I have followed all the steps in the thread to root my KF?
How to check if the KF is really rooted?
Are there any settings to be changed in the superUser.apk?
Please help!!
Thanks a ton!!
Superuser not working
One more thing.
when I tried to update SU binary file,
I got following:
Downloading manifest .. OKAY!
parsing manifest.. Okay!
Latest Version = 3.0.3.2
Checking installed version .. legacy
Fixing database .. okay!
checking for busybox .. not found
Downloading custom busybox .. okay!
checking md5sum ... okay!
checking current install path .. fail!
Failed to find current installed su binary. Update cannot continue.
Does this mean I have to re-root the KF or just install the su binary file? how to do that?
Thanks!
Download the latest kindle fire utility and rerun it for permanent root.
Known Tricks
If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
Please note: If your device can't be seen in fastboot mode, please make sure to install the drivers packaged with this, as it will show up afterwards. You can use the install_drivers.bat with the device plugged in for this.
Copied from the instructions of the kindle fire utility
Above are the tricks if you get stuck but after root install twrp then install fff
I would assume that your not rooted sounds that way to me.
By the way the yellow triangle will be replaced with the new bootloader a white kindle and a blue fire this will be considered the yellow triangle in the description. Good luck
Install permanent root
Install twrp
Install fff
All should be the newest at this point hopefully
Thanks ThePooch.
So, apparently I have to re-root my KF as for some reason it was not rooted correctly. Right?
I believe so the worst that could happen is it could fail if the file already exists but let's hope it goes fine
tanwar said:
Thanks ThePooch.
So, apparently I have to re-root my KF as for some reason it was not rooted correctly. Right?
Click to expand...
Click to collapse
You don't necessarily have to let KFU do its entire "rooting" process.
If you can get into recovery and you are comfortable with adb, you can follow the "Rooting the stock software" section in this guide...
http://forum.xda-developers.com/showthread.php?t=1638452
to push the 'su' binary into the /system partition and set ownership/permissions.
If you are not comfortable with that, you can use KFU, but it will be doing a lot of extraneous things that you probably don't need.
Under extras you will put on Google frame work and go launcher after you have confirmed bootloader recovery and root note that the market can only be seen using go launcher not the kindle one.
---------- Post added at 12:32 AM ---------- Previous post was at 12:13 AM ----------
The easiest way to test root is to download an app that will request root permissions like root explorer for instance if you open the app and you don't see a dialogue pop up requesting permission its very likely that it isn't rooted.
Read-Only file system
Thanks Kinfauns and ThePooch for tips.
@kinfauns, I tried following the steps given in "Rooting the stock software" section of the given link.
http://forum.xda-developers.com/showthread.php?t=1638452
However, when I tried to push su binary file to system folder
adb push C:\kfu\software\su /system/xbin/
I got following message:
failed to copy 'su' to 'system/xbin/su': Read-only file system.
How can I change the permissions of the folder to copy su file?
I tried using shell command:
adb shell chmod 755 /system
However, I got the same message again "Read-only file system"
Please help!!
nevermind I see your on windows 7 like me. adb shell mount system will mount system to read/ write
its all in kinfauns post you just need to be it recovery to execute the commands I believe I would paste it here but its just as easy to read them from there
adb shell chmod 6755 /system/xbin/su not 755 you can probably safely copy and paste the commands from his post right into cmd he has it written up very nicely
tanwar said:
Thanks Kinfauns and ThePooch for tips.
@kinfauns, I tried following the steps given in "Rooting the stock software" section of the given link.
http://forum.xda-developers.com/showthread.php?t=1638452
However, when I tried to push su binary file to system folder
adb push C:\kfu\software\su /system/xbin/
I got following message:
failed to copy 'su' to 'system/xbin/su': Read-only file system.
How can I change the permissions of the folder to copy su file?
I tried using shell command:
adb shell chmod 755 /system
However, I got the same message again "Read-only file system"
Please help!!
Click to expand...
Click to collapse
I think you may be trying to do this while booted into the system software. That won't work because you don't have root access there and you won't be able to mount (or remount) a partition without those privileges. The rest of it won't work without R/W access to the partition, as you've already seen.
To be clear, the device needs to be booted into recovery (TWRP or CWMR) where you do have root privileges. Make sure you start with step one to get the system partition mounted. If successful, "mount" will provide no output.

[GUIDE][ROOT] Blu Dash 3.5 d170 - Help with recovery and root

Update: New guide is in post # 122
http://forum.xda-developers.com/showthread.php?p=40433602#post40433602
The guide is in post # 98
http://forum.xda-developers.com/showthread.php?p=39362805#post39362805
Hello,
I have a Blu Dash 3.5 and would like to install clockworkmod recovery and enable root access, but so far have not found anything. Could you help me?
thank you
I tried using SuperOneClick, Gingerbreak, zroot but all without success.
Anyone have any other option?
_ _
I managed to set up the android SDK on ubuntu but I get permission denied message when trying to copy the files to the /system
I suppose I have to remount the partition in RW to be able to put the files but no idea how to do this.
_ _
fenrixarena said:
Well you can't without it being rooted, right now I just don't care about it anymore it's just a phone, & $30 isn't worth just freeing up some space. No guarantee that will make it run smoother without crashes either, that could just be a result of interface, so a bit of speed don't seem worth it to me, I have my own ringtones with ringdroid so I'm happy.
Everything having to do with extracting the boot.img requires it to be rooted otherwise I know enough about enough crapola already I could make that all spiffy and zabam if I wanted. I would just literally edit all the img files and provide a simple update.zip given I could get signing to work!
unfortunately I get nothing from fastboot at all, not sure it would help though. oem unlock stuff is all I recall about that besides it being a great wau to flash images to the phone
let me know if you make any progress, I'll put in my effort if you do anything at all that intices me to find a path to progress
Click to expand...
Click to collapse
fenrixarena, hope you get to find any progress on rooting this phone. I also agree with you that it is no worth the time or effort with this kind of phone but I think that the challenge is interesting . In my case I have no idea on how you may root it but I am sure it is possible i guess it all in find another compatible boot.img that can be rooted, right?
Regards,
- -
_ _
What is the address of the site that charges $ 30? We can verify that other users would like to do and split the cost ...
I managed to make root ...
I found the CWM recovery and stock recovery for Qsmart.
I was very curious if it would work in BLU and ended up installing the CWM with fastboot. It did not work, the screen just stays with the BLU and not access the recovery.
Then I installed stock recovery and did not work ...
But I realized that Windows recognized the device connected and I recognized two units with unsupported format.
then returned to the prompt and saw that the ADB was working. I used the command 'adb shell' and to my surprise was how the cursor #
So without wasting time already put su and busybox in /system/ bin and superuser.apk in /system/app, I changed the permissions and restarted the phone. And the root was working perfectly. :victory:
Only one problem, I do not have the recovery installed.
I wonder how I can help you to make root without losing recovery
>>
I use Windowns 7 Pro x64 bits.
I installed the drivers in the SuperOneClick version 2.3.3.
With the drivers installed could use fastboot and adb command.
Turning on the phone + vol - access mode fastboot / bootloader
It would be good to get root without losing the recovery. Because we need him to compile a clockworkmod recovery.
I used the romdump and got the following files:
https://docs.google.com/file/d/0B5rQL4bfhfPRZXhhZkg1Mkx5SHc/edit?usp=sharing
I used the mkfs.yaffs2 to convert the file system.tar for system.img
https://docs.google.com/file/d/0B5rQL4bfhfPRMGdaNnQ4b1RwclU/edit?usp=sharing
This system.img would function on another device?
okay, I am having one problem, what did you type for the permissions?
I've got superuser.apk pushed and the su in the /system/bin but when i try to chmod 777 it returns to -r- after I reboot!
Here's howto manually back up now that I have recovery adb root:
cat /proc/mtd
Then just cat (mtd#) > /sdcard/(image.img)
You can restore via fastboot flash
fenrixarena said:
okay, I am having one problem, what did you type for the permissions?
I've got superuser.apk pushed and the su in the /system/bin but when i try to chmod 777 it returns to -r- after I reboot!
Here's howto manually back up now that I have recovery adb root:
cat /proc/mtd
Then just cat (mtd#) > /sdcard/(image.img)
You can restore via fastboot flash
Click to expand...
Click to collapse
you get root access in adb shell?
send su to /system/bin with permission 6755.
busybox to /system/bin with permission 755.
and superuser.apk to /system/app with 644.
reboot your phone
then download terminal emulator on your phone and enter the command su
if the cursor change to # worked
erickreisbr said:
you get root access in adb shell?
send su to /system/bin with permission 6755.
busybox to /system/bin with permission 755.
and superuser.apk to /system/app with 644.
reboot your phone
then download terminal emulator on your phone and enter the command su
if the cursor change to # worked
Click to expand...
Click to collapse
These are actually good news... Right on!!! Cheers if you manage to root Blu Dash 3.5 :victory:
Can someone guide me on how I can Root my phone? What adb tools do i need?
Regards
az0ik said:
These are actually good news... Right on!!! Cheers if you manage to root Blu Dash 3.5 :victory:
Can someone guide me on how I can Root my phone? What adb tools do i need?
Regards
Click to expand...
Click to collapse
I can upload the cwm.img & adb I used + fastboot. Not all adb.exe will recognize the phone. Also drivers from qsmart for adb bridge.
1 boot holding vol down + power (about 15 sec.)
Fastboot flash recovery cwm.img
Then turn phone off.
Boot holding vol UP + Power (about 15 sec)
Adb push su /system/bin
Adb push busybox /system/bin
Adb push superuser.apk /system/app
adb shell
~# chmod 6755 /system/bin/su
~# chmod 755 /system/bin/busybox
~# chmod 644 /system/app/superuser.apk
reboot your phone
terminal emulator - su
permission granted
IT WORKED!
---------- Post added at 02:21 AM ---------- Previous post was at 02:00 AM ----------
sorry, tomorrow I will upload a zip with the img i used and so forth all in one zip so you can root with that, unless it's here by someone else by then I gotta work!
fenrixarena said:
I can upload the cwm.img & adb I used + fastboot. Not all adb.exe will recognize the phone. Also drivers from qsmart for adb bridge.
1 boot holding vol down + power (about 15 sec.)
Fastboot flash recovery cwm.img
Then turn phone off.
Boot holding vol UP + Power (about 15 sec)
Adb push su /system/bin
Adb push busybox /system/bin
Adb push superuser.apk /system/app
adb shell
~# chmod 6755 /system/bin/su
~# chmod 755 /system/bin/busybox
~# chmod 644 /system/app/superuser.apk
reboot your phone
terminal emulator - su
permission granted
IT WORKED!
---------- Post added at 02:21 AM ---------- Previous post was at 02:00 AM ----------
sorry, tomorrow I will upload a zip with the img i used and so forth all in one zip so you can root with that, unless it's here by someone else by then I gotta work!
Click to expand...
Click to collapse
Thank you so much Fenrixarena!! You are awesome :good::good::good:. I still can believe it, i thought it was a lost hope... I really appreciate for uploading the files I am patient enough to wait another day
Follow the ADB and the recovery I've used.
The drivers installed by SuperOneClick, but have these here:
32 bits - http://www.mediafire.com/?21na032gnzbfza2
64 bits - http://www.mediafire.com/?1hrwo325cb1ej2w
Fx
fenrixarena said:
interesting, I got a cwm4s12.img that's larger(4.51) and because of having a 64bit laptop without 32bit support I had to use a smaller ADB (158kb) to be able to recognize the phone and only on regular usb debugging does superoneclick install drivers which was useless since I needed the drivers to work in recovery.
If those files don't work for you I will upload mine
I got my files from foreign thread, and since I download so many versions and custom versions of programs like adb I'm not sure where it came from !!
oh, and he rooted the phone first, I only did it on a more bothersome platform.
Click to expand...
Click to collapse
the root worked on your phone?
Now we need a recovery. I'm trying to learn how to compile cwm, but it is very complicated.

digix sophix 8" tablet root 840g

hey this took me a few hours, i know a bit about androids and it gave me a hard time... thought i would share:
digix sophix 8" tablet root 840g
1: make sure you install your adb drivers, and your tablet is connected to your pc with usb debug mode on, and install unknown sources on.
2. goto your platform-tools adb dir and copy the attached zip files to that dir..
3. run command prompt navigate to your adb platform-tools dir
4. you could create a script, but i had to do it by hand, run these commands from your dos prompt:
Code:
adb shell mount -o rw,remount /system
adb push superuser.apk /system/app/superuser.apk
adb push su /system/bin/su
adb push su /system/xbin/su
adb shell chmod 7655 /system/bin/su
adb shell chmod 755 /system/bin/busybox
adb shell chmod 644 /system/app/Superuser.apk
adb shell chown root:shell /system/bin/su
adb shell chown root:shell /system/xbin/su
adb shell chown root:shell /system/app/Superuser.apk
adb reboot
i hope that works, cause thats all i should have had to do, and i ended up doing a ton of other things that i didnt need to... i had to re-install google apps, and market cause when i tried to root it i accidentially deleted em somehow....
but that should work.. if not.. you can understand the method of the script, and something can be worked by this im pretty sure!
my neighbor bought this tablet at gamestop.. i rooted it for him.... pissed me off for a while... it would be nice if someone could verify this... thanks!
enjoy!
Can you private message me..i really want to root my new sophix tablet... old methods are not working
does either of your tablets freeze all the time? I tried reflashing and everything went through but it still freezes
deathspankd said:
does either of your tablets freeze all the time? I tried reflashing and everything went through but it still freezes
Click to expand...
Click to collapse
I just got mine, and yeah it has frozen up a couple of times. Not all the time, but still annoying. I might return it if it keeps happening.
This is my first time rooting anything.
I have no idea what the first post means past step 1. Can I get some help?
SanguineNoir said:
This is my first time rooting anything.
I have no idea what the first post means past step 1. Can I get some help?
Click to expand...
Click to collapse
I've made a batch script that should help you. It automatically pushes Superuser and the SU binary to their proper places, fixes permissions, and reboots the device over ADB.
I haven't tested it on my father's 840G yet, so use it at your own risk, but theoretically everything should work.
jerbear294 said:
I've made a batch script that should help you. It automatically pushes Superuser and the SU binary to their proper places, fixes permissions, and reboots the device over ADB.
I haven't tested it on my father's 840G yet, so use it at your own risk, but theoretically everything should work.
Click to expand...
Click to collapse
Hey thank you so much.
However, i'm still confused/cautious.
So I got my ADB drivers from adbdriver but when I start the batch it says: Daemon not running, and then Daemon sucessfully started and then nothing. I left it for 15 minutes but nothing happened...what'd I do wrong?
SanguineNoir said:
Hey thank you so much.
However, i'm still confused/cautious.
So I got my ADB drivers from adbdriver but when I start the batch it says: Daemon not running, and then Daemon sucessfully started and then nothing. I left it for 15 minutes but nothing happened...what'd I do wrong?
Click to expand...
Click to collapse
It didn't recognize the device. How exactly did you install the drivers? It would have proceeded if they were correctly installed.
Go into ADB and type:
Code:
adb devices
If nothing comes up the tablet's not on, not plugged in, or the drivers are incorrectly installed.
Worst case scenario, download TeamViewer and I'll try to help you remotely.
SanguineNoir said:
Hey thank you so much.
However, i'm still confused/cautious.
So I got my ADB drivers from adbdriver but when I start the batch it says: Daemon not running, and then Daemon sucessfully started and then nothing. I left it for 15 minutes but nothing happened...what'd I do wrong?
Click to expand...
Click to collapse
I've linked another version of the batch in my first post in this thread. It's got a command that I believe is causing the issue commented out, as well as a bit more troubleshooting.
Also, there's a thread now that has a 15 second ADB driver installer. If the batch still doesn't work, download it here.
jerbear294 said:
I've linked another version of the batch in my first post in this thread. It's got a command that I believe is causing the issue commented out, as well as a bit more troubleshooting.
Also, there's a thread now that has a 15 second ADB driver installer. If the batch still doesn't work, download it here.
Click to expand...
Click to collapse
Yeah it's not showing up. I installed all the drivers correctly.
I'll grab team viewer and we'll just figure it out tomorrow, Reach me on skype at SanguineNoir
SanguineNoir said:
Yeah it's not showing up. I installed all the drivers correctly.
I'll grab team viewer and we'll just figure it out tomorrow, Reach me on skype at SanguineNoir
Click to expand...
Click to collapse
I would Skype you, but my mic's messed up right now. Once you grab TeamViewer, PM me the computer ID and password and I'll connect to find out what's wrong. Hopefully by then I figure out what's wrong with my mic.
sophix 840G TAB ROOT WORKS!!!!
Baidu root 2.3.9.......rooted mine an then I installed supersu for tablets off play store/ but there are no recoveries or custom ROMs for it

Categories

Resources