Related
Ok , I know there is thread about debian running fine on desire z but the tutorial there is highly unfriendly and there are some other stuff you need to do to your desire z. This is my first guide. The reason for posting in dev thread is because chroot and loop requires specific kernel support to power Ubuntu.
Just to explain certain terms here...
Kernel - the interface for android to access hardware. Note that andorid is stripped down version of ubuntu and it does not have loopdevice support
Loopdevice - Imagine virtual disk mount program such as Daemon tools. This requires specifically supported kernels such
Following tutorial will void your warrenty (root and s off) but you can change to warrenty friendly state of course XD Check out xda wiki for more info( study to know what you are doing there.)
There are plenty of guides to get su and busybox( allows android system to be able to utilise more advanced commands) so check out comprehensive guides for g2 and desirez in this wiki below is my version
-------------------------------------------------------------------------
If your phone is stock, do a lot of research before doing root and s off. cyanogenmod has good guide on wiki for you to s off and get permanet root. Just for you to know, s off is to disable security for us to flash new kernel with loopback support and root is well... needed for most of hacks in XDA XD
*note for noobs: this is tested with desire z but G2 should not have problems. just be careful of which device's gfree you are using to s off.
ENGINEERING HBOOT IS NOT REQUIRED FOR THIS AND IS NOT RECOMMENDED FOR YOU TO DO SO AS IT MAY BRICK YOUR PHONE YOU SHOULD NOT HAVE PROBLEMS FLASHING CUSTOM ROM/KERNEL WITHOUT IT (guides are confusing if custom roms require flashing hboot)
Preparation:
1. busybox (install titanium backup and under problems? you can install busybox in a easy way)
2. Recommended: Clockwork recovery(rom manager in market)
3.Root and S off
4.Optional : remove or move sd card installed apps to internal memory or else LOOPDEVICE may be occupied and you may not be able to mount ubuntu. Do this if you encounter error (caused by app2 sd) please note that recent builds in xda mount loop device as 255 to avoid this problem.
You might want to use adb if necessary
5. android terminal from market
6. 2gb free space in sdcard (certain builds use 4gb as storage image, which is limit for fat32 system)
---------Kernel preparation ---------------------------------
Flashing necessary kernel
1. Download suitable kernel with loop device support. I am using cyanogen -> virtuous-kernel-cyanogen kernel from ://files.virtuousrom.com/vision/kernels/
(add http infront) on Stock HTC Sense Rom
2. To flash this, from rom manager, boot into clockworkmod recovery and select zip file to flash. Nandroid backup is recommended beforehand
-------------------------------------------------------------------
Now your phone has loopback support to chroot into UBUNTU or DEBIAN
Well, this method is not native ubuntu but it works fine.
You can now follow any guide on XDA like G1,nexus 1etc on running linux in android. I recommend nexus 1 hacks .com for ubuntu setup or thread "Debian for Desire" for debian setup (note debian seems to have problem with vnc) there are a lot of newbie frendly guides to do this without partitioning your sd card.
What can you do with them? You can use full android terminal , use vim , open office, gcc or eclipse etc ... makes your HTC Vision true small computer with keyboard . Enjoy
Possible solution to errors you encounter while following chroot tutorial for other android devices:
-----------------trouble shoot--------------------------------
Errors:
/device/loop is busy etc.... chroot: cannot execute /bin/bash etc... shutting down ubnutu etc....
Solution: 1. Get loopback support by flashing above kernel i mentioned
if not 2. TYPE SU BEFORE YOU RUN BOOTSCRIPT ON ANDROID TERMINAL
or if they say the bootscript is not found then type sh ./*your boot script name*
if not 3. move sd apps to phone as i mentioned eariler
Other errors could be from not installing busybox.
Note that in some cases, busybox is included inside the custom rom so you dont need to install it.
Post names of kernels with ability to run ubuntu for others to know.I did not test all of them.
This is my first guide on xda and i hope this helped xda in constructive way...
Post script: I will try my best to maintain quality of the posts to be up to xda standard. Thank you for constructive feedbacks...
quick problem i noticed
I'm running post ota de-odexed and I installed virtuous-kernel_vision_advanced-v1.0.9.zip in attempts to get loopdevice but now my phone doesn't react to an touch... hahaha it's no biggie I can't fix, just wanted to state out a weird outcome I have never seen before
But hey! Your prep guide is much appreciated!
EDIT: All of the 1.0.9 kernels seem to break my touch :/
you need virtuous-cyanogen 1.3 not standard vituous kennel. it is under cyanogen. Since it is developed for cyanogen, it should be fine for wide range of roms including sense roms but yes, it is buggy. I am looking for better kennel now....
squarememory said:
Ok , I know there is thread about debian running fine on desire z but the tutorial there is highly unfriendly and there are some other stuff you need to do to your desire z. This is my first guide. The reason for posting in dev thread is because chroot and loop requires specific kennel support to power Ubuntu. Well, do not attempt this unless you can use computer well XD
Following tutorial will void your warrenty (root and s off) but you can change to warrenty friendly state of course XD Check out xda wiki for more info( study to know what you are doing there.)
-------------------------------------------------------------------------
If your phone is stock, do a lot of research before doing root and s off. cyanogenmod has good guide on wiki for you to s off and get permanet root. Just for you to know, s off is to disable security for us to flash new kennel with loopback support and root is well... needed for most of hacks in XDA XD
*note for noobs: this is tested with desire z but G2 should not have problems. just be careful of which device's gfree you are using to s off.
ENGINEERING HBOOT IS NOT REQUIRED FOR THIS AND IS NOT RECOMMENDED FOR YOU TO DO SO AS IT MAY BRICK YOUR PHONE YOU SHOULD NOT HAVE PROBLEMS FLASHING CUSTOM ROM/KENNEL WITHOUT IT (guides are confusing if custom roms require flashing hboot)
----------------------------------------------------------------
Preparation:
1. busybox (install titanium backup and under problems? you can install busybox in a easy way)
2. Recommended: Clockwork recovery(rom manager in market)
3.Root and S off
4.Optional : remove or move sd card installed apps to internal memory or else LOOPDEVICE may be occupied and you may not be able to mount ubuntu. Do this if you encounter error (caused by app2 sd)...
adb if you want to type things in cmd
5. android terminal from market
6. 2gb free space in sdcard
---------Kernel preparation (may not be needed in some custom roms)---------------------------------
Flashing necessary kernel
1. Download suitable kernel with loop device support. I am using cyanogen -> virtuous-kennel-cyanogen kennel from ://files.virtuousrom.com/vision/kernels/
(add http infront) on Stock HTC Sense Rom
2. To flash this, from rom manager, boot into clockworkmod recovery and select zip file to flash. Nandroid backup is recommended beforehand
-------------------------------------------------------------------
Now your phone has loopback support to chroot into UBUNTU or DEBIAN
You can now follow any guide on XDA like G1,nexus 1etc on running linux in android. I recommend nexus 1 hacks .com for ubuntu setup or thread "Debian for Desire" for debian setup (note debian seems to have problem with vnc)
What can you do with them? You can use full android terminal , use vim , open office, gcc or eclipse etc ... makes your HTC Vision true small computer with keyboard . Enjoy
Possible solution to errors you encounter while following chroot tutorial for other android devices:
-----------------trouble shoot--------------------------------
Errors:
/device/loop is busy etc.... chroot: cannot execute /bin/bash etc... shutting down ubnutu etc....
Solution: 1. Get loopback support by flashing above kennel i mentioned
if not 2. TYPE SU BEFORE YOU RUN BOOTSCRIPT ON ANDROID TERMINAL
or if they say the bootscript is not found then type sh ./*your boot script name*
if not 3. move sd apps to phone as i mentioned eariler
Other errors could be from not installing busybox.
Note that in some cases, busybox is included inside the custom rom so you dont need to install it.
Post names of kennels with ability to run ubuntu for others to know.I did not test all of them.
This is my first guide on xda and i hope this helped xda in constructive way...
Click to expand...
Click to collapse
it's KERNEL! not KENNEL!
teh5abiking said:
it's KERNEL! not KENNEL!
Click to expand...
Click to collapse
Really dude? That was the only time he mispelled it and you the spelling police make a lousey post as if he mispelled it everytime...get a life
Sent from my HTC Vision using XDA Premium App
Well thanks for spelling correction. English is not my primary language
Spastic909 said:
Really dude? That was the only time he mispelled it and you the spelling police make a lousey post as if he mispelled it everytime...get a life
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Tell it spastic tell it!
xsteven77x said:
Tell it spastic tell it!
Click to expand...
Click to collapse
I thought you were insulting him XD
I have installed ubuntu without a hitch, but how do i fix the incorrect key bindings?
im thinking of using the technique that uses vnc to access ubuntu on my desire z. i am running 2.3.3 (cyanogenmod-7.1.0) on it. now forgive me for asking this its nearly 1am and im exhausted so my brain is not working right. which version of the kernel am i best getting for this? im a novice at it all but i do want to make sure i do it properly and dont brick my phone.
traumatism said:
im thinking of using the technique that uses vnc to access ubuntu on my desire z. i am running 2.3.3 (cyanogenmod-7.0.0) on it. now forgive me for asking this its nearly 1am and im exhausted so my brain is not working right. which version of the kernel am i best getting for this? im a novice at it all but i do want to make sure i do it properly and dont brick my phone.
Click to expand...
Click to collapse
This is a thread about installing ubuntu on the phone, not accessing it from the phone.
tsubus said:
This is a thread about installing ubuntu on the phone, not accessing it from the phone.
Click to expand...
Click to collapse
*facepalms* yes i know that. i will be installing it along side android and using vnc to access it locally. its a method i wish to use but i need the kernel for installing ubuntu and want to know which one. i shoulda made it more clear really.
ive just tried flashing the latest kernel for cyanogen with 7.1 but it freezes at the HTC screen on boot. any assistance will be apreciated
This is now included in my MoDaCo Custom ROM for the Galaxy Nexus - details.
I have created a custom kernel for those that would like CIFS support or USB drive / keyboard / mouse support. This is a temporary download until such time as MCR is released. This is based on the stock kernel source with purely config tweaks at this time.
This should be flashed via ClockworkMod Recovery.
This is designed for devices running the I9250XXKK1 / ITL41D ROM.
DOWNLOAD - MD5: 4eb172c3222126ceb3eed340f51c7b28
P
Note: Source is now available in my bitbucket repository.
Thanks Paul.
Just two things:
1. You say try using 'fastboot boot' rather than 'fastboot boot' in your post. Just a heads up so you can fix that.
2. So the Galaxy Nexus does not support USB storage out of the box? It needs kernel modifications to make it work?
Thanks for all your hard work.
Stigy said:
Thanks Paul.
Just two things:
1. You say try using 'fastboot boot' rather than 'fastboot boot' in your post. Just a heads up so you can fix that.
2. So the Galaxy Nexus does not support USB storage out of the box? It needs kernel modifications to make it work?
Thanks for all your hard work.
Click to expand...
Click to collapse
1. I think he wanted to say [use 'fastboot boot' rather than 'fastboot flash' to try before flashing].
2. I think he added HID support to the kernel.
Guys any tut on how to flash those md5 files of paul?
DJTaurus said:
Guys any tut on how to flash those md5 files of paul?
Click to expand...
Click to collapse
md5 is not a file, it's a checksum. You flash modified boot.img with custom kernel using fastboot flash boot boot.mck.img (as mentioned in the first post). You need to boot your device in fastboot mode on device with unlocked bootloader. Or maybe I didn't understand the question?
mike1986. said:
md5 is not a file, it's a checksum. You flash modified boot.img with custom kernel using fastboot flash boot boot.mck.img (as mentioned in the first post). You need to boot your device in fastboot mode on device with unlocked bootloader. Or maybe I didn't understand the question?
Click to expand...
Click to collapse
Ok so how do we flash those img's?
1.Boot into fastboot
2.Then connect GN with PC
3..?
DJTaurus said:
Ok so how do we flash those img's?
1.Boot into fastboot
2.Then connect GN with PC
3..?
Click to expand...
Click to collapse
then open terminal and type the command
mike1986. said:
then open terminal and type the command
Click to expand...
Click to collapse
I ll have to wait for the online kitchen then.
I never got the android sdk properly installed on the pc
questions
Sorry, REALLY a newbie here
1. What is CISF and MCR?
2. So, the GN doesn't have HID support at first? I thought that's one of their features
3. Can u make a more detailed tutorial? It's really my first time using boot/flash or whatever it is
xinn3r said:
Sorry, REALLY a newbie here
1. What is CISF and MCR?
2. So, the GN doesn't have HID support at first? I thought that's one of their features
3. Can u make a more detailed tutorial? It's really my first time using boot/flash or whatever it is
Click to expand...
Click to collapse
1. CIFS - http://searchcio-midmarket.techtarget.com/definition/Common-Internet-File-System
MCR - Modaco Custom ROM
2. Not sure about that.
3. If you don't know what CIFS is then why you want to flash this? I mean no disrespect to anyone but if you don't know what something is and you don't know how to flash it then don't flash it. Better wait for ready ROMs (mine is ready but still waiting for working recovery) with custom kernels. Shouldn't take long
mike1986. said:
1. CIFS - http://searchcio-midmarket.techtarget.com/definition/Common-Internet-File-System
MCR - Modaco Custom ROM
2. Not sure about that.
3. If you don't know what CIFS is then why you want to flash this? I mean no disrespect to anyone but if you don't know what something is and you don't know how to flash it then don't flash it. Better wait for ready ROMs (mine is ready but still waiting for working recovery) with custom kernels. Shouldn't take long
Click to expand...
Click to collapse
OK, let me start from the beginning
I was really interested with the Galaxy Nexus
Then when I found out that it didn't have SD card slot, I was really bummed
I was planning on using the GN for watching alot of movies, but without a external storage, it's hard to store alot of files at once (particularly HD videos)
Then I learned that GN was able to use USB OTG
So, I thought of using a flash drive to store my movies, then just plug it into the GN if I wanted to watch something
That's why I was really interested in this costum kernel
I wanted to use the Vanilla Android, if I use modded ROMs, will the themes change?
Having trouble using CifsManager, phone crashes and reboots when I attempt to mount.
xinn3r said:
OK, let me start from the beginning
I was really interested with the Galaxy Nexus
Then when I found out that it didn't have SD card slot, I was really bummed
I was planning on using the GN for watching alot of movies, but without a external storage, it's hard to store alot of files at once (particularly HD videos)
Then I learned that GN was able to use USB OTG
So, I thought of using a flash drive to store my movies, then just plug it into the GN if I wanted to watch something
That's why I was really interested in this costum kernel
I wanted to use the Vanilla Android, if I use modded ROMs, will the themes change?
Click to expand...
Click to collapse
A "custom" kernel is not the same as a ROM, this "custom" kernel will only change the kernel and nothing else.
I put quotes around "custom" as this is just the same kernel but with a few flags enabled.
Also for whatever it's worth, USB-OTG is supposed to be supported by the GN, so it may just be an oversight that they didn't enable module support for it already, so it may come in a future update.
FISKER_Q said:
A "custom" kernel is not the same as a ROM, this "custom" kernel will only change the kernel and nothing else.
I put quotes around "custom" as this is just the same kernel but with a few flags enabled.
Also for whatever it's worth, USB-OTG is supposed to be supported by the GN, so it may just be an oversight that they didn't enable module support for it already, so it may come in a future update.
Click to expand...
Click to collapse
Yes, that's my point, I just want the kernel to be modified, I don't want a costum ROM, that's why I was asking for a tutorial how to do this
suppose that I want to use this kernel,
what will happen when an ota update will be released?
should I reflash this kernel to have the usb host feature?
---------- Post added at 06:01 PM ---------- Previous post was at 05:58 PM ----------
If you want the usb host enabled via official firmware/kernel please write here and ask it to google.
http://code.google.com/p/android/issues/detail?id=22038&thanks=22038&ts=1321813429#makechanges
xinn3r said:
Yes, that's my point, I just want the kernel to be modified, I don't want a costum ROM, that's why I was asking for a tutorial how to do this
Click to expand...
Click to collapse
Obtain Fastboot, if you don't know where to get it, just download this package from Modaco: http://android.modaco.com/topic/348161-18-nov-r2-superboot-rooting-the-galaxy-nexus/
You'll only need "Fastboot-windows.exe" provided you use windows.
Extract it to say c:\android\
Rename it to fastboot.exe (it's not nessecary, but since most guides assume you have "fastboot.exe" it would eliminate some confusion)
Download the kernel from the post
Copy that to c:\android\
Open a command prompt (cmd)
Navigate to c:\android\
Enter Fastboot mode (Shutdown the phone, and then hold down both volume buttons while powering up) you can confirm it's presence by entering "fastboot devices"
If your device is not already unlocked (There's an opened lock icon when you boot up) you will have to execute the following command: (This will void your warranty)
fastboot oem unlock
After that you simply do this to install the new kernel:
fastboot flash boot boot.mck.img
FISKER_Q said:
Obtain Fastboot, if you don't know where to get it, just download this package from Modaco: http://android.modaco.com/topic/348161-18-nov-r2-superboot-rooting-the-galaxy-nexus/
You'll only need "Fastboot-windows.exe" provided you use windows.
Extract it to say c:\android\
Rename it to fastboot.exe (it's not nessecary, but since most guides assume you have "fastboot.exe" it would eliminate some confusion)
Download the kernel from the post
Copy that to c:\android\
Open a command prompt (cmd)
Navigate to c:\android\
Enter Fastboot mode (Shutdown the phone, and then hold down both volume buttons while powering up) you can confirm it's presence by entering "fastboot devices"
If your device is not already unlocked (There's an opened lock icon when you boot up) you will have to execute the following command: (This will void your warranty)
fastboot oem unlock
After that you simply do this to install the new kernel:
fastboot flash boot boot.mck.img
Click to expand...
Click to collapse
Thx alot for the tutorial!
mike1986. said:
1. CIFS - http://searchcio-midmarket.techtarget.com/definition/Common-Internet-File-System
MCR - Modaco Custom ROM
2. Not sure about that.
3. If you don't know what CIFS is then why you want to flash this? I mean no disrespect to anyone but if you don't know what something is and you don't know how to flash it then don't flash it. Better wait for ready ROMs (mine is ready but still waiting for working recovery) with custom kernels. Shouldn't take long
Click to expand...
Click to collapse
How do you use cifs? I'm not quite understanding if it enables the use of server/client type apps such as printershare, idisplay, and splashtop, or if its simply a seperate client. If so, where do you download its companion program in windows? Or is it some kind of cmd prompt only deal?
Since this just resets several flags in the stock ROM will this kernel work with the VZW LTE version of GN when we finally get it, or will a different kernel be needed, or don't know yet?
Wow, do you mean we're getting Revolution for GN?
Since Clockwordmod has been updated, everything is ready.
My GN is on the plane, can't wait!!
Sent from my Nexus S using xda premium
So I've tried searching on here, I've tried googling to no success...So time for my first post on this site I guess.
I have an Acer Iconia Tab A100 running stock ICS (rooted) which now stops during its boot sequence.
I've read that when a device is bricked it stops at the Acer logo on boot, mine goes past this but stops before the Android logo appears.
Stuff I did before this happened:
- Friend rooted my device for me using a guide from these forums.
- I tried seeing what I can do with Superuser permissions and got used to the new features.
- Wanted an app that wasn't compatible with my device so I tried using a Device Spoofer to make my device appear as an HTC Thunderbolt.
- Realized it didn't work still so I used the device spoofer to restore back to my default device.
- Device rebooted and I am now stuck between the Acer logo and the Android logo on boot.
Am I bricked and screwed out of a device?
Is there a way to recover my device/restore to factory?
Any help is appreciated. You all most likely know more that I do.
EDIT: The guide that was followed to root: http://forum.xda-developers.com/showthread.php?t=1531646&highlight=root
phracture said:
So I've tried searching on here, I've tried googling to no success...So time for my first post on this site I guess.
I have an Acer Iconia Tab A100 running stock ICS (rooted) which now stops during its boot sequence.
I've read that when a device is bricked it stops at the Acer logo on boot, mine goes past this but stops before the Android logo appears.
Stuff I did before this happened:
- Friend rooted my device for me using a guide from these forums.
- I tried seeing what I can do with Superuser permissions and got used to the new features.
- Wanted an app that wasn't compatible with my device so I tried using a Device Spoofer to make my device appear as an HTC Thunderbolt.
- Realized it didn't work still so I used the device spoofer to restore back to my default device.
- Device rebooted and I am now stuck between the Acer logo and the Android logo on boot.
Am I bricked and screwed out of a device?
Is there a way to recover my device/restore to factory?
Any help is appreciated. You all most likely know more that I do.
Click to expand...
Click to collapse
Is cwm or twrp recovery installed?
Sent via G2x on temasek b135.2 w/ Trinity TD1.58 kernel (testing)
justjackyl said:
Is cwm or twrp recovery installed?
Sent via G2x on temasek b135.2 w/ Trinity TD1.58 kernel (testing)
Click to expand...
Click to collapse
I don't believe either was installed. Is there anyway to fix this problem without those?
phracture said:
I don't believe either was installed. Is there anyway to fix this problem without those?
Click to expand...
Click to collapse
Well for starters what happened was that tool wrecked build.prop which sits in /system. Not a bug issue except it won't be fixed by resetting, you need to replace/repair build.prop or flash a whole new system to it. Did you enable debugging before doing this? If so adb might be used to repair the damage. If not you'll need to flash an official acer ICS ROM by placing it on the root of external SD named update.zip then power on holding the volume key closest to the lock switch.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
pio_masaki said:
Well for starters what happened was that tool wrecked build.prop which sits in /system. Not a bug issue except it won't be fixed by resetting, you need to replace/repair build.prop or flash a whole new system to it. Did you enable debugging before doing this? If so adb might be used to repair the damage. If not you'll need to flash an official acer ICS ROM by placing it on the root of external SD named update.zip then power on holding the volume key closest to the lock switch.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
Click to expand...
Click to collapse
Ahhh okay I think that makes sense to me, and yes I believe I had debugging turned on so I should be able to fix this I guess fairly simply.
Thanks so much will post to say if I've solved or ran into trouble once i get home.
pio_masaki said:
Well for starters what happened was that tool wrecked build.prop which sits in /system. Not a bug issue except it won't be fixed by resetting, you need to replace/repair build.prop or flash a whole new system to it. Did you enable debugging before doing this? If so adb might be used to repair the damage. If not you'll need to flash an official acer ICS ROM by placing it on the root of external SD named update.zip then power on holding the volume key closest to the lock switch.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
Click to expand...
Click to collapse
Could someone be nice enough as to tell me how to access my device to put the build.prop on it?
I have installed adb and downloaded the files for 4.0.3 using android ADK. I see the build.prop file that I need. However when i try to run adb.exe to see how the program works, I just get a window which scrolls through a large amount of text before closing.
EDIT: I am running windows 7 x64. Would this be easier if I tried using adb on my laptop which runs Ubuntu?
phracture said:
Could someone be nice enough as to tell me how to access my device to put the build.prop on it?
I have installed adb and downloaded the files for 4.0.3 using android ADK. I see the build.prop file that I need. However when i try to run adb.exe to see how the program works, I just get a window which scrolls through a large amount of text before closing.
EDIT: I am running windows 7 x64. Would this be easier if I tried using adb on my laptop which runs Ubuntu?
Click to expand...
Click to collapse
First you need to have the acer drivers installed. Second the tab will need to be booted to the recovery to be seen.
Place the build.prop you need to push to the device in the platform tools folder (the one with adb.exe). Make sure the name is properly build.prop
**There are modded ones here in the dev section here that will work, speed up your tab and/or rename it to an A500 to get more apps.
Open a command propt in the platform-tools folder (shift-right click)
type
adb devices
There should be a device listed
type
adb push build.prop /system
Your done, type reboot
It should reboot with the new build.prop
phracture said:
Could someone be nice enough as to tell me how to access my device to put the build.prop on it?
I have installed adb and downloaded the files for 4.0.3 using android ADK. I see the build.prop file that I need. However when i try to run adb.exe to see how the program works, I just get a window which scrolls through a large amount of text before closing.
EDIT: I am running windows 7 x64. Would this be easier if I tried using adb on my laptop which runs Ubuntu?
Click to expand...
Click to collapse
Open a terminal then cd to where you have adb.exe then run it that way, otherwise it just scrolls help and closes like you saw.
Power on and once it gets stuck booting try
adb devices
And see if it shows up, if it does do
adb pull /system/build.prop
This pulls it to where adb.exe is, from there you can check it for errors or even upload it and we can check it out.
Tapatalked from my Galaxy Nexus - CN(A)
Excuse me for butting in but wouldnt it be easer for him to just do the SD card. A lot less confusing at least fo me..
pio_masaki said:
Open a terminal then cd to where you have adb.exe then run it that way, otherwise it just scrolls help and closes like you saw.
Power on and once it gets stuck booting try
adb devices
And see if it shows up, if it does do
adb pull /system/build.prop
This pulls it to where adb.exe is, from there you can check it for errors or even upload it and we can check it out.
Tapatalked from my Galaxy Nexus - CN(A)
Click to expand...
Click to collapse
I'd be fine with uploading it for you guys to check out, but first I need adb to find my device.
I made sure I have the Acer drivers installed, but when I plug it in and run "adb devices" I get no devices listed.
I tried both at the screen where it stops loading as you said and at the recovery screen as Romman0 said.
Romman0 said:
First you need to have the acer drivers installed. Second the tab will need to be booted to the recovery to be seen.
Place the build.prop you need to push to the device in the platform tools folder (the one with adb.exe). Make sure the name is properly build.prop
**There are modded ones here in the dev section here that will work, speed up your tab and/or rename it to an A500 to get more apps.
Open a command propt in the platform-tools folder (shift-right click)
type
adb devices
There should be a device listed
type
adb push build.prop /system
Your done, type reboot
It should reboot with the new build.prop
Click to expand...
Click to collapse
I tried that and no devices are listed as I said above.
Also, the shift+right click blew my mind. That could've been and will be very useful to save me time.
phracture said:
I'd be fine with uploading it for you guys to check out, but first I need adb to find my device.
I made sure I have the Acer drivers installed, but when I plug it in and run "adb devices" I get no devices listed.
I tried both at the screen where it stops loading as you said and at the recovery screen as Romman0 said.
I tried that and no devices are listed as I said above.
Also, the shift+right click blew my mind. That could've been and will be very useful to save me time.
Click to expand...
Click to collapse
So I still haven't gotten my device to be recognized. Should I try to connect using Ubuntu or Mac OS?
As I was told before, there is something i can do where i put the android API in an update.zip and place it on an external SD. By external SD does this mean micro SD card? Could this solve my problem potentially?
phracture said:
So I still haven't gotten my device to be recognized. Should I try to connect using Ubuntu or Mac OS?
As I was told before, there is something i can do where i put the android API in an update.zip and place it on an external SD. By external SD does this mean micro SD card? Could this solve my problem potentially?
Click to expand...
Click to collapse
Yes the microsd. And yes, if you flash the ICS stock ROM http://forum.xda-developers.com/showthread.php?t=1611696
It will fix it to. Rename to update.zip then place it on your microsd card, power off and boot recovery by pressing both the power and volume rocker closest to the corner at the same time until it starts updating.
Romman0 said:
Yes the microsd. And yes, if you flash the ICS stock ROM http://forum.xda-developers.com/showthread.php?t=1611696
It will fix it to. Rename to update.zip then place it on your microsd card, power off and boot recovery by pressing both the power and volume rocker closest to the corner at the same time until it starts updating.
Click to expand...
Click to collapse
Thanks for confirming and giving me that link. Problem is solved. Thanks everyone for helping a noob out.
Instructions for flashing a phone or tablet device with Ubuntu
What to expect after flashing
Flashing the device
Step 1 - Desktop Setup
Setup the Touch Developer Preview Tools PPA
Step 2 - Device unlock
Step 3 - Initial Device Setup
Step 4 - Deploying Image to Device
Restoring Android
Need help?
The Ubuntu Touch Developer Preview is intended to be used for development and evaluation purposes only. It does not provide all of the features and services of a retail phone and cannot replace your current handset. This preview is the first release of a very new and unfinished version of Ubuntu and it will evolve quickly. If you want to install this release, please follow the guide provided, which details the available features and how to navigate the user experience.
This process will delete all data from the device. Restoring Android will not restore this data.
What to expect after flashing
For detailed information check the release notes
Shell and core applications
Connection to the GSM network (on Galaxy Nexus and Nexus 4)
Phone calls and SMS (on Galaxy Nexus and Nexus 4)
Networking via Wifi
Functional camera (front and back)
Device accessible through the Android Developer Bridge tool (adb)
Supported devices and codenames
The table below lists the supported devices and their corresponding factory images, should you want to switch back to Android. The images can be found here.
Device
Codename
Factory firmware from Google
Galaxy Nexus
maguro
takju or yakju
Nexus 4
mako
occam
Nexus 7
grouper
nakasi or nakasig
Nexus 10
manta
mantaray
Flashing the device
Step 1 - Desktop Setup
The following steps are required on your desktop system that you'll need in order to flash and communicate with the device.
Setup the Touch Developer Preview Tools PPA
The PPA has the tools and dependencies to support Precise, Quantal and Raring. Add the Ubuntu Touch PPA by adding the following custom source list entry to your /etc/apt/sources.list file.
sudo add-apt-repository ppahablet-team/tools
Then do the following:
sudo apt-get update
sudo apt-get install phablet-tools android-tools-adb android-tools-fastboot
Step 2 - Device unlock
If the device is already unlocked, skip to Step 3. These steps will wipe all personal data from the device.
With the device powered off, power on the device by holding the Power button + volume up + volume down.
The device will boot into the bootloader.
Plug the device into the computer via the USB cable.
On your computer, press Ctrl+Alt+T to start a terminal. Type sudo fastboot oem unlock, followed by Enter
On the device screen, accept the terms of unlocking.
Boot the device by pressing the power button (pointed by an arrow with Start on the screen).
Step 3 - Initial Device Setup
Follow these initial steps on your device:
If not booted, boot the device into Android
Enable USB debugging on the device
on Ice Cream Sandwich (version 4.0) go to Settings and turn on USB Debugging (Settings > System > Developer options > USB debugging).
on Jelly Bean (versions 4.1 and 4.2) you need to enter Settings, About [Phone|Tablet] and tap the Build number 7 times to see the Developer Options, activate USB Debugging via Settings > Developer options > USB debugging.
on 4.2.2 you will need to accept a host key on the device, if you already had adb installed, do the following
On the workstation-> adb kill-server; adb start-server
Plug the device into the computer via the USB cable.
Depending on the installed Android version, a popup will show up on the device with the host key that needs to be accepted for the device to communicate with the workstation.
Save the version of the current image on the device, if on Android, to use as a reference to revert back to. The version can be found by going to Settings > About Phone > Build Number.
Step 4 - Deploying Image to Device
To install the Ubuntu Touch Developer Preview on your device, you will need to execute the command below. Please note, this will wipe the contents of the device so ensure you have made a back-up. To install and get updates, run the following command:
phablet-flash -b
The -b performs a full bootstrap on the device. If the device is already unlocked it will carry on. If you have already bootstrapped once and want to install a daily just do:
phablet-flash
This will deploy the latest build onto your device. Your device should reboot into the Ubuntu Unity shell.
Note: the files are saved in Downloads/phablet-flash.
Restoring Android
The Ubuntu Touch Preview image is not for everyone and may not suit your current needs (yet). If you wish to roll back to an Android factory image, follow these steps:
Recall the version that was installed before flashing.
Download the factory image corresponding to your device's model and version (initial table has links).
Ensure the device is connected and powered on.
Extract the downloaded file and chdir into the extracted directory.
run adb reboot-bootloader
run ./flash-all.sh (use sudo if lack of permissions on the workstation don't allow you to talk to the device).
Your device should boot into Android after the process is finished.
Click to expand...
Click to collapse
Need help?
If you got lost somewhere, you found a bug or need some help, we're happy to help you. The Touch Developer Preview is put together by a community of many, who are eager to work together with you on this.
If you've got any troubles or questions with these installation instructions, there's a community willing to help: just ask on Ask Ubuntu!
You can also:
Join us on IRC in #ubuntu-phone on irc.freenode.net and/or
Join our mailing list by
Joining the ubuntu-phone team on Launchpad and
Enabling the team mailing list at https://launchpad.net/~/+editemails
Touch/Install (last edited 2013-02-21 17:04:03 by dpm)
The material on this wiki is available under a free license, see Copyright / License for details.
xD
I wonder if we could have in future, flashable zip Ubuntu image for recovery
albsat said:
I wonder if we could have in future, flashable zip Ubuntu image for recovery
Click to expand...
Click to collapse
In due time brother. I am sure we will be able to get it flashable.
flashable zips for ubuntu for android, via a custom recovery http://www.droid-life.com/2013/02/2...view-on-a-nexus-device-using-custom-recovery/
and yea, this thread needs to be moved. you arent developing anything here, just providing instructions(from another site). doesnt belong in development.
You copied this from canonical page. There is already a thread with the flash able .zip instructions. This thread is on the wrong place and its unnecessary.
Sent from my Galaxy Nexus using xda app-developers app
All things aside.....thuis looks very promissing when iets stable andere 100%functional and working
Sent from my Galaxy Nexus using xda app-developers app
I think they will create the section: Galaxy Nexus Ubuntu Development
Now we wait for the threads asking how to do this.
simms22 said:
flashable zips for ubuntu for android, via a custom recovery http://www.droid-life.com/2013/02/2...view-on-a-nexus-device-using-custom-recovery/
and yea, this thread needs to be moved. you arent developing anything here, just providing instructions(from another site). doesnt belong in development.
Click to expand...
Click to collapse
I haven't flashed Ubuntu yet, but I was wondering if I can can just restore my current rom through twrp recovery. I wasn't sure if Ubuntu changes the recovery on my phone when I flash it.
eqjunkie829 said:
I haven't flashed Ubuntu yet, but I was wondering if I can can just restore my current rom through twrp recovery. I wasn't sure if Ubuntu changes the recovery on my phone when I flash it.
Click to expand...
Click to collapse
Yes u can just restore
Sent from my Galaxy Nexus using xda premium
Esteway.619 said:
Yes u can just restore
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I read somewhere that we need to reflash kernel if we want to restore Android again. I really don't know if it's true.
Closed, please go here >>> http://forum.xda-developers.com/showthread.php?p=38351018#post38351018
My goal for this thread is to gather as much info for the BLU Life One X 2016.
Specs
Screen: 5.2", 1080 x 1920 pixels, ~424 ppi, Gorilla Glass 3
Memory: 2 GB RAM, 16 GB storage, microSD slot (up to 64GB)
Camera: 13 MP rear, 5 MP front, LED flash front & rear, [email protected] video
Battery: Li-Ion 2900 mAh
Chipset: Mediatek MT6753
CPU: Octa-core 1.3 GHz Cortex-A53
GPU: Mali-T720
Model: L0070UU
Links & Other General Resources
BLU Products
Amazon: Black - White
GSMArena
BLU Products Development Team (Google+)
L0070UU User Manual
ClanGSM claim to have firmware files for our phone but it would cost $$$ to download: / mnt / data / ftp / Flashes / BLU / Life One X / L0070UU /
Similar Phones
Wiko Fever (GSMArena)
Micromax Canvas 5 (GSMArena)
XOLO Black 1X (GSMArena)
Elephone P8000 (CM12.1) and P6000 Pro
Quantum Go 4G (PhoneMore)
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Note: While I use a variety of operating systems on a regular basis everything here will be Windows 10 focused.
ADB & Fastboot
Before doing most things mentioned below you will need "adb" and "fastboot" installed. Two of your options are to install the Android SDK Tools or the Minimal ADB and Fastboot tool. If you are somewhat new to this I highly recommend the second one. Go here, download the latest version (1.3.1 as of this writing), and install it. When setup is complete you should have an icon for the Minimal ADB and Fastboot tool.
Note: I highly recommend you add "C:\Program Files (x86)\Minimal ADB and Fastboot" to your PATH variable in Windows. This way you can open a Command Prompt anywhere and use adb or fastboot.
Drivers
I recently setup a 5th gen Kindle Fire 7" tablet on my Windows 10 desktop. Because the BLU Life One X 2016 and the Kindle Fire are similar enough it just worked. To use the Amazon drivers you can find them on this page: https://developer.amazon.com/public...etting-up-your-kindle-fire-tablet-for-testing. The direct link is https://s3.amazonaws.com/android-sdk-manager/redist/kindle_fire_usb_driver.zip. Extract the zip file and then run KindleDrivers.exe.
Unlock Bootloader, Install Custom Recovery, and Install Root
Note #1: All credit for this guide goes to manos78's post for rooting the Wiko Fever!!! You can check it out here.
Note #2: I use Windows 10 on every PC I own. I assume Windows 7 and 8 should work just fine but cannot test that.
Note #3: The following assumes you have setup ADB and the proper drivers before beginning. I will try to detail that at a future time.
Note #4: Your phone will be completely erased. If there is anything you want to save do so beforehand.
1) Unlock Bootloader
Power on the phone and skip through all of the setup options
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly
Type fastboot oem unlock
Press Volume Up to say Yes and wait for this to finish
Type fastboot getvar all and look for (bootloader) unlocked: yes
Type fastboot reboot
You should see your phone reboot a couple times as it erases the phone
2) Install Custom Recovery
Note #1: We will flash a version of CWM or TWRP that was built for a Wiko Fever as they appear to be fully compatible with the BLU Life One X 2016. Go to this thread and download the latest CWM (http://www.sendspace.com/file/4g87bj) or TWRP (http://www.sendspace.com/file/y4jel8). Extract the img file. Again, many thanks to manos78 for CWM and hanuma for TWRP!!!
Power on the phone
You can configure your phone now or just skip through all of the setup options and do that later
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt to wherever you extracted the .img file
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly
For CWM type fastboot flash recovery recovery-custom-wiko-fever.img or for TWRP type fastboot flash recovery TWRP_WikoFever_2.8.7.0.img
Type fastboot reboot
Note: If your phone does not reboot then just hold the power button until it turns off. Hold the power button again until it turns back on.
3) Install Root
Note: While there are newer beta versions of the SuperSU app I am not sure if they will work properly on our stock rom. You can test one of those out and report back but I would recommend you do a full backup beforehand.
Download BETA-SuperSU-v2.52.zip and save it to the phone's internal memory or an inserted microSD card
Plug the phone in to your PC
Open a Command Prompt
Type adb reboot recovery
You should now be in CWM. Go to Install zip, find BETA-SuperSU-v2.52.zip, and install it
When it finishes go to Go Back -> Reboot Phone -> No
Once the phone boots up launch SuperSU and configure it as you like
Xposed
Download the latest version of Xposed for sdk22 and arm64 from here. As of this writing it is xposed-v79-sdk22-arm64.zip. Also download XposedInstaller_3.0_alpha4.apk and xposed-uninstaller-20150831-arm64.zip (just in case).
Reboot into CWM or TWRP and do a full backup
Install xposed-v79-sdk22-arm64.zip and then reboot
Cross your fingers and hopefully your phone will start properly. Mine rebooted like five times during the "Android is starting" step but finally finished.
Once your phone boots up install XposedInstaller_3.0_alpha4.apk
ViPER4Android
ViPER4Android adds audio effects to your Android device and is beloved by many. First we will install SELinuxModeChanger and then ViPER4Android. Special thanks to Tha Watcher for his original write-up here.
1) SELinuxModeChanger
Go to the SELinuxModeChanger page on F-Droid, download the latest version (3.2 as of this writing) or use this direct link, and save it to your Desktop
Launch Minimal ADB and Fastboot and type adb install %USERPROFILE%\Desktop\com.mrbimc.selinux_42.apk
On the phone you may see a prompt saying Installation Blocked. If so, click the little triangle and tap Install anyway (unsafe). If you see a failure just do it again and it should work.
Launch the SELinuxModeChanger app on your phone, grant it root permissions, and click Permissive
Note: If you have any issues with SELinuxModeChanger then head over to the XDA thread.
2) ViPER4Android
Download the latest version in zip format from here and extract ViPER4Android_FX_A4.x.apk to your Desktop
Launch Minimal ADB and Fastboot and type adb install %USERPROFILE%\Desktop\ViPER4Android_FX_A4.x.apk
Launch the ViPER4Android app on your phone, click Yes when prompted, click Super Audio Quality, and then click OK
Grant root access when prompted
Click OK
Reboot your phone
Note: Once your phone reboots you can start configuring ViPER4Android. I cannot really help much with that but feel free to look over the official XDA thread or their Settings Explained page on the official website.
Engineering Mode
Note: If I were you I would not change anything unless you absolutely know what you are doing!
I cannot seem to get the phone codes to work. You can install the MTK Engineering Mode app from the Google Play Store.
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Frequently Asked Questions
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
MTK Droid Tool
MTK SP Flash Tool
Latest Version: 5.1548.00.000
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Q: How can I tell if my model is the BLU Life One X 2016?
A: Go here and see if it is the same model.
Q: When I try to use adb root I get the following error: adbd cannot run as root in production builds
A: You can purchase and install [root] adbd Insecure by Chainfire. Once installed, launch the app, grant it root access, and then check Enable insecure adbd and Enable at boot
Q: How do I (re)mount /system as read-write?
A: Install [root] adbd Insecure as mentioned above, open a Command Prompt, type adb root, and then adb remount rw
Q: How can I disable the audio that plays when starting up or shutting down my phone?
A: Using a file explorer with root access, or an adb shell, delete or rename (with .bak at the end) /system/media/bootaudio.mp3 and /system/media/shutaudio.mp3 and then reboot your phone.
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Reserved #4
Have you tried porting the Elephone rom for the Blu? They both have a MT6753, so from what I understand from reading on XDA it might work. You might need to make changes suggested at http://forum.xda-developers.com/showthread.php?t=2701283.
Has anyone been brave enough to try this yet?
---------- Post added at 02:16 AM ---------- Previous post was at 02:12 AM ----------
I'm receiving my phone tomorrow so i might be the guinea pig...lol
Did this last night on my phone. Most difficult part for myself was finding the correct drivers as this is my first mediatek device. Ended up being my fifth attempt that had the correct set.
After I had the drivers it was extremely similar to a nexus process.
Do you have a link to the drivers
Sent from my 6045X using Tapatalk
I must inform you that I am still running good ol' Windows 7 so there's that.
All credit on my end comes from [Tutorial] Flash/Root/update elephone P8000 by vetkak and the first step with the link. Its not a real link, but a copy and past of the mega.co link had the proper drivers.
If you're on Windows 10 there is a separate thread out there somewhere with instructions for that.
OK thanks
Sent from my 6045X using Tapatalk
I feel like it needs mention that after flashing the recovery (I used the TWRP flavor) that after the fastboot command you need to immediately power off the phone, instead of rebooting, then do the volume up + power button press to get to the custom recovery.
SCrid2000 said:
Have you tried porting the Elephone rom for the Blu? They both have a MT6753, so from what I understand from reading on XDA it might work. You might need to make changes suggested at http://forum.xda-developers.com/showthread.php?t=2701283.
Click to expand...
Click to collapse
Unfortunately the guy that was bringing up the elephone p8000 has sold it and subsequently not be supporting it any longer. I'm happy enough there is custom recovery options and root. An AOSP ROM would be nice, but naturally the custom gestures would be lost.
jmcneil919 said:
Has anyone been brave enough to try this yet?
Click to expand...
Click to collapse
I did but from the original Wiko Fever thread instructions. I did this a couple of weeks before he actually posted this thread and I made my own instructions that I think are clearer and more concise than the Wiko thread; however, rogersa2k's guide is pretty thorough and easy to understand besides the following correction....
The fastboot reboot after flashing the custom recovery doesn't yield the same results, because when I did that it did NOT work! I corrected it by help from a comment by member yrude (and as hottcakes mentions above) and made my own instructions with the addition of adding the installation for Viper4Android. But I hesitate to post it on XDA as I don't want to step on any toes. However, I did post it on Google+, Amazon and GSMarena. If people want this alternate guide and notify me to post it, then I will. Otherwise, I'll keep it off XDA.
hottcakes said:
I must inform you that I am still running good ol' Windows 7 so there's that.
All credit on my end comes from [Tutorial] Flash/Root/update elephone P8000 by vetkak and the first step with the link. Its not a real link, but a copy and past of the mega.co link had the proper drivers.
If you're on Windows 10 there is a separate thread out there somewhere with instructions for that.
Click to expand...
Click to collapse
I was trying to using the link to download the driver, but the mega site asked for "decryption key" before I can download. Is there a key available to share? Thanks,
Tha Watcher said:
I did but from the original Wiko Fever thread instructions. I did this a couple of weeks before he actually posted this thread and I made my own instructions that I think are clearer and more concise than the Wiko thread; however, rogersa2k's guide is pretty thorough and easy to understand besides the following correction....
The fastboot reboot after flashing the custom recovery doesn't yield the same results, because when I did that it did NOT work! I corrected it by help from a comment by member yrude (and as hottcakes mentions above) and made my own instructions with the addition of adding the installation for Viper4Android. But I hesitate to post it on XDA as I don't want to step on any toes. However, I did post it on Google+, Amazon and GSMarena. If people want this alternate guide and notify me to post it, then I will. Otherwise, I'll keep it off XDA.
Click to expand...
Click to collapse
Pls post yours here. I saw your Amazon comment and tried to follow it. Everything seemed to work till I run "fastboot oem unlock" then the PC just displays "Waiting for device response...." and my BLOX never showed any response on screen. I suspected that I did not have the driver for this particular type cellphone device. Thanks,
clu1688 said:
Pls post yours here. I saw your Amazon comment and tried to follow it. Everything seemed to work till I run "fastboot oem unlock" then the PC just displays "Waiting for device response...." and my BLOX never showed any response on screen. I suspected that I did not have the driver for this particular type cellphone device. Thanks,
Click to expand...
Click to collapse
I appreciate that but the only way I'd post it in this thread is if the OP says it's fine. I do not like hijacking or taking over other people's threads.
It sounds like ADB is actually not loaded or working on your computer or otherwise you wouldn't get that message. I could be wrong, though. To test to see if it is indeed working and drivers are properly loaded, what does it respond when you type: adb devices
SCrid2000 said:
Have you tried porting the Elephone rom for the Blu?...
Click to expand...
Click to collapse
Not yet, but I do plan to try to start with that. It's nice that Elephone released the source code for the P8000 so that could help as well. If I ever get to this I will need lots of help.
jmcneil919 said:
Has anyone been brave enough to try this yet?
Click to expand...
Click to collapse
Everything that *I* post in the OP will be something that I tested on my own device first unless I specifically mention otherwise.
hottcakes said:
I feel like it needs mention that after flashing the recovery (I used the TWRP flavor) that after the fastboot command you need to immediately power off the phone, instead of rebooting, then do the volume up + power button press to get to the custom recovery.
Click to expand...
Click to collapse
I will add a note about that but some of us had issues so I chose the alternate method that has worked for me the first time every time.