so i really need help rooting my htc one vx! im following the tutorial here http://forum.xda-developers.com/showthread.php?t=2203225 but the thing is when i enter recovery mode i get teh red triangle. how do i fix this? please help iv tried other methods but none have worked i really want to have my phone rooted.
To Root HTC One VX
LordXombie said:
so i really need help rooting my htc one vx! im following the tutorial here http://forum.xda-developers.com/showthread.php?t=2203225 but the thing is when i enter recovery mode i get teh red triangle. how do i fix this? please help iv tried other methods but none have worked i really want to have my phone rooted.
Click to expand...
Click to collapse
First Unlock Bootloader And Then Root. :silly:
i have unlocked the phone. but it will not allow me to access the bootloader unless threw other means. while in the bootloader it says tampered followed by unlocked. i cannot seem to figure out what is going on.
How to root htc one vx
HTC One VX comes from the
HTC One series of
smartphones consisting of
high-end specifications, such
as Dual-Core processors and
the latest version of Android
on-board. While we already
have a root guide for the
One VX, another root
method has popped-up on
XDA and to help users root
their devices with this new
method, here we’re
presenting a tutorial
explaining everything you
need to root your device.
So, let’s see how you can
root your HTC One VX
smartphone.
I. Before You Begin:
1. This will void the warranty
of the device. However, you
can reinstate it by unrooting
the device if there’s any
unrooting procedure
available.
2. The following procedure
works on Windows based
PCs only.
II. Downloading
Required Files:
download file. http://forum.xda-developers.com/showthread.php?t=2123359
III. Rooting the HTC
One VX:
1. Place the Root Package
archive on the Desktop of
your PC.
2. Extract files from the
archive to your Desktop.
Don’t launch any files just
yet.
3. Turn ON the USB
debugging option on your
device by heading to
Menu>>Settings>>Developer
options>>USB debugging .
4. Turn OFF the device.
5. Reboot the device into
Fastboot mode. To do so,
simply hold down the
Volume DOWN+Power
buttons together.
6. Once inside the Fastboot
mode, connect the device to
your PC using the USB cable.
7. Open a Command Prompt
Window on your Desktop. To
do that, hold down the Shift
button on your keyboard
and right-click on any empty
area on the screen, then
select Open command
window here .
8. Type in following
command into the Command
Prompt Window:
fastboot flash boot boot.img
9. Once it’s done, issue the
following command:
fastboot reboot
10. Your device will reboot.
Once it boots up, enter the
following command:
adb remount
11. Next, enter following
commands into the
Command Prompt Window
one-by-one. Press ENTER
after each line you type:
adb push Superuser.apk /system/app/
adb push su /system/xbin/
adb shell mkdir /system/bin/.ext
adb push .su /system/bin/.ext/
adb shell chmod 6755 /system/xbin/su
adb shell chmod 6755 /system/bin/.ext/.su
adb shell chmod 777 /system/bin/.ext
adb shell ln -s /system/xbin/su /system/bin/su
adb reboot
12. Your device will reboot
in normal mode.
13. Once it boots up, simply
open the Superuser app
from your App Drawer.
14. Tap the Update binaries
button in the app and let it
do the rest of the work.
15. And you’re all done!
Brilliant! Your device has
been successfully rooted and
the SU binaries have also
been updated. Now load-up
some root-only apps on
your device to realize the
power of root-access!
Related
HTC Hero Root access
By fakker1
1. Download:
1. http://developer.android.com/sdk/download.html?v=android- sdk-windows-1.5_r3.zip
2. http://rapidshare.de/files/47972320/orange-htc-hero-uk-boot.img-28-july-2009.zip.html
2. Install HTC Sync from your HTC device
1. Connect device to computer using USB cable.
2. Mount the SD card from the HTC Alerts Menu (Drag from the top of the screen).
3. Install the sync application from the newly discovered drive in Windows.
3. Extract the two zip files into some folder (separate folders for each zip).
4. Go to the Android SDK folder and open the tools folder.
5. Copy the two files from the boot image zip (1.b) into the tools folder:
1. boot.img.insecure
2. boot.img
6. Shutdown the phone.
7. Press and hold the back key and power on the phone.
This is get you into the fastboot screen (the white screen with three androids at the bottom).
8. Connect the phone to the USB cable if it’s unplugged.
9. On Windows, open cmd.exe (Start -> Run -> cmd.exe -> Enter):
1. Change the directory to the tools directory you’ve created earlier.
2.Run fastboot.exe boot boot.img.insecure from within the tools directory.
Output: downloading 'boot.img'... OKAY
booting... OKAY
3. Now your device will start from the given image with root access.
10. Gain root access:
1. In the phone’s alerts menu, click HTC Sync. This will popup the HTC Sync tool in Windows. Ignore it!
2.In cmd type: adb.exe shell
Output:
#
3. From the prompt you got (#) run the following command to mount the phone’s file system in RW mode:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
11. Add su command to your Phone
1. Run the the following commands in the shell (#) – Run each command separately (don’t just copy-paste all the lines!):
1.cat /system/bin/sh > /system/bin/su
2. chmod 4755 /system/bin/su
12.Reboot the phone by typing reboot in the shell (#).
13. The phone will restart and load the original Android ROM.
14. Enjoy the your Rooted Device
From Android Forum
Perhaps better titled "Alternative method to Root" since I personally had a nightmare just installing HTC Sync and on reading, this method certainly seems more complex than the one here http://forum.xda-developers.com/showthread.php?t=543571
Dayz xx
hummm
sorry but that would lose many n00bs....just like me...
i am going to change the title and let the pubic go for what they think is best.
liamhere said:
sorry but that would lose many n00bs....just like me...
i am going to change the title and let the pubic go for what they think is best.
Click to expand...
Click to collapse
You Noob!
Lol. Just kidding, Yeah i think this title is much better! I've been Rooting Android Devices since the g1 came out so im familiar to all this.
Im still waiting for my HTC Hero to arrive, it should be here any second. Once my dog starts barking, it will probably mean fedex guy is here.
ok so i tried to follow the instructions to get my phone rooted!
but im running into a snag....
im here roughly
Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in
Code:
cd C:\android-sdk-windows\tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next line
Now you are all set to run adb commands
Note: for a list of commands type in 'adb' in cmd
CONGRATS YOU NOW HAVE ADB FULLY RUNNING!
except when i type adb shell i get a "$" instead of a "#" in the next line
im not sure if i did something wrong/installed drivers wrong or what??!! any help would be appreciated!
to get your phone rooted, read the rooting tutorial in the development section.
but, in answer to your question, you are getting the '$' instead of the '#' because you do not have root access in your shell.
to have root access in shell, you need to have installed the rooted img, which will then allow for temporary installation of a custom recovery, which must be pushed while the phone is in recovery mode already. then, you can adb shell to the root prompt
ok im very very new too all this! so i apologize up front for not knowing exactly what your talking about! i have been following this guide to root my phone-
forum.xda-developers(DOT)com/showthread.php?t=532719
(take out the (DOT) and make it .com
some1 on this site refereed it to me because i needed to know how to do EVERYTHING from start to finish!
so i am still stuck any help(detailed very detailed help) would be appreciated!
**THIS IS FOR US WIFI & 3G XOOM**
This guide in no way implies or expresses any warranties.
What you choose to do with your equipment is your sole responsibilty.
________________________________________________________________________________________
SUMMARY
You must already be running Honeycomb 3.2 on your Xoom **DO NOT USE WITH HC 3.2.1. IT HAS BEEN REPORTED TO CAUSE WIFI FAILURES** USE THIS TO ROOT HC 3.2 AND THEN UPDATE TO 3.2.1 USING THIS METHOD.
You will be unlocking your Xoom, if you have not already. This will wipe data so make sure to back everything up that you would like to keep.
You will be performing steps in ADB. If you are not familiar with this, read HERE first.
You will need Xoom USB drivers and Fastboot
You will need the WIFI boot (kernel) partition with rooted stock 3.2 kernel (thanks & credit to, solarnz)
OR You will need the 3G Verizon boot (kernel) partition with rooted stock 3.2 kernel (thanks & credit to, solarnz)
You will need Superuser.apk and su binary to enable functioning root
**Before you get started, make sure the USB Debugging option is enabled in the Settings. Go to Settings --> Applications --> Development -->USB Debugging**
PROCEDURE
Download and unzip files. Place rootboot.img, superuser.apk & su binary in the same place you will open your command window.
Open command window:
Type; adb devices - you should see a long serial number on the screen. If no serial number appears, recheck your adb, sdk & moto usb driver files.
Type; adb reboot bootloader
Type; fastboot oem unlock - and follow the steps on your xoom's screen (You have to accept the terms by pressing the volume down key, and then select 'accept' by pressing the volume up key.)
Allow the xoom to boot up completely and go back into settings and enable USB debugging again.
In the command window on your PC type; adb reboot bootloader - (if xoom does not respond, disconnect from pc and reboot manually by holding vol up + power. then reconnect after fully rebooted)
Type; fastboot flash boot rootboot.img (for WiFi)
OR Type; fastboot flash boot 3Grootboot.img (for 3G Verizon)
Type; fastboot reboot
Allow the xoom to boot completely - your xoom should be in normal operating mode for the remainder of the process.
In the command window on your PC type; adb remount
Type; adb push su /system/bin
Type; adb shell
Type; ln -s /system/bin/su /system/xbin/su (this line starts with lower case "L", like llama)
Type; chmod 4755 /system/bin/su
Type; exit
Type; adb push Superuser.apk /system/app
Thats it...your done!! Unplug the xoom and reboot. Your xoom is now stock rooted. You can now flash ClockworkMod, other kernels and roms. To verify root, download a root user app from the market and run it. You should be prompted to allow superuser permissions.
Mac Only Procedure
You will need fastboot for mac - download HERE
Open a terminal (located in the utilities folder)
Navigate to your sdk/platform-tools folder
Type; ./adb devices - (look for the xoom serial number to show its connected.)
Type; ./adb reboot bootloader
Type; chmod 755 fastboot
Type; ./fastboot oem unlock
Type; adb reboot bootloader
Type; ./fastboot flash boot rootboot.img
Type; ./fastboot reboot
Type; ./adb remount
Type; ./adb push su /system/bin
Type; ./adb shell
Type; chmod 4755 /system/bin/su
Type; exit
Type; ./adb push Superuser.apk /system/app
Disconnect and reboot xoom. Download a root app and test.
If you found this helpfull press the THANKS button.
Excellent write-up, I'll try this when I get a chance.
Been trying to downgrade and then get to the rooted, stock 3.2 using a couple routes shown here. They seem to create an issue with CWM not sticking...
Works great!
I just flashed back to 3.01, re-locked the WiFi Xoom (USA), OTA'd to 3.1 and followed that with the OTA to 3.2. I then unlocked and went thru your rooting procedure and it worked great. All tests indicate a successful root. Thanks for the practical guide!
thanks for the easiest way (i dont have an sd card) ..
one Q; why is this boot file about only 2 mb? the original one is aprx. 8 mb.. are we missing some features by replacing the boot files? or is it completely "stock+root" only ?
_delice_doluca_ said:
thanks for the easiest way (i dont have an sd card) ..
one Q; why is this boot file about only 2 mb? the original one is aprx. 8 mb.. are we missing some features by replacing the boot files? or is it completely "stock+root" only ?
Click to expand...
Click to collapse
It is only a boot partition with rooted stock 3.2 kernel.
Sent from my HD2
[*]In the command window on your PC type; adb remount[*]Type; adb push su /system/bin[*]Type; adb shell[*]Type; ln -s /system/bin/su /system/xbin/su [*]Type; chmod 4755 /system/bin/su [*]Type; exit[*]Type; adb push Superuser.apk /system/app
Click to expand...
Click to collapse
when I type adb remount after completely boot, I've got error device not found !!! any idea??
Hussain Isa said:
when I type adb remount after completely boot, I've got error device not found !!! any idea??
Click to expand...
Click to collapse
Are you in fastboot or is your Xoom booted normally? If you are in fastboot, reboot and let the Xoom load normally.
Wow that was easy... Why cant all android devices be this open and straightforward? Im sooo pissed at HTC with the EVO 3D. Cant wait for the Galaxy S2 to come out
Mad respect to Motorola for getting this one right
And last but not least, Thanks so much to the OP for the great writeup!
jase33 said:
Are you in fastboot or is your Xoom booted normally? If you are in fastboot, reboot and let the Xoom load normally.
Click to expand...
Click to collapse
I tried both, enabled USB debugging.
After the xoom load or in fastboot I get the same error! !!!
Sent from my X10i using XDA App
Hussain Isa said:
I tried both, enabled USB debugging.
After the xoom load or in fastboot I get the same error! !!!
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Are you certain you have unlocked the bootloader?
Sent from my HD2
jase33 said:
Are you certain you have unlocked the bootloader?
Click to expand...
Click to collapse
Its already unlocked, so I skipped the unlocking steps.
I will take another try from the beginning
Sent from my X10i using XDA App
Hussain Isa said:
Its already unlocked, so I skipped the unlocking steps.
I will take another try from the beginning
Sent from my X10i using XDA App
Click to expand...
Click to collapse
If you get an error please post exactly what it says.
Sent from my Xoom
Thanks for the write up. Just got my xoom today and right after I updated to 3.2 I thought that I may have a problem trying to root. Your guide worked perfectly for me. The only issue that I had was reading "ln -s," as "In -s." Yeah that was stupid of me.
droidx1978z4 said:
Thanks for the write up. Just got my xoom today and right after I updated to 3.2 I thought that I may have a problem trying to root. Your guide worked perfectly for me. The only issue that I had was reading "ln -s," as "In -s." Yeah that was stupid of me.
Click to expand...
Click to collapse
Glad to here it! And thanks for pointing that out....I will clarify that in the op for others.
Sent from my HD2
thanks jase33 my problem was with the driver, I re-install it & now rooted
Help... I have been having this same problem with multiple procedures. I have everything as instructed. USB debugging ON, SDK installed on Fedora 15, fastboot in /platform-tools folder. I type the first command (and this is the part that keeps happening despite the method used) "adb reboot bootloader" -- the Xoom reboots to screen desscribed as Motorola logo, centered, with "Starting Fastboot protocol support." in the top left corner. Also, in the terminal I get the message < waiting for device > after typing "fastboot oem unlock" That's it.. That's where I always get stuck. I am able to press power button and vol up to reboot normally. But, I can let it sit here like this with logo showing forever. Am I missing any drivers? As I said I am running Linux (Fedora). When I type "adb shell", I can successfully browse the Xoom filesystem.
SOLUTION: Ran fastboot command as root.
su
fastboot oem unlock
WOW! Thanks jase33 that was painless.
Everything worked great, just as you said it would.
fwempa said:
SOLUTION: Ran fastboot command as root.
su
fastboot oem unlock
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Sounds like you worked it out.
Sent from my HD2
Where did you get fastboot for Linux. I just get my self a xoom today, I'm planning to root it but my laptop is running ubuntu
Sent from my Nexus One using XDA App
fwempa said:
Help... I have been having this same problem with multiple procedures. I have everything as instructed. USB debugging ON, SDK installed on Fedora 15, fastboot in /platform-tools folder. I type the first command (and this is the part that keeps happening despite the method used) "adb reboot bootloader" -- the Xoom reboots to screen desscribed as Motorola logo, centered, with "Starting Fastboot protocol support." in the top left corner. Also, in the terminal I get the message < waiting for device > after typing "fastboot oem unlock" That's it.. That's where I always get stuck. I am able to press power button and vol up to reboot normally. But, I can let it sit here like this with logo showing forever. Am I missing any drivers? As I said I am running Linux (Fedora). When I type "adb shell", I can successfully browse the Xoom filesystem.
SOLUTION: Ran fastboot command as root.
su
fastboot oem unlock
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Reinstall the driver, that will solve your problem
Sent from my Xoom using XDA Premium App
1. Download and install Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe
Link to download: http://www.multiupload.co.uk/YXE6FWLFAR
2. Download and install Android SDK (http://dl.google.com/android/android-sdk_r16-windows.zip)
3. With the phone turned OFF, hold VOLUME UP + VOLUME DOWN and power the phone on. This will put you in bootloader mode
4. Using windows/cmd go to the folder where Android SDK was installed (make sure that the folder android-sdk/platform-tools/ contains fastboot.exe and adb.exe etc....
5. using windows/cmd go to the folder /android-sdk/platform-tools
From this folder try the command "fastboot devices" (do not include ") which should list the device connected to your PC.
6. First we have to unlock bootloader,
use this command to unlock bootloader > fastboot oem unlock
(warning.. you will loose all data)
After the bootloader is unlocked the device will reboot normally.
7. Once normally booted from the command prompt issue the commands given below (after each command press enter button)
Note: you need su and superuse.apk (which can be downloaded from here: https://rapidshare.com/files/1319181583/su.zip)
unzip the downloaded file in the same folder where fastboot.exe exist i.e /android-sdk/platform-tools/
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
Done!... your device is now rooted.
it would be good to note that many people have issues with the initial android driver installation.
if you install the drivers, but the phone doesn't show up after a period of time, open control panel -> system -> device manager and look for any devices that have a yellow triangle error (no driver). right click and open properties, and manually select the driver, not auto! the next screen will give you an option to 'select from a list', do this, and find SAMSUNG, then select the latest drivers.
after this, it can still take a minute or two the first time for drivers to install properly, you usually can see the status of this in the usb system tray icon.
if you rebooted to the bootloader (power vol(+) vol(-)), from the command line, if you type "fastboot devices" it should list a device and serial number. if not, you need to go check your drivers, something is missing. also, don't forget how magical a windows reboot can be at times : )
cancerouspete said:
it would be good to note that many people have issues with the initial android driver installation.
if you install the drivers, but the phone doesn't show up after a period of time, open control panel -> system -> device manager and look for any devices that have a yellow triangle error (no driver). right click and open properties, and manually select the driver, not auto! the next screen will give you an option to 'select from a list', do this, and find SAMSUNG, then select the latest drivers.
after this, it can still take a minute or two the first time for drivers to install properly, you usually can see the status of this in the usb system tray icon.
if you rebooted to the bootloader (power vol(+) vol(-)), from the command line, if you type "fastboot devices" it should list a device and serial number. if not, you need to go check your drivers, something is missing. also, don't forget how magical a windows reboot can be at times : )
Click to expand...
Click to collapse
Hi
Thanks for this note which would help many users.
Hi, noob here.
First of all, thanks for the guide.
I have already unlocked the bootloader about a month ago (up to step 6), but would like to root.
Will my phone lose all data again if I root the phone now? I'm not even sure what this actually does, but would like to learn and mess around with it.
You will not loose data. Rooting gets access your system folders by pushing su and superuser through adb.
Hope it helps.
Sent from my Galaxy Nexus using xda premium
smohanv said:
Note: you need su and superuse.apk (which can be downloaded from here: https://rapidshare.com/files/1319181583/su.zip)
unzip the downloaded file in the same folder where fastboot.exe exist i.e /android-sdk/platform-tools/
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
Done!... your device is now rooted.
Click to expand...
Click to collapse
Did you actually test that with a stock rom?
Because adb root will not work with ITL41F at least.
Code:
./adb root
adbd cannot run as root in production builds
Furthermore the chmod for Superuser.apk is totally bogus. No need to mess with it's permissions.
i think a better way is get su and SuperUser.apk from the developers (ChainsDD) site and install it with a temporary boot CWM to install it.
(these instructions are also from memory And i rooted my one from source, but that's a bit involved)
this would mean instead of step 7 do.
7. Download CWM into the same directory as fastboot
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.4-toro.img (Verizon)
or
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.2-maguro.img (GSM)
Make sure to get the right version for your device.
8. download http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
onto the internal storage of the phone( "sdcard" )
9. With the phone turned OFF, hold VOLUME UP + VOLUME DOWN and power the phone on. This will put you in bootloader mode
10. again using windows/cmd go to the folder /android-sdk/platform-tools
From this folder try the command "fastboot devices" (do not include ") which should list the device connected to your PC.
11. Start CWM (without installing it)
fastboot boot recovery-clockwork-XXX-XXX.img
(use the right filename from step 7)
12. choose install update and select the zip from step 8.
You need to use volume up/down to navigate and power to select.
Thanks go to goroh_kun, ayati and DoomLord. All the usual warnings about attempting to root a phone apply. This works on a phone with build number V16R24C, which is current as of this writing. I can't speak for any later updates.
You will need the following:
Java SDK (required for android dev kit – get the JDK): http://www.oracle.com/technetwork/java/javase/downloads/index.html
ADK: http://developer.android.com/sdk/index.html
ADB driver: http://spf.fmworld.net/oss/usb_driver/f-05d/index.html
F-05D rooting files: http://ayati.cocolog-nifty.com/blog/files/F05Droot.zip
zergRush files (tested with v4): http://forum.xda-developers.com/showthread.php?t=1319653
Optional:
- a terminal application of your choice
- busybox installer from the market
- English versions of the .bat files (remove the .txt extension): http://pastebin.com/RBCWvzES and http://pastebin.com/EQfjpDAM
Part 1, installing the ADB driver:
1. Install the JDK
2. Install the ADK
3. Go to C:\Users\YourUsername\.android and edit the adb_usb.ini file.
4. Add 0x04C5 on a separate line at the bottom. Save and close the file.
5. Reboot the computer or restart adb
6. On the phone, press home, settings, applications – toggle Unknown sources to On.
7. Same place, press development and toggle USB debugging to On.
8. Connect the phone to the PC, and when prompted, navigate to the location where you extracted the ADB driver.
Part 2, rooting the phone:
1. Extract the zergRush and rooting files to the same folder. (put the English versions in the same spot if want to use them instead).
2. With the phone connected and in debug mode, run the f05dsu.bat file (DO NOT RIGHT CLICK AND SELECT RUN AS ADMIN).
3. You first will get asked to go to Settings, Setting my body, Step/activity counter app, Pedometer use, is turned On. Press space after doing that.
4. You will then get asked to toggle the same setting OFF once, then back to ON. After doing that, press space and the phone will reboot
5. Wait for the phone to reboot and connect over USB properly. Press space when ready.
6. Files will be transferred over and the phone rooted. If you don't get any errors, press space and wait for the phone to reboot again.
7. The phone should now be rebooted, and you can install Busybox and Superuser from the market.
I had trouble getting the Busybox installers to work properly at first – the stericson one would wipe su and require re-running the f05dsu.bat, and the jrummy one would simply not start properly. I suggest trying the jrummy16 installer first just to see if it runs. In the end I had to do things manually to get it installed, but once that was done both installers worked fine.
Part 3, optional, installing Busybox manually:
1. If superuser has been lost, re-root the phone.
2. Open up your favorite terminal application and enter the following manually:
Code:
su
soff
mount -o rw,remount /system /system
dd if=/data/local/busybox of=/system/xbin/busybox
chown root.shell /system/xbin/busybox
chmod 04755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/xbin
dd if=/data/local/su of=/system/xbin/su
chown root.root /system/xbin/su
chmod 06755 /system/xbin/su
echo insmod /data/local/lsm_disabler.ko > /system/xbin/soff
chmod 755 /system/xbin/soff
At this point you should be able to do a "which su" and get /system/xbin/su as a response. If you don't get any response, Busybox is not properly installed (start over). Doing a "ls -ls /system/xbin/su" should also NOT return a symbolic link to Busybox – if it does, you'll need to copy over su from /data/local again. The same goes for soff. Once this is done, start up jrummy's Busybox installer to confirm the installed version of Busybox, and upgrade it if you want.
Thanks very much, worked well but sadly I managed to boot loop my phone after rooting it.
Now I need to SIM unlock the phone as the factory unlock code is gone.
F05D rooting
Hi there i have successfully rooted my Fujitsu F05D have root access but I can't seem to loads busy box, I have permission through superuser and it goes through the motions but at the end it says " install unsuccessful".
The files are in the system/bin folder but something is wrong. if I use busy box installer jrimmy16 it just say installing and keeps going and never stops if I got to to scripts and click fix file permissions
" run script" it too just spins round and round..
hmm any hints guys.
Don't do a forced install or whatever it's called, that's how I bootlooped and later SIM locked mine, still yet to send it back haha.
Hello, is this working?? I want to root my Docomo Fujitsu Arrows X F-10.. And also my phone keeps on rebooting Please help.. Any ideas why?
does it work on Fujitsu T-02D?