Related
TRADUCTION STOPED, WORK CONTINUE IN ORIGINAL POST (FRENCH)
Reason : NO USER FEED BACK
Thanks to the author of X10 mini Exploit : http://android.doshaska.net/x10miniroot
This script pack is wrote under WINDOWS CMD, then to use on Windows.
These scripts are writen to help to :
Root X10 under ROM 023 or upper
make an INDUSTRIAL APK install (NO APPS IS INCLUDED, Make your choise)
Clean up some Constructor's packages
Install a Theme (NO THEME IS INCLUDED, Make your choise)
Install a BootScreen (NO BootScreen IS INCLUDED, Make your choise)
My scripts are included all INSTRUCTIONS Step by Step
MUST HAVE BEFORE :
Have an X10i (Not tested with X10a)
ROM 023 upper (Tested on DeBranded 026 and 023 )
Be under Windows
Installed SEUS (for drivers)
Change the Screen Time out to 10Mins (or more)
(Param/Sound&Display/Screen Time Out)
For the root step, Use the SONY WITGET for WIFI...
DURING THE SCRIPT RUNNING, PLEASE BE IN DEBUG MODE ON YOUR X10...
YOU CAN DOWNLOAD MY EACH MODULE IN THE ATTACHED FILE ON EACH RELATED POST
/!\ EACH RAR FILE MUST BE EXTRACTED ON C:\ /!\
0)THE MUST HAVE FILE (CORE) : Adb (Without this package, none worked)
DOWNLOAD : 0_CORE Only
Or FULL INSTALL (ENG) : FULL_INSTALL(All Packages)
Or FULL INSTALL (FRENCH) : FullInstall French
YOU NEED TO COMBINE IT WITH ONE OF THE OTHER MODULE (or ALL)
Step 0(adb) + (Rooter / APK Installer / Cleaner / Theme / Boot Screen)
Each RAR file contain his own files
You can say YES when winRAR ask you to overwrite
/!\ Please give me a feed back... worked or not /!\
Click to expand...
Click to collapse
PS : some steps are requiered an Humain action, because for the FW 026 users, the su is Unsecured (then block all batch request...) sorry.. I must to learn VBScrit to release a Full batched script...
STEP 1 : ROOTING THE X10 (026) by the X10 mini Explot Method
DOWNLOAD : 0_CORE + Here
Or FULL INSTALL (ENG) : FULL_INSTALL(All Packages)
Or FULL INSTALL (FRENCH) : FullInstall French
I don't recommand to use the "1 Click" method, because, i want to test the peering of your X10 and your PC.. If your X10 is not detected and peered with your PC, step 2->5 can't be functional...
*********************************************************
Enable "USB Debugging" in "Settings/applications/developpement"
Put on the HOME the SONY's widget "Quick Settings" and enable the WiFi
Plug your phone to the PC
*********************************************************
Click to expand...
Click to collapse
-> Do that asked : Go to the USB DEBUGGING MODE
DISABLE WiFi from the SONY's widget SONY (onthe HOME)
HUMAIN ACTION : Type the command lines as requested
Click to expand...
Click to collapse
-> As wrote, YOU must type these command lines (Can't batch this step yet)
-> Copy/Past is allowed
rootshell
Click to expand...
Click to collapse
type this password : rootnow
cd /sqlite_stmt_journals/
./busybox cp /sdcard/bin/su /system/bin/
./busybox cp /sdcard/bin/busybox /system/bin/
chmod 6777 /system/bin/su
rm /system/bin/rootshell
exit
exit
Click to expand...
Click to collapse
At this step, your X10 is rooted... No need to reboot
STEP 2 : INDUSTRIAL APK INSTALL
DOWNLOAD : 0_CORE + Here
Or FULL INSTALL (ENG) : FULL_INSTALL(All Packages)
Or FULL INSTALL (FRENCH) : FullInstall French
Put your APK files in this folder : (press Any key)
Click to expand...
Click to collapse
-> an Explorer window will pop up with path C:\KitThol_ENG\InstallAPK\app
-> Fill it with ALL your APK that you want to install
-> Press any key in the script window
-> My script will install ALL your APKs by it shelf
STEP 3: CLEAN UP SOME CONTRUCTOR"S PACKAGES
DOWNLOAD : 0_CORE + Here (FR)
Or FULL INSTALL (ENG) : FULL_INSTALL(All Packages)
Or FULL INSTALL (FRENCH) : FullInstall French
Cleaner V2(FR) : Backup on local drive before delete + Face Book and You Tube are NOT deleted
+ Some more deleted apps..
Check the cleansony.sh file if you want to know what i delete
Click to expand...
Click to collapse
-> Check the cleansony.sh file in C:\KitThol_ENG\Cleaner\
-> Delete lines where there package you want to keep (like youtube or facebook)
-> and save it
HUMAIN ACTION : Type the command lines as requested :
Click to expand...
Click to collapse
-> You MUST type these command lines (Not Batchable yet)
-> Copy/Past is allowed
su
Click to expand...
Click to collapse
on the X10 : ALLOW SU request(check Memorise/remember)
echo #WAIT the prompt "#"
Click to expand...
Click to collapse
-> Do that asked
cd sdcard
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
sh cleansony.sh
exit
exit
Click to expand...
Click to collapse
-> You will see some Error messages (": Not found" )...
-> Don't worry.. it's only due to Windows text formated (^M for return)
-> Some apps will be on error (we delete it )
STEP 4 : INSTALL A THEME
DOWNLOAD :0_CORE + Here
Or FULL INSTALL (ENG) : FULL_INSTALL(All Packages)
Or FULL INSTALL (FRENCH) : FullInstall French
Fill this folder with your APK theme (WITHOUT Framework) : [Press ANY KEY]
Click to expand...
Click to collapse
-> A window will pop up with path C:\KitThol_ENG\Theme\APK
-> Fill it with APPS APK theme (not the Framwork)
Put your FRAMEWORK APK in this folder : [Press ANY KEY]
Click to expand...
Click to collapse
-> A window will pop up with path C:\KitThol_ENG\Theme
-> Fill it with FRAMEWORK APK theme
HUMAIN ACTION : Type the command lines as requested :
Click to expand...
Click to collapse
-> you MUST type these command lines (not Batchable yet)
-> Copy/Past is allowed
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
cd /sdcard/
sh applytheme.sh
exit
exit
Click to expand...
Click to collapse
-> Well done, your X10 will Rebooted (now or under few seconds )
STEP 5 : INSTALL A BOOT SCREEN
DOWNLOAD : 0_CORE + Here
Or FULL INSTALL (ENG) : FULL_INSTALL(All Packages)
Or FULL INSTALL (FRENCH) : FullInstall French
Fill here your PNG files :
Click to expand...
Click to collapse
-> A window will pop up with path C:\KitThol_ENG\BootScreen
-> Fill it with the PNG(only png, not directory) of your downloaded BootScreen File
HUMAIN ACTION : Type the command lines as requested :
Click to expand...
Click to collapse
-> you MUST type these command lines (not Batchable yet)
-> Copy/Past is allowed
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
cd /sdcard/Theme/BootScreen/
sh applyBootScreen.sh
exit
exit
Click to expand...
Click to collapse
-> Well done, your X10 will Rebooted (now or under few seconds )
Step 0 is the needed file for my all other modules...
If you want to do a full install, try to execute my scripts by order...
then else, if you need only ONE of theses module you MUST extract the module :
Step 0 + Step(s) needed...
Have fun.. i wait your feed back..
great post. thanks for all the info. can't wait to get started on all this stuff
Have you success what you need with my scripts ?
I fix an error of syntaxes, my Main folder name contain a space... and there no space in path used in scripts...
All must Running now...
I wait your feed back !
Nobody had tested my work ? :-(
It not helped you ?
is it useless ?
Please say something.. i have to continue to this way or i must stop now ?
My partner has an X10 that I would love to test this on but has recently been upgraded to the latest firmware. Sorry.
My worry would be not having tools like nandroid as a safety net.
Sent from my Nexus One using XDA App
First, Thank you for this reply...
my scripts aren't for UPGRADE FW, it goal is to
root (have an administrator access),
help to install MANY applications in one time
help to delete some constructor's applications (who get your device slowly)
Help to istall a theme (because it's a litle bit difficult on FW 026)
Help to istall a Bootscreen (because it's a litle bit difficult on FW 026)
Then you can test it... dont worry, i tested with my french testers...
I just want to help you... International users !!!
Debrand x10
wolf0491 said:
I would try but I'm still on 20 and I'm selling my x10 on 26 so not doing anything to it. I actually have no idea why mine has not updated to 26.
Sent from my X10a using XDA App
Click to expand...
Click to collapse
If you want to be on 026, try this method (Debrand) :
download the FW 026 here
unrar it, there 2 files..
launch SEUS, do a repair... SEUS will download the actual FW of your X10, flash it with it..
when done, go to C:/ProgramData/Sony Ericsson/SEMC OMSI Module/db/13740270/blob_fs (on Windows Vista/7 )
there 2 big files (16Mo and 130Mo)
copy the NAME of le 16mo's files in this directory (SEUS Directory).. past it on the 16Mo of the downloaded FW on my link. do the samething with the bigger file (130Mo)...
Replace the to files in SEUS directory with the 2 files downloaded...(overwrite)
launch SEUS and flash it again with the repair method...
It's done... your X10 will be on 026 after the flash...
Ok. You can use each functionality separately... try to change a theme or bootscreen ? There no danger..
It can be in both section... because it help to apply a theme AND to root a 02x fw.
It's not the probem.
I just want to know if there somebody has use my script ?
If not why you are afraid ?
I let my work here 1 month again... after, i delete it.. be cause i dont want to use this forum storage for something that nobody use it..
sorry double post
this from rad131304 not me, thank you
Windows 7 Sideload Instructions
Hope this helps some people - I tried to be very step-by-step about it.
Again, thank you Pokey9000, the guys and gals from the IRC channel, and everybody else for all of your hard work! 99.9% of this is an aggregation of what is already in this thread; some of it comes from nookdevs also.
You will need the following applications on your Windows 7 computer:
- cygwin (www dot cygwin dot com)
- Android Debug Bridge (ADB) - this comes with the android SDK
- Android USB Drivers - this comes with the android SDK
-- (WOQ) stands for without quotes, it means that I am giving you something between quotes to copy and paste.
-- if you see <some_odd_name> inside quotes, it means you MUST replace this with something from your specific OS instance (e.g. a drive letter, or something)
1. make sure your NC is disconnected from you computer
2. make sure your SD card is mounted on your computer (readable/browsable in explorer)
3. Install cygwin - you only need the base install AFAICT (YMMV), don't worry about the options for now.
4. download nooter at http //www dot mediafire dot com/?hugt8uxcfffpdvg
5. extract the contents to a folder in your cygwin install (standard install path is c:\cygwin)
6. Go to: Start, type in (WOQ) "compmgmt.msc" - this may require UAC elevation
7. Select "Disk Management" under storage
8. note the drive letter of the SD card and the disk number
9. Go To: Start > All Programs > Cygwin > Cygwin Bash Shell
10. At the prompt, type (WOQ): "mount //./<f>: /dev/sd<c>"
Where <f> is your drive letter, and
<c> is the letter you would get if you zero-indexed the disk number into the alphabet (i.e. 0 = a, 1 = b) **
11. press enter - there should be no output
12. at the prompt, type (WOQ): "dd if=<path_to_nooter_from_cygwin_install_folder>/nooter_sdcard_40MB.img of=/dev/sd<c>"
It will sit at this for a few minutes seeming to do nothing, be patient; you should get a response eventually that looks like:
80326+0 records in
80326+0 records out
41126912 bytes (41 MB) copied, 174.525 s, 236 kB/s
13. remove the sd card from the computer and plug it into the NC
14. power down the NC (hold power button for 15 seconds)
15. connect the NC to the computer
16. Wait for a "Composite Device" to be recognized by Windows and fail to install drivers
17. Wait for 15 seconds after the recognition
18. power down the NC
19. remove SD card ***
20. Find your android_winusb.inf file - this is located in your android-sdk install directory in the usb_driver folder. (NOTE: if you installed this in the program files folder, you will need to UAC elevate your editor to edit this file)
21. Paste the following lines into the file below both occurrences of the line ";Moto Sholes" after the ADBInterface definitions:
;B & N Nook Color
%SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0002
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0002&MI_01
22. save the file and close
23. find your adb_usb.ini file - it is usually located in c:\users\<username>\.android\
24. add (WOQ) "0x2080" on its own line
25. power on NC - at this point, the NC should boot normally, but ADB won't be able to recognize it
26. Go To: Start > Devices and Printers
27. Right-click on Nook and select properties
28. Select the hardware tab
29. If you have something that says "Nook" and has a yellow yield sign with a "!", then continue, if not skip to 38
30. Click on "Nook"
31. Select Properties
32. Click Change Settings (may require UAC elevation)
33. Click update driver
34. Select "browse for driver software on your computer"
35. Browse to the android-sdk/usb_driver folder
36. click next
37. You should be done; skip to 47 (I have no idea if this is correct - i pieced it together from somewhere in this as I did not get Nook to appear in the Device Functions List)
38. If you don't have a "Nook" Device Function, click on "USB Mass Storage Device"
39. Select Properties
40. Click Change Settings (may require UAC elevation)
41. Select the Driver Tab
42. Click Uninstall
43. Click OK
44. Disconnect NC
45. Reconnect NC
46. You should be done (this is different from my previous instructions on how to uninstall the NC USB drivers, I have not tested it so YMMV)
47. Go To: start > run > cmd
48. type (WOQ): "cd <path_to_android_sdk>\tools"
49. type (WOQ): "adb.exe kill-server"
You should get something like:
* server not running *
50. type (WOQ): "adb.exe remount"
You should get something like:
* daemon not running. starting it now *
* daemon started successfully *
remount failed: No such file or directory
51. You are done configuring to sideload
From here you should be able to sideload from ADB.
by rad131304
Just to throw it out there...
Does this cause a PERMANENT change to the Color Nook?
Edit: thank you for posting this
I believe it was mentioned in a previous post that if you did a factory reset (power off completely, then hold power, nook button and vol up) that it would reset the Nook back to non rooted factory defaults. Can anyone else confirm this?
HeroHTC said:
Just to throw it out there...
Does this cause a PERMANENT change to the Color Nook?
Edit: thank you for posting this
Click to expand...
Click to collapse
Are these instructions for Win 7 64 or 32 bit?
BTW, how does one go back or to menu without those buttons?
RichTJ99 said:
Are these instructions for Win 7 64 or 32 bit?
BTW, how does one go back or to menu without those buttons?
Click to expand...
Click to collapse
believe this was done on win 64, some buttons are located in or below menu bar, some will depend on launcher.
I also wanted to mention this
http://forum.xda-developers.com/showpost.php?p=9517050&postcount=863
NOTE: I have not even opened my nook box yet, its still sealed but I am getting ready. Just waiting on an email solution.
Do you think a partitioned SD card woul dprevent this from working?
I'm pretty sure my card is partitioned....I read something in the BIG THREAD about departitioning a card.....
I can't get this to work for me and I just thought my card might be the culprit.
Thanks
I cannot find the file listed in step 23. This is the only thing keeping me from root. Also when I plug my nc in, the light on the cord is amber instead of green. It tells me that adb drivers are installed. But it won't show up as a folder in my computer any more. How do I add files without removing the SD card and plugging it into my computer.
Sent from my HERO200 using XDA App
RichTJ99 said:
Are these instructions for Win 7 64 or 32 bit?
BTW, how does one go back or to menu without those buttons?
Click to expand...
Click to collapse
I did this on 32 bit - AFAIK, they don't support cygwin on 64 bit yet (it might run though, but YMMV).
The back and menu buttons are soft-buttons. The nook for some reason hides them by default in a bunch of apps.
sudermatt said:
Do you think a partitioned SD card woul dprevent this from working?
I'm pretty sure my card is partitioned....I read something in the BIG THREAD about departitioning a card.....
I can't get this to work for me and I just thought my card might be the culprit.
Thanks
Click to expand...
Click to collapse
IIRC, somebody said that in the big thread, too.
oakleyrdc said:
I cannot find the file listed in step 23. This is the only thing keeping me from root. Also when I plug my nc in, the light on the cord is amber instead of green. It tells me that adb drivers are installed. But it won't show up as a folder in my computer any more. How do I add files without removing the SD card and plugging it into my computer.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
It could be hidden (so you'll have to change the hidden files and folders setting), or installed in another user directory (like Admin).
If I run Windows XP, how many of these steps would change? I'm thinking it might need its own thread.
I did mine on Win 64bit using winimage. Everything is working fine.
rad131304 said:
I did this on 32 bit - AFAIK, they don't support cygwin on 64 bit yet (it might run though, but YMMV).
Click to expand...
Click to collapse
XP
cabbieBot said:
If I run Windows XP, how many of these steps would change? I'm thinking it might need its own thread.
Click to expand...
Click to collapse
plus 1 for XP
So once your rooted, do you need to do anything special to install apk files that you download from dropbox? Is superuser ready?
i cant find the android_winusb file in the windows XP version of the android SDK. is there a different one that does the same?
EDIT: it appears the sdk is not split between versions of windows
im going to reinstall the sdk and see maybe if i accidently deleted it at some point
cabbieBot said:
If I run Windows XP, how many of these steps would change? I'm thinking it might need its own thread.
Click to expand...
Click to collapse
Very little changes; the only thing I can tell you off the top of my head is that
C:\users\<username>\.android\
Becomes
C:\documents and settings\<username>\.android\
Also, I don't know where, besides device manager, that you could locate the nook like you do in devices and printers - it may show up in my computer, also in scanners and cameras in the control panel - you can always right click a drive, select properties, select the hardware tab, select the b&n storage device, click properties, select the driver tab and uninstall from there....
HTH
EDIT: To delete the NC through device manager:
start > run > compmgmt.msc
browse to Device Manager
Expand Universal Serial Bus Controllers
Select USB Mass Storage Device (there may be multiple)
Right-Click and select "properties"
select the details tab
in the dropdown, select "Hardware Ids" - if this says "USB\VID_2080&...." then this is the NC
click ok
right Click again and select uninstall
disconnect NC from computer
reconnect NC to computer
NC re-finds all drivers, including ADB
start > run > cmd
cd <android-sdk-dir>\tools
adb.exe remount
Fixed instructions!
that's what I get for writing this crap at 1 in the AM ... I left out two INSANELY important steps at step 11.
SORRY!!!!
Windows 7 Sideload Instructions
Hope this helps some people - I tried to be very step-by-step about it.
Again, thank you Pokey9000, the guys and gals from the IRC channel, and everybody else for all of your hard work! 99.9% of this is an aggregation of what is already in this thread; some of it comes from nookdevs also.
You will need the following applications on your Windows 7 computer:
- cygwin (http://www.cygwin.com)
- Android Debug Bridge (ADB) - this comes with the android SDK
- Android USB Drivers - this comes with the android SDK
-- (WOQ) stands for without quotes, it means that I am giving you something between quotes to copy and paste.
-- if you see <some_odd_name> inside quotes or a code block, it means you MUST replace this with something from your specific OS instance (e.g. a drive letter, or something)
make sure your NC is disconnected from you computer
make sure your SD card is mounted on your computer (readable/browsable in explorer)
Install cygwin - you only need the base install AFAICT (YMMV), don't worry about the options for now.
download nooter at http://www.mediafire.com/?hugt8uxcfffpdvg
extract the contents to a folder in your cygwin install (standard install path is c:\cygwin)
Go to: Start, type in (WOQ) "compmgmt.msc" - this may require UAC elevation
Select "Disk Management" under storage
note the drive letter of the SD card and the disk number
Go To: Start > All Programs > Cygwin > Cygwin Bash Shell
At the prompt, type:
Code:
mount //./<f>: /dev/sd<c>
Where <f> is your drive letter, and
<c> is the letter you would get if you zero-indexed the disk number into the alphabet (i.e. 0 = a, 1 = b) **
press enter - there should be no output
REMOVE SD CARD FROM PC
INSERT SD CARD INTO PC
at the prompt, type:
Code:
dd if=<path_to_nooter_from_cygwin_install_folder>/nooter_sdcard_40MB.img of=/dev/sd<c>
It will sit at this for a few minutes seeming to do nothing, be patient; you should get a response eventually that looks like:
80326+0 records in
80326+0 records out
41126912 bytes (41 MB) copied, 174.525 s, 236 kB/s
Click to expand...
Click to collapse
IF THIS COMPLETES ALMOST IMMEDIATELY, YOU PROBABLY HAVE AN ERROR
remove the sd card from the computer and plug it into the NC
power down the NC (hold power button for 15 seconds)
connect the NC to the computer
Wait for a "Composite Device" to be recognized by Windows and fail to install drivers
Wait for 15 seconds after the recognition
power down the NC
remove SD card ***
Find your android_winusb.inf file - this is located in your android-sdk install directory in the usb_driver folder. (NOTE: if you installed this in the program files folder, you will need to UAC elevate your editor to edit this file)
Paste the following lines into the file below both occurrences of the line ";Moto Sholes" after the ADBInterface definitions:
Code:
;B & N Nook Color
%SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0002
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0002&MI_01
save the file and close
find your adb_usb.ini file - it is usually located in c:\users\<username>\.android\
add (WOQ) "0x2080" on its own line
power on NC - at this point, the NC should boot normally, but ADB won't be able to recognize it
Go To: Start > Devices and Printers
Right-click on Nook and select properties
Select the hardware tab
If you have something that says "Nook" and has a yellow yield sign with a "!", then continue, if not skip to 40
Click on "Nook"
Select Properties
Click Change Settings (may require UAC elevation)
Click update driver
Select "browse for driver software on your computer"
Browse to the android-sdk/usb_driver folder
click next
You should be done; skip to 49 (I have no idea if this is correct - i pieced it together from somewhere in this as I did not get Nook to appear in the Device Functions List)
If you don't have a "Nook" Device Function, click on "USB Mass Storage Device"
Select Properties
Click Change Settings (may require UAC elevation)
Select the Driver Tab
Click Uninstall
Click OK
Disconnect NC
Reconnect NC
You should be done (this is different from my previous instructions on how to uninstall the NC USB drivers, I have not tested it so YMMV)
Go To: start > run > cmd
type:
Code:
cd <path_to_android_sdk>\tools
./adb.exe kill-server
You should get something like:
* server not running *
Click to expand...
Click to collapse
if adb.exe is not in tools (or tools does not exist), try:
Code:
cd <path_to_android_sdk>\platform-tools
./adb.exe kill-server
type:
Code:
./adb.exe remount
You should get something like:
* daemon not running. starting it now *
* daemon started successfully *
remount failed: No such file or directory
Click to expand...
Click to collapse
You are done configuring to sideload
From here you should be able to sideload from ADB.
To sideload an app, simply do the following:
Code:
./adb.exe install <app_name>
Thanks Rad!
im going insane, ive completely updated the SDK but i cant find this damn android_winusb file
When you updated the SDK, did you install the USB drivers also? If you did, that file should be in whatever directory you installed the SDK in under the usb_driver subdirectory.
cabbieBot said:
im going insane, ive completely updated the SDK but i cant find this damn android_winusb file
Click to expand...
Click to collapse
I'm an idiot, I was certain the USB Drivers were installed. Done and done now, sheesh what a waste of time!
now to hunt for adb_usb which is being a pain to find too. Has anyone found adb_usb on XP?
I can see the folder C:\documents and settings\<username>\.android\ but theres two folders in there for AVD and AndroidDesktopNotifier. Maybe if someone can upload the adb_usb file I can just throw it in the folder and cross my fingers?
I whish to use this tweak...
http://forum.xda-developers.com/showthread.php?t=1010807
i can't find the init.d folder to push the script in... Someone knwo where ?
Yperion said:
The script works only with cyanogens mod roms, i cant post on the dev thread so plz write it for the other users.
Regards.
Click to expand...
Click to collapse
If you don't have CWM then you can do following:
Make a file with this content:
Version 1:
#!/system/bin/sh
if [ -e /sys/devices/virtual/bdi/179:0/read_ahead_kb ]
then
/system/xbin/echo "128" > /sys/devices/virtual/bdi/179:0/read_ahead_kb;
fi;
Version 2 (If the Version 1 is not working for your ROM - credit goes to rafpigna):
# Tweak mmc read-ahead - rafpigna -
mmcfolder="/sys/devices/platform/msm_sdcc.2/mmc_host/mmc1"
cd $mmcfolder
folderlist=`ls -1`
mmcresult=`echo $folderlist | grep -o '\bmmc1:\w*' | sed 's/mmc1://'`
echo 128 > /sys/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:$mmcresult/block/mmcblk0/queue/read_ahead_kb
cd /
Change the red marked number from 128 to what you need (example 2048) and save it as "99sdcardreadfix", copy it with the Root explorer or push it with ADB into /system/etc/init.d and set permissions to 777. Reboot.
just flash one of the links he posted
It doesn't work with xrecovery ... allready tried.
Sent from my X10i using XDA App
then i have no idea sorry
it worked
Just pushed to /etc/init.d/ set permissions on all checked and reboot
Sd seems to be more fast to open pictures !
Testing with sdcard speed test my result is:
5Mb/s to write and 15 Mb/s to read
Tks
/system/etc/init.d
You have such a folder on x10?
Sent from my X10i using XDA App
28spawn said:
it worked
Just pushed to /etc/init.d/ set permissions on all checked and reboot
Sd seems to be more fast to open pictures !
Testing with sdcard speed test my result is:
5Mb/s to write and 15 Mb/s to read
Tks
Click to expand...
Click to collapse
Pls mate..can you upload the file??
Cuspide said:
You have such a folder on x10?
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Yes! what firmware are you running??
2.1 0435. Bitsnaker ...
I look in system/etc/
No init.d folder ... not even with a search ... :-( strange....
Maybe i bypassed the bootloader ... joking of course
Sent from my X10i using XDA App
Cuspide said:
2.1 0435. Bitsnaker ...
I look in system/etc/
No init.d folder ... not even with a search ... :-( strange....
Maybe i bypassed the bootloader ... joking of course
Sent from my X10i using XDA App
Click to expand...
Click to collapse
ahahah..So you are a rock!!! XD
I don't know why you don't have this folder...Maybe you can create yourself..i have only 1 file inside it!! Anyway i try to create the file and copy it to init.d folder but it's not working!! Any help pls??
I all ready tried to create that folder... put the script in, changed the permission... not working...
Really annoying it really boost sd card reading, noticable whan you open gallery for example...
Cuspide said:
I all ready tried to create that folder... put the script in, changed the permission... not working...
Really annoying it really boost sd card reading, noticable whan you open gallery for example...
Click to expand...
Click to collapse
I think there is an error in the text code:
#!/system/bin/sh
if [ -e /sys/devices/virtual/bdi/179:0/read_ahead_kb ]
then
/system/xbin/echo "128" > /sys/devices/virtual/bdi/179:0/read_ahead_kb;
fi;
I can't get the code to work automatically but it works!
Row Labels Average of Read Average of Write
128 18.067 13.033
2048 62.171 13.793
3072 74.785 13.505
4096 69.367 13.595
with 3072 it even hit 90MB/s sometimes!. thx u mate.
28spawn said:
it worked
Just pushed to /etc/init.d/ set permissions on all checked and reboot
Sd seems to be more fast to open pictures !
Testing with sdcard speed test my result is:
5Mb/s to write and 15 Mb/s to read
Tks
Click to expand...
Click to collapse
wanna share your file ?
"Yperion" wrote me in PM:
:The script works only with cyanogens mod roms, i cant post on the dev thread so plz write it for the other users.
Regards.[/QUOTE]
hmm. i was able to run thru recovery. but i dun feel ALOT of diff. just ABIT faster only.
SD tweeks
mrljlamon said:
wanna share your file ?
Click to expand...
Click to collapse
There is nothing to share here I guess. You are looking at wrong file. there si no system/etc there is only etc/init.d when you use root explorer.
however you can edit your values by
- Manually change read_ahead_kb from 128 to 2048, 3072 or 4096 using root explorer.
i am getting 6 mb/s read and 40 or 50 mb/s write
not bad finding
i was able to increase reading speed from ~10Mb to 18Mb with a script file
the problem with this is that after a reboot it returns to 128Kb
but HELL i had a script so everytime i reboot just need to press one button
atintan said:
There is nothing to share here I guess. You are looking at wrong file. there si no system/etc there is only etc/init.d when you use root explorer.
however you can edit your values by
- Manually change read_ahead_kb from 128 to 2048, 3072 or 4096 using root explorer.
i am getting 6 mb/s read and 40 or 50 mb/s write
Click to expand...
Click to collapse
and witch values you use to get those high values?
Thanks to @HypoTurtle for providing the .img files!
Root privilege allows users to download and use apps such as Titanium Backup. It also allows easier modification of settings.
I thought some of you would like a step-by-step to root the most recent .403 Remix OS. I have tried here to put together a procedure that even new members can follow. Please let me know how it works for you.
PLEASE REMEMBER THAT MESSING AROUND MIGHT RESULT IN PROBLEMS IF YOU DO NOT FOLLOW INSTRUCTIONS EXACTLY.
This is only for 64 bit. Please note that you MUST type all command line commands Exactly as shown (including spaces and caps)
To root you will need only two files: one is a modified ramdisk.img that you will install while in Windows; and one is a superuser su.img to add to the data partition from the Remix OS command line.
1 First, if you haven't already, download and install Remix OS Version .403 from their website. Go through the complete installation.
2 Next, from Windows, using your favorite browser, download ramdisk-403.img and su.img from:
https://drive.google.com/folderview?id=0B3gcDbDvV4MkVWRxU3pYMzVUWEU
3 To substitute the new ramdisk.img:
a Open the File Explorer and copy the ramdisk-403.img file.
b From the File Explorer, click on the Drive with your Remix OS.You will see a "RemixOS" folder.
c Click on it to open it. Now you should see the files including one named ramdisk.img.
d Click on the ramdisk.img and select rename the ramdisk.img to ramdiskorig.img to save it "just in case"
e Now rename the ramdisk-403.img to ramdisk.img
4 To finish you need to restart and boot into Remix OS.
a First thing to do in Remix is go to Settings/Experimental features/Enable terminal debug console and activate it.
b Open the File Manager and click on the Disk with Windows installed (usually Disk 1 or Disk 2)
c Click on "Users" and then on your user ID folder
d Find the "Downloads" folder and click on it. You should see the su.img that you downloaded while in Windows
e Click on the su.img file and drag it to the Download folder on the left. It will copy the su.img to your Download folder
5 Now you are ready to copy the su.img into your /data partition.
a Press ALT&F1 to open the command line. You should see a line of text with the # symbol.
b To copy su.img into /data, at the command line type: cp /data/media/0/Download/su.img /data/su.img
c Note that there are spaces ONLY after cp and img
d Press ENTER. If you receive no error message then you did it correctly.
Press ALT&F7 to leave the command line. Play it safe and reboot. You now can download and run any app that requires root access.
Set to go! Have fun. Let me know how it works for you.
Working
Works with 402???
My WiFi didn't broke with 402, so I'll not upgrade to 403...
Regnas said:
Works with 402???
My WiFi didn't broke with 402, so I'll not upgrade to 403...
Click to expand...
Click to collapse
Not sure. My wifi was broken with 402 and 403 fixed it. Whattaworld!
lollyjay said:
Not sure. My wifi was broken with 402 and 403 fixed it. Whattaworld!
Click to expand...
Click to collapse
Yeah, it's funny...
Anyway,I'll try that later..
Cheers..
lollyjay said:
Not sure. My wifi was broken with 402 and 403 fixed it. Whattaworld!
Click to expand...
Click to collapse
Any chance you have an lsmod from both. I know the issue in 402 was that both wl and b43 were both loaded - it might be viable to create a broadcom switch to flick between the two [one's proprietary and the other is open-source]
HypoTurtle said:
Any chance you have an lsmod from both. I know the issue in 402 was that both wl and b43 were both loaded - it might be viable to create a broadcom switch to flick between the two [one's proprietary and the other is open-source]
Click to expand...
Click to collapse
Yes, do you just want an lsmod output or do you want more specific?
lollyjay said:
Yes, do you just want an lsmod output or do you want more specific?
Click to expand...
Click to collapse
Both outputs or a diff 402-dmesg 403-dmesg > 402-403_diff would be fine. For some reason I'm still on 402 -- haven't gotten the 403 ota yet.
HypoTurtle said:
Both outputs or a diff 402-dmesg 403-dmesg > 402-403_diff would be fine. For some reason I'm still on 402 -- haven't gotten the 403 ota yet.
Click to expand...
Click to collapse
I don't have 402 any more. Here is one from 403. Maybe @Regnas can give you the other.
Module Size Used by Tainted: P
binfmt_misc 9163 1
hid_sensor_als 4217 0
hid_sensor_incl_3d 4947 0
hid_sensor_accel_3d 4768 2
hid_sensor_rotation 4683 0
hid_sensor_magn_3d 5925 0
hid_sensor_gyro_3d 4755 0
hid_sensor_trigger 3417 12 hid_sensor_als,hid_sensor_incl_3d,hid_sensor_accel_3d,hid_sensor_rotation,hid_sensor_magn_3d,hid_sensor_gyro_3d
industrialio_triggered_buffer 1874 6 hid_sensor_als,hid_sensor_incl_3d,hid_sensor_accel_3d,hid_sensor_rotation,hid_sensor_magn_3d,hid_sensor_gyro_3d
kfifo_buf 3374 1 industrialio_triggered_buffer
industrialio 45973 11 hid_sensor_als,hid_sensor_incl_3d,hid_sensor_accel_3d,hid_sensor_rotation,hid_sensor_magn_3d,hid_sensor_gyro_3d,hid_sensor_trigger,industrialio_triggered_buffer,kfifo_buf
hid_sensor_iio_common 5514 7 hid_sensor_als,hid_sensor_incl_3d,hid_sensor_accel_3d,hid_sensor_rotation,hid_sensor_magn_3d,hid_sensor_gyro_3d,hid_sensor_trigger
hid_sensor_custom 9846 0
rtsx_pci_ms 8248 0
memstick 9812 1 rtsx_pci_ms
rtsx_pci_sdmmc 15489 0
mac_hid 3843 0
bsd_comp 4698 0
ppp_deflate 3798 0
ppp_async 6285 0
pppoe 8725 0
pppox 2638 1 pppoe
ppp_generic 22934 5 bsd_comp,ppp_deflate,ppp_async,pppoe,pppox
slhc 5081 1 ppp_generic
wmi 8736 0
wl 6426390 0
cfg80211 477899 1 wl
uvcvideo 66519 1
snd_hda_codec_hdmi 38342 1
videobuf2_vmalloc 4693 1 uvcvideo
videobuf2_memops 2716 1 videobuf2_vmalloc
videobuf2_v4l2 19150 1 uvcvideo
videobuf2_core 21313 2 uvcvideo,videobuf2_v4l2
snd_hda_codec_realtek 67326 1
snd_hda_codec_generic 53744 1 snd_hda_codec_realtek
thinkpad_acpi 66626 1
nvram 6533 1 thinkpad_acpi
soc_button_array 2418 0
snd_hda_intel 28041 1
snd_hda_codec 105597 4 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_codec_generic,snd_hda_intel
snd_hda_core 53903 5 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_codec_generic,snd_hda_intel,snd_hda_codec
snd_hwdep 5785 1 snd_hda_codec
snd_pcm 87019 5 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
snd_timer 20488 1 snd_pcm
snd 65356 9 snd_hda_codec_hdmi,snd_hda_codec_generic,thinkpad_acpi,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 6615 1 snd
shpchp 23487 0
rtsx_pci 41858 2 rtsx_pci_ms,rtsx_pci_sdmmc
r8169 61453 0
mii 4910 1 r8169
psmouse 101828 0
pcspkr 2158 0
lpc_ich 14290 0
intel_rst 2468 0
i915 1084918 9
drm_kms_helper 108824 1 i915
drm 311256 11 i915,drm_kms_helper
fb_sys_fops 1759 1 drm_kms_helper
syscopyarea 3185 1 drm_kms_helper
sysfillrect 3485 1 drm_kms_helper
sysimgblt 2562 1 drm_kms_helper
i2c_algo_bit 5421 1 i915
i2c_i801 16755 0
hid_sensor_hub 11145 9 hid_sensor_als,hid_sensor_incl_3d,hid_sensor_accel_3d,hid_sensor_rotation,hid_sensor_magn_3d,hid_sensor_gyro_3d,hid_sensor_trigger,hid_sensor_iio_common,hid_sensor_custom
hid_multitouch 10208 0
coretemp 6156 0
hwmon 4404 2 thinkpad_acpi,coretemp
btusb 31833 0
btrtl 4762 1 btusb
btbcm 7000 1 btusb
btintel 8387 1 btusb
bluetooth 444084 9 btusb,btrtl,btbcm,btintel
Sent from my on Z00A using XDA Labs
Hi @lollyjay, the method is simple and easy and is working great....Thanks a lot for that.....But how do we enable system r/w because it did not let me edit build.prop to enable brigntness slider... in earlier version I used modified initrd.img....it there any other way to achieve system r/w... Thanks...
lollyjay said:
I don't have 402 any more. Here is one from 403. Maybe @Regnas can give you the other.
Click to expand...
Click to collapse
I would like to help but I don't know how to generate this info..
What is this?
ssanjy said:
Hi @lollyjay, the method is simple and easy and is working great....Thanks a lot for that.....But how do we enable system r/w because it did not let me edit build.prop to enable brigntness slider... in earlier version I used modified initrd.img....it there any other way to achieve system r/w... Thanks...
Click to expand...
Click to collapse
They have removed the brightness slider in 402 at least.
I'm not sure which ramdisk this is; check getprop and see what ro.remixos.box is set to.
I'll upload my ramdisk if you want to check if the slider was readded in 403 [if its set to true].
I also have the modified initrd.img on my thread; where these .imgs are from. But ideally it's best not to use it; the only downside being needing to modify ramdisk.img itself for ro.* prop entries.
HypoTurtle said:
They have removed the brightness slider in 402 at least.
I'm not sure which ramdisk this is; check getprop and see what ro.remixos.box is set to.
I'll upload my ramdisk if you want to check if the slider was readded in 403 [if its set to true].
I also have the modified initrd.img on my thread; where these .imgs are from. But ideally it's best not to use it; the only downside being needing to modify ramdisk.img itself for ro.* prop entries.
Click to expand...
Click to collapse
remixos.box is set to true and when I tried to change it to false I couldn't save it... While in 402 I had found modified initrd which did let me change value of build prop... Anyway thanks for the info
Sent from my S II using XDA Labs
ssanjy said:
remixos.box is set to true and when I tried to change it to false I couldn't save it... While in 402 I had found modified initrd which did let me change value of build prop... Anyway thanks for the info
Click to expand...
Click to collapse
Hi you might try Root Browser from Play Store it can change permissions
Sent from my on Z00A using XDA Labs
lollyjay said:
I don't have 402 any more. Here is one from 403. Maybe @Regnas can give you the other.
Sent from my on Z00A using XDA Labs
Click to expand...
Click to collapse
It would need both from the same device; think I found a 402 that you posted elsewhere.
Code:
[b]Removed[/b]
b43 375752 0
mac80211 504422 1 b43
ssb 45258 1 b43
rng_core 7153 1 b43
bcma 43126 1 b43
efivars 7470 0 [efi variables]
[b]Added[/b]
intel_rst 2468 0 [rapid storage tech]
psmouse 101828 0 [touchpad]
would be the module difference between 402 and 403; so perhaps just blacklisting b43 on 402 would have sufficed [the others are dependant on it]
ssanjy said:
remixos.box is set to true and when I tried to change it to false I couldn't save it... While in 402 I had found modified initrd which did let me change value of build prop... Anyway thanks for the info
Sent from my S II using XDA Labs
Click to expand...
Click to collapse
The 402 initrd should work fine [attach the 403 here just so I can compare to 402 just to see if anything was changed] if you want to modify it that way; but the slider is gone. Only options would be to add a shortcut to the brightness activity from SystemUI or a brightness app.
Hey guys, I'm using an HD install of remix os 403 - replaced the ramdisk - went back into Remix but couldn't access the ALT+F1 terminal for whatever reason. Eventually I managed to get the su.img into the right folder in the data.img and nothing happens. How would I be notified that it has worked? Would I see something different on startup? I assume the su.img is being mounted etc by the modified ramdisk.img.
Would it be a possibility to just make a fresh, clean data.img with just that su.img file already in? That way I could try just replacing the data.img and starting fresh. At this moment I can't see any change from the su.img and ramdisk.img being in place. Probably it's a problem at my end - but i'm confused why the ALT+F1 root terminal doesn't work for me?
I'm using a UK keyboard on an Alienware M17x R4 - any suggestions would be very welcome.
By the way I used Paragon ExtFS for Windows to access the data.img and insert the su.img file (which I verified in the terminal of remixos (not the root terminal, I couldn't get that working) but I can use the LS command in /data and I see that su.img is there.
Thank you for any suggestions
mrpras said:
Hey guys, I'm using an HD install of remix os 403 - replaced the ramdisk - went back into Remix but couldn't access the ALT+F1 terminal for whatever reason. Eventually I managed to get the su.img into the right folder in the data.img and nothing happens. How would I be notified that it has worked? Would I see something different on startup? I assume the su.img is being mounted etc by the modified ramdisk.img.
Would it be a possibility to just make a fresh, clean data.img with just that su.img file already in? That way I could try just replacing the data.img and starting fresh. At this moment I can't see any change from the su.img and ramdisk.img being in place. Probably it's a problem at my end - but i'm confused why the ALT+F1 root terminal doesn't work for me?
I'm using a UK keyboard on an Alienware M17x R4 - any suggestions would be very welcome.
By the way I used Paragon ExtFS for Windows to access the data.img and insert the su.img file (which I verified in the terminal of remixos (not the root terminal, I couldn't get that working) but I can use the LS command in /data and I see that su.img is there.
Thank you for any suggestions
Click to expand...
Click to collapse
Did you remember to go into settings/experimental features to enable terminal debug console? If so try Alt&right arrow for entry/egress
Sent from my on Z00A using XDA Labs
lollyjay said:
Did you remember to go into settings/experimental features to enable terminal debug console? If so try Alt&right arrow for entry/egress
Sent from my on Z00A using XDA Labs
Click to expand...
Click to collapse
I hadn't enabled the console/debug option thank you for that!
Now I'll go and try again. Thanks for the fix, and the systemless root files. I'll be back if it doesn't work, otherwise thanks again!
---------- Post added at 05:50 PM ---------- Previous post was at 05:28 PM ----------
Okay thanks, so that works - Just a small suggestion that somewhere in your description (where you mention the Alt+F1) it could be worth mentioning about enabling the debug console because I didn't find that information when scouring around. Maybe would be helpful to others as ignorant as me
mrpras said:
I hadn't enabled the console/debug option thank you for that!
Now I'll go and try again. Thanks for the fix, and the systemless root files. I'll be back if it doesn't work, otherwise thanks again!
Click to expand...
Click to collapse
My pleasure. You can test root by downloading an app that requires root such as Titanium Backup. It will immediately let you know if it cannot acquire root privilege
Sent from my on Z00A using XDA Labs
Just wanted to note here that the Lenovo ThinkPad Twist is a great dual Windows /Ubuntu and Remix OS daily driver. Great touchscreen display and can be used as a (heavy) tablet with Remix OS. Look at this on eBay http://www.ebay.com/itm/162121987813
I bought three from a school for $99 each.
Sent from my on Z00A using XDA Labs
Greetings!
First, this message will be rather long, for which I apologize. I am providing headings that allow whomever is interested to skip to whatever is relevant to them.
About the device:
It is one of two Eken GC10X tablets, purchased from Micro Center a while back dirt cheap. The second one is 6000 miles away in Europe. . . .
It is currently running Android 4.2.2
Its firmware revision is v2.0patch1
Its kernel version is 3.4.39+, dated Friday, October 18th, 2013, at 18:11:40 CST
Its build number is wing_k70-eng 4.2.2 JDQ39 20131028 test-keys
It comes pre-rooted by default. All that needs to be done is to install a terminal program and pay attention to certain paths.
About me:
I have been messing with computers, programming, and operating systems since the time of "wood burning computers"
I know my hosts file from my fstab, I have run various flavors of both Linux and Windows in both client and server configurations, and I know that both man pages and a good search engine Are Your Friends. (which is how I came to be here!)
Issue:
Since this Eken tablet comes with a bare minimum of internal memory, I was researching ways to mitigate this. I found an article that mentioned a workaround:
Copy everything in root to a large external SD card
Transpose the settings for the internal and external memory in the /etc/vold.fstab file
Save and Reboot
The result of this is a tablet that - regardless of the presence or absence of any external SD card - always boots as if it had never been booted before, (returns to "first-boot / out-of-box" setup). Any installed apps are gone and the "internal" memory - which is about 1-2 gigs - shows absolutely full. In addition to all that, I cannot do anything with the ADB port since it requires setting the "USB Debugging" flag, which gets reset on reboot. (i.e. The ADB interface is not available.
Examining the vold.fstab shows that the original setup of that file has been returned after I did a nuke-and-reboot.
I can reboot and re-install a terminal program and advanced file manager. (X-plore is my favorite)
I see three possible solutions:
Find the reason why it's booting like this and fix it.
Find a compatible firmware release for this tablet and re-flash it - if possible - from an external SD card.[/INDENT]
Do some kind of "nandroid" backup from the other Eken GC10X tablet I have and copy it to this one. Unfortunately it's 6000 miles away and I won't be able to get to it until sometime after January 2019. In addition, I cannot access the device via the ADB port.
Research I have done:
gsmhosting's allwinner forums
This site claims to have a (ahem!), "modified" version of the firmware, which I have downloaded.
The androidmtk site
This site has the "PhoenixCard" software which alleges that it can be used to create external SD card images of firmware files that can:
Install firmware from the SD card to the device.
Allow you to run the firmware from the SD card to verify it. It should be noted that MalwareBytes flags the updater.exe file because it attempts to download from a known Trojan site. Renaming the extension, (exe.bad), solves that problem.
I have not tried re-flashing any firmware version, though I have tried running the firmware from SD, which doesn't work.
Can someone help me with suggestions on how to return this tablet to normal?
Thanks in advance for any help you can provide!
Solution:
I guess it's "umpteenth time's the charm!" :highfive:
Having done considerable research, (with everything pointing to an issue with the busybox file being in the wrong place), I decided to revisit this, did a little more digging and ultimately found a solution.
Since nothing irritates me more than someone posting "I fixed it!" without telling everyone else HOW they fixed it, here are the steps I used to solve this problem.
Please be careful. You will be mucking around with your tablet's/phone's root file system in ways that can be fatal if you're not paying attention. It's not that difficult but you DO have to PAY ATTENTION to what you're doing.
TO-DO:
Instead of copying the busybox file, it should really be a symlink to /sbin/busybox.
If anyone figures out a way to create a symlink in Android that actually works, I'd like to know.
Here it is:
Pre-requisites:
The device MUST be rooted for this to work. I cannot help you with advice on how to root individual devices. This Eken tablet comes rooted by default.
Download off-line from Android Archives, (using a different system), an early version of X-plore, which is an excellent file manager.
Load X-plore onto a thumb-drive or a micro-SD card, (I used a micro-SD), and then install the SD card / thumb drive into the tablet you're trying to fix.
Steps to solve the problem:
First, go to Settings => Security and enable "unknown sources"
Open your device's file manager
Find the copy of X-plore you downloaded, and tap it to begin the off-line installation process.
Once it installs, open it and go to the "configuration" menu. This is within the three-dot menu drop-down in the upper right-hand corner.
Select:
* (near the top) Show hidden files => select the check-box. (optional)
* Root Access => Superuser + mount writable (this allows you to change permissions to permit writing the root filesystem)
* (scroll down) Dark mode => select the check-box. (this is a personal preference; IMHO it makes it easier to read.)
* Exit configuration by using the "back" button or back arrow in the upper left corner.
* You should now see two columns representing two views of the device's file-system.
On the left side, open the "Root" filesystem, also labeled with a "/"
Scroll down and find the "/sbin" folder and open it by tapping on it.
* You may, or may not, see several folders and files. You are looking for the file "busybox"
* If you don't see it there, you may have to "find" it using the magnifying glass icon in the center row of icons.
* Open the "find" dialog and replace the "*.*" with "busybox" and then select "OK".
* (assuming you found it), tap at the right-hand edge of the row with the file-name to "select" it - a big check-mark will appear there.
Go to the right-hand side list now. Find and open:
* Root (/) like you did before.
* system
* bin
* At the top of that column, you should see a folder icon, followed by "/system/bin"
Look to see if there is a file named "busybox" there. (In my case, it was missing - which is the problem)
(assuming it's missing)
Collapse the "bin" folder by tapping on it - it might take a couple of taps.
Touch-and-hold the "bin" folder until a long list appears. Scroll down to the bottom of that list and select "permissions"
Within the permissions dialog, there are three columns: Read, Write, and Execute.
* There should be three selected boxes under "Read".
* There should be ONE selected box, the top one, under "Write"
* There should be three selected boxes under "Execute"
* Directly below the last box under "Read", the box labeled "Recursive" should NOT be selected.
* To the far right of "Recursive" should be a note that reads "Mode: 755"
Under the heading "Write", select the other two boxes so that all three are selected. The word "Mode" should now be followed by "777" Close the permissions dialog by selecting "OK".
Verify the following:
* The arrow at the top of the center column is pointing to the right. If it is not pointing to the right, tap it until it points toward the right-hand column.
* The file "busybox" on the left-hand pane has a check-mark next to it and no other files are selected.
* The "bin" folder on the right-hand side has been collapsed and is selected by being a darker black with NO check-mark.
* The top of that column shows the folder icon and "/system/bin" as the selected path.
Copy the "busybox" file into the /system/bin folder by doing the following:
* Tap the "copy" icon in the center column - it will look like two pieces of paper stacked together.
* Verify that the dialog that opens:
* Just below the top right it says "busybox" (the file you're copying)
* Under that, "Copy to"
* Under that, a folder icon and then "/system/bin".
* Under that, the selection "Move mode (delete source files) is NOT selected!
* Tap "OK" to copy the file to /system/bin. Once the copy is done, the dialog will close.
Tap "bin" on the right hand side to open it if it does not open by itself.
Verify that "busybox" appears in both the left and right hand panes.
Press and hold the "busybox" file until the list dialog re-appears.
* Select "permissions".
* Verify that all three "Read" permissions are set, only the top "Write" permission is set, and all three "Execute" permissions are set. (You may have to clear the bottom two "Write" check-boxes.)
* Verify the "Mode" is set to "755"
* Close the permissions dialog by tapping "OK"
Collapse the "bin" folder by tapping on it.
Long-press the "bin" folder, select "permissions", and set the permissions of the bin folder to "755" the way you did for the busybox file above.
Return to the "Configuration" menu by following the steps at the beginning and select "Superuser" or "Normal User" instead of "Superuser + mount writable" to prevent accidental changes in the future.
At this point, you should be able to close and re-open X-plore and verify that "busybox" actually exists within /system/bin. If it does, you can reboot and your should be good to go.
If it's not there, re-trace the steps I listed above, paying particular attention to the "Superuser" setting in "configuration" and the various file permissions.
If you're still having trouble, post a reply below and I will try to provide what help I can.
Thanks for your patience and I hope this helps others who were puzzling with this as long as I was.