Hello,
I have a new Fujitsu Stylistic M532 Android Tablet. It would be great if someone could help me to root this tablet.
Which Information are neccessary from the tablet?
Maybe there is a standart process to test?
Please let me know what i can do to try to root the tablet?
Best regards
Sent from my M532 using xda app-developers app
Hello again,
Here are some more information about the tablet
Android 4.0.3
Kernel 2.6.39.4
Nvidia Tegra 3 T30S
MicroSDHC Slot
Mini USB Port
Updating via an external memory card (micro SD card)
Download and copy the system update package onto an external memory card (micro SD card).
Slide the memory card (micro SD card) into your Tablet PC.
Switch your Tablet PC off by one long press of the ON/OFF switch and confirm the question on the shut down with OK.
Switch your Tablet PC on again.
When you see the Android logo on the screen, press the ON/OFF switch and the volume button (increase volume) and keep them pressed for 2 seconds and then release them.
⇒ After a few seconds you reach the Recovery menu.
Info: If the Fujitsu logo appears on the screen, then you have not reached the recovery menu. Repeat the above step until you reach the recovery menu.
Select "apply update from external storage".
Info: Navigate as follows through the menu:
Volume button (increase volume) to select an option above the current option
Volume button (decrease volume) to select an option below the current option
ON/OFF switch to confirm the selection
Follow the instructions on the screen to perform the system update.
⇒ After the system update has completed, you will be in the recovery menu again.
Select "Reboot system now" to finish the system update.
Sent from my M532 using xda app-developers app
I am also considering buying this tablet. Therefor a root manual would be highly appreciated.
Thanks.
OK. I think no one has done the root on this tabet.
Maybe somone could give me a hint what i can try to root this tablet?
I`m ready to try some some procedures
maybe a standart procedure is available for android 4?
Or is the rooting of each device different?
What happens if i try a wrong procedure? I think a recovery of the os should always be possible or not?
Maybe someone could answer some questions
Sent from my M532 using xda app-developers app
I have the same tablet. Have you already tried to root it?
Is there any guide available in the meantime?
Hi,
I also have the M532, it is really great.
Any advise how to root it would be appreciated.
Thanks for any hint.
Sent from my STYLISTIC M532
I have no fujitsu tablet, but the same model Pegatron Chagall. (exactly the same)
this set you can upgrade my Fujitsu tablet?
Rom which includes applications?
I don't think so.
Look at the detailed update procedure from Fujitsu and you will see that the update process is checking the model and version information and refuses to install if they do not match.
You're right, the update package does not work on my tablet (Síragon 4N) ... it's a shame.
However, if there is a method to be root, so if you serve ...
Even this recent tablet market, hopefully get into the right hands and can unlock.
Hey, has anyone managed to root the M532?
Is there anyone I could send my M532 to to have it rooted?
ironxp said:
I have no fujitsu tablet, but the same model Pegatron Chagall. (exactly the same)
Click to expand...
Click to collapse
+1
Could someone download the boot.img and recovery.img from this tablet? We need those files in order to modify the following values in the default.prop file
filero.secure=0
ro.debuggable=1
persist.service.adb.enable=1
Repack the images and flash it using fastboot to get a privileged shell.
After doing that you will be able to root this table using "unlockroot" software
mandraxxx said:
Could someone download the boot.img and recovery.img from this tablet? We need those files in order to modify the following values in the default.prop file
Click to expand...
Click to collapse
All you can find is a .pkg file which you need for an upgrade.
How to download boot and recovery
I would be glad to, but how do I find them and get them copied to get to you?
mandraxxx said:
Could someone download the boot.img and recovery.img from this tablet? We need those files in order to modify the following values in the default.prop file
filero.secure=0
ro.debuggable=1
persist.service.adb.enable=1
Repack the images and flash it using fastboot to get a privileged shell.
After doing that you will be able to root this table using "unlockroot" software
Click to expand...
Click to collapse
Here is the pkg file which you can download on this page
-Script by Bin4ry-
I have a Tablet Chagall / Pegatron / Siragon 4N (the same model as the Fujitsu)
I tell them that I tried several rooting script:
Cube Root for ICS 4.0.3 , Cube Root for ICS 4.0.3 v2 , DROID 3 easy root script v7, Root_with_Restore_by_Bin4ry_v8, Google Nexus 7 ToolKit, NRT_v1.5.3., superclick, El UnlockRoot..
and three do not remember ...
And no I worked ...
today ... was half annoyed, and I happened to search again Bin4ry script and found this:
"Root_with_Restore_by_Bin4ry_v10" and try with this script by several methods ... but nothing ...
(http://forum.xda-developers.com/showthread.php?t=1886460)
Then I found this old script bin4ry original,
But it did not work ...
script "Root para ICS 4.1.A.0.562"
What I did was change a few lines ... why were here on xda forum
Here the modified
*******************************************************************
@echo This is an adapted idea from the methods of
@echo Dan Rosenberg (vulnfactory.org)
@echo -Script by Bin4ry-
echo off
cd data
echo Please plug the device in ADB-Mode
adb wait-for-device
echo Rename /data/local/tmp to be able to create symlink
adb shell mv /data/local/tmp /data/local/tmp.old
echo Trying to create /data symlink
adb shell ln -s /data /data/local/tmp
adb reboot
echo Waiting for device to reboot
adb wait-for-device
adb shell rm /data/local.prop > nul
echo Trying to write value in tablet to prop-file
adb shell "echo \"filero.secure=0\" > /data/local.prop"
adb shell "echo \"ro.debuggable=1\" > /data/local.prop"
adb shell "echo \"persist.service.adb.enable=1\" > /data/local.prop"
echo Rebooting
adb reboot
echo Waiting for device to reboot again
adb wait-for-device
echo Try to remount /system
adb remount
echo Pushing su and Superuser.apk
adb push su /system/bin/su
adb shell chmod 06755 /system/bin/su
adb push Superuser.apk /system/app/Superuser.apk
adb shell chmod 644 /system/app/Superuser.apk
echo Cleanup of the Stuff created while running
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.old /data/local/tmp
adb reboot
cd ..
pause
echo Reboot and done Have fun!
*******************************************************************
Note that the only thing not to run this script to copy the application was Superuser.apk and of course change the privileges ...
Install the "superuser" from the market ... and remove the line copy the superuser, and run the whole script.
It was no root ...
I returned to run the scritp of bin4ry, V10 ... and did you root the tablet seems.
(standard option)
Check and reset the tablet, and was even root ..., delete all tablet for recovery to start once again ... and continued to root ...
But, try to certify and document the process for publishing ... and V10 bin4ry script, we apply "unroot"
Now I could not repeat the process, and I could not do root again ...
... but I notice that in the folder / system, I find the SU ...
If someone wants to try, because only must be sure that you can restart the tablet completely ... so that applications may have the lost ...
I managed to root, unroot after applying ...
I root Bin4ry the script, and then with the same script I unroot (Here)
And now I root with script WkPark (Here)
Try making the tablet fujitsu root with these script, they must work ...
My tablet is a Pegatron \ Chagall \ Síragon 4N, which is exactly equal to the Fujitsu ...
ironxp said:
I managed to root, unroot after applying ...
I root Bin4ry the script, and then with the same script I unroot (Here)
And now I root with script WkPark (Here)
Try making the tablet fujitsu root with these script, they must work ...
My tablet is a Pegatron \ Chagall \ Síragon 4N, which is exactly equal to the Fujitsu ...
Click to expand...
Click to collapse
What a pitty!
Did not work on my M532
I only get following message when i try to run the script rooting.bat
Pushing busybox...
error: device not found
error: device not found
error: device not found
rooting.sh: adb: Invalid argument
[*] Remove old fake files...
error: device not found
error: device not found
rooting.sh: adb: Invalid argument
[*] Restore fake backup...
adb: unable to connect for backup
adb: unable to connect for backup
rooting.sh: adb: Invalid argument
[*] Please look at your device and select RESTORE button!
[*] Waiting ...
error: device not found
error: device not found
rooting.sh: adb: Invalid argument
[*] Running ...error: device not found
error: device not found
rooting.sh: adb: Invalid argument
[*] check /data/local.prop
***** FAIL *****
Please retry again
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
Best regards
quaker75 said:
What a pitty!
Did not work on my M532
I only get following message when i try to run the script rooting.bat
Pushing busybox...
error: device not found
Best regards
Click to expand...
Click to collapse
These errors are not connected in "ADB mode" to your pc
Brother, first try to install the driver of google android sdk, and not those of Fujitsu tablet (if you have one installed, it is best to uninstall and reboot the PC)
Then do a factory reset of the tablet, marking the option to delete all.
*- Active in Developer options, USB debugging, stay active and allow test location. Also active in security, unknown sources.
*- Connect the tablet (verifies that Windows recognizes it as "Android ADB Interface")
*- Run the script WkPark friend, follow the instructions and after two reboots, you will have root access to the tablet.
Performs a shutdown and start at the end and if you can run a new factory restore. Install "Root Check" of the market
*- If you do not succeed, try the same steps but running the script Bin4ry friend, and using the "Special" ... you follow the steps indicated.
Always remember to run a shutdown and startup at the end of each script ...
If you have problems with applications that are lost, do not pay much attention as you can re-run a factory reset or restore the tablet for recovery, for it ready.
I can certify that the script works Bin4ry and also the WkPark
(I have a tablet exactly like yours ... Pegatron / Chagall / Síragon 4N)
Related
going through the entire 1.5 to 2.1 root tutorial to a tee, but once i get to the recovery image, this happens (following is an entire copy/paste of what I went through, incase i did something wrong before i hit the point)
Code:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Lemcott>cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools>adb shell mount -o rw,remount /dev/block/mtdblock3
/system
adb server is out of date. killing...
* daemon started successfully *
C:\android-sdk-windows\tools>adb shell mount -o rw,remount /dev/block/mtdblock3
/system
C:\android-sdk-windows\tools>adb push recovery.img /sdcard
1192 KB/s (3926016 bytes in 3.215s)
C:\android-sdk-windows\tools>adb push flash_image /system/bin/flash_image
448 KB/s (9640 bytes in 0.021s)
C:\android-sdk-windows\tools>adb shell flash_image recovery /sdcard/recovery.img
flash_image: permission denied
C:\android-sdk-windows\tools>
EDIT: I am a complete ass hat. nothing to see here, move a long. mods delete this if you please.
P.S. Everyone else: ALWAYS DOUBLE CHECK BEFORE POSTING FOR HELP. *ahem* now be on your way.
try programming thru fastboot. press call + vol down and select the fastboot option and use this command from the pc
fastboot flash recovery recovery.ing
Sent from my Evil Eris v1.1 using the XDA mobile application powered by Tapatalk
It looks like you forgot the step where you modify the flash_image's permissions
Code:
adb shell chmod 755 /system/bin/flash_image
I had the same thing but I just kept reentering
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
and after maybe 4 iterations it worked.
I have a very simular problem:
(moto droid with android 2.1)
$su
su
Permission denied
Click to expand...
Click to collapse
I have try to use chmod the file but it said permission denied on chmod... please help T_T
note this is rooted, of course, when i'm in the phone type su, it'll pop up ask for me to allow or not, allowed, everything seems fine, but when i try to modify files in /system/etc/wifi (trying to make it work for ad hoc) it said permission denied....(even in su???) I tried in adb and it's the same, very very frustrating, any help is appreciated, Thanks.
edit: here's what it looks like using chmod...
>adb shell chmod 755 /system
unable to chmod /system: Read-only file system
>
Click to expand...
Click to collapse
penthoy said:
I have a very simular problem:
(moto droid with android 2.1)
I have try to use chmod the file but it said permission denied on chmod... please help T_T
note this is rooted, of course, when i'm in the phone type su, it'll pop up ask for me to allow or not, allowed, everything seems fine, but when i try to modify files in /system/etc/wifi (trying to make it work for ad hoc) it said permission denied....(even in su???) I tried in adb and it's the same, very very frustrating, any help is appreciated, Thanks.
edit: here's what it looks like using chmod...
Click to expand...
Click to collapse
make it read/write
penthoy said:
I have a very simular problem:
(moto droid with android 2.1)
I have try to use chmod the file but it said permission denied on chmod... please help T_T
note this is rooted, of course, when i'm in the phone type su, it'll pop up ask for me to allow or not, allowed, everything seems fine, but when i try to modify files in /system/etc/wifi (trying to make it work for ad hoc) it said permission denied....(even in su???) I tried in adb and it's the same, very very frustrating, any help is appreciated, Thanks.
edit: here's what it looks like using chmod...
Click to expand...
Click to collapse
I wouldn't try to flash anything you find here to a Moto Droid.
This is for the HTC Droid Eris.
Otherwise, and if I'm misunderstanding you, good luck with your problem.
archmagus said:
It looks like you forgot the step where you modify the flash_image's permissions
Code:
adb shell chmod 755 /system/bin/flash_image
Click to expand...
Click to collapse
I've been bashing my head in ALL day trying to get past this and finally found this thread! This worked perfectly!
theboo7 said:
make it read/write
Click to expand...
Click to collapse
How should i make is read/write?????
i cant get it to work at all.. need help plz.
Hello Guys
why cant i mount that **** together, i have the root permission, but also i dont..somehow
Code:
Microsoft Windows [version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. Alle rettigheder forbeholdes.
C:\Users\Rasmus H. G. Johnsen>d:
D:\>cd android\tools
D:\android\tools>adb devices
List of devices attached
HT9B7LG00092 device
D:\android\tools>adb shell mount -o rw,remount /dev/block/mtdbloc3 /system
mount: Operation not permitted
D:\android\tools>adb shell
$ ls
ls
sqlite_stmt_journals
cache
sdcard
etc
system
sys
sbin
proc
logo.rle
init.rc
init.goldfish.rc
init.bahamas.rc
init
default.prop
data
root
dev
$ exit
exit
Also if I go on and try to do this:
Code:
D:\android\tools>adb push flash_image /system/bin
failed to copy 'flash_image' to '/system/bin/flash_image': Read-only file system
I know that the flash_image fil and my recovery.img file is in this library and also on my sdcard, but I cant push the gotdamn flas_image file in the /system/bin catalog.
Can some one please help me ?
PS. I have the USB-debugging turned ON.
How do you know that you have root? Or, how did you gain root?
doogald said:
How do you know that you have root? Or, how did you gain root?
Click to expand...
Click to collapse
I have the app called androot from google market, ang i have run it to get root.
wfdi said:
I have the app called androot from google market, ang i have run it to get root.
Click to expand...
Click to collapse
I'm not aware of that app, and cannot find it in the market myself (do you have a link?)
However, one way to check for sure if you truly have root is run the adb command adb shell and, when you get a prompt, type the command "su". If it returns with a "#" prompt (rather than the "$" prompt that you are seeing), then you have root on the phone.
Most people these days root with either jcase's 1click root for eris: https://market.android.com/details?id=net.andirc.erisrooter or they use the procedure here: http://androidforums.com/eris-all-things-root/127861-universal-eris-root-dummies.html
You may be able to use the steps here as well, since you seem pretty comfortable with adb and have that working already: http://androidforums.com/eris-all-things-root/125436-detailed-leak-root-tutorial.html
Guys new I found another solution (tested on u8150)
First make sure that you are rooted first.
Open adb shell
Type in su.
Remount the system partition as read write.
Change the owner of system from root to system via chown root system
the exit the shell and push flash_image to system/
also push clockworkmodrecover.img into the system partion dont forget the last /.
then exit.
use a file manager, I used rootbrowser.apk without a memory card and installed recovery.
with rootbrowser copy flash_image to the bin directory.
don't forget to change the owner back to root to the system partition after you finish with rootexplorer or whatever u use even adb can work.
then the rest follows.
The above works only if your'e rooted and have adb.
Goodluck
haha am a genius Installing ROM +Recover without sdcard on u8150
all you have to do is:-
1. Make sure u have installed clockwork mode recovery on your device and have su binary.
2. Open adb with the device normally on.
3. Remount the data partition as read write using mount remount in adb .
4. use adb and push the cynogenmode.zip or any rom that fits into the data partition using
adb push romname.zip /data/
5. Reboot into clockworkmod recovery using the various options available.
6. This is what to do if you don't have a sdcard.
open adb with phone connected and run
adb shell
mount /data /sdcard
then go back to the main recovery menu and wipe dalvik cache only
then choose update from sdcard
flash your rom and tadaaa.
your'e done.
NB:CAUTION MAKE SURE TO FLASH A ROM THAT DOES NOT WRITE INTO THE DATA PARTION
THIS CAN BE DONE BY LOOKING FOR A FILE CALL UPDATE SCRIPT IN THE zip OF THE ROM U WANT TO INSTALL
Am going to make a post about this later.
Goodluck
Lol, 3 and a half year break between responses.
The problem with flash_image & dump_image is that it doesn't work on devices devices which use emmc (recent phones)and have
mmcblk0
and cat /proc/mtd won't work here either.
This means that you have to use dd to write to this devices.
I wonder how guys determine the partitions to use on such devices, and someone should hint as to what is going on since it seems manufacturers seriously don't want people to exploit their devices.
Mod Edit: Unstickied, placed link in wiki:http://forum.xda-developers.com/wiki/index.php?title=Nexus_One Thanks
This is an alternative approach of rooting the Nexus without touching the bootloader.
-no downgrade neccessary
-no battery modification neccessary
-no messing around with SD card slot
-you don't even have to open your phone...
Working and confirmed for ALL ROMs, including European Vodafone EPF30/FRF91, Korean FRF91, AT&T/T-Mo Stock including FRF91
-------
Credits:
-------
- The Android Exploid Crew:
http://c-skills.blogspot.com/2010/07/android-trickery.html
- Amon_RA
- cyanogen
-------
Notes:
-------
- The exploit wasn't found by me (see credits), I just implemented it as a proof of concept for the Nexus One
- Basically this method should work on all currently known ROM versions.
- I tested it on EPF30, Korean FRF91, Vodafone FRF91, US Stock FRF91.
- As usual when doing this kind of stuff: DO THIS AT YOUR OWN RISK.
- It could even work on other Android devices as long as their system partition is at
/dev/block/mtdblock3/ with yaffs2 file system and there is still some space left on the system partition (without any changes).
-------
Prerequisites:
-------
- Locked Nexus One
- Latest Android SDK incl. USB drivers
- Working ADB
- The file "freenexus.zip"
edit:
get it here:
http://multiupload.com/MVT98F5HBY
or
http://dl.dropbox.com/u/1327667/freenexus.zip
MD5: 947C20222056D7C070733E7FCF85CF15
-------
Step-by-step guide:
-------
1. install android sdk & USB drivers
2. extract the content of the zip file into the tools directory of SDK (i.e. \android-sdk-windows\tools)
-> For all Newbies: Take care that you extract the files directly to the tools folder and don't create a new subdirectory freenexus within tools!!! If you did, delete the folder and extract again!!! Check twice that there is no FOLDER freenexus in your tools directory before you continue!!!
3. open a command prompt (Windows: Start, Run, "cmd", OK; Linux: Terminal)
4. change to SDK tools directory (i.e. cd \android-sdk-windows\tools)
5. connect Nexus to USB and check if debugging mode is activated
(Settings/Application/Development/USB Debugging)
6. run "adb devices" in shell and see if there is a device listed. if not back to step 5 or reinstall USB-drivers
7a. for Windows: run "freenexus.bat" in command shell (this copies the neccessary files to /data/local/tmp)
7b. for Linux or manual installation: run the following commands
Code:
adb push freenexus /data/local/tmp/freenexus
adb push Superuser.apk /data/local/tmp/Superuser.apk
adb push su /data/local/tmp/su
adb push busybox /data/local/tmp/busybox
adb shell chmod 755 /data/local/tmp/freenexus
adb shell chmod 755 /data/local/tmp/busybox
8. run the following commands:
Code:
adb shell
(you should see a "$" prompt now)
cd /data/local/tmp
9. on your phone go to a screen where you can easily toggle wifi (widget or settings/wireless)
10. be prepared to toggle wifi immediately after you execute the next step
11. run
Code:
./freenexus
12. toggle wifi on
13. you should see something like that:
[*] Android local root exploid (C) The Android Exploid Crew
[*] Modified by ak for HTC Nexus One
[+] Using basedir=/sqlite_stmt_journals, path=/data/local/tmp/freenexus
[+] opening NETLINK_KOBJECT_UEVENT socket
[+] sending add message ...
[*] Try to invoke hotplug now, clicking at the wireless
[*] settings, plugin USB key etc.
[*] You succeeded if you find /system/bin/rootshell.
[*] GUI might hang/restart meanwhile so be patient.
13b) if you get "permission denied" error, you have most likely not followed the big red newbie hint after point 2. check this by entering "ls -l", if you see a "drwxr-xr-x" and not "-rwxr-xr-x" in front of the line where freenexus is listed you did not follow properly. Search the posts in the thread on how to correct this.
14. run
Code:
rootshell
15. if you succeeded you will be asked for a password, if not try again from step 10
16. enter the password "freenexus"
17. now you should see a "#" as a prompt -> you are root now
18. run the following commands:
Code:
./busybox cp busybox /system/bin
chmod 4755 /system/bin/busybox
busybox cp Superuser.apk /system/app
busybox cp su /system/bin
chmod 4755 /system/bin/su
rm /system/bin/rootshell
exit
exit
19. Check if you keep root rights:
Code:
adb shell
su
20. after you executed the su command the Superuser app on your device should ask you for allowance
21. you should see the "#" prompt again, if you didn't get that try su again
22. done
-------
Comments:
-------
- General
If you are not planning to wipe your data partition (what you probably will do when installing CM6 first time) you should think about deleting all the temp files still lying in /data/local/tmp (for safety reasons and to have more space on /data):
Code:
adb shell
cd /data/local/tmp
rm busybox
rm su
rm Superuser.apk
rm freenexus
rm flash_image (will only exist if you executed the steps below in recovery section)
- Installation of Custom Recovery
If you only want root rights you are done here. If you want to install custom ROMs you have to install
a custom recovery first. Easiest way would be to download "ROM Manager" from the market. There are plenty of tutorials on how to install custom recovery/ROM at xda.
Edit: It is safer to install the recovery manually. In this case or for those of you running into problems with installing custom recovery with ROM Manager (doesn't stick) you can continue with
these steps (without remount of system partition, now tested successfully):
1) Download recovery-RA-nexus-v1.7.0.1.img to the root directory of your SD-Card
- Note: UnMount your SD-Card after copying these files, but keep your phone plugged in
- or don't mount SD-Card at all and push the file via adb to /sdcard
2) Save file "flash_image" to sdk tools directory:
3) In your terminal run
Code:
adb push flash_image /data/local/tmp/flash_image
adb shell
su
- At this point, it will hang until you choose "Allow" on your phone with the SuperUser app pop-up
- $ should now be replaced with #
5) run the following commands:
Code:
[COLOR="Red"]mount -o rw,remount /dev/block/mtdblock3 /system[/COLOR]
cd /data/local/tmp
chmod 755 flash_image
[COLOR="Red"]./flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.1.img[/COLOR]
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
(and if everything worked fine:)
rm flash_image
Alternatively you can continue with step 9 and then steps 16-24 from the old rooting method tutorial
to manually install Amon_RA's recovery. You will also need the file flash_image for that (link taken from HBOOT thread).
- HBOOT
If you rooted from a Korean Rom or have installed the latest Vodafone Rom via PASSIMG you probably have
HBOOT 0.35 which makes it currently difficult to install Cyanogenmod (there is an assertion failure in the install script, at least with CM6 RC1/2. Maybe future versions of CM6 will include HBOOT 0.35 in the script) or other custom ROMs. (You are still on 0.33 if you just installed the Vodafone OTA Update)
There is a tutorial to revert HBOOT here:
http://forum.xda-developers.com/showthread.php?t=726258
Instead of using the EPF30 image you can also use any other PASSIMG file (at least if it has HBOOT 0.33,
otherwise this step wouldn't make sense...)
Note that when flashing a PASSIMG with a different HBOOT version there is a reboot after the HBOOT has been flashed, then after reboot the PASSIMG will be loaded again and the rest of the image will be flashed.
To check HBOOT and Radio version: press and hold trackball while turning on the phone. To exit select Reboot with Vol+/- and press Power button.
Caution:
After you have reverted your HBOOT, you have lost your root rights and you are back on stock recovery.
But you can (or have to) repeat the above procedure to get root rights back.
Edit:
The downgrading also downgrades your radio!!! Before installing CM6 you have to flash a Froyo Radio!
Latest one can be found here:
http://forum.xda-developers.com/showthread.php?t=723839
-------
Troubleshooting:
-------
After trying to flash a custom ROM with ROM Manager one user wasn't able to boot the phone normally and also no longer able to boot to recovery. In this rare case try to download a compatible PASSIMG file:
For example EPF30 (Europe Vodafone 2.1)
http://shipped-roms.com/shipped/Pas...ogle_WWE_1.14.1700.1_EPF30_release_signed.zip
or FRF91 (Europe Vodafone 2.2):
http://shipped-roms.com/shipped/Pas...on_VF_2.15.151.5_R_FRF91_MFG_Shipment_ROM.zip (<-this one is currently a zip in zip. You have to extract it once to get the working PASSIMG.zip)
(Appropriate US-PASSIMGs can also be found on shipped-roms.com, most likely EPE76)
Rename the file to PASSIMG.zip (case sensitive, Windows users take care that the file isn't called PASSIMG.zip.zip hidden extension)
Copy it to main folder of SD card.
Boot phone into Bootloader mode (press and hold trackball when turning on the phone, until fastboot mode starts)
Select Bootloader mode by pressing power button.
The bootloader should then start to analyse the PASSIMG.zip and ask you afterwards to install it.
You're phone (not your SD) will be completely wiped after the procedure but should work again (and can be rooted again...)
sweet!! been waiting for this! will try it tomorrow as soon as i wake up! will report back then!
edit: i cant download freenexus.zip maybe use another hoster?
file section edited.
Great tutorial ! Waiting for some feedbacks
(file link doesn't work)
dolomiti7 said:
file section edited.
Click to expand...
Click to collapse
On the left I can see just an empty folder named "SmartDrive"
link doesn't work
dolomiti7 said:
-> after clicking on "Smartdrive Gastzugang starten" you might get an error message, but after klicking ok on the error message
you should be able to access the folder "nexus" on the left side of the window anyway
Click to expand...
Click to collapse
No way! Can't do anything even after i press ok on the error message
if you click on that there should be a subfolder "nexus" that should be clickable too. at least it works here... anyway. someone wants to upload the file to a hoster? rapidshare... contact me
for the early adaptors (will only work 10 times):
rapidshare.com/files/409266634/freenexus.zip
MD5: 947C20222056D7C070733E7FCF85CF15
multiple download sites!:
http://www.multiupload.com/MVT98F5HBY
or here:
http://dl.dropbox.com/u/1327667/freenexus.zip
thank you. added the link.
This worked flawlessly.
Massive thanks.
Hi, I have a Italian Vodafone Nexus One with FRF91, i have followed all the steps and now in my apps there is Superuser Permission with green light. It means that i have root rights? Can I install Cyanogen Mod now? Thanks, excuse my English.
Worked perfectly on a stock AT&T N1 with FRF91. Thanks!
Excellent tutorial step by step...great work!
Can i change the password at the end?
So once gaining root, I can flash a custom recovery with rom manager without braking/unlocking the boot loader?
@fc_themaster:
if the superuser app popped up at step 19/20 then you have root rights. you can try to install ROM Manager from the market and install a custom recovery with that porgram. it also needs root rights so superuser should pop up again at that point.
@PSeeCO: you don't need to change a password. the password was only used for the temporary rootshell which you (hopefully) deletetd with the command "rm /system/bin/rootshell" in step 18. From that point on root rights are controlled via the Superuser app. If you install an already rooted custom ROM it is obsolete anyway.
@jivemaster: yes, we can! just use ROM Manager from the market to install custom recovery.
dolomiti7 said:
@PSeeCO: you don't need to change a password. the password was only used for the temporary rootshell which you (hopefully) deletetd with the command "rm /system/bin/rootshell" in step 18. From that point on root rights are controlled via the Superuser app. If you install an already rooted custom ROM it is obsolete anyway.
Click to expand...
Click to collapse
Perfect, thank you so much!
This thread is a collaboration by myself, paxChristos, DooMLorD, & amishxda. Please give credit where credit is due. Thanks.
This method has been confirmed to work on all models of the Xperia PLAY - R800x / R800i / R800a / R800at. Also works perfectly with the Xperia Arc.
WARNING: This doesn't work, however, on the Verizon Wireless R800x v2.3.2. Please update to v2.3.3 before rooting. - confirmed by paxChristos
WARNING #2: Confirmed that this doesn't work with 4.0.2.A.0.62
MAJOR WARNING - ICS (4.x) doesn't work with it & any update to GB (2.3.x) after November 2011 won't either.
paxChristos said:
The exploit used in this toolkit was patched back in November of 2011. No more updates will come from the exploit devs.
Click to expand...
Click to collapse
Thanks to everyone who tested this out for me & confirmed that it worked!
NOTE: Before you attempt to root your phone, please ensure that you have the Android SDK installed. It has the adb binary within it.
Android SDK
http://developer.android.com/sdk/index.html
All needed files have been attached for this process to work correctly.
Note: I didn't create zergRush. I only found the method to implement permanent root after zergRush has done its job.
Automatic Root
1) SuperOneClick
SuperOneClick now has the zergRush method built-in.
Please see the source thread if you have any questions.
Downloads available @ http://shortfuse.org/
Source: http://forum.xda-developers.com/showthread.php?t=803682a
2a) DooMLoRD's Easy Rooting Toolkit [v4] (zergRush Exploit)
This is the one click method that everyone has been asking for & DooMLoRD has answered with this.
DooMLoRD said:
UPDATE: added v4, with newest zergRush binary (21 Nov 2011) and few corrections/additions to script
UPDATE: most companies are patching the exploit in the latest firmwares (Samsung, Motorola, Sony Ericsson, etc)
UPDATE: added v3, with newest zergRush binary (16 Nov 2011) and newer superuser files
UPDATE: added v2, with newest zergRush binary (10 Nov 2011) and newer superuser files
[ support the developers ]
There have now been nearly 440,000 downloads of this easy rooting toolkit for various devices (see list here), and many more if you include variations/different translations, etc that use it.
Don't be a leech, buy me a coffee/beer/etc (and use the "Thanks" button!). Imagine if every user of this tool had donated me even $1...
if you want to support Revolutionary Team (creators of the Exploit which makes this possible ) you can donate to Revolutionary Team's PayPal Donation Link
[ Info ]
(WINDOWS ONLY)
WILL WORK ON BOTH LOCKED & UNLOCKED BOOTLOADER DEVICES!
just download the attached file, extract it using winzip/winrar
go to the folder where its extracted and execute "RUNME.bat"
read and follow the instructions on the screen!
Code:
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
[ Tested on ]
Tested & Reported to be working on the THESE devices
[ Credits ]
Credits go to all those involved in making this possible!
zergRush Binary from: Revolutionary - zergRush local root
Inspired from: http://forum.xda-developers.com/showthread.php?t=1312859
[ Donations ]
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc My PayPal Donation Link
if you want to support Revolutionary Team (creators of the Exploit which makes this possible ) you can donate to Revolutionary Team's PayPal Donation Link
[ Download Links ]
DooMLoRD_v4_ROOT-zergRush-busybox-su.zip <NEW>
DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
DooMLoRD_v2_ROOT-zergRush-busybox-su.zip
DooMLoRD_v1_ROOT-zergRush-busybox-su.zip
[ UnRooting ]
want to unroot? read this
[ Scripts posted by others ]
Rooting script for Linux
Rooting script for MAC OSX
Toolkit for GT-I9000
For Atrix 2
For VIZIO vTab1008
regards,
DooMLoRD
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/showthread.php?t=1319653
My deepest thanks to DooMLoRD for automating & simplifying this process!
2b) amishxda's modified Linux script (based on paxChristos' script // Source: DooMLoRD's Easy Rooting Toolkit)
amishxda said:
Update: Updated as per DooMLoRD's v4.0 script with zergRush binary of 21 Nov 2011 and with makespace which deletes Google Maps if there is not enough space.(< 6MB)
Hello
I am completely new to Android but not at all new to Linux.
I used paxchristos script (ran commands manually though) to root my Sony Ericsson Live with Walkman. (WT19i / Android 2.3.4 / Build 4.0.2.A.0.58)
Source threads used:
http://forum.xda-developers.com/showthread.php?t=1319653
http://forum.xda-developers.com/showthread.php?p=18615502
In an attached file, I fixed/modified/added few things in paxchristos script. Here is the detail:
1) Fixed error in symlinking su. (source/destination were same)
2) Don't delete (and recreate) /data/local/tmp/ directory unnecessarily, just delete its contents
3) Uses dd instead of cp (because DooMLoRD's script does, dont know why!). Update: as per anantshri, dd is used because cp has been known to give errors.
4) If your system already has 'adb' then it uses system 'adb' instead of one in zip-archive.
5) Updated zip archive to contain the latest files from DooMLoRD's archive (paxchristos archive seemed old)
Please try/verify and let me know if I missed something.
Thanks.
Click to expand...
Click to collapse
zergRush_automated_Linux_root.zip
Source: http://forum.xda-developers.com/showthread.php?p=20869699
Original script by paxChristos: http://forum.xda-developers.com/showthread.php?p=18615502#post18615502
Manual Root
3) Noob Friendly Guide
paxChristos has provided me with a very comprehensive guide regarding this process for anyone that absolutely wants a step-by-step layout.
It has been attached to this thread within a 7-zip file. If you would like the faster route, please follow my own instructions.
Download PDF Guide
4) Advanced Android Users (& those that are aiming to be) Guide
Download all required files. Drivers have been provided courtesy of paxChristos for anyone that needs them.
Do the following within a cmd (as administrator) or terminal prompt (through sudo or root user)
Code:
adb shell mkdir /data/local/tmp
adb push zergRush /data/local/tmp
adb chmod 755 /data/local/tmp/zergRush
adb shell
cd /data/local/tmp/
./zergRush
adb remount
adb push su /system/bin
adb push su /system/xbin
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
exit
adb install Superuser.apk
Alternate: adb push Superuser.apk /system/app
installed BusyBox (if it doesn't show up on the system already) via any busybox installer market app
Ran SuperUser & verified settings
Code:
adb reboot
Android should be completely rooted!
Automatic Unroot
DooMLoRD's Unrooting Script
DooMLoRD said:
UNROOTING SCRIPT v1.0
so here is the unrooting script to be USED ONLY AND ONLY IF U HAVE USED MY FILES (Easy Rooting Toolkit) FOR ROOTING
[ WARNING ]
if u have used any other way/solution for rooting then PLEASE DO NOT RUN THIS... you MIGHT END UP with damaged system...
(thats cause some ppl create symlinks for busybox in /system/bin/ which wipes out stock symlinks to /system/bin/toolbox and breaks/damages system)
[ DISCLAIMER ]
I AM NOT TO BE HELD RESPONSIBLE IF U DAMAGE UR PHONE / SPILL UR COFFEE / MISS UR ALARMS / ANY OTHER CALAMITY/MISHAP
REMEMBER YOU ARE DOING THIS AT YOUR OWN RISK
now that the warning is clear (hopefully) lets get to unrooting
Tested on:
Sony Xperia ARC
so here is the file.. (WINDOWS ONLY)
just download the attached file, extract it using winzip/winrar
go to the folder where its extracted and execute "RUNME-UNROOT.bat"
read and follow the instructions on the screen!
Code:
---------------------------------------------------------------
Easy rooting toolkit (v1.0)
UNROOTING SCRIPT
created by DooMLoRD
based heavily on FlashTool scripts (by Bin4ry and Androxyde)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) unroot ur device using special script
(2) remove Busybox and assocaited symlinks
(3) remove SU files and assocaiated data
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
if all goes well u will get output LIKE THIS
regards,
DooMLoRD
DooMLoRD_v1_UNROOTING.zip
Click to expand...
Click to collapse
Sources/Acks/Links/Attachments
Sources:
http://forum.xda-developers.com/showthread.php?t=1312082
http://forum.xda-developers.com/showthread.php?t=1296916
http://androidsu.com/superuser/
Acknowledgments:
Ch4lky - Sony Ericsson Xperia fix for zergRush (Revolutionary Team)
ieftm - zergRush (Revolutionary Team)
Revolutionary Team - many thanks to everyone who worked on zergRush
paxChristos - provided debug info to Ch4lky & created the Noob PDF guide
ChainsDD - Superuser & su
DooMLoRD - for the awesome rooting & unrooting scripts
CLShortFuse - SuperOneClick
Cl8rs - identified possibility for Xperia PLAY to use zergRush
XenonMD - confirmed that this works on the R800i
barlw - confirmed that this works on the R800a
Luniticus - confirmed that this works on the R800at
AndroHero - recommended the alternate method for pushing the Superuser.apk to /system/app for working around stability issues
amishxda - for updating paxChristos' script to work on more phones from Linux
Everyone else - who have confirmed that it works on many other phones
Please let me know any new information to smooth out the process. I'll modify this post to ensure it's a smooth one.
zergRush (no longer attaching due to new updates from the devs) - supports a large amount of phones
https://github.com/downloads/revolutionary/zergRush/zergRush.zip
Superuser v3.0.7 apk
http://goo-inside.me/superuser/Superuser-3.0.7-efgh-signed.zip
su v3.0.3.2 binary
http://goo-inside.me/superuser/su-bin-3.0.3.2-efghi-signed.zip
Thanks!!!
Edit: Please PM me if you were a part of discovery, research or one of the tools listed.
Thanks I wasn't trying to be stuck up or anything, just wanted credit.
Awesome...I've been watching the Zerg thread with bated breath and I didn't have to wait long.
i just wish I had my damn usb cable with me right now.
Big thanks to all involved, I will be trying this asap.
Is there a way to un-root? Just curious...
Step-by-literal-step
If you feel like seeing the step by step PDF Guide, go to these : attached to post #1, or:
At dropbox.com: http://db.tt/RaAUnzjW
At Ubuntu one: http://ubuntuone.com/64OujxgkGMv1N2QSoPmXin
or at Filesonic: http://www.filesonic.com/file/2730341354
If you're doing the script rooting in linux, do these things first
1) Download and unzip file (it's below at dropbox.com or ubuntu one; or it's posted in #1 as an attachment)
2) open up terminal
3) type "su"
4) enter your password
4a) if you don't have su set up
4b) type "passwd"
4c) enter you username password (no, there will be no ***s to show that you entered anything, just hit enter when you've inputted your password)
4d) input a password for root (unix) (no, there will be no ***s to show that you entered anything, just hit enter when you've inputted your password)
4e) type "su" and enter your password
5) navigate to location you unzipped the file to (chrome default download is /home/[your username]/Downloads)
6) type "chmod 755 runme-linux"
7) type "cd files"
8) type "chmod 755 adb"
9) type "cd .."
10) type "./runme-linux"
11) type "exit" x2 to exit terminal
12) enjoy your rooted play!
Here's the script (and all applicable files) (totally ripped off DooMLoRD's code, thank him, please, for me), go to these links:
At dropbox.com: http://db.tt/a4H6QFfV
At Ubuntu one: http://ubuntuone.com/7mD63kpsKzGmaou5hcftBV
Here's the linux script code
Code:
#!/bin/bash
#This is DooMLoRD's script for windows. I've ported it to linux
#Somethings to remember
#1) Chmod this file!! ("chmod 777 runme-linux")
#2) Run this script as su in terminal (if you haven't set up your su password run the command "passwd" in terminal, it'll ask you for your username password, and then you'll type in a root password. NOTE: You will not see any changes (i.e. *** representing typed letters) but the password is still being inputted.
#I skipped all of DooMLoRD's info because I'm using VIM and don't feel like rewritting it
echo "--Starting---"
echo "---Killing the adb server to make sure that there are no problems---"
./files/adb kill-server
echo "---Waiting for Device---"
./files/adb wait-for-device
echo "---Cleaning out any previous zergRush attempts---"
./files/adb shell rm -r /data/local/tmp
echo "---Creating temp folder for zergRush---"
./files/adb shell mkdir /data/local/tmp
echo "---Pushing zergRush---"
./files/adb push ./files/zergRush /data/local/tmp/
echo "---Fixing permissions for zergRush---"
./files/adb shell chmod 755 /data/local/tmp/zergRush
echo "---Running zergRush---"
./files/adb shell /data/local/tmp/zergRush
#If it gets stuck here for a long time then try:
#1)disconnect usb cable and reconnect it
#2)toggle "Usb Debugging" (first disable it then reenable it")
echo "---Device found!---"
./files/adb wait-for-device
echo "---Pushing busybox---"
./files/adb push ./files/busybox /data/local/tmp
echo "---Fixing busybox permissions---"
./files/adb shell chmod 755 /data/local/tmp/busybox
echo "---remounting system---"
./files/adb shell /data/local/tmp/busybox mount -o remount,rw /system
echo "---copying busybox to /system/xbin---"
./files/adb push files/busybox /system/xbin
echo "---fixing ownership and permissions---"
./files/adb shell chown root.shell /system/xbin/busybox
./files/adb shell chmod 04755 /system/xbin/busybox
echo "---installing busybox---"
./files/adb shell /system/xbin/busybox --install -s /system/xbin
echo "---cleaning up---"
./files/adb shell rm -r /data/local/tmp/busybox
echo "---pushing SU binary---"
./files/adb push ./files/su /system/bin/su
echo "---correcting ownership and permissions for SU---"
./files/adb shell chown root.shell /system/bin/su
./files/adb shell chmod 06755 /system/bin/su
echo "---correcting symlinks---"
./files/adb shell rm /system/xbin/su
./files/adb shell ln -s /system/bin/su /system/xbin/su
echo "---Pushing Superuser app---"
./files/adb push ./files/Superuser.apk /system/app/
echo "--cleaning---"
./files/adb shell rm -r /data/local/tmp
echo "---rebooting---"
./files/adb reboot
echo "---All done, your Xperia Play has been rooted by DooMLoRD---"
echo "---This script has been ported by paxchristos!!---"
echo "---If have any questions, feel free to email me @ [email protected]"
[Removed walkthrough because it's in the PDF guide. And the PDF guide has pictures. Pretty, pretty pictures of unicorns. Or command line. You decide.]
Thank you to: cl8rs for stumbling up zergRush,
Ch4lky, ieftm, and the Revolutionary team for making (and updating zergRush)
CrimsonSentinal13 for getting us from adb root to phone rooted!
DooMLoRD for doing the script in windows, and giving me something to work off of!
Have fun people, and enjoy!!
Note: With the stock kernal, we cannot overclock, but you can underclock your cpu
Note2: Drivers were added to the first post (Crimsonsentinal13) for sake of keeping everything simpler added drivers for Xperia Play -- to get them to work (if you don't already have them installed, goto device manager, find the SEMC driver (it might show up as android device or unknown device) then update driver, and point it to this zip (unzipped, of course)
Note3: Android SDK Download link: http://developer.android.com/sdk/index.html
Note4: Unrooting?? Who would want to unroot?? One way I unrooted (using my wife's Casio Commando was to uninstall superuser.apk, and the busybox installer (i know, i didn't get rid of everything) but at that point, unless the Verizon/Phone Company employee is a genius, they won't know whether or not you're rooted
Note5: OTA Updates. We don't know what'll happen. If one comes, DENY until we can figure out what'll happen... Most likely, it'll just lose root (hopefully temporarily, we won't know until we get there) but if it bricks all the rooted Plays, I don't want an angry mob with pitchforks at my or Crimsonsentinals13's doorstep
Note6: Updated guide!! Hopefully I fixed all the errors that were in there before (thank you to all the users that pointed them out to me) and added a few things.
Note6B: Somebody had a problem with a busybox installer not downloading from the android market. attached a free one off android market that I used. I only have guesses why this happened (pm setInstallLocation 2...?) but here one is so you have that option as well...
Note6C:I also attached insecure adb. Insecure ADB is COMPLETELY OPTIONAL and should only be downloaded and installed AFTER YOU HAVE ROOT if you want to use root in adb after you reboot. Again COMPLETELY OPTIONAL and you won't necessarily need it.
Note7: As jeffkhlam found out, at no point do you need fastboot. This doesn't unlock the bootloader (no custom roms.)
Note8: If you're having issues doing this, I'll be hopping on and off the thread between 8:00am until about 11:00pm Central Standard Time. If it's not between those hours, please wait, we'll get around to helping you!
Will it work with a locked bootloader
doua27 said:
Will it work with a locked bootloader
Click to expand...
Click to collapse
Yep. My Xperia PLAY is brand new & I got it to work w/o unlocking the bootloader.
I think you forgot the Windows driver you mentioned....
sorry, i was doing it all in linux, and i forgot them they're updating in 5 seconds...
I keep getting "Cannot copy boomsh, : Permission denied" at step 16 Help?
CrimsonSentinel13 said:
All needed files have been attached.
Download all required files.
Do the following within a cmd or terminal prompt
Code:
adb shell mkdir /data/local/tmp
adb push zergRush /data/local/tmp
adb chmod 755 /data/local/tmp/zergRush
adb shell
cd /data/local/tmp/
./zergRush
adb remount
adb push su /system/bin
adb push su /system/xbin
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
exit
adb install Superuser.apk
installed BusyBox (if it doesn't show up on the system already) via any busybox installer market app
Ran SuperUser & verified settings
Code:
adb reboot
Android should be completely rooted!
Sources:
http://forum.xda-developers.com/showthread.php?t=1312082
http://forum.xda-developers.com/showthread.php?t=1296916
http://androidsu.com/superuser/
Acknowledgments: Ch4lky, ieftm, paxChristos, ChainsDD, Cl8rs
Please let me know any new information to smooth out the process. I'll modify this post to ensure it's a smooth one.
Click to expand...
Click to collapse
So if i do this and root the device but still locked bootloader does that mean that i cant install cyanogenmod?
But can used root applications?
garner said:
So if i do this and root the device but still locked bootloader does that mean that i cant install cyanogenmod?
But can used root applications?
Click to expand...
Click to collapse
Yes that's correct it's only for root apps etc. You need to unlock your bootloader for flashing custom roms and kernels. So no CyanogenMod without unlocking your BL.
Regards Dousan...
Is this is also the correct steps for r800i's ?
I'm on 2.3.3 with my r800i , i won't lose anything using this method, with a locked bootloader, just want/need root access lol
Cl8rs said:
I keep getting "Cannot copy boomsh, : Permission denied" at step 16 Help?
Click to expand...
Click to collapse
Same thing here....
CoconutWillie said:
Same thing here....
Click to expand...
Click to collapse
I think he forgot a 'cd' in step 16:
cd /data/local/tmp/zergRush 'enter'
Regards Dousan...
Alright, so after numerous tries i finally got my phone rooted. Big thanks for all the instructions.
Cl8rs said:
I keep getting "Cannot copy boomsh, : Permission denied" at step 16 Help?
Click to expand...
Click to collapse
Make sure that /data/local/tmp has permissions to give you full access.
tekken179 said:
Is this is also the correct steps for r800i's ?
I'm on 2.3.3 with my r800i , i won't lose anything using this method, with a locked bootloader, just want/need root access lol
Click to expand...
Click to collapse
I don't know how it works with the R800i. Please try it & let us know how it works.
Dousan said:
I think he forgot a 'cd' in step 16:
cd /data/local/tmp/zergRush 'enter'
Regards Dousan...
Click to expand...
Click to collapse
zergRush isn't a directory, it's a binary. Using the cd command won't work on it.
See the guide I posted, now has info to get past annoying stutters
Anybody stuck at step 16, input the following commands
1) cd /data/local/tmp
2) rm boomsh
3) rm sh
4) continue on with rooting!
Sent from my R800x using XDA App
Just in case someone is
This page details how to root the Fujitsu Arrows TAB F-01D.
http://arrowstab-f01d.blogspot.com/2012/03/easy-rooting-toolkit-for-arrows-tab-f.html
it works.
Now if only somebody can post the firmware updates..
English instructions
Well, with some help from Google Translate and some creative interpretations, I managed to do this and thought I'd provide some English instructions for others (with some added comments)
DISCLAIMER: AS USUAL, YOU SHOULD KNOW THAT FOLLOWING THESE ACTIONS (AND ESPECIALLY FOLLOWING THEM INCORRECTLY) CAN BRICK YOUR DEVICE (I.E. YOUR DEVICE WILL STOP WORKING, POSSIBLY PERMANENTLY). I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY ARISE FROM YOU FOLLOWING THESE INSTRUCTIONS, YOU DO SO AT YOUR OWN RISK.
Downloads
1. Windows -- the Arrows TAB USB driver Download.
2. Easy rooting toolkit (ERT) for Arrows Tab F-01D (ver 1.0) Download
3. goroh_kun's lsm_disabler.ko Download
Info
4. A su binary, such as the one found in DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
5. Android SDK platform tools. adb(.exe) (and in Windows, specifically: AdbWinApi.dll, AdbWinUsbApi.dll)
Preparation
1. Unzip ert4F01D.zip, and in the subdirectory 'files' place:
* adb.exe (Windows only, from step 4 above)
* AdbWinApi.dll (Windows only, from step 4 above)
* AdbWinUsbApi.dll (Windows only, from step 4 above)
* lsm_disabler.ko (from step 3 above)
* su (from step 5 above)
2. Before connecting the USB, in Settings -> Applications -> Development:
* Check (tick) USB debugging ("Debug mode when USB is connected")
* Check (tick) Stay awake ("Screen will never sleep while charging")
3. Set up the USB drivers and Android Development stuff if you haven't already. I don't use Windows so can't help with this.
The Dirty Work
At this stage, you can run the batch file. Since I don't use Windows, I did the steps by hand, so you'll have to correlate your actions appropriately (I can't read Japanese either, so your guess is as good as mine ).
1. On your PC:
adb shell "mv /data/local/calib.dat /data/local/calib.dat_"
adb shell "ln -s /data/local.prop /data/local/calib.dat"
2. On the tablet, go into Google Maps, touch the GPS icon ("locate me" icon) on the top right hand corner, and then touch the BACK key to exit.
3. On your PC:
adb shell "echo ro.kernel.qemu=1 > /data/local.prop"
adb shell "rm /data/local/calib.dat"
adb shell "mv /data/local/calib.dat_ /data/local/calib.dat"
adb reboot
5. Once the device has fully rebooted, on your PC:
adb shell "mkdir /data/local/lib"
adb push files\lsm_disabler.ko /data/local/lib/
adb shell "insmod /data/local/lib/lsm_disabler.ko"
adb shell "mkdir /data/local/bin"
adb shell "echo '#!/system/bin/sh' > /data/local/bin/autoexec.sh"
adb shell "echo '/system/xbin/soff' >> /data/local/bin/autoexec.sh"
adb shell "chmod 755 /data/local/bin/autoexec.sh"
adb shell "mount -o rw,remount /system /system"
adb shell "ln -s /data/local/bin/autoexec.sh /system/etc/install-recovery.sh"
adb push files\su /system/xbin/
adb shell "chown root.root /system/xbin/su"
adb shell "chmod 06755 /system/xbin/su"
adb shell "echo insmod /data/local/lib/lsm_disabler.ko > /system/xbin/soff"
adb shell "chmod 755 /system/xbin/soff"
adb shell "mount -o ro,remount /system /system"
adb shell "echo > /data/local.prop"
6. I think at this point I was just meant to exit the lock screen.
7. adb reboot
8. Congratulations. You're now rooted. Go to the Play Store and download "Superuser" (by ChainsDD) and "BusyBox" (by Stericson). If you decide to buy BusyBox Pro, do not check the "symlinks" option in version 8.0, otherwise it's game over (no wifi, no adb shell, no root, no remount). It's a pain, but not impossible to repair this situation, see http://forum.xda-developers.com/showthread.php?p=26964465. I've emailed the author and I hope future versions won't trash the system so easily.
After all this, I'd suggest download Titanium Backup for Root users, backing everything up, and uninstall the all the bloatware that came with the device. Read up elsewhere about Titanium Backup.
Let me know if this helped you! Not sure how many other English speakers are using this device
Thank you for this wonderful post! A few questions:
1.) I use the F-01D but I don't live in Japan. One of the gripes I've been having about this tablet is that there doesn't seem to be anyway for me to get firmware updates unless I go there. Once rooted am I able to use Market Enabler to fake a carrier and update my tablet?
2.) This is slightly off on a tangent but since I can't find much English material about this tablet anway I might as well ask here. Another one of my gripes about the tablet is it doesn't seem to handle video very well. even 720p video doesn't play smoothly on it. On most of the software I download, it seems hardware acceleration is not enabled? Is this a hardware issue, or is it blocked by the software. And if the latter would rooting the tablet help resolve this issue; or is there any other solution? From what I've read the OMAP processor in this thing should easily be able to handle 1080p video right?
Many thanks! :good:
Kinslayer81 said:
Well, with some help from Google Translate and some creative interpretations, I managed to do this and thought I'd provide some English instructions for others (with some added comments)
DISCLAIMER: AS USUAL, YOU SHOULD KNOW THAT FOLLOWING THESE ACTIONS (AND ESPECIALLY FOLLOWING THEM INCORRECTLY) CAN BRICK YOUR DEVICE (I.E. YOUR DEVICE WILL STOP WORKING, POSSIBLY PERMANENTLY). I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY ARISE FROM YOU FOLLOWING THESE INSTRUCTIONS, YOU DO SO AT YOUR OWN RISK.
Downloads
1. Windows -- the Arrows TAB USB driver Download.
2. Easy rooting toolkit (ERT) for Arrows Tab F-01D (ver 1.0) Download
3. goroh_kun's lsm_disabler.ko Download
Info
4. A su binary, such as the one found in DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
5. Android SDK platform tools. adb(.exe) (and in Windows, specifically: AdbWinApi.dll, AdbWinUsbApi.dll)
Preparation
1. Unzip ert4F01D.zip, and in the subdirectory 'files' place:
* adb.exe (Windows only, from step 4 above)
* AdbWinApi.dll (Windows only, from step 4 above)
* AdbWinUsbApi.dll (Windows only, from step 4 above)
* lsm_disabler.ko (from step 3 above)
* su (from step 5 above)
2. Before connecting the USB, in Settings -> Applications -> Development:
* Check (tick) USB debugging ("Debug mode when USB is connected")
* Check (tick) Stay awake ("Screen will never sleep while charging")
3. Set up the USB drivers and Android Development stuff if you haven't already. I don't use Windows so can't help with this.
The Dirty Work
At this stage, you can run the batch file. Since I don't use Windows, I did the steps by hand, so you'll have to correlate your actions appropriately (I can't read Japanese either, so your guess is as good as mine ).
1. On your PC:
adb shell "mv /data/local/calib.dat /data/local/calib.dat_"
adb shell "ln -s /data/local.prop /data/local/calib.dat"
2. On the tablet, go into Google Maps, touch the GPS icon ("locate me" icon) on the top right hand corner, and then touch the BACK key to exit.
3. On your PC:
adb shell "echo ro.kernel.qemu=1 > /data/local.prop"
adb shell "rm /data/local/calib.dat"
adb shell "mv /data/local/calib.dat_ /data/local/calib.dat"
adb reboot
5. Once the device has fully rebooted, on your PC:
adb shell "mkdir /data/local/lib"
adb push files\lsm_disabler.ko /data/local/lib/
adb shell "insmod /data/local/lib/lsm_disabler.ko"
adb shell "mkdir /data/local/bin"
adb shell "echo '#!/system/bin/sh' > /data/local/bin/autoexec.sh"
adb shell "echo '/system/xbin/soff' >> /data/local/bin/autoexec.sh"
adb shell "chmod 755 /data/local/bin/autoexec.sh"
adb shell "mount -o rw,remount /system /system"
adb shell "ln -s /data/local/bin/autoexec.sh /system/etc/install-recovery.sh"
adb push files\su /system/xbin/
adb shell "chown root.root /system/xbin/su"
adb shell "chmod 06755 /system/xbin/su"
adb shell "echo insmod /data/local/lib/lsm_disabler.ko > /system/xbin/soff"
adb shell "chmod 755 /system/xbin/soff"
adb shell "mount -o ro,remount /system /system"
adb shell "echo > /data/local.prop"
6. I think at this point I was just meant to exit the lock screen.
7. adb reboot
8. Congratulations. You're now rooted. Go to the Play Store and download "Superuser" (by ChainsDD) and "BusyBox" (by Stericson). If you decide to buy BusyBox Pro, do not check the "symlinks" option in version 8.0, otherwise it's game over (no wifi, no adb shell, no root, no remount). It's a pain, but not impossible to repair this situation, see http://forum.xda-developers.com/showthread.php?p=26964465. I've emailed the author and I hope future versions won't trash the system so easily.
After all this, I'd suggest download Titanium Backup for Root users, backing everything up, and uninstall the all the bloatware that came with the device. Read up elsewhere about Titanium Backup.
Let me know if this helped you! Not sure how many other English speakers are using this device
Click to expand...
Click to collapse
Just wanted to say thank you again. The rooting worked perfectly, though it took me a while to manually type in all the commands. For people who want to try this, you do need to install busybox before any other programs such as rootchecker will properly verify that your device is actually rooted.
And just for anyone wondering - rooting and using MarketEnabler has NOT been able to resolve the issue of not being able to update the software overseas...
Hey, sorry for the late reply, busy times :>
Glad the post helped you! I know I was super amped to finally get rood and get rid of all the bloatware I couldn't even understand. Things have definitely been a lot smoother since then (but far from perfect, also dying for an ICS upgrade). As for your questions:
simzhewei said:
1.) I use the F-01D but I don't live in Japan. One of the gripes I've been having about this tablet is that there doesn't seem to be anyway for me to get firmware updates unless I go there. Once rooted am I able to use Market Enabler to fake a carrier and update my tablet?
Click to expand...
Click to collapse
From playing around, the requirements seem to imply that you *have to* upgrade via cellular data from a Docomo SIM card, and it can't be done via roaming, so yeah, it seems like you have to physically go to Japan to upgrade Your market enabler idea was a good one, but since you tried that (I'm assuming using the Docomo info), I guess the upgrade app is using a different source to check where you're at. Ultimately we need to somehow get hold of an update.zip (or other file) that can be run through the Recovery system (which does exist!).
2.) This is slightly off on a tangent but since I can't find much English material about this tablet anway I might as well ask here. Another one of my gripes about the tablet is it doesn't seem to handle video very well. even 720p video doesn't play smoothly on it. On most of the software I download, it seems hardware acceleration is not enabled? Is this a hardware issue, or is it blocked by the software. And if the latter would rooting the tablet help resolve this issue; or is there any other solution? From what I've read the OMAP processor in this thing should easily be able to handle 1080p video right?
Click to expand...
Click to collapse
Haven't tried 1080p, but after some tinkering I did get 720p playing. I use MX Player, and although they said it would download needed hardware decoders automatically, it didn't, and things improved a lot after I downloaded the MX Player ARMv7 codec. Video plays great, but to get sound, I had to run the sound through the software decoder (just tap the music note icon, and choose "Track #1 (S/W decoder)".
On the other hand, I found the hardware decoding often gets stuck (relaunching MX player just gives you a waiting indicator forever)... and the only way to fix it is a reboot. Since this happens quite often, it's incredibly annoying, and I'm hoping an upgrade will fix it. Let me know if this doesn't happen to you. Also have some very intermittent wifi issues, some things work fine (speedtest, etc) but apps like streaming radio, some work fine (spotify) and others don't work at all (di radio). Some things work fine for a while after a reboot.
---------- Post added at 10:02 AM ---------- Previous post was at 10:00 AM ----------
Incidentally, here's what happens if I try update via recovery (with no update files). Maybe it will help someone. Googling most of the stuff came up with nothing. The ** in the middle somewhere is stuff I couldn't read, guess I should go back and do it again but this is from quite a while ago.
Code:
C_L1_043
2.6.35.7
V19R36D
=======================
SD Downloader
=======================
Device SW Downloading...
Don't remove
the SD Card & the Battery.
checking battery
eMMC SD mount complete.
microSD mount complete.
Firm name :
Firm name :
Target:
Check eMMC(SD).
Firm name :
Update GANG file not found
File open error!
**ddl Touch Firm Write start
Firm name :
/external_sd/I2C_HSSP_Bridge_Parallel.cyacd file not found
firm name :
/sdcard/I2C_HSSP_Bridge_Parallel.cyacd file not found
#sddl touch firm not found ret: 1
SKIP sddl launch firm write end ret: 1
SD : SdFgldfirmwrite -------
firm name :
BAC_H_19.enc =
firm name :
BAC_H_1.9.enc =
error
SKIP sddl fgic firm write end ret: 1
end
****************************
****************************
****
All firmware not found!
****
Interesting situation...
First off...Kinslayer81, thanks for posting this. I found the original in Japanese, and was not eager to try to translate it. Thanks for putting in the work.
For everyone (especially if you got this to work) - when I went through the step, I keep getting a "permissions denied" message. Whether it's the ERT4F01D batch file, or typing the commands in... I get "permissions denied".
Did you guys encounter this?
Glad it helped you On which step are you getting the error? Any strange output on any of the preceding steps?
Every step is important, to be done in the exact same order, e.g. loading google maps and pressing the 'my location' icon, etc.
Dakedo_Baby said:
First off...Kinslayer81, thanks for posting this. I found the original in Japanese, and was not eager to try to translate it. Thanks for putting in the work.
For everyone (especially if you got this to work) - when I went through the step, I keep getting a "permissions denied" message. Whether it's the ERT4F01D batch file, or typing the commands in... I get "permissions denied".
Did you guys encounter this?
Click to expand...
Click to collapse
Permission denied
Oh I know... I'm not new to the game. I've stalked these boards for a while now... This is my first tablet though.
I've tried running both the ERT4F01D batch... and the manual input.
I get it from the batch file, as soon as I tell it to "RUN"... "Permissions Denied"
From manual input - LINE 2: adb shell "ln -s /data/local.prop /data/local/calib.dat" = "Permissions Denied"
Like there's some additional admin privilege I don't have. Hmmmmm....
And here's an additional kicker... the tablet auto-reboots each and every time. I've tried it a number of times (started over from the top), same result each time.
Kinslayer81 said:
Glad it helped you On which step are you getting the error? Any strange output on any of the preceding steps?
Every step is important, to be done in the exact same order, e.g. loading google maps and pressing the 'my location' icon, etc.
Click to expand...
Click to collapse
I must admit, I don't have any great ideas.
So you can move the file in the first step no problem, and just the attempt to symlink gives you the error?
What is the output of "adb shell ls -la /data/local/".
When does the auto reboot occur?
Dakedo_Baby said:
Oh I know... I'm not new to the game. I've stalked these boards for a while now... This is my first tablet though.
I've tried running both the ERT4F01D batch... and the manual input.
I get it from the batch file, as soon as I tell it to "RUN"... "Permissions Denied"
From manual input - LINE 2: adb shell "ln -s /data/local.prop /data/local/calib.dat" = "Permissions Denied"
Like there's some additional admin privilege I don't have. Hmmmmm....
And here's an additional kicker... the tablet auto-reboots each and every time. I've tried it a number of times (started over from the top), same result each time.
Click to expand...
Click to collapse
I'm stumped too...
Well... this is getting a little interesting...
LS command - no problem (included image)
Decided to have another shot at it... and I was able to get a little further. Still encountered a problem
Now, the INSMOD command failed... "Operation not permitted"
Kinslayer81 said:
I must admit, I don't have any great ideas.
So you can move the file in the first step no problem, and just the attempt to symlink gives you the error?
What is the output of "adb shell ls -la /data/local/".
When does the auto reboot occur?
Click to expand...
Click to collapse
file system set to READ-only...
My file systems are set to Read-only... that explains quite a bit....
Dakedo_Baby said:
Well... this is getting a little interesting...
LS command - no problem (included image)
Decided to have another shot at it... and I was able to get a little further. Still encountered a problem
Now, the INSMOD command failed... "Operation not permitted"
Click to expand...
Click to collapse
Dakedo_Baby said:
My file systems are set to Read-only... that explains quite a bit....
Click to expand...
Click to collapse
Do you mind me asking, how did you set your file system to read-write? I have the same error as you were seeing but it's not allowing me to remount as read-write...
Can you confirm what command you used please?
thanks
Sorry again for late reply
Dakedo_Baby, I've looked at your stuff a few times and it's not obvious to me where things are going wrong. I again need some more info to try get a better idea of what's going on:
1) Before the first reboot, let me know the output of: adb shell "cat /data/local.prop"
2) After the reboot, let me know the output of: adb shell id
As for the file systems, well, /data should be already mounted rw, and /system should be mounted ro until you remount it. You can see how each is mounted with just "adb mount".
histrix said:
Do you mind me asking, how did you set your file system to read-write? I have the same error as you were seeing but it's not allowing me to remount as read-write...
Can you confirm what command you used please?
thanks
Click to expand...
Click to collapse
The command to remount the /system partition as read-write is: adb shell "mount -o rw,remount /system /system"
Of course, you should only be executing that step as part of the given sequence and in the correct order. You won't be able to execute the command until after your first reboot in the instructions, after which adb should still be running as root.
Any good Custom ICS roms you guys recommend after rooting the Arrows Tab?
ICS..Hurray!!!
Just found this out in Fujitsu site:
http://spf.fmworld.net/fujitsu/c/update/nttdocomo/f-01d/update1/top/index.html
There is a 4.0.3 download available. Click the 3rd Button (Green) downloads the zip package.
The 2nd link has howto from PC.
Still not sure if this will work, but trying out.
Also may lose root..and whatever else..So keeping my fingers crossed.
Google translation link
http://translate.google.com/transla...update/nttdocomo/f-01d/update1/top/index.html
Will post how it goes.
I made a new thread for this, since it's a different topic and you'll lose root too
http://forum.xda-developers.com/showthread.php?p=32200671
insmod lsm-disabler.so to remount /system rw
Back to the original topic... what I maybe didn't notice before is that the stock kernel blocks even root users from remounting /system as rw. So in case you ever need rw access to /system again, obviously you'll first have to be root, and afterwards you'll need to "insmod lsm-disabler.so" (as per the original instructions) before you can "busybox mount -o remount,rw /system" (or run any root app that remounts the system partition).
locked F-01d
Kinslayer81 said:
Well, with some help from Google Translate and some creative interpretations, I managed to do this and thought I'd provide some English instructions for others (with some added comments)
DISCLAIMER: AS USUAL, YOU SHOULD KNOW THAT FOLLOWING THESE ACTIONS (AND ESPECIALLY FOLLOWING THEM INCORRECTLY) CAN BRICK YOUR DEVICE (I.E. YOUR DEVICE WILL STOP WORKING, POSSIBLY PERMANENTLY). I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY ARISE FROM YOU FOLLOWING THESE INSTRUCTIONS, YOU DO SO AT YOUR OWN RISK.
Downloads
1. Windows -- the Arrows TAB USB driver Download.
2. Easy rooting toolkit (ERT) for Arrows Tab F-01D (ver 1.0) Download
3. goroh_kun's lsm_disabler.ko Download
Info
4. A su binary, such as the one found in DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
5. Android SDK platform tools. adb(.exe) (and in Windows, specifically: AdbWinApi.dll, AdbWinUsbApi.dll)
Preparation
1. Unzip ert4F01D.zip, and in the subdirectory 'files' place:
* adb.exe (Windows only, from step 4 above)
* AdbWinApi.dll (Windows only, from step 4 above)
* AdbWinUsbApi.dll (Windows only, from step 4 above)
* lsm_disabler.ko (from step 3 above)
* su (from step 5 above)
2. Before connecting the USB, in Settings -> Applications -> Development:
* Check (tick) USB debugging ("Debug mode when USB is connected")
* Check (tick) Stay awake ("Screen will never sleep while charging")
3. Set up the USB drivers and Android Development stuff if you haven't already. I don't use Windows so can't help with this.
The Dirty Work
At this stage, you can run the batch file. Since I don't use Windows, I did the steps by hand, so you'll have to correlate your actions appropriately (I can't read Japanese either, so your guess is as good as mine ).
1. On your PC:
adb shell "mv /data/local/calib.dat /data/local/calib.dat_"
adb shell "ln -s /data/local.prop /data/local/calib.dat"
2. On the tablet, go into Google Maps, touch the GPS icon ("locate me" icon) on the top right hand corner, and then touch the BACK key to exit.
3. On your PC:
adb shell "echo ro.kernel.qemu=1 > /data/local.prop"
adb shell "rm /data/local/calib.dat"
adb shell "mv /data/local/calib.dat_ /data/local/calib.dat"
adb reboot
5. Once the device has fully rebooted, on your PC:
adb shell "mkdir /data/local/lib"
adb push files\lsm_disabler.ko /data/local/lib/
adb shell "insmod /data/local/lib/lsm_disabler.ko"
adb shell "mkdir /data/local/bin"
adb shell "echo '#!/system/bin/sh' > /data/local/bin/autoexec.sh"
adb shell "echo '/system/xbin/soff' >> /data/local/bin/autoexec.sh"
adb shell "chmod 755 /data/local/bin/autoexec.sh"
adb shell "mount -o rw,remount /system /system"
adb shell "ln -s /data/local/bin/autoexec.sh /system/etc/install-recovery.sh"
adb push files\su /system/xbin/
adb shell "chown root.root /system/xbin/su"
adb shell "chmod 06755 /system/xbin/su"
adb shell "echo insmod /data/local/lib/lsm_disabler.ko > /system/xbin/soff"
adb shell "chmod 755 /system/xbin/soff"
adb shell "mount -o ro,remount /system /system"
adb shell "echo > /data/local.prop"
6. I think at this point I was just meant to exit the lock screen.
7. adb reboot
8. Congratulations. You're now rooted. Go to the Play Store and download "Superuser" (by ChainsDD) and "BusyBox" (by Stericson). If you decide to buy BusyBox Pro, do not check the "symlinks" option in version 8.0, otherwise it's game over (no wifi, no adb shell, no root, no remount). It's a pain, but not impossible to repair this situation, see http://forum.xda-developers.com/showthread.php?p=26964465. I've emailed the author and I hope future versions won't trash the system so easily.
After all this, I'd suggest download Titanium Backup for Root users, backing everything up, and uninstall the all the bloatware that came with the device. Read up elsewhere about Titanium Backup.
Let me know if this helped you! Not sure how many other English speakers are using this device
Click to expand...
Click to collapse
thanks for the rooting tutorial but mine is also locked to ntt DOCOMO,,,ANY WAY TO UNLOCK IT
how to unlock the network
please help me how to unlock this tablet i got this tablet from my japan friend but it is network locked please help me to unlock this
As I have ordered my MK-809-III , I will use this posting to collect useful data,
and blog about howto root it, howto install a custom ROM on MK809-III and howto
connect the MK 809-III to a Liyama 24" touchscreen (T2451-MTS)
****************************************************************************************
* update 24-10 2013 *
* If you just want quick root and working fast custom ROM, see steps 1-4 *
* 1 - Got NHR_17_20131012.zip *
* 2 - Took file kernel.img from attachment in this post *
* 3 - Put kernel.img in ROM NHR_17_20131012. (rename existing kernel.img in this ROM to kernel.bak) *
* 4 - opened the RKflash tool ,and just flashed it NHR_17_20131012, without touching anything *
****************************************************************************************
Worked the first time.
Neomode Hybrid 1.7 rooted.
Some info's
Device now shows MK908 in device info.
More RAM (5,8GB) less ROM (0.99GB)
My device has the 6210AP Wifi chip. Actually ,I have two ,slightlly different casings ,from 2 sources.
Internally almost identical ,although one has a heatsink on chip.
When I tried to add touschreen drivers,
nothing happens ,seems like kernel doesn't know about lsusb ! (sadly ,neither do I ,I just follow howto's)
- todo
installing a CWM recovery Manager (unsolved yet)
getting touchscreen 24" Liyama to work
SOME useful links
FACTORY TOOLS ! , for our MK809 - http://pan.baidu.com/share/link?shareid=1042563983&uk=2016504119#dir/path=/MK809III刷机工具
XDA member @misk8er has a CFW tool and cooks http://forum.xda-developers.com/showthread.php?t=2489040
Touchscreen info http://www.freaktab.com/showthread.php?1802-Touchscreen
MK-809-III custom ROM and root instructions
----reserved---
Here's a picture of the factory Tools .
I also have this one.
The original ROM on mine is really bad.
And I`m struggeling to find a new one.
If you find one that is good, please post link
Also I can tell you that the PSU was of bad quality, and did`nt even manage to boot device.
Used another 2A PSU I had, and it booted fine.
Very week wifi reseption.
Bluetooth will not work With original ROM.
Hi,
I have the same Android Mini PC - hoping to get this working on my Samsung all in one touchscreen PC.
igloo888 said:
Hi,
I have the same Android Mini PC - hoping to get this working on my Samsung all in one touchscreen PC.
Click to expand...
Click to collapse
How is your wifi?
Found a good rom?
Hagforce said:
I also have this one.
The original ROM on mine is really bad.
And I`m struggeling to find a new one.
If you find one that is good, please post link
Also I can tell you that the PSU was of bad quality, and did`nt even manage to boot device.
Used another 2A PSU I had, and it booted fine.
Very week wifi reception.
Bluetooth will not work With original ROM.
Click to expand...
Click to collapse
Are you 100% sure you have the Mark III edition ?
Where did you buy it and how much did you pay ?
I got mine off Ebay, still not there, 52 euro including shipping..
I found a useful link : http://blog.geekbuying.com/index.ph...07bmk809iii-quad-core-tv-sticks/#.Ujbh-yTCSdL
Too bad I 'STILL don't have my device...I want to start phreaking.
lucid said:
Are you 100% sure you have the Mark III edition ?
Where did you buy it and how much did you pay ?
I got mine off Ebay, still not there, 52 euro including shipping..
I found a useful link : http://blog.geekbuying.com/index.ph...07bmk809iii-quad-core-tv-sticks/#.Ujbh-yTCSdL
Too bad I 'STILL don't have my device...I want to start phreaking.
Click to expand...
Click to collapse
Also got it from Ebay:
http://www.ebay.com/itm/NEW-MK809II...D&orig_cvip=true&rt=nc&_trksid=p2047675.l2557
Hi, I got it too
I've tried to connect external 2,5" HDD via USB and without external power supply, but it didn't work. Do you have any experience?
Can't get the driver loaded on win7 32bit Antony know of another way to root or flash it?
Sent from my LG-P880 using XDA Premium 4 mobile app
xsigik said:
Hi, I got it too
I've tried to connect external 2,5" HDD via USB and without external power supply, but it didn't work. Do you have any experience?
Click to expand...
Click to collapse
Yes, I got external HDD's to work, directly in USB port of stick (but with external power to HDD)
Also, I have a powered USB hub and anything I connect to it works.
For now, I have three problems
1- can't install a CWM , even for RK3188 devices
2 - Can;t find working instructions to obtain ROOT
3 - Can't install a Custom ROM as no CWM manager nor Root
The device is a beauty and a *****.
update ;see first post. the device is a beauty.
Hi,
I have the same Android Mini PC - hoping to get this working on my Samsung all in one touchscreen PC.
Click to expand...
Click to collapse
I've learned that we need to patch our kernel with HID devices discovery. (touchscreen drivers)
http://stackoverflow.com/questions/...3-not-possible-to-select-only-moving-the-poin
stock rom
Does anyone have the original rom for warranty purposes?
Thanks in advance!
Wow, I never thought it would be this hard to just flash my MK809 III .
The tools and the posts I can find are scattered and it's just hard to get going, as I was not succesful in installing CWM.
Before I do more, I'd like to install a working CWM so I can always get back.
This device is about to defeat me !
Successfully rooted!
I am going to write instructions how to root the device.
ROOTED ?
xsigik said:
Successfully rooted!
I am going to write instructions how to root the device.
Click to expand...
Click to collapse
great to see someone has made real progress... Rooting is already something.
If you can also install a CWM manager that would be awesome.
If you write your report, could you also include links to the files/.'
I can host them for you if you want.
Hope you get CWM installed, and a custom ROM
xsigik said:
Successfully rooted!
I am going to write instructions how to root the device.
Click to expand...
Click to collapse
Can't wait, just bought the device and installed it today. Works nice, but root would give hell of a kick to it
How to root MK809 III
Hi,
there is a description how to root the MK809 III.
Linux
Create a file for udev, for example
Code:
/etc/udev/rules.d/70-android.rules
and insert a rule
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="2207", MODE="0666", GROUP="plugdev"
Reload the rules
Code:
chmod a+r /etc/udev/rules.d/70-android.rules
udevadm control --reload-rules
Then you have to create a file
Code:
~/.android/adb_usb.ini
with this code, because of empty list after "adb devices" after this you will be able to see the device in the list
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2207
Make sure USB Debugging is enabled on your mini PC (Settings -> Developer Options)
Connect your device via USB and check an option in the Settings -> USB -> Connect to PC
To avoid conflicts, kill the adb server
Code:
adb kill-server
now you should see your device
Code:
adb devices
in my case
Code:
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
0123456789ABCDEF device
I modified batch file a little bit, there was a mistake in a file name in compare with original file, so SuperSU.apk wasn't installed.
Before you continue after each restart, check the option "Connect to PC"!
Code:
#!/bin/bash
clear
echo "ROOT by xsigik"
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
echo "Rebooting (1/3) - Continue once device finishes rebooting"
read -p "Press [Enter] key to continue"
adb shell rm /data/local.prop > nul
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
adb reboot
echo "Rebooting (2/3) - Continue once device finishes rebooting"
read -p "Press [Enter] key to continue"
adb shell id
echo "If the id is 0 / root then continue, otherwise ctrl+c to cancel and start over"
read -p "Press [Enter] key to continue"
adb remount
adb push su /system/bin/su
adb shell chown 0.0 /system/bin/su
adb shell chmod 06755 /system/bin/su
adb push busybox /system/bin/busybox
adb shell chown 0.0 /system/bin/busybox
adb shell chmod 0755 /system/bin/busybox
adb push SuperSU.apk /system/app/SuperSU.apk
adb shell chown 0.0 /system/app/SuperSU.apk
adb shell chmod 0644 /system/app/SuperSU.apk
adb push RootExplorer.apk /system/app/RootExplorer.apk
adb shell chown 0.0 /system/app/RootExplorer.apk
adb shell chmod 0644 /system/app/RootExplorer.apk
echo "Removing changes except ROOT"
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
adb reboot
echo "Rebooting (3/3) - You should now be Rooted"
In the attachment, there are all required files. Make sure that RootDevice.sh is executable.
Code:
chmod +x RootDevice.sh
windows?
Glad to see someone else is working with one of these. I've had mine for a few weeks, but haven't had much time to fiddle with it. I bought this thing to work as an inexpensive means to start coding on my own. I have never done much of that, but I would like to start. Does this code created require Linux on your PC to run, or could I run it on my windows machine?
frenchbag said:
Glad to see someone else is working with one of these. I've had mine for a few weeks, but haven't had much time to fiddle with it. I bought this thing to work as an inexpensive means to start coding on my own. I have never done much of that, but I would like to start. Does this code created require Linux on your PC to run, or could I run it on my windows machine?
Click to expand...
Click to collapse
Hi,
it's all about adb commands... so if you have an appropriate driver for MK809 III, put the value 0x2207 into adb_usb.ini in your home directory, then you should see the device in adb devices list. Now you can put these commands into the batch file or just copy&paste directly to adb shell.
I can try it under Windows XP, but I have a little problem with the device - hope to boot again after flashing original stock ROM :-/
Ok, my current situation is that I've tried several ROMs, Finless, Neomode, "original" ROM etc... the device was successfully flashed but didn't work, even ROMs that were for MK809 III didn't work. There was only a blank screen / no signal on TV. Only one older ROM worked