Been a bit confused on this. When I initially got this phone i317 (rogers), I rooted no problem, got TWRP running no problem and first thing did a nandroid. Flashed the older stable version of paranoid android 2.54 (i believe) which is based on 4.1.2. No issue what so ever.
As well before i go on, I've been rooting phones a while. Never bricked anything and definitely know the concept of the search button.
After running PA for a day or so and not seeing too many people having issues flashing roms on this phone i flashed another ROM (unfortunately I cant remember which one, but it was one of the popular ones on xda) TWRP had no issues flashing.
When the rom booted and android itself loaded i then had three FC errors and android rebooted. Ok thought it was a bit odd. Said screw it and recovered a backup. However any backup i flashed the error continued. Tried flashing the original PA rom again, the issue continued. Eventually had to reflash in odin the original rooted stock rom.
As you have read this issue has been resolved. My question is what happened? Is this a common problem with this device? Is it perhaps an issue going between 4.1.2 and 4.1.1? Is this just an issue with the devices internal memory? I have yet to read anyone having similar issues, however am not on xda as much as i used to be.
I am really just making sure that i am not missing something obvious or if this was simply an isolated issue before i sample some other ROMS floating around this site.
Any input is appreciated.
Sent from my SGH-I317 using Tapatalk
Did you happen to wipe data before you flashed the new Rom? I have never experienced any force closes while flashing roms.
This is what I usually do when going in between roms.
1. Wipe data/cache twice
2. Flash rom
3. Usually start to hate the Rom after the first minute.
4. GO into recovery
5. Wipe data twice
6. Restore from CWM recovery.
7. Fix permissions (just in case there was a mixup (usually helps resolve force closes)
Hope this helps. If you do happen to wipe data then I am as lost as you are . Maybe try fixing permissions? I am fairly new to android but I have been picking up modding it pretty quick.
______________________________________
Phones: iPhone 4 - > iPhone 5 - > Note 2 (Always on AT&T)
ROM: International N7105XXDMA6 by miscom
LINK: http://forum.xda-developers.com/showthread.php?t=2016575
Kernal: Perseus alpha32.1
A lot of bloatware removed.
Screen on time after normal charge: 7-8 hours always.
I don't think this is a process thing.
I always full wipe before a new rom, clear dalvic and such. This was something different.
Have been stuck in many a bootloop, but never one that caused rebooting when a recovery is flashed or a different rom for that matter.
Sent from my SGH-I317 using Tapatalk 2
Some ROMs require a factory reset wipe on top of the cache and dalvik wipe. I've used PA, and when I did the standard cache and dalvik wipe to PA from JellyBeer, I had repeated FCs, which namely was System UI. Even a nandroid restore after a cache and dalvik wipe had no effect. I was still getting the same FCs. I ended up using all four wipes with TWRP and a clean flash of JellyBeer, then a nandroid restore, to get rid of the FCs. Of course, several of my settings got wiped, including DPIs. Some ROMs just don't play well with other ROMs without a factory reset after the cache and dalvik wipe, which gets rid of your settings for a clean flash.
The other possibility is you're going between 4.1 and 4.2 ROMs. 4.2 ROMs create a new directory that puts all your files into due to multi-user login capabilities. Switching to a 4.1 ROM would certainly cause confusion within the phone without transfer the files back outside of the new directory.
Thank you. That was exactly what I needed to know. Was a scary issue the day after I purchased this phone outright lol. Not an issue I've experienced before with any other device.
Cheers.
Sent from my GT-N7105 using Tapatalk 2
Related
It keeps happening on my evo and im using the newest fresh rom and the current radio http://tweetphoto.com/33676911
jxb25 said:
It keeps happening on my evo and im using the newest fresh rom and the current radio http://tweetphoto.com/33676911
Click to expand...
Click to collapse
that's called a Force Close (FC). It usually happens with an unstable ROM/unstable app but more often it happens when you don't wipe (Cache/Dalvik) before installing a custom ROM.
Backup any important data that's not already on your sdcard, go back into recovery, wiple your cache and dalvik, and flash the ROM again. see if that helps you
initial said:
that's called a Force Close (FC). It usually happens with an unstable ROM/unstable app but more often it happens when you don't wipe (Cache/Dalvik) before installing a custom ROM.
Backup any important data that's not already on your sdcard, go back into recovery, wiple your cache and dalvik, and flash the ROM again. see if that helps you
Click to expand...
Click to collapse
even if im coming from the old fresh to the new fresh i still have to wipe
I'm not familiar with Fresh's ROMs, if you read his threads carefully I'm sure he'll tell you which version upgrades require a wipe and which don't. Usually a drastic upgrade will require a wipe. In your case a wipe will most likely fix these FCs
With the learning curve for the EVO still growing, its usually a good idea to wipe data/cache/dalvik when flashing new roms. Even updates. I haven't seen too many "No Wipe Necessary" around this forum. As long as you've got Titanium or MyBackup, wiping isnt as big of a headache as it used to be. Hope you get things figured out. Screwing with these phones can get frustrating. Dont know how many times I wished I hadnt messed with anything.
well i just wiped and reloaded fresh so hopefully this will fix everything
So, over the weekend, my friend's Nexus has started having odd audio issues. He's been using a Paranoidandroid Jellybean ROM and was working fine for the past few weeks. What happens is that whenever an apps needs to play audio through the speaker (YouTube, Google Play Music, Navigation, changing a ringtone) or when the volume is adjusted, the phone locks up then reboots. We have tried wiping the cache, dalvik cache, fixing permissions, reflashing the rom and flashing different roms, flashing roms without flashing the GApps in afterwards, and using a nandroid recovery. All of these proved fruitless as the problem persists through every flash, wipe, and recovery. In addition to the audio problems, the custom alarms that my friend made are now missing and the /data folder is completely empty. I looked in my /data folder on my SGH-T989 just to confirm that the folder is supposed to have data. My question is: is this a hardware issue, a software issue or both? If hardware he can just replace the phone, but if software, he would like to be able to fix it. We have not attempted to flash a stock rom or ODIN the phone back to stock but we do plan to try that.
If you did not do a full wipe before changing from a rom to PA or any other ROM this can cause a lot of unwanted problems. By doing a full wipe, your problem would be solved. If not it's a hardware issue.
Flashing back to stock ROM isn't really a full wipe. If you are afraid of losing data root the phone and titanium backup
Sent from my Galaxy Nexus (AOKP JB | Popcorn Kernel)
Press the thanks button if my post was helpful
Understandable
JamesInsights said:
If you did not do a full wipe before changing from a rom to PA or any other ROM this can cause a lot of unwanted problems. By doing a full wipe, your problem would be solved. If not it's a hardware issue.
Flashing back to stock ROM isn't really a full wipe. If you are afraid of losing data root the phone and titanium backup
Sent from my Galaxy Nexus (AOKP JB | Popcorn Kernel)
Press the thanks button if my post was helpful
Click to expand...
Click to collapse
While that does make sense, this is how it was explained to me. (I may have forgotten to mention this in the OP) This problem did not start after flashing a new ROM but after 2 weeks of use. When we tried to fix the issue, we did do a full wipe (Wipe data, cache, dalvik cache) and reflashed the rom. But what makes this issue more unusual is that when we used the nandroid that he has, the problem persisted and that nandroid was one that had no issues. The /Data folder is also unusual because even after the reflash and nandroid recovery, that folder remains empty. Are these two issues related or is this coincidence that they are happening at the same time? Also, is there any more info that is needed that will aid in trying to fix this problem?
A similar thing started happening to me whenever I'd use the phone (make or receive a call).
I flashed a different kernel and that fixed it for me.
Sent from my Galaxy Nexus using xda app-developers app
That's pretty weird. The data thing could be causing it. Did he download any app that could cause that folder to be affected? You should try full wipe so you can get that folder back. Does the nandroid still have the data?
Sent from my Galaxy Nexus (AOKP JB | Popcorn Kernel)
Press the thanks button if my post was helpful
Things we've tried
We have tried multiple kernels and different ROMs as well. Every time the problem continues. As for the /data folder, a clean wipe with a fresh ROM flash and nandroids result in that folder remaining empty. At this point, he's going to restore the phone to stock and send it to Verizon to get a new one. I'm starting to think that it's a hardware issue that is causing the phone to reboot when the rear speaker is used but as for the data, I can't think of anything except for maybe something in an app (as was suggested by JamesInsights) or a file on his SD card that corrupted something (although, I doubt that seeing as SU would kick in if a file was asking for SU permissions and getting a virus on a Linux based device is difficult).
Added: I would like to provide a logcat but I don't have the phone near me and I haven't learned to do that yet.
So I've been flashing a couple of different roms this week like Carbon (based on AOSP), PACMAN (Don't know what it's based on), Rootbox (based on AOKP) and Slimbean (AOSP) the method I've been using to flash is wiping data/factory reset, wiping cache/dalvic cache, flashing ROM & gapps, flashing NexusLouder mod, flashing custom kernel, advance restoring data only then rebooting. I think this could be the cause of the boot loops. Or... it could be the function implemented in Carbon which doesn't require you to constantly flash gapps anymore since it backs everything in /system/apps. Anyone know what the cause of the boot loops are for sure?
Extra details - I started using this method ever since I was on AOKP which was my first custom rom. Then a few months ago, I moved to Rootbox, then Carbon, then I tried out PACMAN for a while then reverted back and just today I went back to Rootbox for a while, then I tried out SlimBean and ever since today, I've been getting random bootloops when I restart my phone. It doesn't happen every time I reboot my phone but when it does, clearing the cache solves the problem temporarly and I also had to do a full restore of my nandroid a couple of times today.
Also, I use this method because I have over 75 songs on my playlist which I spent hours creating and I don't want to start all over again. I also don't want to set all my rom settings again either.
Reduce any OC
Undo any Voltage mods
Disable any apps that alter how the system behaves
Disable all apps and enable one by one until you have an issue
You get the idea.
Definitely want to avoid restoring data from another rom and flashing audio mod. If after flashing a new rom you still get the random reboot then you can narrow down the problem.
Sent from my Galaxy Nexus
an easy hint may help: always wipe cache and dalvik AFTER flashing rom, mods... to prevent conflicts :good:
samersh72 said:
an easy hint may help: always wipe cache and dalvik AFTER flashing rom, mods... to prevent conflicts :good:
Click to expand...
Click to collapse
I always do that :thumbup:
Sent from my Galaxy Nexus using xda premium
samersh72 said:
an easy hint may help: always wipe cache and dalvik AFTER flashing rom, mods... to prevent conflicts :good:
Click to expand...
Click to collapse
Thanks for the tip
[Q] Help? I get this when flashing a new rom "Unfortunately setup wizard has stopped"
I have a Galaxy s3 and I have twrp installed. And so far I have tried flashing 4 or 5 different custom roms and every time I end up getting this message "Unfortunately setup wizard has stopped" and then some message about ".com.goolge gpapps has stopped".
I am flashing the rom's and gapps from trwp. And I get the success comment after both the rom and gapps flash. I then restart/reboot and the new rom's custom boot animation comes up, like with cm10 the blue clockwork logo spins, and then after 10 or 20 seconds I get the two error messages and thats its. And when I flashed liquid smooth, I got the Liquid Smooth boot animation.as well and the the two messages. I eventually get my phone tuned off and I get it booted back into twrp and restore my backup to my stock rooted setup which is what I currently have running and so far is the only thing I can get to boot up. I have tried cm10 nightlies from the past week and cm10 stable and liquidsmooth, and a couple others. I downloaded several from goo.manager but i most recently tried a cm nightly i downloaded directly from clockworks site.
Any Idea's. I have seen a couple other threads on other devices with a similar problem but most seemed to have the wrong gapps, and I am using the most current gapps, i even downloaded it from multiple sources to double check.
Does the fact my phone is android 4,1,1 and most these roms are 4.1.2 or newer matter? And if so what is the fix?
nwjimmy said:
I have a Galaxy s3 and I have twrp installed. And so far I have tried flashing 4 or 5 different custom roms and every time I end up getting this message "Unfortunately setup wizard has stopped" and then some message about ".com.goolge gpapps has stopped".
I am flashing the rom's and gapps from trwp. And I get the success comment after both the rom and gapps flash. I then restart/reboot and the new rom's custom boot animation comes up, like with cm10 the blue clockwork logo spins, and then after 10 or 20 seconds I get the two error messages and thats its. And when I flashed liquid smooth, I got the Liquid Smooth boot animation.as well and the the two messages. I eventually get my phone tuned off and I get it booted back into twrp and restore my backup to my stock rooted setup which is what I currently have running and so far is the only thing I can get to boot up. I have tried cm10 nightlies from the past week and cm10 stable and liquidsmooth, and a couple others. I downloaded several from goo.manager but i most recently tried a cm nightly i downloaded directly from clockworks site.
Any Idea's. I have seen a couple other threads on other devices with a similar problem but most seemed to have the wrong gapps, and I am using the most current gapps, i even downloaded it from multiple sources to double check.
Does the fact my phone is android 4,1,1 and most these roms are 4.1.2 or newer matter? And if so what is the fix?
Click to expand...
Click to collapse
Are you wiping system and data before flashing? This is most likely your issue.
zelendel said:
Are you wiping system and data before flashing? This is most likely your issue.
Click to expand...
Click to collapse
yes, cache and dalvik, and a factory reset.
nwjimmy said:
yes, cache and dalvik, and a factory reset.
Click to expand...
Click to collapse
Ok what you have to try is this.
Boot into recovery and wipe system and data (removes settings so you will need to reset up everything) They wipe delvic cache and normal cache, then flash the rom and the proper gapps for the rom.
zelendel said:
Ok what you have to try is this.
Boot into recovery and wipe system and data (removes settings so you will need to reset up everything) They wipe delvic cache and normal cache, then flash the rom and the proper gapps for the rom.
Click to expand...
Click to collapse
On the wipe screen in twrp there is a system option but for data it says format data? Do I need to wipe "system" and "format data"? or does the wipe system option take care of what i need to do? If I need to also select "format data" which do I do first ? format data or system wipe? will i need to wipe cache or dalvik as well, or will those be wiped in the system wipe? Sorry for all the ?'s I am a real noob at all of this.
nwjimmy said:
On the wipe screen in twrp there is a system option but for data it says format data? Do I need to wipe "system" and "format data"? or does the wipe system option take care of what i need to do? If I need to also select "format data" which do I do first ? format data or system wipe? will i need to wipe cache or dalvik as well, or will those be wiped in the system wipe? Sorry for all the ?'s I am a real noob at all of this.
Click to expand...
Click to collapse
No wiping the system doesnt format the data partition. Wipe system then format the data and then wipe the caches and then flash the rom.
Re: [Q] Help? I get this when flashing a new rom "Unfortunately setup wizard has stop
Sounds like your flashing the wrong version of gapps.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Re: [Q] Help? I get this when flashing a new rom "Unfortunately setup wizard has stop
matt_schieman said:
Sounds like your flashing the wrong version of gapps.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Agreed.
Double check your gapps and make sure uts the right version
sent from my 1920 overclocked note 2 running jedi xp12
What gapps should I be using ? I hav gapps jb -20121011. I havnt wiped the additional areas yet either but thats because I want to make sure im installing the correct zip files
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
nwjimmy said:
What gapps should I be using ? I hav gapps jb -20121011. I havnt wiped the additional areas yet either but thats because I want to make sure im installing the correct zip files
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Most rom threads have a download link to the gapps that work with the version of android that specific rom is on. Look in the rom thread for the one you're currently running. There are different gapps for each android version (4, 4.1, 4.2)
I have that same problem too
I was trying to install new roms for my phone i tried liquid smooth and avatar and CM 10. I also tried install a new kernel and also different recoveries but nothing seems to work. I never "dirty" flashed and i use the right gapps. Someone please help me here i hate stock roms!
No matter what Gapps version I've tried I still get this same error. This occurred after trying out the Dark ROM modeled after CM11, but now no matter what ROM I try, this error still occurs. The only time I was ever able to get passed it was using a backup, but that has mysteriously gone AWOL. With that in mind, has anyone actually figured this out? Is there anyone with any USEFUL input? So far all I'm seeing is a bunch of suggestions that don't work.
xantechie said:
No matter what Gapps version I've tried I still get this same error. This occurred after trying out the Dark ROM modeled after CM11, but now no matter what ROM I try, this error still occurs. The only time I was ever able to get passed it was using a backup, but that has mysteriously gone AWOL. With that in mind, has anyone actually figured this out? Is there anyone with any USEFUL input? So far all I'm seeing is a bunch of suggestions that don't
Is your recovery updated to the latest version? Do the roms you are trying support the recovery you are using?
Click to expand...
Click to collapse
fig03 said:
xantechie said:
No matter what Gapps version I've tried I still get this same error. This occurred after trying out the Dark ROM modeled after CM11, but now no matter what ROM I try, this error still occurs. The only time I was ever able to get passed it was using a backup, but that has mysteriously gone AWOL. With that in mind, has anyone actually figured this out? Is there anyone with any USEFUL input? So far all I'm seeing is a bunch of suggestions that don't
Is your recovery updated to the latest version? Do the roms you are trying support the recovery you are using?
Click to expand...
Click to collapse
That's a good point. You should be on TWRP 2.7.0.0 that's the latest version of that recovery.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I use the latest CWM. I'm a creature of habit. The first Samsung I ever put a custom ROM on was done with CWM, so I stick with it. I finally got it to go, but it constantly froze, tried to reset, stuck with the same issue. Never used TWRP, so if someone could actually point me in the right direction, that'd actually be helpful.
xantechie said:
I use the latest CWM. I'm a creature of habit. The first Samsung I ever put a custom ROM on was done with CWM, so I stick with it. I finally got it to go, though...it doesn't really look the way I remember it last it worked, but it's had the issue so long, I forget what it actually looked like before.
Click to expand...
Click to collapse
I have no idea how to use TWRP...it only lists a .img file and no instructions on how to use it. zip files can be used from the bootloader or recovery. WTF am I supposed to do with an .img file. And it can't be to use the terminal emulator because to do that I would have to be able to get passed the Setup Wizard...which is the issue.
I finally figured it out with CWM. Thankfully. The phone would've went flying otherwise.
If anyone else stumbles upon this thread (so they can find the answer for CWM also), you have to format the device from the CWM Recovery to get rid of the crap that is blocking it. I did the following:
Once in CWM Recovery, Remove your SD card to avoid formatting it by accident.
Use the Volume Key to scroll to "mounts and storage".
Format all existing options (this is why the SD needed to be removed); this will blank out the phone's system which was causing the Setup issue to begin with.
Put your SD card with the ROM to be installed back into the phone.
Follow the guide as normal after this (install ROM, then reboot, then KK_gapps, then wipe the two caches, then reboot.)
Hi, in the last minutes i've flashed the 2.7 build of LiquidSmooth Rom from the Paranoid Hello Halo rom... I've done the prcedure like XDA said : Wipe Wipe Wipe (cache, dalvik, system) Flash Rom Flash Gapps. It booted fine but all my apps that i've had on my previous rom was still there... all of them. The most disturbing is my settings were also like I've left them ( disabled pie wifi etc) also my Google Accound was already setuped and good to go. Is it a new feature from flashing 4.2.2 rom to an other 4.2.2 rom ? I've never seen that before. I've also rebooted to make sure it wont boot loop on reboot, and it booted like a charm!
Any clues ?
Weird, never seen that before. Tell us what recovery you have and exactly what you are wiping. Can't think of anything else at the moment I'm sure others will chime in.
Sounds to me like you're not wiping /data. This is where your apps and setting are stored and unless you factory reset using stock recovery, deliberately wipe/format /data, or flash a Rom that wipes it for you, all your apps and settings will remain.
Seems like normal behavior to me.
Sent from my SGH-T999L using xda premium
Ya I re-read it and he just wipes caches and system, definitely need to factory reset lol.
kruse1944 said:
Hi, in the last minutes i've flashed the 2.7 build of LiquidSmooth Rom from the Paranoid Hello Halo rom... I've done the prcedure like XDA said : Wipe Wipe Wipe (cache, dalvik, system) Flash Rom Flash Gapps. It booted fine but all my apps that i've had on my previous rom was still there... all of them. The most disturbing is my settings were also like I've left them ( disabled pie wifi etc) also my Google Accound was already setuped and good to go. Is it a new feature from flashing 4.2.2 rom to an other 4.2.2 rom ? I've never seen that before. I've also rebooted to make sure it wont boot loop on reboot, and it booted like a charm!
Any clues ?
Click to expand...
Click to collapse
Tapatalk.
mt3g said:
Ya I re-read it and he just wipes caches and system, definitely need to factory reset lol.
Click to expand...
Click to collapse
Got it that's why. I was sure wiping system would wipe data too. But do you think its dangerous to not wipe data? Because actually my ROM is rocking right now without issues? Should I reflash it for safety?
It just depends....
It's always best to start clean, especially if you were having problems. But if you want to keep data intact, you should be ok as long as you don't go to an entirely different rom, base, or build.
If you are updating to a newer version of the same build, you're fine. Also if updating to a newer build/version you should be ok, but may have a few hiccups.
However, anytime you go backwards (4.2.2 to 4.1.2) you should wipe it all. The same is true if you are moving to a different base, such as CM to TW. Keeping your internal sdcard data is usually ok, but sometimes it can cause some issues.
Sent from my SGH-T999L using xda premium