Related
I was trying to root my defy with my macbook. I tried superoneclick, but it doesn't work on mac.
I tried z4root on this website [http://forum.xda-developers.com/showthread.php?t=833953]. But it didn't work for me as well it was stuck with "acquiring root shell". But on the website, it said it's compatible with defy.
Does anyone know how to root defy on a mac
Thanks a lot
Even if you could root your defy using a Mac, you'd still need Windows to run RDS lite.
Sucks, I know... but there it is.
On my side I get root with my Mac.
I put a binary on my sdcard, next I execute this binary with adb shell from ''Terminal'' to get root.
Regarding sdb flashing, only way I know it's RSD... But it's a win32 exe.
So I use Virtualbox to launch windows over macos.
This allow me to run RSD like if I was under windows. I flash several sbf without pb !!!
It's late now, but I can put details friday if you are interested.
Being under Linux, I use sbf_flash for flashing and root the phone manually via adb.
Though I don't know about any macos alternatives.
sbf_flash has been updated; there's now a mac os x port, in addition, support has been added for the Defy, Charm and possibly the Atrix.
Click to expand...
Click to collapse
So it's also working for Macos, great.
MisterWB said:
On my side I get root with my Mac.
I put a binary on my sdcard, next I execute this binary with adb shell from ''Terminal'' to get root.
Regarding sdb flashing, only way I know it's RSD... But it's a win32 exe.
So I use Virtualbox to launch windows over macos.
This allow me to run RSD like if I was under windows. I flash several sbf without pb !!!
It's late now, but I can put details friday if you are interested.
Click to expand...
Click to collapse
oh really? thanks a lot
Can u please put down the steps when ur free
MisterWB said:
On my side I get root with my Mac.
I put a binary on my sdcard, next I execute this binary with adb shell from ''Terminal'' to get root.
Regarding sdb flashing, only way I know it's RSD... But it's a win32 exe.
So I use Virtualbox to launch windows over macos.
This allow me to run RSD like if I was under windows. I flash several sbf without pb !!!
It's late now, but I can put details friday if you are interested.
Click to expand...
Click to collapse
Sent from my MB525 using XDA App
Wow! I didn't know about sbf-flash.
Thanks for the heads-up.
My process to obtain root access:
1) connect phone to your mac via usb cable
2) In Finder extract "Getroot.zip" on Desktop for exemple
you should have a Getroot directory now with files inside (su, busybox...)
3) Copy/Paste this "Getroot" directory on root of your sdcard
4) Eject sdcard in Finder
5) push down notification bar on Defy and click "USB..." item
6) Select "none"
7) Check in Defy Settings that "Applications->Developpement->USB debugging" is on
8) On Mac launch Terminal
9) type "adb shell", you should have a "$" prompt
10) type "cd /sdcard/Getroot/"
11) type "sh getroot.sh"
You'll be eject from adb shell, it's normal
12) type again "adb shell", prompt should be "#" now, that mean root privilege !
13) type "cd /sdcard/Getroot/"
14) type "sh copy_rootfile.sh", this copy root file, recovery application and remount script*
15) type "reboot" to reboot phone
16) after reboot don't forget to push down notification bar on Defy and click "USB..." item of your choice
17) Done
Take care that "Settings->Applications->Developpement->USB debugging" mustbe off to boot in recovery mode. In other way you'll get a black screen
Hope I don't make mistake during zipping and writing process !
-----------------------------------------------------
* remount script to use from adb shell or any terminal:
- type "remount rw" to mount /system read-write
- type "remount ro" to mount /system read-only
- type "remount sdcard" to mount /sdcard when usb cable is plug to PC
MisterWB said:
My process to obtain root access:
1) connect phone to your mac via usb cable
2) In Finder extract "Getroot.zip" on Desktop for exemple
you should have a Getroot directory now with files inside (su, busybox...)
3) Copy/Paste this "Getroot" directory on root of your sdcard
4) Eject sdcard in Finder
5) push down notification bar on Defy and click "USB..." item
6) Select "none"
7) Check in Defy Settings that "Applications->Developpement->USB debugging" is on
8) On Mac launch Terminal
9) type "adb shell", you should have a "$" prompt
10) type "cd /sdcard/Getroot/"
11) type "sh getroot.sh"
You'll be eject from adb shell, it's normal
12) type again "adb shell", prompt should be "#" now, that mean root privilege !
13) type "cd /sdcard/Getroot/"
14) type "sh copy_rootfile.sh", this copy root file, recovery application and remount script*
15) type "reboot" to reboot phone
16) after reboot don't forget to push down notification bar on Defy and click "USB..." item of your choice
17) Done
Take care that "Settings->Applications->Developpement->USB debugging" mustbe off to boot in recovery mode. In other way you'll get a black screen
Hope I don't make mistake during zipping and writing process !
-----------------------------------------------------
* remount script to use from adb shell or any terminal:
- type "remount rw" to mount /system read-write
- type "remount ro" to mount /system read-only
- type "remount sdcard" to mount /sdcard when usb cable is plug to PC
Click to expand...
Click to collapse
I am kind of stuck, What do u mean by "USB..." for step 5? Is it usb connection? and for step 6 is it "charge only" for "none"?
I typed "adb shell" in terminal and it was like "command not found".
What should I do now? Btw, thanks for helping
Right, step 5 is "USB Connexion"
and step 6 "Charge only", text may change with language and rom version.
Regarding "adb" it's part of Android SDK: http://developer.android.com/sdk/index.html
So you have to download full SDK kit and install it....
...or use adb executable for mac attached below
On my mac I putted it into /usr/bin
1) In Finder put adb.zip into Download directory
2) In Finder Download directory, extract adb.zip, you'll get an "adb" file
3) Open Terminal
4) Go into Download directory
cd ~/Download
5) Copy adb file into /usr/bin with executable permissions
sudo cp adb /usr/bin/ -> and type your session's password
sudo chmod 755 /usr/bin/adb -> and type your session's password
next you can use "adb shell" like any unix command
Keep me inform
I found the link to download sbf_flash for mac
http://blog.opticaldelusion.org/2011/02/sbfflash-updates.html
[A] How to Root Defy Android OS 2.1 on mac
I tried rooting the defy with z4root and SuperOneClick (using Mono to run it on a mac).
It appears that the z4root no longer works on later firmware updates for the defy, which others confirmed on another forum. For me it got stuck trying to run exploits. Similarly, SuperOneClick hung up during the "waiting for device" phase.
This other thread on xda did work and was super easy to do and I recommend it:
[ROOT] G2x Easy Root for Mac and Linux
http://forum.xda-developers.com/showthread.php?t=1048309
I checked it with "Root Checker Basic" from app store and it is indeed rooted.
beefinit said:
I tried rooting the defy with z4root and SuperOneClick (using Mono to run it on a mac).
It appears that the z4root no longer works on later firmware updates for the defy, which others confirmed on another forum. For me it got stuck trying to run exploits. Similarly, SuperOneClick hung up during the "waiting for device" phase.
This other thread on xda did work and was super easy to do and I recommend it:
[ROOT] G2x Easy Root for Mac and Linux
http://forum.xda-developers.com/showthread.php?t=1048309
I checked it with "Root Checker Basic" from app store and it is indeed rooted.
Click to expand...
Click to collapse
I followed the simple directions in the thread recommended by beefinit. The root.command script that comes with the G2xRootMacLinux_v0.5.zip package appears to have successfully rooted my Defy. The script is designed for a Tmobile LG G2x, but is based on SuperOneClick 1.8, so the fact that is seems to work for the Defy is not that surprising.
Here is the terminal log from when I ran the script:
Last login: Thu May 17 10:41:29 on console
/Downloads/G2xRootMacLinux_v0.5/root.command ; exit;
/Downloads/G2xRootMacLinux_v0.5/root.command ; exit;
Checking for connected device...
Pushing temporary root exploint (psneuter) to device...
2604 KB/s (585731 bytes in 0.219s)
Running psneuter on device...
property service neutered.
killing adbd. (should restart in a second or two)
Waiting for device...
Remounting /system read/write...
remount succeeded
Pushing su to /system/bin/su...
100 KB/s (26324 bytes in 0.255s)
Pushing busybox to /system/bin/busybox...
3162 KB/s (1062992 bytes in 0.328s)
Installing Superuser.apk android application...
775 KB/s (196521 bytes in 0.247s)
Removing psneuter from device...
Rebooting device...
Once device has rebooted you should be rooted.
Press Enter when you're ready to quit:
I'm very new at rooting phones but Superuser app is now installed and I've also installed ROM Toolbox Pro and confirmed that I can get a # prompt via it's Terminal Emulator.
My Defy is an unlocked MB525, Android 2.2.1, System version 34.4.9.MB525.T-Mobile.en.US, Kernel 2.6.32.9-g8431013, Build number 3.4.2-107_JDN-9
I am stuck in the boot loop with standard rom installed.
What I think I did was I edited the png files in the update.zip file. (Used paint)
then i installed the edited rom on my fire with TWRP.
I cleared the cache(s)
Then I rebooted.
When the fire started up i showed the Kindle Fire Logo. (no TWRP or FIREFIREFIRE Triangle)
AND IT STUCK there.
I used the KFU to check it and it says:
ABD:Offline
Boot Status: 4002
Fastboot status: offline
I dont know how to fix this
Please help
Thanks.......
First you need to get the adb working. Based on your post, the KFU doest recognize your KF.
I recommend to configure your PC to use Android composite driver to communicate to KF., then use KFU to do next steps such as installing FFF or recovery tool or ROM.
Sent from my Amazon Kindle Fire using Tapatalk
Try this: http://forum.xda-developers.com/showthread.php?t=1428428
It helped me unbrick my KF when I was stuck in a bootloop this weekend. Hope it helps.
sent from my CommandCenter using xda premium
Thanks But Still Not working
ADB doesnt see my kindle still,
And the program you sent didnt do a thing.
Every option keeps telling me device not found, or just waiting for device.
Can I use push to re copy the photos i edited?
wayoung said:
ADB doesnt see my kindle still,
And the program you sent didnt do a thing.
Every option keeps telling me device not found, or just waiting for device.
Can I use push to re copy the photos i edited?
Click to expand...
Click to collapse
You need to install drivers as ADB Composite, or else you'll probably be stuck there forever. The device not found error is due to a lack of working drivers.
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
and check the adb_usb.ini file in your .android folder in your personal folder
it has to be existent and has to include 0x1949 (i use to add 0x18d1 in a separate line also)
without this folder/file/entries adb will never work !
if they are missing just create this folder and copy the file from c:\kfu\drivers\kindle
Kindle Fire boot loop problem
I still have a boot loop issue with my kindle fire which I just received some days ago (right, I had only 1 day to use it until first the web browser started closing when calling a page, then after repoot, the boot process does not finish, still seeing the kindle fire logo). draining the battery did also not solve the issue.
I installed the android sdk, the usb drivers, configured them and the kindle fire is recognized as device.
Afterwards I installed the Kindle Fire Utility 0.9.3, and tried it, with no success. Here the results:
Activity: kindle fire started (boot logo visible) - plugged it into the pc - started kfu
-------------------------------------------------------------
KFU Screen:
***********************************************
* Kindle Fire Utility 0.9.3 *
***********************************************
1 Bootmode Menu
2 BurritoRoot (Temporary)
3 Install Permanent Root with Superuser
4 Obtain Stock update.zip
5 Install latest TWRP Recovery
6 Install FireFireFire
7 Extras
0 Recheck Device Status
ADB Status: Online
ADB Rooted: No
Boot Status: 0x4000
Please make a selection or hit ENTER to exit
------------------------------------------------------------------------
Now I selected option 1 and tried every boot mode, with similar messages:
Activity: select option 1 (bootmode)
-----------------------------------------------------------------------
KFU screen:
***********************************************
* Kindle Fire Utility 0.9.3 *
***********************************************
1 Normal (4000)
2 Fastboot (4002)
3 Recovery (5001)
0 Recheck ADB/Fastboot Mode
ADB Status: Online
ADB Rooted: No
Boot Status: 0x4000
Please make a selection or hit ENTER to return:
----------------------------------------------------------------------
Activity: typing 2 (fastboot)
----------------------------------------------------------------------
KFU screen
***********************************************
* Activating Fastboot (4002) *
***********************************************
Installing BurritoRoot, Courtesy of Jcase of TeamAndIRC
1054 KB/s (1164225 bytes in 1.078s)
[1] Segmentation fault pm install -r /d...
Activating BurritoRoot...
[1] Segmentation fault am start -W -a a...
Elevating the Shell...
* daemon not running. starting it now *
* daemon started successfully *
/data/local/tmp/BurritoRoot3.bin: not found
mount: Operation not permitted
mount: Operation not permitted
failed to copy 'files\rbfb' to '/system//rbfb': Read-only file system
Unable to chmod /system/rbfb: No such file or directory
Unable to chmod /system/rbfb: No such file or directory
mount: Operation not permitted
mount: Operation not permitted
***********************************************
* Root Activated *
***********************************************
The kindle is successfully running in root mode.
<idme> Invalid permission
reboot: Operation not permitted
The kindle has been told to reboot in Fastboot Mode.
-------------------------------------------------------------------------
Activity: restarting kfu (though it does not return to selection)
-----------------------------------------------------------------------
KFU screen:
***********************************************
* Kindle Fire Utility 0.9.3 *
***********************************************
1 Bootmode Menu
2 BurritoRoot (Temporary)
3 Install Permanent Root with Superuser
4 Obtain Stock update.zip
5 Install latest TWRP Recovery
6 Install FireFireFire
7 Extras
0 Recheck Device Status
ADB Status: Online
ADB Rooted: No
Boot Status: 0x4000
Please make a selection or hit ENTER to exit:
-------------------------------------------------------------------------
--> boot status is still 4000, i.e. no change to fastboot even though the message (which was somehow weird) told this.
Activity: select option 3 (install permanent root)
------------------------------------------------------------------
KFU screen:
***********************************************
* Installing Permanent Root *
***********************************************
Installing BurritoRoot, Courtesy of Jcase of TeamAndIRC
1455 KB/s (1164225 bytes in 0.781s)
[1] Segmentation fault pm install -r /d...
Activating BurritoRoot...
[1] Segmentation fault am start -W -a a...
Elevating the Shell...
* daemon not running. starting it now *
* daemon started successfully *
/data/local/tmp/BurritoRoot3.bin: not found
mount: Operation not permitted
mount: Operation not permitted
failed to copy 'files\rbfb' to '/system//rbfb': Read-only file system
Unable to chmod /system/rbfb: No such file or directory
Unable to chmod /system/rbfb: No such file or directory
mount: Operation not permitted
mount: Operation not permitted
***********************************************
* Root Activated *
***********************************************
The kindle is successfully running in root mode.
mount: Operation not permitted
mount: Operation not permitted
/data/local/tmp/BurritoRoot3.bin: not found
***********************************************
* Root Installed *
***********************************************
Permanent root has been installed.
With great power, comes great responsibility.
Please be careful with how you use root.
It is HIGHLY recommended you have TWRP installed before using root (check your
device's screen for installation instructions).
***********************************************
* Thanks to Jcase *
***********************************************
Please consider donating to jcase by purchasing any of his apps on the market.
...
Or search for "Donate to JCase/TeamAndIR" on the android market.
--------------------------------------------------------------------------
--> after the last action, during the script running, the kindle fire does automatically deactivate and activate the driver on the pc (while the kindle still displays the kindle fire logo).
Does anybody have an idea how I can get this thing up and running again?
if the kf is'nt booting up normally kfu may have problems
i assume you don't have fff & twrp installed - right ?
you can try to install it with option 5
if it says <waiting for device> power it off by holding the pwr button for ~20sec till it turns of - pwr on again - the command should resume and finish
or install manually
tell about the progress
Kindle Fire Stuck in Boot Loop
right, fff and twrp are not installed. I tried option 5, which prompts the following result:
----------------------------------------------------------------
Make sure to follow instructions given to you
recovery.img has been found.
***********************************************
* NOTICE *
***********************************************
Installing TWRP...
If we get stuck here for awhile, power the kindle on and off a few times.
You should also check device manager for "kindle" If so, rerun the driver
installer that came packaged with KFU.
***********************************************
* Activating Fastboot (4002) *
***********************************************
Installing BurritoRoot, Courtesy of Jcase of TeamAndIRC
1774 KB/s (1164225 bytes in 0.640s)
[1] Segmentation fault pm install -r /d...
Activating BurritoRoot...
[1] Segmentation fault am start -W -a a...
Elevating the Shell...
* daemon not running. starting it now *
* daemon started successfully *
/data/local/tmp/BurritoRoot3.bin: not found
mount: Operation not permitted
mount: Operation not permitted
failed to copy 'files\rbfb' to '/system//rbfb': Read-only file system
Unable to chmod /system/rbfb: No such file or directory
Unable to chmod /system/rbfb: No such file or directory
mount: Operation not permitted
mount: Operation not permitted
***********************************************
* Root Activated *
***********************************************
The kindle is successfully running in root mode.
<idme> Invalid permission
reboot: Operation not permitted
The kindle has been told to reboot in Fastboot Mode.
< waiting for device >
----------------------------------------------------------------------
After power-off by holding the power button for sth. about 20 sec. and power on
nothing happens, kfu is still waiting for the device.
how can I install manually?
it's a good practice to move kfu to c:\ and rename it to "kfu" so that it is c:\kfu
- copy recovery.img from c:\kfu\recovery to c:\kfu\tools (check it is ~10mb)
- open a (elevated) command prompt and cd to c:\kfu\tools
- issue "fastboot -i 0x1949 boot recovery.img"
- in case it says <waiting for device> do as in my last post
Kindle Fire Stuck in Boot Loop
I also tried this, but still after power-off and power-on the <waiting for device> does not disappear.
Any other ideas?
what it telling the device manager under android phone ?
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
just reviewed your post - correct me if i'm wrong
- your on stock os 6.2.2
- not rooted
- no fff & twrp
- stuck on "kindle fire" static or animated ?
Kindle Fire Stuck in Boot Loop
The device manager tells me :
Android Composite ADB Interface
I cannot tell the fastboot interface though I am not able to start with fastboot.
Concerning your questions for verification:
- Android OS version: I am not sure which version I have, I didn't check the day I received the device, and the second day it did not boot correct.
- not rooted
- no fff & twrp
- static boot logo, stuck with
could you please try to issue the following commands from command prompt in c:\kfu tools:
"adb devices"
and
"adb shell"
please paste the results
just to verify my guess ...
Kindle Fire Stuck in Boot Loop
sure, the results are:
---------------------------
C:\kfu\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
7864002600000001 device
C:\kfu\tools>
--------------------------------
and
-------------------------------------
C:\kfu\tools>adb shell
$
--------------------------------------
hey cool - thought the shell is messed up - it's not - you can get to fastboot - great
would suggest to follow this thread starting at point 2:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
and your allready downloaded twrp is recovery.img not twrp-blaze-2.0.0RC0.img
simply adapt the corresponding command in the above thread
is you want stock rom i would suggest to use a prerooted stock rom (i prefer the unsecure version):
http://forum.xda-developers.com/showpost.php?p=22393194&postcount=20
Just wondering
Did my changing the stock logo images (png) inside the zip file have anything to do with why the Kindle Fire gets stuck at the logo?
Is there a way with ADB to push the correct images to replace the edited ones?
This seems logical to me as thats what I did and now it is hung on the logo.
Please I'm desperate because Amazon wont even help me cause im canadian
They said they would replace it no problem until I gave my address, and then it was Ohhhh Im msoooo sorry (my butt)
Thanks to all who have responded to the cries of a desperate man.
Update
I have found out that the kindle is mounted read only.
my device now shows
need to know how to change mount to r/w
can i do this with adb?
Kindle Fire Stuck in Boot Loop
hey b63, there is some progress, thank you!
now I have the screen on my kindle where i can select various things, like "advanced settings", "reboot", etc.
how do I install the rom you mention and do I need it to be able to boot without getting stuck again?
wayoung said:
I have found out that the kindle is mounted read only.
my device now shows
need to know how to change mount to r/w
can i do this with adb?
Click to expand...
Click to collapse
yes you can:
"adb remount"
there are also some other commands - try this one first
---------- Post added at 10:49 AM ---------- Previous post was at 10:42 AM ----------
manni4711 said:
hey b63, there is some progress, thank you!
now I have the screen on my kindle where i can select various things, like "advanced settings", "reboot", etc.
how do I install the rom you mention and do I need it to be able to boot without getting stuck again?
Click to expand...
Click to collapse
you should be in twrp now - is this correct ?
it's quite blue - landscape - 8 buttons
if yes resume with point 8 of the description
and yes - i think you have to flash a new rom because your old one seems to be messed up according to your description
Brand new xperia s
6.1.a.0.453
Tried to run as admin, tried compatibilty SP3
Im on windows 7
Installed USB driver from the SDK.
Phone says USB debugging connected.
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (18.12.2012) v17 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
Waiting for device to shop up, if nothing happens please check if Windows ADB-dr
ivers are installed correctly!
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
.
.
Normal Mode enabled!
.
The system cannot find the path specified.
Pushing busybox....
The system cannot find the path specified.
Pushing su binary ....
The system cannot find the path specified.
Pushing Superuser app
The system cannot find the path specified.
Making busybox runable ...
The system cannot find the path specified.
.
The system cannot find the path specified.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
The system cannot find the path specified.
Successful, going to reboot your device in 10 seconds!
Sorted it myself
Had to manually install driver (windows found it itself)
Bin4ry Root tool wont work
bin4ry root tool wont work either...
problem:
================================================== ====================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (18.12.2012) v17 =
================================================== ====================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
then its stuck right there...
@roy8846 and Mang Juan Pedro: check unknown source (setting > security) and USB-Debugging (setting > developer options) on phone
install flashtool, go to C:\Flashtool\drivers and install Flashtool-drivers.exe with all cheked options
Proceeded but not Rooted...
The Bin4ry Rool Tool went on a success but...
MY PHONE AINT ROOTED YET!!!
Maybe Bin4ry Root Tool aint the Answer to my Phone...
Btw, my phone is Cherry Mobile "BLAZE" (Ming Ren a2)
Hello,
My Arc S seems to suffer from the VPN-bug. That's why I am trying to replace a file ('racoon') in the /system/bin directory by a manipulated one. That should solve my problem. Sounds quite simple. But how can I best do that?
I am quite a newbie in this world, but I managed to root my phone, install Ultimate HD 3.0.2 and unlock the bootloader, gratefully using all the knowledge you guys write down in your posts on this forum:good: The exact specs of my phone are at the end of this post.
Here is what I did already, but without luck:
Install Android SDK for Mac in order to get ADB working on my iMac (btw I did the rooting on a windows pc);
Connect phone to USB port (phone is turned ON) and check to see if my phone is there, using the ADB DEVICES command in Terminal. And it is there;
Then try to copy the manipulated racoon-file from the Mac into the /system/bin directory on the phone, using the ADB PUSH command, but I get a read-only file system message;
Thinking the message may be caused by the fact that my bootloader is still locked, I unlocked it (few days after the rooting) using the unlocking code I received from Sonymobile. And it successfully unlocked;
But now I still get the read-only message when using the ADB PUSH command
What am I doing wrong?
Thanks in advance.
Specs:
Sony Ericsson Xperia Arc S (LT18i)
Android 4.0.4
Ultimate HD 3.0.2
2.6.32.9-perf
Unlocked and rooted
A bit further
I've come a bit further following a tutorial I found on the internet (sorry I'm not allowed to post the link as a newbie). It describes how to copy a file, simply by using the phone, instead of adb on the Mac. I am using ConnectBot app on the phone as a terminal. But now I am coping with some syntax problems:
The copy command:
Code:
cp
must be replaced (apparently because of the Busybox version that comes with Ultimate HD 3.0.2), by:
Code:
busybox cp
from what I found out on the internet. And indeed it worked, great!.
But then this:
Code:
chgrp shell racoon
I changed it into this:
Code:
busybox chgrp shell racoon
But it comes with a message that the applet is unknown or something.
So at this moment there is something wrong with the rights to the racoon file and I don't know how to solve it.
Could anyone guide me through this syntax please?
Found it!
Apparently my busybox expects a Group id, instead of Group name. So with the below mentioned statement I managed to execute the code, where 2000 is the id for the group 'shell':
Code:
busybox chgrp 2000 racoon
Btw. the error message was about an unknown group, not applet like I said in my previous post.
Unfortunately the new racoon file didn't solve my problem of not being able to connect through VPN. At least with the original racoon file it tried to connect before an error occured, but with the new racoon file I only get a time-out. No attempts are made to connect.
Just got a "factory refurbished" Kindle Fire 8.9 HD for a STEAL (Amazon gave $50 back on the refurb).
Anyway, now that I have it and have been playing with it for a few weeks, I've realized that the current root methods (including Root Many Android) say they have rooted it, but I don't quite have all the SU access. Digging deeper, I've found that I have System Version 8.4.9.
I can get a partial root, but cannot mount the system to RW
Anyone out there working on the Root of Kindle Fire 8.4.9?
I would just downgrade it and flash a custom rom.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
I would just downgrade it and flash a custom rom.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Stunts,
I'd love to do that, but one of the issues with the current root is I can't use KFFirstAide to do much of anything. I would like to keep the KF as close to stock as I can, as I have kids and the FreeTime app is nice. I'm mostly looking to get the Google Play store up and working.
I've done a search but don't see anything on how to downgrade the KF from 8.4.9 without having root.
What am I missing?
You don't need root. When you initially power the device on it should briefly be detected as a jem device. Download then drivers in my signature and extract them somewhere. Now open the device manager and plug the kindle in while off, when you see the jem device, right click it and hit update drivers, and tell it to look where you extracted mine. If this is windows 8 you will have to disable driver signature enforcement first. If you can manage to get this step completed the rest is simple, it basically involves this: grab a utility like kindle fire first aid and shift + right click it and hit new command window here. With the kindle off and unplugged type
Code:
fastboot -I 0x1949 getvar product
once it says waiting for device plug the kindle in while it is off, it should enter fastboot, from there you can use kffa to downgrade it.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
You don't need root. When you initially power the device on it should briefly be detected as a jem device. Download then drivers in my signature and extract them somewhere. Now open the device manager and plug the kindle in while off, when you see the jem device, right click it and hit update drivers, and tell it to look where you extracted mine. If this is windows 8 you will have to disable driver signature enforcement first. If you can manage to get this step completed the rest is simple, it basically involves this: grab a utility like kindle fire first aid and shift + right click it and hit new command window here. With the kindle off and unplugged type
Code:
fastboot -I 0x1949 getvar product
once it says waiting for device plug the kindle in while it is off, it should enter fastboot, from there you can use kffa to downgrade it.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Tried to downgrade. I can get to fastboot without any issues, but it looks like there are issues with KFFA (I'm using 4.1.87-beta). I get the following when trying to "Completely Restore the KFHD 8.9 8.1.4" (Option 7)
(snipped to the last one for space, all have the final "Unable to establish SSL Certificate)
**********************************************************************
*I Have Fetched The recovery.img - 1 More To Download................*
**********************************************************************
--2014-06-14 13:04:18-- y
<snip> (don't have 10 posts so can't post all the links)
HTTP request sent, awaiting response... 302 FOUND
Cookie coming from address attempted to set domain to dropbox.com
Cookie coming from address attempted to set domain to dropbox.com
Location: (removed as I don't have 10 posts)] [following]
--2014-06-14 13:04:18-- (removed as I don't have 10 posts)
Connecting to address... connected.
ERROR: cannot verify address's certificate, issued by `address High Assurance Server CA':
Unable to locally verify the issuer's authority.
To connect to address insecurely, use `--no-check-certificate'.
Unable to establish SSL connection.
****************************************************************************************
*I Have Fetched The system.img - I Am Ready To Flash The 3 Images......................*
****************************************************************************************
Press any key to continue . . .
target reported max download size of 1006632960 bytes
error: cannot load 'boot.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'recovery.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'system.img': No error
Would You Like To Wipe Data And Cache (y/n) ?
After this, I wipe data and cache and then didn't finish the registration (so I didn't get "pushed" an update, just in case)
Come back up and I'm still in 8.4.9
I've gone in to dropbox and pulled all the images to my computer. Is there a way to move these and get them properly mounted in adb? I'm a relative n00b but getting a bit more comfy in the adb environment and may be able to do it from there, with a bit of help?
Thanks!
Do not actually use KFFA use this method --> http://forum.xda-developers.com/showthread.php?t=2468988
You only need kffa for adb.exe and fastboot.exe ect.
PS. Be sure NOT to to connect to the Internet after until you have OTA blocked, and if you Like you can manually upgrade to what ever firmware you would like, I went back to v848
jmpiv4 said:
Do not actually use KFFA use this method --> http://forum.xda-developers.com/showthread.php?t=2468988
You only need kffa for adb.exe and fastboot.exe ect.
PS. Be sure NOT to to connect to the Internet after until you have OTA blocked, and if you Like you can manually upgrade to what ever firmware you would like, I went back to v848
Click to expand...
Click to collapse
Now I'm stuck in the Kindle Fire boot screen - orange. I got through all the flashes without an issue and unplugged on the final reboot per your instructions. I try to adb to it and there are no devices found.
Edit: Whoops. Was using my old shortcut command keys (arrows) and just changed what flashed to system - forgot to flash to the right places. Trying again!
Illinifan97 said:
Now I'm stuck in the Kindle Fire boot screen - orange. I got through all the flashes without an issue and unplugged on the final reboot per your instructions. I try to adb to it and there are no devices found.
Edit: Whoops. Was using my old shortcut command keys (arrows) and just changed what flashed to system - forgot to flash to the right places. Trying again!
Click to expand...
Click to collapse
Hi guys, thx for all tutorials in this site, but i can't root my Kindle Fire HD 8.9...this is the error
"/system/bin/sh su cannot execute permission denied "
KatanAlive said:
Hi guys, thx for all tutorials in this site, but i can't root my Kindle Fire HD 8.9...this is the error
"/system/bin/sh su cannot execute permission denied "
Click to expand...
Click to collapse
Is your Kindle up and running? I also have a Kindle Fire HD 8.9 and yesterday I downloaded latest update.bin file (8.4.9) from Amazon and updated my Kindle and later rooted it using the manual method described in http://forum.xda-developers.com/showthread.php?t=2069117 thread. It was total success. Just don't miss a single step from that method.
Actually I had my Kindle (ver 8.4.8) rooted before and Google Play installed with the same method but I was having some issues (not because of rooting but because I had been tinkering with the system apps) so decided to update to overcome those glitches. I installed RootKeeper from Google Play and told it to protect my root access during update process but this crap could not. After update I lost my root and now Google Play Store and related services stopped working, as I didn't have root access so couldn't manage to delete their apks from System apps. So I decided to root it again with the same method and I did it, after rooting it again I went to system apps and deleted old apks of Google Play and other related apks. Then I agin installed Google Play using the automatic method mentioned in above thread.
Sorry if this story is irrelevant but I just wanted to share my experience so any one searching for something could find a clue from it. One thing is confirmed here, KFFirstAid can easily install Google Play after 8.4.9 update and the above mentioned manual method can root it successfully. I am not sure about automatic method though.
you have been very usefull! Thx...but, i still can't root with any method
Can i ask you for some help (i've actually the 8.4.9 version) in private?
KatanAlive said:
Hi guys, thx for all tutorials in this site, but i can't root my Kindle Fire HD 8.9...this is the error
"/system/bin/sh su cannot execute permission denied "
Click to expand...
Click to collapse
KatanAlive said:
you have been very usefull! Thx...but, i still can't root with any method
Can i ask you for some help (i've actually the 8.4.9 version) in private?
Click to expand...
Click to collapse
Of course. I am not very knowledgable but I would try my best to share my experience.
akb1ajay said:
Of course. I am not very knowledgable but I would try my best to share my experience.
Click to expand...
Click to collapse
I write you a pm
I just tried the fastboot stuff and it will not enter fastboot. Do i need a fastboot cable?
Also i would like to remove all things kindle aka custom roms. So thats a non issue meaning if the only way to root a hd 8.9 with 8.4.9 rom version that was some how pushed on to my kindle via ota that i had turned off but got turned back on some how. Then thats fine and infact i want to remove amazons crap rom any how.
Nanaki-seto said:
I just tried the fastboot stuff and it will not enter fastboot. Do i need a fastboot cable?
Also i would like to remove all things kindle aka custom roms. So thats a non issue meaning if the only way to root a hd 8.9 with 8.4.9 rom version that was some how pushed on to my kindle via ota that i had turned off but got turned back on some how. Then thats fine and infact i want to remove amazons crap rom any how.
Click to expand...
Click to collapse
Read post 9 on previous page.
akb1ajay said:
Read post 9 on previous page.
Click to expand...
Click to collapse
Already tried this. It works partially only once it is fully done rebooting the kindle fire is running so slowly as to be unworkable for any thing. Also the lock swipe etc looks torn inhalf. At this point i have to use recorvery to get it to respond properly. I need to root or change rom out right (preferably) But the fast boot commands do nothing. Tried getting it to show up as gem device and use the other drivers that are suppose to let me enter fast boot by a fastboot command. It does not seem to work.
So after trying the method in post 9 again i need to recover to factory again. As it is running extremely slow
stunts513 said:
I would just downgrade it and flash a custom rom.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Stunts what is the best surefire way to downgrade? My previously rooted kindlefire hd 8.9 just got ota updated to 8.4.9. I had disabled ota i thought but it would seem it wasnt. Now i can not reroot it properly. I want to just go with a custom rom and be done with this mess. I do not have a fastboot cable. But it would seem there are ways around that such as the fastboot -i etc etc how ever i tried that and it did not work (including getting the drivers to the jem. I think i may be missing the chance to get the update drivers bit done intime (not sure here). At any rate help!!! heh
Again what i want to do
Downgrade to easiest rom ver to flash from to a custom rom using what ever meathod is the most effective minus fastboot cable. also recommendations on rom to use are very welcome.
akb1ajay said:
Is your Kindle up and running? I also have a Kindle Fire HD 8.9 and yesterday I downloaded latest update.bin file (8.4.9) from Amazon and updated my Kindle and later rooted it using the manual method described in http://forum.xda-developers.com/showthread.php?t=2069117 thread. It was total success. Just don't miss a single step from that method.
Actually I had my Kindle (ver 8.4.8) rooted before and Google Play installed with the same method but I was having some issues (not because of rooting but because I had been tinkering with the system apps) so decided to update to overcome those glitches. I installed RootKeeper from Google Play and told it to protect my root access during update process but this crap could not. After update I lost my root and now Google Play Store and related services stopped working, as I didn't have root access so couldn't manage to delete their apks from System apps. So I decided to root it again with the same method and I did it, after rooting it again I went to system apps and deleted old apks of Google Play and other related apks. Then I agin installed Google Play using the automatic method mentioned in above thread.
Sorry if this story is irrelevant but I just wanted to share my experience so any one searching for something could find a clue from it. One thing is confirmed here, KFFirstAid can easily install Google Play after 8.4.9 update and the above mentioned manual method can root it successfully. I am not sure about automatic method though.
Click to expand...
Click to collapse
This worked for getting root back, but didn't initially work for the Google apps. It looks like Amazon filled the file system /system leaving no room for the apps. Since I don't use Text To Speech, I removed /system/tts/ivona/vox_en_us_salli22i which is 100+MB, freeing plenty of space for Google apps. I saved a copy to /sdcard just in case. I recommend saving a copy of system.img first, since my first attempts at removing files deleted the apk, but didn't free the space and I had to do a restore once.
Full Manual Root - Kindle Fire HD 8.9 System Version 8.4.9 on Ubuntu Linux 14.04
Hi Guys,
If none of the usual methods work, here is a method for rooting Kindle Fire HD 8.9 with the new 8.4.9 system version. It was written for and tested on Linux, but should work on Windows as well.
Requires Linux and "DOS" scripting knowledge - particularly if anything goes wrong. If you are not familiar with linux shell, please do not try!
USE AT YOUR OWN RISK!!!
I was struggling a whole day with rooting my Kindle Fire HD 8.9 with the 8.4.9 stock rom. I use Linux (Ubuntu 14.04) and don't really have access to Windows. I've tried several methods, including several versions of the Bin4ry method, but the result was:
a) nothing happened at the end,
b) the system was hell slow, but did not get the root prompt/access.
Finally I've managed to root with a full manual - no script running - method. It was based on Bin4ry v18.5.1 root: the tools were uploaded to the kindle from the package, and the rooting steps were based on the RunMe.bat (manually entering step-by-step). It requires an installed adb on the linux machine (I have it from an Android SDK install)!
Sources:
http://forum.xda-developers.com/showthread.php?t=2277105 : I've started from here. I recommend to read this before starting the process.
http://forum.xda-developers.com/showthread.php?t=2069117 : "C-2) The next steps are used to Root the Kindle - Alternative Method (Manual Version)"
http://pocketnow.com/2012/10/10/root-without-unlocking : for understanding the exploit
Requirements:
1. Install adb on the linux machine.
2. Download Root MANY ANDROID 32-bit!(Dropbox): https://dl.dropbox.com/u/54456659/Win32.zip and extract.
Rooting:
The steps are based on manually entering the commands of the "1)Normal" method of the RunMe.bat:
1) In a terminal change to the directory where Win32.zip was extracted and enter:
Code:
adb push stuff/busybox /data/local/tmp/.
adb push stuff/su /data/local/tmp/.
adb push stuff/Superuser.apk /data/local/tmp/.
adb shell chmod 755 /data/local/tmp/busybox
2) Restore the fake “backup”. Note: _do not click restore on your Kindle device_! Just enter the command into the command prompt on your PC and press the enter key:
Code:
adb restore fakebackup.ab
3) Run the “exploit”:
Code:
adb shell “while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done”
(It will display a lot of "link failed File exists" lines)
4) Now that the “exploit” is running, click restore on your device.
5) Once it finishes, reboot your device. Note: Don’t use your kindle yet, this exploit reboots into emulator mode which will be laggy with a flickering screen (or no display at all). This is normal.
Code:
adb reboot
6) Once rebooted, open a shell:
Code:
adb shell
Check: Once you do step 6, your should have a root shell (your prompt should be #, not $). If it’s not #, start again from step 2.
7) Continue with the steps of the RunMe.bat - now entering the commands in the root shell:
Code:
/data/local/tmp/busybox mount -o remount,rw /system
/data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su
/data/local/tmp/busybox mv /data/local/tmp/Superuser.apk /system/app/Superuser.apk
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
chmod 655 /system/app/Superuser.apk
chmod 755 /system/xbin/busybox
rm /data/local.prop
reboot
Done .
The Method described above didn't work for me.
Tried to do it step by step but the exploit part is not working, gives me a syntax error.
Then i used runme.bat and the exploit seems to work (slow reboot, scrambled kindle logo) but root isn't working properly afterwards.
It's kinda half-rooted now, with SuperSU working and displaying "granted root access..."-messages but if i try to install the play store i'm stuck.
ESexplorer is in root mode, mounted system R/W but when i try to move vending.apk to system/app it fails. No root access it seems
Opening SuperSU results in a failed update process....
Any kind of help is deeply appreciated...
Fixing that syntax error
Toastytwo said:
The Method described above didn't work for me.
Tried to do it step by step but the exploit part is not working, gives me a syntax error.
Then i used runme.bat and the exploit seems to work (slow reboot, scrambled kindle logo) but root isn't working properly afterwards.
It's kinda half-rooted now, with SuperSU working and displaying "granted root access..."-messages but if i try to install the play store i'm stuck.
ESexplorer is in root mode, mounted system R/W but when i try to move vending.apk to system/app it fails. No root access it seems
Opening SuperSU results in a failed update process....
Any kind of help is deeply appreciated...
Click to expand...
Click to collapse
This method worked for me! I also got a syntax error the first time arround but I fixed it by splitting this command (adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done") into 2 separate command 1) adb shell, 2) while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done
After taking away the quotes it worked exactly as described!