Database Info

[ROM] CyanogenMod 6 For Vega (unofficial)

I have created the vendor files for the advnet vega based apon the cyanogen ones for the Gtab, and compiled CM6 for the vega. This is not supported by cyanogen's team yet as the vega isnt officialy supported by them yet so please take that into mind (dont ask for support on the cyanonen irc ect u probably wont get it) but feel free to ask support on this thred.
Nither me or the CyanogenMod team take no responsability for any damage caused bu this rom. by flashing it means u understand this risks and accept the risks.
What doesnt work :-
- Camera
- Rotation can be funny (if it works at all)
[UPDATE]
- Black Screen Of death can occur when rebooting (looking into this ASAP) so be prepared to restore
What works :-
- Every thing else (i think)
[INSTALL]
1) get the .zip file from the bottion of the post
2) copy it to SD card
3) reboot into recovery
4) MAKE NANDROID BACKUP
5) flash zip from recovery (you will get a boot write error thats normal)
6) reboot
7) DONE
[DOWNLOAD]
http://db.tt/UmV1dYK
[CREDITS]
CyanogenMod Team for there src
Bekit for the Gtab vendor this is based on
Anyone else i have forgotten
[MY VENDOR]
If anyone else wants to try and improve on this please feel free.
https://github.com/BuzzBumbleBee/android_device_vega/tree/froyo
(Please note at the current time the boot.img that the compile creates will not work on the vega to u will have to make one by extracting the original ramdisk from the boot.img)

thanks mate been tring with cyanogenmod for gtablet..gonna try now. THis bad boy vega need some action
got error message:
assert failed: package_extract_file("boot.img" ,"/temp/boot.img")
E:Error in /sdcard/CM-6.2.0-Vega.zip
(status 7)
Installation aborted.
edit: fixed.
I successfully installed, I put the original boot.img from vega into the zip, taking it for a spin now. Thanks Apache14.

I sold my Vega because of the screen imo wasnt great and the wi-fi issue.
Would have loved to have tried this rom though.
Good work !!!

Thanks to apache14 and everyone involved
How do we get market onto the tab. thanks in advance

Dunno about market any CM6 compatable gapps will work ..... also the adding boot.img isnt needed as there is no need to flash the boot.img (the stock advent one works pritty well for now)

Apache14 said:
Dunno about market any CM6 compatable gapps will work ..... also the adding boot.img isnt needed as there is no need to flash the boot.img (the stock advent one works pritty well for now)
Click to expand...
Click to collapse
thx mate, misread the first post

Anyone working on fixing the black screen of death on cold boot a lot of people are getting with clockwork? I know there are enough people who don't have CW installed because of this that anything that depends on it will have a more limited appeal.

arad85 said:
Anyone working on fixing the black screen of death on cold boot a lot of people are getting with clockwork? I know there are enough people who don't have CW installed because of this that anything that depends on it will have a more limited appeal.
Click to expand...
Click to collapse
I have installed clockwork a couple of times and no black screen of death. Its straight forward.
Follow the instruction paul gave on modaco.
Download the Recovery image and flash utility and extract to desktop
open terminal
adb devices to make sure your device is connected
cd to the directory of file you just extract
then type
adb push recovery.img /data/local/
adb push flash_image /data/local/
adb shell chmod 4755 /data/local/flash_image
adb shell /data/local/flash_image recovery /data/local/recovery.img
thats done.
If you on mcr 6, the vega reboot recovery is already installed if not download from the market.
cheers

alphaola said:
I have installed clockwork a couple of times and no black screen of death. Its straight forward.
Click to expand...
Click to collapse
Yes, it's very straightforward. I've done it a few times too and followed the instructions. I still get the bsod as do a number of others. Without CM installed, no bsod...
Try power cycling your Vega back-to-back using the power button. I bet you'll get it to bsod reasonably quickly.

BSOD
Some people have reported black screen of death when rebooting with the power menu. so be careful and be prepared to restore (or flash stock boot,img again)
I am looking into this error now and hope to have a fix pritty soon

Apache14 said:
I am looking into this error now and hope to have a fix pritty soon
Click to expand...
Click to collapse
Brilliant - thanks

Apache14 said:
Some people have reported black screen of death when rebooting with the power menu. so be careful and be prepared to restore (or flash stock boot,img again)
I am looking into this error now and hope to have a fix pritty soon
Click to expand...
Click to collapse
arad85 said:
Brilliant - thanks
Click to expand...
Click to collapse
i fixed it. Copy boot.img,system.img and ramdisk.img from vega into the cyanogenmod zip,then flash, it also boot into recovery using rom manager.
Note: Do not unzip the cyanogengenmod, just use winrar to open it and copy those files into it then close it

alphaola said:
i fixed it. Copy boot.img,system.img and ramdisk.img from vega into the cyanogenmod zip,then flash, it also boot into recovery using rom manager.
Click to expand...
Click to collapse
Sorry, being particularly thick today. How do I get hold of the three .img files?

arad85 said:
Sorry, being particularly thick today. How do I get hold of the three .img files?
Click to expand...
Click to collapse
download the advent vega system file from advent vega website,zip it using winrar.

alphaola said:
download the advent vega system file from advent vega website,zip it using winrar.
Click to expand...
Click to collapse
<facepalm>

arad85 said:
<facepalm>
Click to expand...
Click to collapse
no stress man. Its quite smooth and fast, love the animation as well

alphaola said:
no stress man. Its quite smooth and fast, love the animation as well
Click to expand...
Click to collapse
So I did all this, and now have a device that is....
... exactly the same as before but with CWR installed (even says it's MoDaCo ROM). The flashing process took only a few seconds and no boot write error. Am I missing something here?
EDIT: hang on... just realised the zip file was wrong!!

To get the market and apps
Download http://android.d3xt3r01.tk/cyanogen/gapps/gapps-mdpi-tegra-20101020-signed.zip, then flash using rom manager. then once you reboot you should get all your apps and market. enjoy

arad85 said:
So I did all this, and now have a device that is....
... exactly the same as before but with CWR installed (even says it's MoDaCo ROM). The flashing process took only a few seconds and no boot write error. Am I missing something here?
EDIT: hang on... just realised the zip file was wrong!!
Click to expand...
Click to collapse
ahahha mate,it works.
Download button savior to make navigation easy

Hello all
Really looking forward to a stable version with an idiot proof install for folks like me.
Great work
Rgds
Lok

[ROM](Working Update.zip) -> Defy Update.zip Cookie Cutter Rom

Defy Froyo 3.4.2 Cookie Cutter Rom​
Q. How Do I use the Update.zip?
A. Go to Market & Download Defy SD-Recovery & Install..
1. Next place the Update.zip on the /sdcard via PC
2. Turn on MoTo Phone Portal ( SD-Recovery is SD Based so you need to Turn Off USB Mass Storage )
3. ADB Debugging does not have to be Turned Off on my version
Once Booted into the Recovery apply the update.zip
wait a few minutes & it should be done...
Please Reads the notes I left in the Update.zip if you build a Custom Update.zip, this will save you trouble down the road.
What's Flashed?
A. Boot.img
B. dev_tree
C. Moto Blur 3.4.2 Rom ( Yes I know it's not the latest, built off what I had )
D. UNO & TMO-TV Removed
E. Rooted ( SU & Superuser )
F. Busybox Installed to xbin
G. Rest of Rom is stock
Once installed, remove eugene.apk from /system/app ( Old boot strap that need adb turned off before rebooting / defy sd-recovery does not have this issue)
Q. I Edited the update.zip & Now it fails verf. in recovery when trying to flash!
A. example of signapk on signing the edited update
java -Xmx1024m -jar signapk.jar -w testkey.x509.pem testkey.pk8 update1.zip update.zip
Download: Original Post

To Update other parts of the Phone: Add this to the update-scripts for what you are flashing.
If we had all these Parts from 2.1 we could go back.
package_extract_file("lbl", "/tmp/lbl");
write_raw_image("/tmp/lbl","lbl");
delete("/tmp/lbl");
package_extract_file("device_tree.bin", "/tmp/device_tree.bin");
write_raw_image("/tmp/device_tree.bin","devtree");
delete("/tmp/device_tree.bin");
package_extract_file("cdrom", "/tmp/cdrom");
write_raw_image("/tmp/cdrom","cdrom");
delete("/tmp/cdrom");
package_extract_file("logo.bin", "/tmp/logo.bin");
write_raw_image("/tmp/logo.bin","logo.bin");
delete("/tmp/logo.bin");
package_extract_file("umts_wrigleyref_build.bin", "/tmp/umts_wrigleyref_build.bin");
write_raw_image("/tmp/umts_wrigleyref_build.bin","bpsw");
delete("/tmp/umts_wrigleyref_build.bin");
package_extract_file("cdt.bin", "/tmp/cdt.bin");
write_raw_image("/tmp/cdt.bin","cdt.bin");
delete("/tmp/cdt.bin");

Hey eugene,
Glad to see you working on Defy too
I think this will be major help for developers and btw that 3.4.2 version did you used? since there are many of them.
Thanks.

um. 107 I think since it has a floating update.zip someplace & sbf.
Ill update to the latest when I start building roms
Sent from my MB525 using XDA App

i don't understand. is the boot.img still the signed cg35.smg?
if so, can't we just use the cmw to do that?
can you post more detailed chages you made over cmw?
other than the signapk and usb debugging described.
many thanks.

eugene373 - great work!
racca said:
i don't understand. is the boot.img still the signed cg35.smg?
if so, can't we just use the cmw to do that?
can you post more detailed chages you made over cmw?
other than the signapk and usb debugging described.
many thanks.
Click to expand...
Click to collapse
Same here, i'm pretty interested in more details, thank you

this Zip File is for what ?
Thanks
Greetings

you can not use cwm due encryption. If you dont know what an update.zip is stick to nandroid...
This is for rom builders.
Heading out, when I get home ill make it clearer.
Though, now that I think about it cwm might be fine due to the nature of how it works.
Ill test later and let everyone know
Sent from my MB525 using XDA App

So we are able to install updates via the "normal" Motorola Recovery mode? So we are able to get a "unbrickable" Defy?
Edit: got it myself. The ZIP File won't be recognized by the motorola recovery... anyway thanks for your job

Now, what can SD-recovery do? Can it write other partitions, like cdt.bin?

Simplestas said:
Now, what can SD-recovery do? Can it write other partitions, like cdt.bin?
Click to expand...
Click to collapse
Yes. I can add the string if you would like
eugene373 said:
To Update other parts of the Phone: Add this to the update-scripts for what you are flashing.
package_extract_file("lbl", "/tmp/lbl");
write_raw_image("/tmp/lbl","lbl");
delete("/tmp/lbl");
package_extract_file("device_tree.bin", "/tmp/device_tree.bin");
write_raw_image("/tmp/device_tree.bin","devtree");
delete("/tmp/device_tree.bin");
package_extract_file("cdrom", "/tmp/cdrom");
write_raw_image("/tmp/cdrom","cdrom");
delete("/tmp/cdrom");
package_extract_file("logo.bin", "/tmp/logo.bin");
write_raw_image("/tmp/logo.bin","logo.bin");
delete("/tmp/logo.bin");
package_extract_file("umts_wrigleyref_build.bin", "/tmp/umts_wrigleyref_build.bin");
write_raw_image("/tmp/umts_wrigleyref_build.bin","bpsw");
delete("/tmp/umts_wrigleyref_build.bin");
package_extract_file("cdt.bin", "/tmp/cdt.bin");
write_raw_image("/tmp/cdt.bin","cdt.bin");
delete("/tmp/cdt.bin");
Click to expand...
Click to collapse

eugene373 said:
Yes. I can add the string if you would like
Click to expand...
Click to collapse
CwM can do exactly the same afaik, i've already made quite a few update.zip with it.
after reading all your notes, do you actually mean that we can't use format on those patitions?
if you do, well, i learned it the hard way, and delete_recursive also works for me.
thanks for putting up an excellent example if not for anything else, it's much needed.

racca said:
CwM can do exactly the same afaik, i've already made quite a few update.zip with it.
after reading all your notes, do you actually mean that we can't use format on those patitions?
if you do, well, i learned it the hard way, and delete_recursive also works for me.
thanks for putting up an excellent example if not for anything else, it's much needed.
Click to expand...
Click to collapse
Correct, you can only format with the stock recovery ( Hence the reason why I used the Stock Recovery ) any Partition with cwm recovery will cause a non-booting system..
regarding cwm I've not tested it, so Likely it will work.. Steven is still working on the cwm recovery & there is no point in me adding another cwm bootstrap recovery... Mine is just pure stock & works perfect.
I'm still weeding through the /bin /etc file's to find exactly what needs left...
but main goal was to provide an example of what is needed to make an update.zip with out breaking the system.

what exactly is the benefit of this new method?

drsouly said:
what exactly is the benefit of this new method?
Click to expand...
Click to collapse
um? Your joking right!
Update versus a nandroid, I would have thought it was a no brainier....
Build & edit roms on the fly + being able to flash boot.img & downgrading is fine without sbf unless you screw up completely..

eugene373 said:
um? Your joking right!
Update versus a nandroid, I would have thought it was a no brainier....
Build & edit roms on the fly + being able to flash boot.img & downgrading is fine without sbf unless you screw up completely..
Click to expand...
Click to collapse
ok now i got it thx

drsouly said:
ok now i got it thx
Click to expand...
Click to collapse
no problem, wasn't sure if you was being a smart-ass or honestly didn't know...
either way, sorry If I offended you.
~Eugene

I didn't understand yet . I can or not apply the update file using stock recovery?
EDIT: forget I understood now.
Sent from my MB525 using XDA App

psicodelico said:
I didn't understand yet . I can or not apply the update file using stock recovery?
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Read OP.... Download Defy SD-Recovery from Market

Yeah, I read again slowly and understood.
Sent from my MB525 using XDA App

[MOD][Update: 12-Aug-2011]Rooted CG from CH Leak

Thanks to dangpzanco for the GREAT IDEA.
I finally got my Rooted GB working here. I can't provide a download link now but I'm going to do it later for sure.
Apparently there was a final signature check that was done somewhere after mounting the cache partition, preventing me from booting with a pure update.zip on top of froyo /system. Thanks to dangpzanco I could bypass it and get root.
Quick Guide (requires froyo, root and Droid2bootstrapper):
1. Download fixed SBF bellow. It's made from the CH leak containing ONLY: CG35.smg (boot) CG47.smg (recovery) CG61.smg (devtree) firmware.hmg (header) RAMDLD.smg (flash updater).
2. Download root_and_recovery.zip and copy it to SD Card.
3. Download full leaked SBF from General Forum (CH, signed) and use MotoAndroidDepacker to extract all images.
4. Copy the CG39.smg to /sdcard/
5. Boot into CWM
6. From CWM open adb shell and use this command: dd if=/sdcard/cg39.sm of=/dev/block/system
7. Still on CWM apply root_and_recovery.zip
8. Still on CWM wiped everything
9. Boot on bootloader and flash fixed SBF
10. Reboot

I actually did the same thing! I read it somewhere in one of the topics. I installed Defy BootMenu instead of CWM. Works great! Right now I've almost removed all the Chinese crap and got the GApps working (from CM7).
I also removed the Blur items for the Chinese SN's. I'll see if I can get Twitter and Facebook working with it.
2nd-init would be nice too actually. Does the method provided in the other thread work with this ROM?
Edit: the instructions were indeed from dangpzanco!

And right now I found a possible bug. My camera doesn't work. Everything is black and stays black. Photo's are take as they should however.
Can you check whether you have the same issue?

w0ndersp00n said:
And right now I found a possible bug. My camera doesn't work. Everything is black and stays black. Photo's are take as they should however.
Can you check whether you have the same issue?
Click to expand...
Click to collapse
Here it works fine. Have you tried to edit /system/build.prop?
Change device from ME722 to A953.

Yes, I changed it to A953...
Maybe I have deleted something that was necessary for the viewfinder... But what xD
Edit: Allright, nevermind. Somehow a reboot fixed it :-D On to the next step

Something bad happened when I tried to apply 2nd-init on this. The phone rebooted just after 2nd M logo not allowing me to get into CWM. Wierd, since CWM should take place before 2nd-init. Will need to raflash froyo and start over. We should find a way to root Gingerbread without CWM to make things faster.

That's odd indeed. I have to say, I think the CWM method of rooting is actually quite easy. For SuperOneClick I need to get my PC/laptop out every time and with the update.zip I can do it as I please.
I really hope you'll succeed wit 2nd-init. If you need help, just shout! Today and tomorrow I have enough time.
I'll make a nandroid of my current setup, so I can continue trying out stuff.

w0ndersp00n said:
That's odd indeed. I have to say, I think the CWM method of rooting is actually quite easy. For SuperOneClick I need to get my PC/laptop out every time and with the update.zip I can do it as I please.
I really hope you'll succeed wit 2nd-init. If you need help, just shout! Today and tomorrow I have enough time.
I'll make a nandroid of my current setup, so I can continue trying out stuff.
Click to expand...
Click to collapse
Yeps, it is easy indeed, but to do it I need to SBF froyo before installing GB again. In other words if I mess up the phone I will need to flash 2 versions instead of one. That's why it would be easier to flash just GB.

Hey there, nice I could help.
I think you could copy the /dev/block/system back after rooting and build the SBF with it.
@Milestone 2 (Finnaly on Gingerbread!)

dangpzanco said:
Hey there, nice I could help.
I think you could copy the /dev/block/system back after rooting and build the SBF with it.
@Milestone 2 (Finnaly on Gingerbread!)
Click to expand...
Click to collapse
I tried that with froyo but it didn't work.

you can try also this defy leaked gb rooted nandroid backup.
http://www.multiupload.com/SPZ8SIEC60
version 4.5.1-134 multilanguage.
use fixedsbf from new leaked milestone2 rom and milestone2patch from MS2Ginger thread.
In this rom /system/app/kpilogger.apk cause battery drain so delete it after install.

Something is seriously wrong... My backlight never shuts down. It's black, but when it's dark you'll see it's still on!
I actually can't change the brightness from settings. So I did a complete reinstall and the problem persists!
I'm using brightcontrol app now to adjust the brightness, but does anyone else has this issue? Or is it something I did?

r2beta0 can you please upload the nandroid of your system?
I try to get adb in CWM but it didn't recognize it.

julianlatasa said:
r2beta0 can you please upload the nandroid of your system?
I try to get adb in CWM but it didn't recognize it.
Click to expand...
Click to collapse
My system is messed. I still need to get 2nd-init to work. I'm having a lot of trouble trying to compile my custom version of logwrapper hijack. As I don't have experience in compiling stuff to ARM/Android it is being a pain in the a**. I'd appreciate some help here

Try setting up a QEMU environment with the GB leak kernel's zImage.
Edit: Now we can port CM7!!! Devtree.img is now signed.
@Milestone 2 (Finnaly on Gingerbread!)

dangpzanco said:
Try setting up a QEMU environment with the GB leak kernel's zImage
@Milestone 2 (Finnaly on Gingerbread!)
Click to expand...
Click to collapse
And how do I do that?
I tried some ways till this point:
- Installed CodeSourcery G++ Lite toolchain (could compile, but android didn't run)
- Installed NDK and tried some commands I could find on blog posts (no luck)
- Now I just finished setting up an ubuntu 10 VM with all the steps described on developer.android.com. I think I am now able to compile android system, but I don't want to as it will take a LOOONG time.
Do you know how do I build a specific module into android source? For example:
system/core/toolbox
I'm a developer, and have compiled stuff to run on linux/unix many times. But this ARM stuff is way complicated. Writing the code isn't the problem, but compiling is. Lots of flags I haven't seem before, and so on.

r2beta0 said:
And how do I do that?
Do you know how do I build a specific module into android source? For example:
system/core/toolbox
Click to expand...
Click to collapse
I just uncovered this answer by myself.
A 'make toolbox' on root folder seems to work just fine. Now I need a way to define new targets on android build system.

http://and-developers.com/
Has a page just for compiling the kernel from source. (I can't remember the link)
I also got stuck when trying to compile from AOSP... but I think you need to have ALL the files downloaded from source (specially the big prebuilt folder) even if you want to compile a single binary.
Well I'm not sure of anything...
Edit:Now I read what you wrote... so never mind you got it.
@Milestone 2 (Finnaly on Gingerbread!)

dangpzanco said:
http://and-developers.com/
Has a page just for compiling the kernel from source. (I can't remember the link)
I also got stuck when trying to compile from AOSP... but I think you need to have ALL the files downloaded from source (specially the big prebuilt folder) even if you want to compile a single binary.
Well I'm not sure of anything...
Edit:Now I read what you wrote... so never mind you got it.
@Milestone 2 (Finnaly on Gingerbread!)
Click to expand...
Click to collapse
Yeps I've made a full repo sync. It took 3 hours and is worth 6GB disk space

Great news! Can't wait to see a true custom ROM working
Just thought I'd share what I've learned: don't mess too much with your build.prop Somehow my modifications were the reason of my backlight not working right and making every app crash that wanted to use a sensor. But it's working again

[DEV] CM7 for Karbonn A9

I managed to successfully compile CWM Recovery from sources for A9, but with a few issues (key-mapping where touch buttons don't work, etc)
Decided to take the jump to compiling CM.
Modified the extract-files from sgs2 but I have no knowledge when it comes to libraries, proprietary files, 'blobs', what the options in the makefiles mean,etc.
I have absolutely no idea what I'm supposed to do next, as compiling for unsupported devices doesn't give me many search results. I have the CyanogenMod GB branch synced, and a device tree for A9 set up, with a few file modifications done.
Any and all help, references, links to explanations are welcome.
Managed to compile it, finally, check posts below.
Sources: https://github.com/Siarc/a9

Shark- said:
I managed to successfully compile CWM Recovery from sources for A9, but with a few issues (key-mapping where touch buttons don't work, etc)
Decided to take the jump to compiling CM.
Modified the extract-files from sgs2 but I have no knowledge when it comes to libraries, proprietary files, 'blobs', what the options in the makefiles mean,etc.
I have absolutely no idea what I'm supposed to do next, as compiling for unsupported devices doesn't give me many search results. I have the CyanogenMod GB branch synced, and a device tree for A9 set up, with a few file modifications done.
Any and all help, references, links to explanations are welcome.
Sources: https://github.com/Siarc/a9
Click to expand...
Click to collapse
Dude, the only help i could give is test the ROM , let me know when you want it and i will be more than happy to help :fingers-crossed:

I've spent a lot of time, and it's simply not worth it, cannot even manage to get it to compile in the right directory. I can't believe there are so many people who have the knowledge but not one single reply.

CM7!
Flash at your OWN RISK.
I will not be held responsible if you brick/mess up your device.
This is meant for the A9, not anything else.
This is an experimental build, I cannot even guarantee that it will boot.
==========================================================================
Download : http://www.mediafire.com/?f85rdpx0kvbtmvh
Code:
SHA1: dd40f0cef5b40d8a8b5b3966e29074889bad9b8e
MD5: c2a28a1d012f2b3a4a1f79ead24c8d66
I'll be damned if you even get to the standby screen. I don't have the time to test it right now and restore backups if it doesn't work.
If it doesn't work, the screen will probably go blank and you should reboot into recovery (or you may get a bootloop)
If you think it has got past boot, try and run logcat and dmesg and post back the logs so I can know what went wrong.
Using dmesg and logcat: http://www.flashmyandroid.com/forum...ogcat-and-dmesg-outputs-for-trouble-shooting-!
Before flashing:
Backup all sdcard contents.
Make nandroid backup via CWM, test restore it, copy to computer just in case.
-------------------------------------------------------------------------------------------------------------
Make sure you have a nandroid backup (and test it out! if you get MD5 mismatch like I did, you'll be spending a lot more time getting your phone restored) on your phone /sdcard as well as your computer.
A microSD card reader (in case the sdcard gets wiped and you have no means of transferring your nandroid backup)
-------------------------------------------------------------------------------------------------------------
Instructions:
Place zip file on /sdcard
Flash zip via CWM (If you don't already have it, this is the one: http://www.mediafire.com/?aen9w6uinz923hy)
Wipe /data, /cache and dalvik-cache from CWM.
Reboot
Used the stock kernel, device tree is over here: https://github.com/Siarc/a9
[I have also tried manually flashing a previous build's system image, it wouldn't work, restored nandroid, everything back to normal.]
Only testers who are comfortable flashing ROMs and have a computer with fastboot working should try it out, in case there is a need to flash the recovery partition.

Shark- said:
Flash at your OWN RISK.
I will not be held responsible if you brick/mess up your device.
This is meant for the A9, not anything else.
This is an experimental build, I cannot even guarantee that it will boot.
==========================================================================
Download : http://www.mediafire.com/?f85rdpx0kvbtmvh
Code:
SHA1: dd40f0cef5b40d8a8b5b3966e29074889bad9b8e
MD5: c2a28a1d012f2b3a4a1f79ead24c8d66
I'll be damned if you even get to the standby screen. I don't have the time to test it right now and restore backups if it doesn't work.
If it doesn't work, the screen will probably go blank and you should reboot into recovery (or you may get a bootloop)
If you think it has got past boot, try and run logcat and dmesg and post back the logs so I can know what went wrong.
Using dmesg and logcat: http://www.flashmyandroid.com/forum...ogcat-and-dmesg-outputs-for-trouble-shooting-!
Before flashing:
Backup all sdcard contents.
Make nandroid backup via CWM, test restore it, copy to computer just in case.
-------------------------------------------------------------------------------------------------------------
Make sure you have a nandroid backup (and test it out! if you get MD5 mismatch like I did, you'll be spending a lot more time getting your phone restored) on your phone /sdcard as well as your computer.
A microSD card reader (in case the sdcard gets wiped and you have no means of transferring your nandroid backup)
-------------------------------------------------------------------------------------------------------------
Instructions:
Place zip file on /sdcard
Flash zip via CWM (If you don't already have it, this is the one: http://www.mediafire.com/?aen9w6uinz923hy)
Wipe /data, /cache and dalvik-cache from CWM.
Reboot
Used the stock kernel, device tree is over here: https://github.com/Siarc/a9
[I have also tried manually flashing a previous build's system image, it wouldn't work, restored nandroid, everything back to normal.]
Only testers who are comfortable flashing ROMs and have a computer with fastboot working should try it out, in case there is a need to flash the recovery partition.
Click to expand...
Click to collapse
I will test it bro..
thnks for compiling.

Shark- said:
Flash at your OWN RISK.
I will not be held responsible if you brick/mess up your device.
This is meant for the A9, not anything else.
This is an experimental build, I cannot even guarantee that it will boot.
==========================================================================
Download : http://www.mediafire.com/?f85rdpx0kvbtmvh
Code:
SHA1: dd40f0cef5b40d8a8b5b3966e29074889bad9b8e
MD5: c2a28a1d012f2b3a4a1f79ead24c8d66
I'll be damned if you even get to the standby screen. I don't have the time to test it right now and restore backups if it doesn't work.
If it doesn't work, the screen will probably go blank and you should reboot into recovery (or you may get a bootloop)
If you think it has got past boot, try and run logcat and dmesg and post back the logs so I can know what went wrong.
Using dmesg and logcat: http://www.flashmyandroid.com/forum...ogcat-and-dmesg-outputs-for-trouble-shooting-!
Before flashing:
Backup all sdcard contents.
Make nandroid backup via CWM, test restore it, copy to computer just in case.
-------------------------------------------------------------------------------------------------------------
Make sure you have a nandroid backup (and test it out! if you get MD5 mismatch like I did, you'll be spending a lot more time getting your phone restored) on your phone /sdcard as well as your computer.
A microSD card reader (in case the sdcard gets wiped and you have no means of transferring your nandroid backup)
-------------------------------------------------------------------------------------------------------------
Instructions:
Place zip file on /sdcard
Flash zip via CWM (If you don't already have it, this is the one: http://www.mediafire.com/?aen9w6uinz923hy)
Wipe /data, /cache and dalvik-cache from CWM.
Reboot
Used the stock kernel, device tree is over here: https://github.com/Siarc/a9
[I have also tried manually flashing a previous build's system image, it wouldn't work, restored nandroid, everything back to normal.]
Only testers who are comfortable flashing ROMs and have a computer with fastboot working should try it out, in case there is a need to flash the recovery partition.
Click to expand...
Click to collapse
I did as u said..
i wiped data / chache/ delvik cache .. But not able to install..
i m writing the exact error...
" Installing update..
assert failed : getprop("ro.product.device")== "a9" || getprop("ro.build.product") =="a9" ||getprop("ro.product.board")== "a9"
E: Error in /sdcard/cm7-20120911-UNOFFICIAL-a9.zip
(status 7)
Installation aborted. "

vijetaverma said:
I did as u said..
i wiped data / chache/ delvik cache .. But not able to install..
i m writing the exact error...
" Installing update..
assert failed : getprop("ro.product.device")== "a9" || getprop("ro.build.product") =="a9" ||getprop("ro.product.board")== "a9"
E: Error in /sdcard/cm7-20120911-UNOFFICIAL-a9.zip
(status 7)
Installation aborted. "
Click to expand...
Click to collapse
In the /system directory, edit the build.prop file and add this line:
Code:
ro.build.product=a9
Make sure it persists after a reboot.

Great work Friend's
Shark- said:
In the /system directory, edit the build.prop file and add this line:
Code:
ro.build.product=a9
Make sure it persists after a reboot.
Click to expand...
Click to collapse
Bro please reply fast cant Waite now.I also want to install cm7

Shark- said:
In the /system directory, edit the build.prop file and add this line:
Code:
ro.build.product=a9
Make sure it persists after a reboot.
Click to expand...
Click to collapse
just woke up..
I m adding that line.. will Post result in a while
---------- Post added at 10:28 AM ---------- Previous post was at 10:00 AM ----------
Still not able to install..
Error
"
same as previous one..
(status 7)
Installation aborted
"

Any more info like the previous one? Ro.build anything?
Sent from my A9 using xda app-developers app

Shark- said:
Any more info like the previous one? Ro.build anything?
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
all same as before..nothing changed..

Can you post the complete log
Sent from my A9 using xda app-developers app

There is no systemui.apk in the build, so it's never gonna boot up
I think without kernel sources developing cm7 is impossible.
Anyway I really appreciate the effort you took in trying to compile cm7 for our device
Sent from my A9 using xda app-developers app

SystemUI can be copied in the makefiles , and I wouldn't say its impossible to compile, just very difficult.
Sent from my A9 using xda app-developers app

No phone.apk, conversations.apk camera.apk, systemui.And many permissions xml file are missing.You can't use stock apk instead of these, they need to be build specially for our device.
The reason why I said it is impossible is I have seen very good devs finding it very difficult to build cm7 for devices having kernel source released.our device don't even have kernel source available.Normal gingerbread kernel without any modification won't boot up cm7.
Sent from my A9 using xda app-developers app

Well thanks for the encouragement
Sent from my A9 using xda app-developers app

mahfoozceecy said:
There is no systemui.apk in the build, so it's never gonna boot up
I think without kernel sources developing cm7 is impossible.
Anyway I really appreciate the effort you took in trying to compile cm7 for our device
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
Shark- said:
SystemUI can be copied in the makefiles , and I wouldn't say its impossible to compile, just very difficult.
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
mahfoozceecy said:
No phone.apk, conversations.apk camera.apk, systemui.And many permissions xml file are missing.You can't use stock apk instead of these, they need to be build specially for our device.
The reason why I said it is impossible is I have seen very good devs finding it very difficult to build cm7 for devices having kernel source released.our device don't even have kernel source available.Normal gingerbread kernel without any modification won't boot up cm7.
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
Shark- said:
Well thanks for the encouragement
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
So guys is anyone working on CM7 for A9 ?

MiUi Rom released..
http://forum.xda-developers.com/showthread.php?p=41289727

Porting cyanogenmod 12.1 on fire hd8 2017

I'm experimenting with getting the cm 12.1 to work on my hd8 2017.
One of my college friend suggested to try replace part of the folders in the system partition with the one in the cm and today i've tryed and to my astonishment it reachd the cm 12.1 splash screen and from there i'm getting a very nice bootloop
I know this is probably the worst way of porting a rom ( seems to me so, im not an expert) but if some rom-porting expert can tell me what is wrong with the boot process even just for the sake of knowledge.
in the attachments a splash-screen image and a partial logcat (the logcat was capture when the tablet was "dirty" and still had FireOS data and cache)

I know @Rortiz2 was looking at doing the same thing.
Maybe you two can coordinate.

t0x1csh said:
i'm experimenting with getting the cm 12.1 to work on my hd8 2017.
One of my college friend suggested to try replace part of the folders in the system partition with the one in the cm and today i've tryed and to my astonishment it reachd the cm 12.1 splash screen and from there i'm getting a very nice bootloop
i know this is probably the worst way of porting a rom ( seems to me so, im not an expert) but if some rom-porting expert can tell me what is wrong with the boot process even just for the sake of knowledge.
In the attachments a splash-screen image and a partial logcat (the logcat was capture when the tablet was "dirty" and still had fireos data and cache)
Click to expand...
Click to collapse
oh my god!! What rom used as base!!??? What folders did you replaced? More info please! Also you need to wipe data and system before flash a ROM.
Send it to me please, I will take a look.

Rortiz2 said:
oh my god!! What rom used as base!!???
Send it to me please, I will take a look.
Click to expand...
Click to collapse
cm-12.1-20190616-UNOFFICIAL-i9105p from androidfilehost on top of 50.6.2.6 i dont have the image right now but i can make you one
my friend send me this https://forum.xda-developers.com/showthread.php?t=2545618 and i followed it step by step

t0x1cSH said:
cm-12.1-20190616-UNOFFICIAL-i9105p from androidfilehost on top of 50.6.2.6 i dont have the image right now but i can make you one
my friend send me this https://forum.xda-developers.com/showthread.php?t=2545618 and i followed it step by step
Click to expand...
Click to collapse
Dude you need to use a ROM from an mtk 64 bit device!
I suggest this: https://forum.xda-developers.com/elephone-p7000/development/rom-t3355842
Let me port it using that guide and I will send you a .zip for flash it using flashfire.

Rortiz2 said:
Dude you need to use a ROM from an mtk 64 bit device!
I suggest this: https://forum.xda-developers.com/elephone-p7000/development/rom-t3355842
Let me port it using that guide and I will send you a .zip for flash it using flashfire.
Click to expand...
Click to collapse
well what i changed is mostly java so i dont think the arch is that important plus mostly of the libraries on the fire hd8 are 32 bit

t0x1cSH said:
well what i changed is mostly java so i dont think the arch is that important plus mostly of the libraries on the fire hd8 are 32 bit
Click to expand...
Click to collapse
Libraries on hd8 2017 are 64 bit too (lib64 folder). And yes, it's very important. You can't port a ROM from an Snapdragon device to an MTK one lol.
I'm surprised that the bootanimation started.
Did you used flashfire for flash it?

Rortiz2 said:
Libraries on hd8 2017 are 64 bit too (lib64 folder). And yes, it's very important. You can't port a ROM from an Snapdragon device to an MTK one lol.
I'm surprised that the bootanimation started.
Did you used flashfire for flash it?
Click to expand...
Click to collapse
nope i've patched the system image from the ota
but excluding the libraries (that i didn't touch) i know that you can't port a rom if the apps are odex at least until you deodex all of them becouse the odex contains the compiled code specific to the processor, correct me if i'm wrong

t0x1cSH said:
nope i've patched the system image from the ota
Click to expand...
Click to collapse
And flashed it with "hacked fastboot" no?

Rortiz2 said:
And flashed it with "hacked fastboot" no?
Click to expand...
Click to collapse
yep

t0x1cSH said:
yep
Click to expand...
Click to collapse
So you mounted stock system.img, replaced that folders, unmounted it and flashed it tought fastboot? Very interesting. IDK why bootanimation started if you're using stock boot.img that doesn't starts the bootanimation service from init.rc.

Rortiz2 said:
So you mounted stock system.img, replaced that folders, unmounted it and flashed it tought fastboot? Very interesting. IDK why bootanimation started if you're using stock boot.img that doesn't starts the bootanimation service from init.rc.
Click to expand...
Click to collapse
should i try with the link you send me or is a waste of time? the process is quite laborious

t0x1cSH said:
should i try with the link you send me or is a waste of time? the process is quite laborious
Click to expand...
Click to collapse
You can try if you want. I'm porting it too for see if it works, the problem is that I will make a zip so you will need to use flashfire to flash it..
PS: your hacked fastboot allows to flash boot.img's that are not from amazon?

Rortiz2 said:
You can try if you want. I'm porting it too for see if it works, the problem is that I will make a zip so you will need to use flashfire to flash it..
PS: your hacked fastboot allows to flash boot.img's that are not from amazon?
Click to expand...
Click to collapse
no

t0x1cSH said:
no
Click to expand...
Click to collapse
Ok.

is this a little step forward? @Rortiz2

t0x1cSH said:
is this a little step forward? @Rortiz2
Click to expand...
Click to collapse
Yep all it's ok except one rror:
Code:
load_driver(/system/lib/egl/libGLES_mali.so): dlopen failed: cannot locate symbol "_ZN12DpBlitStream14setPQParameterERK9DpPqParam" referenced by "libgpu_aux.so"...
You need to create a shim for that and since is ported, you can't
What ROM used this time?

Rortiz2 said:
Yep all it's ok except one rror:
Code:
load_driver(/system/lib/egl/libGLES_mali.so): dlopen failed: cannot locate symbol "_ZN12DpBlitStream14setPQParameterERK9DpPqParam" referenced by "libgpu_aux.so"...
You need to create a shim for that and since is ported, you can't
What ROM used this time?
Click to expand...
Click to collapse
well last night i switched to the cynogenmod 12.1 port for the hd7 (i know 32bit) this time i copied also part of the 32bit libraries (when an import error on a library occurred i replaced the library with the hd7 one ) slowly advancing in the android boot before a bootloop

t0x1cSH said:
well last night i switched to the cynogenmod 12.1 port for the hd7 (i know 32bit) this time i copied also part of the 32bit libraries (when an import error on a library occurred i replaced the library with the hd7 one ) slowly advancing in the android boot before a bootloop
Click to expand...
Click to collapse
Glad to see that is working
Try replacing libgpu_aux.so
Regards!

Rortiz2 said:
Glad to see that is working
Try replacing libgpu_aux.so
Regards!
Click to expand...
Click to collapse
actually i did not replace libGLES_mali.so(still from hd8 rom) but i replaced libgpu_aux and i get the same error