Develop Bugs

[Q] Installing MIUI on Defy; stuck on the Motorola logo

Hi,
I am trying to flash MIUI on my Defy which is currently running the official 2.2.2 released here in India.
What i have done so far (and repeated the entire process several times):
-Rooted the phone using SuperOneClick
-Installed ROM Manager
-Installed Clockworkmod Recovery 2.5.1.8 for Defy
-Downloaded 'miuiandroid_Defy-2.3.4a' the then latest version of MIUI from their site and the corresponding language pack
-Installed and booted into custom recovery
-Took a nandroid backup of the current ROM
-Wiped data, cache and dalvik cache
-Selected the .zip ROM file from the sdcard and installed it
-After the installation was done, i rebooted the system
This is where the problem started. I had read that the phone might take forever for its first boot. But in my case, the phone would stay stuck on the M logo till i removed the battery. On restart, the same thing repeated.
I found the SBF for the retail version of 2.2 i found on the forums and used RSD Lite 4.9 to flash it to the phone and then restored the nandroid backup i had made previously to get back to where i started from. And i repeated the entire process 4 times using 3 different versions of MIUI.
Am i missing something here? What can i do to get the phone to move past that M logo? I have been trying to find a solution to this issue since over a week now. None of the forums seem to have a solution to a similar problem. Any help would be appreciated.

Answer to all Your problems
It's a common mistake. You must have forgotten about wipe all (cache and personal data) before installing zip package containing MIUI.

hex24 said:
It's a common mistake. You must have forgotten about wipe all (cache and personal data) before installing zip package containing MIUI.
Click to expand...
Click to collapse
I did that. Everytime i tried to install the ROM i did all the three.

Install 2nd inti not CMW and than install MIUI...
Sent from my MB526 using XDA App

ifu said:
Install 2nd inti not CMW and than install MIUI...
Sent from my MB526 using XDA App
Click to expand...
Click to collapse
It worked! It worked!
Thanks a lot!

[Q] MIUI for V One Help! (What in hells name am I doing wrong?!)

Hey there;
Firstly, thanks for your great efforts on the ports of your roms and consistent, useful forum help.
I appreciate that you probably get a load of these threads but I could really use some help with the installation of the ROM, as I've had a load of problems trying to install it.
I am attempting to install the MIUI rom (http://forum.xda-developers.com/showthread.php?t=1797515), and I am coming from the original software that comes with the device.
I have an unrooted One V, coming from the base OS and kernel. Currently, I can't get past the Jellybean Android screen (getting stuck on starting apps), and usually I can't even get past the MIUI screen at all. Here are the steps I've taken;
- I downloaded this kernel: boot-TK-USB-201302150054 from this thread: http://forum.xda-developers.com/show....php?t=1765687 and flashed it in fastboot, twice.
- Then launch into recovery, follow the instructions on your thread (format all apart from SD), and go ahead and install the .zip.
- Clear Delvik, clear Battery and Fix permissions, then proceed to reboot in an attempt to get in. At this point it hangs on MIUI screen for up to 5 minutes.
- I then try re-flashing the kernel in fastboot again. Still no help.
- I then try and reinstall the .zip from the SD card, and still no improvement.
I imagine I'm doing something very wrong, but I can't work out what it is and it's driving me crazy.
Can you help?!
Thanks in advance, Reasoner.

you are installing an older rom version which has no support..and is old

paarthdesai said:
you are installing an older rom version which has no support..and is old
Click to expand...
Click to collapse
Any chance you good point me in the right direction for an newer version?
Also, am I doing all the steps right?

paarthdesai said:
you are installing an older rom version which has no support..and is old
Click to expand...
Click to collapse
Okay, I have now attempted to install YOUR version of MIUI, and I'm still not having any luck.
I have;
- Flashed the boot.img using the one you suggest on your thread (twice)
- Booted into Recovery, cleared all caches excluding SD
- installed from .zip in CWM Recovery
- Cleared Delvik
On reboot I still get stuck on the MIUI screen.

Reasoner said:
Okay, I have now attempted to install YOUR version of MIUI, and I'm still not having any luck.
I have;
- Flashed the boot.img using the one you suggest on your thread (twice)
- Booted into Recovery, cleared all caches excluding SD
- installed from .zip in CWM Recovery
- Cleared Delvik
On reboot I still get stuck on the MIUI screen.
Click to expand...
Click to collapse
Ignore this, tried again and got through! Thanks a bunch!

[Q] Android RevolutionHD 18 AromaInstaller Crash

Hi,
i have some problems with the Android RevolutionHD Rom 18, but im not allowed yet to answer there.
Everytime i try to install the rom via cwm the aromainstaller crashes at the point, where i have to tick the terms of use.
I already tried:
reroot with superSU and not superuser
installed cwm
installed the stock kernel and flashed everything new
wiped multiple times
started from internal and external sd
Can someone please help me? There must be a simple solution.

mandastar said:
Hi,
i have some problems with the Android RevolutionHD Rom 18, but im not allowed yet to answer there.
Everytime i try to install the rom via cwm the aromainstaller crashes at the point, where i have to tick the terms of use.
I already tried:
reroot with superSU and not superuser
installed cwm
installed the stock kernel and flashed everything new
wiped multiple times
started from internal and external sd
Can someone please help me? There must be a simple solution.
Click to expand...
Click to collapse
Use TWRP instead of CWM. Problem solved

[Solved]Nexus won't boot after ROM and other things

Hello guys, I've searched a little and didn't find any posts that could help me specifically for the Galaxy Nexus.
I've flashed my phone a long time ago and have been using Paranoid Android for probably over a year.
The problem is, my cellphone was really really slow. So I decided to try a new ROM and re-flash it. And So I did.
I've tried flashing this Full_Auto R11 kernel then the CyanogenMod 12 and finally GAPPS.
I was getting error status 6 on Clockwork mod on gapps, but eventually got around it. But it didn't install play store, I've tried manually adding but it didn't work.
So I went for another 5.0 ROM (I'm really interested in getting android 5.0). Wiped all the data, all the cache, installed everything and rebooted.
Bam! Infinite booting screen.
No, I didn't create a nandroid backup because I'm really dumb.
So, I need your help. What I want to do is to get my phone working again with a 5.0 ROM (if possible).
I can boot into ClockWork Recovery just fine, if that helps.
Thank you for the attention.

I would recommend to install latest full factory package from Google.
Then you will start with everything stock, so flash latest TWRP recovery via fastboot (CWM is no longer supported, so error 6 when installing new Lollipop Google Apps appears).
Then in TWRP, do a factory reset, wipe /cache and /system partitions.
Then you can install your Lollipop ROM (over ADB or by pushing ROM package to emulated sdcard).
After this, install latest Full_Auto kernel.
At the end, install Pico Google Apps.
You must install the Pico version, because our /system parition is too small to handle Lollipop with all Google Apps included.
This should work for you, and you will have fully working Lollipop on your Galaxy Nexus
P.S: If you intall the AOSP Lollipop ROM by @freshgiammi and you miss root access, install latest SuperSU flashable zip.

Thank you!
Thank you man!
I've ran into some troubles but managed to do everythings correctly =)
This post can be locked up now.
Thanks again for the reply, LamarrCZ!!

Problems after installing CM12.1 nightlies

Hi everyone,
Today I installed the new CM12 nightlies, after rebooting my HTC one m8 it showed me a popup message that google play services stopped working. I also couldnt launch particular apps. So after looking for a solution I tried reinstalling Gapps hoping this would solve the problem.
I downloaded the minimal Gapps ZIP file and flashed it using TWRP recovery, after I wiped the cache and dalvik cache. Once rebooted I started to get the anoying pop up notifications '' Gmail stopped working'' and ''youtube stopped working''. These two messages won't go away and makes my phone unusable. I think the reason why these messages keep popping up is because i flashed the minimal version of Gapps so I downloaded the normal version of Gapps on my computer since my phone isnt accesable because of the pop-up notifications that won't go away. What I did next was plug in my phone to my computer and moved Gapps L-3-14-15.zip to my SD card and installed it again. I also wiped the cache and dalvik cache. after I did a reboot and everything seemed fine for the first 20 seconds... It didnt last long. Im still having the same problem as before Gmail and youtube has stopped working. Do any of you know how to fix this without doing a system recovery?
Thanks in advance
HTC one m8
Cyanagonmod 12.1
Rooted
TWRP
S-on (don't know if this is relevant)

Copy important files to computer. Factory reset. Set it up as new device.

ikeny said:
Copy important files to computer. Factory reset. Set it up as new device.
Click to expand...
Click to collapse
To me it sounds like you installed a gapps 5.0 package not a 5.1 package. With the CM Nightly you need to make sure you're using an updated gapps package designed for android 5.1+.
I always use a minimal gapps package but usually CM has a link available on their page. Double check that you're installing a gapps 5.1 package. I am currently running the 5.1 nightlies and they're great thus far... 4/20 and 4/19 are both confirmable as working on my end. Good luck.
To correct Wipe /data /system /cache and dalvik reinstall the nightly and flash a 5.1 gapps package.

jcole20 said:
To me it sounds like you installed a gapps 5.0 package not a 5.1 package. With the CM Nightly you need to make sure you're using an updated gapps package designed for android 5.1+.
I always use a minimal gapps package but usually CM has a link available on their page. Double check that you're installing a gapps 5.1 package. I am currently running the 5.1 nightlies and they're great thus far... 4/20 and 4/19 are both confirmable as working on my end. Good luck.
To correct Wipe /data /system /cache and dalvik reinstall the nightly and flash a 5.1 gapps package.
Click to expand...
Click to collapse
I guess the minimal Gapps package that I first installed wasnt for 5.1
In order to get rid of the pop up notifications I started my phone in safe mode. This worked and I saw there was a new update for cm12.1 after the update finished and I booted up my phone the pop up notification werent there anymore but google play services was also uninstalled. What I did next was installing the newest google play services pack. After it was done I installed the 5.1 Gapps version on my phone and now everything seems working fine again. I did get some notifications that an app such as chrome stopped working but a simple reinstal of the app fixed the problem. Somehow the apps that I moved to my external SD card arent here anymore but im glad I didnt have to do a factory reset.
Thanks for your help

jcole20 said:
To me it sounds like you installed a gapps 5.0 package not a 5.1 package. With the CM Nightly you need to make sure you're using an updated gapps package designed for android 5.1+.
I always use a minimal gapps package but usually CM has a link available on their page. Double check that you're installing a gapps 5.1 package. I am currently running the 5.1 nightlies and they're great thus far... 4/20 and 4/19 are both confirmable as working on my end. Good luck.
To correct Wipe /data /system /cache and dalvik reinstall the nightly and flash a 5.1 gapps package.
Click to expand...
Click to collapse
every time i update my cm12 nightlies it has its own recovery (cyanogen recovery) but my zip files are not working with that recovery. (ex. cmzip.gapps, and kernels). for my device it works on PhilZ touch recovery. so the tendency is i have to flash fastboot boot.img(philz touch)again and again.
using Thunderzap kernel 4.15 im stock on bootloop.
running cm12.1 nightlies (4/20/15)
also gapps not compatible.

decoction said:
every time i update my cm12 nightlies it has its own recovery (cyanogen recovery) but my zip files are not working with that recovery. (ex. cmzip.gapps, and kernels). for my device it works on PhilZ touch recovery. so the tendency is i have to flash fastboot boot.img(philz touch)again and again.
using Thunderzap kernel 4.15 im stock on bootloop.
running cm12.1 nightlies (4/20/15)
also gapps not compatible.
Click to expand...
Click to collapse
I use twrp and I've not had any issues with a cm recovery replacing twrp. On the 420 nightly I don't even see a recovery.img in the cm zip so I'm assuming you're updating via cm itself. I think there's a setting in there to choose to update cm recovery or not.
To flash Phillz recovery you're syntax would be "fastboot flash recovery recoveryimgname.img" the boot.img is your kernel. I'm not sure how many aosp 5.1 kernels the m8 has but I've not really been able to find any so I just use the cm one.
To correct your issues I would flash twrp 2.8.6 via fastboot flash recovery. Wipe everything from recovery (cache data dalvik system) and reinstall. If it was me I'd update cm via zip from now on if it was causing me these issues. Good luck
HTC One (M8) ViperOne + Hypernova

Everything seemed working fine again until 30 min. ago...
I got the notification chrome has stopped working. (Haven't had this message all the morning and chrome worked just fine.)
I restarted my phone and the first thing I noticed was that some of my apps have disapeared from my home screen, they are still in the app tray tho. Also my keyboard input mode has been set back to AOSP while normaly I use Swiftkey keyboard as my standard input. Chrome was still pushing me not working notification so I reinstalled chrome and now it works fine again. Not sure for how many time...
Its kinda anoying but maybe tonights nightlies will solve the problem somehow. If not, do you have any sugestions how to fix this?

jcole20 said:
I use twrp and I've not had any issues with a cm recovery replacing twrp. On the 420 nightly I don't even see a recovery.img in the cm zip so I'm assuming you're updating via cm itself. I think there's a setting in there to choose to update cm recovery or not.
To flash Phillz recovery you're syntax would be "fastboot flash recovery recoveryimgname.img" the boot.img is your kernel. I'm not sure how many aosp 5.1 kernels the m8 has but I've not really been able to find any so I just use the cm one.
To correct your issues I would flash twrp 2.8.6 via fastboot flash recovery. Wipe everything from recovery (cache data dalvik system) and reinstall. If it was me I'd update cm via zip from now on if it was causing me these issues. Good luck
HTC One (M8) ViperOne + Hypernova
Click to expand...
Click to collapse
Thank you for that info. it really helps. by the way i got problems when i updated it to the cm12 4/21/15 update. got this message "trebuchet has stop working" so i decided to use cm resurrection remix.

decoction said:
Thank you for that info. it really helps. by the way i got problems when i updated it to the cm12 4/21/15 update. got this message "trebuchet has stop working" so i decided to use cm resurrection remix.
Click to expand...
Click to collapse
Yeah I mean nightlys merge with code that it's being worked on and may break or fix certain things. Nightly builds may be perfect or they may not even boot. You kind of have to just flash them and see. Cm is very generic coding and depending on your carrier may not have the non open source vendor blobs necessary to make, say, your speakers work properly. It really depends. I don't believe Verizon had released their kernel source for lollipop so sometimes downgrading firmware to known source (ie 4.4.4) may help alleviate connectivity issues with Wi-Fi and things of that sort. Team UBs build and lollipop dream 5.0.2 have been my go tos as of late. The lollipop dream build is the smoothest running cm build I've ever used even on nexus devices. Very well made.
HTC One (M8) ViperOne + Hypernova