Database Users

Help Will 5 MIUI Rom

Good afternoon
I come from the last verção ICS Cyanogen mod 5 / 12 but when I install Miui rom the phone is simply not boot or crashes when connecting my palace just after installation
Rom install Miui
-Wipe Data
-Wipe Cache
-Wipe Batery Stasta
. I have installed recovery boot menu because I have everything right Cyanogem working
After MIUI nothing works only Boot menu, Recovery,
Any ideas?

Try flash MIUI again, then wipe cache and factory/data again. Or you can try download MIUI update again or try older version.

Wipe dalvik cache also.
And double or triple wipe before and after flash.
If nothing works, going back to froyo is the best way to start.

ezaias said:
Good afternoon
I come from the last verção ICS Cyanogen mod 5 / 12 but when I install Miui rom the phone is simply not boot or crashes when connecting my palace just after installation
Rom install Miui
-Wipe Data
-Wipe Cache
-Wipe Batery Stasta
. I have installed recovery boot menu because I have everything right Cyanogem working
After MIUI nothing works only Boot menu, Recovery,
Any ideas?
Click to expand...
Click to collapse
which ics version you come from? or have you flashed the full euro sbf? anyway,make sure you have the right kernel(ch 2.2.2) for miui.

Endless7 said:
which ics version you come from? or have you flashed the full euro sbf? anyway,make sure you have the right kernel(ch 2.2.2) for miui.
Click to expand...
Click to collapse
Brazil Retail reinstalled 2.2, I installed Recovery, boot menu, all following the posting MIUI Zip installed correctly (installation successful)
2 Wipe Data
1Wipe Cache
The phone incident is just several minutes' MIUI "and restarted it fails to complete the boot
Any comment?
Ademiro all of xda

[Q] AOSP Paradise

intalled AOSP Paradise and gapps on my defy(green lense) and everything seems to be working great except:
1. everytime i turn my phone off when i turn it back on the Mokee logo comes up 1st and then it loads AOSP fine but i have to re-enter all my google info
2. it doesn't save any of my settings.
3. it wont let me download any apps...they start downloading but just sit there downloading and if they do finish, it says cant install, not enough memory but i reformatted the sd partition in recovery before installing AOSP because i knew it didnt have enough memory to even install it.
4. Why does that Mokee screen come on still?
i had the Mokee ROM before but shouldnt that have gone away when i wiped data and cache?
Did i do something wrong on install? i did wipe data/factory reset, wipe cache, flashed ROM, flashed gapps, wipe dalvik cache and rebooted twice. it loads fine and everything seems to be working but i dont like having to start from scratch everytime i turn my phone on.
Help pls...frustrating

Try clean install as said in this thread.
forum.xda-developers.com/showthread.php?p=32093770#post32093770
Make sure you flash new rom before rebooting

Flash SBF and then Flash new ROM

[Q]AOSP Paradise
Euro_Rules said:
Flash SBF and then Flash new ROM
Click to expand...
Click to collapse
ok that fixed boot screen but not the redoing of google, downloading apps or saving settings...any other suggestions?:fingers-crossed:
i figured it out! i was missing the firmware from when i bricked it...so, i found a firmware file, flashed it and now it works like a charm!! yay

Moved to Q&A. Please ask all questions there.

[Q] Slimrom 4.3 freezes on reboot (mako)

Hey guys,
I'm not a total scrub at flashing roms and there's still a bunch of things that I don't understand. I'm pretty positive that I flashed Slimrom correctly but here's the situation.
Started on 4.2.2 Slimrom
Reboot to TWRP recovery
Format factory reset/format data, system, cache, dalvik cache
Flash Slimrom 4.3 stable build 1
Successfully reboots into 4.3
Okay now here's the weird part.
The first time I rebooted back into recovery to flash gapps. After I flashed gapps and tried to reboot into the rom, the phone freezes at the screen with "google" and the unlock sign on the bottom. The only way I can get it to boot into the rom again is if I reformat/reset EVERYTHING (including format data) and reflash 4.3. After a few tries of messing around with not wiping dalvik/cache and stuff I realized that even if I don't flash gapps it still freezes on the google screen. So here's my main problem
After flashing 4.3 slimrom, the phone boots into the rom only once. If I try restarting my phone it freezes on the "google" screen.
Anyone know what I'm doing wrong?
Just to clarify it's a LG Google Nexus 4 mako.
Sorry if I'm being redundant. I just want to give as much detail as possible. If you need anymore info let me know!
Thanks

ms3195 said:
Hey guys,
I'm not a total scrub at flashing roms and there's still a bunch of things that I don't understand. I'm pretty positive that I flashed Slimrom correctly but here's the situation.
Started on 4.2.2 Slimrom
Reboot to TWRP recovery
Format factory reset/format data, system, cache, dalvik cache
Flash Slimrom 4.3 stable build 1
Successfully reboots into 4.3
Okay now here's the weird part.
The first time I rebooted back into recovery to flash gapps. After I flashed gapps and tried to reboot into the rom, the phone freezes at the screen with "google" and the unlock sign on the bottom. The only way I can get it to boot into the rom again is if I reformat/reset EVERYTHING (including format data) and reflash 4.3. After a few tries of messing around with not wiping dalvik/cache and stuff I realized that even if I don't flash gapps it still freezes on the google screen. So here's my main problem
After flashing 4.3 slimrom, the phone boots into the rom only once. If I try restarting my phone it freezes on the "google" screen.
Anyone know what I'm doing wrong?
Just to clarify it's a LG Google Nexus 4 mako.
Sorry if I'm being redundant. I just want to give as much detail as possible. If you need anymore info let me know!
Thanks
Click to expand...
Click to collapse
Are you flashing the right Gapps package? Be sure you are flashing the latest 4.3 one.

abaaaabbbb63 said:
Are you flashing the right Gapps package? Be sure you are flashing the latest 4.3 one.
Click to expand...
Click to collapse
Yep I'm positive. I redownloaded both the 4.3 rom and gapps package multiple times just to make sure. Also it doesn't reboot even if I don't flash gapps. Doesn't boot at all if I flash both the rom then gapps at the same time.

bump

then, wipe data/factory reser and flash the stock rom. the rom might be the problem

davinnwilliam said:
then, wipe data/factory reser and flash the stock rom. the rom might be the problem
Click to expand...
Click to collapse
It works for everyone else though. It's Slimrom 4.3 stable build 1.

Rom isn't the problem.Slim rom beta 1(4.3) is super stable. Use any version of twrp recovery other than 2.6.1.0 and wipe system+data,flash slim rom,flash slim gapps,reboot.
Note: if you flashed franco kernel then this may be the issue for your bootloop also you may want to upgrade your bootloader and radio to 4.3 versions(bootloader more important)

Bootloop, again

Was on cloudy's latest gpro2 rom with dorimatrix 4.8.1, updated to 4.9 and wiped cache and dalvic cache and upon first boot everything I would click force closed after a minute or so so I attempted rebooting. It would then go into a bootloop. I adb rebooted into recovery, wiped the caches, and flashed 4.8.1. It now did the same thing as it did before, followed by a bootloop when I rebooted it. Decided to try flashing to a different rom, so I did a complete backup and sent over the latest CM11 nightly. Wiped all and flashed, and now I'm bootlooping at the CM screen with no recovery access.
I remembered when I was already bootlooping that I needed to flash the 4.2.2 partitions to use an AOSP roms. A little too late huh. Now I'm stuck at the CM bootanimation and no ADB. Are my only options to use mobile odin and start over from or can you guys come up with something else?

mejorguille said:
Was on cloudy's latest gpro2 rom with dorimatrix 4.8.1, updated to 4.9 and wiped cache and dalvic cache and upon first boot everything I would click force closed after a minute or so so I attempted rebooting. It would then go into a bootloop. I adb rebooted into recovery, wiped the caches, and flashed 4.8.1. It now did the same thing as it did before, followed by a bootloop when I rebooted it. Decided to try flashing to a different rom, so I did a complete backup and sent over the latest CM11 nightly. Wiped all and flashed, and now I'm bootlooping at the CM screen with no recovery access.
I remembered when I was already bootlooping that I needed to flash the 4.2.2 partitions to use an AOSP roms. A little too late huh. Now I'm stuck at the CM bootanimation and no ADB. Are my only options to use mobile odin and start over from or can you guys come up with something else?
Click to expand...
Click to collapse
Fixed it... realized I still had recovery active, booted into it with the button combo, wiped, installed cloudy pro, all is good.

[Q] [CM12] GApps Crash On Startup

Hello,
I upgraded my Verizon Galaxy S4 from CM11 to CM12 last night, using the nightly build from 1/7/2015. The upgrade went smoothly, except for gapps. I have not been able to get them to successfully run on Lollipop. I have tried the following builds of gapps:
PA GAPPS
2014-11-09
2014-12-20
I use the following installation process each time:
Boot into CWM 6.0.3.2
wipe data/factory reset
wipe cache partition
mounts and storage > format /system
wipe dalvik cache
install CM.zip
install gapps.zip
When I reboot the phone, it gets into the lock screen as expected, but when I swipe it to unlock, I instantly get a stream of errors ("Setup wizard has stopped", "Google+ has stopped", etc). The exact errors depend on which gapps version I install, since they come with (slightly) different apps in the packages.
Has anyone had success with the Lollipop gapps packages and CyanogenMod?

rowdypixel said:
Hello,
I upgraded my Verizon Galaxy S4 from CM11 to CM12 last night, using the nightly build from 1/7/2015. The upgrade went smoothly, except for gapps. I have not been able to get them to successfully run on Lollipop. I have tried the following builds of gapps:
PA GAPPS
2014-11-09
2014-12-20
I use the following installation process each time:
Boot into CWM 6.0.3.2
wipe data/factory reset
wipe cache partition
mounts and storage > format /system
wipe dalvik cache
install CM.zip
install gapps.zip
When I reboot the phone, it gets into the lock screen as expected, but when I swipe it to unlock, I instantly get a stream of errors ("Setup wizard has stopped", "Google+ has stopped", etc). The exact errors depend on which gapps version I install, since they come with (slightly) different apps in the packages.
Has anyone had success with the Lollipop gapps packages and CyanogenMod?
Click to expand...
Click to collapse
https://s.basketbuild.com/gapps
try that gapps which works for me very fine.
Factory reset
install Cm and then gapps. it should work all fine actually. :laugh: goodluck. reply here for further problems.

xDroidZz said:
try that gapps which works for me very fine.
Factory reset
install Cm and then gapps. it should work all fine actually. :laugh: goodluck. reply here for further problems.
Click to expand...
Click to collapse
I tried that one again - no dice. com.google.process.gapps crashes on startup, followed by a long list of other Google apps included in the package.

Same problem.
---------- Post added at 03:12 PM ---------- Previous post was at 03:01 PM ----------
Nexus 7 2013 WiFi

Any fix for this? I've been struggling with it for a whole day now.

I have not found a fix. I reverted back to KitKat since I needed to use my phone during the week.

Bump

I finally managed to fix the problem. All the clean flashes did nothing, and I made sure they were squeaky clean, so I decided to start from scratch. I ODIN'd back to stock, installed TWRP instead of Clockworkmod, and reinstalled the rom and gapps package. I booted into the setup wizard and all is right in the world. Thanks for all who helped me!

Do you know what version of CWM you were running? I might try updating it over the weekend and see if that works as an alternate solution.

Try this. This worked for me.
http://fitsnugly.euroskank.com/?rom=banks&device=gapps

Gapps crashes
rowdypixel said:
I tried that one again - no dice. com.google.process.gapps crashes on startup, followed by a long list of other Google apps included in the package.
Click to expand...
Click to collapse
Before adding gapps after flashing cm-12 wipe dalvik and cache, flash ktoonz lollipop kernel then flash gapps for lollipop. This worked for me.

anonymousguy44 said:
I finally managed to fix the problem. All the clean flashes did nothing, and I made sure they were squeaky clean, so I decided to start from scratch. I ODIN'd back to stock, installed TWRP instead of Clockworkmod, and reinstalled the rom and gapps package. I booted into the setup wizard and all is right in the world. Thanks for all who helped me!
Click to expand...
Click to collapse
Hey I'm having the same problem, can you describe how in Odin you got back to stock? You flashed stock and lost your custom recovery? That's weird, I figured a custom recovery was like a bios