***[TUTORIAL]Meizu MX4 Android to Ubuntu Touch*** - Meizu MX

*****WARNING!!! All your actions with the phone is at your own risk. The author are not liable. This is just your choice. ******​
You need an MX4 Android version and an PC with Ubuntu, phablet-tools and adb-fastboot installed.
$ adb devices
$ adb shell grep ro.product.name /system/build.prop
ro.product.name=arale
$ adb shell grep build.id /system/build.prop
ro.build.id=KOT49H
$ adb shell grep ro.product.device /system/build.prop
ro.product.device=arale
$ ubuntu-device-flash query --device=arale --list-channels
$ wget http://people.canonical.com/~alextu/tangxi/recovery/recovery.img
$ adb reboot-bootloader
$ fastboot flash recovery recovery.img
$ fastboot reboot
From recovery:
$ ubuntu-device-flash touch --device=arale --channel=ubuntu-touch/stable/meizu.en --developer-mode --password=1234 --wipe
You can change you build.prop from another way: Root Browser.

@empies

Recovery must be unlocked? Can I flash it on CM12.1 or must be only Flyme?

Shadoworion said:
Recovery must be unlocked? Can I flash it on CM12.1 or must be only Flyme?
Click to expand...
Click to collapse
I found this tutorial on channel official of developing. I care yes just flash the recovery.

Naphtha said:
I found this tutorial on channel official of developing. I care yes just flash the recovery.
Click to expand...
Click to collapse
Can you give me link of this original tutorial? Have you ever tried it?

Shadoworion said:
Can you give me link of this original tutorial? Have you ever tried it?
Click to expand...
Click to collapse
Nope. I can't give you the link. I have an Mx4 32 gb with ubuntu touch, if i flash it is useless

Hi,
my build.prop values are:
ro.product.name=cm_mx4
ro.build.id=LMY48Y
ro.product.device=mx4
Do I have to change these before flashing?
Thanks in advance.

Danj1 said:
Hi,
my build.prop values are:
ro.product.name=cm_mx4
ro.build.id=LMY48Y
ro.product.device=mx4
Do I have to change these before flashing?
Thanks in advance.
Click to expand...
Click to collapse
yes change it first

Code:
2015/11/24 18:21:33 Device is |arale|
2015/11/24 18:21:33 Flashing version 7 from ubuntu-touch/stable/meizu.en channel and server https://system-image.ubuntu.com to device arale
/home/david/.cache/ubuntuimages/ubuntu-touch/stable/meizu.en/arale/version-7.tar.xz
/home/david/.cache/ubuntuimages/pool/device-a8a0e27cb5670a0ccb9dacd2b12dc80b2df8fe776235cf9a0f7478ef7aa934a4.tar.xz
at this moment the terminal is in slowdown status. what do I need to do?

Shadoworion said:
Code:
2015/11/24 18:21:33 Device is |arale|
2015/11/24 18:21:33 Flashing version 7 from ubuntu-touch/stable/meizu.en channel and server https://system-image.ubuntu.com to device arale
/home/david/.cache/ubuntuimages/ubuntu-touch/stable/meizu.en/arale/version-7.tar.xz
/home/david/.cache/ubuntuimages/pool/device-a8a0e27cb5670a0ccb9dacd2b12dc80b2df8fe776235cf9a0f7478ef7aa934a4.tar.xz
at this moment the terminal is in slowdown status. what do I need to do?
Click to expand...
Click to collapse
only, wait

2015/11/24 20:49:43 error pushing: failed to copy '/home/user/.cache/ubuntuimages/pool/device-ABCDEF.tar.xz' to '/cache/recovery//device-ABCDEF.tar.xz': No space left on device
Click to expand...
Click to collapse
Any idea how to get more space. What can safely be deleted?
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 946.3M 128.0K 946.1M 0% /dev
/dev/block/platform/mtk-msdc.0/by-name/cache
106.2M 53.2M 50.8M 51% /cache
Click to expand...
Click to collapse
/cache # du -h
4.0K ./lost+found
53.1M ./recovery
4.0K ./backup/1/_full
4.0K ./backup/1/_delta
12.0K ./backup/1
16.0K ./backup
53.2M .
Click to expand...
Click to collapse

Danj1 said:
Any idea how to get more space. What can safely be deleted?
Click to expand...
Click to collapse
you do wipe? you insert "--wipe"?

Naphtha said:
you do wipe? you insert "--wipe"?
Click to expand...
Click to collapse
The command I used:
ubuntu-device-flash touch --device=arale --channel=ubuntu-touch/stable/meizu.en --wipe

Naphtha said:
*****WARNING!!! All your actions with the phone is at your own risk. The author are not liable. This is just your choice. ******​
You need an MX4 Android version and an PC with Ubuntu, phablet-tools and adb-fastboot installed.
$ adb devices
$ adb shell grep ro.product.name /system/build.prop
ro.product.name=arale
$ adb shell grep build.id /system/build.prop
ro.build.id=KOT49H
$ adb shell grep ro.product.device /system/build.prop
ro.product.device=arale
$ ubuntu-device-flash query --device=arale --list-channels
$ wget http://people.canonical.com/~alextu/tangxi/recovery/recovery.img
$ adb reboot-bootloader
$ fastboot flash recovery recovery.img
$ fastboot reboot
From recovery:
$ ubuntu-device-flash touch --device=arale --channel=ubuntu-touch/stable/meizu.en --developer-mode --password=1234 --wipe
You can change you build.prop from another way: Root Browser.
Click to expand...
Click to collapse
Seriously? You said stupid and you make a tuto exactly same as i said ?? -_-

bobslesbricoleurs said:
Seriously? You said stupid and you make a tuto exactly same as i said ?? -_-
Click to expand...
Click to collapse
btw it's not same be changed something and he already tried without changing device name etc.
damn WHY always after i brick phone
---------- Post added at 02:47 PM ---------- Previous post was at 02:45 PM ----------
@Naphtha is after ubuntu installation preloader unlocked ?

Partition resize of mx4 for flash ubuntu touch : http://forum.xda-developers.com/meizu-mx/general/meizu-mx4-partitions-table-help-resize-t3256902

Well. This Tuto is not complete, right? No need to re-size or anything?

hi this ways woks ? any issue ?

makakiel said:
hi this ways woks ? any issue ?
Click to expand...
Click to collapse
Nope don't work. If you flash ubuntu touch with this tutorial is full brick.

actualy what is missing ?
I see a other on wit ubuntu desktop this one work ?

Related

[REQ] Need someone to check something for me on a STOCK Vibrant

Anyone out there willing to help me out?
I just someone to run this command with their phone hooked up, USB Debugging ENABLED:
adb shell ls -l -R /sys/class > class_structure_VIBRANT.txt
This will output a text file in whichever directory you run the command from, that will list the hardware capabilities of the phone for me - this would help me IMMENSELY from a development standpoint!
Check out the text file - zero personal / private information will be in there!
Thanks!
I have a samsung that is ROOT, has the gps-fix for ROOT users, the custom recovery image.
Is that good for you?
abcdavidefg said:
I have a samsung that is ROOT, has the gps-fix for ROOT users, the custom recovery image.
Is that good for you?
Click to expand...
Click to collapse
That would be a start - I'd like to find one that is non-root, though!
Doward said:
That would be a start - I'd like to find one that is non-root, though!
Click to expand...
Click to collapse
http://www.4shared.com/document/7F2UoKt-/class_structure_VIBRANT.html
This is from an un-rooted Vibrant bone stock Rom just after flashing it with ODIN!
mp2ning said:
http://www.4shared.com/document/7F2UoKt-/class_structure_VIBRANT.html
This is from an un-rooted Vibrant bone stock Rom just after flashing it with ODIN!
Click to expand...
Click to collapse
Great, thank you!
*edit*
Oh wow... oddball structure there!!
Can I get these as well?
adb shell ls -l -R /sys/devices/platform > platform_structure_VIBRANT.txt
and
adb shell ls -l -R /sys/devices/virtual > virtual_structure_VIBRANT.txt
adb shell ls -l -R /sys/devices/platform > platform_structure_VIBRANT.txt
http://www.4shared.com/document/ouZxt2TF/_2__platform_structure_VIBRANT.html
adb shell ls -l -R /sys/devices/virtual > virtual_structure_VIBRANT.txt
http://www.4shared.com/document/Vnvz-oEQ/virtual_structure_VIBRANT.html
I had already rooted after I posted the first file so I unrooted to get these last 2 files in case it matters!
mp2ning said:
adb shell ls -l -R /sys/devices/platform > platform_structure_VIBRANT.txt
http://www.4shared.com/document/ouZxt2TF/_2__platform_structure_VIBRANT.html
adb shell ls -l -R /sys/devices/virtual > virtual_structure_VIBRANT.txt
http://www.4shared.com/document/Vnvz-oEQ/virtual_structure_VIBRANT.html
I had already rooted after I posted the first file so I unrooted to get these last 2 files in case it matters!
Click to expand...
Click to collapse
LOL awesome, thanks!!
I connect my phone, open the cmd and then I type this
cd\
cd AndroidSDK\tools\
adb shell ls -l -R /sys/class > class_structure_VIBRANT.txt
I dont get error, but i dont get any text.
I am just trying to help
abcdavidefg said:
I connect my phone, open the cmd and then I type this
cd\
cd AndroidSDK\tools\
adb shell ls -l -R /sys/class > class_structure_VIBRANT.txt
I dont get error, but i dont get any text.
I am just trying to help
Click to expand...
Click to collapse
What do you get?
If the file completes, then you should be able to type in 'dir' and see class_structure_VIBRANT.txt in there
Doward said:
What do you get?
If the file completes, then you should be able to type in 'dir' and see class_structure_VIBRANT.txt in there
Click to expand...
Click to collapse
I attach the files that you asked for it

[REQ] Need someone to check something for me on a STOCK Streak

Anyone out there willing to help me out?
I just someone to run this command with their phone hooked up, USB Debugging ENABLED:
adb shell ls -l -R /sys/class > class_structure_STREAK.txt
This will output a text file in whichever directory you run the command from, that will list the hardware capabilities of the phone for me - this would help me IMMENSELY from a development standpoint!
Check out the text file - zero personal / private information will be in there!
Thanks!
Enjoy
STOCK - 2.1 (hope that's alright )
Meltus said:
Enjoy
STOCK - 2.1 (hope that's alright )
Click to expand...
Click to collapse
That's fine... interesting structure Dell went with.
Mind if I get these, too?
adb shell ls -l -R /devices/platform > platform_structure_STREAK.txt
AND
adb shell ls -l -R /devices/virtual > virtual_structure_STREAK.txt
Not good news on those 2.
The first one just says:
"adb server is out of date. killing...
* daemon started successfully *
R: No such file or directory
/devices/platform: No such file or directory"
and the second one:
"/devices/virtual: No such file or directory"
My fault!
adb shell ls -l -R /sys/devices/platform > platform_structure_STREAK.txt
AND
adb shell ls -l -R /sys/devices/virtual > virtual_structure_STREAK.txt
That should do it
Also, are you rooted?
Doward said:
My fault!
adb shell ls -l -R /sys/devices/platform > platform_structure_STREAK.txt
AND
adb shell ls -l -R /sys/devices/virtual > virtual_structure_STREAK.txt
That should do it
Also, are you rooted?
Click to expand...
Click to collapse
Yeah that did it
and no, i'm just on the Stock 2.1 beta.
(both are in the zip, to big to upload individually)
Meltus said:
Yeah that did it
and no, i'm just on the Stock 2.1 beta.
(both are in the zip, to big to upload individually)
Click to expand...
Click to collapse
Awesome, big thanks!!
Feel like beta testing something for me?
I am always fond of beta-testing. But what is it ?
Doward said:
Awesome, big thanks!!
Feel like beta testing something for me?
Click to expand...
Click to collapse
Sure thing

Why 'adb remount' failed on a Rooted neuxs one

Hi,
I have rooted my Nexus one. I can do "'adb shell and then 'su' under the shell"
But on my MacOS Desktop, when I execute 'adb remount', it still said
$ adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
Can anyone please help me resolve this?
Thank you.
[size=+4]DO *NOT* POST QUESTIONS IN THIS FORUM - only tips/info/etc.[/size]
Right at the top. Why does this have to be repeated on a daily basis?
Can you please move my thread to the right forum? I can't find a way to do it.
Anyhow, to answer you question... you "adb remount" is disabled in production releases... just rooting does not allow this.
You need a modified boot image where ro.secure=0 in default.props, instead of ro.secure=1. The ro.secure flag in the boot image indicates whether the root filesystem can be remounted as read/write... 0 indicated it can be... 1 indicated it cannot be.
If ro.secure=0, this is referred to as insecure boot.
Most custom ROMs have this by default... some rooted stock ROMs do not have this...
Will the Modified GRI40 (2.3.3 Gingerbread) ROM from this
http:// forum.xda-developers.com/showthread.php?t=968396
Does what I need? Thanks.
Or you can also use these commands to mount and unmount the system partition as writable:
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
mount -o remount,ro /dev/block/mtdblock3 /system
Thank you. That seems to be an easier solution for me.
But after I did
$ adb shell
$ su
# mount -o remount,rw /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
I go to another shell and i did
adb push sqlite3 /system
failed to copy 'sqlite3' to '/system/sqlite3': Read-only file system
$ adb push sqlite3 /system/bin
failed to copy 'sqlite3' to '/system/bin/sqlite3': Permission denied
Click to expand...
Click to collapse
It still does not let me push 'sqlite3' to /system or /system/bin
That is what I need.
Thank you for any more pointers.
hap497 said:
Thank you. That seems to be an easier solution for me.
But after I did
I go to another shell and i did
It still does not let me push 'sqlite3' to /system or /system/bin
That is what I need.
Thank you for any more pointers.
Click to expand...
Click to collapse
Don't try to combine adb commands with shell commands.
Copy/move/push the file to your sdcard first.
Then open a root shell, mount it as rw, then copy the file from your sdcard to the directory you want.
Thanks. but I get 'failed on '/sdcard/sqlite3' - Cross-device link'
$ su
# mount -o remount,rw /dev/block/mtdblock3 /system
# mv /sdcard/sqlite3 /system/
failed on '/sdcard/sqlite3' - Cross-device link
# ls -l /sdcard/sqlite3
----rwxr-x system sdcard_rw 24120 2010-10-16 22:04 sqlite3
Click to expand...
Click to collapse
and i have tried:
# mv /mnt/sdcard/sqlite3 /system/bin/
failed on '/mnt/sdcard/sqlite3' - Cross-device link
# ls -l /mnt/sdcard/sqlite3
----rwxr-x system sdcard_rw 24120 2010-10-16 22:04 sqlite3
Click to expand...
Click to collapse
I get the 'sqlite3' from SuperOneClickv1.7-ShortFuse.zip.
Wholly crap, don't use the mv command! Bad idea!!! mv does not move the data, it moves the hardlink to the data! Thank your lucky stars mv wouldn't let you do it.
Use cp instead. cp will actually copy the data to where you're going.
Thank you. But I don't have 'cp' in my adb shell.
# cp
cp: not found
# /system/bin/cp
/system/bin/cp: not found
Click to expand...
Click to collapse
From here:
http://android-tricks.blogspot.com/2009/02/cp-on-android.html
I use 'cat' command to move to /system/bin
How do you have mv but not cp? Do you not have BusyBox installed?
No. I just need to search 'BusyBox' on Android market and install it? That is?
hap497 said:
Thank you. But I don't have 'cp' in my adb shell.
From here:
http://android-tricks.blogspot.com/2009/02/cp-on-android.html
I use 'cat' command to move to /system/bin
Click to expand...
Click to collapse
The cat command will work fine, no busybox needed: cat source_file > dest_file
efrant said:
The cat command will work fine, no busybox needed: cat source_file > dest_file
Click to expand...
Click to collapse
Woah there partner. Cat shouldn't be used on binary files, only ascii files. While it might work fine, it is not the recommended practice and really should not be done.
OP, Yes, BusyBox can be installed from the market.
GldRush98 said:
Woah there partner. Cat shouldn't be used on binary files, only ascii files. While it might work fine, it is not the recommended practice and really should not be done.
Click to expand...
Click to collapse
Really? I was unaware of that. It worked every time I used it.
efrant said:
Really? I was unaware of that. It worked every time I used it.
Click to expand...
Click to collapse
On standard Unix/Linux/etc. systems, cat works fine for binary files. It's only under DOS that cat or type shouldn't be used for binaries.
back in my ADB days.. itd say remount failed or w.e but i could still access my phone..
but i dont know.. ever since i switched to linux i stopped using ADB.. hahah

Can't Install OPPO ADB drivers, here's the solution

1. Install SDK tools http://forum.xda-developers.com/showthread.php?t=2199526
2. Connect oppo find 5
3. Install driver oppo via disc option "Android Composite ADB Interface", http://www.oppo.com/index.php?q=software/view&sw_id=631 (32/64bits)
4. open adb_usb.ini lacated at "C:\Users\<your username>\.android\adb_usb.ini" with notepad (if doesn't exist create one)
5. copy & paste/replace
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x22D9
For test, conect your phone with adb eneable and type into console:
adb devices
For fastboot usage:
fastboot -i 0x22D9 <command>
ex.
fastboot -i 0x22D9 reboot
eliaspizarro said:
1. Install SDK tools
....
Click to expand...
Click to collapse
Thanks, for the step 1 you should link to http://forum.xda-developers.com/showthread.php?t=2199526
eliaspizarro said:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x22D9
Click to expand...
Click to collapse
0x22D9 is for any Oppo type or just for Oppo Find 5?
Regards
OldClass said:
0x22D9 is for any Oppo type or just for Oppo Find 5?
Regards
Click to expand...
Click to collapse
i don't know if works on other oppo devices, but surely works on oppo find 5, how you can find device ID?
You need to search into device propierties -> Device managment -> select oppo device (or any android device), right click (properties)-> details-> id hardware:
a list appear, look for a number like 22D9, then replace into tutorial, 0x<number>.
ok my bro
but i want ask about push deodex using adb.
can you tell me how to push deodex using adb?
regards
OldClass said:
ok my bro
but i want ask about push deodex using adb.
can you tell me how to push deodex using adb?
regards
Click to expand...
Click to collapse
I haven't tried yet, but maybe:
0) get root AKA SuperSu or ChainfireSu
1) If you are on Oppo Frimware install adb insecure
then open the app and start service.
2) finally conect your phone and:
adb push <file.jar/apk> /system/bin (or wherever)
Note: if you are on CM10.1 skip step 0) and 1).
Universal Deodexer
eliaspizarro said:
I haven't tried yet, but maybe:
0) get root AKA SuperSu or ChainfireSu
1) If you are on Oppo Frimware install adb insecure
then open the app and start service.
2) finally conect your phone and:
adb push <file.jar/apk> /system/bin (or wherever)
Note: if you are on CM10.1 skip step 0) and 1).
Universal Deodexer
Click to expand...
Click to collapse
thanks for your tutorial
i'll try to push deodex (1 file) to /system/app but i got "no left space device", how to repair it?
should i delete some apps? how to delete it?
regards
OldClass said:
thanks for your tutorial
i'll try to push deodex (1 file) to /system/app but i got "no left space device", how to repair it?
should i delete some apps? how to delete it?
regards
Click to expand...
Click to collapse
from windows console CMD / linux terminal console
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
then, you can push
eliaspizarro said:
from windows console CMD / linux terminal console
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
then, you can push
Click to expand...
Click to collapse
ok, thanks
this is right?
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
chmod 644 /system/app/*
chown root.root /system/app/*
chmod 644 /system/framework/*
chown root.root /system/framework/*
exit
Regards
OldClass said:
ok, thanks
this is right?
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
chmod 644 /system/app/*
chown root.root /system/app/*
chmod 644 /system/framework/*
chown root.root /system/framework/*
exit
Regards
Click to expand...
Click to collapse
it's ok, another method is fix permissions through cwm
eliaspizarro said:
it's ok, another method is fix permissions through cwm
Click to expand...
Click to collapse
Thanks a lot for your help...
Sent from my Find 5 using xda premium
I can't get my ADB to work. I followed the steps and got it to saying: Android Composite ADB Interface in the device manager.
But when I cmd: adb devices it just says: List of Devices attached
then nothing..
I have my phone on USB debugging
Please Help?!
NVM Got it to work!
needed to reset the server
adb kill-server
then
adb start-server
Oppo find 5 no system
Hello guys I just reformatting my SDCARD before installing the ROM and am now no operating system installed on my computer ADB fastboot, PdaNet. After I install everything with the command window open and used the ADB PUSH command to copy my ROM to SDCARD, but it comes at a time that is a mistake and does not finish copying. Can someone help me?
After go to fastboot seems i need install some drivers to send commands to device, any help? What drivers i need to fastboot work?

[Q&A] Install or Mount (IOM) | Create chroot on device in minutes

Project thread created..
http://forum.xda-developers.com/showthread.php?t=2627255
install-or-mount-v0.8-gui.zip
Use this thread for help
Device List
Change Log
Sony Xperia P - CM11 4.4.2
Error with
Code:
handle_error mke2fs -qF -t $fs_type $IMGLOC/$IMGNAME
Needed another command.
ONDR4SH3K said:
Sony Xperia P - CM11 4.4.2
Error with
Code:
handle_error mke2fs -qF -t $fs_type $IMGLOC/$IMGNAME
Needed another command.
Click to expand...
Click to collapse
I figured that was gonna be an issue.
There are so many variants when it comes to device / busybox, I tried to get around that by including my own binary but fail on my part i guess...
Anyways.
Fix this line
Code:
LINE: 310 handle_error mke2fs -qF -t $fs_type $IMGLOC/$IMGNAME
to
Code:
handle_error mk2fs.ext2 $IMGLOC/$IMGNAME
userdelroot said:
I figured that was gonna be an issue.
There are so many variants when it comes to device / busybox, I tried to get around that by including my own binary but fail on my part i guess...
Anyways.
Fix this line
Code:
LINE: 310 handle_error mke2fs -qF -t $fs_type $IMGLOC/$IMGNAME
to
Code:
handle_error mk2fs.ext2 $IMGLOC/$IMGNAME
Click to expand...
Click to collapse
I rewrite with mke2fs -F $IMGLOC/$IMGNAME this working well.
But another problem with debootstrap. See attachment. So it's end of testing, isn't it?
ONDR4SH3K said:
I rewrite with mke2fs -F $IMGLOC/$IMGNAME this working well.
But another problem with debootstrap. See attachment. So it's end of testing, isn't it?
Click to expand...
Click to collapse
hmm...
I had that error initially also and I corrected it, probably should of documented what I fixed...
in the terminal type
uname
Is that a valid command?
change install-or-mount
Code:
LINE :333 handle_error debootstrap --no-check-gpg --extractor=ar --arch=armhf --foreign $DIST $MOUNT $MIRROR
to
Code:
handle_error debootstrap --no-check-gpg --extractor=ar --arch armhf --foreign $DIST $MOUNT $MIRROR
userdelroot said:
hmm...
I had that error initially also and I corrected it, probably should of documented what I fixed...
in the terminal type
uname
Is that a valid command?
Click to expand...
Click to collapse
Yes, it print Linux. I try another deboostrap. You use VERSION='1.0.40~ubuntu0.4'. So I find new one.
EDIT: New debootstrap with the same error.
ONDR4SH3K said:
Yes, it print Linux. I try another deboostrap. You use VERSION='1.0.40~ubuntu0.4'. So I find new one.
EDIT: New debootstrap with the same error.
Click to expand...
Click to collapse
Yea, it has to do with the line above I believe.
userdelroot said:
hmm...
I had that error initially also and I corrected it, probably should of documented what I fixed...
in the terminal type
uname
Is that a valid command?
change install-or-mount
Code:
LINE :333 handle_error debootstrap --no-check-gpg --extractor=ar --arch=armhf --foreign $DIST $MOUNT $MIRROR
to
Code:
handle_error debootstrap --no-check-gpg --extractor=ar --arch armhf --foreign $DIST $MOUNT $MIRROR
Click to expand...
Click to collapse
Sry, not working, but I deleted line with checking architecture and I got new error. See attachment.
EDIT:
I use:
sh install-or-mount -i -n linux.img -m /data/local/chroot -l /data/local -o precise -0
Rewrited mk2fs line in install-or-mount file to: mke2fs -F $IMGLOC/$IMGNAME
Deleted if [ -z "$ARCH" ] || [ -z "$HOST_OS" ]; then error 1 WHATARCH "Couldn't work out current architecture" fi line in deboostrap file
I think if I deleted this line, chroot not mounted correctly and bootstrap can't continue. So we need figure out, how fix architecture error.
I found this: http://uyirpodiru.blogspot.cz/2012/08/debootstrap-error-e-couldnt-work-out.html
ONDR4SH3K said:
Sry, not working, but I deleted line with checking architecture and I got new error. See attachment.
EDIT:
I use:
sh install-or-mount -i -n linux.img -m /data/local/chroot -l /data/local -o precise -0
Rewrited mk2fs line in install-or-mount file to: mke2fs -F $IMGLOC/$IMGNAME
Deleted if [ -z "$ARCH" ] || [ -z "$HOST_OS" ]; then error 1 WHATARCH "Couldn't work out current architecture" fi line in deboostrap file
I think if I deleted this line, chroot not mounted correctly and bootstrap can't continue. So we need figure out, how fix architecture error.
I found this: http://uyirpodiru.blogspot.cz/2012/08/debootstrap-error-e-couldnt-work-out.html
Click to expand...
Click to collapse
All the errors you are getting I did get at one point, I forgot how I fixed them, cause I was working on another project..
Ill do some testing, as I am working on the code right now.
Ill post when I find a solution to those..
Also before continuing I wanted to just let you know.
the debootstrap requires 'ar' archiver which I do not believe comes with CM.
busybox ar
That is why I included my own version.
I may have some work arounds tho so give me a few..
userdelroot said:
All the errors you are getting I did get at one point, I forgot how I fixed them, cause I was working on another project..
Ill do some testing, as I am working on the code right now.
Ill post when I find a solution to those..
Also before continuing I wanted to just let you know.
the debootstrap requires 'ar' archiver which I do not believe comes with CM.
busybox ar
That is why I included my own version.
I may have some work arounds tho so give me a few..
Click to expand...
Click to collapse
New vesion 0.2 in attachment. Is on the way.
EDIT: I put busybox from /sbin to /system/xbin and it looks like deboostrap working, but you have error with Release. Attachment no.3.
Thanks for helping.
is it normall ubuntu for desktop or Ubuntu phone version?
desktop
JFizDaWiz said:
desktop
Click to expand...
Click to collapse
I'm confused
Does touch work? Or do we need OTG cables
milestoneman said:
I'm confused
Does touch work? Or do we need OTG cables
Click to expand...
Click to collapse
You need root, and an android device.
No OTG cables..
It build's a chroot image on the device, with android running in the background.
You can run X windows (only LXDE currently because it is lightwieght) on the device and then vnc into it from anywhere, even a desktop...
There are other tools out there for this however, they require you to download the images. Which are usually between 1gig - 4gigs.
Instead of downloading the images, this creates the image and only downloads approximately 200megs for the packages.
Thanks for the explanation, sounds great
Sent from my Nexus 7 using Tapatalk
ONDR4SH3K said:
New vesion 0.2 in attachment. Is on the way.
EDIT: I put busybox from /sbin to /system/xbin and it looks like deboostrap working, but you have error with Release. Attachment no.3.
Thanks for helping.
Click to expand...
Click to collapse
Yea, crap, that was my bad, I should check where the system busybox is installed. It should default to /system/xbin
But some roms I guess put it in /system/sbin ? Possibly a typo on the rom developers part? LOL
Anyways, I will add code to correct this.
EDIT: How did you fix image 2?, as it should stop at the error in image type every time.
At any rate, image 2 error is because it can't find sh. in the install-or-mount/bin directory type this..
ls -l bin/
Make sure sh is symlinked to /system/bin/sh or /system/xbin/busybox if not that is causing the error in picture 2
it should look like this...
ls -l bin/
sh sh -> /system/xbin/busybox
If you don't see that do the following:
cd /data/local/install-or-mount
busybox touch bin-configs/sh
rm -rf .bin-configs-done
if you have something like that it should be ok, however to be safe since you moved you your busybox
from inside install-or-mount
rm -rf .bin-configs-done
Yes there is a DOT in front of bin-configs-done
I receive a permission denied error with debootstrap as well
Edit: crap I didn't see all the replies up there
Sent from my GT-N7105 using Tapatalk
Will it works on my armv7 single core tablet?
I fix it other way:
mount -o remount,rw /system
cp busybox /sbin /system/xbin
mount -o remount,ro /system
I hope that commands are fine.
I has no solution for fetch Release error, yet. I tried rewrite URL, but unsussesful.
Its in scripts folder line mirror_styles Release
Sent from my Xperia P using xda app-developers app
---------- Post added at 01:06 AM ---------- Previous post was at 01:00 AM ----------
Already testing on armv7 device dual core. OP must fix a few errors but you can try it.
Sent from my Xperia P using xda app-developers app

Categories

Resources