[Q] help with reboot_recovery.sh - Galaxy S II Q&A, Help & Troubleshooting

Hey im trying to write a reboot_recovery.sh script to reboot to recovery for my i9100 and the OTA.
Anyone know the correct path ?
I added an example from a different device.

up..

Reboot recovery help
Hi, thank you very much for posting the information. I tried to use your script on the RK3066 based TV Box - DroidTV X1 . This script is supposed to be called by the OTA Updater to reboot the box to the recovery mode. It didn't work for me.
When I tried to execute it through the terminal connection on the box I get this error:
dd: can't open '/dev/block/nandf': Permission denied
reboot: Operation not permited.
Could you please advice what these commands supposed to do:
Code:
#!/system/bin/sh
echo -n boot-recovery | busybox dd of=/dev/block/nandf count=1 conv=sync; sync; reboot
and why do I'm getting this kind of messages?
Thanks a lot for your help!

Related

[Q] How to Complete uninstall Chainfire 3d drivers

Please help before installing and apply nvidia patch my games like plant vs zombie running without problem.
but after unsuccessful attempt of play nvidia games on my deivce Samsung SGSL i9003.
i uninstall this, set plugin to default and uninstall drivers.
But Still my games are no longer running.
I face problem with plant vs zombie. it crash as it start but before chainfire3d it run perfectly.
waiting for reply asap..
manrock111 said:
Please help before installing and apply nvidia patch my games like plant vs zombie running without problem.
but after unsuccessful attempt of play nvidia games on my deivce Samsung SGSL i9003.
i uninstall this, set plugin to default and uninstall drivers.
But Still my games are no longer running.
I face problem with plant vs zombie. it crash as it start but before chainfire3d it run perfectly.
waiting for reply asap..
Click to expand...
Click to collapse
bro the same problem happened to my phone so i reflashed my custom rom.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
I have the same problem. Chainfire caused me many problems. I want to completely remove it, but I can't.
I put another ROM and whiped data, and it still makes problems. Please help!
manrock111 said:
Please help before installing and apply nvidia patch my games like plant vs zombie running without problem.
but after unsuccessful attempt of play nvidia games on my deivce Samsung SGSL i9003.
i uninstall this, set plugin to default and uninstall drivers.
But Still my games are no longer running.
I face problem with plant vs zombie. it crash as it start but before chainfire3d it run perfectly.
waiting for reply asap..
Click to expand...
Click to collapse
Hy i have same problem . Can you solve this problem? /clear completly chainfire3d/
Same problem, I used to be able to run The Settlers and other games, now I can't..
I uninstalled drivers, set plugin to default, then uninstalled the app, but still it doesn't work
Having root access from recovery is a must to solve problems if you run into them (run "/system/lib/cf3d_uninstall.sh" as root to remove the driver and restore the old one)
1. boot into jb recovery mode
2. run "adb devices" - to make sure the phone drivers are ok (should output a long hex string and "device")
3. run "adb shell" from command prompt
4. in shell prompt "sh system/lib"
5. still in shell "sh /cf3d_uninstall.sh"
phone will reboot and you have working jb system
- it worked for me but no guarantee it'll work for you!
hope it helps.
if sh /cf3d_uninstall.sh doesnt work , try 'sh /system/lib/cf3d_uninstall.sh" instead.
another solve
guys at first i tried to use adb
i got no permissions
so i thought i can use terminal emulator
first open terminal emulator
write SU and give terminal the superuser rights
now use the command
"/system/lib/cf3d_uninstall.sh"
or
"sh /cf3d_uninstall.sh"
after success
your phone will stop giving orders and responding
now you can remove the battery and you are done
ty i hope i helped
mido1122 said:
guys at first i tried to use adb
i got no permissions
so i thought i can use terminal emulator
first open terminal emulator
write SU and give terminal the superuser rights
now use the command
"/system/lib/cf3d_uninstall.sh"
or
"sh /cf3d_uninstall.sh"
after success
your phone will stop giving orders and responding
now you can remove the battery and you are done
ty i hope i helped
Click to expand...
Click to collapse
Under JB, I don't find any system/lib folder at all... Any idea where's the chainfire3D placed in it?
Same problem in my gt2 p3100
manrock111 said:
Please help before installing and apply nvidia patch my games like plant vs zombie running without problem.
but after unsuccessful attempt of play nvidia games on my deivce Samsung SGSL i9003.
i uninstall this, set plugin to default and uninstall drivers.
But Still my games are no longer running.
I face problem with plant vs zombie. it crash as it start but before chainfire3d it run perfectly.
waiting for reply asap..
Click to expand...
Click to collapse
please help chainfire3d has spoiled my android gaming life.
Terminal emulator displaying ''not found''
mido1122 said:
guys at first i tried to use adb
i got no permissions
so i thought i can use terminal emulator
first open terminal emulator
write SU and give terminal the superuser rights
now use the command
"/system/lib/cf3d_uninstall.sh"
or
"sh /cf3d_uninstall.sh"
after success
your phone will stop giving orders and responding
now you can remove the battery and you are done
ty i hope i helped
Click to expand...
Click to collapse
Terminal emulator displaying ''not found''
dailyuse17 said:
Terminal emulator displaying ''not found''
Click to expand...
Click to collapse
Below is my Logs:
######## Below was executed from Windows command prompt. I have "adb.exe" installed in the Desktop\404 ##########
C:\Users\Chu\Desktop\404>adb kill-server
C:\Users\Chu\Desktop\404>adb wait-for-device
* daemon not running. starting it now *
* daemon started successfully *
C:\Users\Chu\Desktop\404>adb shell
########## After you've executed 'adb shell', i will login to the phone as user shell ##########
[email protected]:/ $ su
########## You have to switchuser to root to gain full access, as seen below, you are "root" ##########
[email protected]:
# cd /system
cd /system
[email protected]:/system # cd lib
cd lib
########## Above, i change directory to /system/lib ##########
[email protected]:/system/lib # ls cf*
ls cf*
cf3d_uninstall.sh
########## Found the file to be cf3d_uninstall.sh and execute the shell script with the command below ##########
[email protected]:/system/lib # sh cf3d_uninstall.sh
sh cf3d_uninstall.sh
rm failed for /system/lib/cf3d_sh, No such file or directory
usage: reboot [-n] [-p] [rebootcommand]
########## There, the phone will restart, and you'll get back your phone. Just ignore the "no such file or directory" error above. It'll still work ##########
Good luck.
manchuks said:
Below is my Logs:
######## Below was executed from Windows command prompt. I have "adb.exe" installed in the Desktop\404 ##########
C:\Users\Chu\Desktop\404>adb kill-server
C:\Users\Chu\Desktop\404>adb wait-for-device
* daemon not running. starting it now *
* daemon started successfully *
C:\Users\Chu\Desktop\404>adb shell
########## After you've executed 'adb shell', i will login to the phone as user shell ##########
[email protected]:/ $ su
########## You have to switchuser to root to gain full access, as seen below, you are "root" ##########
[email protected]:
# cd /system
cd /system
[email protected]:/system # cd lib
cd lib
########## Above, i change directory to /system/lib ##########
[email protected]:/system/lib # ls cf*
ls cf*
cf3d_uninstall.sh
########## Found the file to be cf3d_uninstall.sh and execute the shell script with the command below ##########
[email protected]:/system/lib # sh cf3d_uninstall.sh
sh cf3d_uninstall.sh
rm failed for /system/lib/cf3d_sh, No such file or directory
usage: reboot [-n] [-p] [rebootcommand]
########## There, the phone will restart, and you'll get back your phone. Just ignore the "no such file or directory" error above. It'll still work ##########
Good luck.
Click to expand...
Click to collapse
my phone camera doesnot work well due to chainfire3d how to uninstall completely . at this time i m completely uninstall the chai fire 3d but camera does not work . my camera shows the blur photos when in the camera mode
How to do this when installed it by mistake on samsung gt-i9505 please? thanks.
---------- Post added at 02:36 AM ---------- Previous post was at 02:05 AM ----------
Ok, like i didn't see the file in the folders concerned, this saved me (applied it without looking or searching the file i didn't see). big up and thanks.
http://forum.xda-developers.com/showpost.php?p=39301435&postcount=8
Help me please...
bolibo said:
Having root access from recovery is a must to solve problems if you run into them (run "/system/lib/cf3d_uninstall.sh" as root to remove the driver and restore the old one)
1. boot into jb recovery mode
2. run "adb devices" - to make sure the phone drivers are ok (should output a long hex string and "device")
3. run "adb shell" from command prompt
4. in shell prompt "sh system/lib"
5. still in shell "sh /cf3d_uninstall.sh"
phone will reboot and you have working jb system
- it worked for me but no guarantee it'll work for you!
hope it helps.
Click to expand...
Click to collapse
Hi.. i tried what you have suggest but still not able to recover my phone...please help me
:crying::crying::crying::crying::crying::crying::crying:
:\android-sdk-windows\platform-tools>adb devices
List of devices attached
0123456789ABCDEF device
C:\android-sdk-windows\platform-tools>adb shell
[email protected]:/ $ sh /system/lib/cf3d_uninstall.sh
sh /system/lib/cf3d_uninstall.sh
mount: Operation not permitted
/system/lib/cf3d_uninstall.sh[4]: can't create /system/lib/libGLESv1_CM.so: Read
-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chmod /system/lib/libGLESv1_CM.so: Read-only file system
/system/lib/cf3d_uninstall.sh[11]: can't create /system/lib/libGLESv2.so: Read-o
nly file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chmod /system/lib/libGLESv2.so: Read-only file system
rm failed for /system/lib/cf3d_uninstall.sh, Read-only file system
rm failed for /system/lib/cf3d_sh, No such file or directory
usage: reboot [-n] [-p] [rebootcommand]
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
1|[email protected]:/ $
Help
Hello, guyz. the solution for this problem is that you should unistalled the divers you have installed to reduce the graphics (which u have installed in chainfire 3d) unistalled it and you are ready play your game again with the same graphic which you have earlier
thanks!
manju_xda said:
Hi.. i tried what you have suggest but still not able to recover my phone...please help me
:crying::crying::crying::crying::crying::crying::crying:
:\android-sdk-windows\platform-tools>adb devices
List of devices attached
0123456789ABCDEF device
C:\android-sdk-windows\platform-tools>adb shell
[email protected]:/ $ sh /system/lib/cf3d_uninstall.sh
sh /system/lib/cf3d_uninstall.sh
mount: Operation not permitted
/system/lib/cf3d_uninstall.sh[4]: can't create /system/lib/libGLESv1_CM.so: Read
-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chmod /system/lib/libGLESv1_CM.so: Read-only file system
/system/lib/cf3d_uninstall.sh[11]: can't create /system/lib/libGLESv2.so: Read-o
nly file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chmod /system/lib/libGLESv2.so: Read-only file system
rm failed for /system/lib/cf3d_uninstall.sh, Read-only file system
rm failed for /system/lib/cf3d_sh, No such file or directory
usage: reboot [-n] [-p] [rebootcommand]
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
1|[email protected]:/ $
Click to expand...
Click to collapse
You must be rooted to do that.
Help!!
El_Dark said:
You must be rooted to do that.
Click to expand...
Click to collapse
Hi, i'm a boy from Finland. I have the same problem as "manju_xda" but i have the root permissions in my device..
The question is.. .. I'm stucked with chainfire 3d and my adb shell tells that "adbd cannot run as root in production builds" .. What to do?
And sorry for my bad english
For those who found this thread on Google, I found my solution in here: http://forum.xda-developers.com/showthread.php?t=2362873

How to root Fujitsu Stylistic M532

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)

[INFO] MK-809 III - (2GB,WiFi,BT/4.2.2. 8 GB ROM)

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

Huawei ascend p7 non rooted busybox linking read-only filesystem

Hello everyone,
I've updated my firmware to the latest version of my huawei ascend p7 making it impossible to root my phone. Now what I'm trying to do is get the non-rooted busybox working and replace the old links of commands with the ones in busybox. I'm using the following commands to do that:
First I export the path and such using:
Code:
export PATH=$PATH:/data/data/burrows.apps.busybox/app_busybox;
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/data/data/burrows.apps.busybox/app_bussybox
Now I'm able to use busybox in my terminal (only for that session, when I exit the terminal and restart it I would have to re-do the export path thing).
So... I wanted to replace all the links to those of busybox using the following command:
Code:
for c in `busybox --list`; do busybox ln -s busybox $c; done
This however outputs for each command for example cat:
Code:
ln: cat: Read-only file system
I've read somewhere that you can remount your system partition in order to make it writeable? Is this the way to do it? And if so what commands should I run? I have access through adb and a normal shell on the phone. Remember: it's non-rooted...
EDIT: seems like I can't remount /system without root priviledges...
Also I would like to be able to have a full colored bash shell with a bashrc (in which I can add the path to busybox aswell) if that's possible.
I'm using jackpal's android terminal emulator.
EDIT: I think I might've posted this on the wrong forum, if anyone is so kind as to move this to this forum: http://forum.xda-developers.com/ascend-p7/help I would greatly appreciate it. Altho I think this might be a general question rather then a model specific question.

[MOD] [Stratos/Pace] Universal init.d Enabler!

What is init.d?
init.d is a folder placed in /system/etc wich has been legendary used since the old android times to run scripts at boot. I've decided to make this simple script becouse lots of my users on my AmazBoost MOD thread were asking how they can enable init.d on stock ROM or simply on an unsupported ROM. It's easy to run and doesn't require any kind of coding skills!
What you need
- AmazFit Stratos/Pace
- Rooted ROM
How to install
1) Download the mod zip from download link and unzip it
2) Connect the wath to the PC
3) Place the enable.sh file inside your adb folder and open there a command prompt (or terminal for Mac OS/linux) then type the following codes:
Code:
adb root
adb push enable.sh /sdcard/
adb shell sh /sdcard/enable.sh
4) Done!
5) You NEED to reinstall the mod running the installer after every ROM update!
Changelog
First release!
Download and enjoy!
https://goo.gl/HYqEZt
If my work was useful always press thanks!​
There is a typo in the script:
touch /system/ect/install-recovery.sh
chmod 755 /system/etc/install-recovery.sh
chown 0:2000 /system/ect/install-recovery.sh
should be
Code:
touch /system/etc/install-recovery.sh
chmod 755 /system/etc/install-recovery.sh
chown 0:2000 /system/etc/install-recovery.sh
jprelay said:
There is a typo in the script:
touch /system/ect/install-recovery.sh
should be
Code:
touch /system/etc/install-recovery.sh
Click to expand...
Click to collapse
Ooops didn't check it perfectly just used a Compiler to see if there were some syntax errors, thanks I'll updating the file now!
Inviato dal mio G8141 utilizzando Tapatalk
Script name and command name don't match either, enabler.sh
I think that I found a solution..I wish is helpful !
1) First of all you need to have unlock bootloader and then run the temporary root
(check in "PERMANENT INSTALL" description)
AFTER ROOTING LETS GO FOR UNIT SUPPORT!
I used the init.d support through terminal emulator
2) Download the term-init.sh v3 .
3) Connect the watch to your PC.
4) Place the term-init.sh file inside your adb folder and open the command prompt.. then type the following codes:
(if adb shell or adb root not working, try to disconnect and connect your watch )
Code:
adb root
adb push term-init.sh /sdcard/
(or you can drag and drop it in your sdcard)
adb shell sh /sdcard/ term-init.sh
5) After that go and run the installer.bat file from Amazboost folder!
6) Done!​
I tried this tools but i have error
Code:
+ $'\r'
: not foundble.sh[12]:
/sdcard/enable.sh[13]: syntax error: 'if' unmatched
tminhnhat said:
I tried this tools but i have error
Code:
+ $'\r'
: not foundble.sh[12]:
/sdcard/enable.sh[13]: syntax error: 'if' unmatched
Click to expand...
Click to collapse
Same here too, the OP seems to have been making a lot of mistakes in his scripts
How is the init.d supposed to be enabled?
Hi, i want to enable AmazBoost so i came to this post to enable init.d but i lost, i dont understand what i need to do, when i follow the instructions i get this error.
########################################################
# #
# AmazFit universal init.d enabler by @AmazDev #
# #
########################################################
Mounting system...
Usage: mount [-r] [-w] [-o options] [-t type] device directory
: not foundbler.sh[12]:
/sdcard/enabler.sh[13]: syntax error: 'if' unmatched
I have Stratos 2 A1619
I have a Stock ROM 2.3.6.0 Unlocked
Thanks
---------- Post added at 05:20 PM ---------- Previous post was at 05:04 PM ----------
Hi, i tried with the other instructions but again i have a error:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell sh /sdcard/term-init.sh
Init.d Enabler by Ryuinferno @ XDA
Script NOT running as root!
Superuser access not granted!
Please type 'su' first before running this script...
C:\Program Files (x86)\Minimal ADB and Fastboot>su
'su' is not recognized as an internal or external command,
operable program or batch file.
kostasntamas said:
I think that I found a solution..I wish is helpful !
1) First of all you need to have unlock bootloader and then run the temporary root
(check in "PERMANENT INSTALL" description)
AFTER ROOTING LETS GO FOR UNIT SUPPORT!
I used the init.d support through terminal emulator
2) Download the term-init.sh v3 .
3) Connect the watch to your PC.
4) Place the term-init.sh file inside your adb folder and open the command prompt.. then type the following codes:
(if adb shell or adb root not working, try to disconnect and connect your watch )
Code:
adb root
adb push term-init.sh /sdcard/
(or you can drag and drop it in your sdcard)
adb shell sh /sdcard/ term-init.sh
5) After that go and run the installer.bat file from Amazboost folder!
6) Done!​
Click to expand...
Click to collapse
hi mate, do you modify the term-init.sh?
may i know which version of busybox that you are using?
currently im using the busybox from here: https://forum.xda-developers.com/showpost.php?p=78031249&postcount=107
and when i try to install term-init.sh, i encountered below error:
Code:
grep applet NOT FOUND!
run-parts applet NOT FOUND!
Required applets are NOT FOUND!
Please reinstall busybox!
illkid69 said:
hi mate, do you modify the term-init.sh?
may i know which version of busybox that you are using?
currently im using the busybox from here: https://forum.xda-developers.com/showpost.php?p=78031249&postcount=107
and when i try to install term-init.sh, i encountered below error:
Code:
grep applet NOT FOUND!
run-parts applet NOT FOUND!
Required applets are NOT FOUND!
Please reinstall busybox!
Click to expand...
Click to collapse
i have same problem do u find any solution?
Is anybody enable init.d on stock fw?
Hi,
I'm trying to install the Amazboost tweaks on my rooted Stratos (A1619) with Global FW (2.3.10.5) but I suspect that the installation of the tweaks via busybox is not running correctly. I have followed precisely the procedures with success but there is no log in the AmazBoost/LOGS folder after the reboot.
I have installed the last version of busybox (V1.29.3 for MIPS) in both /system/bin and /system/xbin but no log at all.
Some posts said that init.d is not working with stock fw.
Is that true?
Is anybody can help me to check if init.d can be enabled on my rooted Stratos (A1619) with Global FW (2.3.10.5)? And how can we verify that it works?
Thanks
Hi,
I'm still trying to understand why init.d is not running on my Stratos (A1619) with Global FW (2.3.10.5).
The init.d script refers to the "run-parts" file located in the /system/xbin/ directory.
But run-parts is not present.
I have found one file coming from the xperia x10 forum but it is not working on the Stratos: /system/xbin/run-parts: not executable: 32-bit ELF file
Is somebody could provide me this run-parts file compliant with the Stratos? (or help me to understand why the amazboost tweaks are not correctly installed)

Categories

Resources