I installed cm12.1 rom for my samsung galaxy note 8 gt-n5110 and after i turned it on this was what happened. It constantly showed text boxes like "unfortunately, google app has stopped" and after i closed it another one showed up and now i cant control it anymore! I cant even finish the setup! What can i do?
Im new to these firmware stuff btw.
sunglassesman said:
I installed cm12.1 rom for my samsung galaxy note 8 gt-n5110 and after i turned it on this was what happened. It constantly showed text boxes like "unfortunately, google app has stopped" and after i closed it another one showed up and now i cant control it anymore! I cant even finish the setup! What can i do?
Im new to these firmware stuff btw.
Click to expand...
Click to collapse
Try a smaller Gapps package than the one that you flashed with the ROM. The package you used is probably too large to fit in the system partition along with the ROM.
Or, you didn't factory reset, wipe cache and wipe dalvik cache when you flashed the ROM. Failing to do those wipes will cause bugs due to the new system conflicting with the saved system data/settings from the previous system. In other words, data left over from the old ROM is causing problems with the new ROM.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Try a smaller Gapps package than the one that you flashed with the ROM. The package you used is probably too large to fit in the system partition along with the ROM.
Or, you didn't factory reset, wipe cache and wipe dalvik cache when you flashed the ROM. Failing to do those wipes will cause bugs due to the new system conflicting with the saved system data/settings from the previous system. In other words, data left over from the old ROM is causing problems with the new ROM.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Hey thanks for replying but it seems like i cant even finish the setup. Therefore i cant load any files into my device. Any suggestions?
sunglassesman said:
Hey thanks for replying but it seems like i cant even finish the setup. Therefore i cant load any files into my device. Any suggestions?
Click to expand...
Click to collapse
Boot back into recovery, then factory reset, wipe cache and wipe dalvik cache, then reboot.
If that doesn't work, try booting back into recovery then flash the ROM then the Gapps then factory reset, wipe cache and wipe dalvik cache then reboot.
If that doesn't work, try booting back into recovery, then select the "Wipe" option, then choose the "advanced wipes" option, then choose the system partition, then swipe the slider at the bottom to run the wipe, then try flashing just the ROM but don't flash the Gapps, factory reset, wipe cache and wipe dalvik cache then reboot. After you get the device booted, you can delete the Gapps file then download a smaller package and put it in your phone's internal storage then boot back into recovery and select the "Install" option, at this point, you already have the ROM installed so no need to flash it again, but you do need to flash the new Gapps file, then factory reset, wipe cache and wipe dalvik cache.
Do you see how important it is to factory reset, wipe cache and wipe dalvik cache every time you flash? It is a vital step.
Sent from my SM-S767VL using Tapatalk
Hey thanks for all these but my device is using cwm right now so can you pls rewrite the instructions for me?
Also i cant finish the setup with all these popups so theres no way i can load files into it.
And yeah i guess i didnt wipe data or caches away after i finished flashing the files.
Thank you so much.
Related
I am new to android and yesterday I accidentally clicked the red download button when I held the power button down. Then a black screen with yellow text came up and said "don't power off the target!!" I left the phone on for about 30 minutes, but the battery died. Now when I power up the device I get the message com.android.phone has stopped working. I also tried a factory reset but it didn't fix anything. The device is rooted, I checked using the root checker app (i bought the phone from someone). How can I fix this? Any help is appreciated, Thanks.
Try pulling the battery for 10 minutes or so. Do you know what ROM you are running? Only other thing I can think to try is trying to boot into CWM and wiping cache and dalvik. The usually fixes a lot of my issues.
Sent from my SGH-I997 using xda app-developers app
After wiping Dalvik/cache, go into Advanced, and select Fix Permissions, just to cover all of the simple bases. If none of that works, you may have to Heimdall/Odin back to stock and start all over again.
I got into CWM, but there is no option for advanced. There are 4 options: reboot system now, apply update from SD card, wipe data/factory reset, wipe cache partition. There are no other options. Maybe I have an older version of CWM, on the top it says Android system recovery <3e>
Is the wipe cache partition what i have to click to wipe cache. Thanks for the help.
neogamma said:
I got into CWM, but there is no option for advanced. There are 4 options: reboot system now, apply update from SD card, wipe data/factory reset, wipe cache partition. There are no other options. Maybe I have an older version of CWM, on the top it says Android system recovery <3e>
Is the wipe cache partition what i have to click to wipe cache. Thanks for the help.
Click to expand...
Click to collapse
Yes...wipe cache partition to wipe cache.
And it does appear like you have the old 3e Modded Recovery. I forget the version numbers but the CWM recoveries: commonly referred to as green, red and blue, will give you other options including Advanced as mentioned above
Sent from a de-FUNKt Infuse
If you plan on doing any serious flashing, I'd think you'd want to upgrade to Red CWM. Here's a thread that tells you how.
I'd recommend Method 1:
http://forum.xda-developers.com/showthread.php?t=1107881
Samsung Galaxy S2 i727 Skyrocket.
I recently updated to a 4.3 rom.
It booted up and I just got a message "Unfortuanately, Nfc Service has stopped. Blame Tyler."
I couldn't get the message to go away and the only thing I could do was a hard reboot.
Still same issue.
Rebooted into Recovery mode.
Factory Reset, wipe cache partition, format /system, wipe dalvich cache
Restored an older rom.
It booted up with no issues. But when I rebooted, I just get the Samsung logo and then the screen goes black.
I even tried Factory Reset, wipe cache partition, format /system, wipe dalvich cache and installed a new rom from scratch.
Same problem.
I have no idea what to try next or why this is happening.
Any help or comments are welcome.
Thanks
benraines said:
Samsung Galaxy S2 i727 Skyrocket.
I recently updated to a 4.3 rom.
It booted up and I just got a message "Unfortuanately, Nfc Service has stopped. Blame Tyler."
I couldn't get the message to go away and the only thing I could do was a hard reboot.
Still same issue.
Rebooted into Recovery mode.
Factory Reset, wipe cache partition, format /system, wipe dalvich cache
Restored an older rom.
It booted up with no issues. But when I rebooted, I just get the Samsung logo and then the screen goes black.
I even tried Factory Reset, wipe cache partition, format /system, wipe dalvich cache and installed a new rom from scratch.
Same problem.
I have no idea what to try next or why this is happening.
Any help or comments are welcome.
Thanks
Click to expand...
Click to collapse
What recovery are you using?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Clock Work Method CWM...
I've done several ROM updates in the past with no problems...
benraines said:
Clock Work Method CWM...
I've done several ROM updates in the past with no problems...
Click to expand...
Click to collapse
What version of cwm? Most likely you need to update it. And what 4.3 rom?
Thanks.
I had a an older version of CWM and just upgraded to 6043..
Its now working with reboots...
I didn't realize CWM had that type of effect..
jd1639 said:
What version of cwm? Most likely you need to update it. And what 4.3 rom?
Click to expand...
Click to collapse
When I knew CyanogenMod 11s had been ported to the nexus 5, I set off to get it on my device. I had stock android 4.4.4 running, had rooted my phone, and had cwmr.
I got into recovery mode, wiped data, wiped cache and flashed. It din't work. I wiped dalvik cache and tried again, but still didn't work.
Now I'm stuck on the google logo screen.
What can I do?
alejo7797 said:
When I knew CyanogenMod 11s had been ported to the nexus 5, I set off to get it on my device. I had stock android 4.4.4 running, had rooted my phone, and had cwmr.
I got into recovery mode, wiped data, wiped cache and flashed. It din't work. I wiped dalvik cache and tried again, but still didn't work.
Now I'm stuck on the google logo screen.
What can I do?
Click to expand...
Click to collapse
Restore your nandroid backup
alejo7797 said:
When I knew CyanogenMod 11s had been ported to the nexus 5, I set off to get it on my device. I had stock android 4.4.4 running, had rooted my phone, and had cwmr.
I got into recovery mode, wiped data, wiped cache and flashed. It din't work. I wiped dalvik cache and tried again, but still didn't work.
Now I'm stuck on the google logo screen.
What can I do?
Click to expand...
Click to collapse
Try also wiping system (flashable zip should format it but do it just to be sure) and unmounting system
Also, I'm not sure if it's an actual port or if it's just CM11 with .apk files added, see here: http://forum.xda-developers.com/showpost.php?p=54420961&postcount=9
Lethargy said:
Try also wiping system (flashable zip should format it but do it just to be sure) and unmounting system
Also, I'm not sure if it's an actual port or if it's just CM11 with .apk files added, see here: http://forum.xda-developers.com/showpost.php?p=54420961&postcount=9
Click to expand...
Click to collapse
I formatted system, and unmounted system, but gives the same error
alejo7797 said:
I formatted system, and unmounted system, but gives the same error
Click to expand...
Click to collapse
I don't know then, I've never had many issues flashing ROMs.
alejo7797 said:
I formatted system, and unmounted system, but gives the same error
Click to expand...
Click to collapse
Re-flash download the zip. Then wipe data, system and the caches
Sent from my Nexus 5 using XDA Free mobile app
Install a different ROM.
What error are you getting?
Freshly baked from my Nexus 5
Hmm problem can be in many places. You can redownload the zip...maybe the one you have is corrupted. When you you flash the zip try to uncheck the verify signature option. After you redownloaded the zip. Mount usb storage and conect to your pc to copy the zip to ext card. Wipe data cache system and dalvik before you flash.
Sent from my Nexus 5 using XDA Premium 4 mobile app
So every time I have dirty flashed Euphoria OS, it has frozen at the Google boot screen. This has forced me to wipe system, install the rom, install gapps, and reconfigure settings. What am I doing wrong that can't I update normally without having to wipe system?
stynatu46 said:
So every time I have dirty flashed Euphoria OS, it has frozen at the Google boot screen. This has forced me to wipe system, install the rom, install gapps, and reconfigure settings. What am I doing wrong that can't I update normally without having to wipe system?
Click to expand...
Click to collapse
What works for me is to wipe cache and davlik before I dirty flash the Rom.
Then after flashing the Rom, SuperSu......... etc wipe cache and davlik again before rebooting.
I have never had any problems dirty flashing Euphoria with this method on both Nexus 5 and Nexus 4.
One more thing. I always make sure to have the latest TWRP installed before I attempt any dirty flash.
Latest version as of this post is TWRP 2.8.5.2
joegestes said:
What works for me is to wipe cache and davlik before I dirty flash the Rom.
Then after flashing the Rom, SuperSu......... etc wipe cache and davlik again before rebooting.
I have never had any problems dirty flashing Euphoria with this method on both Nexus 5 and Nexus 4.
Click to expand...
Click to collapse
I usually do both of those things. I will say that I used ROM Installer to update it, but then dirty flashed with twrp and it still didn't work. Maybe next week I should just straight out flash with TWRP first?
Okay I just did this today and the thing STILL happens. I'd flash the update, wipe dalvik/cache, then reboot system. Then it hangs on Google boot screen for at least 10 minutes. Then I go back to TWRP, wipe system, data, cache, and flash it again and then starts to work, but all my apps are gone. Why can't I just flash the update and have it done with it instead of constantly tinkering around? Am I doing something wrong? is this what a dirty flash is?
I noticed this in your Log
"<6>[ 0.514020] [email protected]: Power-off reason: Triggered from UVLO (Under Voltage Lock Out)"
Are you undervolting?
Ignore. Wrong thread.
Bump
stynatu46 said:
Okay I just did this today and the thing STILL happens. I'd flash the update, wipe dalvik/cache, then reboot system. Then it hangs on Google boot screen for at least 10 minutes. Then I go back to TWRP, wipe system, data, cache, and flash it again and then starts to work, but all my apps are gone. Why can't I just flash the update and have it done with it instead of constantly tinkering around? Am I doing something wrong? is this what a dirty flash is?
Click to expand...
Click to collapse
See if this helps.
If you have many apps, try waiting 10 minutes or longer after wiping cache/davlik before rebooting into android. Or you could try a double wipe.
Apparently, it can take quite a while for cache to clear even if TWRP shows complete.
joegestes said:
See if this helps.
If you have many apps, try waiting 10 minutes or longer after wiping cache/davlik before rebooting into android. Or you could try a double wipe.
Apparently, it can take quite a while for cache to clear even if TWRP shows complete.
Click to expand...
Click to collapse
I've tried this several times yesterday, I think I waited 20 minutes and rebooted again to do the same thing. I also don't have that many apps, I only have 4 rows filled in my app drawer
Okay everyone, I found the problem! All I had to do was uninstall the driver/app for CF.lumen before flashing because it tampered with the /system partition making it unable to boot. I then installed it again after the flash was done.
So it seems my lollipop custom hyperdrive rom has come down with a odd hangup suddenly where if I install a new app and then reboot it suddenly comes to a freezing halt after awhile, unless I go back and uninstall the most recently installed app's again and reboot. I've tried clearing dalvik and art cache and regular cache.... My question was what is clearing system, I know if I clear data I loose all my user installed app's info, is system the same thing but preinstalled app's when ya first boot up the rom and your defined choices in settings? What else am I able to do before trying a dirty flash or clean install altogether to get rid of this odd bug?
n1nj4Lo said:
So it seems my lollipop custom hyperdrive rom has come down with a odd hangup suddenly where if I install a new app and then reboot it suddenly comes to a freezing halt after awhile, unless I go back and uninstall the most recently installed app's again and reboot. I've tried clearing dalvik and art cache and regular cache.... My question was what is clearing system, I know if I clear data I loose all my user installed app's info, is system the same thing but preinstalled app's when ya first boot up the rom and your defined choices in settings? What else am I able to do before trying a dirty flash or clean install altogether to get rid of this odd bug?
Click to expand...
Click to collapse
Wiping system partiton would mean that you dont have an OS like in computer if you format the C drive(hypothetically), your pc wont boot up but your data(in hard drive D or E) would be there. Only wipe system from TWRP if you will subsequently flash another ROM. You could do a factory reset instead(goto TWRP click Wipe then Swipe To Factory Reset . If that doesnt solve your problem, flash a stock ROM or switch to a diff custom one.