Related
This thread is about installing Android natively on your Vogue so it completely replaces Windows Mobile.
[size +1]Important: This thread is now out of date, if you want to flash Android, use the new "norootfs" NBHs.[/size]
There are 2 installation methods:
If you are already running android from your sd card then use method 2, if you want a fresh install of android 1.5 from a windows machine use method 1.
For both methods, you must have a HardSPL installed, if you have flashed a custom wince rom before then you will, otherwise read one of the other threads on XDA about how to do this.
Method 1:
------------------------------------------------------------------
download the following:
http://www.mediafire.com/?zldjhfnkzk2
Unzip it and follow the instructions in README-ANDROID.txt.
All you have to do is copy the androidinstall.tar file to your sd card and run ROMUpdateUtility.exe on your PC.
Now Donate:
https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_SM.gif:NonHosted
Method 2:
------------------------------------------------------------------
Check here for NBH files containing a linux kernel and initrd to allow you to flash android to your vogue and wipe windows completely.
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
The ROMs are dated and there are three versions.
They are identical except the resolution; 240x320, 320x428 and 320x480.
You will also need a new rootfs:
http://it029000.massey.ac.nz/vogue/files/rootfs.zip
This rom will copy your rootfs, system and data to nand (the internal storage of the phone) so you will only be running from nand. To do this, make sure you have a working setup (using system.sqsh and data.img without partitions) and install the new rootfs. Make sure it still works.
Make sure you have a carrier rom to go back to. Android currently doesn't let you change any of the radio parameters so you would have to flash back to a carrier rom to re-provision your phone.
Now create 3 empty files in the root of your sd card called:
rootfstonand
systemfstonand
datafstonand
These must be all lower case with no extensions and they will be deleted once each fs has been copied.
Now flash the rom corresponding to your resolution and wait.
There are 3 ways to flash a rom.
1. Use ROMUpdateUtility under windows (this may not work on these roms, i haven't tried it). Rename the nbh file to RUU_signed.nbh.
2. Use HTCFlasher under Linux, this is what I have been doing and although a bit quirky, it does work. A binary that fixes a few things with HTCFlasher is on the website.
3. Rename the nbh file to VOGUIMG.NBH, put it on an SD card and boot the phone while holding down the power and camera keys.
When it starts, it should be running from nand. The tmp and cache dirs are still mounted from sd, so you do need the sd card in there but it's not really used much.
If something goes wrong or you haven't copied the correct files, press volume up while it is booting (after the two vibrates preferably). It will display a message saying that its in recovery mode. You should be able to plug the phone into a computer and the sd card will appear as a usb drive. You can also connect using adb.
There are a few limitations, rootfs must be less than 13M, system must be less than about 90M and data must be less than about 128M. This means unless you use a very stripped down system with apps2sd, hero probably won't work.
I've put a linux adb binary on the files page that fixes the annoying history 'feature' too.
Remember, this will completely wipe windows mobile and all your data from the phone. Run android from SD first to make sure you like it and don't want to be able to easily go back to windows mobile.
I've spent a lot of time on this so I would like people to donate if they use it.
This is my paypal:
https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_SM.gif:NonHosted
Woot!
Doing this now =)
dzo said:
I've spent a lot of time on this so I would like people to donate if they use it.
This is my paypal:
https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_SM.gif:NonHosted
Click to expand...
Click to collapse
I'm paypaling 5 bucks right now.... and I dont have a Vogue, I have a kaiser, but hey, $5 is long overdue for all the work you've done for the kernel... if NAND support hits the kaiser, I'll probably throw another $5-10 your way.
*paypaled - I normally dont do this kind of stuff, but its the holiday season, the MSM Android project has made SO much progress cause of DZO, if everyone just donated $5-10, it would at least be a nice gesture for all the work he's done*
I just registered to say thanks for all the hard work! I'll paypal you some cash once I get it up and running! I have a couple questions...
First, what works and doesn't work with this version? Bluetooth, tethering, nav?
Second, what version of android is this?
After flashing android using this method, can you still force the phone into the bootloader? I am assuming this is how you would flash back to windows.
Thank you, dzo. This is incredible work!
Now that you've gotten this far, can you answer some questions for those of us considering making the switch to Android:
What is/is not working in this build?
What version of Android is this?
What are the advantages of running one resolution over another?
Will we require new drivers to sync to our PCs when running Android instead of WinMo? Are they available for all OSes? (XP, Vista, 7, OSX, Linux)
How can we return to WinMo if necessary?
What's next in your development goals? With any ideas, can you give any sort of time frame on what we can expect and maybe when?
If I understand correctly, theres "NO" build in here, you play with builds in your DS, and when you are ready and like one..you just use that system.sqsh data.img rootfs (provided) and..the nbh, all in the root of the sd card. And it will flash the nand with your files! So..thats it!
Nice one dzo, hoping for you to get to kaiser
Hey Martin, I can't even use these flashable images, but if it weren't for you I wouldn't even be running Android via haret, plus you've answered so many of my questions and I've never donated. So, since you're actually now, I'll donate $10.
flashing from windows
Can someone try flashing from windows, then use mtty and run
Code:
set 16 0
task 3
I had to do that to get my test phone out of bootloader last night even after flashing from Linux. But it's up and running 'the new old fashioned way' now.
gswarriorfan said:
I just registered to say thanks for all the hard work! I'll paypal you some cash once I get it up and running! I have a couple questions...
First, what works and doesn't work with this version? Bluetooth, tethering, nav?
Second, what version of android is this?
Click to expand...
Click to collapse
nothing that hasnt already worked works there is no change...
dj13241 said:
After flashing android using this method, can you still force the phone into the bootloader? I am assuming this is how you would flash back to windows.
Click to expand...
Click to collapse
yea camera + power + reset hole
Shidell said:
Thank you, dzo. This is incredible work!
Now that you've gotten this far, can you answer some questions for those of us considering making the switch to Android:
What is/is not working in this build?
What version of Android is this?
What are the advantages of running one resolution over another?
Will we require new drivers to sync to our PCs when running Android instead of WinMo? Are they available for all OSes? (XP, Vista, 7, OSX, Linux)
How can we return to WinMo if necessary?
What's next in your development goals? With any ideas, can you give any sort of time frame on what we can expect and maybe when?
Click to expand...
Click to collapse
i can answer a few
1 nothing that wasnt already working this isnt a build!!!, this is a way for VOGUE users to be able to put a working build "data.img and system.sqsh" they already have working on their phone and to be able to get rid of android
2 this isnt a build
3 320x240 shows more on screen 320x428 and 320x480 show more on screen but it is a little blurry
4 you will require adb drivers located on http://code.google.com/p/vogue-android and as far as i know they work on vista 32 and win 7 32 bit and there are different ones also located at vogue-android for win 7 64b
there are adb drivers for linux in the android SDK located here http://developer.android.com/sdk/1.6_r1/index.html make sure you download 1.6r1 though! 1.5r3 doesnt work for our devices in linux
5 just reflash any wm rom (that works with vogue of course)
mrkite38 said:
Can someone try flashing from windows, then use mtty and run
Code:
set 16 0
task 3
I had to do that to get my test phone out of bootloader last night even after flashing from Linux. But it's up and running 'the new old fashioned way' now.
Click to expand...
Click to collapse
you could also use the bootloader cmd prompt in htc flasher and do:
Code:
set 16 0
ResetDevice
Does this have lcd density set? Because eclair is density 120, but looks better in 320x428 with 160 density. If not, is there a way to set density after flashing?
Ahhh ok I get it now. I'll still donate when I get it up and running. Thanks!
OMFG!!!! dzo you are something else!!!
I just got my Vogue a few weeks back and I am surprised on how well Android runs on this thing (I have a Raphael as well, but no comparison to this)
Having a flashable rom to a WM device... unbelievable...
Kudos for your work man!!!!
I guess the question on a lot of people's minds right now is this... how do you go back to WM?
you could also use the bootloader cmd prompt in htc flasher and do:
Code:
set 16 0
ResetDevice
Click to expand...
Click to collapse
I tried that and it came back in bootloader with 'RUUNBH' in the upper right corner. Then I added the task3 and it booted normally. Who knows, maybe I did something else funny.
I used htcflasher on my newly-reloaded ubuntu laptop, but I wasn't able to get it to work under windows. So I thought that maybe flashing from windows was ok, but it just needed a kick through mtty to get going.
What do those two bootloader commands do? Not that it really matters since dzo says the newest version should work from windows anyway...
egzthunder1 said:
I guess the question on a lot of people's minds right now is this... how do you go back to WM?
Click to expand...
Click to collapse
Boot back to bootloader and flash it! Did that myself last night.
Also, how do we make a smaller data.img? I keep getting 256MB versions.
scizzle said:
Does this have lcd density set? Because eclair is density 120, but looks better in 320x428 with 160 density. If not, is there a way to set density after flashing?
Click to expand...
Click to collapse
There's no density set on the kernel cmd line, I'd have to make another nbh for that.
However, since system can now be made r/w you should be able to edit /system/default.prop to change density.
Do:
adb remount
adb pull /system/default.prop .
edit the file and change ro.sf.lcd_density
adb push default.prop /system/
reboot
Thanks you so much dzo. i got this working, now im going through all my android files on my computer to find a build that i like, and wanna keep as my main build, but one thing, does the data really have to be less than 128mb? because almost all my android builds are alot bigger which is annoying.
but other than that it worked like a charm. thanks so much.
p.s. once i get some $$ (the 15th of december [my payday]) and find a permanent build i'll send some donations for you hard work.
dzo said:
There's no density set on the kernel cmd line, I'd have to make another nbh for that.
However, since system can now be made r/w you should be able to edit /system/default.prop to change density.
Do:
adb remount
adb pull /system/default.prop .
edit the file and change ro.sf.lcd_density
adb push default.prop /system/
reboot
Click to expand...
Click to collapse
Legend! Thank you. I will try it as soon as I can figure out the data.img haha.
scizzle said:
Also, how do we make a smaller data.img? I keep getting 256MB versions.
Click to expand...
Click to collapse
jamezelle said:
i used the following commands to make a new data img
Code:
dd if=/dev/zero of=~/data.img bs=1048576 count=128
mke2fs -F ~/data.img
to make a blank 128 mb data.img file in my home folder
Click to expand...
Click to collapse
- I can now confirm that flashing the nbh with the ruu works from Windows.
- dzo, I have a panel type 3 us sprint vogue. everything booted up fine, the buttons work, but the touchscreen isn't. Will post logcat / dmesg in a bit.
edit: uploaded zip w/ logcat and dmesg
this is the 2.3.1 kernel off my nexus s modded with ro.secure=0. adb remount works again! apparently people really like this option? lots of complaints it didnt work since upgrading to 2.3.1.
edit: added @supercurio's ext4 file system hack. all credits to him for providing the how-to.
edit2: added the boot.img from CM7 with @supercurio's ext4 file system hack.
test:
Code:
fastboot boot roext4.img
install:
Code:
fastboot flash boot roext4.img
Thank you sir, trying this now.
Yes I love my adb remount, makes things a ton easier for upgrading the market manually with adb push for example.
Michael.B. said:
Thank you sir, trying this now.
Yes I love my adb remount, makes things a ton easier for upgrading the market manually with adb push for example.
Click to expand...
Click to collapse
Worked great. Wifi and adb remount again on 2.3.1
Michael.B. said:
Worked great. Wifi and adb remount again on 2.3.1
Click to expand...
Click to collapse
glad someone got some use out of it.
Any chance you can make a version that works on CM7? I just tried this and wifi doesn't work w/ CM7.
Sent from my Nexus S using XDA App
added cm7 boot.img with ext4 hack.
My bluetooth stopped working after flashing roext4.img. it tries to activivate but fails......
Thanks for the CM7 version! Works great.
Sent from my Nexus S using XDA App
unremarked said:
Thanks for the CM7 version! Works great.
Click to expand...
Click to collapse
glad i could give something back. even if its minor.
teckhwee said:
My bluetooth stopped working after flashing roext4.img. it tries to activivate but fails......
Click to expand...
Click to collapse
I just test my bluetooth w/ the CM7 version. It doesn't work as well. I guess the ext4 hack breaks it in general. I went back to my original boot.img, and bluetooth works again.
Luxferro said:
I just test my bluetooth w/ the CM7 version. It doesn't work as well. I guess the ext4 hack breaks it in general. I went back to my original boot.img, and bluetooth works again.
Click to expand...
Click to collapse
yep. bluetooth seems to be an issue with it. i dont use bt at all so its not really an issue for me.
I confirm that there is a problem with Bluetooth
k0mpresd said:
yep. bluetooth seems to be an issue with it. i dont use bt at all so its not really an issue for me.
Click to expand...
Click to collapse
^
I'm okay with giving up Bluetooth for the performance enhance.
Sent from my Nexus S using XDA App
MMM, wifi is working but i can't complete quadrant benchmark!
MrNameless said:
MMM, wifi is working but i can't complete quadrant benchmark!
Click to expand...
Click to collapse
Quadrant doesn't work correctly on gingerbread. It happens on stock roms as well. it's just random, and sometimes it will complete.
this is voodoo kernel? do you need special recovery?
k0mpresd said:
Code:
fastboot flash boot cm7.img
Click to expand...
Click to collapse
It looks like the noauto_da_alloc flag has to be applied to the /data mount after bluetooth services are started. Where in the img did you have it specify that flag was it in the initial mount or did you remount with it at the end of init?
Zenoran said:
It looks like the noauto_da_alloc flag has to be applied to the /data mount after bluetooth services are started. Where in the img did you have it specify that flag was it in the initial mount or did you remount with it at the end of init?
Click to expand...
Click to collapse
here is the modded file. if you have a better solution, let me know and ill post an img.
Before anything............. This may Brick your phone, follow instructions and it wont
Big shoutouts to:
2nd-init------
skrilax_cz for writing this awesome trick!
edgan for getting it working on atrix with taskset
this hack:
eval for crazy loopback mount idea and all scripts
unknown for lots of helpful testing and debug
XLR88 for the system.img of GB 2.3.4
This is an example of the sort of thing that 2ndinit makes possible
but it is a quick hack and running with the wrong kernel - so still buggy
Bugs
1) The screen flips out when locked, so basically you swipe left and screen goes right.
2) No wifi
3) Camera dont work
4) Moto sign in not working
5) fingerprint
Working
1) Mobile data
2) network
3) Google sign in
4) Market
5) Calls
Will update when fixes are found and bugs are ironed out.
How to get GingerBread via 2ndinit on a locked bootloader for motorola atrix
Tools you need
Adb or Rootexplorer, 2ndinit.apk, terminal
Fastboot
Install 2ndinit.apk
Reboot
in terminal type
ls -a /sys/kernel/debug
Click to expand...
Click to collapse
should get output not
...
Click to expand...
Click to collapse
Download this ...........http://download839.mediafire.com/gv6kzdu34z3g/lcldnltaqj8xd9x/2ndGB.tgz
extract this to sdcard
Download this ...........http://hotfile.com/dl/122055970/0a6dfce/moto-fastboot.zip.html
Extract to sdcard
Delete everything in /preinstall
adb shell
su
cd /preinstall
rm -rf
Click to expand...
Click to collapse
copy 2nd-init, taskset, busybox to /preinstall
In ternimal
chmod 755 2nd-int
chmod 755 taskset
chmod 755 busybox
Click to expand...
Click to collapse
Rename hk. Img to system.img to and then copy to /preinstall folder
copy files from /ETC/rootfs/ to /system/etc/rootfs/ and set permissions
chmod 644 /system/etc/rootfs/*
Click to expand...
Click to collapse
copy this to /system/bin/ download and add gb directory to /data/ so it becomes /data/gb/
In terminal type
ls -a /sys/kernel/debug
Click to expand...
Click to collapse
you should get nothing at all
reboot.....
Backup your data this is a recommendation just in case
reboot again...........
when rebooting hold volume down then scroll down to EARLY USB ENUMERATION then volume up (do this everytime you want gingerbread)
wait.............
You should successfully boot into GingerBread... Congradulations
getting back to froyo
reboot
If all this fails, install 2ndinit.apk from here
Then repeat this tutorial...
Sorry about the crap video
WATCH HERE
If anyone can help to solve the flip of screen here is some clues that may help
1) screen is working prefectly until screen turns off, then it flips
Glad my work could be of use =)
And thanks for taking this off my hands while I'm away... hope you can fix the touch screen left-right input flip ... if anyone has any ideas, PM me, _unknown and stevendeb25. Here's to hoping all international users can enjoy 2.3.4 soon!
PS. haha thanks for quoting all my cursing in IRC about my /data failures
How my hack works
For international devs who want an idea of how I did it (before stevendeb25's tutorial & release) the following details my mount_ext3.sh:
Loopback hack only loads if you fastboot menu to early USB enum, so, run if ro.usb_mode==debug (plus helps us debug to adb early... why /system/etc/rootfs/default.prop we copy to / has ro.secure=0 & persist.service.adb.enable=1) In addition to default.prop we copy, extracted files from GB's ramdisk:, /init, /init.rc (modified, comment out mounting /system) and ueventd.rc from etc/rootfs, plus symlink /sbin/ueventd->/init.
Next, mknod and mount /preinstall rw, where we keep taskset, 2nd-init and busybox binaries, as well as system.img (CG60 from hktw 2.3.4 sbf.) It's probably already in /dev/block/ but this varied across froyo builds so mknod and mount rw to be safe. Good idea to use /preinstall/busybox from now on as /system mount dis/appears.
e2fsck -y the system.img and then losetup the loopback mount, umount -f -l /system, and mount -t ext3 <loopbackdevice> /system. For debug cat out /proc/mounts to a file in /preinstall or /data, actually I also append ">>/preinstall/debug 2>&1" to every command. Finally, now you can (taskset) 2nd-init your new system!
Unfortunately, seems necessary to fastboot -w or just rm -r /data/* between boots of froyo and GB. Annoying, but I couldn't easily get a GB-only /data mounted.
Now, can you fix the input flip left-right after lock screen? Clues are: it doesn't happen if this trick is tried on GB kernel (with Froyo ramdisk, system, and same 2nd-init trick.) Also, it persists after warm reboot, GB->GB. Pulling in /system/lib/hw from Froyo didn't help. Tho you'll want to bring back (and insmod) aev.ko, evfwd.ko, plus revert dhd.ko to Froyo version, as the first two are in-kernel on GB, and the latter seems to differ. I am fairly confident most bugs can be fixed by replacing (lock screen? nvrm_daemon?) pieces of GB userspace with Froyo versions in system.img. I just lost a bit of ambition after finding the fastboot oem unlock in the BL plus I will be away for a bit.
So, good luck to stevendeb25 and all you non-ATT Atrix hackers!
At least International users get some Gingerbread love! Good job guys!
i can't believe!!!
what a great new!!!
thanks guys!
the video seems to be really amazing!
wanna try it!!!!
that bootscreen looks awesome at first part in the video, is that stock?? oo
Excellent work brothers, you guys are really making us proud as well as you should be!
Very good job!
Now I can start dreaming about GB in my non-att atrix
You sexy, sexy man! Rawr!!
Great news
Sent from my MB860 using XDA Premium App
stratax said:
that bootscreen looks awesome at first part in the video, is that stock?? oo
Click to expand...
Click to collapse
Yeah stock orange uk bootscreen
Sent from my MB860 using XDA Premium App
Lol..
Awesome Steven, lookin' forward
bongd said:
You sexy, sexy man! Rawr!!
Click to expand...
Click to collapse
Stock Bell Atrix on Rogers with updated radio, Rooted, deodexed, Honeycomb theme, and frozen!
Released ............ enjoy guys, if dont want flip screen, dont lock the phone
This remember me when we try to put android on Windows Mobile Phones!haha
Anyway, nice work man, Let's play a lil
Wow, good work guys. I am sure this has been torture for international users. For the past couple of weeks, we in the states (or anyone on at&t) have been like kids on Christmas, while everyone else sits on the sidelines It's a good thing the 2nd init port got put to good use.
HolySorento said:
This remember me when we try to put android on Windows Mobile Phones!haha
Anyway, nice work man, Let's play a lil
Click to expand...
Click to collapse
Android has been ported to the Iphone, but as far as I know only to the older generations.
c'mon guys, are you trying that??
post your opinions!!
stevendeb25 said:
Released ............ enjoy guys, if dont want flip screen, dont lock the phone
Click to expand...
Click to collapse
Great work steve
Steven, is there no way for you to use drivers from the hktw build to fix wifi and camera?
Or do those require kernel level access or something?
Sent from my MB860 using XDA Premium App
stevendeb25 said:
Yeah stock orange uk bootscreen
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Think anyone could post this? It looks much better than the ATT one.
tasty_boy said:
c'mon guys, are you trying that??
post your opinions!!
Click to expand...
Click to collapse
I'd love to try but without wifi and that flip issue I think I'll pass this version.
Sinful Animosity said:
Steven, is there no way for you to use drivers from the hktw build to fix wifi and camera?
Or do those require kernel level access or something?
Click to expand...
Click to collapse
Other way around... if you pull in dhd.ko from the latest Froyo build you flashed on your system, as well as aev.ko and evfwd.ko (and /system/etc/firmware or wifi/ ?) into loopback mounted /system you will have more chance of working wifi in HKTW2.3.4. (HINT HINT you could do this directly in the mount_ext3.sh script... copy useful 2.2 stuff to /preinstall, copy back into new /system after unmount,remount, even insmod if you have to...)
Remember, this trick produces a mismatch between /system version (GB,2.3.4) and kernel version in boot.img which is actually running. We can take care of ramdisk post-hoc before 2nd-init but older kernel and its API is still in place so pieces of HKTW userspace will have to be replaced/modded to fix bugs. This version of mount_ext3 is an early release for the hackers who want to tinker until it works... good luck! I will have only web and ssh access off and on for 10 days but can answer any questions by PM, on IRC or here..
After testing CM10 for a while (thx codeworx) I now ported my NanoBoot image to CM10.
Changes compared to original CM10 boot:
"insecure" (means: / and /system mounted read-write (easy 'adb push' into /system ...), ro.secure = 0)
support for /system/etc/init.d/ init scripts
(somewhat) easy UMS access
Changes in r10:
Use 179:24 instead of 179:25 as address for UMS (fixes UMS on Windows)
to enable UMS for external SD with this boot.img it is enough to do:
Code:
setprop sys.usb.config mass_storage,adb
to return to MTP:
Code:
setprop sys.usb.config mtp,adb
TIP:
If you use Linux you may use some function like:
Code:
ums () {
if [[ $1 == "+" ]]; then
adb root
sleep 2
adb -s c1607c00051963f shell 'setprop sys.usb.config mass_storage,adb'
else
adb root
sleep 2
adb -s c1607c00051963f shell 'setprop sys.usb.config mtp,adb'
fi
}
'ums +' will enable UMS, 'ums -' will disable UMS on your tablet (not to mention it needs to be connected (...))
replace '-s c1607c00051963f' with '-s <your adb id>' - you get the id via 'adb devices'.
If you only got one adb-enabled device, you could remove '-s c1607c00051963f' from the commands.
If there's more than one device connected adb needs to know which one should receive the commands.
I did not yet have the time to modify framework-res.apk to add UMS to the list of options...
Flash using img/pit with either Odin or Heimdall. Or use zip to flash using CWM.
Images for Odin/Heimdall
PIT:
p3100.pit http://downloads.nanolx.org/P3110/p3100.pit
p3110.pit http://downloads.nanolx.org/P3110/p3110.pit
Stock CM10 Kernel:
NanoBoot-r10-CM10.img http://downloads.nanolx.org/P3110/NanoBoot-r10-CM10.img
Johnsel's CM10OC Kernel:
-No WiFi-
Zips for CWM
Stock CM10 Kernel:
NanoBoot-r10-CM10.zip http://downloads.nanolx.org/P3110/NanoBoot-r10-CM10.zip
Johnsel's CM10OC Kernel:
-No WiFi-
Tried this on my P3113 and it broke my WiFi.
Macadamia Daze said:
Tried this on my P3113 and it broke my WiFi.
Click to expand...
Click to collapse
Here with 3110 it works... if you provide me the original 3113 boot.img, I can re-pack one, that should work.
And it only works with Cyanogen Mod 10. Not on 9 or stock rom.
Setialpha said:
Here with 3110 it works... if you provide me the original 3113 boot.img, I can re-pack one, that should work.
And it only works with Cyanogen Mod 10. Not on 9 or stock rom.
Click to expand...
Click to collapse
I am using CM10, so here's the original boot.img for CM10 on the P3113. You don't need the stock one, do you?
Macadamia Daze said:
I am using CM10, so here's the original boot.img for CM10 on the P3113. You don't need the stock one, do you?
Click to expand...
Click to collapse
try with attached CWM zip.
n00b here.....what does this do??
Sent from my GT-P3113 using Tapatalk 2
F3AR420 said:
n00b here.....what does this do??
Sent from my GT-P3113 using Tapatalk 2
Click to expand...
Click to collapse
Just as first post says. This is a modified boot image for cyanogen mod 10 (no other ROM supported!) for galaxy tab 2 7", which makes / and /system read-write, adds support for init-scripts and adds pretty easy way to access UMS (USB Mass Storage) for external SD-Card.
According to your signature you're using an incompatible rom anyway - so don't use this.
@Macadamia Daze: now also tested with a 3100 I got my hands on: WiFi works. Dunno why it doesn't work with 3113 (I got no clue whether 3113 has some special WiFi stuff or whatever). Either way, please tell me, whether the attached one for 3113 (two posts above) works with WiFi.
Setialpha said:
@Macadamia Daze: now also tested with a 3100 I got my hands on: WiFi works. Dunno why it doesn't work with 3113 (I got no clue whether 3113 has some special WiFi stuff or whatever). Either way, please tell me, whether the attached one for 3113 (two posts above) works with WiFi.
Click to expand...
Click to collapse
Silly me; the problem was an incompatible kernel (Johnsel's). I returned to the default CM10 kernel and reflashed this, so now WiFi works. Still, in Windows it doesn't work properly. While it does create a new removable disk in Computer, it gives the "Please insert a disk into drive" error when I try to open it. Haven't tested in Linux yet, but based on my earlier tests with your previous UMS solution, it probably works.
---------- Post added at 08:12 PM ---------- Previous post was at 07:22 PM ----------
Ooh, I have good news! I used Device Manager to examine the blank drive letter on the computer, and it was recognizing it basically like an SD card reader with no SD card. So, I decided to poke around some of the files referenced in your UMS script from before to check their values. When I tried to open /sys/devices/virtual/android_usb/android0/f_mass_storage/lun/file, I got an error. Thinking it may not be working properly, I created a file on my computer with the contents "/dev/block/vold/179:24" and ADB pushed it to overwrite the broken file. Instantly, my SD card mounted on the PC. I hope this is useful information for you!
Macadamia Daze said:
Silly me; the problem was an incompatible kernel (Johnsel's). I returned to the default CM10 kernel and reflashed this, so now WiFi works. Still, in Windows it doesn't work properly. While it does create a new removable disk in Computer, it gives the "Please insert a disk into drive" error when I try to open it. Haven't tested in Linux yet, but based on my earlier tests with your previous UMS solution, it probably works.
---------- Post added at 08:12 PM ---------- Previous post was at 07:22 PM ----------
Ooh, I have good news! I used Device Manager to examine the blank drive letter on the computer, and it was recognizing it basically like an SD card reader with no SD card. So, I decided to poke around some of the files referenced in your UMS script from before to check their values. When I tried to open /sys/devices/virtual/android_usb/android0/f_mass_storage/lun/file, I got an error. Thinking it may not be working properly, I created a file on my computer with the contents "/dev/block/vold/179:24" and ADB pushed it to overwrite the broken file. Instantly, my SD card mounted on the PC. I hope this is useful information for you!
Click to expand...
Click to collapse
I see... 179:24 is the sdcard itself, 179:25 (what I use) is the first partition on the sdcard... unixoid systems don't care about that, but windows seems too... I'm gonna test with 179:24 on Linux and if it works there (I'd say yes even without testing, I provide an update). Thanks for testing.
r10 is now online - fixes UMS issue on Windows.
I can't get WiFi to work with Johnsel's CM10OC Kernel - so I skiped uploading those image/zip...
You can find me in Freenode #cyanogenmod-dev if you care to sort out what's happening with the wifi on my kernel
Johnsel said:
You can find me in Freenode #cyanogenmod-dev if you care to sort out what's happening with the wifi on my kernel
Click to expand...
Click to collapse
It fails to load something and therefore can't be enabled, don't remember exact log-message right now.
I'll contact you, when I'm hacking around the next time.
This is pretty interesting.
Two things
1-Doesn't CM10 already support init.d scripts?
2-Would it be possible to swap the mountpoints for the "internal" sdcard space and the actual microSD card slot? My current method of re-mounting things right after boot is OK but not very elegant.
DivinityCycle said:
This is pretty interesting.
Two things
1-Doesn't CM10 already support init.d scripts?
2-Would it be possible to swap the mountpoints for the "internal" sdcard space and the actual microSD card slot? My current method of re-mounting things right after boot is OK but not very elegant.
Click to expand...
Click to collapse
1 - atleast not via boot.img - that's why I added it.
2 - I have an older tablet I used before (ARNOVA 7C G2) it worked with this one, so it should work with this one, too. But you should never enable UMS while some app is running... On that other tablet I had to use EXT2 or EXT4 on SD-Card else all that permission stuff didn't work (FAT only has very basic permission rules for files). Also I recommend using second partition of SD-Card for /data. (first gets used as external storage and is managed by vold - at least that is what I did on my other tablet).
I attached init.espresso.rc, so that you can play around with the mount points (re-send me the file after you're done and I can provide you a flashable zip).
Setialpha said:
1 - atleast not via boot.img - that's why I added it.
2 - I have an older tablet I used before (ARNOVA 7C G2) it worked with this one, so it should work with this one, too. But you should never enable UMS while some app is running... On that other tablet I had to use EXT2 or EXT4 on SD-Card else all that permission stuff didn't work (FAT only has very basic permission rules for files). Also I recommend using second partition of SD-Card for /data. (first gets used as external storage and is managed by vold - at least that is what I did on my other tablet).
I attached init.espresso.rc, so that you can play around with the mount points (re-send me the file after you're done and I can provide you a flashable zip).
Click to expand...
Click to collapse
That's the thing I have been wrestling with lately, what's "the best" way to manage this stuff?
It seems like the main thing that needs to be done for legacy purposes is linking the regular /storage/sdcard0/data directory over to /storage/sdcard1/data/.
One idea I had was to format the "internal" sdcard (/storage/sdcard0) with ext4, which would allow symlinks to exist there, then just remove the data directory and replace it with a symlink that points to /storage/sdcard1/data.
From what I've read, ext4 is supposed to be a better, higher performance solution, so I'm kinda curious to try it out.
It would make UMS pretty worthless to Windows guys like me, but I basically do everything via network anyways (SFTP mostly).
Is it possible to control the file systems used on the internal & external sdcards in the init? I didn't look too deeply at it cuz I don't know how to rebuild a boot.img (at least not yet)
Tested this with the current AOKP JB nightly, and it also breaks WiFi. I'm trying now to keep the rom and restore the CM10 NanoBoot backup. Fingers crossed it will be stable.
THIS THREAD IS NOW OUTDATED. Page 17 and on contains information for Ubuntu Touch Saucy port.
NEW THREAD ON THE WAY.
http://forum.xda-developers.com/showthread.php?t=2426924
What works. Wifi+ADB+Touch.
What doesn't work: Sound+Bluetooth. Bluetooth doesn't work yet in Ubuntu Touch, and Sound doesn't work with the Evervolv source. Camera.
Download these files.
http://cdimage.ubuntu.com/ubuntu-to...c-demo/quantal-preinstalled-phablet-armhf.zip Ubuntu Touch RootFS
Recovery Image.
http://gdurl.com/A0mz/download
Put on your SDCARD and install in ClockWorkMod. You know.. when you first turn on the tablet, moboot loads.. you should see a menu for clockwork recovery mod.
EDIT: Oh yeah.. First do a factory reset in recovery mod, THEN install the zip files... The factory reset formats the cm-cache and cm-data partitions.. There are 3 partitions. cm-cache cm-data cm-system. Factory reset formats cache and data.. When you install the first zip, it formats the system partition. Then after that install the RootFS.zip that you downloaded from ubuntu... It extracts the RootFS to the cm-data partition, that you formatted. So it should be clean.
Reboot.
Enjoy!
Oh yeah.. Onscreen Keyboard is not sized right. Seems to be an Ubuntu bug... If your fonts are wrong. .reboot.. check out /system/etc/init.d/90userinit for the stuff I added.
thanks to the usual guys. JCSullins, Evervolv, Tigeris and litz and ompx in ubuntu-touch on irc. The wifi fix was an idea I got while stuck in traffic. Can't believe it worked.
Oh yeah.. THANK YOU DR. MARBLE.
PS. I read somewhere you need at least 600MB of free space, AFTER you copy the files to the sdcard, for the extraction to go well...
nice
Awesome, can't wait to try this out!
How to install that on tp?
Way too cool!! tnx for all the hard work
tux-world said:
How to install that on tp?
Click to expand...
Click to collapse
He says: POST IT SOON. In other words: you have to wait until he finishes the porting.
Crazy how the font turned out like that
Sent from my SAMSUNG-SGH-T989 using xda premium
Great news
SGA, thanks for your effort in bringing Ubuntu touch to Touchpad!
If you need help with testers, let me know
Vistaus said:
He says: POST IT SOON. In other words: you have to wait until he finishes the porting.
Click to expand...
Click to collapse
is this CM?
tux-world said:
is this CM?
Click to expand...
Click to collapse
No. It's Ubuntu Touch, but from what I have heard on XDA Developer T.V. (check 'em out on YouTube) it is based on CyanogenMod.
Sent from my Xperia S ~XZXperience~Unlocked BL~Rooted~6.1.A.2.55~
I'm assuming the install process will be similar to The Nexus line, flash the core system then the phablet zip.
Sent from my Nexus 7 using xda app-developers app
What source did you use to compile? I tried to compile it and kept getting some weird error got frustrated and gave up.
blmvxer said:
I'm assuming the install process will be similar to The Nexus line, flash the core system then the phablet zip.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I think that's how it will always be. The core zip is device specific and contains the CM base while the phablet zip is for all devices.
Off to 3.0.8
EDIT TO POST. UNMOUNT PROC OUTSIDE OF CHROOT VIA USERINIT, AND NETWORK MANAGER WORKS WITHOUT FANOTIFY
Going to try a newer kernel to get wifi working. We need Fanotify in the kernel for the network manager to see the wireless. Has to do with proc mounted inside of a chroot and daemons having permission. Sad because once you run ubuntu_chroot shell to get in, you can run iwlist wlan0 scan...
Status Update Complete.
How to compile. Grab evervolv's device folder, but not his vendor folder.. grab hardware/qcom hardware/atheros and the compat-wireless from.. some folder.. forgot the name... I got these from evervolv's ubuntuphone branch for tenderloin.. (the kernel) and his build of android.
Those are the current sources.. May change.. Be sure to change ev.mk file to cm.mk, and change /vender/ev (inside of ev.mk) to /vendor/cm, ev.dependencies file to cm.dependencies....
JCSullins announced he will start work on JB. So that is cool. But.. 3.0.8 Kernel doesn't have working sound or bluetooth. Until someone figures that out with 3.0.8, Ubuntu-Touch and the Touchpad WILL NOT HAVE SOUND. (cough cough nag jcsullins cough cough).. That guy is the man to go to for that.
Backporting Fanotify is not easy. You run into having to change the msm code. (I ran into msm-watchdog.c) So much you might as well just go to 3.0.8.. I have an odd feeling that is someone were to backport it, sound would stop working....
EDIT TO POST. UNMOUNT PROC OUTSIDE OF CHROOT VIA USERINIT, AND NETWORK MANAGER WORKS WITHOUT FANOTIFY
Backup you jellybean system folder to a tarball and then extract it somewhere.. Same with the Ubuntu Touch system folder.
(I was about to give up!)
cp -R -f /jellybean/lib/* /system/lib
cp -R -f /ubuntutouch/lib/* /system/lib
cp -R -f /jellybean/etc/firmware/* /system/etc/firmware (my adreno firmware was missing, so this will fix that)
reboot.. and it worked.. merged libraries.
Fonts are not bad all the time..... Going to try this with 3.0.8 tonight.. If someone is bored today, give it a shot. Let us know how it works.
To brunch tenderloin I have to manually create out/host/linux-x86/bin and stick mkimage in there.
go to vender/cm/vendersetup.sh and add add-lunch-combo cm-tenderloin-userdebug.. I think.
there is a mkimage in the ubuntu touch source.. I used that. /system/extras/mkimage.. it needs to be compiled gcc mkimage.c -o mkimage -lz
then copy it cp ./system/extras/mkimage/mkimage ./out/host/linux-x86/bin no idea if this is required.
there are 2 bzr branch commands that need to be run.. google that.. Should be in Ubuntu Porting guide, but it's not. ubuntuappmanager library and some other library.
edit: run this inside of the ubuntu touch source folder/ubuntu
"bzr branch lphablet-extras/libhybris hybris" stupid smiles. =)
"bzr branch lplatform-api platform-api"
http://forum.xda-developers.com/showthread.php?p=38745624
dont forget to run extract-files.sh and get-prebuild, etc.
source build/envsetup.sh
lunch (pick 14)
brunch tenderloin
I bring over ts_srv and that other ts program from jellybean to ubuntu and currently add commands to /system/etc/init.d/90userinit to get stuff running.. Lazy, I am.
Confused? That is my rough draft guide.
A dude by the name of tigeris, or something that started with tig.. he helped me a lot on ubuntu-phone on irc. So did another guy named.. omxy.. I think... I will find them. Gotta go,
EDIT TO POST. UNMOUNT PROC OUTSIDE OF CHROOT VIA USERINIT, AND NETWORK MANAGER WORKS WITHOUT FANOTIFY
My wife would really like someone to pick this work up.. She wants me to .. "come back to the family"....
Oh yeah.. Wifi does work.
To get wifi working..
do this.
ubuntu_chroot shell
mount -o proc proc /proc
network manager should now bomb.
this is for open security.
ifconfig wlan0 essid "your essid"
ifconfig wlan0 up
dhcpcd wlan0
dhcpcd taken from jellybean tar.gz from the bin folder.. So.. yeah.. but no network-manager without fanotify and some other daemons. be sure to take dhcpcd stuff from etc.
DONT RUN ubuntu_chroot all by itself.. It will crash.
ALSO you MUST unmount proc before shutting down or it will be stuck in mtab and you will have old stuff inside of the /proc folder, inside of chroot, or rather /data/ubuntu/proc..
Problems? Restore ubuntufs tarball in recovery.
I will release something sometime soon.. after testing 3.0.8.. but if you know how to do all this stuff, be my guest.
Why don't you create your own github and share with us?
I bet that there are a lot of devs who want to continue.
I am really interested but I kind of got lost when you said to get the files from Evervolv... Can you post links to be more specific please?
Thank you.
Its just githib.com/evervolv
Sent from my Touchpad using xda premium
Doing that tonight... By the end of tonight I will release something..
It will be 3 files.
The first will be the .zip file that has the actual /system folder
second is of course from ubuntu and is the rootfs.
Third will be a tarball you guys can extract once the tablet is booted that will just have touch and graphics working. You can use wifi if you run it from adb, and keep the tablet powered on.
I haven't even touched pixel ratio.
Oh.. a 4th file.. of the whole ubuntu touch folder.. cleaned and made proper.. Uploaded to google drive.. Or hell I guess I can look at github...
Gotta play mario with my little girl first.
jshafer817 said:
Gotta play mario with my little girl first.
Click to expand...
Click to collapse
LOL
Gotta always spend time with them :good: