Related
Hello,
I am going to prensent you today how to install ubuntu on your android device. Some of you propably already tried ,and had problems
making it work (or not). I modified the tutorial to make it easier, and corrected things. I also modified some paths in the scripts so that it can work with
cm7, if you are not a cm7 user you can download the other scripts too.
I based myself on this tutorial:
http://androlinux.com/android-ubuntu-development/how-to-install-ubuntu-on-android/
So let's start !
First, download the following cm7-ubuntu.rar file (decompress and copy over the whole ubuntu directory to the exeternal SD card of your Android smartphone/tablet:
Download cm7-ubuntu.rar:
http://www.fileserve.com/file/KQWsbRG
If you are a miui user, download cm7-ubuntu.rar, and replace the scripts by these:
http://www.fileserve.com/file/Tu8WZP5
If you are a not a cm7 neither a miui user, download cm7-ubuntu.rar, and replace the scripts by these:
http://www.fileserve.com/file/tuVMB9h
1) Make sure your phone is rooted and that busybox installed (if you are on cm7 all is ok).
2) Download Terminal Emulator on the market. Open it and type “su” to enter super user mode, then type “cd /emmc” or "cd /sdcard/external_sd" if your are a miui user or "cd /sdcard" if you are not on cm7, and “cd ubuntu” to enter the ubuntu directory in your SD card of your Android device.
3) Next, type “sh ubuntu.sh” to run the script which will basically get your Ubuntu image ready to run on your Android smartphone/tablet.
If you get error messages, don’t worry and keep going.
4) Type “bootubuntu” to enter Ubuntu. (Next time you enter Ubuntu, you just need to type “bootubuntu” from your /emmc/ubuntu directory, no need to run ubuntu.sh again.
If you got “[email protected]” at this point, congratulations! This means your Android OS comes with loop device support and Ubuntu is now running “chrooted” on top of your Android OS!!!
However, if there is an error like : "losetup: /dev/block/loop2: No such file or directory", this propably means that app2sd is conflicting with your sdcard, so to solve that
move all your applications on your internal sdcard and try again. If this doesn't solve your problem, that means that your kernel doesn't support loop
devices in most of the case, try flashing other kernels.
If after that you still have problems post, and I will try to reply when I have time
5) How to Install Programs on your Ubuntu!
Once you’ve got Ubuntu running on your Android device, it’s time to install some Ubuntu packages(or programs).
Type “apt-get update” to update, this is the first thing you will need to do before installing any new programs.
6) How to Install OpenSSH-server on your Android Ubuntu!
Type “apt-get install openssh-server” to install OpenSSH-server. What is OpenSSH-server? If you want to connect to your Android Ubuntu via an IP address (and SSH into it), you will want to do this.
7) How to Install TightVNCServer on your Android Ubuntu!
If you want to access the GUI of your Android Ubuntu, you can install TightVNCServer, which allows you to access the Android Ubuntu via Android VNC app on your Android smartphone/tablet or even access it remotely from your desktop computer.
Type “apt-get install tightvncserver” to install.
8) How to Install LXDE!(optional)
Next, we will install LXDE (Lightweight X11 Desktop Environment). Although we can use Ubuntu’s default GNOME (and trust me I love that), LXDE takes up less memory so our GUI access will be faster.
If you like GNOME, you can skip this step though.
Type “apt-get install lxde”
How to setup xstartup file so that when TightVNCServer is started, the LXDE runs instead of GNOME:
Type:
export USER = root
vncserver
(here he will ask you for a password for vnc, then if you want a view-only password, this mean you connect to vnc and you cannot interact with ubuntu, say n if you don't want and y if you want)
cat > /root/.vnc/xstartup
#!/bin/sh
xrdb $HOME/.Xresources
xsetroot -solid grey
icewm &
lxsession
Then press Volume-down&D togethe.
9) How fix language and start vnc at each boot:
Type:
touch /root/.bashrc
cat > /root/.bashrc
export LANG=en_US.UTF-8
export USER=root
rm /tmp/.X1-lock
rm /tmp/.X11-unix/X1
vncserver -geometry 1024x800 <== Here, you can change the resolution settings 1024×800 to the resolution of your liking. (Do not write that !)
Then again press Volume-down&D together.
10) Now we are going to reboot ubuntu to apply changes:
Reboot your phone, open Terminal Emulator again and type:
su
bootubuntu
Now your TightVNCServer is ready to accept any incoming connections from your phone or computer. Just point to the correct IP address and use port number 5901 to connect.
On your Android smartphone, just download the free app “Android-VNC-Viewer” and set the IP address to “127.0.0.1″ , port number 5901 and insert the password you set before in password.
Then enjoy !
SHUT DOWN UBUNTU: Sorry you have to reboot the phone, if you try to boot other ubuntu your phone will start to lag
Extra:
If you want more space to install programs & stuff, you can extend your user space without loosing your data.
Requirements:
Linux (you can make a live CD) or just an environment like cygwin for windows
Procedure:
1. UnZip Android or your present ubuntu.img file to your Home Folder. Or a folder of your liking (or even on your memory card!), just remember to cd before you do the following:
2. Open Terminal and Copy&Paste (Ctrl+C, Ctrl+Shift+V) this:
Code:
dd if=/dev/zero bs=1M count=XXX >> ubuntu.img
where XXX is the amount, in MB, by which data.img should be increased by.
My filesize started out as 256MB and I wanted a total of 512MB. That would mean I needed a extra 256MB, so I executed this:
Code:
dd if=/dev/zero bs=1M count=256 >> ubuntu.img
3. Run a file system check and file system resizer
Code:
e2fsck -f ubuntu.img
resize2fs ubuntu.img
e2fsck -f ubuntu.img
if prompted, press "y" for "yes"
4. Copy all of the Android files onto your SD card, put it into your phone...
Source: http://forum.xda-developers.com/showthread.php?t=737826
Sorry for my bad english
If you liked this thread, don't forget there is a Thanks button !
I have a problem with miui chamaleon rc2 . after i type bootubuntu i cant get [email protected] . im thinking that talonmtd dont support loopdevice but i have tried also with plapytus with no luck . you know i kernel with loop support for my rom ?
thanks
Do you have adb ?
MIU is based on cm7, you should have loop support...
do you have the error losetup : /dev/block/loop2: No such file or directory ?
im restarting device and i will copy all the commands . one moment
edit : i get this :
# sh ubuntu.sh
sh ubuntu.sh
modprobe: chdir(/lib/modules): No such file or directory
←[H←[Jmkdir: can't create directory '/data/local/mnt': File exists
←[H←[Jcd: can't cd to /emmc/ubuntu
chmod: bootubuntu: Operation not permitted
chmod: fsrw: Operation not permitted
chmod: mountonly: Operation not permitted
chmod: ubuntu.img: Operation not permitted
chmod: ubuntu.sh: Operation not permitted
chmod: unionfs: Operation not permitted
←[H←[J
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
This process does NOT damage Android OS!
Original Installer by Charan Singh
Modified for Ubuntu Chroot by Max Lee at AndroLinux.com ,G2Hacks.com and Ne
eHacks.net
To enter the Ubuntu Linux console just type 'bootubuntu'
# bootubuntu
bootubuntu
mknod: /dev/loop2: File exists
losetup: /dev/block/loop2: No such file or directory
mount: mounting /dev/block/loop2 on /data/local/ubuntu failed: Invalid argu
mount: mounting devpts on /data/local/ubuntu/dev/pts failed: No such file o
ectory
mount: mounting proc on /data/local/ubuntu/proc failed: No such file or dir
y
mount: mounting sysfs on /data/local/ubuntu/sys failed: No such file or dir
y
net.ipv4.ip_forward = 1
Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory non
ent
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory non
ent
Setting localhost on /etc/hosts
bootubuntu: cannot create /data/local/ubuntu/etc/hosts: directory nonexiste
READY TO ROCK AND ROLL BABY!
Brought to you by NexusOneHacks.net and the open source community!
chroot: can't execute '/bin/bash': No such file or directory
Shutting down Ubuntu
umount: can't umount /data/local/ubuntu/dev/pts: No such file or directory
umount: can't umount /data/local/ubuntu/proc: No such file or directory
umount: can't umount /data/local/ubuntu/sys: No such file or directory
umount: can't umount /data/local/ubuntu: Invalid argument
losetup: /dev/loop2: No such device or address
No, verify you don't have applications on your external sd card, if there is, transfer them to the internal sd card
EDIT: Yes, verify you don't have applications on your sd card
i dont have application on sd card
Okay this is wierd !
2 possibilities :
1. busybox is not installed
2. Your phone do not support loop devices
Can you send me a file in your /proc/ directory named config.gz ? (sorry it is a pain in the ass...)
Oh sorry I forgot how is named your external sdcard ? emmc or sdcard ?
Rename it to *.gz . Xda dont accept gz extension . I looked to sh script and i think the problem is that in cm7 sdcard is /sdcard not /emmc .
my external card is named /sdcard/external_sd and is a 16 gb class 2 so is a bit slower
Okay I think if found, I going to post new scripts for you quickly, I just verify that you have loop support
EDIT: Yes you have loop support, it is scripts
Replace these scripts : http://www.fileserve.com/file/Tu8WZP5
AnonymeLex said:
Okay I think if found, I going to post new scripts for you quickly, I just verify that you have loop support
EDIT: Yes you have loop support, it is scripts
Replace these scripts : http://www.fileserve.com/file/Tu8WZP5
Click to expand...
Click to collapse
Dont worry , but please upload this to xda because i hate fileserve and i have to wait 1200 seconds to download another file . Thanks
Yes, I forgot it's quicker, but does it work finally ?
I think is better that you fix the first post with instruction for miui users
Ok works , thanks a lot
i maked an error .
after this cat > /root/.bashrc i typed :
export LANG=en_US.UTF-8
export USER=root
rm /tmp/.X1-lock
rm /tmp/.X11-unix/X1
vncserver -geometry 800x480
exit
so every time i run bootubuntu this shut down . XD what i have to do to fix that ?
Edit : im recopying all including new script and i will not do same error
I'm using Ubuntu since 2006, it's really nice to see that the interest in Linux is growing so fast!
thunderteaser said:
I'm using Ubuntu since 2006, it's really nice to see that the interest in Linux is growing so fast!
Click to expand...
Click to collapse
im using ubuntu since the first version of android XD . im using it in dual boot . but i have changed 5 pc since 2005 for too use . is in use 24h/7d also with overclock . super pc !!! super android !!
thunderteaser said:
I'm using Ubuntu since 2006, it's really nice to see that the interest in Linux is growing so fast!
Click to expand...
Click to collapse
We can't ignore linux
(
Alberto96 said:
i maked an error .
after this cat > /root/.bashrc i typed :
export LANG=en_US.UTF-8
export USER=root
rm /tmp/.X1-lock
rm /tmp/.X11-unix/X1
vncserver -geometry 800x480
exit
so every time i run bootubuntu this shut down . XD what i have to do to fix that ?
Edit : im recopying all including new script and i will not do same error
Click to expand...
Click to collapse
Oh never thinked we could be in such a situation
The .bashrc is inside ubuntu.img, I don't really see a solution appart redownloading...
Sorry
Wait, exit don't really close ubuntu I think, it juste close terminal you should still able to connect via vnc and modify .bashrc ! To shut it down do Ctrl+D
I was flashing my yakjuxw over to yakju, when fastboot started failing to load system.img.
I have tried 4.0.2 and 4.0.1. Every image except for system.img works.
Code:
[[email protected] yakju-itl41f]# fastboot flash system system.img
error: cannot load 'system.img'
And it doesn't work using the zip either;
Code:
[[email protected] yakju-itl41f]# fastboot update *.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 325426112 bytes
error: update package missing system.img
I am running Archlinux.
Somewhere in the ./flash-all.sh script my ``sdcard'' was wiped, so I've lost my nandroid(s), but I can boot CWM from my PC. Help?
Open the zip file in a explorer-window somewhere and locate the system.img file and then try the first one over again.
None of these files are magic and they are pretty easy to explore to find the components you are looking for.
Are you sure you've unpacked things correctly?
What does the output from "ls -la" run in the the same folder say?
josteink said:
Open the zip file in a explorer-window somewhere and locate the system.img file and then try the first one over again.
None of these files are magic and they are pretty easy to explore to find the components you are looking for.
Are you sure you've unpacked things correctly?
What does the output from "ls -la" run in the the same folder say?
Click to expand...
Click to collapse
I unpacked the zip, so all the images in it are in this folder, but here's the output:
Code:
[[email protected] yakju-itl41f]# ls -la
total 663156
drwxr-x--- 2 david users 4096 Jan 18 20:17 .
drwxr-xr-x 4 david users 4096 Jan 18 20:07 ..
-rw-r----- 1 david users 93 Nov 21 18:20 android-info.txt
-rw-r--r-- 1 david users 4151296 Jan 1 2009 boot.img
-rw-r----- 1 david users 2363392 Nov 24 09:44 bootloader-maguro-primekj10.img
-rwxr-x--- 1 david users 831 Nov 24 09:44 flash-all.sh
-rw-r----- 1 david users 189165717 Nov 24 09:44 image-yakju-itl41f.zip
-rw-r----- 1 david users 12583168 Nov 24 09:44 radio-maguro-i9250xxkk1.img
-rw-r--r-- 1 david users 4491264 Jan 1 2009 recovery.img
-rwxrwxrwx 1 david users 325426112 Jan 1 2009 system.img
-rw------- 1 david users 140856312 Nov 22 11:09 userdata.img
Did you actually ever unlock fast boot? Just guessing here, at this point.
Sent from my Galaxy Nexus using Tapatalk
redownload stock images?
just an update, this is solved. The solution was found in rebooting my pc, which is something I, as a Linux user, seldom do, and my laptop cannot be trusted to boot due to its buggy BIOS.
Sent from my Galaxy Nexus
Korntoff said:
just an update, this is solved. The solution was found in rebooting my pc, which is something I, as a Linux user, seldom do, and my laptop cannot be trusted to boot due to its buggy BIOS.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Ridiculously old thread, I realize, so I feel kinda bad bumping it, but it's an early result on Google when searching for this problem, so I'll update a bit.
Rebooting will work, but isn't necessary, and is inconvenient. You just need to kill fastboot, it's hung with another process.
In linux, open up a terminal.
Code:
ps ax|grep fastboot
Note the PID(s)
Code:
kill -9 <PID1> <PID2>...<PIDn>
Another reason for this error is if you have device encryption enabled. In order to restore factory image, you first need to format /data to remove encryption.
I have no idea why this causes the error "cannot load system.img", but it definitely does.
Cerinthus said:
Ridiculously old thread, I realize, so I feel kinda bad bumping it,
In linux, open up a terminal...
Click to expand...
Click to collapse
Thanks for posting this.
In windows, I used task manager to find the ADB process and killed it, and then it worked fine.
groopk said:
Thanks for posting this.
In windows, I used task manager to find the ADB process and killed it, and then it worked fine.
Click to expand...
Click to collapse
To do this without searching thought task manager , just type "adb kill server " and then " adb start server" :thumbup:
Sent from my SCH-I605 using Tapatalk
quite an old thread again, but replying anyway.
The "failed to allocate ***** bytes" message means that it failed on memory of your computer, not on the storage of your phone.
Code:
fastboot.c
...
void *unzip_file(zipfile_t zip, const char *name, unsigned *sz)
{
...
*sz = get_zipentry_size(entry);
datasz = *sz * 1.001;
data = malloc(datasz);
if(data == 0) {
fprintf(stderr, "failed to allocate %d bytes\n", *sz);
return 0;
}
...
If it turns out that your machine has too small memory(unfortunately, which was also my case), you could unzip the file containing img files and flash system, boot and recovery images one by one. It's just the same.
great help
On the verge of flashing lolipop on my beloved n5, I got stuck with that stupid errror.
Thanks for the helpfull post.
downgrade to 4.4.4
just downgrade to 4.4.4 and then flash android 5.... mine worked....
FreakyTux said:
quite an old thread again, but replying anyway.
The "failed to allocate ***** bytes" message means that it failed on memory of your computer, not on the storage of your phone.
Code:
fastboot.c
...
void *unzip_file(zipfile_t zip, const char *name, unsigned *sz)
{
...
*sz = get_zipentry_size(entry);
datasz = *sz * 1.001;
data = malloc(datasz);
if(data == 0) {
fprintf(stderr, "failed to allocate %d bytes\n", *sz);
return 0;
}
...
If it turns out that your machine has too small memory(unfortunately, which was also my case), you could unzip the file containing img files and flash system, boot and recovery images one by one. It's just the same.
Click to expand...
Click to collapse
This was it! Thanks for posting!
Update ADB. That worked for me
same problem
i tried everything above but nothing works ..... can anyone help me out here
Alternate Way that always works..!!
1. Install TWRP recovery.
2. Mount USB Storage
3. Copy the system.img to phone storage
4. Select Install and then Select Install Image
5. Select the system.img file
6. Select partition as system
7. Confirm install
Done..
Korntoff said:
I was flashing my yakjuxw over to yakju, when fastboot started failing to load system.img.
I have tried 4.0.2 and 4.0.1. Every image except for system.img works.
Code:
[[email protected] yakju-itl41f]# fastboot flash system system.img
error: cannot load 'system.img'
And it doesn't work using the zip either;
Code:
[[email protected] yakju-itl41f]# fastboot update *.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 325426112 bytes
error: update package missing system.img
I am running Archlinux.
Somewhere in the ./flash-all.sh script my ``sdcard'' was wiped, so I've lost my nandroid(s), but I can boot CWM from my PC. Help?
Click to expand...
Click to collapse
rakesh.aggarwal said:
1. Install TWRP recovery.
2. Mount USB Storage
3. Copy the system.img to phone storage
4. Select Install and then Select Install Image
5. Select the system.img file
6. Select partition as system
7. Confirm install
Done..
Click to expand...
Click to collapse
with lots of thanks and much love!! fixed my device yeeyyyy!!!!
I was wondering if I could mount an empty.img file so that I could add executable into it and chmod 777 them or what ever the number is maybe 666.
Then I would add the location to my $PATH variable in the "/system/etc/mkshrc" file so I could execute those programs from any directory.
What say you?
Has this been done before?
It works!
Well, I wen ahead and tried it out, I figured "What the hell, its not like I have to format my sd card." It worked!
So what I did
1) I changed directories to Downloads. ("cd ~/Downloads")
2) I created a directory for my image in Downloads, and moved into it. (mkdir image && cd ./image)
3) I created an empty 4 gig image called apps.img using dd ("dd if=/dev/zero of=apps.img bs=1MB count=0 seek=4096")
4) I formated it to ext2 ("mke2fs -F apps.img")
5) I used adb to push it to my phone ("adb push ~/Downloads/image/apps.img /storage/sdcard0/Download/")
6) Then on my phone as su I mounted the image ("mount -o loop '/storage/sdcard0/Download/apps.img' '/data/local/mnt' ") {with single quotes around the directories, the double quotes wrap the whole actual command, you don't need them} [EDIT: I used bash on the phone to do this, ie I "su" [enter] ; "bash" [enter] ; "THE ABOVE COMMAND" [enter]
7) To test I used the python interpreter as my executable so I created a folder in /data/local/mnt called apps,(note* I should have made that folder on my pc before I pushed it to my phone to ensure that the foder was actually in the apps.img file.) I created two more folders "bin" and "lib" using "File Manager" on my phone. I then moved what I needed to run python into those folders (though you'll see I forgot something)
8) I added PYTHONHOME PYTHONPATH and added the bin folder I created to $PATH in the /system/etc/bash/bashrc file (Ask and I'll explain). If you don't have bash the mkshrc file is located "/system/etc/mkshrc" on your phone (if its Sprint SGSIII) adding environment variable there will accomplish the same thing, sorta.
9) I connected my phone to pc w/usb, opened up a teminal on pc, started an adb shell
10)........
Code:
[email protected]:~$ adb devices
List of devices attached
xxxxxxxx device
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # bash
void endpwent()(3) is not implemented on Android
localhost / # which python
/data/local/mnt/apps/bin/python
localhost / # python
'import site' failed; use -v for traceback
Python 2.6.2 (r262:71600, Mar 20 2011, 16:54:21)
[GCC 4.4.3] on linux-armv7l
Type "help", "copyright", "credits" or "license" for more information.
>>> import os
>>> import sys
>>> import math
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: No module named math
>>> import io
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/manuel/AptanaStudio3Workspace/python-for-android/python-build/output/usr/lib/python2.6/io.py", line 63, in <module>
ImportError: No module named _fileio
>>>
localhost / # exit
[email protected]:/ # ^D
[email protected]:/ $ ^D
[email protected]:~$
I'm thinking that if I can get my mkbootimg tools to work, I would mod an init script to mount the apps.img and then create links for each file in say '/mnt/apps/bin' create a link*in '/system/bin'. this should allow for phones with small or near full system partition install stuff like busybox or your own pprograms. More usefull for a developer.
I wanna try this with pythonforandroid, if I can make python and its modules. accessible during early init or just before the boot process finishes in general, and use it to run python, maybe python can handle boot in a different way, or maybe just one specific. function you might needs.
one big question I have. Does the pythonforandroid interpreter run ontop of the D VM?
Edge-Case said:
I'm thinking that if I can get my mkbootimg tools to work, I would mod an init script to mount the apps.img and then create links for each file in say '/mnt/apps/bin' create a link*in '/system/bin'. this should allow for phones with small or near full system partition install stuff like busybox or your own pprograms. More usefull for a developer.
I wanna try this with pythonforandroid, if I can make python and its modules. accessible during early init or just before the boot process finishes in general, and use it to run python, maybe python can handle boot in a different way, or maybe just one specific. function you might needs.
one big question I have. Does the pythonforandroid interpreter run ontop of the D VM?
Click to expand...
Click to collapse
I don't think so. All command-line programs I know of interface directly with the kernel.
Sent from my S3 on Sense 5 (you jelly?)
CNexus said:
I don't think so. All command-line programs I know of interface directly with the kernel.
Sent from my S3 on Sense 5 (you jelly?)
Click to expand...
Click to collapse
So getting an extended set of Linux (kernel) cli programs working with Android (kernel) is a matter of having the nessissary libraries, kernel prereq., and being compiled for the target processor?
From what I have read, the Android kernel has been cut back so far from the original Linux kernel that its difficult to port "Linux apps" to Android. Something about a slimmed down version of the GNU C/C++ libraries and the Android kernel being designed to run mostly Dalvik.
I haven't tried directly running any "Linux app" (already compiled for arm) on Android yet, but my game plan for that test was to load up an .img file with the nessissary execs, libs, config, etc files (as ext3 this time) and running some scripts that get the paths variables set up and then execute the script, I wrote a short Bash script that sets up python variables and adds others to PATH etc, and it worked, I had python on the img and the img mounted to /mnt/myside and python ran but with some errors, I need to get the variables right, its driving me mad, if its not this its that, last time it was the basic "help()" command not being declaired or something.
Well thats my plan, either these "Linux apps" run on Android without problem or I am going to A) write my own kernel to be compatible with Android/ cli Linux or I am going to get as much source code as I can and practice the art of compiling against Android and/or patching the code when/where nessissary.
We'll see what happens, I've done enough today/night.
I am not responsible for whatever may happen to you or your device when using this, Run this at your own risk!!
Requires unlocked bootloader!
Based on SuperSU - v4.46 (the binary updates from within the app later on)
I put together root installer script that comes with SU-binary/App with a insecure boot.img, everything is done over adb shell since we don't have a recovery right now but i will be working on it and already booted CWM
For current firmware:
LMY47D - root-boot
For past firmware:
LRX21V - root-boot
For past firmware:
LRX21M - root-boot
crappy video but simple demonstration :good:How to install:
Download the zip depending on your Nexus Player's firmware than extract & run root-boot.bat (Other operating system support coming soon for the installer script) Made on windows 7
Follow and read the on screen instruction carefully
Click to expand...
Click to collapse
SU app and binarys gets installed to /system/* directory's, The insecure boot.img gets installed to be able to access root adb shell and install those binarys
The root-boot boot.img is temporarily booted once during this process on the first boot of installation, it does not flash the boot.img
The previous boot.img before the installation is restored after SU is installed
Click to expand...
Click to collapse
Thanks @Chainfire for Superuser
My Donation Box
Troubleshooting:
Check to make sure your device gets picked up in adb before running the script - - - ADB Drivers
This tool uses an unlocked bootloader and i have not unlocked mine yet, does unlocking the bootloader wipe the device? - - - Yes unlocking the bootloader will wipe the device
After fastboot flashed the boot.img than rebooted to the home screen i continued the the script like the installation steps said but it returned "device not found" - - - As long as it shows transferring files a few seconds after than its fine, adb restarts at that moment which will than return "device not found" than it reconnects and transfers. if fastboot flashed than rebooted fine than adb shouldn't have an issue
Help! Something went wrong and im bootlooping but i dont want to loose all my saved data - - - Everything is fine, Download the factory zip from here for your android version than extract the zip and retrieve the system.img and copy it into a folder that contains adb/fastboot and boot your device into fastboot mode and do "fastboot flash system system.img" doing it this way wont wipe your "/data" partition leaving everything intact but will restore the system back to its defaults
(If you were to run the factory zip as an update than it would format everything)
I installed SU with this method but cant use adb commands on my device - - - Go into "Settings>About" and click on "Build" 7 times very fast and it will enable "Developer options" in the settings menu, Go back to the settings menu and open developer options (You may need to reboot if it doesnt show up immediately) and enable the "USB debugging" option
Ill be updating this as new version of lollipop get released
support for both firmwares are up, any issues let me know i tested them both though and everything looked okay
Reuploading, had a minor issue
Edit: LRX21M link back up, let me know if there's any issues
Whoa...
Let the games begin....
ftarules said:
Whoa...
Let the games begin....
Click to expand...
Click to collapse
yeup, after recovery i have a few system modification ideas for the settings apk i was considering
i do have other devices to worry about though so it may take some time
bunchies said:
I put together root installer script that comes with SU-binary/App with a insecure boot.img, everything is done over adb shell since we don't have a recovery right now but i will be working on it and already booted CWM
For current firmware:
LRX21V - root-boot
Click to expand...
Click to collapse
Working well, Thank you, after semi-manually adapting for working from Linux Mint.
I don't have permission to do "adb logcat" or "adb shell logcat" anymore though, unless I restart adbd as root.
mikereidis said:
Working well, Thank you, after semi-manually adapting for working from Linux Mint.
I don't have permission to do "adb logcat" or "adb shell logcat" anymore though, unless I restart adbd as root.
Click to expand...
Click to collapse
Use adb shell
than type su to use root adb shell
Since running the script everything seems all good except for using voice search. Anybody else having issues where voice search just closes?
Update: Erased and manually flashed the V firmware as I was on M and now it appears to be working correctly, not sure if this is going to be a problem with people stuck on M for now but you may want to think of upgrading your fimware.
Getting ADB device not found.. Anywhere I can download drivers from? I have the latest android-sdk
xReaper7x said:
Getting ADB device not found.. Anywhere I can download drivers from? I have the latest android-sdk
Click to expand...
Click to collapse
http://developer.android.com/sdk/win-usb.html
at what point, adb will restart about half way through and it shows it cant connect to device but it really is
but if your in fastboot and it cant connect to the device than thats an issue
i should note this in the OP
Subscribed for later. Awaiting someone else to port a recovery for this, I am lazy.
Snuzzo said:
Subscribed for later. Awaiting someone else to port a recovery for this, I am lazy.
Click to expand...
Click to collapse
lol Snuzzo :good: recovery coming soon
Links are down. Does anyone have a mirror of 21V?
prsterero said:
Links are down. Does anyone have a mirror of 21V?
Click to expand...
Click to collapse
Links are up, hosted on android file host
Can mirror in a bit if needed
bunchies said:
Links are up, hosted on android file host
Can mirror in a bit if needed
Click to expand...
Click to collapse
Looks like it's working now. Before I was getting that the file couldn't be found. Thanks I appreciate you releasing this I just got it unlocked so time to root and have some fun expanding the storage to 128gb
Alright so I just got around to running the script, and none of the commands work after booting back up. There's a failure for every rmdir and mkdir command that's used, so the device doesn't get rooted. I tried doing a adb remount, but the device isn't allowing that.
________________________________________________________
root-boot: By Bunchies @xda
________________________________________________________
________________________________________________________
Power off/unplug the device, hold the power button while
plugging in the device until you see the google logo and
than let go to enter fastboot mode
________________________________________________________
________________________________________________________
Plugin the device to a PC using a usb cable
________________________________________________________
Press any key to continue . . .
waiting for ADB
target reported max download size of 536870912 bytes
sending 'boot' (5424 KB)...
OKAY [ 1.357s]
writing 'boot'...
OKAY [ 1.515s]
finished. total time: 2.876s
rebooting...
finished. total time: 0.602s
When boot completes
and you see the launcher
Press any key to continue . . .
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
rm: /system/bin/install-recovery.sh: Read-only file system
mkdir failed for /system/app/SuperSU, Read-only file system
mkdir failed for /system/bin/.ext, Read-only file system
failed to copy 'SuperSU/SuperSU.apk' to '/system/app/SuperSU/': Is a directory
failed to copy 'x86/su' to '/system/xbin/su': Read-only file system
failed to copy 'x86/supolicy' to '/system/xbin/supolicy': Read-only file system
failed to copy 'x86/libsupol.so' to '/system/lib/libsupol.so': Read-only file sy
stem
failed to copy 'x86/99SuperSUDaemon' to '/system/etc/init.d/99SuperSUDaemon': Re
ad-only file system
failed to copy 'x86/install-recovery.sh' to '/system/etc/install-recovery.sh': R
ead-only file system
cp: system/xbin/su: No such file or directory
cp: system/xbin/su: No such file or directory
cp: system/xbin/su: No such file or directory
cp: /system/xbin/sugote-mksh: Read-only file system
ln: /system/bin/su: Read-only file system
ln: /system/bin/install-recovery.sh: File exists
rm: /system/bin/app_process: Read-only file system
ln: /system/bin/app_process: File exists
mv: rename /system/bin/app_process32 to /system/bin/app_process32_original: Read
-only file system
ln: /system/bin/app_process32: File exists
cp: /system/bin/app_process32_original: No such file or directory
Unable to chmod /system/app/SuperSU: No such file or directory
Unable to chmod /system/app/SuperSU/SuperSU.apk: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/lib/libsupol.so: No such file or directory
Unable to chmod /system/bin/.ext: No such file or directory
Unable to chmod /system/bin/.ext/.su: No such file or directory
Unable to chmod /system/etc/init.d/99SuperSUDaemon: No such file or directory
Unable to chmod /system/xbin/daemonsu: No such file or directory
Unable to chmod /system/xbin/sugote: No such file or directory
Unable to chmod /system/xbin/sugote-mksh: No such file or directory
Unable to chmod /system/etc/install-recovery.sh: No such file or directory
Unable to chmod /system/xbin/supolicy: No such file or directory
Unable to chmod /system/bin/app_process32_original: No such file or directory
Unable to chmod /system/bin/app_process_init: No such file or directory
chcon: Could not label /system/xbin/su with ubject_r:system_file:s0: No such
file or directory
chcon: Could not label /system/bin/.ext/.su with ubject_r:system_file:s0: No
such file or directory
chcon: Could not label /system/lib/libsupol.so with ubject_r:system_file:s0:
No such file or directory
chcon: Could not label /system/etc/init.d/99SuperSUDaemon with ubject_r:syste
m_file:s0: No such file or directory
chcon: Could not label /system/bin/sh with ubject_r:system_file:s0: Read-onl
y file system
chcon: Could not label /system/xbin/sugote with ubject_r:zygote_exec:s0: No
such file or directory
chcon: Could not label /system/xbin/supolicy with ubject_r:system_file:s0: N
o such file or directory
chcon: Could not label /system/xbin/sugote-mksh with ubject_r:system_file:s0:
No such file or directory
chcon: Could not label /system/bin/app_process32_original with ubject_r:zygot
e_exec:s0: No such file or directory
chcon: Could not label /system/bin/app_process_init with ubject_r:system_file
:s0: No such file or directory
Finished, you can now exit the installer
Press any key to continue . . .
Edit: Fixed it! I had to manually do "adb root" then "adb remount" and remount succeeded that time and I was able to run the rest of the script and saw all the file transfers.
prsterero said:
Alright so I just got around to running the script, and none of the commands work after booting back up. There's a failure for every rmdir and mkdir command that's used, so the device doesn't get rooted. I tried doing a adb remount, but the device isn't allowing that.
Edit: Fixed it! I had to manually do "adb root" then "adb remount" and remount succeeded that time and I was able to run the rest of the script and saw all the file transfers.
Click to expand...
Click to collapse
Glad to hear that!
bunchies said:
Glad to hear that!
Click to expand...
Click to collapse
The first time around I got into the bootloop so I had to start over. Second time and it worked now it seems that I can't get apps to install through the adb install command. I'm mainly trying to get es file explorer and stick mount so I can use an external flash drive. Is it possible that the root method somehow nuked this functionality? I've already restarted the adb server numerous times, rebooted the player, turned debugging off and back on, etc. Even after all that it just sits after displaying the transfer rate and never finishes.
Edit: Nevermind. Looks like this issue also goes back to having to do adb root and adb remount. Gotta do it for everything apparently
prsterero said:
The first time around I got into the bootloop so I had to start over. Second time and it worked now it seems that I can't get apps to install through the adb install command. I'm mainly trying to get es file explorer and stick mount so I can use an external flash drive. Is it possible that the root method somehow nuked this functionality? I've already restarted the adb server numerous times, rebooted the player, turned debugging off and back on, etc. Even after all that it just sits after displaying the transfer rate and never finishes.
Edit: Nevermind. Looks like this issue also goes back to having to do adb root and adb remount. Gotta do it for everything apparently
Click to expand...
Click to collapse
Weird, windows 8?
What is this:
- This is a script which can be used from a Linux PC (should work on Mac too) in order to modify the OTA updates.
- It is suitable for all 6039 and 6045 devices.
- The owners of 6039 which returned the fastboot commands to their devices by using the guide in this section need to use the script in order to modify and install future OTA updates.
- The script removes the checks and the patches for the recovery. In addition for the 6039 users removes the check and the patches which remove the fatsboot commands.
How to use it:
- There are dependencies (i.e. packages which are needed) in order the script to function properly. In order to be widely supported the script has been written as bash script and needs only zip and unzip binaries in order to modify the upgrade file. All other commands used in it should be available as core packages on any Linux system.
- The script must have executable permissions and the update file to be provided as argument e.g.
Code:
ota_modifier.sh /home/Downloads/update.zip
there a few questions which can be asked by the script, which must be answered with y/n. At the end, in the directory from where the script has been executed, you will have a modified flashable ZIP which can be installed through TWRP in order to upgrade the device.
md5sum: ca536d39ec63845eb55803e1e8b57e3d ota_modifier.zip
P.S. If someone can modify the script to work under Windows is welcome to do it.
petrov.0 said:
What is this:
- This is a script which can be used from a Linux PC (should work on Mac too) in order to modify the OTA updates.
- It is suitable for all 6039 and 6045 devices.
- The owners of 6039 which returned the fastboot commands to their devices by using the guide in this section need to use the script in order to modify and install future OTA updates.
- The script removes the checks and the patches for the recovery. In addition for the 6039 users removes the check and the patches which remove the fatsboot commands.
How to use it:
- There are dependencies (i.e. packages which are needed) in order the script to function properly. In order to be widely supported the script has been written as bash script and needs only zip and unzip binaries in order to modify the upgrade file. All other commands used in it should be available as core packages on any Linux system.
- The script must have executable permissions and the update file to be provided as argument e.g.
Code:
ota_modifier.sh /home/Downloads/update.zip
there a few questions which can be asked by the script, which must be answered with y/n. At the end, in the directory from where the script has been executed, you will have a modified flashable ZIP which can be installed through TWRP in order to upgrade the device.
md5sum: f401a1a5baafa20110cf47606b45d99a ota_modifier.zip
P.S. If someone can modify the script to work under Windows is welcome to do it.
Click to expand...
Click to collapse
Not a zip file?
[email protected]:/workarea/android/idol3/updates > ls
update_20150928.zip
[email protected]:/workarea/android/idol3/updates > ota_modifier.sh update_20150928.zip
The provided file is not a zip file!
[email protected]:/workarea/android/idol3/updates > unzip update_20150928.zip
Archive: update_20150928.zip
signed by SignApk
inflating: META-INF/com/android/metadata
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: firmware/VERINFO/NON.VER
inflating: patch/boot.img.p
inflating: patch/emmc_appsboot.mbn.p
inflating: patch/firmware/IMAGE/CMNLIB.B01.p
inflating: patch/firmware/IMAGE/CMNLIB.MDT.p
inflating: patch/firmware/IMAGE/DXHDCP2.B01.p
inflating: patch/firmware/IMAGE/DXHDCP2.MDT.p
inflating: patch/firmware/IMAGE/ISDBTMM.B01.p
inflating: patch/firmware/IMAGE/ISDBTMM.MDT.p
inflating: patch/firmware/IMAGE/KEYMASTE.B01.p
inflating: patch/firmware/IMAGE/KEYMASTE.MDT.p
inflating: patch/firmware/IMAGE/MBA.MBN.p
inflating: patch/firmware/IMAGE/MODEM.B00.p
*update* You need to strip the filename to make it case insensitive. You may have files that don't end in .zip at all if they use the name the update saves as which was a number like 67039
[email protected]:/workarea/android/idol3/updates > ota_modifier.sh update_20150928.Zip
The file update_20150928.Zip is OK!
Creating a copy of the file...
Working hard...
*** Would you like to remove the checks and the ***
*** patches which remove the fastboot commands ? ***
*** Note that if your device is 6045 probably is not ***
*** affected by this, therefore is recommended to ***
*** choose 'n' from the prompt below. ***
*** If the update is for 6039 choose 'y' ***
Clean them all [y/n]: n
Creating the modified update file
/workarea/android/idol3/updates/update_20150928_modified.zip has been created.
Cleaning of the mess !
DONE!!!
[email protected]:/workarea/android/idol3/updates > ls -l
total 57420
-rw-r--r-- 1 famewolf famewolf 58793801 Sep 14 01:30 update_20150928.Zip <--- Where is the file it says it just created? Only the original is present.
famewolf said:
Not a zip file?
[email protected]:/workarea/android/idol3/updates > ls
update_20150928.zip
[email protected]:/workarea/android/idol3/updates > ota_modifier.sh update_20150928.zip
The provided file is not a zip file!
[email protected]:/workarea/android/idol3/updates > unzip update_20150928.zip
Archive: update_20150928.zip
signed by SignApk
inflating: META-INF/com/android/metadata
....
*update* You need to strip the filename to make it case insensitive. You may have files that don't end in .zip at all if they use the name the update saves as which was a number like 67039
Click to expand...
Click to collapse
Hm, interesting. Actually the check is based on the 'magic' of the file. Can you run:
Code:
file update_20150928.zip
and to provide the output.
Edit: Probably I should remove this check and to unzip the file blindly. And then on unsuccessful unzip to exit with error. Probably this is a better approach.
petrov.0 said:
Hm, interesting. Actually the check is based on the 'magic' of the file. Can you run:
Code:
file update_20150928.zip
and to provide the output.
Click to expand...
Click to collapse
[email protected]:/workarea/android/idol3/updates > file update_20150928.zip
update_20150928.zip: ERROR: cannot open `update_20150928.zip' (No such file or directory)
/workarea is a NAS share mounted via NFS if that matters. It may also explain why the output file disappeared. I'll try running it on a "local" directory.
---------- Post added at 05:34 PM ---------- Previous post was at 05:31 PM ----------
I think your path is off somewhere. Also if you upzip "blindly" you can still check the return code to ensure it was 0.
[email protected]:/tmp > ota_modifier.sh update_20150928.Zip
The file update_20150928.Zip is OK!
Creating a copy of the file...
Working hard...
*** Would you like to remove the checks and the ***
*** patches which remove the fastboot commands ? ***
*** Note that if your device is 6045 probably is not ***
*** affected by this, therefore is recommended to ***
*** choose 'n' from the prompt below. ***
*** If the update is for 6039 choose 'y' ***
Clean them all [y/n]: n
Creating the modified update file
zip I/O error: Permission denied
zip error: Could not create output file (../update_20150928_modified.zip)
/tmp/update_20150928_modified.zip has been created.
Cleaning of the mess !
DONE!!!
[email protected]:/tmp > ls up*
update_20150928.Zip
famewolf said:
[email protected]:/workarea/android/idol3/updates > file update_20150928.zip
update_20150928.zip: ERROR: cannot open `update_20150928.zip' (No such file or directory)
/workarea is a NAS share mounted via NFS if that matters. It may also explain why the output file disappeared. I'll try running it on a "local" directory.
---------- Post added at 05:34 PM ---------- Previous post was at 05:31 PM ----------
I think your path is off somewhere.
[email protected]:/tmp > ota_modifier.sh update_20150928.Zip
The file update_20150928.Zip is OK!
Creating a copy of the file...
Working hard...
*** Would you like to remove the checks and the ***
*** patches which remove the fastboot commands ? ***
*** Note that if your device is 6045 probably is not ***
*** affected by this, therefore is recommended to ***
*** choose 'n' from the prompt below. ***
*** If the update is for 6039 choose 'y' ***
Clean them all [y/n]: n
Creating the modified update file
zip I/O error: Permission denied
zip error: Could not create output file (../update_20150928_modified.zip)
/tmp/update_20150928_modified.zip has been created.
Cleaning of the mess !
DONE!!!
[email protected]:/tmp > ls up*
update_20150928.Zip
Click to expand...
Click to collapse
Yes, on the local machine will be better (also try the script from there) ... It works without problems on Debian and openSUSE
... No write access to / tmp ... Come on, who does not have access to there. <- This was an error in the script.
OK there was an error indeed in the directory switch (it was behind the fi) when you select n on the prompt. Download the script again. It is already updated.
Edit: @famewolf thanks for the fast response in order to be corrected.
petrov.0 said:
OK there was an error indeed in the directory switch (it was behind the fi) when you select n on the prompt. Download the script again. It is already updated.
Edit: @famewolf thanks for the fast response in order to be corrected.
Click to expand...
Click to collapse
Are you checking the "n" branch because I'm still unable to generate an output file trying both /tmp and /workarea/idol3/updates I've posted my update file at the bottom.
Example:
[email protected]:/tmp > /workarea/android/idol3/ota_modifier.sh update_20150928.Zip
The file update_20150928.Zip is OK!
Creating a copy of the file...
Working hard...
*** Would you like to remove the checks and the ***
*** patches which remove the fastboot commands ? ***
*** Note that if your device is 6045 probably is not ***
*** affected by this, therefore is recommended to ***
*** choose 'n' from the prompt below. ***
*** If the update is for 6039 choose 'y' ***
Clean them all [y/n]: n
Creating the modified update file
zip I/O error: Permission denied
zip error: Could not create output file (../update_20150928_modified.zip)
/tmp/update_20150928_modified.zip has been created.
Cleaning of the mess !
DONE!!!
[email protected]:/tmp > ls up*
update_20150928.Zip
[email protected]:/tmp >
This is on Linux Mint 17.2 KDE which is based on Ubuntu 14.04.
Choosing Y at the check DOES produce an output file.
[email protected]:/tmp > /workarea/android/idol3/ota_modifier.sh update_20150928.Zip
The file update_20150928.Zip is OK!
Creating a copy of the file...
Working hard...
*** Would you like to remove the checks and the ***
*** patches which remove the fastboot commands ? ***
*** Note that if your device is 6045 probably is not ***
*** affected by this, therefore is recommended to ***
*** choose 'n' from the prompt below. ***
*** If the update is for 6039 choose 'y' ***
Clean them all [y/n]: y
Cleaning the patches which affect the fastboot commands...
Creating the modified update file
/tmp/update_20150928_modified.zip has been created.
Cleaning of the mess !
DONE!!!
[email protected]:/tmp > ls up*
update_20150928_modified.zip update_20150928.Zip
[email protected]:/tmp >
Try the file yourself:
*Removed to prevent people from trying to install it on the wrong devices*
famewolf said:
Are you checking the "n" branch because I'm still unable to generate an output file trying both /tmp and /workarea/idol3/updates I've posted my update file at the bottom.
....
Click to expand...
Click to collapse
Damn. Sorry somehow I messed files ... this not been updated ... This section from the script must look like this:
Code:
if [ -d patch ]; then
if [[ "$ans" == "y" ]] || [[ "$ans" == "Y" ]]; then
pushd patch &>/dev/null
for i in emmc_appsboot.mbn.p hyp.img.p rpm.img.p sbl1.img.p tz.img.p
do
rm "$i"
done
popd &>/dev/null
fi
I will upload the correct file after a minute.
@famewolf now is OK ... checked (twice) .
petrov.0 said:
@famewolf now is OK ... checked (twice) .
Click to expand...
Click to collapse
Success!
-rw-r--r-- 1 famewolf famewolf 58623940 Oct 1 19:48 update_20150928_modified.zip
-rw-r--r-- 1 famewolf famewolf 58793801 Sep 14 01:30 update_20150928.Zip
Will have to restore factory image of UE40 then try to apply the update (I have a modified build.prop and other files that will prevent an update).
Windows users can put the update and the script on a jump drive and boot into a linux live iso to run it...the live iso can be booted in virtualbox as well which is a free virtual pc package.
*update* Just a quick followup to say the modified update applied just fine via twrp and worked as expected.
I see almost everyone is using Ubuntu. Would Debian be ok (I don't see why it shouldn't)? I am dual booting W7/Debian 8.2 and would hate to change to Ubuntu.
Thanks
Sent from my 6045Y using XDA Free mobile app
famewolf said:
Success!
-rw-r--r-- 1 famewolf famewolf 58623940 Oct 1 19:48 update_20150928_modified.zip
-rw-r--r-- 1 famewolf famewolf 58793801 Sep 14 01:30 update_20150928.Zip
Will have to restore factory image of UE40 then try to apply the update (I have a modified build.prop and other files that will prevent an update).
Windows users can put the update and the script on a jump drive and boot into a linux live iso to run it...the live iso can be booted in virtualbox as well which is a free virtual pc package.
*update* Just a quick followup to say the modified update applied just fine via twrp and worked as expected.
Click to expand...
Click to collapse
Anghirrim said:
I see almost everyone is using Ubuntu. Would Debian be ok (I don't see why it shouldn't)? I am dual booting W7/Debian 8.2 and would hate to change to Ubuntu.
Thanks
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
Where you see this ? Of course it will work.
Anghirrim said:
I see almost everyone is using Ubuntu. Would Debian be ok (I don't see why it shouldn't)? I am dual booting W7/Debian 8.2 and would hate to change to Ubuntu.
Thanks
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
I used OpenSuse KDE for around 10 years. I only switched to Linux Mint in the last couple of years due to issues getting certain hardware to work under opensuse that just worked out of the box with linux mint. (gscan2pdf..a minolta 1250W printer) I also was frustrated that certain software packages were only available from users instead of being in the main opensuse repo and some of those were broken in various ways. Debian should work just fine...actually just about any linux should work just fine but you could always use a live iso in virtualbox or boot off a live iso directly.
No need for a live one don't worry. I was more guessing about dependencies name issue or conflicts.
I used to be an Archlinux user for several years and know how complicated it can be when you mix 32 and 64 bits libraries.
I'm using my computer less and less so moved to Debian for a slower update pace.
Regarding Ubuntu, in the compilation topics, most of the people talk about Ubuntu so I was guessing there was something specific.
Thanks guys.
Sent from my 6045Y using XDA Free mobile app
Web based OTA modifier
This is strictly just "pie in the sky" thinking.....what would be ideal would be to have a webpage where you can upload your update and it processes it then provides you the modified file. I've seen this done with similar things...I know there are places online that would provide a linux shell to run the script..not sure how the web page would integrate but that would allow people to request the update from a phone.
Anyway the safest update method is to go to TWRP and 1) Backup your system, data, boot of existing system in case of problems. 2)Restore a factory image of the version you are on so everything is as the update will expect. 3) Apply the modified update. 4) Make another backup..this time of system image and boot..this will become your new "factory image" for the next update. You can then apply zip's like the supersu.zip and any special ones you've created with the zipme app. Finally reboot.
Really nice. Please port to windows.
Bostrot said:
Really nice. Please port to windows.
Click to expand...
Click to collapse
You'd have better luck in googling how to run bash scripts under windows (or using my live iso + jumpdrive suggestion). petrov.0 doesn't use windows.
do you think it's possible to crossflash my 6045y with the 6045i latest update with this modification since the partitions are the same?
keyra74 said:
do you think it's possible to crossflash my 6045y with the 6045i latest update with this modification since the partitions are the same?
Click to expand...
Click to collapse
As stated many times before, NO! The most recent update will only install on UE40 firmware and it upgrades it to UER0. It checks for it and even if it didn't the source code for the 6045Y and the 6045i are different...even if you removed the check when it tried to patch your radio it would probably kill both cell and wifi and create a mess you probably could not get back from unless you've used @DallasCZ's Backup_All script to backup all partitions on your device.
Having partitions in the same order just means they can use the same recovery since system, data and boot will be in the same places...nothing more.
alright