Yeah!!!!
pcGoose said:
Yeah!!!!
Click to expand...
Click to collapse
How'd you go about it?
Sent from my SM-N920T using Tapatalk
I connected Remix mini to pc with UART cable, and installed update-su.xxx. zip from there.
You GOTTA post some How-To's here!
MANY Remix Mini owners on the planet are trying to accomplish just this!
Great Job, though.
For those who would like to root Remix Mini:
Jide will not offer root access and do not encourage our users to root their devices as it voids the warranty of Remix Mini.
The gain of root access outshadows the lost warranty of any device imo. We are not even talking about a 700$ device here.
Done a quick search here before work. Correct there are 3v and 5v uart? At what voltage level do we need to be to interface with the mini?
RemixOS_Cameron said:
For those who would like to root Remix Mini:
Jide will not offer root access and do not encourage our users to root their devices as it voids the warranty of Remix Mini.
Click to expand...
Click to collapse
i was 1 of the original backers of this kickstarter project and was looking forward with excitement to receiving my mini told some of my friends and relatives who were also enthusiastic, so i received my mini played with it and patiently waited for a method to become available to root it people asked me about my mini but in all honesty could not recommend it because of the lack of root access.
i believe most of the people who backed the project are like myself enthusiasts and have at least 1 or more rooted devices have become dismayed by JIDE`S intransigence by refusing to offer any form of root access they are now playing catchup as remix os gets ported to other devices with better specs . i know were ill be looking for my next version of remix os and it sadly wont be with JIDE.
There's a header for UART on the corner of the PCB. Hook up RX, TX, and GND through a serial port. RX -> TX, TX -> RX and GND -> GND. Serial-to-USB/FTDI works, it's what I'm using right now.
Use minicom (or something like CoolTerm if you're on Windows) to connect: 8N1 (8 data bits, no parity bits, 1 stop bit) with a baudrate of 115200.
Bam. Root terminal.
Code:
[email protected]:/ # ls
acct
cache
charger
config
d
data
default.prop
dev
etc
file_contexts
fstab.sun50iw1p1
init
init.common.rc
init.environ.rc
init.rc
init.recovery.sun50iw1p1.rc
init.sun50iw1p1.rc
init.sun50iw1p1.usb.rc
init.trace.rc
init.usb.rc
init.zygote32.rc
init.zygote64_32.rc
logger
mnt
nand.ko
proc
property_contexts
root
sbin
sdcard
seapp_contexts
selinux_version
sepolicy
service_contexts
storage
sunxi-ir-rx.ko
sunxi_tr.ko
sys
system
ueventd.rc
ueventd.sun50iw1p1.rc
vendor
verity_key
[email protected]:/ #
johnmurrayvi said:
There's a header for UART on the corner of the PCB. Hook up RX, TX, and GND through a serial port. RX -> TX, TX -> RX and GND -> GND. Serial-to-USB/FTDI works, it's what I'm using right now.
Use minicom (or something like CoolTerm if you're on Windows) to connect: 8N1 (8 data bits, no parity bits, 1 stop bit) with a baudrate of 115200.
Bam. Root terminal.
Click to expand...
Click to collapse
http://www.ftdichip.com/Products/Cables/USBTTLSerial.htm
Just for verification. any cable goes since we are not connecting vcc?
It is the cable I am using
"Eruner PL2303HX USB To TTL To UART RS232 COM Cable Module Converter" : Amazon ($6.99)
White -> TX
Green -> RX
Black -> GND
1. Download UPDATE-SuperSU.zip
2. Unzip the UPDATE-SuperSU.zip
3. Copy superSU and META-INF/com/google/android/update-binary(from #2) onto USB drive
on putty
mount -o rw,remount /
mount -o rw,remount /system
cd /system/bin
ln -s busybox-smp unzip
cd /data/local/tmp
cp /mnt/usbhost/Storage01/UPDATE-SuperSU-xxx.zip /data/local/tmp
cp /mnt/usbhost/Storage01/update-binary /data/local/tmp
sh update-binary 0 1 /data/local/tmp/UPDATE-SuperSU-xxx.zip
reboot
Nidor said:
http://www.ftdichip.com/Products/Cables/USBTTLSerial.htm
Just for verification. any cable goes since we are not connecting vcc?
Click to expand...
Click to collapse
Yeah any should work.
I just grabbed the one I had in front of me already, from Sparkfun, which happened to be 3.3V since I'm using it for XBees. Worked fine for me.
pcGoose said:
It is the cable I am using
"Eruner PL2303HX USB To TTL To UART RS232 COM Cable Module Converter" : Amazon ($6.99)
Click to expand...
Click to collapse
If you don't have one already, I'd say go with pcGoose's choice. FTDI ones are pretty pricey these days.
No, we are not connecting vcc。
johnmurrayvi said:
Yeah any should work.
I just grabbed the one I had in front of me already, from Sparkfun, which happened to be 3.3V since I'm using it for XBees. Worked fine for me.
If you don't have one already, I'd say go with pcGoose's choice. FTDI ones are pretty pricey these days.
Click to expand...
Click to collapse
pcGoose said:
No, we are not connecting vcc。
Click to expand...
Click to collapse
Just RX, TX, and GND.
Whoops, didn't mean to imply 3.3V was actually related to the Mini's UART.
Thanks for catching that, didn't intend for that ambiguity.
@johnmurrayvi @pcGoose
Thanks for the info. Finally I can get started on actually using my mini.
SuperSU install doesn't work.
I tried to install SuperSU v265, but it wouldn't install. Then I tried to install SuperSU v246 and it did something, but now Remix isn't booting any more! :crying: I can still communicate with Remix Mini via CoolTerm, but my thumb drive isn't available any more. (I guess you call it not mounted??)
As a Windows User, I guess can use some help here!
Can you post a link to a working UPDATE-SuperSU-xxx.zip ? (I mean one that would work here on Remix Mini)
Guerol said:
I tried to install SuperSU v265, but it wouldn't install. Then I tried to install SuperSU v246 and it did something, but now Remix isn't booting any more! :crying: I can still communicate with Remix Mini via CoolTerm, but my thumb drive isn't available any more. (I guess you call it not mounted??)
As a Windows User, I guess can use some help here!
Can you post a link to a working UPDATE-SuperSU-xxx.zip ? (I mean one that would work here on Remix Mini)
Click to expand...
Click to collapse
https://download.chainfire.eu/696/SuperSU/
I'm about to buy an USBUART PL2302 Cable, hoping it works.
pcGoose said:
https://download.chainfire.eu/696/SuperSU/
Click to expand...
Click to collapse
This is the same SuperSU v2.46, what broke my Remix Mini in the first place...
Could the Remix Mini Version be relevant?
I have another Rexmix Mini unopened in original packaging. Would it help to use this one without updating first?
Guerol said:
This is the same SuperSU v2.46, what broke my Remix Mini in the first place...
Could the Remix Mini Version be relevant?
I have another Rexmix Mini unopened in original packaging. Would it help to use this one without updating first?
Click to expand...
Click to collapse
experiencing the same thing as you. Thought I missed something but haven't had time to play around with it.
I updated to latest os version before trying to root. Everything seemed ok during the steps but after reboot it never gets past second bootlogo and can't seem to mount usb even through terminal cmd...
maybe they implemented something in newer os version that on startup looks for changes/modifications?
If you got the stomach for it I'll say try and root your second one without updating it first.
did you install busybox ?
Nidor said:
experiencing the same thing as you. Thought I missed something but haven't had time to play around with it.
I updated to latest os version before trying to root. Everything seemed ok during the steps but after reboot it never gets past second bootlogo and can't seem to mount usb even through terminal cmd...
maybe they implemented something in newer os version that on startup looks for changes/modifications?
If you got the stomach for it I'll say try and root your second one without updating it first.
Click to expand...
Click to collapse
here is a link to a chinese site the guy said he installed busybox first
h**p://23pin.logdown.com/posts/435610-root-remix-mini
Related
This guide is to enable USB charging on your Samsung Galaxy Tab.
Requirements:
- Any rooted ROM with Pershoot's kernel
- ScriptManager (free market app)
- USB Charging Script
Procedures
- Ensure you have a rooted rom/custom rom with pershoot's kernel like task650 and PhantomHacker's In Paris rom. Download and install ScriptManager from Android Market. Download the script using the link above and store it anywhere on your tab.
- Open script manager
- Navigate to wherever you stored the script and choose it. Tick run as root and run on boot. Press run.
- If it asks for superuser/root access, please allow it.
- you're done. Press home to exit. Reboot.
Note
Please read and follow all instructions and I am not responsible if anything goes wrong. this should not damage your battery. the reason why samsung disabled usb charging is not because they were worried it would damage the battery. it is because the tab charges very slowly over usb, so they didnt want people to leave a zero battery tablet charging overnight on their pc usb to wake up and find that its only charged 50%.
The common USB connections provide 5 volts DC and between 500mAh to 1,000mAh at most whereas the main power supply provides 12 volts DC and between 1200mAh to 2400mAh. Our Samsung Galaxy Tab needs about 2,000mAh for normal charging. This mod just lets you charge using that low voltage and current from the usb anyways. It is useful for someone like me who never lets the battery drain to zero and I am almost always next to a laptop so when I am watching tv or doing something else, it is always charging.
thanks to pershoot for his kernel, developers on this forum for their excellent roms.
thanks to Giblet-dono for his help and pointers in this thread
dpakrr said:
This guide is to enable USB charging on your Samsung Galaxy Tab. Please read and follow all instructions and I am not responsible if anything goes wrong.
Requirements:
- Any ROM with Pershoot's kernel
- Samsung Mobile drivers (most of you should already have them)
- Latest Android SDK (download the zip file)
- ADB files
Procedure:
- Dont plug in your Galaxy Tab via USB yet. Make a nandroid backup just incase something goes wrong. (Boot into clockworkmod recovery -> backup and restore -> backup)
- Install the Samsung Mobile drivers
- Extract the contents of the sdk zip file onto your desktop. you should get a folder called android-sdk-windows.
- Open this folder and copy all its contents. Go to your C: drive and create a folder called androidsdk and paste the files into this folder.
- Extract the contents of the ADB files zip file you downloaded to C:\androidsdk\tools
- On your tablet, go to Settings->Applications->Development and enable USB debugging. Plug in your Galaxy Tab now.
- On your Windows computer, click on Start and type in cmd in the search bar and press enter.
- type the following and press enter after each line
cd\
cd androidsdk\tools
adb devices
- you should see a combinations of letters and numbers followed by the word device. this means that the adb can interact with your tablet.
- type in the following to enable usb charging (ensure that command prompt is still in the C:\androidsdk\tools folder). again press enter after each line.
adb shell
echo 1 > /sys/class/power_supply/battery/force_usb_charging
exit
you should now be able to charge your tablet via usb.
thanks to pershoot for his kernel, developers on this forum for their excellent roms, and a whole bunch of online guides i looked up on how to access adb lol
Click to expand...
Click to collapse
Will this work on my viewsonic gtablet as well?
hi sorry. like i said in the "requirements", for this to work you need a kernel made by a developer called pershoot. i dont know if hes made any for the viewsonic tablets. please visit his website and see if he has kernels for viewonic tablets and if he has included the option to enable usb charging on them
thats amazing, will try it as soon as possible
SamerBerjawi said:
thats amazing, will try it as soon as possible
Click to expand...
Click to collapse
thanks. let me know how you go.
I do this on tab with terminal emulator every time I reboot. No need to plug in and ADB.
Just su before echo...
Sent from my SPH-D710 using Tapatalk
halmo20 said:
I do this on tab with terminal emulator every time I reboot. No need to plug in and ADB.
Just su before echo...
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Hi thanks. If there's an easier way of ddoing this can you please tell us the steps. I did what you suggested but it says permission denied. Thanks
I have put the line in a init.d script which automatically runs on boot!
You can also use script manager (free) to make a script which does this on boot !
Goodluck!
Giblet-dono said:
I have put the line in a init.d script which automatically runs on boot!
You can also use script manager (free) to make a script which does is on boot !
Goodluck!
Click to expand...
Click to collapse
Hi thanks. So did you jjust created a script with the following line -
echo 1 > /sys/class/power_supply/battery/force_usb_charging
OK figured it out thx
Work work work, thank you bro .
uomoto said:
Work work work, thank you bro .
Click to expand...
Click to collapse
Your welcome. Are you following the old instructions or the new ones? If you follow the new instructions the usb charging is always set to on even after you restart
Giblet-dono said:
I have put the line in a init.d script which automatically runs on boot!
You can also use script manager (free) to make a script which does this on boot !
Goodluck!
Click to expand...
Click to collapse
Adding to an existing script works for me. Could not get it working for a new script. Must be missing something. Ironically I just made two cables up tonight with resistors as per other forums. Both hardware and software setups work well! Screw you Samsung
Oh and, THANK YOU for the tip. Go Blacks!
Do you leave the #!... Line in there or delete that?
Keep getting permission denied when I run it. A superhero issue?
tallgrasshawk said:
Do you leave the #!... Line in there or delete that?
Keep getting permission denied when I run it. A superhero issue?
Click to expand...
Click to collapse
Yep leave that line there. Press enter to go to the next line. Then type in
su
Press enter again. It should ask for superuser permission which requires root. Allow it root access. Now type in
echo 1 > /sys/class/power_supply/battery/force_usb_charging
And save it and follow the rest of the steps in OP
I'm not getting a su request when I'm typing the script. Getting a notification when I run it, then says su isn't found
tallgrasshawk said:
I'm not getting a su request when I'm typing the script. Getting a notification when I run it, then says su isn't found
Click to expand...
Click to collapse
Make sure of the following -
- your tablet is rooted
- you have busybox v1.18.2 or lower by downloading busybox installer from market
running in Paris, so that's taken care of.
Su gave permission now. It's just sitting there saying it's running [email protected]:/ #. should it stay like that or will it finish at some point. Thanks for the script, once I figure this out it'll be great.
tallgrasshawk said:
running in Paris, so that's taken care of.
Su gave permission now. It's just sitting there saying it's running [email protected]:/ #. should it stay like that or will it finish at some point. Thanks for the script, once I figure this out it'll be great.
Click to expand...
Click to collapse
Yep its supposed to just sit there. Once you have saved it, just press the back key and choose the file you created. Tick run as root and run on boot and click run. Again it won't do much and it will just show you a command prompt screen. Press home. It should work.
If its getting too complicated for you to follow, I just uploaded my script in the OP. just download it to your tab and run it using ScriptManager. Just tick run as root and run on boot and run it. Thats all. Dont need to type anything.
I tried it, it's working. Thanks for the mod
I'm curious about one thing regarding this mod.
Would it be possible that this can hurt the battery? I mean, what happends to the battery if it gets fed with a current and voltage that is not the current and voltage it was made for? Could that damage the cells?
I'm a computer engineering student but unfortunately we do not study much electronics, perhaps someone with deep electronics and/or chemical knowledge could write something about this? Would be awesome to know more on why/why not it can/can not harm the battery.
Could someone compile the following file for me? I'd do it myself, but, unfortunately, I don't have access to a computer, nor will I for a while (I'm touchpad only for now).
https://github.com/CyanogenMod/hp-kernel-tenderloin/blob/gingerbread/drivers/net/usb/mcs7830.c
The driver is for a USB-Ethernet adapter that I'm trying to get working on the Touchpad through ICS (cm9).
Thanks.
Is this for USB 3g dongles??
No, not for a 3G adapter, but for one that goes from USB to Ethernet cable.
jcsullins compiled it for me, by the way, so I no longer need the driver (many thanks to him).
However, I can confirm that ICS on CM9 recognized it without problems as eth0 and once I ran dhcpd and assigned a DNS server, I had no problems connecting to the internet. So feel free to add a driver for your own adapter if you have one.
So to review:
-copy driver (to /system/lib/modules)
-insert module ("insmod /system/lib/modules/*yourdriver*.ko")
-get an IP address (manually, or "/system/bin/dhcpd eth0")
-add DNS (setprop net.dns1 *yourDNSserver*)
A couple caveats, I've noticed.
1) It doesn't play nice with wifi. I sort of expected this, but bringing up wlan0 and eth0 at the same time crashes the tablet.
2) Not all apps recognize the internet connection. This is a bit frustrating since most do (including the Browser), but not all.
potissimus said:
No, not for a 3G adapter, but for one that goes from USB to Ethernet cable.
jcsullins compiled it for me, by the way, so I no longer need the driver (many thanks to him).
However, I can confirm that ICS on CM9 recognized it without problems as eth0 and once I ran dhcpd and assigned a DNS server, I had no problems connecting to the internet. So feel free to add a driver for your own adapter if you have one.
So to review:
-copy driver (to /system/lib/modules)
-insert module ("insmod /system/lib/modules/*yourdriver*.ko")
-get an IP address (manually, or "/system/bin/dhcpd eth0")
-add DNS (setprop net.dns1 *yourDNSserver*)
A couple caveats, I've noticed.
1) It doesn't play nice with wifi. I sort of expected this, but bringing up wlan0 and eth0 at the same time crashes the tablet.
2) Not all apps recognize the internet connection. This is a bit frustrating since most do (including the Browser), but not all.
Click to expand...
Click to collapse
Thanks for the extra info--but a link the the driver jcsullins provided you would be a lot more helpful! Any chance you can post it somewhere for us?
all4adriver said:
Thanks for the extra info--but a link the the driver jcsullins provided you would be a lot more helpful! Any chance you can post it somewhere for us?
Click to expand...
Click to collapse
*bump*
is there a USB ethernet adapter that will work on our touchpads without a driver?
all4adriver said:
*bump*
is there a USB ethernet adapter that will work on our touchpads without a driver?
Click to expand...
Click to collapse
I figured out how to compile drivers manually myself shortly after my posts in this thread. I havent used my build environment in a while though, should still be able to check out what (if any) drivers are built into the kernel by default. Do you already have an adapter?
ba114 said:
I figured out how to compile drivers manually myself shortly after my posts in this thread. I havent used my build environment in a while though, should still be able to check out what (if any) drivers are built into the kernel by default. Do you already have an adapter?
Click to expand...
Click to collapse
OMG thank you for responding! No, I don't have an adapter yet--was waiting to find out which one works and I'll buy that. I'm open to suggestions. Thank you!
You are my shining beacon of hope ba114! Have you had a chance to see what drivers might exist in the kernel?
I read elsewhere that the cyanogenmod for the asus transformer contains a driver compatible with Asix AX88772. That chipset is what this cheapo adapter (OMG, no links for noobs!) uses. I have half a mind to buy one just to see, but it would help immensely if someone could confirm that jcsullins cm9 or cm10 for the touchpad also has support for this chipset baked in...
Hopefully giving you something to work with will make this less of a "needle in the haystack"...
Thanks!
really wish I could post links, as jscullins has posted the driver!
hxxp://goo.im/devs/jcsullins/cmtouchpad/misc/mcs7830.ko
all4adriver said:
really wish I could post links, as jscullins has posted the driver!
hxxp://goo.im/devs/jcsullins/cmtouchpad/misc/mcs7830.ko
Click to expand...
Click to collapse
http://goo.im/devs/jcsullins/cmtouchpad/misc/mcs7830.ko
could use some help
OK, finally got my OTG cable and USB ethernet. Let's do this!
Tried to follow these instructions:
So to review:
-copy driver (to /system/lib/modules)
-insert module ("insmod /system/lib/modules/*yourdriver*.ko")
-get an IP address (manually, or "/system/bin/dhcpd eth0")
-add DNS (setprop net.dns1 *yourDNSserver*)
Had to troubleshoot why my Touchpad wasn't being seen as a USB mass storage device. DONE. I'm feeling like a boss.
Windows Explorer didn't see the main system--just the "SD Card". What ever--not big deal. I copied the driver over to the SD Card. Downloaded Astro File Manager to copy the file to /system/lib/modules. Nope. Denied.
No problem! Dropped to terminal and enabled super user. Astro is still a no go. No worries!! I'm a big boy--I'll do this in terminal! Taught myself enough command line jargon to navigate to the file, and copy it to the intended directory. NOPE. Directory is read only.
OK, so I navigate there and try to chmod the directory with u+w. "Bad mode". Research that to learn I have to use the numbers. So I try that (775) and now it tells me it is a read-only file system.
sigh
It might not seem like it, but I'm trying. I really am.
Can someone tell me how to get past step one of this process? Please? What on earth am I doing wrong?
I recently had to do some wizardry on my phone to get openvpn to co-operate, and I suspect that would work here but I don't understand the commands, and fear I'd end up screwing something up.
This was the command:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
I'm guessing I need to unmount the system so I can work on it and copy the file into that directory? Is that the case? Would the command line be the same, or different?
Anyone else get this to work now that the driver has been posted publicly?
Thanks!!!!
To help those who come after me:
Grab ES File Explorer. It includes a Root Explorer that lets you mount the file system as writable. The "copy to" command claimed to work but did not copy the file. Copy the driver, then manually navigate to /system/lib/modules and paste. Voila.
-insert module ("insmod /system/lib/modules/*yourdriver*.ko")
Click to expand...
Click to collapse
this appeared to work
-get an IP address (manually, or "/system/bin/dhcpd eth0")
Click to expand...
Click to collapse
this took me a long time to figure out. as far as I can tell, the only "directions" noobs like me have to follow contain typos. the command should read dhcpcd eth0
HOWEVER, what I get instead is eth0: interface not found or invalid
a little help here? Does the mcs7830.ko driver work with the Asix AX88772 chipset?
Stupid question--should I be expecting the touchpad to power the USB ethernet adapter via the OTG cable, or do I require a "Y" cable to supply power? Is that why I'm getting:
eth0: interface not found or invalid
Click to expand...
Click to collapse
all4adriver said:
Stupid question--should I be expecting the touchpad to power the USB ethernet adapter via the OTG cable, or do I require a "Y" cable to supply power? Is that why I'm getting:
Click to expand...
Click to collapse
I would assume so. Every HP Touchpad tutorial that I've see that mentions an OTG cable also mentions it needing to be powered.
Hi all,
I have been going on xdadevelopers a lot and have received so much helpful information. Now, I decided to give in my contribution to the forum. This is my first tutorial so there might be some mistakes...please be easy on me.
The reason I write this tutorial is because I have not found a good one yet on the internet. Although this thread "Just rooted my remix mini" provided some information, but I feel like a more detailed tutorial would be appropriate. So here we go!
Success screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Credits: all credits goes to these two links and authors:
http://forum.xda-developers.com/remix/remix-mini/rooted-remix-mini-t3311736
http://23pin.logdown.com/posts/435610-root-remix-mini
Requirements:
- Difficult level: Medium
- Tools:
+ Small screw driver
+ Scissors
+ A USB flash drive.
+ Thin metal wire.
+ Serial Converter (I bought on Amazon.com)
- Software:
+ Appropriate driver for the serial converter. Mine is CP2102 driver. Download here. If your serial converter use PL2303 then download this driver. You can google for your specific driver as well.
+ CoolTerm. Download here
+ SuperSU. Download here
- A lot of patience.
Steps:
1. As you can see, I stripped the wire and cut it in small pieces. As long as it is metal wire, that's okay.
2. Open up the Remix Mini with a screw driver.
2a. Flip it up side down, and rip the rubber ring out. It's okay, it will still adhere to the case afterward. Once you ripped it out, you will see two screws holding the remix mini. Proceed unscrew them and gently take the case apart.
2b. Gently take the case apart:
3. Connecting the serial converter to the board.
3a. Plug the 3 metal wires into RX, TX, and GND cable endings of the serial converter.
3b. Connect the other ends of 3 mental wires into RX, TX, and GND of the board.
3c. Make sure connection as such: RX to TX, TX to RX, and GND to GND. This part took me a lot of patience because the wires kept falling off. So please try to keep them in place.
4. Install appropriate serial converter driver.
5. Plug the serial converter into PC.
6. Extract and open CoolTerm.
6a. Click Options -> Serial Port -> Hit "Re-Scan Serial Ports" so it detects the appropriate port for serial converter. Mine is COM3.
- To find out, go to Device Manager -> Ports
6b. Select the right port. Then change the setting as in the picture:
Baudrate: 115200
Data Bits: 8
Parity: None
Stop Bits: 1
Click to expand...
Click to collapse
6c. Go to tab Terminal -> Select Line Mode.
6d. Hit OK.
7. Power Remix mini up (make sure this happens or you will get serial 103 or 104 error code)
8. Hit Connect button in CoolTerm.
8a. If you have done everything correctly until here, texts will appear in CoolTerm as your Remix Mini booting up.
8b. The texts will keep flowing up. Wait until you only see CPU readings. Then proceed to next step.
9. Download the UPDATE-SuperSU-v2.46.zip file. (Please double check the zip's file name. In my case, I am using SuperSU version 2.46)
9a. Copy UPDATE-SuperSU-v2.46.zip file onto flash drive.
9b. Extract the downloaded "UPDATE-SuperSU-v2.46.zip", from the extracted, go to META-INF/com/google/android/update-binary, copy "update-binary" file onto flash drive.
9c. Make sure you have 2 files, UPDATE-SuperSU-v2.46.zip AND update-binary, on the flash drive.
9d. Plug the flash drive to Remix Mini.
10. Commands: (copy each line and paste into CoolTerm)
Code:
/dev/tty.usbserial 115200
mount -o rw,remount /
mount -o rw,remount /system
mkdir /tmp
cd /system/bin
ln -s busybox-smp unzip
cd /data/local/tmp
cp /mnt/usbhost/Storage01/UPDATE-SuperSU-v2.46.zip /data/local/tmp [COLOR="Red"]<- Double check zip's file name and try Storage02 if Storage01 does not work because it depends on which usb port you plug the flash drive in. [/COLOR]
cp /mnt/usbhost/Storage01/update-binary /data/local/tmp
cd /data/local/tmp
sh update-binary 0 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip
reboot
11. Success. :victory::good:
11a. Wait for Remix Mini booting up, optimizing app..and DONE! CONGRATS! You have now voided your Remix Mini's warranty and cannot receive OTA system update anymore.
I have not figured out how to update manually but please hit me up if anyone knows how.
11b. Download Root checker to verify.
GOOD LUCK!!!!!! :good:
I'm gonna wait for an easier way..
This has got to be a joke.
Bro, have you tried kingroot, I'm not crazy about it but it works 99℅of the time
Sent from my LG-D415 using Tapatalk
No it is not a joke, no it will not get easier. Jide made it clear they will not support rooting. The amount of support available is minimal so this is the way. Difficult not if you have done stuff like this before ( FTA satellite. Etc.) kingoroot and all other software has been proven NOT to work. Hardware hacking is the only way so far.
Note: first boot takes longer than factory. Be patient. Jide will know it has been hacked so no support for updates but the opportunity to customize was worth it for me.
robot_head said:
Bro, have you tried kingroot, I'm not crazy about it but it works 99℅of the time
Sent from my LG-D415 using Tapatalk
Click to expand...
Click to collapse
I tried everything..even Baidu Root...nothing works...I am happy that I can do so many things with the Remix Mini now...rooting it was a genius decision lol
Major kudos, this is a true root method for all the hardware hackers out there. You've never truly "hacked" until you've tapped into a UART console. Very exciting!
So when I try this the remix mini just sits at the splash screen and coolterm just keeps saysing
Code:
/dev/block/mmcblk0p12fs_mgr: exec: pid 1667 exited with return code 1: Unknown error 256fs_mgr: begin to format ext4 buffer : /dev/block/mmcblk0p12fs_mgr: finish format to ext4:
while counting up on the pid number. Any idea why that might be?
bullet25 said:
So when I try this the remix mini just sits at the splash screen and coolterm just keeps saysing
Code:
/dev/block/mmcblk0p12fs_mgr: exec: pid 1667 exited with return code 1: Unknown error 256fs_mgr: begin to format ext4 buffer : /dev/block/mmcblk0p12fs_mgr: finish format to ext4:
while counting up on the pid number. Any idea why that might be?
Click to expand...
Click to collapse
I have not seen that before. May I ask at which step that this occurred? This looked like the device was formatting ext4 itself...it's weird.. can you double check and try everything again carefully?
unloseking2500 said:
I have not seen that before. May I ask at which step that this occurred? This looked like the device was formatting ext4 itself...it's weird.. can you double check and try everything again carefully?
Click to expand...
Click to collapse
I happens at step 8. I think the mini might actually be dead because even closed up it doesn't boot.
Sounds like a software issue. Someone else had a recovery partitionfrom Jide search maybe they could upload it.
bullet25 said:
I happens at step 8. I think the mini might actually be dead because even closed up it doesn't boot.
Click to expand...
Click to collapse
Interesting...yeah, try oncouch1's method..try to recover from a partition..see if it helps?!
oncouch1 said:
No it is not a joke, no it will not get easier. Jide made it clear they will not support rooting. The amount of support available is minimal so this is the way. Difficult not if you have done stuff like this before ( FTA satellite. Etc.) kingoroot and all other software has been proven NOT to work. Hardware hacking is the only way so far..
Click to expand...
Click to collapse
I also believe so. Grats on your success tho.
I have a question:-
I have a Tronsmart Vega S95 Telos with Remix OS firmware (Amlogic S905/Mali-450mp5/2 Gb Samsung DDR3/16 Gb Samsung KLMAG2WEMB-B031 eMMC/Realtek RTL8211F Ethernet/Ampak AP6335 Wifi+BT 4.0/Genesis GL850G USB 2.0 hub/JMicron JM20329 USB 2.0 to SATA bridge).
I opened up the TV box and saw the pin holes for PL2303 interface. I tried connect my PL2303 cable with its driver on Mac OS. The connection was succesful, I saw the response in my terminal in the form of message feed. But, I can't go any further. I'm still new to PL2303 use and I don't know how to go from the message feed to issue some commands. Then I see your thread and I think now I got some hope.
My question (again) is:- Do you think I can use your method to root my Tronsmart S95 Telos (with Remix OS flashed and working)?
Many thanks in advance.
PS. Here is the link to a photo of the S95 Telos board showing the PL2303 interface. The photo is not mine. I linked it from a guy tutoring the teardown, but my board looks exactly the same.
(I'm a new XDA user so I can't attach a photo from outside link, sorry for inconvenience)
www,cnx-software.com/wp-content/uploads/2015/12/Tronsmart_Vega_S95_Telos_Board_Large,jpg
Yoswin said:
I also believe so. Grats on your success tho.
I have a question:-
I have a Tronsmart Vega S95 Telos with Remix OS firmware (Amlogic S905/Mali-450mp5/2 Gb Samsung DDR3/16 Gb Samsung KLMAG2WEMB-B031 eMMC/Realtek RTL8211F Ethernet/Ampak AP6335 Wifi+BT 4.0/Genesis GL850G USB 2.0 hub/JMicron JM20329 USB 2.0 to SATA bridge).
I opened up the TV box and saw the pin holes for PL2303 interface. I tried connect my PL2303 cable with its driver on Mac OS. The connection was succesful, I saw the response in my terminal in the form of message feed. But, I can't go any further. I'm still new to PL2303 use and I don't know how to go from the message feed to issue some commands. Then I see your thread and I think now I got some hope.
My question (again) is:- Do you think I can use your method to root my Tronsmart S95 Telos (with Remix OS flashed and working)?
Many thanks in advance.
PS. Here is the link to a photo of the S95 Telos board showing the PL2303 interface. The photo is not mine. I linked it from a guy tutoring the teardown, but my board looks exactly the same.
(I'm a new XDA user so I can't attach a photo from outside link, sorry for inconvenience)
www,cnx-software.com/wp-content/uploads/2015/12/Tronsmart_Vega_S95_Telos_Board_Large,jpg
Click to expand...
Click to collapse
Hi honestly I had never heard of your box. I am not sure if you can use the same software etc. If you could communicate with the box you should be able to hack it. That being said depending on cost you may want to leave it to someone with experience! Remix was 50 bucks so no big risk for me.
...
oncouch1 said:
Hi honestly I had never heard of your box. I am not sure if you can use the same software etc. If you could communicate with the box you should be able to hack it. That being said depending on cost you may want to leave it to someone with experience! Remix was 50 bucks so no big risk for me.
Click to expand...
Click to collapse
Thanks for reply. I don't think the method can hard brick my device any way. The box itself can be flashed via a PC program made by CPU manufacturer (Amlogic here) and I have both stock firmware and Remix OS firmware images. So I think it's gonna worth a try. Thanks any way for your comment.
Keep us posted, may need one of those!?
Okay got my remix replaced. New remix updated to latest update then did root. It started boot looping. Had to run these commands in coolterm turing a boot loop.
Code:
mount -o rw,remount /system
dd of=/dev/block/by-name/system if=/data/local/tmp/system_image
Don't know if that was the latest update to cause that or what but its all working now. Also was able to easily install the google play services again and get playstore.
Of course I once again broke the power button because that wire is hanging on by a thread.
Apologies for the noob question but what does a root on the Remix Mini allow someone to do with regards to OS options and what are the other advantages?
vinicioh23 said:
I'm gonna wait for an easier way..
Click to expand...
Click to collapse
Please see this: https://secure.avaaz.org/en/petitio...tters_Users_need_root_access_to_remix_mini_1/
Just wanted to give a thanks it worked perfect for me...Just want to add that if you happen to use a built in serial port on an older pc or laptop don't forget to put a ttl converter on your port, or your console screen will be garbage printing out
I found something interesting. When i used the OTG checker, i noticed that 3 system files are disabled(they don't have full permissions).
Here's what you have to do(if the FIX button doesn't work)
1.Use a root explorer (Xplore is needed)
2.Find the files with the X from the screenshot
3. Change the permissions and check all the boxes.
4.Reboot and done!
Someone test this and comment if it does or if it doesn't work.
I didn't tried ( i didn't root yet) but i hope it will work
(Tried on my s4 mini and it worked)
Johnny TDN said:
I found something interesting. When i used the OTG checker, i noticed that 3 system files are disabled(they don't have full permissions).
Here's what you have to do(if the FIX button doesn't work)
1.Use a root explorer (Xplore is needed)
2.Find the files with the X from the screenshot
3. Change the permissions and check all the boxes.
4.Reboot and done!
Someone test this and comment if it does or if it doesn't work.
I didn't tried ( i didn't root yet) but i hope it will work
(Tried on my s4 mini and it worked)
Click to expand...
Click to collapse
Hey, just tried. I've fixed permission for android.hardware.usb.host.xml file and now the otg checker give me only green check. Rebooted the phone but when i plug in my usb pen anything happen
Zeph1990 said:
Hey, just tried. I've fixed permission for android.hardware.usb.host.xml file and now the otg checker give me only green check. Rebooted the phone but when i plug in my usb pen anything happen
Click to expand...
Click to collapse
You must do on the all files. Now only android.hardware.usb.host.xml
Zeph1990 said:
Hey, just tried. I've fixed permission for android.hardware.usb.host.xml file and now the otg checker give me only green check. Rebooted the phone but when i plug in my usb pen anything happen
Click to expand...
Click to collapse
Do it for all of the files. Not only on android.hardware.usb.host.xml
doesn't work..
you must make changes to kernel also for otg to work
snapdesign said:
doesn't work..
you must make changes to kernel also for otg to work
Click to expand...
Click to collapse
Did you checked all the boxes on the permissions?
Johnny TDN said:
Did you checked all the boxes on the permissions?
Click to expand...
Click to collapse
what do you see in the photo? also otg needs support from kernel... it doesn't work without it
i make a custom kernel with host permissions but doesn't work anyway...
Possible problem its software and managed vold's...
In the RAMDISK it's pointed correct for USB OTG
/devices/hisi-usb-otg/usb1/* auto auto defaults voldmanaged=usbotg:auto
BadWolfYe said:
i make a custom kernel with host permissions but doesn't work anyway...
Possible problem its software and managed vold's...
In the RAMDISK it's pointed correct for USB OTG
/devices/hisi-usb-otg/usb1/* auto auto defaults voldmanaged=usbotg:auto
Click to expand...
Click to collapse
can you make a kernel with multirom support?
edit: you are the same bad wolf from htcmania?
snapdesign said:
can you make a kernel with multirom support?
edit: you are the same bad wolf from htcmania?
Click to expand...
Click to collapse
Yes the same
And in this moment MultiROM its innecesary (no support for other roms only EMUI...)
BadWolfYe said:
Yes the same
And in this moment MultiROM its innecesary (no support for other roms only EMUI...)
Click to expand...
Click to collapse
well, someone is working on a cm build... when that will boot we should have a kernel with multirom...
i tried on more way too for OTG already,,, added lines too vold.fstab etc etc but it wont support,,,
UPDATE
My phone is rooted and i am testing it. Hope it works on mine. If it doesn't, the post should be removed
Hiya Fellas,
I was messing around with my development build last night and I was able to turn on USB host mode and successfully plug in and use a usb flash drive. Now keep in mind that this was on CM 13 but, this might also work on a rooted stock.
Using adb or terminal app.
1. Look for a path in /sys/devices that ends with hisi_usb (e.g /sys/devices/f4000000.hisi_usb)
2. Now inside that folder there should be a file called plugusb.
3. use this command
echo hoston > /sys/devices/f4000000.hisi_usb/plugusb
Replace "f4000000" with the real value.
Now plug in your device and see if it is recognized!
EDIT: You may need to be root to do this!
ADB: "adb root"
TERMINAL APP: "su"
Meticulus said:
Hiya Fellas,
I was messing around with my development build last night and I was able to turn on USB host mode and successfully plug in and use a usb flash drive. Now keep in mind that this was on CM 13 but, this might also work on a rooted stock.
Using adb or terminal app.
1. Look for a path in /sys/devices that ends with hisi_usb (e.g /sys/devices/f4000000.hisi_usb)
2. Now inside that folder there should be a file called plugusb.
3. use this command
echo hoston > /sys/devices/f4000000.hisi_usb/plugusb
Replace "f4000000" with the real value.
Now plug in your device and see if it is recognized!
EDIT: You may need to be root to do this!
ADB: "adb root"
TERMINAL APP: "su"
Click to expand...
Click to collapse
The value changed... I forgot my USB adapter in the car... will update the in a few minutes... if it works you resolved a big thing in what..2 days from having the device? great dev... thanks!
EDIT: unfortunately it doesn't work on my device... also after reboot the value changed to OFF again... great find although
Meticulus said:
Hiya Fellas,
I was messing around with my development build last night and I was able to turn on USB host mode and successfully plug in and use a usb flash drive. Now keep in mind that this was on CM 13 but, this might also work on a rooted stock.
Using adb or terminal app.
1. Look for a path in /sys/devices that ends with hisi_usb (e.g /sys/devices/f4000000.hisi_usb)
2. Now inside that folder there should be a file called plugusb.
3. use this command
echo hoston > /sys/devices/f4000000.hisi_usb/plugusb
Replace "f4000000" with the real value.
Now plug in your device and see if it is recognized!
EDIT: You may need to be root to do this!
ADB: "adb root"
TERMINAL APP: "su"
Click to expand...
Click to collapse
WORK !!! THANK YOU !
- install from Playstore Universal Init.d
- Open Universal Init.d and activate support
- Create a generic text file Ex. usbotg in /etc/init.d folder with the following content
#!/system/bin/sh
echo hoston > /sys/devices/f4000000.hisi_usb/plugusb
!!!! Replace "f4000000" with the value found in your smartphone (my: ff100000) !!!!
- give to the file 755 permission
- reboot
I used Root Explorer to do all.
Enjoy !
Meticulus said:
Hiya Fellas,
I was messing around with my development build last night and I was able to turn on USB host mode and successfully plug in and use a usb flash drive. Now keep in mind that this was on CM 13 but, this might also work on a rooted stock.
Using adb or terminal app.
1. Look for a path in /sys/devices that ends with hisi_usb (e.g /sys/devices/f4000000.hisi_usb)
2. Now inside that folder there should be a file called plugusb.
3. use this command
echo hoston > /sys/devices/f4000000.hisi_usb/plugusb
Replace "f4000000" with the real value.
Now plug in your device and see if it is recognized!
EDIT: You may need to be root to do this!
ADB: "adb root"
TERMINAL APP: "su"
Click to expand...
Click to collapse
ThankS!!!! It worked but, there are some troubles:
after using that command doesn't work the usb cable phone - PC (need reboot or to write "hostoff" instead of "hoston");
after rebbot need again to rewrite the command.
With universal Init.d it can be a little easy cause you can make 2 file ( 1 for hoston and 1 for hostoff) and just run them from app, so with 2 touch you can enable and disable otg instead of wirting everytime the command using terminal.
Edit: universal init.d doesn't work properly so I used a script runner and just run from it (with root permissions) 1 of 2 script (enable, disable).
Edit2: Look these images to see what I've done(don't need to reboot phone after):
Image 1: http://prnt.sc/ckk9hs
Image 2: http://prnt.sc/ckka26 (used this app: https://play.google.com/store/apps/details?id=com.snclabs.scriptrunner&hl=it)
Don't know if anyone else has this problem but for some weird reason when I try plug in my 8gb or 128gb it won't work but if plug in the 32gb memory stick bam it works fine any one know the reason y?
Sent from my HUAWEI VNS-L31 using XDA-Developers mobile app
Noel.89 said:
Don't know if anyone else has this problem but for some weird reason when I try plug in my 8gb or 128gb it won't work but if plug in the 32gb memory stick bam it works fine any one know the reason y?
Sent from my HUAWEI VNS-L31 using XDA-Developers mobile app
Click to expand...
Click to collapse
I've tried with my 16gb usb pendrive, 500gb external HD, 2TB external HD and it worked fine with all of them...
SevenSlevin said:
I've tried with my 16gb usb pendrive, 500gb external HD, 2TB external HD and it worked fine with all of them...
Click to expand...
Click to collapse
Really how did you get yours to work maybe I'm doing something wrong putting the file in wrong place
Sent from my HUAWEI VNS-L31 using XDA-Developers mobile app
We're back with an OTA update for 1GB and 2GB Remix Minis. Also, please know that if you are experiencing any type of streaming video issues, we've identified the problem, worked on a fix and are currently testing it now. If it passes, it'll be on the next update.
___________________________________________________
Remix OS on Remix Mini (1GB & 2GB) update version: 2.0.626
Release date: November 4, 2016
Release notes:
Updated Remix OS TV mode’s UI to the latest version.
IMPORTANT NOTE: For users who have NOT updated since version 2.0.307, all updates between 2.0.307 and 2.0.626 have been included. This is a critical update for the functions and usability of your Remix Mini. We strongly suggest you update to this version. This also means that this update may take a few minutes longer than regular updates.
__________________________________________________
Please continue to give us feedback here: http://support.jide.com/hc/en-us/requests/new
Thanks!
Do you have it as non ROM but as a firmware file to overwrite all partitions and have a fresh version of 2.0.626?
RemixOS_Jason said:
We're back with an OTA update for 1GB and 2GB Remix Minis. Also, please know that if you are experiencing any type of streaming video issues, we've identified the problem, worked on a fix and are currently testing it now. If it passes, it'll be on the next update.
___________________________________________________
Remix OS on Remix Mini (1GB & 2GB) update version: 2.0.626
Release date: November 4, 2016
Release notes:
Updated Remix OS TV mode’s UI to the latest version.
IMPORTANT NOTE: For users who have NOT updated since version 2.0.307, all updates between 2.0.307 and 2.0.626 have been included. This is a critical update for the functions and usability of your Remix Mini. We strongly suggest you update to this version. This also means that this update may take a few minutes longer than regular updates.
__________________________________________________
Please continue to give us feedback here: http://support.jide.com/hc/en-us/requests/new
Thanks!
Click to expand...
Click to collapse
How to exit TV Mode without restarting?
RemixOS_Jason said:
We're back with an OTA update for 1GB and 2GB Remix Minis. Also, please know that if you are experiencing any type of streaming video issues, we've identified the problem, worked on a fix and are currently testing it now. If it passes, it'll be on the next update.
___________________________________________________
Remix OS on Remix Mini (1GB & 2GB) update version: 2.0.626
Release date: November 4, 2016
Release notes:
Updated Remix OS TV mode’s UI to the latest version.
_______________________________________________
Click to expand...
Click to collapse
Can't find a way to close Tv Mode and back to normal desktop. How?
dinh_duy said:
Can't find a way to close Tv Mode and back to normal desktop. How?
Click to expand...
Click to collapse
press circle next to start button
kesmtk said:
press circle next to start button
Click to expand...
Click to collapse
Thanks. Gonna try it later.
Do you mean, you'd rather have a fresh copy of Remix OS on version 2.0.626 with none of your previous saved data and apps? Did you have your previous version rooted? I believe if you were just looking for a fresh start with the latest version of Remix OS, you can reboot your Mini, and then press F2 when prompted, and then do a factory reset. You may need to go through some updates, but I'm told you should restart in 2.0.626.
I hope this helps.
kesmtk said:
Do you have it as non ROM but as a firmware file to overwrite all partitions and have a fresh version of 2.0.626?
Click to expand...
Click to collapse
RM1C was rooted but unrooted cannot apply OTA
My device is RM1C. I Wanted to root on 2.0.512 version. but it autoupdated to some unstable version 2.0.622 with crashes after exiting fullscreen app. (I noticed there appeared an error messages on some missing file when connected via uart port. this is the message:
init: unknown magic init: unknown magic init: boost open /sys/devices/soc.0/cpu_budget_cool.16/roomage fail, No such file or directory!
init: boost open /sys/devices/soc.0/cpu_budget_cool.16/roomage fail, No such file or directory!
) but 2.0.512 was most stable version for me no errors on the uart also.
I rooted 2.0.622 version and allowed an app that I bought "gamecontroller2touch pro" to grant superuser permissions. It works as mapping xbox360 controller buttons to touch games like a charm, where a jide keymap does not support xbox360 it only works for keyboard input.
Then I saw a version for RM1C 2.0.627 was dowloaded in autoupdater. I unrooted and made system partition as it was. but it detects that the system was accessed as R/W and OTA update aborts with error 7.
I just wonder if the new version will not have that error that makes crash the desktop after exiting from fullscreen(as I found workaround to reutn to desktop after crash is to click xbox360 "back " button ). I have the incremental OTA for RM1C version 2.0.627 on usb, but cant install it . need reflash system.img.
RemixOS_Jason said:
Do you mean, you'd rather have a fresh copy of Remix OS on version 2.0.626 with none of your previous saved data and apps? Did you have your previous version rooted? I believe if you were just looking for a fresh start with the latest version of Remix OS, you can reboot your Mini, and then press F2 when prompted, and then do a factory reset. You may need to go through some updates, but I'm told you should restart in 2.0.626.
I hope this helps.
Click to expand...
Click to collapse
Got it. I remember your issue. I'm trying to work out 2 solutions for you:
1. Downgrade as you asked for. I'm waiting for the Chinese ROM team to give me the package and tutorial to be translated.
2. Flashing the Global (English) ROM into your Mini.
Do you prefer either/or? I'll respond still in private message to you about this.
Thanks!
kesmtk said:
My device is RM1C. I Wanted to root on 2.0.512 version. but it autoupdated to some unstable version 2.0.622 with crashes after exiting fullscreen app. (I noticed there appeared an error messages on some missing file when connected via uart port. this is the message:
init: unknown magic init: unknown magic init: boost open /sys/devices/soc.0/cpu_budget_cool.16/roomage fail, No such file or directory!
init: boost open /sys/devices/soc.0/cpu_budget_cool.16/roomage fail, No such file or directory!
) but 2.0.512 was most stable version for me no errors on the uart also.
I rooted 2.0.622 version and allowed an app that I bought "gamecontroller2touch pro" to grant superuser permissions. It works as mapping xbox360 controller buttons to touch games like a charm, where a jide keymap does not support xbox360 it only works for keyboard input.
Then I saw a version for RM1C 2.0.627 was dowloaded in autoupdater. I unrooted and made system partition as it was. but it detects that the system was accessed as R/W and OTA update aborts with error 7.
I just wonder if the new version will not have that error that makes crash the desktop after exiting from fullscreen(as I found workaround to reutn to desktop after crash is to click xbox360 "back " button ). I have the incremental OTA for RM1C version 2.0.627 on usb, but cant install it . need reflash system.img.
Click to expand...
Click to collapse
option 2 ; ) flash RM1C 2GB ram with RM1G firmware
..........option 2, I have pm'ed a message for you Thank You for help. :good:
RemixOS_Jason said:
Got it. I remember your issue. I'm trying to work out 2 solutions for you:
1. Downgrade as you asked for. I'm waiting for the Chinese ROM team to give me the package and tutorial to be translated.
2. Flashing the Global (English) ROM into your Mini.
Do you prefer either/or? I'll respond still in private message to you about this.
Thanks!
Click to expand...
Click to collapse
How and how long will this go on?
As a long time fan of Android-x86 I didn't really notice the Jide hardware until "The Merge"...
Now I see the Mini being sold off for half price and I wonder: Will it be obsolete on arrival?
I don't think I'd need Nougat on the device. I'd even think I'd be able to live with Lollipop.
But I can't operate a computer in my home network, that is unsafe to operate.
So I need the assurance that it will receive security updates until the end of its life cycle (3-5 years after purchase).
And I need the ability to control any computer I operate.
So will there be security updates until 2020?
Will you provide them or will you enable the community to provide them?
And will I be able to administer the system, de-activating services which have un-fixed vulnerabilities, blocking IPs, etc?
Generally that requires operating with root permissions on Linux systems, including those with an Android GUI.
$40 for a multi-media capable Linux systems running an attractive GUI is a great offer.
$40 for a potential IoT bot in my home network, which I can only throw away once somebody manages to subvert it, is a very bad investment, especially if it causes external damage.
So what will it be?
And will your future systems be any different?
BTW: Apart from 8 big desktops (Windows, Linux & Remix), 2 silent Atoms (Remix, Windows + Linux), 6 Notebooks (Windows, Remix & Linux), I operate 5 Android tablets and 10 Android phones (Canogenmod based Android, rooted by design).
Some of the PC hardware is 10 years old (3.4GHz Quad-Core Penryns work just fine with Nvidia GTX 1070), some of the Androids are still great after almost 6 years (e.g. Asus Eee Pad Transformer).
All of them run up-to-date operating systems with the latest patches. Typically not thanks to the vendor who produced the hardware but to the open source community which maintains Linux and Cyanogenmod.
If you treat the software on your hardware differently than Android-x86, you'll burn the brand very, very quickly.
usb boot
i have the remix mini rm1g with 626 is there a way to boot ubuntu via usb if i can boot into ubuntu can i install it and reinstall remix os on ubuntus root directory using grub customizer i know i can do that with remix os for pc
joeylikesubuntu said:
i have the remix mini rm1g with 626 is there a way to boot ubuntu via usb if i can boot into ubuntu can i install it and reinstall remix os on ubuntus root directory using grub customizer i know i can do that with remix os for pc
Click to expand...
Click to collapse
I don know, havent tried load linux on remix, I have rasbpberry pi and orange pi where they load everything from sd card.....remix mini loads from nand flash.
Maybe if you go to remix about screen and keep clicking build number to activate developer options.
Then dev options appear near about button in the options screen. Then enable usb debugging. select usb0 for debugging (the upper usb port)
install adb driver http://adbdriver.com/ . plug male - male usb cable PC-usb>remix upper usb port. Enter adb and enter root console. Maybe from root console it is possible to setup remix to load from sd card(where you linux kernel will be) by edidting uboot .
kesmtk said:
I don know, havent tried load linux on remix, I have rasbpberry pi and orange pi where they load everything from sd card.....remix mini loads from nand flash.
Maybe if you go to remix about screen and keep clicking build number to activate developer options.
Then dev options appear near about button in the options screen. Then enable usb debugging. select usb0 for debugging (the upper usb port)
install adb driver http://adbdriver.com/ . plug male - male usb cable PC-usb>remix upper usb port. Enter adb and enter root console. Maybe from root console it is possible to setup remix to load from sd card(where you linux kernel will be) by edidting uboot .
Click to expand...
Click to collapse
I don't think so. This is not a developer device, and not a traditional PC. It is a closed Android device (like Android phones and tablets), so would require custom bootloader/boot/etc. to loader other software. The Mini is made to show of Jide's bread and butter, their Remix OS software. They likely won't support officially installing any other 3rd party OS, since again, they are selling software and the hardware is incidental. Compared to the Raspberry Pi, which is open hardware designed for developing, and made to run various Linux releases and has broad support.
Now that it's EOL for the mini and no new updates are coming for it could we PLEASE have root?
4llerbuntu said:
Now that it's EOL for the mini and no new updates are coming for it could we PLEASE have root?
Click to expand...
Click to collapse
rooting easy, you must have uart to usb adapter. if you unscrew two screws under the rubber cover you will see 3 pins with GND tx and rx. Your usb to uart dongle shold have gnd tx and rx pins. 3,2 volt reading on the tx and gnd with multimeter. solder uart gnd pin to remix mini gnd. then uart tx to remix mini rx, and uart rx pin to remix mini tx. Open hyperterminal in windows. dial with com port setting 112500 none 8. and you have terminall root. from there you can cd to usb drive to install root
kesmtk said:
rooting easy, you must have uart to usb adapter. if you unscrew two screws under the rubber cover you will see 3 pins with GND tx and rx. Your usb to uart dongle shold have gnd tx and rx pins. 3,2 volt reading on the tx and gnd with multimeter. solder uart gnd pin to remix mini gnd. then uart tx to remix mini rx, and uart rx pin to remix mini tx. Open hyperterminal in windows. dial with com port setting 112500 none 8. and you have terminall root. from there you can cd to usb drive to install root
Click to expand...
Click to collapse
Looool:crying:
This is "easy"??
Seriously?
I always knew about this method. So there must be a reason I haven't tried it.
Anyways, id prefer rooting similar to what we have on numerous other Android devices, smartphones and TV boxes.
They usually don't require opening the device and a UART cable ......
re
4llerbuntu said:
Looool:crying:
This is "easy"??
Seriously?
I always knew about this method. So there must be a reason I haven't tried it.
Anyways, id prefer rooting similar to what we have on numerous other Android devices, smartphones and TV boxes.
They usually don't require opening the device and a UART cable ......
Click to expand...
Click to collapse
Well I had an old usb nokia adpter I tierd it appart and discoverd it has an uart interface with 3.2 volt communications sigal logic which is what is needed for remix mini. I soldered communications and boom I am as root user for remix mini . I copied supersu.zip and a instalation file from zip file inthe same foler. ran instalation file via sh command and root installed.
Maybe its possible to access root terminal from usb debugging.. I didnt try that.
You can install adb driver from adb.com. then click remix mini settings about. keep clicking version to get developer. enable developer. click settings menu again. click developer. click usb debuugging on. click usb0. then connect upper usb remix mini to pc usb. open pc cmd line and enter adb console. maybe from there you could do the stuff as root . I could
How do you install this? I'm currently on 2.0.203 and it says it fails trying to check for a new version. My internet is working fine though.
jbradshw said:
How do you install this? I'm currently on 2.0.203 and it says it fails trying to check for a new version. My internet is working fine though.
Click to expand...
Click to collapse
You must donwload phoenixsuit
https://www.dropbox.com/s/x7mnzui95c4459z/PhoenixSuit_EN_V1.0.8.msi?dl=0
adbdriver from
adbdriver.com
remix image
https://osdn.net/projects/remixos/downloads/66607/factory_image_rm1g_B2016110301-secure.img/
Warnining you will lose your all remix mini data.! games apps etc.
go to remix mini settings > abount. keep clicking on version number . the developer options will enable.
again go to settings>developer options > enable usb debuging , select usb0.
UNplug remix mini power cable.
Get a cliper and make a tool to push a "reset" button that is located in the hole in the back of remix mini. Try to for yourself by sticking cliper in the hole and feel the putton presses.
use usb MALE-MALE cable. connect remix mini upper usb port to laptop/PC usb.
I use windows 7 64bit
in laptop/PC:
1. Install the ADB tool
2. INstall PhoenixSuit. You will be guided through their installation instructions.
!let it autoupdate and restart it after updated
3. After the installation finishes, you can run PhoenixSuit by double-clicking the PhoenixSuit icon on the desktop.
4. Click ‘Firmware’ to enter the firmware flashing interface.
5. Click ‘Image’ to select the Remix OS img file.
!! click download one or multi partition to flash:
https://p5.zdusercontent.com/attach...Df0FXhMJxbcJLYkUku2_vQ.bLJYy1dgTWPhpfUCaIS3WA
6. Connect your Remix Mini to the PC via a USB-USB cable. NOTE: The cable must be plugged into the top USB port of remix mini.
7. Insert a straightened paperclip into the hole ar the back of your Remix Mini to press reset button.
8. while keeping clip inserted (reset button pushed) insert power cable to remix mini. Flashing image will start automatically, you can release the clicp holding reset button.
9. wait to complete, reboot mini.
Wow... what happened to the auto-update feature?