Related
Hi I am currently running debian on my phone using the method outlines here
http://www.myhangoutonline.com/2009/11/22/install-linux-on-your-g1/
Ive gotta say it quite slow and the method of installation is strange.
Here is a video of someone dual booting NATIVE debian on a G1. Read descrip in video for more info.
http://www.youtube.com/watch?v=tX1BOGl8Fnw
I would really want an option where you boot into recovery (Holding Home) and there is a menu where you can choose to boot into a normal recovery (Amon_Ra's) and the other options would let you choose between what OS you want to boot into like Gnome,OpenMoko,Debian. A normal boot would take you back to android.
Speeking of OpenMoko
there is a tut here
http://wiki.openmoko.org/wiki/OpenMoko_on_HTC-Dream
and i was wonderin weather anyone had tried this because it seems very interesting and would make it possible to bood gnome,debian etc
any opinions are highly appreciated
let me know what you think.
i dunno if im allowed to but bump
donut = 1.6 right?
yes
cupcake = 1.5
donut = 1.6
eclair = 2.0/2.1
Hi!
I've got OpenMoko dual-booting natively on my G1.
When I first looked into the problem, I saw that:
1) OpenMoko option involved boot flashing that would disable booting into Android.
2) Debian option had no ready-to-use rootfs. You had to bring on the usbnet and install debian packages through netinstall. But Debian was able to dual boot, thanks to FukTheRegister's excellent recovery image.
I surely needed something in the middle
I had contacted the OpenMoko port developer, leviathan (a nice guy btw). He's doing some great job of hacking the forked Android kernel to work on HTC Dream together with some other guys. He told me that he was continuing his work on OpenMoko for HTC Dream and that made me want to try it instead of Debian. By the way, FukTheRegister's Debian and Ubuntu ports are based on leviathan's OpenMoko kernel.
What I did to install and dual-boot OpenMoko was:
1) I partitioned my microSD card into three partitions: FAT, ext3, ext3
2) I extracted the OpenMoko rootfs to the third partition (ext3)
3) I made myself a recovery image that would consist of the most recent OpenMoko kernel from gitorious AND FukTheRegister's ramdisk (I just glued them together and threw away some modules to make it fit into 5Mb - maximum for recovery partition images)
4) I copied the recent kernel modules to /lib/modules/ on the 3rd partition of the sd card
5) I copied my recovery image to the sd card and flashed it with flash_image recovery /sdcard/openmoko-recovery-partition3.img right on the phone (under root).
After that I was able to boot OpenMoko with holding HOME + END during the bootup or Android (holding nothing).
See http://vaskas.ru/om-g1/ for all the relevant files.
If you want to try it yourself:
- repeat stage 1) after me
- take the openmoko-rootfs-20091128.tar.gz and repeat stage 2) after me
- copy the openmoko-modules-20100128.tar.gz to /lib/modules/ on the 3rd partition and extract it there
- take the openmoko-recovery-partition3.img and repeat stage 5) after me
P.S. I am not 100% sure that it's going to work for you, because I experimented a lot. It's pretty likely to work though.
hi again vaskas!
thx for work. Tried your setup, it worked for me.
Now it would be nice to have a recovery with an option to boot the second ext3.
Openmoko on Dream ----> nice!
Seems to get a usb connection:
http://wiki.openmoko.org/wiki/Usb_networking
Is a ssh/dropbear server already running on boot?
vaskas thx so much for the huge leap forward ecept im a little confused. so when i hold home + power using ur method it will boot into openmoko, butif i boot normally it wouild go into android, but what if i wanted to boot into normal recovery like amon_ra's?
if i boot into android normally and then run quickboot app and select recovery will it boot opoenmoko or amon_ra's recovery. also with your method does keeping apps on the first ext3 still work? while the second ext3 is for openmoko?
also when making second ext3 partition what size should i make it?
p.s this is sooooooo sick with open moko the possibilities are endless aswell as for people who prefer they can turn openmoko into debian and some time in the future android
so future = openmoko installed instead of android and then being able to boot debian/android or stay in openmoko environment.
also if it's not to much trouble vaskas can u please make a vid and put on you tube or here thx in advance andthx for ur hard work
olvap377 said:
vaskas thx so much for the huge leap forward ecept im a little confused. so when i hold home + power using ur method it will boot into openmoko, butif i boot normally it wouild go into android, but what if i wanted to boot into normal recovery like amon_ra's?
Click to expand...
Click to collapse
No, normal recovery won't be there, since my image replaces it. As far as I know, it's the only way to dual-boot now. If you wish to use your normal recovery image (amon_ra's or cyanogen's), just flash it with flash_image recovery my.img. When you're done with it, flash it back to openmoko's.
olvap377 said:
if i boot into android normally and then run quickboot app and select recovery will it boot opoenmoko or amon_ra's recovery. also with your method does keeping apps on the first ext3 still work? while the second ext3 is for openmoko?
also when making second ext3 partition what size should i make it?
Click to expand...
Click to collapse
I haven't tried quickboot yet.
Yes, Apps2SD still works perfectly with the first of ext3 partitions. I suggest that you make the second one at least 700Mb in size. I've got 500Mb taken by OpenMoko, for instance.
olvap377 said:
also if it's not to much trouble vaskas can u please make a vid and put on you tube or here thx in advance andthx for ur hard work
Click to expand...
Click to collapse
Well, you shouldn't really thank me since I only built a recovery image It's the kernel and ramdisk hackers who rock.
I'll make a vid when I have some free time, but I really suggest that you try it yourself
scheich said:
hi again vaskas!
thx for work. Tried your setup, it worked for me.
Now it would be nice to have a recovery with an option to boot the second ext3.
Openmoko on Dream ----> nice!
Seems to get a usb connection:
http://wiki.openmoko.org/wiki/Usb_networking
Is a ssh/dropbear server already running on boot?
Click to expand...
Click to collapse
FukTheRegister's ramdisk has such an option. I can try to make such a recovery if you need it.
Yes, dropbear is started automatically.
I'd love to see a solid and stable distro that would provide all the things that Android doesn't have, with:
- A compact desktop environment, supposedly e17 or LXDE
- Midori or Google Chrome
- Pidgin
- Sylpheed or Claws for GPG-secured e-mail
- MPlayer or VLC
- FBReader
- evince
- AbiWord
- Gnumeric
- Conky
- Gpodder for podcasts
- Some music player like Sonata
- Cron, sshd, gcc, scripting languages like Python and Ruby
- Zhone for making calls, texting, storing the address book
See, I'm not advocating touch-oriented software. I think we still need touch-capable apps for calling, texting and the address book. The others can be easily manipulated with the trackball and keyboard on G1.
That's what we should aim for IMHO: http://wiki.openmoko.org/wiki/Image:Debian_lxde_zhone.png
OpenMoko project has all this stuff. And that's really awesome. The question is if such an OS should be based on Angstrom (like OpenMoko SHR) or Debian (see http://wiki.openmoko.org/wiki/Debian). My preference is Debian since I'm a long-time Debian/Ubuntu user.
i prefer debian too and i will try this when i get home
i'm sorry for my really dumb question.
but how can i copy something from windows (7) to a ext2 partition?
and if you are creating those partitions, do both ext2 have to be primary or
one primary and one secondary?
thx in advance
lolmensch said:
i'm sorry for my really dumb question.
but how can i copy something from windows (7) to a ext2 partition?
and if you are creating those partitions, do both ext2 have to be primary or
one primary and one secondary?
thx in advance
Click to expand...
Click to collapse
They both have to be primary. I also recommend you to upgrade them to ext3 which is more stable thanks to journaling.
As far as I know, it's not possible to write to extX partitions from Windows. You can copy the files you need to the FAT partition and move them within the phone using Astro or other file manager.
You can mount the second ext3 partition from Terminal Emulator in Android like this:
$ su
# cd /sdcard
# mkdir SD2
# mount /dev/block/mmcblk0p3 /sdcard/SD2
Then it will be accessible from Astro in /sdcard/SD2.
i followed all the steps correctly but it just gets stuch at boot screen if i try to boot into recovery
any advice
maybe this has something to do with the fact that i have ebi1 phone?
pls help i really want this
EDIT:
wow im dumb i figured it out if u look at my sig ull see the way my partitions are setup
i followed all ur steps except each time i changed instructions from p3 to p4 becasue i also have a linux swap so when i installed this recovery it tried to boot from part3 which is my swap and obviously didn;t work
so vaskas can u please for everyone who has a linux swap release another recovery except that boots from part4?
Have also a swap as the fourth partition.. That doesn't matter, I think. Its only important, that the second ext3 is the third partition.
Heres my partition table:
fdisk -l /dev/mmcblk0
Code:
Disk /dev/mmcblk0: 1977 MB, 1977614336 bytes
255 heads, 63 sectors/track, 240 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000ac1bc
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 1 64 514048+ b W95 FAT32
/dev/mmcblk0p2 65 131 538177+ 83 Linux
/dev/mmcblk0p3 132 223 738990 83 Linux
/dev/mmcblk0p4 224 240 136552+ 82 Linux swap / Solaris
olvap377 said:
i followed all the steps correctly but it just gets stuch at boot screen if i try to boot into recovery
any advice
maybe this has something to do with the fact that i have ebi1 phone?
pls help i really want this
EDIT:
wow im dumb i figured it out if u look at my sig ull see the way my partitions are setup
i followed all ur steps except each time i changed instructions from p3 to p4 becasue i also have a linux swap so when i installed this recovery it tried to boot from part3 which is my swap and obviously didn;t work
so vaskas can u please for everyone who has a linux swap release another recovery except that boots from part4?
Click to expand...
Click to collapse
Ok, try http://vaskas.ru/om-g1/openmoko-recovery-partition4.img - it should work.
I'll try to make a multiple-choice one soon.
thx alot il try when i get home from school
EDIT: still dosent work just freezes at boot screen
plzzzz help any advice
olvap377 said:
thx alot il try when i get home from school
EDIT: still dosent work just freezes at boot screen
plzzzz help any advice
Click to expand...
Click to collapse
Do you mean you're stuck into the "G1" screen? If so, it's a recovery/kernel problem, not really connected with partitioning and stuff. I'm not sure if this openmoko kernel supports EBI1/32A, may be it's the problem
Well I have a dream which is 32b but with ebi1 radio I think this is the problem because amon_ra has a special recovery just for rogers dreams meaning something is different between them
If u could compare amon's rogers to normal recovery and find the differences could u chabge yours to make the latest part 4 file ebi1 compatible?
olvap377 said:
Well I have a dream which is 32b but with ebi1 radio I think this is the problem because amon_ra has a special recovery just for rogers dreams meaning something is different between them
If u could compare amon's rogers to normal recovery and find the differences could u chabge yours to make the latest part 4 file ebi1 compatible?
Click to expand...
Click to collapse
Frankly speaking, I don't think I'm going to have much time for this Since my radio is different, I won't be able to test it properly too.
Actually, I hope that more people join the thread so that we'll be able to solve much more problems together. I wonder where the guys from "Installing Debian on G1" are gone, I saw 2-3 people really interested in native Linux there.
Can you still rename the thread? If so, what do you think about appending something like " - Native OpenMoko and Debian" to it?
EDIT: compared Amon_Ra's recoveries in hex editor, they seem quite different
hi everyone i am currently trying to install android 3.2 on my htc hd2 and the steps i am following are to copy the android folder to the root of my sd card and then once i have done this then to tap on the CLRCAD file then tap the haret file then a loading bar comes up then goes to a black screen and in small writing in the top left hand corner it says
haret boot
shutting down hardware
turning off mmu...
in preloader
psr=600000df
tags preloaded to 0x11b00100 (size 0x0000f00)
kernel relocated to 0x11b0b000 (size0x0023f12c)
initrd relocated to 0x12200000 (size 0x001d0137)
jumping to kernel...
i have repeated this process a dozen times to ensure that i have not missed anything out last nite i made sure that the battery was fully charged and also i updated my rom from the htc website to the latest version as i have read that some people cant get android working at all unless they did this. i did the process until i got the black screen again and left it all night thinking that it may take a long timer as it is the first time i have ever tried loading android but i woke up and the screen was still there i am not sure what i have done wrong i have watched videos on youtube and read forums but no one else seems to have had this problem any help would be greatly appriciated thanks
i have just tried to boot an older version of froyo android the 2.2v i got past the first black screen and it went to the black screen where the white writing starts to scroll down the the writing faded into white lines what am i doing wrong
back up your sdcard contents to your computer.
format it, preferably from a linux box. if your stuck with win-blows, then you can do a full format, not the quick format.
now put JUST THE ANDROID folder on the sdcard.
put sdcard in phone, boot into android. when it boots, dont do ANYTHING for 5 min. reboot.
once it reboots, goahead and log in, synch etc.... then reboot
after that you can coppy the rest of the sdcard contents back over and be good to go.
which winmo rom, radio rom, and android build are u using?
i am using the darkstone froyo 3.7 build i am not sure what radio is or which one i am using i will try what you have suggested and let you know how it goes
right i formated (full) the sd car using windows vista the only way i could do this is plugging my phone into my laptop using the usb and formatting it that way
then i copied just the android folder to my sd card
rebooted the phone and went to file explorer opened the android folder doulbe clicked on clrcad then on haret
i was then stuck on the screen that i was before so i waited 5 mins just like you said to rebooted the phone and it was still on windows.
i repeated the same steps and waited ten minutes still no luck
also just so i understand after i waited five minutes should i be able to reboot the phone i do i have to pull the battery out like i did and where you put (when it reboots login etc)
is there any way you could email me a file to see if it is the files i am using
thanks for all you help so far guys!!!!
i am from th UK i dont know if that makes a difference
i have a 2gb sd card
i have just done some research on the radio versions and round a thread called master radio for the htc hd2 on xda but i am unsure which one to use and could this be the root of my problem thanks again
OS version 8.2.2.1869(21869.5.0.82)
manila version 2.5.20121429.0
ROM version 1.72.206 (8637200) WWE
ROM date 04/15/10
radio version 2.07.51.22_2
Protocol version 15.32.50.07U
i have just done a bit more research and found out that i need to use a .50 for flashing could this be a problem if i dont could this be th root of my problem
very big part I'd say.... It does say on just about EVERY build that you need a .50 radio NOT a .51....
snowy88 said:
i have just done a bit more research and found out that i need to use a .50 for flashing could this be a problem if i dont could this be th root of my problem
Click to expand...
Click to collapse
could be...
u need at least 2.08.50 or higher radio i thought so.
linkie he Definitve Guide To Android On HTC HD2
[RADIO] The HTC HD2 Master Radio Thread ( i would try Leo_RADIO_2.12.50.02_2 or 2.14 )
Good luck tell us when it did work
t1h5ta3 said:
back up your sdcard contents to your computer.
format it, preferably from a linux box. if your stuck with win-blows, then you can do a full format, not the quick format.
now put JUST THE ANDROID folder on the sdcard.
put sdcard in phone, boot into android. when it boots, dont do ANYTHING for 5 min. reboot.
once it reboots, goahead and log in, synch etc.... then reboot
after that you can coppy the rest of the sdcard contents back over and be good to go.
Click to expand...
Click to collapse
snowy88 said:
i was then stuck on the screen that i was before so i waited 5 mins just like you said to rebooted the phone and it was still on windows.
i repeated the same steps and waited ten minutes still no luck
also just so i understand after i waited five minutes should i be able to reboot the phone i do i have to pull the battery out like i did and where you put (when it reboots login etc)
Click to expand...
Click to collapse
no, depending on the class (speed) of your card it'll take 15-20 min to initalize on the first boot... theres alot going on in the background.
once its booted...ie: once it shows the initial android log in screen. ie: it has actualy booted into android.
if you pull the battery in the middle of the first boot, you just corupted the data it was writing.
format the card again - get rid of the corupted files.
now start over.
and yes, you got to have the corect radio installed etc.
most roms have a requirements list... if not folow the stickies.
as ive stated a ton of times in a ton of thereads, its worth installing ether droid explorer or adb on your pc if for no other reason but to be able to run a logcat so you can watch it run comandline, aswell as post it so others can help you debug/troubleshoot.
I have the same issue with linux showing that message then it boots up a green htc sign and stays there.. i left it there for 40 minutes waiting to see if anything would happen and never did. I had android running before but did a full format on my sd card and then installed another and this happens everytime i try.
I am running Miri_Dinik- V 19.0 WWE
Radio: 2.15.50.14
I also am using the 16g sd card that came with my tmo hd2
i have been searching for days for an answer and decided to finally make a post to see if i can get any answers
thanks
Hi
I am trying to install Android on my HD2
I am using Energy's Sencity rom with radio 2.12.50 and I am trying to install Core Droid v0.4.
I have formatted my SD to fat32 and placed the Android folder in the root. SD\Android
When I execute haret the background goes black and green "HTC" appears in the middle of the screen, first time I let it sit there for 45 minutes second time I let it sit there for 3 hours.
Any idea whats going on?
bump.anyone?
Iunno. Maybe there's a problem with the build. If other builds work, then it's prolly that build has problems. Does that build create a data image on first boot or do you have to place a blank data image in it for it to boot?
If it creates a data image on first boot, delete the one semi created in the folder and try boot again.
If you have to place a blank data image in it for it to boot then try a different blank data image.
Kailkti said:
Iunno. Maybe there's a problem with the build. If other builds work, then it's prolly that build has problems. Does that build create a data image on first boot or do you have to place a blank data image in it for it to boot?
If it creates a data image on first boot, delete the one semi created in the folder and try boot again.
If you have to place a blank data image in it for it to boot then try a different blank data image.
Click to expand...
Click to collapse
It is suppose to create a data image but no no semi data image or complete data image is created.
I really have no idea then, sorry. ._.
HSPL, maybe, iunno...
Enough space to create the data image? Very unlikely seeing as how it's try to fill up what it can...
Well you found the root of the problem though, it's not creating a data image... Maybe you can try putting a blank data image into it, and take off that line in the startup.txt where it creates a data image, or keep it, iunno, try it first without taking it off, and then take it off if it doesn't work...
Link and Name of your build please?
Help!!!
I have a T-Mobile HTC HD2. I want to install android on it. At first I put the MDJ Gingerbread SD Build on it. It loaded then I went back to WinMo 6.5 and tried to load it back and it wouldn't go. So I deleted it and installed the DL Desire build. It sticks on android logo and nothing happens. Help please.
CE OS 5.2.21892
SPL 2.10.00
Speed 1024 MHz
Radio 2.10.50.26
ROM Version 2.13.531.1
same thing happened to me, but i tried at different version.. still cnanot ...
Hello,
After rooting my Tattoo, I installed ROM manager and flashed the clockworkMod Recovery 3.0.0.6 (for tattoo/click).
When I install the rom cyanogenmod 7 RC1 or RC2 (I try CM7 nightlybuild 19 as well) via clockworkmod, he said that the rom is successfully installed but when I launch the ROM, the ROM stucked on the tattoo boot screen (not on the CM7 boot screen, I never saw the CM7 boot screen).
Any idea to resolve my problem?
Thanks
Stuck for how long? About 2 minutes it is ok and then the CM boot logo come up.
First boot takes a long time.
Did you wipe your device before flashing CM ROM? If not do so in recovery menu. (wipe all, factory setting, clear cache etc...)
Same here. At first when i got boot screen, i thought i blew it, but it took few minutes to urn up...
it happened twice to me. Wipe cache at first ... if it doesn't boot, wipe all.
Good luck!
I wipe all before every flash.
I flash the rom "update-cm-7.0.0-RC2-click-signed.zip" and after the gapps "gapps-gb-20110307-signed.zip".
On my screen, I saw only "TATTOO". , I waited during 10 minutes...
charlesdg said:
I wipe all before every flash.
I flash the rom "update-cm-7.0.0-RC2-click-signed.zip" and after the gapps "gapps-gb-20110307-signed.zip".
On my screen, I saw only "TATTOO". , I waited during 10 minutes...
Click to expand...
Click to collapse
try other rom file. and don't install gap yet. I had been there too.
I tried the rom "FroYo AOSP(2.2.2_r1) for Tattoo v0.3 released" and it works!
How can I install cyanogenmod 7? which rom can I use from cyanogenmod 7?
I tried repeating installation 6 times then it worked. I think install isn't clean. try again.
with which rom?
Try latest cyanogen rom rc - and here you will find all the info.
It's really great, try it.
charlesdg said:
I wipe all before every flash.
I flash the rom "update-cm-7.0.0-RC2-click-signed.zip" and after the gapps "gapps-gb-20110307-signed.zip".
On my screen, I saw only "TATTOO". , I waited during 10 minutes...
Click to expand...
Click to collapse
I have the same problem. Today I've tried the RC3 without being able to boot it, stuck at Tattoo logo. Doing a logcat I see many "DEBUG" row. The previous nightly build 31 boot correctly but after a while hang and sometime the system reboot itself. The nFinityGB 0.92 and previous, despite being CyanogenMod based, runs correctly. I've not been able to figure why I have so many problem with a rom that for most people is rock solid.
Please let me know if nFinityGB rom works correctly.
Have had success booting RC2.2 & RC3
I have had no problems flashing or booting Cyanogen 7 RC2.2 and RC3, using Rom Manager from Android market.
The problem seems to be solved in RC3, but the default cpu speed is too high to boot without getting some instability. At the third try I've been able to get into cpu settings to lower the maximum speed to 615 MHz. Now it works without stabilty issues.
Hey guys someone please help me out...even im stuck with the same problem....
Boot LOOPs continuously... i dont find any solution to this... phone isnt working atol and if i want to get back to the stock rom it says "USB CCONNECTION ERROR" so im really in a bad situation here....
guess have to travel to college without music (
I try the CM7 RC4 and the rom is bootlooping when I launch it! :-s
I went back on the CM6 :-(
charlesdg said:
I try the CM7 RC4 and the rom is bootlooping when I launch it! :-s
I went back on the CM6 :-(
Click to expand...
Click to collapse
If you feel dare, you can use this little init script that i've created for personal use. It sets a maximum cpu frequency of 528MHz in the early boot phase, allowing the phone to be stable. Once the phone booted, you can change the cpu speed using the CM Settings menu.
To place it in the correct directory, you must use adb.
- Just download it somewhere in your computer
- rename it removing the .txt extension (the resulting name will be 02slowdown)
- normally flash the CyanogenMod rom and do not reboot
- connect the usb cable between the phone and the computer
- mount the /system partition using the Clockwork storage and mounts menu
- copy the script in the /system partition with the command
Code:
adb push 02slowdown /system/etc/init.d/
- change the script owner with
Code:
adb shell chown root:shell /system/etc/init.d/02slowdown
- change the permissions with
Code:
adb shell chmod 750 /system/etc/init.d/02slowdown
- reboot and cross your finger
Now the phone should boot regularly without getting nasty FC
Hope this will help someone.
There is another way to apply this workaround: you can open the zipped rom with 7zip or something like that and put the "02slowdown" script in the /system/etc/init.d subdirectory of the archive. I used this method to flash the cm7 stable version.
my first reboot took a bit longer too. I just waited and voilá. Droid skater and CM7 installed.
lupp0l0 said:
If you feel dare, you can use this little init script that i've created for personal use. It sets a maximum cpu frequency of 528MHz in the early boot phase, allowing the phone to be stable. Once the phone booted, you can change the cpu speed using the CM Settings menu.
To place it in the correct directory, you must use adb.
- Just download it somewhere in your computer
- rename it removing the .txt extension (the resulting name will be 02slowdown)
- normally flash the CyanogenMod rom and do not reboot
- connect the usb cable between the phone and the computer
- mount the /system partition using the Clockwork storage and mounts menu
- copy the script in the /system partition with the command
Code:
adb push 02slowdown /system/etc/init.d/
- change the script owner with
Code:
adb shell chown root:shell /system/etc/init.d/02slowdown
- change the permissions with
Code:
adb shell chmod 750 /system/etc/init.d/02slowdown
- reboot and cross your finger
Now the phone should boot regularly without getting nasty FC
Hope this will help someone.
Click to expand...
Click to collapse
Thanks man! It works for the rom CM7 stable mod
charlesdg said:
Thanks man! It works for the rom CM7 stable mod
Click to expand...
Click to collapse
I'm glad to be useful!
There is another way to apply this workaround: you can open the zipped rom with 7zip or something like that and put the "02slowdown" script in the system/etc/init.d subdirectory of the archive. I used this method to flash the cm7 stable version.
Sent from my HTC click using XDA App
lupp0l0 said:
I'm glad to be useful!
There is another way to apply this workaround: you can open the zipped rom with 7zip or something like that and put the "02slowdown" script in the system/etc/init.d subdirectory of the archive. I used this method to flash the cm7 stable version.
Sent from my HTC click using XDA App
Click to expand...
Click to collapse
If I don't, every times I launch cm7, I have to do the manipulation (with adb) explain above?
Hi all
Im trying to compile OmniRom for Galaxy Note 2 N7100.
Did everything as instructed.
When running "brunch n7100" I have an error:
=============================================
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/samsung/n7100/omni_n7100.mk]]: "vendor/samsung/smdk4412-common/common-vendor.mk" does not exist. Stop.
WARNING: Trying to fetch a device that's already there
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/samsung/n7100/omni_n7100.mk]]: "vendor/samsung/smdk4412-common/common-vendor.mk" does not exist. Stop.
** Don't have a product spec for: 'omni_n7100'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
=============================================
What should I do to fix it?
Thanks
EDIT: OK, "The Muppets", of cause. Not it builds...
sms2000 said:
EDIT: OK, "The Muppets", of cause. Not it builds...
Click to expand...
Click to collapse
First off, I'd use DonkeyCoyote instead of TheMuppets. Entropy said TheMuppets wouldn't work, but he might have been speaking about only one device. Still I'd use DonkeyCoyote instead.
Still not building?
PonsAsinorem said:
First off, I'd use DonkeyCoyote instead of TheMuppets. Entropy said TheMuppets wouldn't work, but he might have been speaking about only one device. Still I'd use DonkeyCoyote instead.
Still not building?
Click to expand...
Click to collapse
I'm using VM on Win7 8Gb machine so it's slow. Last time it stopped on Email right after successfully building boot.img.
Attempting to rebuild.
I'll try my next with DonkeyCoyote.
sms2000 said:
I'm using VM on Win7 8Gb machine so it's slow. Last time it stopped on Email right after successfully building boot.img.
Attempting to rebuild.
I'll try my next with DonkeyCoyote.
Click to expand...
Click to collapse
It didn't not stop...
Actually it is compiling libchromodium.so (forget how it spell), which is 1.2GB in size.
Just let it run for few hours, it will completed eventually.
PS: I'm using VM on Win8.1 4GB, no complain here.
Sent from Windows 98
Yep, it fails again and again on 'libwebviewchromium.so'. The well known 'Error 1' aka not enough RAM.
I recently built a dedicated computer (8Gb + Haswell 3220) just for ROM compiler but have no time to install it properly. Dealing with VMs is not good.
My VM has 4Gb RAM of total 8Gb installed. I know I need 8+ but have to wait till new RAM received.
For now the thread is on hold.
Thanks for all your help.
EDIT: Just for the small experiment I added a 8Gb 'swap' partition to VM and the following build succeeded using no more than 450Mb of it.
I think we need 6 to 8Gb of RAM for good.
Now the question is would it boot and run for good? But we will see...
Ya I did set the swap partition to 8gb... And it will boot nicely.
If it didn't boot, jus replace/delete the media_profiles.xml
Another note, my Bluetooth and hardware decoding /encoding fail... Pls test it on ur system too.
Sent from Windows 98
dynomist said:
Ya I did set the swap partition to 8gb... And it will boot nicely.
If it didn't boot, jus replace/delete the media_profiles.xml
Another note, my Bluetooth and hardware decoding /encoding fail... Pls test it on ur system too.
Sent from Windows 98
Click to expand...
Click to collapse
I indeed failed to boot. Just the black screen with nothing. I think it was a very bad idea to use TheMuppets with "jallybean".
And what is "media_profiles.xml" for? And where?
U r using jb blob?
i think OmniRom hv all the stuff u need
http://docs.omnirom.org/Samsung_Galaxy_Note_II
___
Btw did ur screen show omnirom animation?
If yes u r lucky, u need to enabled the ro.adb.secure=0 in ur build.prop, then only you can use adb without authorization to troubleshoot.
Type# adb logcat > logcat.txt
___
Google media profile...
Sent from Windows 98
dynomist said:
U r using jb blob?
i think OmniRom hv all the stuff u need
http://docs.omnirom.org/Samsung_Galaxy_Note_II
___
Btw did ur screen show omnirom animation?
If yes u r lucky, u need to enabled the ro.adb.secure=0 in ur build.prop, then only you can use adb without authorization to troubleshoot.
Type# adb logcat > logcat.txt
___
Google media profile...
Sent from Windows 98
Click to expand...
Click to collapse
Yes, if you can download the closed source parts from the phone itself. I cannot. Something wrong with switching 'adbd' to 'root'. It switches sort of but locks at the downloading (never finishes).
Currently I'm recompiling with 'DonkeyCoyote'.
'Nightly' build fails to pass boot animation
I downloaded and installed OmniRom Nightly. Not good.
It cannot pass the boot animation. The OMNI BA just loops across different colors for 15 minutes already.
As I remember the same problem I have with any AOSP or CM ROM. I suspect the problem is the boot loader related.
When I installed my first 4.3 ROM it required the latest BL and I flashed it. Should I downgrade now? Which version of BL works for sure and where can I find it?
Thanks.
EDIT: I verified. My Bootloader - MJ5. Is it OK?
EDIT 2: Downgraded to DMF2 and succeeded installing OmniRom Nightly. Testing...
glad that you able to solve the booting prob...
pls update the roms status after u done with your testing