Database Users

[wip] icedroid/froozendroid [ics-sdk] Still not booting

First of all i want to give all my Thanks To mike1986
For Letting me use Android Revolution HD as Base for this port: http://forum.xda-developers.com/show....php?t=1245892
This is an attempt to get the ICS-SDK Port for our beloved EEE-Pad's
ive been working on this for a half day and i came so far that it do boot up to black screen, as feonix friend did,
now i need to edit kernel to load the screen properly (yes this probably caused by the kernel)
still no sucess
Before commenting, I appreciate all your help, i seriously do, just please ask before what iv'e done instead of say what i have to do
To do

RESERVED!
ICEDROID/FROOZENDROID
V0.1
#edited boot image, makes it load correct framework files
Gets passed the asus logo!
Now got it to boot to black screen!
YES Feonix. I came here to!

Reserved also!
Upcoming
Edit bootfiles, currently screen is not started correctly!

Will this flash over a honeycomb rom?
When i had a galaxy s we had to repartition going from 2.2-2.3. As ICS is such a change from H, i just wanted to check.
Ps. Good work so far. Thanks.
Sent from my Transformer TF101 using xda premium

Reopening - let's make sure we all stay on topic and contribute to real development

[WIP] ICS SDK-Port
Ok so iv'e been following the "developer's" foox22
THANKS TO ANDROID REVOLUTION HD (Mike1986) for letting me use their port as a base of this!
(my 1.st zip was this way but then i got no boot.img that was optimized for this)
Forgive me for this post/topic, but this is the zip that should make the ICS to boot,
if you notice its a black and nothing else then its should be due to no "edited build.prop of our resolution!
that's why someone here before never got it to "boot"
http://www.multiupload.com/IU8R71F500
if this doesn't boot up, try get a logcat
And yes you all other developers can try get me a logcat // REGARDS

Im gonna delete your other thread

Do we have a list of what may not work currently?

acdcking12345 said:
Do we have a list of what may not work currently?
Click to expand...
Click to collapse
i need to know what if its loading properly, if anyone just can try V007, as that's the one that is correct, boot.img loads all correct framework file's if it doesn't boots up then its a, screen resolution problem or a lib problem,

about to flash in a min when back up finishes. will report
just hangs on black screen after eeepad splash

tomqman said:
about to flash in a min when back up finishes. will report
just hangs on black screen after eeepad splash
Click to expand...
Click to collapse
black screen, you did wipe everything ??

Moving this to General - there really isn't any real development going on other than some copies, pastes, and asking testers to bork their device. The OP can't test this on his own device but is asking others to do it for him. This is not development. When something of substance happens - then create a new thread that is actual development in the development section.

ok so to repack the boot.img
blobpack <headerfile=kernelblob.HEADER> <outfile=kernelblob> <partitionname=? kernelblob.ebt or kernelblob.LNX > <partitionfile=kernelblob.ebt or kernelblob.LNX >
and is this even nessesary ?_? kernelblob.LNX-config
what did this come from, after i repacked the kernelblob.LNX O___o

http://android.modaco.com/topic/348194-04-nov-icl23d-galaxy-nexus-boot-recovery-system-dump/
Did you see this?

Ranatsu said:
http://android.modaco.com/topic/348194-04-nov-icl23d-galaxy-nexus-boot-recovery-system-dump/
Did you see this?
Click to expand...
Click to collapse
leaked o__O test build omfg thats so cool, even if its avaible for sdk!
anyhow im sure we cant use it :/

SWEATTAIMI said:
leaked o__O test build omfg thats so cool, even if its avaible for sdk!
anyhow im sure we cant use it :/
Click to expand...
Click to collapse
You are right, it's no use for us... the Galaxy Nexus has NEON support, all binaries are compiled with that, and our TF (and every Tegra2 tablet) misses NEON...

fonix232 said:
You are right, it's no use for us... the Galaxy Nexus has NEON support, all binaries are compiled with that, and our TF (and every Tegra2 tablet) misses NEON...
Click to expand...
Click to collapse
Got it anyway

[Q] Anyone working on miui 4.0?

Now that we have a pretty good android 4.0 port, is anyone working on a port of miui 4?

I think this is 4.0 based http://forum.xda-developers.com/showthread.php?t=1481168

Davoss said:
I think this is 4.0 based http://forum.xda-developers.com/showthread.php?t=1481168
Click to expand...
Click to collapse
No it isn't...
Sent from my Huawei Ideos X5 using xda premium

Sorry, my mistake. I saw video on youtube with this rom, and there was android 4.0.3 in settings.

MIUI au (australia) have a desire z port of miui 4.0, but from my previous experience of porting, I am not the person to port it. I cant even get stockwells script to work properly. Maybe I will try revisit it when I set ubuntu up in virtualbox again. It might be possible to pull files from Aurora and use the script with them.
Just got to get GB installed when Huawei finally release it for atmel screens and then can play again.

PaulMilbank said:
MIUI au (australia) have a desire z port of miui 4.0, but from my previous experience of porting, I am not the person to port it. I cant even get stockwells script to work properly. Maybe I will try revisit it when I set ubuntu up in virtualbox again. It might be possible to pull files from Aurora and use the script with them.
Just got to get GB installed when Huawei finally release it for atmel screens and then can play again.
Click to expand...
Click to collapse
I have tried (and failed) to hack/port using this guide (base ROM using dzo's Aurora, and desire z MIUI 4 for port files):
http://forum.xda-developers.com/showthread.php?t=1499411
Every attempt was just a bootloop - with adb in recovery, all ported files appeared to be in /system with the right perms, but still no go..
Anyone else care to have a go?

haydnlj said:
I have tried (and failed) to hack/port using this guide (base ROM using dzo's Aurora, and desire z MIUI 4 for port files):
http://forum.xda-developers.com/showthread.php?t=1499411
Every attempt was just a bootloop - with adb in recovery, all ported files appeared to be in /system with the right perms, but still no go..
Anyone else care to have a go?
Click to expand...
Click to collapse
I have bricked 1 device trying to port (not with this guide), but you can try with this guide:
Porting ROM
It might work. It'll make an "universal" port, which might work.

dev activity

this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull

demonoid phenomenom said:
this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull
Click to expand...
Click to collapse
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.

jeah thats right, i was wondering because my expirience with atrix 2 , previous to the ics update, i was using supercharger rom series, but again i understand that they got a leak to work on, and a bootstrap to flash the restores they where creating, and that stock leaked rom was awesome
sent from the gray stuff inside my skull

mattlgroff said:
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.
Click to expand...
Click to collapse
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?

Le_Poilu said:
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?
Click to expand...
Click to collapse
Would be nice to know for sure. The current methods cannot find 'Android Magic'.

I'm looking forward to seeing this forum get some custom ROMs too...

Looks like progress is getting on with it now

Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.

tiberiu24 said:
Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.
Click to expand...
Click to collapse
You won't be able to build a full android system from that source. The most you can do is
Code:
$ . build/envsetup.sh
$ lunch generic_x86-eng
$ make [I]target[/I]
Where target is something like out/target/product/generic/system/bin/bluetoothd or bluetoothd

I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Sent from my GT-I9300 using xda app-developers app

hiemanshu said:
I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Click to expand...
Click to collapse
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either

turl1 said:
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either
Click to expand...
Click to collapse
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H

hiemanshu said:
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H
Click to expand...
Click to collapse
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom

turl1 said:
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom
Click to expand...
Click to collapse
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me

hiemanshu said:
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me
Click to expand...
Click to collapse
Let's continue talking on PM then
re. 2, I actually did need to patch build on AOSP after all . CM on the other hand, has BOARD_CUSTOM_BOOTIMG_MK from the tf tablets.

Hey I posted a rom over at droidrzr.com for use till aosp is ready. This should be enough till we get a jb leak
Sent from my XT890 using Tapatalk 2

Hi Folks
While I don't own a RAZR I , I have been Jaffing around with building CM10.1 and AOSP for x86, I've been getting in going on my FX8120, just need to sort the OpenGLES MESA drivers out.
Anyways I've got CM10.1 built for x86 using the mr1-staging branch ( I think it's been merged to cm10.1 ) and an edited mini-x86 device tree .
Busybox was a B**stard to build though, although on one of the branches there is an .config-minimal-x86 .config-full-x86, still needed tweaking tho.
I submitted my patches http://review.cyanogenmod.org/#/c/27377/ and http://review.cyanogenmod.org/#/c/27373/, however It seems x86 isn't top of cm's agenda.... or I'm missing something about assigning reviewers.
Obviously a base x86 build is only part of the story for you guys as you'll face all the regular problems that emedded devices have, not checked the specs for the RazR but I'm sure there's some binary blobs in your future,
Hack On Folks! :good:

Can anybody port jelly bean miui for motorola bravo???

CAN ANYBODY PORT JELLY BEAN MIUI FOR MOTOROLA BRAVO??? DEFY already has miui JB,here is the link:http://forum.xda-developers.com/showthread.php?t=1161110

hiandro said:
CAN ANYBODY PORT JELLY BEAN MIUI FOR MOTOROLA BRAVO??? DEFY already has miui JB,here is the link:http://forum.xda-developers.com/showthread.php?t=1161110
Click to expand...
Click to collapse
I could, but it would be a couple of days at least before I could even try. I'm busy making stock roms for the Atrix HD from its fastboots and converting the Xperia Z XXHDPI icons to XHDPI for a rom I'm working on. Might have to test an Atrix HD Miui as well . Once I'm done with that crap I'll give it a shot.
To do it yourself, use a PC a zip manager, and text editor -- 7-Zip & Notepad ++ for Windows, File Roller & Gedit on Linux, Whatever's appropriate on a Mac~
The apps I recommend are the one that I use for doing this and know work properly for what we're doing. DO NOT USE STOCK NOTEPAD OR WORDPAD ON WINDOWS -- YOU'VE BEEN WARNED.
Use Latest Quarx CM10 for Bravo and Latest Defy MIUI
Open Defy Miui
Delete libbayercamera.so, liboemcamera.so, libsoccamera.so
Take any think that says libcamera from Bravo CM10 from /system/lib and put them in Defy Miui zip (libcamera_client.so, libcameraservices.so, libkobecamera.so)#
Go to /system/lib/hw in Defy Miui
Rename any file with jordan to kobe** (gps.jordan.so to gps.kobe.so, camera.jordan.so to camera.kobe.so -- same for the rest)
Open Miui build.prop
Search and Replace works good for this part (CTRL+H with Linux's Gedit)
Replace any jordan with kobe**
Replace any 525\526 with 520*
Replace any Defy with Bravo*
Go to the bottom, set camera to ClassA, 3m, & delete the 2 flash lines
Save build.prop
Go to /system/etc in Defy Miui
Replace mot_ise_imager_cfg.bin
Replace media_profiles.xml
Delete the Defy camera cal files
IF the Miui rom is custom kernel
Go to /system/bootmenu/ in Miui Defy and delete everything. Add in /system/bootmenu from Quarx Bravo CM10%$
Go to /system/lib/modules in Miui Defy and delete everything, replace with Bravo CM10.%
Click to expand...
Click to collapse
The only other thing that might need to be done is replacing Miui's /system/lib/libandroid_runtime.so. If it boots and runs you don't have to. If it loops, replace it.
* These can be skipped if you don't mind being branded as a Defy
** These two are mutually exclusive, whatever the value is in build.prop is what the gps.propvalue.so should be in /system/lib/hw -- you'll bootloop if they're different
# Can be skipped if you don't take pictures or would like to use the Defy's libsoccamera.so to take 16:9 848x480 widescreen videos. Its one or the other -- Defy driver with no photo camera but better\widescreen videos or Bravo driver with photo camera but only 4:3 aspect videos.
$ This is to use the Bravo's kernel and ramdisk, if Miui is stock kernel based, ignore this step
% Custom Kernel roms only
~ I've only ran a Mac for 30 minutes, OS 7 or 8, and all I did was make it cuss and say dumb things with the text to speech option. I couldn't wrap my head around a mouse with only 1 clicker :silly:
Funny, the above reads really similar to how you port basically any Defy rom to the Bravo ICS+ and I know I've posted that tutorial before. These same instructions work for GB roms as well, just slightly modify accordingly.

thanks man!!
skeevy420 said:
I could, but it would be a couple of days at least before I could even try. I'm busy making stock roms for the Atrix HD from its fastboots and converting the Xperia Z XXHDPI icons to XHDPI for a rom I'm working on. Might have to test an Atrix HD Miui as well . Once I'm done with that crap I'll give it a shot.
To do it yourself, use a PC a zip manager, and text editor -- 7-Zip & Notepad ++ for Windows, File Roller & Gedit on Linux, Whatever's appropriate on a Mac~
The apps I recommend are the one that I use for doing this and know work properly for what we're doing. DO NOT USE STOCK NOTEPAD OR WORDPAD ON WINDOWS -- YOU'VE BEEN WARNED.
Use Latest Quarx CM10 for Bravo and Latest Defy MIUI
The only other thing that might need to be done is replacing Miui's /system/lib/libandroid_runtime.so. If it boots and runs you don't have to. If it loops, replace it.
* These can be skipped if you don't mind being branded as a Defy
** These two are mutually exclusive, whatever the value is in build.prop is what the gps.propvalue.so should be in /system/lib/hw -- you'll bootloop if they're different
# Can be skipped if you don't take pictures or would like to use the Defy's libsoccamera.so to take 16:9 848x480 widescreen videos. Its one or the other -- Defy driver with no photo camera but better\widescreen videos or Bravo driver with photo camera but only 4:3 aspect videos.
$ This is to use the Bravo's kernel and ramdisk, if Miui is stock kernel based, ignore this step
% Custom Kernel roms only
~ I've only ran a Mac for 30 minutes, OS 7 or 8, and all I did was make it cuss and say dumb things with the text to speech option. I couldn't wrap my head around a mouse with only 1 clicker :silly:
Funny, the above reads really similar to how you port basically any Defy rom to the Bravo ICS+ and I know I've posted that tutorial before. These same instructions work for GB roms as well, just slightly modify accordingly.
Click to expand...
Click to collapse
I've been thinking to dive into developer's world ,you know.and i think this will be great stuff to start with..,THANKS A LOT skeevy420, i will certainly start working now.
I see, you are enjoying your new Atrix HD. good for you man and also i hope you will not leave bravo development(we need you)http://forum.xda-developers.com/ima...um.xda-developers.com/images/icons/icon10.gif

hiandro said:
I've been thinking to dive into developer's world ,you know.and i think this will be great stuff to start with..,THANKS A LOT skeevy420, i will certainly start working now.
I see, you are enjoying your new Atrix HD. good for you man and also i hope you will not leave bravo development(we need you)http://forum.xda-developers.com/ima...um.xda-developers.com/images/icons/icon10.gif
Click to expand...
Click to collapse
I'm not. I just have to play with my new toy for a bit.
Good luck with that. I'll help you test if you get it going.
I have my hands full trying to get any Atrix HD ICS rom to work with the AT&T JB kernel. Best I've done so far is getting the Canadian Bell ICS to finish gapps setup and get to the homescreen. Bootloops about a minute after that and I'll get maybe 30 seconds of screen time -- stressing maybe cause it only happened 3 out of 8 tries.. Can't get a logcat or even have the phone recognized over usb. Getting it to a partially working system, even if only for a minute, lets me know that it could possibly fully work.

Highly unstable
skeevy420 said:
I'm not. I just have to play with my new toy for a bit.
Good luck with that. I'll help you test if you get it going.
I have my hands full trying to get any Atrix HD ICS rom to work with the AT&T JB kernel. Best I've done so far is getting the Canadian Bell ICS to finish gapps setup and get to the homescreen. Bootloops about a minute after that and I'll get maybe 30 seconds of screen time -- stressing maybe cause it only happened 3 out of 8 tries.. Can't get a logcat or even have the phone recognized over usb. Getting it to a partially working system, even if only for a minute, lets me know that it could possibly fully work.
Click to expand...
Click to collapse
I did whatever you said and camera,WiFi worked well.But whenever I try to create Google account the device just reboots.It is highly unstable,only about 80 MB ram is free(slow),also music player also showed same problem as Google account did,
How can I make it stable,any idea???

If you can, upload what you're working on and I'll try it out. That'll be easier than asking for logcats and giving you ideas to try.
What gapps did you use? I always use the Defy Minimal gapps.

ok
skeevy420 said:
If you can, upload what you're working on and I'll try it out. That'll be easier than asking for logcats and giving you ideas to try.
What gapps did you use? I always use the Defy Minimal gapps.
Click to expand...
Click to collapse
i didnt use any gapps, i thought miui already had gapps by default.i just changed build.props and others that you told in earlier post.
where can i upload the zip so that you can download????

hiandro said:
i didnt use any gapps, i thought miui already had gapps by default.i just changed build.props and others that you told in earlier post.
where can i upload the zip so that you can download????
Click to expand...
Click to collapse
Gapps depends on the rom -- some come with them, some don't.
You can upload to anywhere -- Mediafire, Google Drive, Dropbox, whatever's convenient for you.

hiandro said:
CAN ANYBODY PORT JELLY BEAN MIUI FOR MOTOROLA BRAVO??? DEFY already has miui JB,here is the link:http://forum.xda-developers.com/showthread.php?t=1161110
Click to expand...
Click to collapse
a chinese guy is working on it , and he said its coming soon,
http://bbs.gfan.com/forum.php?mod=viewthread&tid=6022223&extra=page=1
this is the preview, sorry for my bad english

banyelaiwande said:
a chinese guy is working on it , and he said its coming soon,
http://bbs.gfan.com/forum.php?mod=viewthread&tid=6022223&extra=page=1
this is the preview, sorry for my bad english
Click to expand...
Click to collapse
looks nice and clean,
ok man ,you have to keep on eye on that and share the link when he's done.

is up
hiandro said:
looks nice and clean,
ok man ,you have to keep on eye on that and share the link when he's done.
Click to expand...
Click to collapse
The rom is alredy posted in the first post of the trhead in the link i am downloading right now but i dont think i will try it today i am hapy with the 4.2.2 http://forum.xda-developers.com/images/smilies/biggrin.gif

everal1810 said:
The rom is alredy posted in the first post of the trhead in the link i am downloading right now but i dont think i will try it today i am hapy with the 4.2.2 http://forum.xda-developers.com/images/smilies/biggrin.gif
Click to expand...
Click to collapse
Is 4.2.2 available for bravo?,give me the link please...

here
hiandro said:
Is 4.2.2 available for bravo?,give me the link please...
Click to expand...
Click to collapse
just search in the 4.1.1 thread in motorola bravo development some times for know when there are a new update
in the first page of the 4.1.1 thread you can search for the quarks build and in the server just search for 10.1 bavo sorry i cant post links xD

skeevydude said:
I could, but it would be a couple of days at least before I could even try. I'm busy making stock roms for the Atrix HD from its fastboots and converting the Xperia Z XXHDPI icons to XHDPI for a rom I'm working on. Might have to test an Atrix HD Miui as well . Once I'm done with that crap I'll give it a shot.
To do it yourself, use a PC a zip manager, and text editor -- 7-Zip & Notepad ++ for Windows, File Roller & Gedit on Linux, Whatever's appropriate on a Mac~
The apps I recommend are the one that I use for doing this and know work properly for what we're doing. DO NOT USE STOCK NOTEPAD OR WORDPAD ON WINDOWS -- YOU'VE BEEN WARNED.
Use Latest Quarx CM10 for Bravo and Latest Defy MIUI
The only other thing that might need to be done is replacing Miui's /system/lib/libandroid_runtime.so. If it boots and runs you don't have to. If it loops, replace it.
* These can be skipped if you don't mind being branded as a Defy
** These two are mutually exclusive, whatever the value is in build.prop is what the gps.propvalue.so should be in /system/lib/hw -- you'll bootloop if they're different
# Can be skipped if you don't take pictures or would like to use the Defy's libsoccamera.so to take 16:9 848x480 widescreen videos. Its one or the other -- Defy driver with no photo camera but better\widescreen videos or Bravo driver with photo camera but only 4:3 aspect videos.
$ This is to use the Bravo's kernel and ramdisk, if Miui is stock kernel based, ignore this step
% Custom Kernel roms only
~ I've only ran a Mac for 30 minutes, OS 7 or 8, and all I did was make it cuss and say dumb things with the text to speech option. I couldn't wrap my head around a mouse with only 1 clicker :silly:
Funny, the above reads really similar to how you port basically any Defy rom to the Bravo ICS+ and I know I've posted that tutorial before. These same instructions work for GB roms as well, just slightly modify accordingly.
Click to expand...
Click to collapse
I did!
WIUI Defy v4 + cm-10-20130507-NIGHTLY-mb520 from Quarx
i made MIUI Motorola Bravo port, thanks for your help.
here is file for test on your bravo:
https://www.dropbox.com/s/s84tvlh8dxqn7cx/WIUI_v4_JB_Bravo_3_1_21.zip

Porting CyanogenMod to Desire 820s MT6752

I came across CM12.1 rom for Lenovo K3 Note on needrom. Considering that K3 have the same chipset as ours, I've been thinking that it can be ported to our device.
I've tried to port it past few days but failed. Any developer would come up and try to port it?

What have you done? Device tree something else?

Nope. Just changing libs here and there, according to this guide. I'm still noob in porting roms so I can't do much.

amirarsyad97 said:
I came across CM12.1 rom for Lenovo K3 Note on needrom. Considering that K3 have the same chipset as ours, I've been thinking that it can be ported to our device.
I've tried to port it past few days but failed. Any developer would come up and try to port it?
Click to expand...
Click to collapse
Did you edit the updater script?

Gibz97 said:
Did you edit the updater script?
Click to expand...
Click to collapse
Yes. I'm actually having problem in repacking system.new.dat files. The same as the guy face here. Finding the solution require me to learn Linux. I'm still new at Linux, so I need some time to learn.
Other than that is okay (perhaps). I followed some other guides like http://forum.xda-developers.com/android/development/guide-how-to-port-lollipop-based-roms-t3223938 and http://forum.xda-developers.com/showthread.php?t=2707438.
Oh and one more thing, the rom is ported by @Cheshkin. I've tried to seek his permission to port the rom through pm, but still no answer. So I cannot post the rom here (if I done porting it) without his permission.

amirarsyad97 said:
Yes. I'm actually having problem in repacking system.new.dat files. The same as the guy face here. Finding the solution require me to learn Linux. I'm still new at Linux, so I need some time to learn.
Other than that is okay (perhaps). I followed some other guides like http://forum.xda-developers.com/android/development/guide-how-to-port-lollipop-based-roms-t3223938 and http://forum.xda-developers.com/showthread.php?t=2707438.
Oh and one more thing, the rom is ported by @Cheshkin. I've tried to seek his permission to port the rom through pm, but still no answer. So I cannot post the rom here (if I done porting it) without his permission.
Click to expand...
Click to collapse
If you have an idea for kernel, I'll help you

amirarsyad97 said:
Yes. I'm actually having problem in repacking system.new.dat files. The same as the guy face here. Finding the solution require me to learn Linux. I'm still new at Linux, so I need some time to learn.
Other than that is okay (perhaps). I followed some other guides like http://forum.xda-developers.com/android/development/guide-how-to-port-lollipop-based-roms-t3223938 and http://forum.xda-developers.com/showthread.php?t=2707438.
Oh and one more thing, the rom is ported by @Cheshkin. I've tried to seek his permission to port the rom through pm, but still no answer. So I cannot post the rom here (if I done porting it) without his permission.
Click to expand...
Click to collapse
Let's wait for the response then

Would be graet to see CM to release this device's potential. Especially since HTC is taking it's sweet time with 6.0 update and 5.1 was officially skipped.
Anyway if you would need some testers I would gladly help.

Good news! The permission has been granted. I will try my best to port this rom.

And what with 820n?
Sent from my HTC Desire 820 using XDA Free mobile app

Dragonfail said:
And what with 820n?
Sent from my HTC Desire 820 using XDA Free mobile app
Click to expand...
Click to collapse
We don't have 64-bit kernel sources for 820n MSM chipset

Hi @amirarsyad97, so did you manage to extract system files?

Gibz97 said:
Hi @amirarsyad97, so did you manage to extract system files?
Click to expand...
Click to collapse
I already did, but I can't repack it. So instead I tried looking for other roms while staying away from dat files - cm12.1 ulefone be touch 2 and blisspop k3 note.
Now I'm having problems with the kernel. The rom won't boot at all, the worse I can't get the dmesg.
I don't have much free time to explore kernels in detail. If anybody can help me with porting the kernel, it would be a pleasure.

amirarsyad97 said:
I already did, but I can't repack it. So instead I tried looking for other roms while staying away from dat files - cm12.1 ulefone be touch 2 and blisspop k3 note.
Now I'm having problems with the kernel. The rom won't boot at all, the worse I can't get the dmesg.
I don't have much free time to explore kernels in detail. If anybody can help me with porting the kernel, it would be a pleasure.
Click to expand...
Click to collapse
I will try porting the kernel using the kitkat kernel as base when I find time

Unfortunately, I did not succeed, I could not even get into the bootanimation. Hope someone can help us.
I am now trying to squeeze the Lollipop system partition so that we can liberate some more free space for the internal storage, hope it works

That would be the coolest thing???

Hello guys hope you have been doing great, Was too busy with school, exams and stuff.
Good news!! I have finally managed to boot into CM 12.1 after I successfully ported it today.
It's lightning fast but has some bugs: USB, bluetooth and Sim don't work currently and it needs some resizing of the framework images.
I will try to work on it until Sunday and hopefully someone else can take over with modifying it

Gibz97 said:
Hello guys hope you have been doing great, Was too busy with school, exams and stuff.
Good news!! I have finally managed to boot into CM 12.1 after I successfully ported it today.
It's lightning fast but has some bugs: USB, bluetooth and Sim don't work currently and it needs some resizing of the framework images.
I will try to work on it until Sunday and hopefully someone else can take over with modifying it
Click to expand...
Click to collapse
I was wondering how you can make the kernel work. Anyway good work!

amirarsyad97 said:
I was wondering how you can make the kernel work. Anyway good work!
Click to expand...
Click to collapse
Use this kernel and build.prop and use the original system (don't replace with stock files) https://mega.nz/#!c4USzSTL!rXmsjMYaxR9ECwNeiMjissLPuFRLBWBUSLIuwiBFwQk
Almost everything works right now except Bluetooth, camera and Sim

Great work keep it up
Sent from my HTC Desire 820 dual sim using XDA-Developers mobile app