I GET THE SAME THING! thank you for this LOL
this is what i do:
Reboot into CWM, Wipe data/cache/dalvik
Go into advanced, report error and show log.
reboot recovery Flash base.
At this point if you get the boot loop, 3finger back into CWM (sometimes it takes me 2 times, maybe because my finger slips, but yeah)
in CWM go to advanced again, report error and show log and DO NOT reboot recovery, Flash the BASE again
this time it should boot. Now reboot into recovery, report error/show log and reboot recovery.
flash the options chooser. upon reboot it might take you back into CWM, just reboot system.
I noticed on the first flash of the base which causes the bootloop after the installation it shows that it has an error setting some permissions which is why it might need a second flash.
This process might be lengthy and idk what the hell it does. but thats how i got it to work.
I hope Th3Bill sees this and has some input
Ill post a log of the first flash that causes the bootloop later on.
EDIT: and Th3Bill is currently working on a version with a different CM base because the newest one might not be compatible with MIUI which is causing google account, SMS and Browser FC's. Thanks Bill!
EDIT2: after looking over my post, this process is pretty much just after the first flash it boot loops, 3 finger and flash again without rebooting recovery. LOL over explaining
)
Nope...I don't port theirs....my AOKP is ported from my Photon one (like all my Infuse builds). I actually have 2.0 done...they're still on 1.0 (I also had 1.0 done before their release
Reversion build of 2.9.14 is UP on Jokersax.com. It's based on the older scott.hart.bi CM10 build, so it should be more compatible with MIUI, which is still a bit behind on Android version
AOKP reversion will come later tonight...
!
I think everyone is going to be REALLY happy with me. I am going to be able to eliminate the need for report error, show log (unless you have a failed installation of a previous build). Reason we had needed to do report error show log was to remove the prop choices that you had previously made, as they could affect how your system installed. I am inputting scripts into all my aroma zips from now on that deletes those prop choices at the end of installation
KNOWN ISSUES:
The graphics related issues are due to not having proper drivers to use for this. Don't ask for an ETA on a fix. Moto won't be giving us the drivers, so there is no fix
- Videocamera : Use VideoCam Illusion
Slight Lag possible on screen transitions
USB tether
If you need to report a NEW bug, report it once, and the next TWO people VERIFY it. I don't need everyone reporting same bug 20 times. I you can, provide me the following information:
- Version you're using
- What type of fwipe you did and what ROM you came from
- Have you restored any data from something like Titanium Backup
- What app is misbehaving and what you were doing when it started
- Logcats<--THIS IS PREFERRED.
If you don't know how to logcat, go HERE and learn. This really nice guy took the time to write out a good how to
When you have a LOGCAT and would like to post it, please go to pastebin and post it in there, then LINK that location in this thread...I don't want to see them posted directly in here.
- MIUI.us Team-for US translation and
- MIUIAndrouid Team-for GB translation
- scott.hart.bti=For the CM10 base I use and for helping me with source building
- Jokersax11-for being my initial inspiration on Photon, being a cool guy, and helping me along in my early days
- Amarullz=for creating the Aroma Installer
- Spleef-for collaborating on those first builds that got me into Android
- All my testers and users
- Anyone else I may have forgotten
