First of all: Tools to be used in this guide were developed by user And_pda from Russian 4pda.ru forum. So all credits must go to And_pda
The original thread (in Russian) is here. Actually the original thread is about several tools to works with different images for different phones. But we will talk only about Moto G.
The guide will describe how to extract all files from system partition from stock firmware. The tools works under Windows (I personally tested them on Win 7).
If you unzip any stock firmware (for instance RETAIL-GB_4.4.2_KLB20.9-1.10-1.9_cid7_CFC_1FF_v5_SVC.xml.zip) you will find 3 files, which represents system partition: system.img_sparsechunk.0, system.img_sparsechunk.1 and system.img_sparsechunk.2.
There are two steps to be performed to get system file extracted.
Step 1 - it will convert 3 files (system.img_sparsechunk.0, 1, 2) into temporary file system_motog.img:
1. Download RKwinToolsMod_v2_8.rar and extract it.
Lets assume that it is extracted to D:\RKwinToolsMod_v2_8. If not you have to modify ConvertMotoG.bat file located in Scripts folder.
You have to edit the string set wf=D:\RKwinToolsMod_v2_8\Cygwin\ according to path where you extracted archive.
2. Copy ConvertMotoG.bat to the folder where stock firmware is unzipped (i.e. where system.img_sparsechunk.0, system.img_sparsechunk.1 and system.img_sparsechunk.2 are lockated)
3. Run CMD and "cd" to the folder where where stock firmware is unzipped
4. In CMD run ConvertMotoG.bat. File system_motog.img will be created.
Step 2 - it will extract all files and folders from system_motog.img:
1. Download ImgExtractor_1_3_4.rar and extract it.
2. Create directory System in the folder where system_motog.img is located;
3. Copy ImgExtractor.exe into the folder where system_motog.img is located;
4. Run CMD and "cd" to the folder where system_motog.img is located
5. In CMD run the following: ImgExtractor system_motog.img System
After ImgExtractor finished you will have all system files and folders in System directory.
That's all
PS. ImgExtractor also can extract modem firmware (NON-HLOS.bin)
Thanks for this. I was looking for a method to do this not too long ago and had no luck.....Thanks again!
Sent from my Moto G using XDA Premium 4 mobile app
romuloxiii said:
Thanks for this. I was looking for a method to do this not too long ago and had no luck.....Thanks again!
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Anyone made a working CWM installer yet of a ROM that I can tweak like in the old pixelrom days ?
I have a ROM ready and some init.d startup scripts but my installer script is lacking and needing lots of work.
i double clicked the convertmotog.bat but nothing happened
Confirmed working here. Make sure you set path in the copied batch file and followed all steps of the instructions.
Sent from my XT1032 using Tapatalk
wildestpixel said:
Confirmed working here. Make sure you set path in the copied batch file and followed all steps of the instructions.
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
i get this and nothing more, am i suppose to wait or anything?
Create system_motog.img Please wait...
Press any key to continue . . .
Working here too. Thanks a lot for the guide!! :good:
Nandeh said:
Working here too. Thanks a lot for the guide!! :good:
Click to expand...
Click to collapse
for some reason i cannot use the convertmotog.bat can you send me the unpacked file?
gwiqu said:
for some reason i cannot use the convertmotog.bat can you send me the unpacked file?
Click to expand...
Click to collapse
Here we go. Simply delete the last file extension .txt
My question hopefully someone knows how to recreate sparsechunks from system. IMG ?
Sent from my Nexus 7 using Tapatalk
wildestpixel said:
My question hopefully someone knows how to recreate sparsechunks from system. IMG ?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Why not just simply redownload the firmware zip? I think that recreate sparsechunk parts won't be easy...
Nandeh said:
Why not just simply redownload the firmware zip? I think that recreate sparsechunk parts won't be easy...
Click to expand...
Click to collapse
That's not what I'm trying to achieve. I wanted to make a fastboot flashable ROM with root and busybox.
Sent from my Nexus 7 using Tapatalk
wildestpixel said:
That's not what I'm trying to achieve. I wanted to make a fastboot flashable ROM with root and busybox.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Ok, then you don't need to divide the system.img into parts, you can flash it directly with fastboot:
fastboot flash system system.img
Nandeh said:
Ok, then you don't need to divide the system.img into parts, you can flash it directly with fastboot:
fastboot flash system system.img
Click to expand...
Click to collapse
If it were that easy I would have done it! File system limits flash chunks to c. 512MB so sparsechunks are required.
Sent from my Nexus 7 using Tapatalk
wildestpixel said:
My question hopefully someone knows how to recreate sparsechunks from system. IMG ?
Click to expand...
Click to collapse
I have asked tools developer about recreating sparsechunks - he is not going to make such tool.
Another point. If your bootloader is locked you will not able to flash recreated sparsechunks.
wildestpixel said:
If it were that easy I would have done it! File system limits flash chunks to c. 512MB so sparsechunks are required.
Click to expand...
Click to collapse
There are following fastboot options:
-P enable parallel loading for multi-flash if there is no enough memory on host to load whole image
-S <size>[K|M|G] automatically sparse files greater than size. 0 to disable
Have you tried it to flash not divided system.img ?
Hi, I have problem with "Step 1"...
When I run ConvertMotoG.bat, it does nothing
Windows 8.1 x64
Ja_som said:
Hi, I have problem with "Step 1"...
When I run ConvertMotoG.bat, it does nothing
Windows 8.1 x64
Click to expand...
Click to collapse
hard to tell from the screenshot, but my guess is you need to rename your sparsechunk files. if they are named system.img_sparsechunk1 you need to change them to system.img_sparsechunk.1 for the BAT file to work.
make sure to rename each file: system.img_sparsechunk.1 system.img_sparsechunk.2 system.img_sparsechunk.3 ... etc
hope that helps/works
cedarknoll said:
hard to tell from the screenshot, but my guess is you need to rename your sparsechunk files. if they are named system.img_sparsechunk1 you need to change them to system.img_sparsechunk.1 for the BAT file to work.
make sure to rename each file: system.img_sparsechunk.1 system.img_sparsechunk.2 system.img_sparsechunk.3 ... etc
hope that helps/works
Click to expand...
Click to collapse
Thank you, now is everything OK
cedarknoll said:
hard to tell from the screenshot, but my guess is you need to rename your sparsechunk files. if they are named system.img_sparsechunk1 you need to change them to system.img_sparsechunk.1 for the BAT file to work.
make sure to rename each file: system.img_sparsechunk.1 system.img_sparsechunk.2 system.img_sparsechunk.3 ... etc
hope that helps/works
Click to expand...
Click to collapse
I was just going to post it as i figured it out, but nice find though, if i had read it it would've saved a lot of time hahaha
And btw thanks a lot to the OP, really useful
cedarknoll said:
hard to tell from the screenshot, but my guess is you need to rename your sparsechunk files. if they are named system.img_sparsechunk1 you need to change them to system.img_sparsechunk.1 for the BAT file to work.
make sure to rename each file: system.img_sparsechunk.1 system.img_sparsechunk.2 system.img_sparsechunk.3 ... etc
hope that helps/works
Click to expand...
Click to collapse
i get this
D:\RK\Scripts>ConvertMotoG.bat
Create system_motog.img Please wait...
'D:\RK\Cygwinsparse2img' is not recognized as an internal or external command,
operable program or batch file.
'D:\RK\Cygwinsparse2img' is not recognized as an internal or external command,
operable program or batch file.
'D:\RK\Cygwinsparse2img' is not recognized as an internal or external command,
operable program or batch file.
Press any key to continue . . .
what do i do?
edit: nvm i got it
Related
Hi all :
I try open all CGs for see the files, but i only know to open CG39 and some more..
sudo mount -o loop CG.39.smg CG39
But the others ¿¿
Some one have the answer ¿?¿?¿?
There is a Perl script which can unpack boot and recovery (CG35 & CG47) in this thread: http://forum.xda-developers.com/showthread.php?t=443994
Filipitripi said:
Hi all :
I try open all CGs for see the files, but i only know to open CG39 and some more..
sudo mount -o loop CG.39.smg CG39
But the others ¿¿
Some one have the answer ¿?¿?¿?
Click to expand...
Click to collapse
CG64.smg & CG65.smg: partition tables that you can open using fdisk/sfdisk
CG33.smg is a CDROM ISO file!
iirc one or two of them are the splash image (not 100% sure now)
Filipitripi said:
Hi all :
I try open all CGs for see the files, but i only know to open CG39 and some more..
sudo mount -o loop CG.39.smg CG39
But the others ¿¿
Some one have the answer ¿?¿?¿?
Click to expand...
Click to collapse
how to repack cg39.smg
if you have any details on windows 7 how to open repack do send me.
rachit2588 said:
how to repack cg39.smg
if you have any details on windows 7 how to open repack do send me.
Click to expand...
Click to collapse
http://sourceforge.net/projects/ext... 2.2 (Latest)/ext2explore-2.2.71.zip/download
It will allow you opening ext3 images inside Windows
^very good idea
danimagrin said:
http://sourceforge.net/projects/ext... 2.2 (Latest)/ext2explore-2.2.71.zip/download
It will allow you opening ext3 images inside Windows
Click to expand...
Click to collapse
so now i can see files on cg39.smg using ext2reader but the thing is now how to get system image from cg39.smg to system.img ??
rachit2588 said:
so now i can see files on cg39.smg using ext2reader but the thing is now how to get system image from cg39.smg to system.img ??
Click to expand...
Click to collapse
System.img to be restored with Nandroid? If yes you have to extract all files with ext2reader then use mkyaffs2image to build system.img.
danimagrin said:
System.img to be restored with Nandroid? If yes you have to extract all files with ext2reader then use mkyaffs2image to build system.img.
Click to expand...
Click to collapse
with mkyaffs2image its jus showing me a cmd windows for some less thn 1 sec and its jus goes away...please upload the version you are using...also let me know if it needs any prerequisite software to be installed.
It's because mkyaffs2image is a command line app, just like in the DOS days... To use it you should open a cmd window (type cmd at Windows menu and press enter), go to the directory right before the one you extracted files (you use cd "dirname" to enter in a directory and "cd .." to leave it. So when you are in the directory right before the one in which you've extracted files type "mkyaffs2image CG39extracteddir system.img"
danimagrin said:
It's because mkyaffs2image is a command line app, just like in the DOS days... To use it you should open a cmd window (type cmd at Windows menu and press enter), go to the directory right before the one you extracted files (you use cd "dirname" to enter in a directory and "cd .." to leave it. So when you are in the directory right before the one in which you've extracted files type "mkyaffs2image CG39extracteddir system.img"
Click to expand...
Click to collapse
oh , ok.. its working..thanks
danimagrin said:
It's because mkyaffs2image is a command line app, just like in the DOS days... To use it you should open a cmd window (type cmd at Windows menu and press enter), go to the directory right before the one you extracted files (you use cd "dirname" to enter in a directory and "cd .." to leave it. So when you are in the directory right before the one in which you've extracted files type "mkyaffs2image CG39extracteddir system.img"
Click to expand...
Click to collapse
ok last doubt...after creating system.img can it be restored via custom recovery..??
how to add md5 check sums for that so that custom recovery can identify as proper nandorid..!!??
rachit2588 said:
oh , ok.. its working..thanks
Click to expand...
Click to collapse
You welcome!
Sure you can use it with nandroid, you must download md5sum.exe, place it together with mkyaffs2image, after you used mkyaffs2image then type "md5sum system.img" and it will generate checksum. Create a file called "nandroid.md5" and paste what md5sum returned. You can open a nandroid.md5 file of another backup and you'll understand better how it's done..
excellent..i got it
@danimagrin help me how to add root files if our cg39 image is unrooted..??
ie how to manually add root files from some rooted cg39 image to some non rooted original image..which files and folders are required to add/replace..?? ne thoughts..
rachit2588 said:
@danimagrin help me how to add root files if our cg39 image is unrooted..??
ie how to manually add root files from some rooted cg39 image to some non rooted original image..which files and folders are required to add/replace..?? ne thoughts..
Click to expand...
Click to collapse
I know how to do it on Linux, because you've to run chmod and chown to set su and Superuser.apk permissions. I'll see if it's possible to do it inside Windows and I'll answer you asap.
Where did you get mkyaffs2image for Windows? Are you running it with -f flag or not? Have you already made an image and restored it and did it really work? I'm afraid if will not work because of the same problem above...
danimagrin said:
I know how to do it on Linux, because you've to run chmod and chown to set su and Superuser.apk permissions. I'll see if it's possible to do it inside Windows and I'll answer you asap.
Where did you get mkyaffs2image for Windows? Are you running it with -f flag or not? Have you already made an image and restored it and did it really work? I'm afraid if will not work because of the same problem above...
Click to expand...
Click to collapse
yes i have made an system.img with md5 nandroid check sum...but still not restored with CWM Recovery...yeah mkyaffs2image works on windows...find out in the attached IMG depacker
rachit2588 said:
yes i have made an system.img with md5 nandroid check sum...but still not restored with CWM Recovery...yeah mkyaffs2image works on windows...find out in the attached IMG depacker
Click to expand...
Click to collapse
I'll test it as soon as I get home and then I tell you!
Hello !
I'm trying to set up a dual boot with Ubuntu and Android on my TF101.
I'm using Frank's Tool to do so.
I know i must have the boot.img the recovery.img and the system.img files, and that is the problem : i can't manage to dump my current ROM in img format. I tried with several Recoveries, but i just can't...
All i have in the best scenario is the following :
boot.img
recovery.img
system.ext4.dup
or :
boot.img
recovery.img
system.ext4.tar.a (400+ mb) and system.ext4.tar (0 kb)
Is there any way to grab the system.img from my current ROM, of am i forced to use the one provided in OLiFE Prime (which is fully stock... :crying: )
Many thanks in advance.
What file formats are the .img files? Linux doesn't care about the extension at the end like windows does. You could name the file dog_food.blah and linux is just as happy.
If you just need dumps of the partition, then the dd command will work for system. These will probably be ext4 filesystems.
What are the file types of the olife files that you want to change? From the linux command line, you can just type "file <some system.img here>" and it will tell you. I'm guessing it will say ext4 filesystem. Those tar files you have can probably be converted to what you need.
Disclaimer, I haven't dual booted my tablet and I don't know a thing about Frank's tools.
EDIT: I spent 30 seconds looking at Frank's tools, which appear to be an nvflash interface for windows. I suppose this means you want everything in an nvflash-able format. boot.img and recovery.img will be ANDROID! packed files, while system.img will be an ext4 filesystem.
To be sure, boot.img and recovery.img will start with ANDROID! There are also some boot tools by Rayman and other sources if you want to manipulate these. I think you can grab the system with "dd if=/dev/block/mmcblk0p1 of=/Removable/MicroSD/system.img" It will take a while and will be a large file, maybe 500MB. Depending on where your sdcard is, you might have to change that bit around.
If any of this doesn't make sense, then feel free to google or ask. Good luck!
Is there a way to mount or extract the files within the stock system.img (and other img files)?
i was trying to do this a few days ago and i found that somehow the system.img from the firmware was protected, i tried lots of programs but none worked, all marked an error. so i dont know what to do next.
Well, I ended up flashing the system.img file and then rebooting immediately into TRWP and taking a backup. From that I was able to copy it down and extract the contents. Kind of roundabout but it worked. If someone has a more direct method I'd like to know how it can be done.
Download ImgExtractor 1.3.4 by And_PDA (Program page here). To use, open a command prompt in the directory where ImgExtractor.exe and system.img are, and enter:
Code:
ImgExtractor.exe system.img System -i
where system.img is the file you're extracting and System is the folder it will extract all of the files to (it will create one if it doesn't already exist). The "-i" is optional, but it shows the individual files as they are extracted (verbose output), and is more fun to look at than an idle window.
See the readme or double click on ImgExtractor.exe for more usage info.
EDIT: Download is now linked to my DropBox and added with readme below.
Summersett said:
Download ImgExtractor 1.3.4 by And_PDA (Program page here). To use, open a command prompt in the directory where ImgExtractor.exe and system.img are, and enter:
Code:
ImgExtractor.exe system.img System -i
where system.img is the file you're extracting and System is the folder it will extract all of the files to (it will create one if it doesn't already exist). The "-i" is optional, but it shows the individual files as they are extracted (verbose output), and is more fun to look at than an idle window.
See the readme or double click on ImgExtractor.exe for more usage info.
EDIT: Download is now linked to my DropBox and added with readme below.
Click to expand...
Click to collapse
]
that worked perfectly, i'll attach that file because the russian page 404'd it, so i had to find it somewhere else.
its attached if anyone want it. thanks!
On my TF700T I'm currently running CyanogenMod version 11-20140805-SNAPSHOT-M9-tf700t. I currently have CWM Recovery 6.0.4.4
I want to return to a stock Asus ROM from their website.
I've tried flashing WW_epad-user-10.6.1.14.10.zip with CWM but get an error...
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /storage/sdcard1/WW_epad-user-10.6.1.14.10.zip
(Status 7)
Installation aborted.
What is it I'm doing wrong?
No thoughts?
I just tried commands from this thread, and I get error: cannot open 'blob' - yes the blob files was in the same folder as fastboot.
What cant I get this to work???
Bad download maybe?
sbdags said:
Bad download maybe?
Click to expand...
Click to collapse
I've downloaded the update 4-5 times... How big a deal is the different models? WW, TW, US??? I think it's WW, it was purchased in Australia.
Thanks for replying
When you tried to flash the zip from cwm did you unzip it first? I.e., flash the zip in the zip?
Other than that check the output of fastboot devices first.
sbdags said:
When you tried to flash the zip from cwm did you unzip it first? I.e., flash the zip in the zip?
Other than that check the output of fastboot devices first.
Click to expand...
Click to collapse
Yup I unzipped the download.
I'm running a Mac book pro, but running boot camp or OSX I still get 015d262e98340004 fastboot
typing fastboot reboot did reboot the tablet so fastboot and adb are working correctly.
FL00DY said:
I currently have CWM Recovery 6.0.4.4
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /storage/sdcard1/WW_epad-user-10.6.1.14.10.zip
Click to expand...
Click to collapse
IIRC the "staging" target doesn't work in CWM - don't remember about TWRP. But you can edit the updater-script and replace "staging" with "/dev/block/mmcblk0p4", that should work.
FL00DY said:
I get error: cannot open 'blob' - yes the blob files was in the same folder as fastboot.
Click to expand...
Click to collapse
That's a common mistake in many of the guides - the file must be in your *current* directory.
FL00DY said:
Yup I unzipped the download.
I'm running a Mac book pro, but running boot camp or OSX I still get 015d262e98340004 fastboot
typing fastboot reboot did reboot the tablet so fastboot and adb are working correctly.
Click to expand...
Click to collapse
Hmm I've never used a mac in my life so I can't help you any further. On a windows machine or linux the last thing to check is that the blob file is in the same folder but you already said that.
Can you run an md5sum on the zip file (I know you dl'ed it 5 times) just to confirm it is not getting corrupted....
Other than that I'm out of ideas - sorry.
_that said:
IIRC the "staging" target doesn't work in CWM - don't remember about TWRP. But you can edit the updater-script and replace "staging" with "/dev/block/mmcblk0p4", that should work.
That's a common mistake in many of the guides - the file must be in your *current* directory.
Click to expand...
Click to collapse
The stock updater-script looks like this
Code:
assert(package_extract_file("blob", "/tmp/blob"), write_raw_image("/tmp/blob",
"staging"),delete("/tmp/blob"));
When you say replace "staging" - what should the bottom line look like?
This post says the blob must be in the same folder as the fastboot.exe - what do you mean when you say the file must be in your "current" directory?
sbdags said:
Hmm I've never used a mac in my life so I can't help you any further. On a windows machine or linux the last thing to check is that the blob file is in the same folder but you already said that.
Can you run an md5sum on the zip file (I know you dl'ed it 5 times) just to confirm it is not getting corrupted....
Other than that I'm out of ideas - sorry.
Click to expand...
Click to collapse
I've setup adb and fastboot to work the same way in Windows & OS X. I used to be a PC guy til I moved to graphic design... Thanks everyone for the help :good:
FL00DY said:
When you say replace "staging" - what should the bottom line look like?
Click to expand...
Click to collapse
If you don't know how to do a simple text substitution, I'd recommend you use the fastboot method.
FL00DY said:
This post says the blob must be in the same folder as the fastboot.exe - what do you mean when you say the file must be in your "current" directory?
Click to expand...
Click to collapse
That post is wrong as I already said. Files whose name you specify on a command line must be in your current working directory (of your shell), unless you specify them with a path. So you either have to use "cd" to the directory containing the blob file, or you have to specify the (relative or absolute) path to the blob file on the fastboot command line.
_that said:
If you don't know how to do a simple text substitution, I'd recommend you use the fastboot method.
Click to expand...
Click to collapse
Well I just wasn't sure if I was only replacing Staging ...
Meaning should the line look like this ...
Code:
"/dev/block/mmcblk0p4"),delete("/tmp/blob"));
That post is wrong as I already said. Files whose name you specify on a command line must be in your current working directory (of your shell), unless you specify them with a path. So you either have to use "cd" to the directory containing the blob file, or you have to specify the (relative or absolute) path to the blob file on the fastboot command line.
Click to expand...
Click to collapse
OK sure that makes sense, I just didnt want you meant by current. Thanks very much :good:
It all worked on Friday, thanks so much @_that life saver ... oh and I wasn't trying to steal your thunder in the other thread :good:
This guide is to root Remix OS for PC
You will need Ubuntu for Rooting (You can download and run it in live CD)
If you are experienced with linux systems don't read whats written in bracket
1. Download and Extract RemixRoot.zip
2. Copy system.img from your pendrive or hdd wherever you have installed Remix Os to this folder (ie RemixRoot folder it should be alongside Readme.txt)
3. Open Terminal (Ctrl+Alt+T)
4. Type
Code:
sudo -i
5. Enter your password (If you are running in live cd then no password)
6. Change directory to RootRemix folder (Goto tmp folder, right click and goto properties and copy location, this is your <dir> replace it in command below )
Code:
cd <dir>
7. If you did it right next line of terminal will end with RemixRoot# followed by blinking cursor
8. Now run rootx.sh script by typing
Code:
sh rootx.sh
9. If everything goes right there wont be any error message and you will get a root.img in your RemixRoot folder
10. Rename it to system.img and copy to your pendrive/hdd replacing previous system.img
11. Reboot and go to RemixOS and update SuperSU binaries
12. That's it! you are now rooted
Thanks to Chainfire & hackarchive
I tried it but i got no system.img, i got r/w access to system (choosen by install) so i tried to symlink it to my system directory and commented out all image mounted related things from script and then tried it.
but after that i cannot boot android anymore, i think the problem is app_process linking to daemonsu, since i set back to original it boots like normal but no superuser access. SuperSU said theres is no superuser installed.
Any suggestion?
Silly question but will I lose root access if I update to the newest version by flashing the new image over the top?
Yes a silly question.... Deserves a silly answer. It will still be underneath, but good luck trying to retrace it!
any other method for rooting, without using ubuntu?
#tested with ubuntu live, and it works like a charms. Thank you..
Sent from my C46G using XDA Premium 4 mobile app
ninharp said:
I tried it but i got no system.img, i got r/w access to system (choosen by install) so i tried to symlink it to my system directory and commented out all image mounted related things from script and then tried it.
but after that i cannot boot android anymore, i think the problem is app_process linking to daemonsu, since i set back to original it boots like normal but no superuser access. SuperSU said theres is no superuser installed.
Any suggestion?
Click to expand...
Click to collapse
same problem here.
Hope same other method can solved
I modified the original script to work with the system folder installation and i removed all app_processX dependend things from script (dunno if it affects the root in any way, cannot find any issue by now) Read the Readme.txt for further installation instructions. The link you find on the reddit sub that GoPal has posted! I cannot post links right now.
Try this
kretex said:
Hope same other method can solved
Click to expand...
Click to collapse
ninharp said:
I tried it but i got no system.img, i got r/w access to system (choosen by install) so i tried to symlink it to my system directory and commented out all image mounted related things from script and then tried it.
but after that i cannot boot android anymore, i think the problem is app_process linking to daemonsu, since i set back to original it boots like normal but no superuser access. SuperSU said theres is no superuser installed.
Any suggestion?
Click to expand...
Click to collapse
You will get root.img file you will have to rename it to system.img
masdeco said:
same problem here.
Click to expand...
Click to collapse
Me too [emoji25]
Envoyé de mon E5333 en utilisant Tapatalk
I've just installed RemixOS 2.0 onto a partition on my Lenovo X200T. I followed the instructions and all was good until I tried to run SuperSU. When it tried to update via the normal method the install failed and asked for a reboot. Any suggestions.
ninharp said:
I modified the original script to work with the system folder installation and i removed all app_processX dependend things from script (dunno if it affects the root in any way, cannot find any issue by now) Read the Readme.txt for further installation instructions. The link you find on the reddit sub that GoPal has posted! I cannot post links right now.
Try this
Click to expand...
Click to collapse
the answer is replace the system folder. this is my methode :
1. copy the system img from the extracted remix iso to somewhere
2. then run the script
3. unpack the system img that already rooted and copy all the content to the system folder of the remix (replace)
4. done. Remix os rooted.
Guys, I installed Remix to ext4 partition (in order to use all free space), so there's no "system.img" on it (but there's "system" folder). How to modify the script or to root Remix other way?
masdeco, thanks for the idea! How do you unpack img file, btw?
4ezahernya said:
Guys, I installed Remix to ext4 partition (in order to use all free space), so there's no "system.img" on it (but there's "system" folder). How to modify the script or to root Remix other way?
masdeco, thanks for the idea! How do you unpack img file, btw?
Click to expand...
Click to collapse
after root the system img then mount it, copy all the content to the system folder of your remix.
since I am a linux user so I use this command :
mount -o loop system.img tmp
this is so cool cool
Works Lenovo Yoga 2 11
Installed to a partition on my HD:
Downloaded RemixOS iso
extracted contents of iso
created temp, data and system folders
ran this tool to root the system.img (now root.img)
renamed root.img back to system.img
mounted system.img to temp folder
copied contents of temp folder to system folder
added entry in grub
now I am triple booting Windows, Linux and RemixOS 2.0 Android with ROOT
Thank You!!!
here is a xdelta3 for patching system.img for those using Remix OS 2 from a USB stick and run windows
GizmoTheGreen said:
here is a xdelta3 for patching system.img for those using Remix OS 2 from a USB stick and run windows
Click to expand...
Click to collapse
can you please explain its usage?
the_poolee said:
can you please explain its usage?
Click to expand...
Click to collapse
me too!
Please
the_poolee said:
can you please explain its usage?
Click to expand...
Click to collapse
dariett said:
me too!
Please
Click to expand...
Click to collapse
it shouldn't be too hard to figure out, put the files in your folder of choice with the system.img from your usb stick, run the batfile. it should create a file named rooted system image, now just replace system.img on your usb stick with that and run...
ofcourse I am assuming your system.img is identical to the one I had, which it should be if it was the 2.0 dev preview which is the only thing you can get today, right?