yashsingh1/xdaforums huggingface dataset:
[Remix Mini General] Nidor:
[MENTION=2448653]johnmurrayvi[/MENTION] [MENTION=7269569]pcGoose[/MENTION]

Thanks for the info. Finally I can get started on actually using my mini.
[Remix Mini General] Guerol:
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)
[Remix Mini General] pcGoose:
https://download.chainfire.eu/696/SuperSU/
[Remix Mini General] Xkhoax:
I'm about to buy an USBUART PL2302 Cable, hoping it works.
[Remix Mini General] Guerol:
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?
[Remix Mini General] Nidor:
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.
[Remix Mini General] afgok:
did you install busybox ?

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
[Remix Mini General] johnmurrayvi:
I don't think it's dependent on the os version.

I ran into similar issues originally as well, but I managed to work around them with some modifications. When I have some time (hopefully either tonight or tomorrow) I'll try to pull the files off and double check exactly what I had done to make it work.

I believe I used a system mode version (not the newer hybrid systemless/system format) of 2.65. I had to do a little tweaking in the update-binary script. One change I recall I needed to make was commenting out a section that checked for "/sbin/unzip" and bailed out if it didn't find it, saying something along the lines of "BAD RECOVERY DETECTED". Since the update-binary is being manually run from the shell while the device is not in recovery (AFAICT in the [stock] recovery, accessing a shell over UART doesn't work but I didn't spend much time on it.), the fact the script bails out is erroneous.

Pretty sure I also had the BIN and COM variables pointing to /data/local/tmp instead of /tmp.

Also, after it installed and rebooted, I seem to remember having to move the SuperSU.apk from /system/app/SuperSU/SuperSU.apk to /system/app/SuperSU.apk and using "chmod 644" on it.

[MENTION=3268147]Guerol[/MENTION], I also had issues with the USB randomly not mounting. It actually didn't even see my drive as being attached if I used the upper port. So, make sure you plug it into the bottom port on the Mini.

Since the USB gets recognized as a block device, and the internal storage isn't, the USB will *likely* be at /dev/sda. I'll need to double check the device naming because I can't say for sure this will work verbatim, you should be able to use

mount /dev/sda1 /mnt/usbhost/Storage01

to manually mount the drive.

I'll get a more clear/detailed list of instructions, and pull the files back off my Mini, once I get a chance to.

FWIW, I did not install busybox beforehand. There's already a system version in /system/bin/busybox-smp that can be used for the process.

Once I had SuperSU installed, I just downloaded BusyBox on the Play Store and used that (reasoning: the pro version was already in my account and it lets you configure symlinks/applets, which I prefer to do instead of a whole-sale install possibly overwriting links in the system image by default).

One suggestion I have for anyone doing this though, once you have access to the root shell over UART, make a backup of at least the system partition. You can use "dd" to save an image to the internal storage card and then pull it off with a USB or something. It wouldn't hurt to back up other partitions either.
[Remix Mini General] bullet25:
I keep getting a error in CoolTerm when trying this. Error: 104: Framing Error. Anybody know how to fix this?
[Remix Mini General] Guerol:
Disconnect USB-UART Adapter from your PC and reconnect it again. This should help.
[Remix Mini General] johnmurrayvi:
In CoolTerm, click Connections -> Options. Select the "Receive" category on the left hand side list. Under "Receive Options" at the top, check the box for "Ignore receive signal errors".
[Remix Mini General] johnmurrayvi:
Here are the files I just pulled out of my /data/local/tmp.

I had to add the ".txt" extension for the update-binary to upload so just remove it should you end up using it.

Currently, the SuperSU apk is in /system/app/SuperSU/SuperSU.apk, which I mentioned I needed to fix before. I believe I had to make the fix, then afterwards, I let SuperSU run it's "update the SU binary"/reinstall SuperSU on it's own.

It's basically just a matter of boot strapping SuperSu so it'll reinstall/setup everything the way it wants after you allow the initial root ability.
[Remix Mini General] Guerol:
Which other partitions would you propose?

This mount command doesn't work. This is probably because there is no sda1 in /dev

I tried both usb-ports. I tried to use a micro-sd card as well. I am not getting any storage device mounted. :crying:

I am now unboxing a never used remix mini (packaging still sealed) and will try to root with your modified v2.65 files.
[Remix Mini General] johnmurrayvi:
Try putting them in dropbox or something and download the files onto the internal storage instead. Then, just adjust the paths in the commands you run to where ever you downloaded the files to.

---------- Post added at 02:41 PM ---------- Previous post was at 02:30 PM ----------

There's a number of partitions actually. I haven't gotten a chance to poke around at them yet to see what they actually contain, but here's a list:

root@rm1g:/ # ls /dev/block/by-name
Reserve0
Reserve1
Reserve2
UDISK
alog
boot
bootloader
cache
env
misc
private
recovery
system
verity_block
[Remix Mini General] Guerol:
GUI is not booting up. There is only this root terminal session. :(

Without GUI I am not sure, how to install and configure dropbox. :rolleyes:

Any other ideas, how to transfer files to remix mini without GUI? :confused:
[Remix Mini General] bullet25:
So that worked but now all I get in CoolTerm is a ton of garbled text. Any idea now or is it a ****ty UART cable?
[Remix Mini General] johnmurrayvi:
It may be that system partition was mounted (maybe mounted as RO for that specific error) when you tried to dd. You would need to put a staticly-linked busybox somewhere that isn't on the system partition and run dd from it. Otherwise, it'll try to run dd from the system partition, which wouldn't work if the system partition was unmounted.

Glad you got the external storage working at least. I did have a fair number of warnings running the update-binary script as well, primarily because the libraries in system/lib are 32 bit even though the mini is running an ARM64. Also, the update-binary unsuccessfully tries to change the SELinux contexts with chcon and chattr; I had those as well.

After you ran it and rebooted, did you see SuperSU installed? Was it in /system/app?

Basically you just want to get the essential parts in place to be able to run SuperSU. From there, you can use SuperSU to reinstall/fully install everything properly.

Check the baud rate? Maybe check that TX -> RX and RX -> TX too.
[Remix Mini General] Xkhoax:
waiting for a video
[Remix Mini General] oncouch1:
Guerol - quick question, did you hit the button by the microsd? On some Chinese devices it would force a factory reset.
[Remix Mini General] oncouch1:
[IMG="partition info"]https://onedrive.live.com/redir?resid=F0139E3CA0E42920!1247&authkey=!ACMM2gJqUEqfNrM&v=3&ithint=photo%2cjpg[/IMG]

I found all the partition info, don't know what to do with it unfortunately. Time to read more........

I am able to see the logs for the system update I have run in the stock recovery but cannot access them in the gui due to lack of root I imagine.
[Remix Mini General] Guerol:
Odyssey is over!

I am closing the case successfully!! :) Both my Remix Minis are rooted and operational !! :D My thanks go to johnmurrayvi for his help and to pcGoose for first how-to root. :good:

No, it wasn't necessary to do something with busybox. System partition needed just to be set to RW. That was all. I could restore /system and Remix Mini was able to start his GUI again.

mount -o rw,remount /system
dd of=/dev/block/by-name/system if=/data/local/tmp/system_image

Yes, I hit the reset button, but the (undocumented) reset button on Remix Mini doesn’t work at all. :(

I have also tried to reset the Remix Mini via Recovery, but it just deletes the data partition. It doesn’t restore the system partition.

After unbricking my Remix Minis by restoring the system partition, I tried the following solution:

I can confirm this solution works!!! :D :D :D

I compared this solution with the solution described by pcGoose. It is funny. Both solutions are practically the same. (The chinese site doesn’t tell anything about installing busybox at all.) The Chinese guy has only one extra line (as 3rd Line):

mkdir /tmp

This line doesn’t look important, but it is!

I tried the solution without this line (as described by pcGoose) and my 2nd Remix Mini was semi bricked again. This line is important!

Those of you, who has been stuck on this state, doesn’t need restore the system partition as I did.

You can insert this line (as 3rd line) in the solution presented by pcGoose or use the one of this Chinese site. It will not just unbrick your Remix Mini, it will root it as well. (Just tested by myself.) :D

After rooting the Remix Mini, I updated SuperSu and it asked me about updating binary files as well. I let him updating the binary files by normal method. It worked fine.

By trying to root the Remix Mini I learned more about linux/unix for example about creating and restoring image backups from system. So I had a interesting idea and tested it out. Yes, you can actually create a image backup of a already rooted Remix Mini by

dd if=/dev/block/by-name/system of=/data/local/tmp/system_image

and restore it on a unrooted Remix Mini. Voila you rooted it without any hassle!! Very practical if you own more than one Remix Mini. :good:

I have also tested some root APPs as well.

:D VMLite VNC Server: It is the only Remote Control solution, which seems to work with Remix Mini. So you can control the Remix Mini from another place. Since it costs money. If you find another (working!!) Remote Control APP give me a shout.

:D AdAway (not available via playstore): It removes all ads. Yeah!!

:D Quick Boot: It can shut down, reboot and reboot to recovery as well.

:D Total Commander: My favorite File Manager. It works without root as well, but with root you can access all folders.
[Remix Mini General] oncouch1:
Congrats! Care to post an image to save me some typing ? ;) quick question do I need a UART cable or can I make one out of an old USB cable? Or can this be done via adb?
[Remix Mini General] Guerol:
The cable is not so important since only 3 wires are used. Any cable with (at least) 3 wires will do.

More important is where you connect this wires. The internal port of Remix Mini is a serial/UART port. It is not a USB port.

Either you use a older PC with a serial port or you buy a cheap USB to serial/UART converter.
[Remix Mini General] oncouch1:
I used an amazon cable and coolterm. The terminal kept scrolling data (my settings issue?) so I typed via cut and paste. Now I am rooted! The boot took a long time. So I repeated instructions and then it started. When restarting my mini now takes longer and every time it says updating but it works. A shout out to all who made this possible.
[Remix Mini General] sirichais:
If it possible to rewrite how to root remix mini as working version.

Thanks.
[Remix Mini General] oncouch1:
I used XDA and this site to get it done:

http://23pin.logdown.com/posts/435610-root-remix-mini

You do have to translate from chinese but the important stuff is understandable.

Beaware once rooted Jide will know and no longer support you!But for 50 bucks have fun.
[Remix Mini General] blender3d:
just rooted my Remix mini as well

Just to clarify, the chinese guy you found didn't install busybox as there was a binary already present in Remix's system folder.

I tried to do it with the most recent UPDATE-SuperSU.....zip without any success. Instead, what i did was having a look into the update-binary shell file (META-INF/com/google/android/update-binary). Starting from line 59 there is a nice introduction on how to install all the needed files yourself. So in the end it is just alot of cp,chmod,chown and chcon typing. Keep in mind the Remix has an 64bit architecture.

Unfortunately i didn't record the whole process but this should give you an hindisght on how to do it yourself.

Files to be installed from zip:

common/Superuser.apk

common/install-recovery.sh

arm64/su (do different locations and with different contexts [chcon], don't mess this up)

arm64/supolicy

arm64/libsupol.so

target locations come from the update-binary file.

The next step is the real dangerous one! Don't do anything like this if you don't know what you are doing!

mv /system/bin/app_process64 /system/bin/app_process64_original

ln -s /system/xbin[or whereever you installed the su binaries]/daemonsu /system/bin/app_process64

After that you may run

/system/xbin/su --install (which in my case seemed to do absolutely nothing)

Really check that you have applied all the chcon['s] as in the update-binary file. Or else you may run into serious trouble (if /system/xbin/daemonsu doesn't have the context your system should not start anymore).

You can check the chcon['s] with ln -Z. If your file is not in the list, it doesn't have the context.

For a shorter list (e.g. /system/bin) you can also type like " ls -laZ app_* "
[Remix Mini General] kanyazsombor:
What remix os version did you root?

Theoretically could be good any regular usb cable if I cut the unnecessary end?

Thanks
[Remix Mini General] walscobry:
ROOT or BUST

If you do not have ROOT it is not your device it still belongs to the company that made it. If a company does not provide ROOT or a method for it then they ARE doing something they don't want to you know about. It's that simple. ROOT or you are a victim.

That is why I played with one my MINIs for 2 days. No ROOT so back in the box. Did not even bother to open the 2nd. I discouraged everyone from purchasing. Learn something from this. Voiding the warranty is fine.
[Remix Mini General] gohanSS:
Root voids warranty 99% of the times anyway

Inviato dal mio ASUS_Z00A utilizzando Tapatalk
[Remix Mini General] enginmanap:
I have successfully rooted my device using the information here, thanks to everyone. This is the first time I used UART, and I think there are somethings worth mentioning here for newcomers

1) for UART to work, you need to power the remix mini.

2) My device constantly printed cpu state information, This makes typing a little harder, but the input is not mangled, don't worry (if you did not make typing mistake, than cancel using ctrl+c

3) The root install script says it did not found some files. but it also says "done". I don't have any idea why, but it did not cause any issues on my case.

Also, I am guessing after the rooting process, we should avoid OTAs? Or will it just remove the root, but function properly?
[Remix Mini General] Guerol:
There is no need to avoid OTAs since (unfortunately) Remix update process will detect root access and refuse to update. :rolleyes:
[Remix Mini General] zhlvf:
Rooted OS image?

Hi rooting-masters,

does anybody have a rooted image I can flash on my remix mini? I don´t know how to use an uart-cable. Could I flash an OS image in recovery mode?

I searched in youtube "How to root Remix mini?" but there is still no instruction video...

Thanks in advance! :)
[Remix Mini General] oncouch1:
I think you have to root before you can install a .IMG file.

It is not that hard to do via UART just different. Read all the in this thread and between them and the link to the Chinese page you can do it. Remember warranty, support and updates will stop once rooted.
[Remix Mini General] sashusmom:
To all of you that have rooted- what are the advantages to it on the remix mini. There are no other roms to load- You lose your updates- Is it worth it just to have titanium back up? What other stuff can you do with a rooted remix mini? Thanks :0)
[Remix Mini General] killerps:
adaway, task managing, xposed, apps/games from unknown sources with copying data to local storage, using usb drives as storage for apps...etc
[Remix Mini General] theredbaron1834:
The only reason I want root is I want to use my DS3/4s wirelessly. You can sort of get the ds4 working without root, but the keys are all wrong and the touchscreen doesn't work. The mini just is useless without root, imo. Even tried giving it away to family, no takers.
[Remix Mini General] dinjin:
Hey, I'm new to UART but I've tried following all the posts/blog but I'm getting stuck. I am connecting my remix to my computer successfully, but coolterm gets filled with

[ 227.150188] CPU Budget:update CPU 0 cpufreq max to 1104000 min to 480000
[ 227.162220] CPU Budget hotplug: cluster0 min:0 max:4
[ 227.670508] CPU Budget hotplug: cluster0 min:0 max:4
[ 229.670197] CPU Budget:update CPU 0 cpufreq max to 1104000 min to 480000
[ 229.689778] CPU Budget hotplug: cluster0 min:0 max:4
[ 231.690396] CPU Budget hotplug: cluster0 min:0 max:4
[ 231.771600] CPU3: shutdown
[ 231.774621] psci: CPU3 killed.
[ 231.971643] CPU2: shutdown
[ 231.974659] psci: CPU2 killed.
[ 231.981103] CPU2: Booted secondary processor
[ 231.981103] CPU2: update cpu_power 1968128
[ 231.781075] CPU3: Booted secondary processor
[ 231.781075] CPU3: update cpu_power 1968128
[ 234.971520] CPU3: shutdown
[ 234.974493] psci: CPU3 killed.
[ 234.980988] CPU3: Booted secondary processor
[ 234.980988] CPU3: update cpu_power 1968128

and it just repeats onward, cpu1-3. I haven't tried waiting it out since my connection is sort of touchy and I'm inpatient. But the remix boots to the desktop just fine otherwise, so I don't know what's going on. :confused: Am I supposed to enter commands even with that text flowing? It doesn't get to the "root@rm1tw#". Can anyone help?
[Remix Mini General] kanyazsombor:
It's ok. Don't worry. You can write there.

But also can try in coolterm: options/2nd tab/line mode instead of raw. That way you will have a line at the bottom for the commands.

From the Chinese site use the following command :

/dev/tty.usbserial 115200

After this you will have the "root..."

Than use all the commands (on the Chinese site. The command is after the # sign in each line)

DirtyLightningBacon
[Remix Mini General] unloseking2500:
Full detailed tutorial of how to root remix mini here: http://xdaforums.com/remix/remix-mini/how-to-root-remix-mini-t3388437
[Remix Mini General] Rone5390:
Cameron Having problem with my mini it will shut down and reboot repeatably sometimes. I can hit enter and stop it as it fades. It usually straightens out eventually. how do I fix this.
[Remix Mini General] romtim:
Please see this https://secure.avaaz.org/en/petitio...ters_Users_need_root_access_to_remix_mini_1/﻿
[Remix Mini General] RetroHetero:
We realize that it voids the warranty, however, as owners and buyers of YOUR device, we have THE RIGHT to do whatever the hell we want with it. If I can risk rooting and flashing a custom ROM on a $600+ smartphone, then I sure as hell am going to risk doing the same on a device that only costs around $50. I don't understand why Jide keeps insisting on denying it's customers with root access. While the majority will not care about having root access, there are people who like tinkering with stuff. To be honest, I bought this device thinking that it would have root access and that is a big part of why I bought this device in the first place.

You are a disappointment, Jide.
[Remix Mini General] dinh_duy:
Could you please upload your system_image file then send me link? Thank you so much for help!
[Remix Mini General] joeylikesubuntu:
warranty

i do not care if it voids the warranty this thing was cheap why should we give a damn about the warranty we bought it we own it we should be able to fix it or change it whenever we wish don't go down this jail route please your giving android a bad name good luck trying to convince the intelligent to buy one
[Remix Mini General] WacoJohn:
What I don't get is if Jide doesn't allow rooting, why then, in APP STORE/SETTINGS, is there an option ALLOW ROOT INSTALLATION check box?? .... and what would happen if I checked it??
[Remix Mini General] gohanSS:
Maybe for root only apps? ?

Inviato dal mio ASUS_Z00A utilizzando Tapatalk
[Remix Mini General] WacoJohn:
Probably for rooted apps but I thought maybe Jide is now approving ROOT. Just thought I would ask.
[Remix Mini General] lynxznet:
Now we need custom recoveries and ability to unlock the bootloader.
[One (M7) Q&A, Help & Troubleshooting] deadman3000:
I have been testing out some dash cam apps for my car on my M7 with HD Revolution. 93.0 but am having issues recording any video with dash cam overlays. It becomes extremely jerky. I have tried several apps and all have the same issue. I have tried different resolutions, bitrates, codecs, FPS etc all with the same result. On app called DailyRoadVoyager does not have overlay recording in the unpaid app and records perfectly even at 1080P (just like the normal camera app does). But anything with overlays brings video recording to its knee's.

Is there anything I can do fix this or am I going to need a new phone or dedicated dash cam? I tried it on my brothers S6 Edge BTW and had no such issues.
[G2 Q&A, Help & Troubleshooting] Velkyrix:
This is not the 2% error, this is not close to that.

Don't worry my g2 is not bricked, i just want to downgrade but can't because of this problem.

When i tempt to flash a kdz, LGUserCSTool Just crashes on me.

I heard a few people managed to get a log on this, but I don't have the option (windows 10.1).

So, can anyone here help me?

Probably this will take sometime, because every thread I open/opened usually gets ignored by everyone:crying:

Help please!
[G2 Q&A, Help & Troubleshooting] Velkyrix:
This is exactly like the other thread I opened... am I doing something wrong?

why isn't anyone ever replying to me....

and before someone just comes here and says patience,

the last thread I opened was 4 months ago and till today no one replied....

really am I doing something wrong?
[G2 Q&A, Help & Troubleshooting] raptorddd:
try different computer if it crahses or do a format computer.