Related
I have been working on some boot/recovery ROM rebuilds for the Garmin/Asus Garminfone A50 (T-Mobile), as well as the scripts and instructions... I'm not sure where to host them.
I personally don't want to host them myself, and was wondering if there is a repository of sorts.
At the moment, I have the following:
* The tools necessary (dump_image & flash_image) to dump the firmware from the phone
* The scripts necessary to unpack/repack the boot/recovery ROM's (modified to support the Garminfone's different address layout). Linux based.
* Pre-built boot and recovery images that give permanent root and mount the system/data partitions as r/w by default.
* Instructions on how to do it yourself, complete with some tech info on the layut of the Garminfone boot/recovery images and how to verify before you flash it that it built properly.
* Instructions on how to flash the phone without risking bricking it, since there is no hardware key combo to get into recovery and a fastboot that's not fully implemented. The technique goes like:
- Verify with a hex editor that the proper addresses are in the header
- Flash the new boot image to recovery
- Reboot into recovery to make sure it boots the new boot image properly
- Flash the rooted recovery image to the recovery partition
- Reboot into recovery once more and verify that works
- Flash the tested boot image to the boot partition
- Reboot normally and have fun
That method works fairly well, and unless you target the wrong partition, and gives you a 99.9% success rate
I'm going to post what I can on the Wiki (as far as instructions go), but it would be nice if I had a place to put the tool set as well.
I'd rather not use one of the temporary sites like Mediafire or what not, since files on those sites have a tendency to disappear.
Please no PM's on having me send them the files directly. I don't have a heck of a lot of spare time and don't want to get into the habit of sending these out manually.
If you're against the typical file hosts and the files aren't too big you could try using dropbox or sugarsync and sharing the links.
Can I ask you a question? I have a Kyocera ZIO M6000 and have the openzio clockworkmod 2.5.1.1 port that only works with "fastboot boot openzio-recovery" and we have tried flashing to our recovery partition with no success. What will it take to break the tether and reboot recovery locally without fastboot?
Sent from my Zio using XDA App
merwin said:
I have been working on some boot/recovery ROM rebuilds for the Garmin/Asus Garminfone A50 (T-Mobile), as well as the scripts and instructions... I'm not sure where to host them.
I personally don't want to host them myself, and was wondering if there is a repository of sorts.
At the moment, I have the following:
* The tools necessary (dump_image & flash_image) to dump the firmware from the phone
* The scripts necessary to unpack/repack the boot/recovery ROM's (modified to support the Garminfone's different address layout). Linux based.
* Pre-built boot and recovery images that give permanent root and mount the system/data partitions as r/w by default.
* Instructions on how to do it yourself, complete with some tech info on the layut of the Garminfone boot/recovery images and how to verify before you flash it that it built properly.
* Instructions on how to flash the phone without risking bricking it, since there is no hardware key combo to get into recovery and a fastboot that's not fully implemented. The technique goes like:
- Verify with a hex editor that the proper addresses are in the header
- Flash the new boot image to recovery
- Reboot into recovery to make sure it boots the new boot image properly
- Flash the rooted recovery image to the recovery partition
- Reboot into recovery once more and verify that works
- Flash the tested boot image to the boot partition
- Reboot normally and have fun
That method works fairly well, and unless you target the wrong partition, and gives you a 99.9% success rate
I'm going to post what I can on the Wiki (as far as instructions go), but it would be nice if I had a place to put the tool set as well.
I'd rather not use one of the temporary sites like Mediafire or what not, since files on those sites have a tendency to disappear.
Please no PM's on having me send them the files directly. I don't have a heck of a lot of spare time and don't want to get into the habit of sending these out manually.
Click to expand...
Click to collapse
I would also suggest dropbox or even id host them off my computer via ftp
Can your method work with Garminasus A10?
Merwin you still working on this?
Yeah, I am working on it still. I am still looking for a better place than dropbox or hosting off of someone's home PC...
As for the A10, if you can get me a dump of the boot and recovery images I can make one for that too... you will want to preferably use the dump_image utility to get the image and the flash_image utility to flash it.
I can probably attach those to a post with dump instructions. They're tiny.
Basically, you root your phone, copy the files to a certain location, type a couple commands to fix permissions on the executables, then run a command to dump the image.
Flashing back requires clearing the boot or recovery partition with a command and then using the flash_image command to flash it.
My method tests the new boot image first by flashing it to recovery first and rebooting into recovery to make sure the new image works. Then flash the modified recovery image to the recovery and make sure it is rooted (so you can get things up again if something does go wrong). Then you flash the new tested boot image to boot. If, for some reason, that fails, it should reboot automatically into recovery after a few boot failures. Never had to test that, since I pre-test all images I make.
hi merwin, we are a fans group of GA a10 and we trust a lot in your work! if you need any kind of help contact me! probably you are the first in the world who can flash a GA phone
Merwin, Im not completely sure which type of place your looking for if its not either ftp or online file sharing
Rapidshare
2shared
Filefront
4shared
Hi merwin,
I found this page, is that similar to your method? Hope you guys can find out something.
http://mygarminfone.blogspot.com/
afoster1003 said:
Merwin, Im not completely sure which type of place your looking for if its not either ftp or online file sharing
Rapidshare
2shared
Filefront
4shared
Click to expand...
Click to collapse
You forget one widely used protocol. Good old http on a standard web server.
Those other sites annoy me greatly, between the amount of ads, having to wait to download and daily limits, and the fact that they are temporary unless I pay. I am against them on principle.
I figure if there is enough interest, someone will step up to host them, otherwise I will just provide scripts, instructions, and technical info for people to do it themselves.
slumpz said:
Hi merwin,
I found this page, is that similar to your method? Hope you guys can find out something.
http://mygarminfone.blogspot.com/
Click to expand...
Click to collapse
You are my hero That blog has the missing pieces I need to keep going.
A couple of days ago I found some info on how to decompile the .update files which gives us the recovery image and system partition from any other phone that uses a similar format, like the Asus A10... providing a whole host of opportunities for the Asus phones that are still being maintained.
For instance, I grabbed the files from the Chinese A50 that has newer firmware.
With the info from the blog, I may be able to at least compile and integrate the newer kernel and wifi firmware (which is stored on the phone and loaded into memory at boot). The Chinese version does have newer wifi module firmware in it... whether it is compatible or not is another story.
On another note, has anyone successfully downloaded the open sources kernels from Asus? I have tried every method on their site and all but a couple of the kernel versions in the zip are corrupt. One from march extracts fine, so I may use that as a base to start with.
merwin said:
You are my hero That blog has the missing pieces I need to keep going.
A couple of days ago I found some info on how to decompile the .update files which gives us the recovery image and system partition from any other phone that uses a similar format, like the Asus A10... providing a whole host of opportunities for the Asus phones that are still being maintained.
For instance, I grabbed the files from the Chinese A50 that has newer firmware.
With the info from the blog, I may be able to at least compile and integrate the newer kernel and wifi firmware (which is stored on the phone and loaded into memory at boot). The Chinese version does have newer wifi module firmware in it... whether it is compatible or not is another story.
On another note, has anyone successfully downloaded the open sources kernels from Asus? I have tried every method on their site and all but a couple of the kernel versions in the zip are corrupt. One from march extracts fine, so I may use that as a base to start with.
Click to expand...
Click to collapse
I have, magically I might add. I downloaded the source for v.5.0.70 and managed to get it compiled. The resulting files can be found on on my blog, the one Slumpz posted(I can't post links yet, lol.)
The only problem is, I don't have much experience with anything linux. But, If you have any questions Merwin, email me, [email protected].
Here's a little how to, just check my blog, or google: How To: Build Garmin-Asus Kernel from Source.
am willing to giv a subdomain/storage ftp access on this domain for the good of the community if it helps any
Domain darkjester.net
Disk Usage 5.4 / 1500.0 MB
Bandwidth 100000 MB (100GB)
Home Root /home/a2931495
Apache ver. 2.2.13 (Unix)
PHP version 5.2.*
MySQL ver. 5.0.81-community
Activated On 2011-05-15 14:42
Status Active
Hello guys, are you still working on this.
I found out that A10 has a new firmware posted, which is versioned 5.2.7 instead of 5.0.x like the others. I wonder if there's any method to test this firmware on foreign A10 (non Chinese firmware)?
So, got an HTC Sensation 4G... meaning not much more work on the Garminfone for me.
Still trying to find time to compile everything that I have done into some semi-coherent document with the unlocked boot and recovery images. I still have the Garmin, so if someone manages a huge breakthrough then I may pick it up again. Really didn't want to get rid of the phone but there just isn't enough community development going on to make it worthwhile.
By the way, the Garminfone GPS blows every other phone away. The Sensation 4G is crap in comparison.
Drawing from the impressive work of CrashXXL in rooting our phones, jahrule in simplifying the process, and Sabissimo in developing a tutorial to bake in apps for those of us with locked bootloaders and write protected systems, I have with great effort arrived at this glorious day. I present to thee: Suicide Flash.
What is Suicide Flash? It is a collection of Bash scripts and other files which streamline and automate the process of using the Qualcomm emergency download mode (Qualcomm HS-USB QDLoader) to write to the system partition on Moto phones using MSM8960 processors. It applies the method used to root these devices (see here, for example) to the task of arbitrary system modification. In other words: Suicide Flash makes it easy(ish) to modify system files for those of us who can't use traditional methods.
Code:
DISCLAIMER: This is obviously a dangerous tool. I mean, it
flashes your phone by bricking it first. Be smart. I shan't be held
responsible if your phone melts, explodes, loses all of its data,
or cheats on you with a hula dancer.
Who Can Use It?
Suicide Flash is for sure compatible with most Moto X variants. The testing has been done primarily with an XT1049, the Republic Wireless model, but has also included the XT1060 (Verizon) and should work on most/all of them. However, in theory any phone, or at least any Moto phone, using the MSM8960 chip could be compatible, such as the Droid Turbo. So to simplify:
XT1049 (Moto X Republic Wireless): Tested and working
XT1060 (Moto X Verizon): Tested and working
XT1058 (Moto X AT&T): Untested, highly likely to work
XT10XX (Any other Moto X): Untested, likely to work
Others: Untested, may work as long as they use MSM8960
How Do I Use It?
Suicide Flash (SF) consists of three main scripts: a flashing script, a package creation script, and a pushing script. Details:
suicideflash.sh: Flashes SF packages to the phone in bricked (QDLoader) mode
pkgmaker.sh: For developers. Creates SF packages from system images.
suicidepush.sh: Uses the SF system to "push" system files in an ADB-like way
To use these scripts, simply extract them to a place of your convenience. All scripts must be run from the root Suicide Flash folder. Do not run any of them from within the "scripts" folder. Also, while it may not strictly be necessary, it is best (if you are developer) to include any relevant system images in the root Suicide Flash folder, as well.
As an end user, you can download SF packages created by developers and flash them using the main Suicide Flash script. As a developer, you can pull system images and use them to create SF packages with the pkgmaker.sh script. Anyone can feel free to use the Suicide Push script to push files to their device. For more information, here are the help pages for each.
Suicide Flash:
Code:
Usage: suicideflash.sh PACKAGE
Flashes PACKAGE to the system parition of a Moto phone using Qualcomm
emergency download mode.
Options:
-h, --help displays this help message
-s, --skip skips all prompts and runs without user interaction
Created by the Nicene Nerd, whose blog at <http://www.thenicenenerd.com/> has
absolutely nothing to do with Android
Package Maker:
Code:
Usage: pkgmaker.sh [OPTION]... ORIGINALSYSTEM TARGETDEVICE REQUIREMENTS
SYSTEMOFFSET OUTPUTFILE
Creates a Suicide Flash package for writing to Moto phones via the emergency
Qualcomm download mode.
Arguments:
ORIGINALSYSTEM provides the original system image to be modded
TARGETDEVICE specifies the model of phone for the package to flash
REQUIREMENTS notes any important requirements for the phone state
prior to flashing
examples: "Stock", "Rooted", or "Rooted+Xposed"
SYSTEMOFFSET the address of the system partition on the target device
should be in hex format (i.e. 0x6420000 or 6420000)
can use value ADB to pull the offset over ABD
OUTPUTFILE the name of the Suicide Flash zip package to be created
Options:
-h, --help returns this help message
-m MODDEDSYSTEM specifies an existing modded system image
if not given, will mount original for modification
Created by the Nicene Nerd, whose blog at <http://www.thenicenenerd.com/> has
absolutely nothing to do with Android
Suicide Push:
Code:
Usage: suicidepush.sh LOCALFILE REMOTEFILE
Uses Suicide Flash to push LOCALFILE to a phone system at REMOTEFILE.
Created by the Nicene Nerd, whose blog at <http://www.thenicenenerd.com/> has
absolutely nothing to do with Android
What Do I Need to Use It?
A Linux installation
ADB
Fastboot
Rhino
Python
A package called python-serial
VirtualBox
ADB Insecure (if developing or using Suicide Push)
If you don't have some of these (except, obviously, the first one and the last one), you can run the included script install-tools.sh. It will automatically install anything you're missing.
Okay, Give Me Step-By-Step Instructions
For End Users:
Download the attached Suicide Flash zip
Extract the zip to a convenient folder and open a terminal window there
Go ahead and use sudo su
Run install-tools.sh
Download an SF package from a developer for your device
Flash the package with the command:
Code:
./suicideflash.sh DOWNLOADEDPACKAGE.zip
Profit!
For Developers:
Download the attached Suicide Flash zip
Extract the zip to a convenient folder and open a terminal window there
Go ahead and use sudo su
Run install-tools.sh
Pull a system image from your phone
Run pkgmaker.sh to create an SF package
Upload the package for the benefit of others
For Anyone, to Use Suicide Push
Download the attached Suicide Flash zip
Extract the zip to a convenient folder and open a terminal window there
Go ahead and use sudo su
Run install-tools.sh
Push files to your phone's system partition with this command:
Code:
./suicidepush.sh LOCAL_SOURCE /system/PUSH_DESTINATION
So, What Can I Do with It Right Now?
If you're a developer, you can get to work creating SF packages for your device. If you're just a plain ol' user, there's not much to be done until others chip in. I have uploaded one package as a sample and for the convenience of anyone looking to root their XT1049 and install Xposed. I will maintain a master list of uploaded packages as people make them.
XDA:DevDB Information
Suicide Flash for Moto, Tool/Utility for the Moto X
Contributors
Nicene Nerd, CrashXXL, Sabissimo
Version Information
Status: Testing
Created 2015-08-07
Last Updated 2015-08-07
Master Package List
XT1049: Republic Wireless Moto X
- root-xposed-xt1049-4.4.4.zip: Root and Xposed for XT1049. Requires stock 4.4.4 from SBF, not OTA.
- busybox-xt1049-rooted-xposed-4.4.4.zip: BusyBox for XT1049. Requires 4.4.4 rooted w/ Xposed.
XT1058: AT&T Moto X
- root-xt1058-4.4.4.zip: Root for XT1058 KitKat. Requires stock 4.4.4 from SBF, not OTA.
- xposed-xt1058-rooted-4.4.4.zip: Xposed for XT1058 KitKat. Requires rooted 4.4.4.
- root-xt1058-5.1.zip: Root for XT1058 Lollipop. Requires stock 5.1 from SBF, not OTA.
XT1060: Verizon Wireless Moto X
- root-xt1060-4.4.4.zip: Root for XT1060. Requires stock 4.4.4 from SBF, not OTA.
- xposed-xt1060-rooted-4.4.4.zip: Xposed for XT1060. Required rooted 4.4.4.
Changelogs:
08/07/2015 - v0.2
- suicideflash.sh: Increased wait period before giving error on not finding phone in emergency mode
- mountimg.sh: Fixed issue which would cause errors preventing images from mounting
- pkgmaker.sh: Added option to pull system image over ADB, improved error handling
Developer pkgmaker.sh Tutorial: Creating an Xposed Framework Package
Say you want to make a package that installs the Xposed framework, since that requires writing to /system. Here's how you would do it with Suicide Flash (assuming you have already rooted the phone):
Open a terminal window to your Suicide Flash root folder. Then sudo su.
Pull a system image. One way to do that:
Code:
adb root
adb shell dd if=/dev/block/platform/msm_sdcc.1/by-name/system /sdcard/originalsystem.img bs=1024
adb pull /sdcard/originalsystem.img
Run the pkgmaker script like this, assuming you're using a rooted XT1049 on 4.4.4, but you don't know the offset of the system partition, so you want to pull it via ADB. The script will be placed in output/xposed-flash-package.zip.
Code:
./pkgmaker.sh originalsystem.img XT1049 "Stock 4.4.4" ADB xposed-flash-package.zip
The script will pause when originalsystem.img is mounted for writing. As root, copy the Xposed app_process file (which you can extract from the APK if you need it) to "mnt-originalsystem.img/bin/app_process". Then press enter.
The script will continue executing, hopefully without errors.
Voila! Your package xposed-flash-package.zip is ready to upload and/or flash.
Finally!
The XT1049 has stumped me for a long time, but finally someone found a way!
Just a thought as I'm going into this, there's no mention of drivers for linux. Obviously this isn't to "user" level yet, and I wouldn't put myself too much beyond that, but it's a nice thing to include. I'll be trying it later, but are the drivers for USB/ADB the same as the emergency mode drivers? I'm kind of nervous to try because of the soft brick, and there doesn't appear to be any mention of how the flashed file that bricks it is put back. I'm assuming I can pull the original image before I flash the new one, but I'm not sure yet.
Also, if you have it tested and everything with Republic, I would appreciate a torrent or hosted file somewhere. If there isn't one before I finish, I'll post it.
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
Cindex said:
The XT1049 has stumped me for a long time, but finally someone found a way!
Just a thought as I'm going into this, there's no mention of drivers for linux. Obviously this isn't to "user" level yet, and I wouldn't put myself too much beyond that, but it's a nice thing to include. I'll be trying it later, but are the drivers for USB/ADB the same as the emergency mode drivers? I'm kind of nervous to try because of the soft brick, and there doesn't appear to be any mention of how the flashed file that bricks it is put back. I'm assuming I can pull the original image before I flash the new one, but I'm not sure yet.
Also, if you have it tested and everything with Republic, I would appreciate a torrent or hosted file somewhere. If there isn't one before I finish, I'll post it.
Click to expand...
Click to collapse
Sorry for the double post but I can't edit yet, just realized that the zip file there is all that's needed for Republic. I was going to post the ADB/USB driver setup link for linux, but I'm not allowed yet.
Cindex said:
The XT1049 has stumped me for a long time, but finally someone found a way!
Just a thought as I'm going into this, there's no mention of drivers for linux. Obviously this isn't to "user" level yet, and I wouldn't put myself too much beyond that, but it's a nice thing to include. I'll be trying it later, but are the drivers for USB/ADB the same as the emergency mode drivers? I'm kind of nervous to try because of the soft brick, and there doesn't appear to be any mention of how the flashed file that bricks it is put back. I'm assuming I can pull the original image before I flash the new one, but I'm not sure yet.
Click to expand...
Click to collapse
You shouldn't need to do anything special for Linux drivers. It works straightforwardly as long as you have fastboot and ADB. The flashed file that creates the softbrick is included by the package maker script in every Suicide Flash package, so it is easy to unbrick. In fact, I can upload another package just for unbricking if you'd like.
Added a BusyBox package for XT1049, and added root and Xposed packages for XT1060.
Edit: also added root packages for XT1058 on both KitKat and Lollipop, plus Xposed for XT1058 KitKat.
Nicene Nerd said:
You shouldn't need to do anything special for Linux drivers. It works straightforwardly as long as you have fastboot and ADB. The flashed file that creates the softbrick is included by the package maker script in every Suicide Flash package, so it is easy to unbrick. In fact, I can upload another package just for unbricking if you'd like.
Click to expand...
Click to collapse
That's good to know, I looked around and couldn't find anything on the driver for the Qualcomm Emergency Download mode. I suppose not needing one would be why. Actually some kind of emergency package to unbrick might be good. Now that I see the script in there I don't have a problem, but someone might like it.
So now I'm wondering if I actually have to do a factory reset again, or if I can just flash the SBF file itself and not have to wipe. I'm not sure how big of a difference there is, because I did the factory restore recently and the OTA update was like 6MB or something. I wouldn't think there's be an issue flashing it rather than factory restore. Any ideas?
Also, if anyone knows a good way to do this with Virtualbox it would be a nice addition. I'm personally not going to bother since I already have a bootable Ubuntu USB, but it seems that most people would rather set up a VM with a small linux distro. If it had the tools baked in, it would make it an easy process.
Cindex said:
That's good to know, I looked around and couldn't find anything on the driver for the Qualcomm Emergency Download mode. I suppose not needing one would be why. Actually some kind of emergency package to unbrick might be good. Now that I see the script in there I don't have a problem, but someone might like it.
So now I'm wondering if I actually have to do a factory reset again, or if I can just flash the SBF file itself and not have to wipe. I'm not sure how big of a difference there is, because I did the factory restore recently and the OTA update was like 6MB or something. I wouldn't think there's be an issue flashing it rather than factory restore. Any ideas?
Also, if anyone knows a good way to do this with Virtualbox it would be a nice addition. I'm personally not going to bother since I already have a bootable Ubuntu USB, but it seems that most people would rather set up a VM with a small linux distro. If it had the tools baked in, it would make it an easy process.
Click to expand...
Click to collapse
Technically, the only reason for the SBF is because when you install OTA updates, files may end up in slightly different positions depending on the circumstances. For this to work, you must start with an identical system partition to the one used for making the package. So all you need to really do is extract the system.img and flash it, if you wish. No data loss necessary.
Also, I'll look into a minimal VM. I thought about actually trying to make a Windows version of Suicide Flash. I'm not sure which I'll end up with.
So I tried this on my Ubuntu 12.04.5 last night, and it didn't recognize the device in fastboot. I'm going to try on Ubuntu 15.04 soon here. Another question for you though, which sdk do I use for XPosed? I don't seem to be able to figure it out searching all over. I would think 16, but maybe it's for Lollipop?
I think I'm going to get some of these with the OTA, it'll make it easier for the average Republic user once it's gotten going.
Cindex said:
So I tried this on my Ubuntu 12.04.5 last night, and it didn't recognize the device in fastboot. I'm going to try on Ubuntu 15.04 soon here. Another question for you though, which sdk do I use for XPosed? I don't seem to be able to figure it out searching all over. I would think 16, but maybe it's for Lollipop?
I think I'm going to get some of these with the OTA, it'll make it easier for the average Republic user once it's gotten going.
Click to expand...
Click to collapse
I can't answer your Xposed Lollipop question. I was wondering the same thing, but I ended up simply pulling the file from an existing Xposed installation. I suppose you could do the same and then diff the files to find out which is correct.
As for the OTA, that's not possible. Every time an OTA is installed, the files can end up in different places on the flash memory, and this utility requires knowing the exact locations for making changes. You'd have to make separate packages for every phone. Otherwise you'll end up with bootloops.
Has anyone tried using Suicide Push? It's slow, but I thought it would be the more celebrated part of this since it lets you do basically the same as an ADB push to the system partition. You could even install Xposed that way:
Code:
./suicidepush.sh local_app_process_file /system/bin/app_process
Nicene Nerd said:
Has anyone tried using Suicide Push? It's slow, but I thought it would be the more celebrated part of this since it lets you do basically the same as an ADB push to the system partition. You could even install Xposed that way:
Code:
./suicidepush.sh local_app_process_file /system/bin/app_process
Click to expand...
Click to collapse
I'm still working on getting it to root. I was going to a few days ago, but my flash drive burned out. I'm going to try Ubuntu 14.04.3.
What linux distro did you use?
---------- Post added 14th August 2015 at 12:41 AM ---------- Previous post was 13th August 2015 at 11:47 PM ----------
Sorry to double post again, but I can't edit yet and have a few more things. I can't seem to be able to find a RW SBF file. I'm thinking restore from factory sounds like a good solution, but I don't know if that's the same thing.
How can I pull a system image if I'm not root? Without an SBF file, I need to package it for myself. Without root, I can't pull the system.img. I'm sure others on networks not covered yet would like to know also. Where did you get your system.img?
Also, if we can get this deep, and you can modify the bootloader, couldn't you just flash the old bootloader image and then the rest of the ROM? Then we could unlock the bootloader using older methods. We might have to flash block by block, but it should work?
Cindex said:
I'm still working on getting it to root. I was going to a few days ago, but my flash drive burned out. I'm going to try Ubuntu 14.04.3.
What linux distro did you use?
---------- Post added 14th August 2015 at 12:41 AM ---------- Previous post was 13th August 2015 at 11:47 PM ----------
Sorry to double post again, but I can't edit yet and have a few more things. I can't seem to be able to find a RW SBF file. I'm thinking restore from factory sounds like a good solution, but I don't know if that's the same thing.
How can I pull a system image if I'm not root? Without an SBF file, I need to package it for myself. Without root, I can't pull the system.img. I'm sure others on networks not covered yet would like to know also. Where did you get your system.img?
Also, if we can get this deep, and you can modify the bootloader, couldn't you just flash the old bootloader image and then the rest of the ROM? Then we could unlock the bootloader using older methods. We might have to flash block by block, but it should work?
Click to expand...
Click to collapse
I used Ubuntu 14.04.
The RW 4.4.4 SBF can be found here or here. It does not appear possible to pull a system image without root. But even without permanent root, KingRoot can get you temp root long enough to pull a system image.
As for the bootloader, there's certainly a chance that this could be done. It's just so risky that I won't try it myself. If there was a single variable missed, it could easily mean hard-brick. But in theory, as far as I understand, it might work. The biggest obstacle might be partition changes. If you got the bootloader to get into fastboot mode, though, you could presumably fix that with an old SBF.
Flashing the olderer bootloader will not work (I have tried and confirmed it does not work). It is because the efuses verify the bootloader.
Wow! That's hell of a tool you've created here Awesome job! I haven't tried it myself yet, but, judging by source code, it should get the work done. More of a developer tool, ofc, but it's more then impressive Maaan, I wish there was a normal way to work with ext4 partitions to make it available on Windows))
Since you've made "push" version of it (and that's the most interesting part, longest though), the next step in future development should be doing the same with TWRP flashable zips. Some of them just put apk-s in system folder, some of them have shell scripts inside, I've yet to figure out the pattern But that would be awesome next step to this awesome project
download link not found )
theres a tool bar at top crash with download links next to discussions and screenshots
Sabissimo said:
Wow! That's hell of a tool you've created here Awesome job! I haven't tried it myself yet, but, judging by source code, it should get the work done. More of a developer tool, ofc, but it's more then impressive Maaan, I wish there was a normal way to work with ext4 partitions to make it available on Windows))
Since you've made "push" version of it (and that's the most interesting part, longest though), the next step in future development should be doing the same with TWRP flashable zips. Some of them just put apk-s in system folder, some of them have shell scripts inside, I've yet to figure out the pattern But that would be awesome next step to this awesome project
Click to expand...
Click to collapse
I've actually started work on a Windows version, but it's on back burner because school just started. Here's a hint, though: with OSFMount and Ext2Fsd, you can mount Moto system images (pulled from the phone, not SBF ones) as hard drives or removable disks. Suicide Flash for Windows will rely on them.
So what are the chances I could use this to pull a system.img, and actually go in and delete some apps out of my XT1058? I had some success but it pulled the image as a mbn and I'm hesitant to try flashing it.
lpjunior999 said:
So what are the chances I could use this to pull a system.img, and actually go in and delete some apps out of my XT1058? I had some success but it pulled the image as a mbn and I'm hesitant to try flashing it.
Click to expand...
Click to collapse
Here's what you'll want to do:
Create the system image on the phone with
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/oldsystem.img bs=1024
ADB pull or MTP copy the image to your PC.
Run pkgmaker.sh like so:
Code:
./pkgmaker.sh oldsystem.img XT1058 "My System" 4B000000 modded-system.zip
When prompted, you can delete apps as root from the mounted system image under mnt-oldsystem.img/app or mnt-oldsystem.img/priv-app
Continue and finish the script.
Flash with
Code:
./suicideflash.sh -s output/modded-system.zip
I recently purchased an MX10 Android TV Box running Android 7.1.2
It is supposed to be rooted and SuperSU came installed but when you run it, it reports that the SuperSU binary is not installed and SuperSU cannot install it. I've done a full factory reset but the image comes back broken like that.
I downloaded updated firmware for this box and the SuperSU zip file but I cannot get this box into recovery mode. Everything I've found says to stick a toothpick in the AV hole and power up the box. When I do that, the MX10 logo shows but then it pops up with "erasing" and then reboots. All that does is a full factory reset.
If I run Root Checker, it says I don't have root.
Anyone have any experience with this issue and this box? If I can't get into recovery mode then I can't fix SuperSU and/or update the firmware to one where I'm rooted.
The box otherwise seems to work ok with the exception that I cannot set a live wallpaper. I'm just not rooted.
Thanks for any help!
-TimG
TimothyGaray said:
I recently purchased an MX10 Android TV Box running Android 7.1.2
It is supposed to be rooted and SuperSU came installed but when you run it, it reports that the SuperSU binary is not installed and SuperSU cannot install it. I've done a full factory reset but the image comes back broken like that.
I downloaded updated firmware for this box and the SuperSU zip file but I cannot get this box into recovery mode. Everything I've found says to stick a toothpick in the AV hole and power up the box. When I do that, the MX10 logo shows but then it pops up with "erasing" and then reboots. All that does is a full factory reset.
If I run Root Checker, it says I don't have root.
Anyone have any experience with this issue and this box? If I can't get into recovery mode then I can't fix SuperSU and/or update the firmware to one where I'm rooted.
The box otherwise seems to work ok with the exception that I cannot set a live wallpaper. I'm just not rooted.
Thanks for any help!
-TimG
Click to expand...
Click to collapse
Yeah i just got mine yesterday and im having the same issue. I get a Root user account error with Root Checker Pro. Ive tried clearing data in the SU app but nothing. There is an update for SU in the Play Store but i read on Freaktab where someone said not to update SU app or it will give you a bootloop. I havent updated it yet cuz i wanted to do some more investigating but i really dont see the harm in just updating the app itself. I know updating the su binary will result in a bootloop because i updated the binary on my T95Z and got the bootloop. Ive been googling all day trying to find a TWRP.img file for the MX10 but have found nothing yet. Ive also been looking for a root method for this box as well but not sure what i should use. It would be nice if these each box had it own sub forum like the phones have.. would make life so much easier. lol
If you figure anything out i would appreciate if you would pass that info on.. will do likewise.
htxp://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/freaktabs-tools-utility-collection/656634-twrp-recovery-for-rockchip-devices
I'm in the same boat. Recieved my mx10 a week ago. Tried the tooth pick in the av port. Shows on screen 'erasing' and eventually factory defaults. No root
Android 7.01 said:
htxp://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/freaktabs-tools-utility-collection/656634-twrp-recovery-for-rockchip-devices
I'm in the same boat. Recieved my mx10 a week ago. Tried the tooth pick in the av port. Shows on screen 'erasing' and eventually factory defaults. No root
Click to expand...
Click to collapse
Have you updated the SU app? Not the su binary but the app from play store itself?
Hi, actually I was looking to root the MX10 but for a simple reason:
all I want to to is to get a shutdown or power off button, but this seems missing on the MX10 .. !!! First time I see a box without the shutdown option.
I looked up for apps providing power off button but they all require root access and so don’t work on the out-of-the-box MX10.
Anyone has same need and a solution?
Hi, I received my MX10, a few days ago and have the same problem (SuperSU issue).
I purchased it from GeekBuying, and posted on their blog, for the latest firmware update I could find: http://blog.geekbuying.com/2017/12/...r4-32gb-emmc-tv-box-firmware-update-20171214/
Really want to root it, so I can edit the keyboard/remote control files to map keys on the H18+ remote I bought at the same time as the MX10.
I haven't tried flashing different firmware (or booting into recovery). If/when I receive a reply to my post on the GeekBuying blog, I'll post here - but no idea if they'll reply.
supergiulio said:
Hi, actually I was looking to root the MX10 but for a simple reason:
all I want to to is to get a shutdown or power off button, but this seems missing on the MX10 .. !!! First time I see a box without the shutdown option.
I looked up for apps providing power off button but they all require root access and so don’t work on the out-of-the-box MX10.
Anyone has same need and a solution?
Click to expand...
Click to collapse
Hey bud if you hold the power button down on the remote for about 5 seconds and it will bring the reboot menu up.. it has shut down and restart.
Do the same to boot up
Ok.. everyone else that was wondering about root.. looks like this is our answer.. no root.. no TWRP...... for now at least. This box is still fairly new so im
not giving up. It took 4-5 months for them to get root for Snapdragon S8 so who knows.. it may come for the MX10 one day too
{
"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"
}
freak69ize said:
Hey bud if you hold the power button down on the remote for about 5 seconds and it will bring the reboot menu up.. it has shut down and restart.
Ok.. everyone else that was wondering about root.. looks like this is our answer.. no root.. no TWRP...... for now at least. This box is still fairly new so im
not giving up. It took 4-5 months for them to get root for Snapdragon S8 so who knows.. it may come for the MX10 one day too
View attachment 4436137
Click to expand...
Click to collapse
Seems really odd that it would come with Super SU installed, and not be rooted. Then again, it also advertises (on GeekBuying.com - in case anyone purchased elsewhere) that it comes with Kodi pre-installed, and mine didn't.
---------- Post added at 12:25 AM ---------- Previous post was at 12:21 AM ----------
TimothyGaray said:
...I downloaded updated firmware for this box and the SuperSU zip file...-TimG
Click to expand...
Click to collapse
Whereabouts did you get the firmware? Was it this one MX10_RK3328_KODI18.0_20171208.img ? Listed on this GeekBuying blog entry: http://blog.geekbuying.com/2017/12/...r4-32gb-emmc-tv-box-firmware-update-20171214/
RADiuMOz said:
Seems really odd that it would come with Super SU installed, and not be rooted. Then again, it also advertises (on GeekBuying.com - in case anyone purchased elsewhere) that it comes with Kodi pre-installed, and mine didn't.
---------- Post added at 12:25 AM ---------- Previous post was at 12:21 AM ----------
Whereabouts did you get the firmware? Was it this one MX10_RK3328_KODI18.0_20171208.img ? Listed on this GeekBuying blog entry: http://blog.geekbuying.com/2017/12/...r4-32gb-emmc-tv-box-firmware-update-20171214/
Click to expand...
Click to collapse
Yeah i agree.. odd it ships with su installed but no root. Theres some fw's on this page.... ive downloaded just in case i ever need it... dont see why i would since there is no root though. lol
http://freaktab.com/forum/tv-player...3328-4-32gb-tv-box-2-4ghz-wifi-fast-lan/page2
Hi mate,
Try my guide in the Media TV Box Amlogic forum. The recovery image is for TWRP. But you could try Philz or others. Worked on S912 and S905 so far fine.
https://forum.xda-developers.com/an...mlogic-s905x-s912x-faq-backup-switch-t3752897
No root? I suggest you follow backup instructions, take 3 backups - all paritions, boot only, recovery only.
Then you can extract the boot image from your backup and use that with Magisk to root your system. After Magisk modifies your boot image, reboot, and flash the modified package via TWRP bootable (see topic)
If you have anything you wish to contribute, please feel free to post anything you have learnt that you feel will help others.
Cheers mate!
Thanks for the tip
Thanks Freak69! It was so easy ... but still it would be good to root the MX10
freak69ize said:
Hey bud if you hold the power button down on the remote for about 5 seconds and it will bring the reboot menu up.. it has shut down and restart.
Do the same to boot up
Ok.. everyone else that was wondering about root.. looks like this is our answer.. no root.. no TWRP...... for now at least. This box is still fairly new so im
not giving up. It took 4-5 months for them to get root for Snapdragon S8 so who knows.. it may come for the MX10 one day too
View attachment 4436137
Click to expand...
Click to collapse
flipmode_11 said:
Hi mate,
Try my guide in the Media TV Box Amlogic forum. The recovery image is for TWRP. But you could try Philz or others. Worked on S912 and S905 so far fine.
https://forum.xda-developers.com/an...mlogic-s905x-s912x-faq-backup-switch-t3752897
No root? I suggest you follow backup instructions, take 3 backups - all paritions, boot only, recovery only.
Then you can extract the boot image from your backup and use that with Magisk to root your system. After Magisk modifies your boot image, reboot, and flash the modified package via TWRP bootable (see topic)
If you have anything you wish to contribute, please feel free to post anything you have learnt that you feel will help others.
Cheers mate!
Click to expand...
Click to collapse
Hey @flipmode_11 - which TWRP image should we use, please? In your post, you state to, "Download the X96 Media Player TWRP Recovery image...or a different device". As the X96 is S905X (from a quick Google - don't shoot me if I'm wrong!) and the MX10 is RK3328, the TWRP image for the X96 wouldn't work, would it? I took a look at the list of devices and can't find a matching device.
Cheers,
Richard.
---------- Post added at 09:59 PM ---------- Previous post was at 09:54 PM ----------
Somethng that REALLY annoys me about the MX10, is that I can't get it to write to my external USB drive (NTFS). It worked just fine - out of the box - on my old MXIII-G, but the MX10 just won't write to it (Total Commander and an FTP server app I usually use in order to access it from my LAN). Is this because of some weird driver, or because of root (permissions... I checked under apps and it has access to storage - but of course it does, because it can read the drive)?
I'm probably not too fussed about rooting this thing, if I can just get external drives working with it.
I did read about Android not supporting NTFS, for write - but my old MXIII-G did, so I'm assuming this should, too. The only other thing I can think of, is that the MXIII-G had something in the firmware for writing to NTFS.
I can't see why there would be external USB drive support, but you can't write to it - I mean, it's a TV box, surely there are some other people out there who copy movies, etc. to an external drive on the box, to watch?
G'day mate,
Yeah look just give it a try and see how you go. Booting to this recovery.img will not make any modifications. It is simply loading an interface and relevant dependencies for it to run. I read something about how RockChip devices are limited or something. I forget now, but that made me steer clear of them, despite having more regular updates and new hardware. :/ hmmm
No, you won't find a matching device. It is shocking that these mass-manufacturered generic devices aren't also listed. I recommend you give the recovery.img in my topic a stab.
Where did you source you MX10 from? Have you asked them? Although, every single Chinese seller I have come across has zero working knowledge or which models are better, plus have 101 mistakes in their specs (just got a $50 and $100 refund on Ebay for X96 and a 10.1" tablet! Wrong specs!).
NTFS? So it can READ but not WRITE? Hmm I would wipe everything in FAT32 for Android. Everything is much happier. You could try exFAT which is a superior file system. Have you tried this? Got any other ExFAT + FAT32 devices? Hmm actually I think I've been down that path with exFAT (Paragon tools to solve). Double check exFAT compatibility before proceeding with backup/wipe/re-format. Actually I know the Nexus 6 was able to read NTFS storage as helped a mate with one. But depends on the manufacturer! But the Nexus6 couldn't write to HPFS - never tested exFAT. I think there is an app - USB Media Exporter...? USB Media Explorer..? - I forget!?!
As you mentioned Total Commander, you could try it with the Paragon tool plug-in: https://play.google.com/store/apps/details?id=com.paragon.tcplugins_ntfs_ro -or- https://play.google.com/store/apps/details?id=com.paragon.mounter (not tried this, but images looks interesting - free!). I use Solid Explorer + Smart File Manager - never been a fan of TC... There are other methods out there, but they require Root, which will not help you! e.g. ChainFire's StickMount.
No, I think you should proceed. However, as per my topic, take a full backup of 3+ partitions prior to making changes. I had to revert to a backup on 20th as had 2x SED processes going nuts. Titanium backup'd all important stuff. Then rebooted to Micro SD TWRP and did 3 Partitions (leaving int. storage intact). So Rooting is essential. It really is. Plus using Magisk is even more important, as it does not make modifications to /System which makes life much easier upgrading/troubleshooting/debugging et al.
NOTE: I would infact backup all the data on that ext. drive, delete partitions and create 2 FAT32/EXFAT/NTFS for redundancy. I have had too many past issues with partitions getting corrupt on external drives.
1. Backup Boot partition, 2. Extract the backup and find the boot.img, 3. Install Magisk Manager, click Install and select option 2 and browse for the boot.img, 4. Flash updated /MagiskManager/boot.img via TWRP and you are rooted w/ Systemless SU and BusyBox. There is seriously nothing better than having Root and being Play "Certified". You won't look back! Plus you can always re-flash the stock Boot.img and do OTA manufacturer updates, then open Magisk Manager and repeat.
Mac is like that. You can only read NTFS drives, but read / write to stupid HFS/HPFS drives with Mac, unless you install something like Paragon to read NTFS. The same for Windows, can read HFS+ but read/write NTFS.
Every Android device, regardless of OS, is totally different. Different Kernel's, different builds, ...
Good luck and let me know how you go?
Cheers mate!
RADiuMOz said:
Hey @flipmode_11 - which TWRP image should we use, please? In your post, you state to, "Download the X96 Media Player TWRP Recovery image...or a different device". As the X96 is S905X (from a quick Google - don't shoot me if I'm wrong!) and the MX10 is RK3328, the TWRP image for the X96 wouldn't work, would it? I took a look at the list of devices and can't find a matching device.
Cheers,
Richard.
---------- Post added at 09:59 PM ---------- Previous post was at 09:54 PM ----------
Somethng that REALLY annoys me about the MX10, is that I can't get it to write to my external USB drive (NTFS). It worked just fine on my old MXIII-G, but the MX10 just won't write to it (Total Commander and an FTP server app I usually use in order to access it from my LAN). Is this because of some weird driver, or because of root (permissions... I checked under apps and it has access to storage - but of course it does, because it can read the drive)?
I'm probably not too fussed about rooting this thing, if I can just get external drives working with it.
I did read about Android not supporting NTFS, for write - but my old MXIII-G did, so I'm assuming this should, too. The only other thing I can think of, is that the MXIII-G had something in the firmware for writing to NTFS.
I can't see why there would be external USB drive support, but you can't write to it - I mean, it's a TV box, surely there are some other people out there who copy movies, etc. to an external drive on the box, to watch?
Click to expand...
Click to collapse
flipmode_11 said:
G'day mate,
Yeah look just give it a try and see how you go. Booting to this recovery.img will not make any modifications. It is simply loading an interface and relevant dependencies for it to run. I read something about how RockChip devices are limited or something. I forget now, but that made me steer clear of them, despite having more regular updates and new hardware. :/ hmmm
No, you won't find a matching device. It is shocking that these mass-manufacturered generic devices aren't also listed. I recommend you give the recovery.img in my topic a stab.
Where did you source you MX10 from? Have you asked them? Although, every single Chinese seller I have come across has zero working knowledge or which models are better, plus have 101 mistakes in their specs (just got a $50 and $100 refund on Ebay for X96 and a 10.1" tablet! Wrong specs!).
NTFS? So it can READ but not WRITE? Hmm I would wipe everything in FAT32 for Android. Everything is much happier. You could try exFAT which is a superior file system. Have you tried this? Got any other ExFAT + FAT32 devices? Hmm actually I think I've been down that path with exFAT (Paragon tools to solve). Double check exFAT compatibility before proceeding with backup/wipe/re-format. Actually I know the Nexus 6 was able to read NTFS storage as helped a mate with one. But depends on the manufacturer! But the Nexus6 couldn't write to HPFS - never tested exFAT. I think there is an app - USB Media Exporter...? USB Media Explorer..? - I forget!?!
As you mentioned Total Commander, you could try it with the Paragon tool plug-in: https://play.google.com/store/apps/details?id=com.paragon.tcplugins_ntfs_ro -or- https://play.google.com/store/apps/details?id=com.paragon.mounter (not tried this, but images looks interesting - free!). I use Solid Explorer + Smart File Manager - never been a fan of TC... There are other methods out there, but they require Root, which will not help you! e.g. ChainFire's StickMount.
No, I think you should proceed. However, as per my topic, take a full backup of 3+ partitions prior to making changes. I had to revert to a backup on 20th as had 2x SED processes going nuts. Titanium backup'd all important stuff. Then rebooted to Micro SD TWRP and did 3 Partitions (leaving int. storage intact). So Rooting is essential. It really is. Plus using Magisk is even more important, as it does not make modifications to /System which makes life much easier upgrading/troubleshooting/debugging et al.
NOTE: I would infact backup all the data on that ext. drive, delete partitions and create 2 FAT32/EXFAT/NTFS for redundancy. I have had too many past issues with partitions getting corrupt on external drives.
1. Backup Boot partition, 2. Extract the backup and find the boot.img, 3. Install Magisk Manager, click Install and select option 2 and browse for the boot.img, 4. Flash updated /MagiskManager/boot.img via TWRP and you are rooted w/ Systemless SU and BusyBox. There is seriously nothing better than having Root and being Play "Certified". You won't look back! Plus you can always re-flash the stock Boot.img and do OTA manufacturer updates, then open Magisk Manager and repeat.
Mac is like that. You can only read NTFS drives, but read / write to stupid HFS/HPFS drives with Mac, unless you install something like Paragon to read NTFS. The same for Windows, can read HFS+ but read/write NTFS.
Every Android device, regardless of OS, is totally different. Different Kernel's, different builds, ...
Good luck and let me know how you go?
Cheers mate!
Click to expand...
Click to collapse
Ok so ive been on Samsung for the last 5-6 years and never had to backup things like boot.img, recovery.img cuz we have have odin, so there was never any need to...... so i just did a google search on how to do this but it only brings up ways to do it with root. Can you explain how to do this or link to a tut?
Also could i get a more in depth of using Magisk? I have it on my HTC M7 but i rarely ever play around with it... actually im root with SU on it. So i have to run Magisk on my MX10.. search for boot.img.. patch it.. flash some zip in twrp.. and how do i get twrp on the box.. through adb? I should know this as long as ive been rooting but root on U.S. snapdragon samsung phones is totally different since the bootloader cant be unlocked. Thanks for your info so far bro
Post redundant.
flipmode_11 said:
Did you see my questions?
Where did you source your device from? Ebay? Online? Retail?
What software and steps above did you try?
Did you try the Paragon app with Total Commander?
Did you try downloading the recovery.img linked in the Media TV Box category? https://forum.xda-developers.com/showthread.php?p=75644464
Using Magisk is even more important these days as developers attempt to detect SU/Root, plus Magisk does not make modifications to your /System partition which makes life MUCH easier upgrading / troubleshooting / debugging and allows you to mask Root/SuperUser to then use all apps (Spotify, Play, Netflix, Stan, et al.)
Click to expand...
Click to collapse
I got my box from Amazon. Ive not tried anything with it yet. I dont use Total Commander.. that was another guy saying something about it and wanting to be able to write to external sd... i could care less for that. I want root for adaway and a few other things. Im using Blockada right now to block ads but i cant use it and Expressvpn at the same time.. so my choices are either block ads or run vpn to be anonymous.. cant do both because you cant run two vpns at the same time in android and blockada's vpn is not the same kind of vpn.
Ok i just read your thread.. i will give it a try sometime this weekend maybe.
Ya know the weird thing is is that DevCheck says i have root and busybox installed. Su app is there but say su binaries arent installed. I dont get why this box is shipped like this. lol
You are funny! I was talking to @RADiuMOz - I had quoted him.
No wonder your reply made no sense. Then my reply made no sense.
Please see my topic on AMLogic devices "AMLogic S905 S912 FAQ ✰ Fix Root, Switch SU, Backup/Restore etc ✩ Media Player TV Box" here: https://forum.xda-developers.com/an...mlogic-s905x-s912x-faq-backup-switch-t3752897
I would suggest you follow the steps to Backup first as it does not make any changes to your system.
Then follow steps to Root (download 3 files) and proceed with the FAQ I have written on how to root and which of the 3 methods suit you (probably the one similar to Part 1 of the backup, plus flashing the ZIP.
I had similar corrupt Root issue where SU and SUD were present, but didn't appear to have permissions. Some apps reported Root OK, and others No Root.
Anyway, let me know how you go. I have documented how to un-root / clean-up and then to re-root your system (i.e. Corrupt Root). Reply there.
Cheers!
p.s. May I suggest you check out AdGuard instead of AdAway? It lets you subscribe to block lists, plus you can set-up DUAL VPN's with it (read their KB/FAQ's). AdGuard's menu's allows you to accomodate both being able to VPN and run adblocking at the same time - ROOT Free. So you can probably ignore everything I have even said! LOL (AdGuard > Left Menu > Settings > Proxy Settings)
VyprVPN is far better and I suggest you try them when they have a promo. You can enable an option to block malicious servers, etc. But no way of managing this and adding adverts. Anyway, I switched and tried various VPN providers and found VyprVPN far better, plus offer a higher level of OpenVPN encryption which is not blocked or detected by 3rd parties called "Chameleon".
freak69ize said:
I got my box from Amazon. I want root for AdAway and a few other things. Im using Blockada right now to block ads but i cant use it and ExpressVPN at the same time.. so my choices are either block ads or run vpn to be anonymous.. cant do both because you cant run two vpns at the same time in android and blockada's vpn is not the same kind of vpn.
Ok i just read your thread.. i will give it a try sometime this weekend maybe.
Ya know the weird thing is is that DevCheck says i have root and busybox installed. Su app is there but say su binaries arent installed. I dont get why this box is shipped like this. lol
Click to expand...
Click to collapse
EXPERIMENT: Has anyone tried an OTG adapter in the USB-C slot for a Galaxy S8? Then connect a small USB drive with a recovery.img only, formatted in FAT32? You could even try placing the recovery.img on your Micro SD inside your phone...? Perhaps while holding down menu + up or menu + down, switch on your phone, and it might read the recovery.img on the external memory and boot into that?
*Anyway*, try the same thing in your MX10 and report back add success. Use a compatible S905 TWRP recovery.img (see my type here with download attached and tested with S905x Devices.
Hmm... So many ideas... so many things I have not tried!
freak69ize said:
Hey bud if you hold the power button down on the remote for about 5 seconds and it will bring the reboot menu up.. it has shut down and restart. Do the same to boot up
Ok.. everyone else that was wondering about root.. looks like this is our answer.. no root.. no TWRP...... for now at least. This box is still fairly new so im not giving up. It took 4-5 months for them to get root for Snapdragon S8 so who knows.. it may come for the MX10 one day too
View attachment 4436137
Click to expand...
Click to collapse
flipmode_11 said:
G'day mate,
Yeah look just give it a try and see how you go. Booting to this recovery.img will not make any modifications. It is simply loading an interface and relevant dependencies for it to run. I read something about how RockChip devices are limited or something. I forget now, but that made me steer clear of them, despite having more regular updates and new hardware. :/ hmmm
No, you won't find a matching device. It is shocking that these mass-manufacturered generic devices aren't also listed. I recommend you give the recovery.img in my topic a stab.
Where did you source you MX10 from? Have you asked them? Although, every single Chinese seller I have come across has zero working knowledge or which models are better, plus have 101 mistakes in their specs (just got a $50 and $100 refund on Ebay for X96 and a 10.1" tablet! Wrong specs!).
NTFS? So it can READ but not WRITE? Hmm I would wipe everything in FAT32 for Android. Everything is much happier. You could try exFAT which is a superior file system. Have you tried this? Got any other ExFAT + FAT32 devices? Hmm actually I think I've been down that path with exFAT (Paragon tools to solve). Double check exFAT compatibility before proceeding with backup/wipe/re-format. Actually I know the Nexus 6 was able to read NTFS storage as helped a mate with one. But depends on the manufacturer! But the Nexus6 couldn't write to HPFS - never tested exFAT. I think there is an app - USB Media Exporter...? USB Media Explorer..? - I forget!?!
As you mentioned Total Commander, you could try it with the Paragon tool plug-in: https://play.google.com/store/apps/details?id=com.paragon.tcplugins_ntfs_ro -or- https://play.google.com/store/apps/details?id=com.paragon.mounter (not tried this, but images looks interesting - free!). I use Solid Explorer + Smart File Manager - never been a fan of TC... There are other methods out there, but they require Root, which will not help you! e.g. ChainFire's StickMount.
No, I think you should proceed. However, as per my topic, take a full backup of 3+ partitions prior to making changes. I had to revert to a backup on 20th as had 2x SED processes going nuts. Titanium backup'd all important stuff. Then rebooted to Micro SD TWRP and did 3 Partitions (leaving int. storage intact). So Rooting is essential. It really is. Plus using Magisk is even more important, as it does not make modifications to /System which makes life much easier upgrading/troubleshooting/debugging et al.
NOTE: I would infact backup all the data on that ext. drive, delete partitions and create 2 FAT32/EXFAT/NTFS for redundancy. I have had too many past issues with partitions getting corrupt on external drives.
1. Backup Boot partition, 2. Extract the backup and find the boot.img, 3. Install Magisk Manager, click Install and select option 2 and browse for the boot.img, 4. Flash updated /MagiskManager/boot.img via TWRP and you are rooted w/ Systemless SU and BusyBox. There is seriously nothing better than having Root and being Play "Certified". You won't look back! Plus you can always re-flash the stock Boot.img and do OTA manufacturer updates, then open Magisk Manager and repeat.
Mac is like that. You can only read NTFS drives, but read / write to stupid HFS/HPFS drives with Mac, unless you install something like Paragon to read NTFS. The same for Windows, can read HFS+ but read/write NTFS.
Every Android device, regardless of OS, is totally different. Different Kernel's, different builds, ...
Good luck and let me know how you go?
Cheers mate!
Click to expand...
Click to collapse
First up - sorry mate - I actually thought I'd replied to your post, but clearly either didn't submit it, or just dreamed the whole thing.
I have to wait for free time at the weekends (I have kids), but I'll go back to your topic and give that a go.
As for NTFS, etc. I ended up buying a Synology DS218J NAS box as I want my daughter to be able to back up her MacBook to it, as well as probably back up some of my stuff to it as well - and of course then use for the MX10. I bought it from GeekBuying, and they're not that particularly helpful. Not intentionally unhelpful, though.
My MXIII-G was great for just working straight out of the box, with the external NTFS drive (exact same drive).
So now, as for rooting, my only reason will be so I can remap some of the keys on my remote - but don't absolutely have to do that. But I'll do backups anyway, so that I'm ready for if/when any firmware updates come out.
I'll certainly know to have a MUCH better look round, before buying my next Android TV box, though - that's for sure. I did a quick search, but didn't find anything on a user level - but also didn't search XDA: just did a regular Google search.
Thanks for your detailed reply, as I know it takes time and thought on your part - it's much appreciated. As soon as I've got something to report, I'll post in the same thread, so other people can perhaps benefit from my findings.
Cheers,
Richard.
---------- Post added at 08:52 PM ---------- Previous post was at 08:48 PM ----------
flipmode_11 said:
G'day mate,
Yeah look just give it a try and see how you go. Booting to this recovery.img will not make any modifications. It is simply loading an interface and relevant dependencies for it to run. I read something about how RockChip devices are limited or something. I forget now, but that made me steer clear of them, despite having more regular updates and new hardware. :/ hmmm
No, you won't find a matching device. It is shocking that these mass-manufacturered generic devices aren't also listed. I recommend you give the recovery.img in my topic a stab.
Where did you source you MX10 from? Have you asked them? Although, every single Chinese seller I have come across has zero working knowledge or which models are better, plus have 101 mistakes in their specs (just got a $50 and $100 refund on Ebay for X96 and a 10.1" tablet! Wrong specs!).
NTFS? So it can READ but not WRITE? Hmm I would wipe everything in FAT32 for Android. Everything is much happier. You could try exFAT which is a superior file system. Have you tried this? Got any other ExFAT + FAT32 devices? Hmm actually I think I've been down that path with exFAT (Paragon tools to solve). Double check exFAT compatibility before proceeding with backup/wipe/re-format. Actually I know the Nexus 6 was able to read NTFS storage as helped a mate with one. But depends on the manufacturer! But the Nexus6 couldn't write to HPFS - never tested exFAT. I think there is an app - USB Media Exporter...? USB Media Explorer..? - I forget!?!
As you mentioned Total Commander, you could try it with the Paragon tool plug-in: https://play.google.com/store/apps/details?id=com.paragon.tcplugins_ntfs_ro -or- https://play.google.com/store/apps/details?id=com.paragon.mounter (not tried this, but images looks interesting - free!). I use Solid Explorer + Smart File Manager - never been a fan of TC... There are other methods out there, but they require Root, which will not help you! e.g. ChainFire's StickMount.
No, I think you should proceed. However, as per my topic, take a full backup of 3+ partitions prior to making changes. I had to revert to a backup on 20th as had 2x SED processes going nuts. Titanium backup'd all important stuff. Then rebooted to Micro SD TWRP and did 3 Partitions (leaving int. storage intact). So Rooting is essential. It really is. Plus using Magisk is even more important, as it does not make modifications to /System which makes life much easier upgrading/troubleshooting/debugging et al.
NOTE: I would infact backup all the data on that ext. drive, delete partitions and create 2 FAT32/EXFAT/NTFS for redundancy. I have had too many past issues with partitions getting corrupt on external drives.
1. Backup Boot partition, 2. Extract the backup and find the boot.img, 3. Install Magisk Manager, click Install and select option 2 and browse for the boot.img, 4. Flash updated /MagiskManager/boot.img via TWRP and you are rooted w/ Systemless SU and BusyBox. There is seriously nothing better than having Root and being Play "Certified". You won't look back! Plus you can always re-flash the stock Boot.img and do OTA manufacturer updates, then open Magisk Manager and repeat.
Mac is like that. You can only read NTFS drives, but read / write to stupid HFS/HPFS drives with Mac, unless you install something like Paragon to read NTFS. The same for Windows, can read HFS+ but read/write NTFS.
Every Android device, regardless of OS, is totally different. Different Kernel's, different builds, ...
Good luck and let me know how you go?
Cheers mate!
Click to expand...
Click to collapse
Apologies! I thought I'd replied, here, but clearly didn't submit it, or just dreamed I had. I've replied to your PM, but also for anyone/everyone else's benefit (and in brief), I bought my MX10 from GeekBuying. I just bought a NAS box, so I'm going to use that instead of trying to get NTFS working, although the people at GeekBuying said, "Our factory tests show that the MX10 can read and write ntfs hard drives. So please try again." I'd be interested to hear whether anyone else is able to write to NTFS.
I'm going to go back to your topic, and give that a go - and will then post back here, to let everyone know (hopefully might benefit someone).
Cheers,
Richard.
i have mx10 and it suddenly stuck in start logo when i open,i dont have any idea please help.
i try to factory reset using toothpick and hit the factory reset no command coming out to delete all files and quick return to booth the system.
whwn i try to reboot again stuck in start logo i'll wait for 30 min but still just rounding the startup logo.Please help me...
Hey everyone!
I know that one of the biggest barriers for completely ditching my MacBook Pro for my Pixelbook was the ability to use ADB and fastboot (upgrading Android versions, flashing TWRP, factory resetting). ADB and fastboot are installed on later versions of Chrome OS; unfortunately, these versions are too old for devices like the Pixel 2 (XL) and there isn't a ton of information on how to get them updated and working properly.
As such, I created an installation script that will push the latest versions of the platform tools to the local binary directory and install a small wrapper script so you can use the commands as you normally would. The scripts should be fairly easy to read if you have a basic understanding of the command line, I have commented them so it's clear what is going on.
The installation script can be used to install the tools for the first time as well as upgrading to newer version as they come out. The changelog for each version can be found here.
Please see the README for the full instructions and let me know if you have any questions, enjoy!
On Chrome OS Canary version 69 on an ARM CPU, ADB and Fastboot are both installed by default.
zarthan said:
On Chrome OS Canary version 69 on an ARM CPU, ADB and Fastboot are both installed by default.
Click to expand...
Click to collapse
Do they actually work? They were installed on my Chromebook Plus out of the box but they are too outdated for my Pixel 2 XL.
Will this work in Acer c720p, or is it too old? If not what about Samsung Chromebook pro? Would it have to be in developer mode?
firegoblin said:
Will this work in Acer c720p, or is it too old? If not what about Samsung Chromebook pro? Would it have to be in developer mode?
Click to expand...
Click to collapse
In theory, it should work for both.
Please see the README as it answers the second question.
nathanchance said:
In theory, it should work for both.
Please see the README as it answers the second question.
Click to expand...
Click to collapse
Dear lord my c720p has a purpose now. Thank you! ChromeOS ftw
nathanchance said:
In theory, it should work for both.
Please see the README as it answers the second question.
Click to expand...
Click to collapse
Do you know if there is anyway to run a shell directly from the downloads folder in ChromeOS? I couldn't get fastboot to function properly.
firegoblin said:
Do you know if there is anyway to run a shell directly from the downloads folder in ChromeOS? I couldn't get fastboot to function properly.
Click to expand...
Click to collapse
Going to have to give me more details, like the stuff I request in the README.
Sent from my Pixel 2 XL using XDA Labs
nathanchance said:
Do they actually work? They were installed on my Chromebook Plus out of the box but they are too outdated for my Pixel 2 XL.
Click to expand...
Click to collapse
fastboot doesn't report version but adb is 1.32 which is old. I don't know how recent adb was added to Chrome OS but I am sure I have used them in the past. I have lived in Canary for the last 2 years so I have no idea whether it was a Canary thing or widely available within developer mode.
Another option since you are in developer mode is Crouton and install a fullish version of Linux. adb does work within a Crouton session. Even if I was to update the version installed in Chrome OS, I would need to reinstall it every day since Canary is updated daily and sometimes two or three times a day. Even stable can be updated mid-cycle so you could get caught with the outdated one at an inopportune time.
zarthan said:
fastboot doesn't report version but adb is 1.32 which is old. I don't know how recent adb was added to Chrome OS but I am sure I have used them in the past. I have lived in Canary for the last 2 years so I have no idea whether it was a Canary thing or widely available within developer mode.
Another option since you are in developer mode is Crouton and install a fullish version of Linux. adb does work within a Crouton session. Even if I was to update the version installed in Chrome OS, I would need to reinstall it every day since Canary is updated daily and sometimes two or three times a day. Even stable can be updated mid-cycle so you could get caught with the outdated one at an inopportune time.
Click to expand...
Click to collapse
For me personally, I bought a Chromebook for Chrome OS, not the hardware, so Crouton wasn't really an option.
You don't need to reinstall these as they are in /usr/local/bin so they're not touched during a Chrome OS upgrade.
I don't think I understand "Crouton wasn't really an option". Crouton is a simple script that installs various versions of Linux desktops that run alongside Chrome in a chroot. Probably any Chromebook made can install Crouton. The only thing required is to be in developer mode, which you are. I choose to run my sessions in a tab but it can be a separate window. Not much you can't install and run in these sessions.
zarthan said:
I don't think I understand "Crouton wasn't really an option". Crouton is a simple script that installs various versions of Linux desktops that run alongside Chrome in a chroot. Probably any Chromebook made can install Crouton. The only thing required is to be in developer mode, which you are. I choose to run my sessions in a tab but it can be a separate window. Not much you can't install and run in these sessions.
Click to expand...
Click to collapse
Would help if I actually did proper research into Crouton :silly:thanks for the clarification, I'll have to check it out soon
Crouton was developed by a Google employee. You can create a pretty complete development environment. An i7 and 16 GB RAM are becoming more and more appealing.
zarthan said:
Crouton was developed by a Google employee. You can create a pretty complete development environment. An i7 and 16 GB RAM are becoming more and more appealing.
Click to expand...
Click to collapse
Ended up trying it yesterday, I'm a big fan so far. Will continue to explore it, thanks for the tip!
nathanchance said:
Ended up trying it yesterday, I'm a big fan so far. Will continue to explore it, thanks for the tip!
Click to expand...
Click to collapse
http://skycocker.github.io/chromebrew/
If you mainly just want command line to install packages.
There is also chromebrew, almost a chromeos version of homebrew on mac.
Hello!
First off I would like to thank you very much for making this installation script! I've been waiting the whole time since I bought my Chromebook about 3 weeks ago for somebody to post a script to install ADB/fastboot since the recent added support of the 2 to ChromeOS. ADB/fastboot support is the entire reason why I bought this Chromebook, if it did not have it, I would of been stuck buying a Windows laptop. I was really excited when I read they just added support recently for ADB/fastboot! I have a couple of small problems and if anybody can help me out, it will be greatly appreciated.
1. I cannot get ADB to work yet on my Pixel 2 XL, but fastboot works no problem. When I try to use ADB, it says device is "offline". Sometimes it says "unauthorized" when I've accepted permissions and click 'always allow from this computer' etc etc. Do I have to use a root shell to run adb/fastboot or can i use a regular shell like on my old windows laptop? Do i have to use sudo before every single command as well or just 'adb devices' like I would on a windows. I know these are noob questions but it is because I am a noob and have only used ADB/fastboot on a WIndows 7 laptop before this.
2. My other question is when I powerwashed and it booted to the user sign in screen, I tried to click enable debugging features but it said not all of the features could of been enabled. Wth does that mean? How can I fix it? Does the chromebook stay in developer mode after I powerwash it if it was in dev mode before I powerwashed it? I did return it back to the dev channel after the powerwash bc I noticed it was back on stable.
Do I have to install a custom version of Chromium OS before this will work?
Thank you guys so much, and thanks again @nathanchance for making this script. Also thanks for your Pixel 2 XL kernel, I use that as well. Cheers!
My device is the Acer Chromebook R11 .. 32 GB HD / 4 GB RAM with a 64 GB sdcard in it .. 2 in 1 tablet/laptop .. x86_64
ok so how do I copy the files I downloaded to another directory? The chrome files explorer only shows drive and downloads
Nathan
Will you be building your own kernel and or system images for pixelbook?
smartymcfly said:
Nathan
Will you be building your own kernel and or system images for pixelbook?
Click to expand...
Click to collapse
No. The entire reason I got a Pixelbook is so that I could have a super stable local device and do all my heavy computing on a remote server.
nathanchance said:
Hey everyone!
I know that one of the biggest barriers for completely ditching my MacBook Pro for my Pixelbook was the ability to use ADB and fastboot (upgrading Android versions, flashing TWRP, factory resetting). ADB and fastboot are installed on later versions of Chrome OS; unfortunately, these versions are too old for devices like the Pixel 2 (XL) and there isn't a ton of information on how to get them updated and working properly.
As such, I created an installation script that will push the latest versions of the platform tools to the local binary directory and install a small wrapper script so you can use the commands as you normally would. The scripts should be fairly easy to read if you have a basic understanding of the command line, I have commented them so it's clear what is going on.
The installation script can be used to install the tools for the first time as well as upgrading to newer version as they come out. The changelog for each version can be found here.
Please see the README for the full instructions and let me know if you have any questions, enjoy!
Click to expand...
Click to collapse
Hi Nathan,
I also have a Chromebook plus which is not x86_64. Have you written a script compatible with the Chromebook plus?
Thank you for all your contributions to the community!
-Dan
I published a script that can automatically resign GrapheneOS OTAs with your own keys, and also optionally apply a few modifications like enabling ADB root (without turning on ro.debuggable), ignoring allowbackup and changing the update URL.
You can use it if you like GrapheneOS (I think it's the Android OS with the best engineering, security and privacy), but would also like to have full control of your device, by controlling the verified boot keys of your device and applying modifications that make the OS do what you want regardless of what upstream OS developers, app developers, or anyone else might want.
Note that, on the other hand, GrapheneOS follows the Google Android security model which says that the OS will not perform an action you want it to perform if it may result in something that "application developers, content producers, service providers, and employers" do not consent to (which means not letting you have root, or ignore app wishes regarding backups and other settings, or send arbitrary responses to app requests, etc.), while this script will let you do what you want with your own device regardless of whether it's in anyone else's interest or not, including things that this script does not itself support since you control the verified boot keys of the device and can thus sign anything; all this while still taking advantage of all the security and privacy features in GrapheneOS, including verified boot.
You can find it at https://github.com/chriswoope/resign-android-image
Currently it's intended for people with good technical knowledge, although once you set it up (if you run Qubes a lot of steps are automated) it should continue working with no or minimal intervention.
Thank you very much for this
Hi, do you still update your tools? I've changed quite some things while traing to get this running for a Pixel 7....
I had to adept quite some changes (e.g. for init_boot on A13 shipped device, incresed HeapSize for Java, as SmailPatcher crashes, problems while generating keys with signify-openbsd and also missing tools like zip and unzip on a fresh installed debian), but in the end I received a nice zip which I've flahsed to the device, but I ended up in a Bootloop (Google Logo, Graphene Logo, some seconds and then.. reboot).
So, did someone got this running with A13 (and at best also on a Pixel 7)?
pmatj said:
Hi, do you still update your tools? I've changed quite some things while traing to get this running for a Pixel 7....
I had to adept quite some changes (e.g. for init_boot on A13 shipped device, incresed HeapSize for Java, as SmailPatcher crashes, problems while generating keys with signify-openbsd and also missing tools like zip and unzip on a fresh installed debian), but in the end I received a nice zip which I've flahsed to the device, but I ended up in a Bootloop (Google Logo, Graphene Logo, some seconds and then.. reboot).
So, did someone got this running with A13 (and at best also on a Pixel 7)?
Click to expand...
Click to collapse
I was not able to get this working myself unfortunately
but using a different script called AVBRoot and using it on a self built build of GrapheneOS I am able to lock the bootloader with Magisk Root
I have created this guide to help people https://forum.xda-developers.com/t/...-using-rooted-grapheneos-magisk-root.4510295/
pmatj said:
Hi, do you still update your tools? I've changed quite some things while traing to get this running for a Pixel 7....
I had to adept quite some changes (e.g. for init_boot on A13 shipped device, incresed HeapSize for Java, as SmailPatcher crashes, problems while generating keys with signify-openbsd and also missing tools like zip and unzip on a fresh installed debian), but in the end I received a nice zip which I've flahsed to the device, but I ended up in a Bootloop (Google Logo, Graphene Logo, some seconds and then.. reboot).
So, did someone got this running with A13 (and at best also on a Pixel 7)?
Click to expand...
Click to collapse
Hey, did you ever get this working on Pixel 7?
User.Hemlock said:
Hey, did you ever get this working on Pixel 7?
Click to expand...
Click to collapse
You can use AVBRoot to patch and sign roms to get root with a locked boot loader using GrapheneOS
I wrote a guide here https://forum.xda-developers.com/t/...-using-rooted-grapheneos-magisk-root.4510295/
FireRattus said:
You can use AVBRoot to patch and sign roms
Click to expand...
Click to collapse
Thanks! Haven't had a chance to dig into AVBroot yet, but I'm guessing the patching capability would include things like ignoring allowbackup? (that was one of OP's features that I was interested in)
User.Hemlock said:
Thanks! Haven't had a chance to dig into AVBroot yet, but I'm guessing the patching capability would include things like ignoring allowbackup? (that was one of OP's features that I was interested in)
Click to expand...
Click to collapse
The main purpose of AVBRoot is to root and sign an image so that with pixel devices for example you can lock the bootloader and have root
With root you can achieve ignoring the allowbackup, I believe you could do this with xposed
I also just use root apps like Swift Backup to backup everything on my device